TWI328384B - Method and apparatus for enhanced file distribution in multicast or broadcast - Google Patents

Description

丄 328384 IX. DESCRIPTION OF THE INVENTION: TECHNICAL FIELD OF THE INVENTION The present invention relates generally to data communication and, more particularly, to enhanced file distribution in data communication systems in a multicast or multicast environment. [Prior Art] Global network interconnection enables fast access to information regardless of geographic distance. 1 shows a simplified schematic diagram of a global network connection, generally referred to as the Internet, indicated by reference numeral 20. Internet 20 is essentially a network of architectures with different levels of hierarchy. Internet 2 is operated under the Internet Protocol (IP) published by the Internet Engineering Task Force (IEtf). Details of the ip can be found in the Request for IETF (Request f〇r C〇mments) (RFC) 791. Connecting to the Internet 2 is a number of individual networks, sometimes referred to as a local area network (LAN) or a wide area network (WAN), depending on the network size. Some such networks 22, 24 and 26 are shown in Figure i. Within each of the networks 22, 24, and 26, there are several pieces of equipment that are connected to each other and that communicate with each other. Just to name a few examples are computers, printers, and servers, which are commonly referred to as nodes. When a node is connected to the Internet via its Internet 2, the node needs to send the data packet to the IP address. The corresponding node in other networks. Similarly, data packets sent by the corresponding nodes in other networks to the originating node must also conform to ιρ. The application of different pain types makes it necessary for different levels of agreements to work in conjunction with U. Give a few examples. Assume that node 28 in network 22 attempts to download an archive from another node 30 in network 114293.doc 1328384. For file transfers, a higher level agreement called the File Transfer Protocol (FTP) is used very often. FTP can be found in RFC 959, published by the IETF. As such, the data packets sent by node 30 to node 28 must in particular conform to FTP and IP. As another example, assume that node 28 in network 22 browses a website proposed by another node 32 in network 24 via Internet 20. At this point, nodes 28 and 32 may use another higher level agreement called Hypertext Transfer Protocol (HTTP). HTTP is available in RFC 2616, published by the IETF. Similarly, the data packets exchanged must in particular conform to HTTP and IP. The exemplary protocol FTP and HTTP are carried via another intermediate level agreement called the Transmission Control Protocol (TCP). TCP can be found in RFC 793. Under TCP, the goal is to accurately transfer data. As such, the error data is always retransmitted. TCP and TCP-dependent protocols (such as FTP and HTTP) are used for one-to-one applications. Technological development has made data-intensive data transfer possible. For example, a network capable of handling high bandwidths allows for the exchange of multimedia files, such as audio and video files that typically hold large amounts of data. When a large number of nodes receive such multimedia files, the file transfer via the conventional unicast method may be less efficient. In particular, the files need to be copied first and then individually passed to each node. Therefore, there is a need to develop other types of protocols suitable for broadcast or multi-cast services to address the increased need for one-to-many applications. To meet this need, a one-way transport file transfer (FLUTE) protocol specifically adapted for multi-cast file distribution applications has been devised. The FLUTE Agreement can be found on November 14, 2003 by the IETF under the heading "FLUTE-File 110293.doc 1328384

Delivery over Unidirectional Transport" RFC 3926. In the evening broadcast conversation, the traffic flow is more or less unidirectional. That is, if there is a fundamental existence, the reverse data traffic is restricted. There is a broadcast or multiple = delivery application that sends data to many receivers. The data transmitted under the FLUTE protocol is carried over the User Datagram Protocol (UDP), not in the HTTP and FTP protocols. The same is carried on Tcp. Under UDP, the error data is usually not retransmitted. For accurate data transmission, the FLUTE protocol usually transmits data in a redundant manner and uses an error correction scheme. Using the FLUTE protocol, it is transmitted during the file transfer session. One or more files. The files are carried in data packets in the form of asynchronous layered coding (ALC), called ALC packets. Depending on the length of the file, 'each file can be transmitted in one or more ALC packets. The file is called the target. The target can be identified by the file attribute contained in the file transfer table (FDT). At the receiver end, the file attribute is weighted from the ALC packet. The original file "cannot process the received archive object until the corresponding file attribute is correctly received. For the higher guilty nature of Fdt reception, the copied FDT instance usually inserts the payload data in the ALC packet sent to the receiver. At this point, fdt and content standards are transmitted more or less simultaneously. Thus, even if the content file is correctly received (which is not the case), the receiver needs to correctly receive the FDT, retrieve the file attributes from FDT and then process the file. The content file received. That is, the successful decoding and subsequent rendering of the received file depends more or less on the successful download of the file attributes required to process the ALC packet. This dependency inevitably leads to a delay of 110293.doc 1328384 And often adversely affects the quality of content presentation. In addition, users who do not have the correct file attributes make frequent attempts to obtain the required file attributes, thereby occupying the communication channel. Therefore, this may not be the available communication resources. The most effective use. Therefore, it is necessary to provide a more effective solution to obtain a wider range of better quality. In addition, in the communication system providing the broadcast service, the file for broadcasting in the broadcast service can be accessed by the user. The content of the broadcast file is transmitted in a communication session. Sending the file attributes required to process the broadcast file in another communication session. According to the configuration, receiving the file attributes before the content file enables the broadcast file to be downloaded and processed more efficiently. Those skilled in the art will refer to the drawings from the following detailed embodiments. It will be readily appreciated that these and other features are preferred, and the same components are shown in the drawings. [Embodiment] The following embodiments are provided to enable any person skilled in the art to make and use the invention. In the following embodiments, the details are set forth for the purpose of explanation. It will be appreciated that those skilled in the art will recognize that the invention can be practiced without the specific details. In other instances, well-known structures and processes have not been described in detail to avoid obscuring the details of the present invention. The present invention is not intended to be limited to the implementations shown, but rather to the principles and features disclosed herein. The most widely consistent. Figure 2 shows a simplified schematic diagram of an exemplary embodiment of the present invention. The entire system 110293.doc 1328384 is generally indicated by reference numeral 40. In communication system 40, only two networks 42 and 44 are shown for simplicity and clarity of the description. Networks 42 and 44 are linked by a backbone network 46, such as an intranet or the Internet. It is assumed that in this embodiment, network 42 is operated by a service provider. The service provider installs a node 48 in the network 42. In this example, node 48 is referred to as a Broadcast Service Distributor (BSD). Content server 48 can be designed to hold broadcast content as well as related broadcast information provided by the service provider. In the network 44, there is a user node 50 that is capable of receiving services including services provided by the server node 48 via the backbone network 46. In this embodiment, node 50 is depicted as a wireless device, such as a personal digital assistant (PDA), a mobile computer, or a cellular telephone, to name a few. Network 44 supports wireless technologies such as the cdma2000 standard set forth by 3GPP2 (3rd Generation Partnership Project 2), which is an association of several international standards bodies, including the US TIA/EIA (Telecommunications Industry Association/Electronic Industries Association). It should be noted that the network 40 may also support other standards, such as the WCDMA (Broadband Coded Multi-Directional Proximity) standard issued by the 3GPP (3rd Generation Partnership Project), which is coordinated and supported by different European standards bodies. For standards developed by the Forward Link (FLO) web forum, the Forward Link Network Forum promotes associations of different organizations in the wireless industry for standardization in FLO networks. Subscriber unit 50 communicates with network 44 via a wireless access network (RAN) 52. The RAN 52 includes a base station controller/packet data control function (BSC/PDF) 54 coupled to a plurality of base stations (BS) 66A through 66N. In the network 44, a packet data serving node (PDSN) 68 and a broadcast service node (BSN) 70 are constructed. Both PDSN 68 and BSN 70 provide the functionality to establish an interface between backbone network 46 and RAN 52 in network 44 110293.doc -10- 1328384. The installation of BSN7 is used more for multi-cast or broadcast use, while PDSN 68 mostly handles unicast applications. In this specification, the terms multiplex broadcast and broadcast are used interchangeably. In the network 44, there is another server connected to the BSN 70, called the Broadcast Multicast Service (BCMCS) content server 63. Typically, the BCMCS Content Server 63 pre-stores broadcast content and related content of the broadcast content, including material provided by the content server 48 and transmitted via the backbone network 46.

In an exemplary embodiment, communication in certain nodes is depicted as being performed in a wireless manner. However, it should be understood that this need not always be the case. Non-wireless communications via other different components in their nodes are also applicable. For example, instead of a wireless device, node 50 can be a fixed computer or another server that communicates with network 44 via an optical link or a conventional conductive cable.

It is assumed that in this embodiment, the backbone network 46 supports the Internet Protocol (ιρ)β. Before describing the operational details, it is necessary to first generally explain the data packet during the packet data communication via different levels of hierarchy protocols. Processing, and the relationship between their operations under the arm. In the network communication technology, the agreement is tiered according to the Open Systems Interconnection (OSI) type as stated by the International Organization for Standardization (ISO) and the International Telecommunication Union. Telecommunication Standards Sector (ITU_T). The goal is to promote the interoperability of multi-vendor devices. The gp ’ per-level agreement hierarchy has its own specifications. In this way, as long as the specifications of the specific hierarchical structure level are met, it is ensured that the products of this level are open (4) other products of other levels are compatible. - Figure 3 shows a stack of hierarchical hierarchical agreements, which is referred to as "Cooperation 2 I is generally indicated by reference numeral 72. H Internet Engineering 110293.doc 1328384 Working Group (IEtF) Model Construction ^ Agreement Stack 72, the Internet Engineering Task Force model is similar to the OSI model but not exactly the same as the 0SI model. According to the IETF model, the IP protocol stack 72 has five layers, starting from layer to layer 5. Therefore, data packets sent by nodes (such as nodes 48 or 5) shown in Figure 2 must be processed via protocol stack 72. The protocol stack 72 is built into the node in the form of software or hardware or a combination thereof. Similarly, data packets received by the same node must be processed via the same protocol stack 72 but in reverse order. Give an example. Assuming that the data packet is processed for issue from a node (e.g., node 48 (Fig. 2)), the data packet is first created based on one of the associations in the application layer (i.e., layer 5). Layer 5 includes Hypertext Transfer Protocol (HTTP), Service Mail Transfer Protocol (SMTP), File Transfer Protocol (FTp), Instant Transfer Protocol (RTP), and One-Way Transmitting/Asynchronous Layered Encoding (FLUTE/ALC) protocols. Further assume that the data packet is a product of the v〇Ip (Internet Voice Protocol) conversation. The data packet must therefore be formatted according to the RTp format in layer 5, such as a time sensitive data packet that is encoded according to the RTP generated in layer 5, which needs to be processed on the fly. In particular, defective packets are typically not resent but simply discarded to avoid blocking the transmission of other incoming data packets. The RTP data packet is therefore typically carried via the User Data Encapsulation Protocol (UDP) layer in Layer 4. Therefore, the data packet from the RTP in layer 5 must be further represented by UDP in layer 4. On the other hand, if the data packet originates from other protocols in layer 5 (such as FTP), the data packet is typically sent via the Transmission Control Protocol (TCP) in layer 4. Under TCP, the correct delivery of data packets is most important. Thus, H0293.doc -12· always resends the defective packet, although it may slow down the entire data transfer process. The data packets after the transport layer (layer 4) are added with information such as source and destination nicknames. After passing through the transport layer (layer 4), the data packet is then sent to the network layer (layer 3) for processing. In this particular case, the data packet obtained from layer 4 must be reformatted according to IP (for example, based on the source and destination address of the added data packet). The data packet must then be constructed to fit the applicable agreement in the link layer (layer 2). For example, if server node 4$ is connected to the network via Ethernet, layer 2 will be Ethernet as stated in IEEE 802.3, issued by the Institute of Electrical and Electronics Engineers (IEEE). The form of the road agreement. The bottom layer of the protocol stack 72 in Figure 5 is the physical layer (layer 1}, which implements the entity implementation of the data packet transmission. For example, in Figure 2, if the interface g between the node 48 and the network 42 As a conventional wired bond, the physical layer (layer 1) focuses on both the hardware circuit on node 48 and the interface circuit on network 42. As another example, in Figure 2, if node 50 and BS 66A The communication link is an air interface. In this case, the 'physical layer (layer 1) is associated with the atmospheric space and the hardware circuit of the RAN 52 that transmits and receives signals via the atmospheric space. Reference is now made to Fig. 3. As for the exemplary node 5 0 Received data packet (Fig. 2), which must be processed via the same protocol stack 72 but in reverse order (i.e., from layer 1 to layer 5). The operation of the exemplary broadcast process in system 40 is described herein. 2, as previously mentioned, 'assumed that node 48 (i.e., BSD) is installed in network 42 by providing a broadcast service to a service provider with 110293.doc 13 1328384, where node 5 is among the users For example, in this case, node 5〇 can be from another network. Swim to the network 44 and seek access to news clips, such as 7: 〇〇p m. news access available to the service provider of the network = network 42. If the network 44 supports broadcast services, the network 44. A broadcast channel is often maintained for available services. Information on available services can be organized in the form of downloadable files. 'Or, the same information can be presented in the form of a continuous stream of visual data. Lu assumes that 'is available in this illustrative embodiment Services are aggregated into downloadable files in a manner similar to the Broadcast Service Guide (SG), which consists of various organizations in the wireless industry, including service providers, hardware and software vendors, and network operators. The Association Open Action Alliance (1) MA) was released for the purpose of unifying various standards in wireless communication systems. The details of the SG are stated in the "Established Publications" OMA-TS-BCAST-Service-Guide-Vl.~@#$@@. At this point, when in the network 44, the user of the node needs to refer to Sg obtains the available service in φ. For this purpose, the SG must be downloaded from the network 44. The user of the node 5 then selects the service sought and then tunes to the channel carrying the service as provided in the SG. For some services (such as music downloads), the user of the node 5 can first download the file sought and then listen to the downloaded file. For other services (such as news broadcast dialogue), the content of the file sought is downloaded and Presented more or less simultaneously.~ The service sought is presented immediately, as is the case download associated with the service. This approach brings several disadvantages. In particular, because the successful presentation of the archive content depends not only on the success of the content itself. Under 110293.doc 1328384, and depending on the successful download of the archive attributes required to process the content archive. This dependency inevitably leads to delays and often adversely affects the user's The content presentation experience. In addition, in order to better ensure reliable data packet reception, redundant data is usually sent. Therefore, as explained further below, this may not lead to the most efficient use of available communication resources. The file content is transmitted via the FLUTE/ALC protocol. To ensure proper data transfer, the Carousel File Distribution (CFD) method is conventionally used in conjunction with the FLUTE/ALC protocol. Figure 3A shows the FLUTE/ALC protocol. A more detailed representation, and will be discussed further later. Figure 4 shows a method of a CFD scheme operating under the FLUTE/ALC protocol. In Figure 4, reference numeral 74 denotes a file. A multimedia content (such as in this example) The news clip can contain multiple files. In file 74, one of the data packets #1 to #5 represents each ALC data packet. An ALC containing a file transfer table (FDT) 78 also configured in the ALC protocol format. The data packet is associated with the transfer of each file 74. In FDT 78, various parameters or attributes required to decode data packets #1 through #5 are included. The number can include, but is not limited to, file name, file identifier (ID), file source location (ie, URI), rendering time, file size, content type, encoding scheme, forward error correction (FEC) type, and FEC. Related parameters, as well as safety-related parameters (if applicable). In the CFD method, the file is transmitted multiple times. In this example, the file 74 including the content packets #1 to #5 is associated with the associated FDT 78 for the first time. The transmission is carried out in the first pass 73, and then the second pass in the second pass 75. At 110293.doc -15 - 1328384, the first time passes through 73 'FDT 78 before the content packet #(1)5 is transmitted. In the second pass 75, the 'phase' listens to 78 at the end of the content packet #1. The purpose of retransmitting each block is to eliminate the need for all receivers to fully adjust the time in order to receive the standard. That is, the receiver is synchronized for the purpose of receiving the file.

Another reason for repeatedly transmitting each file is to ensure the correctness of the data transfer during the event that the FEC scheme is not installed or the FEC mechanism is not operational even if it is installed. To achieve this, the CFD method is designed to contain three scenes identified by Scene A, BAC as shown in (4) 4. In addition to the three scenarios A, B and C, the failed file download can be advertised. In scenario A, assume that node 5〇 attempts to download file 74. The node 50 needs to successfully receive the FDT 78 during the first pass of u. Assume that the first pass of the FDT 78 download is successful and error-free. Then the node and the subsequent data packet are sent to #5. Assume that the first pass of all the data packets in 73 “to” is also successful. Node 50 can be used in the fdt 78 downloaded from the first pass 73

Information to decode all the packets in packets #1 to #5 for the entire file combination. In scenario B, during the first pass 73 download slot case 74, it is assumed that the capture of the package 78 is successful. It was also successful in the first pass of all the content packets and even after (2) except for the data packet #3. It is assumed that the implemented FEc mechanism does not play a role. In this case, node 5 must wait until the second pass 75 occurs to receive the same data packet during the second pass 75 to compensate for the corresponding defective packet #3 received in the first pass 73. Subsequently, node 5 can use the information from the first pass of FDT 78 to solve all the data 110293.doc 1328384 packets for the reconstruction of file 74. In scene c, even if all the data packets #1 to #5 are correctly downloaded in the first pass 73, the node fails to correctly receive 1; ^ π in the first pass 73. In this case, node 50 must wait until the second pass 75 occurs to retrieve the corresponding FDT 78 to compensate for the correct gfDT 78 from the first pass 73 for proper decoding of all data packets of file 74. Under the condition of unsuitable signal reception, additional steps as described above in Scenes A, 6 and 之 on the top of the FEC may not be able to correct any corrupted data. That is, as mentioned previously, the download of the announceable file 74 fails. In scenario B, the loss of data packet #3 may only affect the quality of the file 74 during rendering. However, in scenario c, the unsuccessful capture of FDT 78 can result in a loss of the entire archive 74, since without FDT 78, the entire archive 74 cannot be processed. In this case, node 50 may have to wait until the next carousal cycle occurs only to have another chance to obtain FDT 78, which may be for many time periods, such as the time period extended by time through 73 and 75. If this happens, then additional time delays and communication channel occupancy are inevitable. If device 50 is a mobile device as in this example, the additional time delay translates into additional power consumption of the device's battery. In the course of action, the preservation of battery life is extremely important. In accordance with an exemplary embodiment of the present invention, the FDT and content data packets are not received within the frequency band as is known in practice. The fact is that as will be described later, the file attributes and content data are received out of band. The term 'intra-band" is interpreted below to mean the transmission of information within the same transmission session via the same transmission channel and further. In-band information H0293.do. •17· 1328384 The example of transmission is shown and described in the transmission process of Figure 4. On the other hand, the term "out-of-band" is interpreted to mean the transmission of information via different transmission sessions, which is independent of the transmission through the same transmission channel or different transmission channels, as illustrated by the transmission process shown in Figure $ and as follows Described. See Figure 5 now. In this embodiment, the archive attribute 82 (such as previously mentioned is included in the comparison with the payload data (such as data packets #1 to #5)

The FDT 78 slot (four) is transmitted separately, that is, outside the band rather than in the band. Preferably, F 传输 is transmitted via the network 4 4 (Fig. 2) and in the broadcast channel. For example, 'fa can be part of the previously mentioned SG. The SG and thus the fa are first obtained by the node 50 seeking the broadcast service. That is, in the first communication session. Get FA 82 during the period. After the FA 82 is properly retrieved, the node % can then tune to the channel based on the information provided in the SG to obtain a content file (such as the standard 84). That is, the content slot is obtained during the second communication session 86. As shown in Figure 5, there is no fdt inserted into the content archive. The truth is that the content files (for example, files 83 and 84) are designed to pass continuously and uninterruptedly. In other words, the content file is downloaded during the communication pair (4) only after the confirmation node 5 has correctly taken the FA 82 during the communication alignment. Therefore, it can be avoided that when both (4) and FDT are in frequency (4) and are received as described above, the successful processing of the file is governed by the successful download of the corresponding FDT during the pass-through process if a defect data packet is found ( For example, the data packet #4 in the period slot 84, and the FEC mechanism installed by the reference numeral in FIG. 5 fails to correct the defect packet 110293.doc • 18· 1328384 #4 ' The second time passes through the corresponding data in 87 to repair the material. If the repair process is unsuccessful, the quality of the file 84 may be degraded to some extent during the presentation. However, the failure scenario C as shown in Figure 4 The situation as described above may not occur. The reason is that, as previously described in (4), the FA 82 has been successfully received during the communication session 81. Operation in the manner described above does not require occupation for fdt transmission. Any of the in-band channels, thereby enabling more targeted content acquisition. # The acquisition time can also be substantially reduced. Therefore, the congestion in the communication channel can be alleviated, thereby facilitating the available communication resources. In addition, if node 50 (Fig. 2) is a mobile device, a shorter file acquisition time means that the time required to wake up the battery of node 50 during the download of the content file is shorter. Therefore, the battery can be saved. It should be further noted that the FA 82 shown in Figure 5 is one of many FAs that need to be obtained for proper decoding of all files of the sought service session, and the file 84 is in the file. One. However, fa 82 has a number of common attributes that are only relevant to file 84 and to other files such as adjacent files 83. Therefore, all FAs can be organized into files suitable for all files in the transmission session. The primary FAe retrieved, or instead of the primary FA, may divide the aggregated FA into two parts. The first part may save the file attributes regarded as longevity. The attributes may include file name, file m, file location, presentation time. And the distribution time window. m, the attribute of the relatively short life can be placed in the second part of the FA. The short life attribute can include the application file size, the transfer file size, the content type, Code scheme, fec type and parameters, and safety-related parameters. The first part can be kept in the middle and relatively unchanged with the time of 110293.doc -19- 1328384. The second part can be updated periodically in sg to reflect Changing conditions.

As mentioned earlier, some of the slots may first be downloaded and said to be executed by the user at a time selected by the user. Examples are music (4) and software update files. Other files may be downloaded first but preferably at a particular time. An example is a news broadcast conversation as will be described below. In either case, according to another aspect of the invention, the content file acquisition and presentation need not be performed simultaneously. Instead, the bidding can be performed individually and before the file rendering process. For the convenience of explanation, a more specific example is explained. Returning now to Figure 2. False 6 In this example again, the user of node 5 wants to watch a news broadcast that is normally available at 7: 〇〇p.m via normal television broadcasts. In the SG broadcast via the network 44, information about the 7:00 p.m. news clip is generally available. Network 44 has information from the service delivery network via backbone network 46. There are two time windows in the SG, namely, · Distribution Window (DW) " &" Rendering Window (PW)". Figure 6 shows this configuration. A time window is set in the DW, in which the node 50 needs to be activated to receive the 7:00 P'm• news conversation file. For example, in this real money, from 5:00 pm to 6:30 pm 'It is the time interval of the node 5 〇 can receive the news file on the other hand, on the other hand, the PW identifies the presentation time of the downloaded news conversation, at 3 In the example it is from 7:00 Pm to 7:30 pm. That is, the files downloaded during this time 3 will be presented as 7:00 p.m. news. The additional benefit of separating DW from PW is 'allowing the user to download the audit file before the presentation time to avoid traffic channel overload during the presentation time that is usually consistent with the peak time. Even a large amount of traffic load in the network 44 during the DW period. In the event, a 110293.doc file download can still slowly flow to its respective receivers with a small amount of traffic and properly completed before the PW begins. Based on the information provided by the SG, it is assumed that node 50 is powered on and is used to receive news clips during a time period from 5:25 p.m. to 5:3 7 p.m. The time required for the download is 12 minutes in this example, which may be shorter than the presentation time, and if appropriate file compression techniques are implemented, the presentation time is 30 minutes in this case. The previously mentioned method of node 50 is shown in the flow chart of FIG. Figure 8 shows a corresponding method implemented by network 44. According to yet another aspect of the present invention, the transfer of payload data can be improved. For file content downloads, the FLUTE/ALC protocol can be used. As mentioned previously, unlike data packets transmitted over the TCP transport layer (Figure 3) in FTP, the data packets in the FLUTE/ALC are carried on the UDP transport layer. FTP is more suitable for one-to-one applications, and the error packets are usually retransmitted, although this slows down the entire transmission process. The FLUTE/ALC protocol via UDP bearer is designed to accommodate multiple broadcast or broadcast applications. The error data is usually not retransmitted. The truth is that the error in data transmission is reduced by using an appropriate forward error correction (FEC) scheme. Referring now to Figure 3A, a schematic representation of the FLUTE/ALC protocol, generally indicated by reference numeral 96, is shown. The data packets of the FLUTE Agreement are carried by the ALC Agreement. The ALC Agreement was stated in RFC 3450, published in December 2002 by the IETF under the heading "Asynchronous Layered Coding (ALC) Protocol Instantiation". The ALC Agreement is one of the basic agreements for multi-cast transmissions. 110293.doc • 21 · 1328384. Data transmission including ALC does not require uplink signal transmission (ie, transmission from the receiver to the transmitter) and uses FEC for reliable data retrieval. The ALC also utilizes a layered coded transport (LCT) architecture block 98 for multi-rate congestion control (CC) 97 and utilizes the FEC architecture block 99 for reliable content delivery. The LCT is described in the December 2002 issue of the "Layered Coding Transport (LCT) Building Block" IETF publication RFC 345 1. The FEC ° FLUTE protocol, which is also issued by the IETF, describes the application of ALC for multi-cast file delivery. However, the conventional FLUTE/ALC protocol is primarily designed for use in non-action environments. The file download process can be further improved in wireless environments where battery power needs to be preserved and air link bandwidth is more critical. To achieve this, each data packet in the payload can be designed to be tighter. Figure 9 shows an exemplary compact ALC data package identified by reference numeral 94 that is formatted to more closely conform to the conventional ALC packet detailed in RFC 3450. The ALC Packet Format 94 has been designed and published in the literature published by 3GPP2. Ding 8 23.346 broadcast / multi-cast monthly good service (1 \ 〇 ] ^ 8) the same. The main difference between the format shown in the data packet 84 and the format detailed in the document 3GPP TS 23.346 is the lack of any intra-band transmission of the file description information (i.e., the file attributes required to process the payload of the data packet 94). FIG. 10 shows another exemplary tight seal package format indicated by reference numeral 96. The data packet 96 is generally improved and suitable for use in a wireless communication environment. In particular, congestion control information is eliminated. In a wireless environment, the wireless medium is a single access component for adjusting multiple access components at different data rates. 110293.doc -22- 1328384 Congestion control is not required. In the data packet 94 shown in Figure 9, the additional burden is a 16-word group. As for the data packet 96 shown in Figure 1 , the additional burden is only 8 words. Figure 11 is a schematic illustration of a portion of a hardware implementation of a device such as node 50 shown in Figure 2, designated by reference numeral 1A, in accordance with an illustrative embodiment of the present invention. Device 100 can be constructed and constructed in a variety of forms, such as, for example, a laptop, PDA, or cellular telephone. Apparatus 100 includes a central data bus 102 that links a number of circuits together. The circuits include a CPU (Central Processing Unit) or a controller 〇4, a receiving circuit 106, a transmitting circuit 108, and a memory unit ι (^ if the device 100 is part of a wireless device, the receiving and transmitting circuit 1〇6 and 108 can be connected to a radio frequency (RF) circuit, but not shown in the drawings. The receiving circuit 106 processes and buffers the signals β before transmitting the received signals to the data bus β2. The transmission circuit 1〇8 processes and buffers the data before the device 1 sends the data from the data bus 102, and the CPU/controller 104 performs the data management function of the data bus 102 and further performs the general data processing function' Executing the contents of the instructions of the memory unit u. Instead of being individually arranged as shown in FIG. 11, or, the transmission circuit 1 8 and the receiving circuit 106 may be part of the CPU/controller 104. The memory unit 11 includes a group An instruction, generally indicated by the reference numeral ι〇ι. In this embodiment, the instructions include, for example, a portion of the protocol stacking function U2 that is capable of handling, in particular, the FLUTE/ALC protocol as described above. The set of instructions also includes a broadcast client function 114 capable of performing the method shown and described in FIG.

110293.doc -23· 1328384 In this embodiment, the memory unit 110 is a RAM (random access memory) circuit. Exemplary instruction portions 112 and 114 are software common programs or modules. The memory unit 11 can be connected to another memory unit (not shown) that is volatile or non-volatile. Or 'memory unit 110 may be composed of other circuit types, such as EEPROM (Electrically Erasable Programmable Read Only Memory), EPROM (Electronic Programmable Read Only Memory), r〇m (read only memory), ASIC (Special Application Integrated Circuit), Disk, Optical Disc, and Other Types Known in the Art FIG. 12 schematically shows a portion of a hardware implementation of a broadcast server, such as one of the BSN devices 70 shown in FIG. It is indicated by reference numeral 12〇. The device 12A includes a central data bus 12h that couples a plurality of circuits together. The circuits include a CPU (Central Processing Unit) or a controller 124, a receiving circuit 126, and a transmitting circuit 128'. 129 and a memory unit 131 » The network data bus (not shown) to which the receiving and transmitting circuits 126 and 128 can be connected is coupled to the network data bus. The receiving circuit 126 processes and buffers the signals received from the network data bus (not shown) before being sent to the internal data bus 122. The transmission circuit 128 processes and buffers the "bedding material before the device 120 issues the data from the data bus 122. Alternatively, transmission circuit 128 and receiving circuit 126 may be collectively referred to as an interface circuit. The CPU/controller 124 performs the data management duties of the data bus 122 and performs the general-purpose material processing functions, including the execution of the memory unit 内3 i command. The database storage unit 129 stores materials such as the SG and its various parameters and content files.

A 110293.doc -24· 1328384 The memory unit 131 includes a set of instructions, generally indicated by the reference numeral ΐ2ι. In this embodiment, the instructions specifically include a portion of the protocol stack 132 and a broadcast host 134. The memory unit 131 can be composed of the memory circuit type as mentioned above and is not repeated any more. The functions of the protocol stack 132 and the broadcast host 134 include groups of instructions in accordance with the present invention, such as those shown in Figures 3 and 8, and as previously described. It should be further noted that the processes described and illustrated in Figures 7 and 8 above may also be encoded as computer readable instructions for execution on any computer readable medium known in the art, and are incorporated herein by reference. In the context of the patent, the term "computer-readable medium," denotes any medium that participates in providing instructions to any processor, such as the CPUs/controllers 1.4 and 124 shown and described in Figures 11 and 12, respectively, for execution. The medium may be of a storage type and may take the form of a volatile or non-volatile storage medium as also previously described, for example in the form of memory cells no and m as described in Figures π and 12. The media may also be of the transmission type and may include coaxial electro-optical, copper wire, photo-iron, and an air interface carrying acoustic and electromagnetic waves capable of carrying signals readable by a machine or computer. Finally, as in this embodiment As described, the Node BSD 48 is described as being installed in the service & donor network 42. This may not always be the case. The BSD 48 may be installed in another network that is not part of the service provider. The out-of-band transmission channels described in the illustrative embodiments can be logically or physically distinguished as is typically practiced in spread spectrum communications. Additionally, different out-of-band conversations can be by different apostrophes rather than as previously mentioned. Separate for identification. Thus, for example, in Figure 5, FDT can be transmitted on Layer 1 (Figure 3) UDP via 110293.doc • 25· 1328384 by a target 埠 corresponding to the first-transmission session. The 4th squad is transmitted with the - target nickname during the first: transmission material. In addition, it should be clear that the flowcharts in Figures 7 and 8 are also adapted to download and execute files, such as music (4), according to user selection. For example, the user can collect and independently determine the file distribution and file presentation window from the SG. In addition, as described in the example, the backbone is described as operating under IP. Other agreements besides IP are possible. For example, in the FLO network, according to the title issued by the FL0 Internet Forum, "FL〇A Bu

The Interface Specification" (^(^〇1112〇〇5〇〇1) agreement will be applicable. In the FLO network, instead of SG, the corresponding file attributes can be placed in System Information (SI), Further details can be found in the literature published by the FLO Network Forum, fl〇f〇rUm2006.005. Further, any of the logic blocks, circuits and algorithm steps described in connection with the embodiments can be implemented in hardware, software, firmware or a combination thereof. Those skilled in the art will appreciate that these and other changes in form and detail may be made without departing from the scope and spirit of the invention. [Simplified Schematic] Figure 1 is a schematic diagram of a global network connection; FIG. 3 is a schematic diagram showing a protocol stack of hierarchical levels; FIG. 3A is a more detailed schematic representation of the FLUTE protocol; FIG. 4 is a schematic representation of the FLUTE protocol; Schematic diagram of a set of methods for a CFD method operating under the agreement; FIG. 5 is a schematic diagram showing a CFD method 110293.doc • 26-1328384 method operating in accordance with an exemplary embodiment of the present invention; FIG. 6 is a view showing the time at different times FIG. 7 is a flow chart showing file capture and processing according to an exemplary embodiment of the present invention; FIG. 8 is a flowchart showing file transfer according to an exemplary embodiment of the present invention; Flow chart

9 is a schematic diagram showing an exemplary compact ALC data packet; FIG. 1A is a schematic diagram showing another tightly sealed packet format suitable for file transfer via wireless communication; FIG. 11 is configured in accordance with an exemplary embodiment of the present invention. A schematic diagram of a portion of a circuit that receives and processes a node of a broadcast archive; and FIG. 2 is a schematic diagram of a portion of circuitry of a node configured to deliver a broadcast archive in accordance with an illustrative embodiment of the present invention. , [Main component symbol description] 20 22 , 24 , 26 28 , 30 ' 32 40 42 ' 44 46 48 50 52 Internet network node communication system / system network backbone network node / content server / server node /BSD User Node/User Unit/Node/Device Radio Access Network (RAN) 110293.doc •27- 1328384

54 Base Station Controller/Packet Data Control Function (BSC/PDF) 63 Broadcast Multicast Service (BCMCS) Content Server 66A, 66N Base Station (BS) 68 Packet Data Service Node (PDSN) 70 Broadcast Service Node (BSN)/BSN Device 72 Agreement Stack 73 First Pass/Time Pass 74 File 75 Second Pass/Time Pass 78 File Transfer Table (FDT) 81 First Communication Dialog/Communication Dialog 82 File Properties/FA 83 File 84 File/Data Packet 85 First Pass 86 Second Communication Conversation/Communication Dialogue 87 Second Pass 90 Defect Packet 96 Data Packet 97 Multirate Congestion Control (CC) 98 Layered Code Transport (LCT) Architecture Block 99 FEC Architecture Block 100 Device/Device 110293.doc -28- 1011328384 102 104 106 108 110 112 114

120 121 122

124 126 128 129 131 132 134 #1 ' #4, A, command central data bus / data bus CPU (central processing unit) or controller receiving circuit transmission circuit memory early dollar agreement stack function / command part broadcast client Function/instruction part device command central data bus/internal data bus/data bus CPU (central processing unit) or controller receiving circuit transmission circuit library storage unit memory unit protocol stack broadcast host #2, #3, data Packet #5 B, C Scene 110293.doc -29-

Claims (1)

1328384 Patent Application No. 095112587 Replacement of Chinese Patent Application (December 98) X. Patent Application Range: A method for downloading a file for broadcasting in a communication system, comprising: in the first communication session Receiving an archive attribute for processing at least one file of the broadcast, wherein the processing includes using the profile to reconstruct the at least one file; and separately receiving the broadcast with the file attributes in a second communication session At least one file. The method of claim 1, further comprising: receiving the file attributes via the first communication channel; and, wherein the at least one file is received by a first communication channel. The method of claim 1, wherein the communication system supports Internet Protocol (IP) 'The method further comprises: receiving the file attributes via a first nickname by the User Datagram Protocol (UDP) of the IP And receiving the at least one ® file via the second nickname by the UDP of the IP. 4. The method of claim </ RTI> further comprising continuously receiving a plurality of files of the broadcast in the second communication session, and receiving the plurality of files for processing the plurality of files in the first communication session An archive attribute, wherein the first communication session is earlier than the second communication session. 5. The method of claim 1, wherein the at least one file comprises a plurality of data packets, the method further comprising not receiving the file attributes in each of the data packets for processing the at least one file. 110293-981211.doc Tour day correction replace g 6. If requested! The method further comprises: - the object squatting μ ^ 匕 3 in the far second communication session t is connected to the plurality of files of the broadcast, and the case belongs to the scorpion and the step includes using some of the files belonging to 1 & quot Born to deal with the plural number of sorrows, Gan + laps a few loose cases 'where some of these file attributes pass* share the case between the multiple files. Yang M煲 is used to process the plurality of files 7· as in the method of claim 1 , straight into a cow „ ^ ^ , the progress package 3 is provided in the file attributes; the at least one selected security person presenting the broadcast Time information of the dead case to allow the at least one file to be presented at a predetermined time. A method for transmitting a file in a communication system, comprising: transmitting in a - communication session 10 for processing the broadcast a slot attribute of at least one of the slots, wherein the processing includes using the slot attribute to reconstruct the at least one file; and transmitting the broadcast at least in the first overnight & 9. The file of claim 8, further comprising: transmitting the file attributes via a first communication channel; and, ''to the at least one file sent by a first pass k channel. 1 〇· The method of claim 8, wherein the communication system supports an internet protocol (IP), the method further comprising: transmitting the files via a first nickname by the user datagram protocol (UDP) of the IP The attribute; and the UDP by the IP sends the at least one file via a second nickname. 110293-981211.doc 2- 11. Commenting on the method of modifying the replacement page such as the kiss item 8 by %ι月//日It further includes continuously transmitting a plurality of files of the broadcast in the second communication session, and transmitting, in the first communication session, the file attributes for processing the plurality of files, wherein the first conversation is earlier than The second communication session. 12. The method of claim 8, wherein the at least one file comprises a plurality of data packets, the method further comprising in each of the data packets Not providing an archive attribute for processing the at least one file. The method of Kissing Item 8, further comprising transmitting the plurality of files of the broadcast in the second communication session, and further comprising the first communication session Providing some of the file attributes, wherein the (4) attributes are generally shared among the plurality of files for processing the plurality of files 0 &quot;months, 8 methods&apos; The attribute includes time information for presenting the at least one (fourth) of the broadcast. A device configured to receive a broadcast in a communication system, comprising: a younger brother, an outsider The component of the archive attribute of the archive is less than one file, and the processing is performed by using the file attribute to reconstruct the at least one file attribute individually for receiving the broadcast in the second communication session with the file. The component of the at least one file, such as the device of claim 15, the further comprising: a structure for receiving the file attributes via a first piece; and a communication channel H0293-981211.doc 1328384 Township π月&quot; The day correction replacement page is for receiving a component of the at least one file via a second communication channel. 17. The device of claim 15, wherein the communication system supports an Internet Protocol (IP), the device further comprising: for receiving the user data protocol (UDP) over the IP via a first nickname a component of the file attribute; and means for receiving the at least one file via the second nickname by the UDP of the IP. 18. The apparatus of claim 15 further comprising means for continuously receiving the plurality of archives of the broadcast in the second communication session, and for receiving in the first communication session for processing the plurality of The component of the file attribute of the file 'where the first-communication session is earlier than the second communication session 0. 19. The device of claim 15 is - ... small 〇 吸 双 卿 卿 买 , , , , , , Each of them - does not include (four) in the processing, at least the file attributes of the file. 2. The device of claim 15, wherein the step further comprises means for receiving the plurality of _ of the broadcast in the second communication pair, and the step of processing comprises processing the file attribute such as Γ=Γ A plurality of components of a file, in which a second file attribute is generally shared among the plurality of files for processing the plurality of files. 21: The device of claim 15 wherein the file attributes include the at least one of the at least one of the macros for presenting the broadcast. At the time of the preview, 110293-981211 .doc 1328384 Lion π Yueqing is replacing the page I 22 · a device for transferring files of a L 1 -> 23 ^ - _I ^ 杈 broadcast in a communication system, The method includes: means for transmitting, in a first communication session, an archive attribute for processing at least one file of the broadcast, the process comprising: using the file attribute to reconstruct the at least one file; The means of the at least one file of the broadcast is individually transmitted with the file attributes in the second communication session. 23. The device of claim 22, further comprising: for communicating via a first pass; S, a call, and a call. The channel develops the components of the archive attributes; and the means for transmitting at least one file via a second pass. 24. The device of claim 22, wherein the device is further configured to: use the User Datagram Protocol (UDP) of the 1P via the first An nickname to send the components of the file attributes; and means for transmitting the at least one file via the _ second nickname by the UDP of the IP. 25. The apparatus of claim 22, further comprising the means for continuously transmitting the plurality of archives of the broadcast in the (four) two communication session and for transmitting the details in the first communication session using ^^ _ Means for processing the file attributes of the plurality of files, wherein the 兮坌-.3 这 通 通 活 活 活 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 26. The device of claim 22, wherein the at least one file comprises a plurality of assets II0293-98I2Ji.doc 1328384 27. 28. 29. The year A//A correction replacement page material package, the device further comprising The file attributes are not provided in each of the data packages for processing the components of the at least one file. The apparatus of claim 22, further comprising means for transmitting the plurality of archives of the broadcast in the second communication session, and further comprising means for providing certain of the archive attributes in the first communication session, Some of these file attributes are typically shared among the plurality of files for processing the plurality of files. The device of claim 22, wherein the file attributes include time information for presenting the at least one file of the broadcast. A device for use in a broadcast in a communication system, comprising: a processor; and a memory unit connected to the processing unit, the memory unit package processor executable instructions, the processors being executable The instructions are for receiving, in a communication session, at least one instance of an attribute for processing the broadcast, wherein the processing includes using the slot attribute to reconstruct the to-file and in-second communication session The at least one file of the broadcast is received with the archive attributes. The device of claim 29, wherein the memory unit further comprises a benefit executable instruction 'the processor executable instructions for receiving the file attributes via a first communication channel' and receiving via a second communication channel The at least one file. The device of claim 29, wherein the communication system supports an internet protocol (IP), the memory unit further comprising processor executable instructions, 30. 31. 110293-981211.doc The Tour (4) &quot;Day Correction Replacement Page Line Order is used to receive the file attributes via the 1P User Datagram Protocol (UDP), via the _ 笛7 brother-nickname, and The UDP of the IP receives the at least one file via the _ &amp;&amp; 32 nickname. The device of claim 29, wherein the memory unit further comprises processing the executable command to enable the processor executable instructions to continuously receive the plurality of broadcasts in the second pass ▲ The file, and the first communication session in the first L pair "the receiving of the plurality of claims for processing the plurality of rights cases" is earlier than the second communication session. The device of claim 29, wherein the at least one file comprises a plurality of files, wherein each of the data packets does not include an archive attribute for the file of μ to &gt;. 34. The apparatus of claim 29, wherein the memory unit further comprises processing a stolen binding instruction, the processor executable instructions for receiving the broadcast, the number of the broadcast in the second conversation Archives' and use some of the attributes of the file to handle the number of files held by the file, wherein some of the file attributes are hanged between the plurality of files for use in processing the plural Files. 35. According to the decoration of claim 29, the file attribute of the basin is set to include the % attribute of the at least one file for presenting the broadcast to allow the presentation to be presented at a predetermined time. At least one file. 36. An apparatus for transmitting a file in a communication system, comprising: a processor; and a memory unit that is consuming to the processor, the memory unit includes 110293.981211.doc 1328384 A year/month modified date page processor executable instructions 'The processor executable instructions are used to send a slot attribute for processing at least one file of the broadcast in a first communication session And wherein the processing includes using the file attribute to reconstruct the at least one instance' and the at least one file of the broadcast is individually transmitted with the file attributes in the second communication session. 37. The device of claim 36, wherein the memory unit further comprises processor executable instructions for use via a first The communication channel transmits the profile attributes and sends the at least one file via a second communication channel. 38. The device of claim 36, wherein the communication (4) system supports an internet protocol; (10), wherein the memory unit further comprises processor-executable instructions for the processor-executable instructions for using the Ip The User Datagram (UDP) sends the file attributes via the - apostrophe, and the at least one broadcast is sent by the second nickname by the UDP. 39. The device of claim 36, wherein the memory unit further comprises The instructions are executable by the processor for transferring one file via the copy of the file transfer (FLUTE). a device of item 36 wherein the memory unit further includes ==, the processor executable instructions for continuously transmitting the plurality of files of the broadcast in the second pass, and at the first lL pair The file is sent to the department, and the files in the middle of the file are 41. The message is earlier than the second communication session. The device of 36 means that the at least one file includes a plurality of files I10293-9812 ll.doc 1328384 material packets, wherein each of the data packets has at least one file attribute of the file. The device of item 36 wherein the memory unit further comprises processing: a processor executable instruction for transmitting a plurality of (four) of the broadcast in the second pass, and in the first communication Providing certain such file attributes, wherein the certain file attributes are shared between the plurality of files for processing the plurality of documents. 43. The device of claim 36, wherein the file attributes include time information for presenting the at least one file of the broadcast. a computer readable medium having computer executable instructions encoded thereon, the computer executable instructions for:, receiving, in a - communication dragon, an archive attribute for processing at least one slot of a broadcast The processing includes using the file attribute to reconstruct the at least one file; and The From Month &quot;Day Correction Replacement page&quot; does not include processing for the at least one file of the broadcast to be individually received with the file attributes in a second communication session. The computer readable medium of claim 44, further comprising computer executable instructions encoded thereon for: receiving the file attributes via a first communication channel; and receiving the at least via a second communication channel a file. 46. The computer readable medium of claim 44, wherein the communication system supports Internet Protocol (IP), the computer readable medium further comprising computer readable instructions for: 110293-981211.doc 1328384 a month &quot; The day correction replacement g receives the file attributes via a first nickname via the ip User Datagram Protocol (UDP); and the UDP via the IP receives the at least one file via a second nickname. 47. A computer readable medium comprising computer executable instructions encoded thereon, the computer executable instructions for: transmitting an archive attribute for processing at least one file of a broadcast in a first communication session Wherein the processing includes using the file attribute to reconstruct the at least one file; and transmitting the at least one file of the broadcast individually with the file attributes in a second communication session. The computer readable medium of claim 47, further comprising computer executable instructions encoded for: transmitting the file attributes via a first communication channel; and transmitting the at least one file via a second communication channel . Stone horse on it 49. The computer executable instructions of claim 47 (4), wherein the computer executable instructions of the __step package (4) are used to: deliver the property of the building via a first user data protocol (UDP); Nickname By (4) the Qing sends the at least one file via a second number 110293-981211.doc