US20010019561A1 - Method for setting time stamp in syt field of packet headers for ieee-1394 devices - Google Patents
Method for setting time stamp in syt field of packet headers for ieee-1394 devices Download PDFInfo
- Publication number
- US20010019561A1 US20010019561A1 US09/027,499 US2749998A US2001019561A1 US 20010019561 A1 US20010019561 A1 US 20010019561A1 US 2749998 A US2749998 A US 2749998A US 2001019561 A1 US2001019561 A1 US 2001019561A1
- Authority
- US
- United States
- Prior art keywords
- frame
- packet
- data
- dcl
- presentation time
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/40052—High-speed IEEE 1394 serial bus
- H04L12/40058—Isochronous transmission
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/40052—High-speed IEEE 1394 serial bus
- H04L12/40071—Packet processing; Packet format
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/40052—High-speed IEEE 1394 serial bus
- H04L12/40117—Interconnection of audio or video/imaging devices
Definitions
- This invention relates generally to data communications and, more particularly, to a method for controlling isochronous data communications within a digital system having a bus architecture that complies with the IEEE-1394 Standard for a High Performance Serial Bus.
- bus architectures are known in the prior art, and each bus architecture operates according to a communications protocol that defines the manner in which data transfer between components is accomplished.
- IEEE-1394 Serial Bus Standard A typical serial bus having the IEEE-1394 standard architecture is comprised of a multiplicity of nodes that are interconnected via point-to-point links, such as cables, that each connect a single node of the serial bus to another node of the serial bus. Data packets are propagated throughout the serial bus using a number of point-to-point transactions, wherein a node that receives a packet from another node via a first point-to-point link retransmits the received packet via other point-to-point links.
- serial bus of the IEEE-1394 Serial Bus Standard may be used as an alternate bus for the parallel backplane of a computer system, as a low cost peripheral bus, or as a bus bridge between architecturally compatible buses.
- a communications protocol of the IEEE-1394 Serial Bus Standard specifies two primary types of bus access: asynchronous access and isochronous access.
- Asynchronous access may be either “fair” or “cycle master”.
- Cycle master access is used by nodes that need the next available opportunity to transfer data.
- Isochronous access is used by nodes that require guaranteed bandwidth, for example, nodes transmitting video or audio data.
- the transactions for each type of bus access are comprised of at least one “subaction”, wherein a subaction is a complete one-way transfer operation.
- the video data may be transferred for example, between a mass storage device (e.g., a digital memory such as a hard disk drive, a flash memory device or other storage medium) and a digital video camera or other recorder (e.g., to store an edited video sequence) under the control of a computer processor or other device (e.g., a DMA controller).
- a mass storage device e.g., a digital memory such as a hard disk drive, a flash memory device or other storage medium
- a digital video camera or other recorder e.g., to store an edited video sequence
- the video data is transferred as a series of frames, each frame being made up of a number of data packets.
- the individual data packets include a number header fields (which include various information regarding the data as well as addressing information) as well as the video data itself.
- the frames In order to ensure that each frame of the video data is played out in the proper sequence, the frames must be “time stamped” with an appropriate frame presentation time (e.g., measured in terms of “cycle time” of an isochronous transaction on a bus complying with the IEEE-1394 Serial Bus Standard) when they are recorded.
- the frame presentation time for individual frames of data is recorded in a particular header field, referred to as an SYT field, of the first packet of each frame (note that for non-video applications, the concept of a “frame” is not used and the SYT field may be located and stamped in each packet or only some of the packets of a data transfer).
- the frame presentation time “stamped” in the SYT field of the packet header is an indication to the receiver of the time that the frame should be played out.
- the frame presentation time may be up to 450 sec. in the future. That is, from the point of view of the receiver, the SYT field frame presentation stamp value for a given frame of data must be within 450 ⁇ sec. of the time the first packet in that frame is received.
- the computer processor or other device which is controlling the transfer must insert appropriate frame presentation time stamp (or SYT) values into the SYT fields of the first packet in each frame of the video data.
- the 450 ⁇ sec. requirement is specific to video data and other types of data, e.g., MIDI audio data, may have other frame presentation time requirements.
- a presentation time stamp field of a packet of data for transmission in a digital network is set with a presentation time value determined according to a computed packet rate for the data.
- a presentation time stamp field of a first packet of a second frame of data for transmission in a digital network is set with a presentation time value determined according to a computed packet rate for the data.
- the packet rate may be computed by measuring a difference between a desired presentation time value of a first packet in a first frame of the data and an actual transmission time of the first packet of the first frame. The first frame preceding the second frame in time of transmission within the network.
- FIG. 1 illustrates a digital system having a serial bus made up of a number of nodes and supporting the control of isochronous data according to one embodiment of the present invention
- FIG. 2 shows an exemplary software architecture supporting a Data Stream Command Language (DCL) according to one embodiment of the present invention
- FIG. 3 illustrates a nil terminated DCL program having DCL Jump commands to allow for the transmission of varying packet rates within a digital network according to one embodiment of the present invention
- FIG. 4 illustrates one example of a DCL program which may utilize a ModifyDCLJump operation to control a data stream in a digital system according to one embodiment of the present invention
- FIG. 5 is a flow diagram illustrating one embodiment of the present invention and, particularly, a process for calculating a frame presentation time value from a computed data packet rate and the determination of a new packet rate based thereon;
- FIG. 6 is a flow diagram which summarizes a process for determining a frame presentation time value for frames of data to be transmitted in a digital network according to one embodiment of the present invention.
- FIG. 1 shows an exemplary digital system 5 utilizing the methods of the present invention.
- presentation time stamp fields of data packets for transmission in the digital network 5 may be set with a presentation time value determined according to a computed packet rate for the data.
- the packet rate may be computed by measuring a difference between a desired presentation time value and an actual transmission time of the first packet of a frame of data transmitted prior to a current frame of interest.
- the present invention is described with referencto the transmission of video data within digital network 5 , it should be noted that for non-video applications the concept of a “frame” is not used and the SYT field may be located and stamped in each packet or only some of the packets of a data transfer.
- the present invention is applicable to any digital data transmission within a network having a bus architecture that complies with the IEEE-1394 Standard for a High Performance Serial Bus and is not limited to video data transfer applications.
- the digital system 5 of FIG. 1 includes a central processing unit (CPU) 10 , a monitor 18 , a printer 26 , a video camera 32 , a video cassette recorder (VCR) 36 , a keyboard 42 , and a mouse 46 .
- the CPU 10 includes an internal hard drive 14 and a memory (not shown).
- Each of the devices of digital system 5 is coupled to a local node of the serial bus. In general, the device to which a node is coupled acts as the “local host” for that node.
- the CPU 10 is the local host for the CPU node 12 ; the monitor 18 is the local host for the monitor node 16 ; the printer 26 is the local host for the printer node 24 ; the video camera 32 is the local host for the video camera node 30 ; the VCR 36 is the local host for the VCR node 34 ; the keyboard 42 is the local host for the keyboard node 40 ; the mouse 46 is the local host for the mouse node 44 ; and the internal hard drive 14 is the local host for the internal hard drive node 15 .
- the CPU 10 is the local host for the CPU node 12 ; the monitor 18 is the local host for the monitor node 16 ; the printer 26 is the local host for the printer node 24 ; the video camera 32 is the local host for the video camera node 30 ; the VCR 36 is the local host for the VCR node 34 ; the keyboard 42 is the local host for the keyboard node 40 ; the mouse 46 is the local host for the mouse node 44 ; and the internal hard drive 14 is the local host for the internal hard
- a point-to-point link such as cable 20 is used to connect two nodes to one another.
- CPU node 12 is coupled to internal hard drive node 15 by an internal link 21 , to monitor node 16 by cable 20 , and to keyboard node 40 by a cable 20 e .
- the keyboard node 40 is coupled to the mouse node 44 by a cable 20 f .
- the monitor node 16 is coupled to the nodes of the other peripherals (not shown) by cable 20 a and to the printer node 24 by cable 20 b .
- the printer node 24 is coupled to the video camera node 30 by cable 20 c and to the VCR node 34 by cable 20 d .
- Each of the cables 20 - 20 f and the internal link 21 may be constructed in accordance with the IEEE-1394 Serial Bus Standard and may include a first differential signal pair for conducting a first signal, a second differential signal pair for conducting a second signal, and a pair of power lines.
- Each of the nodes 12 , 15 , 16 , 24 , 32 , 34 , 40 and 44 may have identical construction, although some of the nodes, such as mouse node 44 , can be simplified because of their specific functions. Thus, the nodes can be modified to meet the needs of a particular local host. For example, each node may have one or more ports, the number of which is dependent upon its needs. For example, CPU node 12 , as illustrated, has 3 ports, while the mouse node 44 has only 1 port.
- Digital system 5 supports the transfer of data packets (e.g., made up of digital video and/or audio) associated with a data stream.
- digital video data from hard drive 14 may be transmitted to video camera 32 , e.g., for recording onto digital video tape.
- the video data transmitted to video camera 32 will comprise isochronous data packets in accordance with the IEEE-1394 Serial Bus Standard.
- Each of these isochronous data packets will include header information and payload information.
- the payload information comprises the video data to be recorded.
- the header information is used for routing the video data to the video camera 32 and for error detection and correction.
- the header information of the first packet for each frame of the video data includes a presentation time stamp value within an SYT field of the header.
- the presentation time stamp value is determined according to a computed packet rate for the data, as discussed further below.
- the video data is transmitted on a particular isochronous channel within digital system 5 .
- the isochronous channel is identified by a channel identification number (channel ID).
- channel ID is maintained in a data record stored in the digital system 5 (e.g., in the memory associated with CPU 10 ) and is used by the various application programs and driver routines running on CPU 10 to coordinate the transfer of data.
- the use of a common channel ID allows the interoperation of application programs, driver routines, and other software routines which otherwise may not be capable of operating together.
- the present invention takes advantage of a feature of currently available hosts designed for use with the IEEE-1394 Serial Bus Standard.
- Current hosts and/or their associated nodes
- the cycle number is determined from the cycle time found in the cycle start packet broadcast by the cycle master on the bus.
- the cycle time indicates the cycle number.
- the local host and/or its respective node, associated with the data transmitting device is programmed to begin transmission on a particular isochronous cycle number (“N”).
- This SYT value may be precomputed for the data (e.g., using equation (1) above) in advance of the actual data transmission, thus avoiding the hardware interrupt latency issues described above.
- the appropriate SYT value is written into the SYT field of the first packet (e.g., using conventional techniques for establishing the header of a packet to be transmitted on a bus complying with the IEEE-1394 Serial Bus Standard) for each corresponding frame of data to be transmitted.
- M the packet rate for the data
- M may not be an integer value.
- M the packet rate for the data
- the data stream command language (DCL) is, in one embodiment, a set of commands that control data flow into or out of a data stream, such as the data stream between hard drive 14 and camera 32 discussed above.
- a collection of DCL commands are connected together into a linked list to form a DCL program which can be assigned to a particular data stream such as a data stream associated with an isochronous channel.
- the default execution order of a DCL program is to start with the first DCL command in the program and to follow the DCL command links. This execution order may be changed by using DCL jump commands. Accordingly, if every frame in a data stream is characterized by a DCL program which includes 267 packets/frame, appropriate DCL jump commands may be inserted into the program stream to allow a transmitter to send 267 packets per frame or to send only 266 packets per frame.
- FIG. 2 illustrates a software architecture 48 supporting the DCL.
- An application program 50 running on digital system 5 may provide a user interface which allows a user to control the transfer of digital video data to camera 32 .
- a driver 54 called by the application program 50 may utilize DCL services provided by a services library 56 to develop a DCL program to control the data streams which make up the transfer.
- Each data stream contains data packets as described above and in the IEEE-1394 Serial Bus Standard.
- the DCL program generated by the driver 54 will consist of a nil terminated linked list of DCL commands. At least a minimum set of commands are provided to control the data stream.
- a DCLSendPacketStartOp command may be used to specify the first part of a packet to be sent to a data stream (e.g., from hard drive 14 ). Subsequent parts of a packet may be specified using a DCLSendPacketOp command.
- a packet is defined as a contiguous string of DCL packet commands that start with a DCL packet start command and end with any DCL command that is not a DCL packet command.
- scatter/gather lists may be used in constructing packets.
- a DCL compiler may sum respective size fields in any DCL packet start and packet commands defining the packet of interest.
- DCL send packet buffers need not include a packet header. Instead, a packet header will be constructed by the compiler, based upon the channel number for the data stream associated with the DCL program, any tag and sync bits specified by a DCLSetPacketAttributes command and the computed length of the packet.
- Exemplary DCLCommands and records e.g., DCLSendPacketStartOp, DCLSendPacketOp, DCLTransferPacket, DCLReceivePacketStartOp, DCLReceivePacketOp, DCLReceiveBufferop, DCLCallProcDCLSetPacketAttributesOp, DCLLabelOp, and DCLJumpOp are described in detail in U.S. patent application Ser. No. 08/731,173, entitled “Software Architecture for Controlling Data Streams”, filed Oct. 10, 1996, by Erik P. Pope and assigned to the Assignee of the present application, the entire disclosure of which is incorporated herein by reference.
- the DCLJumpOp command is used to change the default order of a DCL program.
- the DCLJumpOp command may be used by a driver to create a looping DCL program, as shown in FIG. 3.
- the DCL program includes the DCUump command which allows for the looping (e.g., by pointing to an earlier DCL label in the program stream) and is also nil terminated to allow for ease of compilation.
- the DCLJumpOp command may use the following record. struct DCLJumpStruct ⁇ DCLCommandPtr pNextDCLCommand; UInt32 compilerData; UInt32 opcode; DCLLabelPtr pJumpDCLLabel; ⁇ ; typedef struct DCLJumpStruct DCLJump *DCLJumpPtr; pNextDCLCommand Link to next DCL command in program. compilerData DCL compiler's private data. opcode Opcode specifying type of DCL command. pJumpDCLLabel Pointer to DCL label to jump to.
- the pJumpDCLLabel field specifies the DCL label command to jump to.
- the services library 56 also provides a means to update a DCL program.
- the SetDCLProgramCompilerNotificationProc sets the routine to call when a DCL program is updated and is typically called by an interface module. If a driver wishes to change a DCL command while a DCL program is running, the compiler must be notified to change the corresponding DMA commands. This may happen, for example, if a driver wishes to change the destination of a DCL jump command by calling DCLModifyJump (see below).
- the DCLModifyJump routine will call the DCL program's notification routine and pass it the DCL jump command that has been modified. The modification routine then makes any changes necessary to change the target of the jump command.
- a sample call is as follows. OSStatus SetDCLProgramCompilerNotificationProc ( DCLProgramID dclProgramID, DCLCompilerNotificationProcPtr dclCompilerNotificationProc); --> dclProgramID DCLProgramID to set start event of. --> dclCompilerNotificationProc Proc to call on DCL program updates.
- the ModifyDCLJump operation is provided to modify a DCL jump command in a DCL program that is currently running.
- a sample call for this routine is as follows.
- OSStatus ModifyDCLJump DCLProgramID dclProgramID, DCLJumpPtr pDCLJump, DCLLabelPtr pDCLLabel
- --> dclProgramID DCLProgramID to set start event of.
- This routine may be called while a DCL program is in progress as illustrated with reference to FIG. 4.
- the DCL program 100 shown in FIG. 4 has been created to transfer video data to camera 32 , e.g., for recording on a video tape.
- the buffer's contents will be updated by the associated driver with a new frame of data.
- the program is written to always transmit a certain number of packets per frame (e.g., 267 packets/frame) unless certain jump instructions (e.g., jump instruction 100 ) are modified as the program is running.
- a driver has created a frame transmission operation having a number of DCL send packet commands 104 .
- DCL call procedure (call proc) command 106 which notifies the driver that a frame of data has been sent and that the associated buffer should be updated with new data.
- the driver has placed a DCL jump command 102 . So long as the data in a buffer following a DCL jump command should be transmitted, the DCL jump command will simply jump to a DCL label (note, for clarity the label commands have not been shown in FIG.
- the DCL jump command will jump to a DCL label beyond that packet.
- the driver will call ModifyDCLJump to set the DCL jump command before the 267th packet to point to a DCL label beyond the associated buffer (i.e., DCL jump command 102 will be modified to point to DCL Call Proc command 106 ).
- the 267th packet (which is an empty packet as there are typically fewer than 266 packets of true video data per frame—the remaining packets being empty packets) will be sent.
- ⁇ z SYT [z] ⁇ (cycle start # for frame z ) ⁇ a.
- the current M is then adjusted (e.g., using the ModifyDCLJump procedure described above) according to the ⁇ for the previously transmitted frame.
- the desired M av 266.5 and that the host transmitter is programmed to begin transmitting frame 0 on cycle 0.
- the present invention involves setting a presentation time stamp field (the SYT field) of a first packet of a given frame of data for transmission in a digital network with a presentation time value (e.g., the SYT value from column 2 of the above table) determined according to a computed packet rate (e.g., M) for the data.
- a current packet rate (M) is used to compute a current SYT value for a frame as described above.
- a new ⁇ is determined as the difference between the current SYT value and the corresponding cycle # for the frame minus a.
- a new packet rate is determined at step 204 . This new packet rate may be used to compute the next M value for the next frame, and so on until all the packets have been transmitted.
- the actual cycle # that a frame begins transmission on must be determined and accounted for.
- Current local hosts and/or their associated nodes developed to be compatible with the IEEE-1394 Serial Bus Standard include a register which maintains the current cycle time. This register can be read during transmit operations and, as a result, a track of the actual cycle time (or cycle #) that transmission of a frame is commenced may be determined. This actual frame transmission time may be compared with (or used in lieu of) the predicted transmission time to compute an appropriate M so as to maintain frame synchronization.
- a host is programmed to begin transmission of data on a desired cycle #, e.g., cycle 0.
- the packet rate for the data is computed (or preset for the first frame as discussed above) at step 302 and, at step 304 , the appropriate SYT value based on the computed packet rate is determined. This SYT value may be stamped into the SYT field of the first packet of the frame at step 306 .
Abstract
Description
- This invention relates generally to data communications and, more particularly, to a method for controlling isochronous data communications within a digital system having a bus architecture that complies with the IEEE-1394 Standard for a High Performance Serial Bus.
- The components of a computer or other digital system are typically coupled to a common bus for communicating information to one another. Various bus architectures are known in the prior art, and each bus architecture operates according to a communications protocol that defines the manner in which data transfer between components is accomplished.
- The Institute of Electrical and Electronic Engineers (IEEE) has promulgated a number of different bus architecture standards including IEEE standards document 1394, entitledStandard for a High Performance Serial Bus (hereinafter “IEEE-1394 Serial Bus Standard”). A typical serial bus having the IEEE-1394 standard architecture is comprised of a multiplicity of nodes that are interconnected via point-to-point links, such as cables, that each connect a single node of the serial bus to another node of the serial bus. Data packets are propagated throughout the serial bus using a number of point-to-point transactions, wherein a node that receives a packet from another node via a first point-to-point link retransmits the received packet via other point-to-point links. A tree network configuration and associated packet handling protocol ensures that each node receives every packet once. The serial bus of the IEEE-1394 Serial Bus Standard may be used as an alternate bus for the parallel backplane of a computer system, as a low cost peripheral bus, or as a bus bridge between architecturally compatible buses.
- A communications protocol of the IEEE-1394 Serial Bus Standard specifies two primary types of bus access: asynchronous access and isochronous access. Asynchronous access may be either “fair” or “cycle master”. Cycle master access is used by nodes that need the next available opportunity to transfer data. Isochronous access is used by nodes that require guaranteed bandwidth, for example, nodes transmitting video or audio data. The transactions for each type of bus access are comprised of at least one “subaction”, wherein a subaction is a complete one-way transfer operation.
- In the case of, for example, digital video data transfers within digital systems conforming to the IEEE-1394 Serial Bus Standard, the video data may be transferred for example, between a mass storage device (e.g., a digital memory such as a hard disk drive, a flash memory device or other storage medium) and a digital video camera or other recorder (e.g., to store an edited video sequence) under the control of a computer processor or other device (e.g., a DMA controller). The video data is transferred as a series of frames, each frame being made up of a number of data packets. The individual data packets include a number header fields (which include various information regarding the data as well as addressing information) as well as the video data itself.
- In order to ensure that each frame of the video data is played out in the proper sequence, the frames must be “time stamped” with an appropriate frame presentation time (e.g., measured in terms of “cycle time” of an isochronous transaction on a bus complying with the IEEE-1394 Serial Bus Standard) when they are recorded. The frame presentation time for individual frames of data is recorded in a particular header field, referred to as an SYT field, of the first packet of each frame (note that for non-video applications, the concept of a “frame” is not used and the SYT field may be located and stamped in each packet or only some of the packets of a data transfer). In essence, the frame presentation time “stamped” in the SYT field of the packet header is an indication to the receiver of the time that the frame should be played out. For digital video data, the frame presentation time may be up to 450 sec. in the future. That is, from the point of view of the receiver, the SYT field frame presentation stamp value for a given frame of data must be within 450 μsec. of the time the first packet in that frame is received. Thus, in the example given above, when the digital video data is transferred from the mass storage device to the recording medium, the computer processor or other device which is controlling the transfer must insert appropriate frame presentation time stamp (or SYT) values into the SYT fields of the first packet in each frame of the video data. Note that the 450 μsec. requirement is specific to video data and other types of data, e.g., MIDI audio data, may have other frame presentation time requirements.
- In the past, such time stamping operations have required the use hardware interrupt procedures to determine a current cycle time which could then be written to the SYT field of a packet. However, there are times at which such interrupt procedures cannot be completed within the 450 μsec. (e.g., for digital video applications) time limitation. As a result, some frames of data are “lost” and any resulting display of the entire video data stream is degraded. It would therefore be desirable to have other solutions which do not rely on the hardware interrupt procedures of the past for time stamping the SYT fields of data in a digital network complying with the IEEE-1394 Serial Bus Standard.
- Methods for controlling isochronous data communications within a digital system having a bus architecture that complies with the IEEE-1394 Standard for a High Performance Serial Bus are described.
- In one embodiment, a presentation time stamp field of a packet of data for transmission in a digital network is set with a presentation time value determined according to a computed packet rate for the data.
- In a further embodiment, a presentation time stamp field of a first packet of a second frame of data for transmission in a digital network is set with a presentation time value determined according to a computed packet rate for the data. The packet rate may be computed by measuring a difference between a desired presentation time value of a first packet in a first frame of the data and an actual transmission time of the first packet of the first frame. The first frame preceding the second frame in time of transmission within the network.
- The present invention is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:
- FIG. 1 illustrates a digital system having a serial bus made up of a number of nodes and supporting the control of isochronous data according to one embodiment of the present invention;
- FIG. 2 shows an exemplary software architecture supporting a Data Stream Command Language (DCL) according to one embodiment of the present invention;
- FIG. 3 illustrates a nil terminated DCL program having DCL Jump commands to allow for the transmission of varying packet rates within a digital network according to one embodiment of the present invention;
- FIG. 4 illustrates one example of a DCL program which may utilize a ModifyDCLJump operation to control a data stream in a digital system according to one embodiment of the present invention;
- FIG. 5 is a flow diagram illustrating one embodiment of the present invention and, particularly, a process for calculating a frame presentation time value from a computed data packet rate and the determination of a new packet rate based thereon; and
- FIG. 6 is a flow diagram which summarizes a process for determining a frame presentation time value for frames of data to be transmitted in a digital network according to one embodiment of the present invention.
- As described herein, methods for controlling isochronous data communications within a digital system having a bus architecture that complies with the IEEE-1394 Standard for a High Performance Serial Bus are provided. For example, FIG. 1 shows an exemplary digital system5 utilizing the methods of the present invention. As will be described in detail below, in one embodiment presentation time stamp fields of data packets for transmission in the digital network 5 may be set with a presentation time value determined according to a computed packet rate for the data. The packet rate may be computed by measuring a difference between a desired presentation time value and an actual transmission time of the first packet of a frame of data transmitted prior to a current frame of interest. Although the present invention is described with referencto the transmission of video data within digital network 5, it should be noted that for non-video applications the concept of a “frame” is not used and the SYT field may be located and stamped in each packet or only some of the packets of a data transfer. The present invention is applicable to any digital data transmission within a network having a bus architecture that complies with the IEEE-1394 Standard for a High Performance Serial Bus and is not limited to video data transfer applications.
- Some portions of the detailed description which follows are presented in terms of data structures, algorithms and symbolic representations of operations on data within a computer network and/or a computer memory. These descriptions and representations are the means used by those skilled in the computer science arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical and/or magnetic signals capable of being stored, transferred, combined, compared and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers or the like. It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise, it will be appreciated that throughout the description of the present invention, use of terms such as “processing”, “computing”, “calculating”, “determining”, “displaying”, or the like, refer to the actions and processes of a computer or other digital system that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
- The digital system5 of FIG. 1 includes a central processing unit (CPU) 10, a
monitor 18, aprinter 26, avideo camera 32, a video cassette recorder (VCR) 36, akeyboard 42, and amouse 46. TheCPU 10 includes an internalhard drive 14 and a memory (not shown). Each of the devices of digital system 5 is coupled to a local node of the serial bus. In general, the device to which a node is coupled acts as the “local host” for that node. For example, theCPU 10 is the local host for theCPU node 12; themonitor 18 is the local host for themonitor node 16; theprinter 26 is the local host for theprinter node 24; thevideo camera 32 is the local host for thevideo camera node 30; theVCR 36 is the local host for theVCR node 34; thekeyboard 42 is the local host for thekeyboard node 40; themouse 46 is the local host for themouse node 44; and the internalhard drive 14 is the local host for the internalhard drive node 15. Those skilled in the art will appreciate that it is not always necessary for every node to have a local host, nor is it necessary that a local host always be powered. - A point-to-point link such as
cable 20 is used to connect two nodes to one another.CPU node 12 is coupled to internalhard drive node 15 by aninternal link 21, to monitornode 16 bycable 20, and tokeyboard node 40 by acable 20 e. Thekeyboard node 40 is coupled to themouse node 44 by acable 20 f. Themonitor node 16 is coupled to the nodes of the other peripherals (not shown) bycable 20 a and to theprinter node 24 bycable 20 b. Theprinter node 24 is coupled to thevideo camera node 30 bycable 20 c and to theVCR node 34 bycable 20 d. Each of the cables 20-20 f and theinternal link 21 may be constructed in accordance with the IEEE-1394 Serial Bus Standard and may include a first differential signal pair for conducting a first signal, a second differential signal pair for conducting a second signal, and a pair of power lines. - Each of the
nodes mouse node 44, can be simplified because of their specific functions. Thus, the nodes can be modified to meet the needs of a particular local host. For example, each node may have one or more ports, the number of which is dependent upon its needs. For example,CPU node 12, as illustrated, has 3 ports, while themouse node 44 has only 1 port. - Digital system5 supports the transfer of data packets (e.g., made up of digital video and/or audio) associated with a data stream. For example, digital video data from
hard drive 14 may be transmitted tovideo camera 32, e.g., for recording onto digital video tape. The video data transmitted tovideo camera 32 will comprise isochronous data packets in accordance with the IEEE-1394 Serial Bus Standard. Each of these isochronous data packets will include header information and payload information. The payload information comprises the video data to be recorded. The header information is used for routing the video data to thevideo camera 32 and for error detection and correction. In addition, and in accordance with one embodiment of the present invention, the header information of the first packet for each frame of the video data includes a presentation time stamp value within an SYT field of the header. The presentation time stamp value is determined according to a computed packet rate for the data, as discussed further below. - The video data is transmitted on a particular isochronous channel within digital system5. The isochronous channel is identified by a channel identification number (channel ID). The channel ID is maintained in a data record stored in the digital system 5 (e.g., in the memory associated with CPU 10) and is used by the various application programs and driver routines running on
CPU 10 to coordinate the transfer of data. The use of a common channel ID allows the interoperation of application programs, driver routines, and other software routines which otherwise may not be capable of operating together. - When video data is to be transmitted, the present invention takes advantage of a feature of currently available hosts designed for use with the IEEE-1394 Serial Bus Standard. Current hosts (and/or their associated nodes) may be programmed to begin transmitting isochronous data on a particular cycle number. The cycle number is determined from the cycle time found in the cycle start packet broadcast by the cycle master on the bus. The cycle time indicates the cycle number. Thus, according to the present invention, the local host and/or its respective node, associated with the data transmitting device is programmed to begin transmission on a particular isochronous cycle number (“N”). Then, assuming that “M” data packets are to be transmitted for each frame (i.e., M is a computed packet rate for the data) and that “x” represents the frame number, then the frame presentation time value to be stamped in the SYT field of the first packet for each frame of data to be transmitted is given by:
- SYT[x]=N+Mx+a, (1)
- where the value “a” is a precomputed offset. In the case of digital video,
- 0<a<450 μsec.
- For example, if the transmitter is programmed to begin transmitting
frame 0 on cycle 0 (i.e., N=0), then -
- This SYT value may be precomputed for the data (e.g., using equation (1) above) in advance of the actual data transmission, thus avoiding the hardware interrupt latency issues described above. When the packets are ready for transmission, the appropriate SYT value is written into the SYT field of the first packet (e.g., using conventional techniques for establishing the header of a packet to be transmitted on a bus complying with the IEEE-1394 Serial Bus Standard) for each corresponding frame of data to be transmitted.
- Unfortunately, M, the packet rate for the data, may not be an integer value. For example, in the case of digital video to be displayed on an NTSC compatible device (e.g., a television or video monitor), M≈266.973. This presents a problem because only an integer number of packets can be transmitted for each frame (i.e., there are no partial packets and even an empty packet counts as one). In addition, there are occasions where no packets are transmitted during an isochronous cycle (e.g., a “missed” cycle). Each of these situations must be accounted for.
- The present invention accommodates the need for a non-integer M as follows. Assume that the desired average M (hereafter Mav) to maintain proper synchronization is 266.5 (as indicated above, NTSC compatibility requires M≈266.973, however, for simplicity in the following examples, 266.5 is used). To achieve an overall Mav=266.5, sometimes the transmitter will need to send 266 packets/frame and sometimes 267 packets/frame. To accommodate such varying frame lengths, a data stream command language is provided. The data stream command language (DCL) is, in one embodiment, a set of commands that control data flow into or out of a data stream, such as the data stream between
hard drive 14 andcamera 32 discussed above. A collection of DCL commands are connected together into a linked list to form a DCL program which can be assigned to a particular data stream such as a data stream associated with an isochronous channel. The default execution order of a DCL program is to start with the first DCL command in the program and to follow the DCL command links. This execution order may be changed by using DCL jump commands. Accordingly, if every frame in a data stream is characterized by a DCL program which includes 267 packets/frame, appropriate DCL jump commands may be inserted into the program stream to allow a transmitter to send 267 packets per frame or to send only 266 packets per frame. - FIG. 2 illustrates a
software architecture 48 supporting the DCL. Anapplication program 50 running on digital system 5 (e.g., in conjunction with an operating system 52) may provide a user interface which allows a user to control the transfer of digital video data tocamera 32. Adriver 54 called by theapplication program 50 may utilize DCL services provided by aservices library 56 to develop a DCL program to control the data streams which make up the transfer. Each data stream contains data packets as described above and in the IEEE-1394 Serial Bus Standard. - The DCL program generated by the
driver 54 will consist of a nil terminated linked list of DCL commands. At least a minimum set of commands are provided to control the data stream. For example, a DCLSendPacketStartOp command may be used to specify the first part of a packet to be sent to a data stream (e.g., from hard drive 14). Subsequent parts of a packet may be specified using a DCLSendPacketOp command. A packet is defined as a contiguous string of DCL packet commands that start with a DCL packet start command and end with any DCL command that is not a DCL packet command. Thus, scatter/gather lists may be used in constructing packets. To determine the total size of a packet, a DCL compiler (e.g., an interface module 58) may sum respective size fields in any DCL packet start and packet commands defining the packet of interest. DCL send packet buffers need not include a packet header. Instead, a packet header will be constructed by the compiler, based upon the channel number for the data stream associated with the DCL program, any tag and sync bits specified by a DCLSetPacketAttributes command and the computed length of the packet. Exemplary DCLCommands and records, e.g., DCLSendPacketStartOp, DCLSendPacketOp, DCLTransferPacket, DCLReceivePacketStartOp, DCLReceivePacketOp, DCLReceiveBufferop, DCLCallProcDCLSetPacketAttributesOp, DCLLabelOp, and DCLJumpOp are described in detail in U.S. patent application Ser. No. 08/731,173, entitled “Software Architecture for Controlling Data Streams”, filed Oct. 10, 1996, by Erik P. Staats and assigned to the Assignee of the present application, the entire disclosure of which is incorporated herein by reference. - The DCLJumpOp command is used to change the default order of a DCL program. For example, the DCLJumpOp command may be used by a driver to create a looping DCL program, as shown in FIG. 3. The DCL program includes the DCUump command which allows for the looping (e.g., by pointing to an earlier DCL label in the program stream) and is also nil terminated to allow for ease of compilation.
- The DCLJumpOp command may use the following record.
struct DCLJumpStruct { DCLCommandPtr pNextDCLCommand; UInt32 compilerData; UInt32 opcode; DCLLabelPtr pJumpDCLLabel; }; typedef struct DCLJumpStruct DCLJump *DCLJumpPtr; pNextDCLCommand Link to next DCL command in program. compilerData DCL compiler's private data. opcode Opcode specifying type of DCL command. pJumpDCLLabel Pointer to DCL label to jump to. - The pJumpDCLLabel field specifies the DCL label command to jump to.
- The
services library 56 also provides a means to update a DCL program. The SetDCLProgramCompilerNotificationProc sets the routine to call when a DCL program is updated and is typically called by an interface module. If a driver wishes to change a DCL command while a DCL program is running, the compiler must be notified to change the corresponding DMA commands. This may happen, for example, if a driver wishes to change the destination of a DCL jump command by calling DCLModifyJump (see below). The DCLModifyJump routine will call the DCL program's notification routine and pass it the DCL jump command that has been modified. The modification routine then makes any changes necessary to change the target of the jump command. Typically, this will involve changing the destination of a DMA branch command. A sample call is as follows.OSStatus SetDCLProgramCompilerNotificationProc ( DCLProgramID dclProgramID, DCLCompilerNotificationProcPtr dclCompilerNotificationProc); --> dclProgramID DCLProgramID to set start event of. --> dclCompilerNotificationProc Proc to call on DCL program updates. - The ModifyDCLJump operation is provided to modify a DCL jump command in a DCL program that is currently running. A sample call for this routine is as follows.
OSStatus ModifyDCLJump ( DCLProgramID dclProgramID, DCLJumpPtr pDCLJump, DCLLabelPtr pDCLLabel); --> dclProgramID DCLProgramID to set start event of. --> pDCLJump Pointer to DCL jump command to modify. --> pDCLLabel Pointer to new destination of the DCL jump command. - This routine may be called while a DCL program is in progress as illustrated with reference to FIG. 4. Suppose the
DCL program 100 shown in FIG. 4 has been created to transfer video data tocamera 32, e.g., for recording on a video tape. Ideally, as a frame of data is transmitted from a respective buffer (e.g., in memory or hard drive 14) to thecamera 32 as part of an associated data stream, the buffer's contents will be updated by the associated driver with a new frame of data. However, to account for situations where the packet rate must be varied (e.g., to achieve a non-integer average packet rate), the program is written to always transmit a certain number of packets per frame (e.g., 267 packets/frame) unless certain jump instructions (e.g., jump instruction 100) are modified as the program is running. - To further illustrate, as shown in FIG. 4, a driver has created a frame transmission operation having a number of DCL send packet commands104. In total, 267 packets/frame are transmitted. At the end of each frame transmission operation is a DCL call procedure (call proc)
command 106 which notifies the driver that a frame of data has been sent and that the associated buffer should be updated with new data. After thesend packet command 104 regarding packet number 266, the driver has placed aDCL jump command 102. So long as the data in a buffer following a DCL jump command should be transmitted, the DCL jump command will simply jump to a DCL label (note, for clarity the label commands have not been shown in FIG. 4) before that buffer, allowing the associated data in the buffer to be passed to the data stream. However, if the buffer following a DCL jump command contains a packet which should not be transmitted (e.g., when only 266 packets/frame are to be transmitted), the DCL jump command will jump to a DCL label beyond that packet. Thus, whenever the driver is notified to only transmit 266 packets, it will call ModifyDCLJump to set the DCL jump command before the 267th packet to point to a DCL label beyond the associated buffer (i.e.,DCL jump command 102 will be modified to point to DCL Call Proc command 106). thus, the 267th packet (which is an empty packet as there are typically fewer than 266 packets of true video data per frame—the remaining packets being empty packets) will be sent. - To determine when the driver should be notified to only send 266 packets, the following routine is used. A value “Δ” is computed so that when
- Δ≧1, M=267, and
- Δ<1, M=266, where
- Δz =SYT[z]−(cycle start # for frame z)−a.
- The cycle start # for the frames is always incremented by the current M to achieve the desired overall average frame rate (Mav=266.5 in this example). The current M is then adjusted (e.g., using the ModifyDCLJump procedure described above) according to the Δ for the previously transmitted frame. To illustrate, assume again that the desired Mav=266.5 and that the host transmitter is programmed to begin transmitting
frame 0 oncycle 0. If M is established to begin at 266 and a=2 (i.e., representing an offset of twice the frame period or 250 μsec.), then new values for M are computed as shown in Table 1 below:TABLE 1 cycle # to begin transmission of M SYT[x] = N + Mavx + a frame x Δ 266 SYT[0] = 0 + (266.5)(0) + 2 = 2 frame[0] begins on cycle 00 266 SYT[1] = 0 + (266.5)(1) + 2 = 268.5 frame[1] begins on cycle 266 0.5 266 SYT[2] = 0 + (266.5)(2) + 2 = 535 frame[2] begins on cycle 532 1.0 267 SYT[3] = 0 + (266.5)(3) + 2 = 801.5 frame[3] begins on cycle 799 0.5 266 SYT[4] = 0 + (266.5)(4) + 2 = 1068 frame[4] begins on cycle 1065 1.0 267 SYT[5] = 0 + (266.5)(5) + 2 = 1334.5 frame[5] begins on cycle 1332 0.5 - From the above Table 1, it can be seen that an SYT value for a current frame is computed using a current M. Then, Δ is computed for the current frame and M is adjusted accordingly for the next frame to achieve an Mav of 266.5.
- In addition, the present invention (at least in this one embodiment) involves setting a presentation time stamp field (the SYT field) of a first packet of a given frame of data for transmission in a digital network with a presentation time value (e.g., the SYT value from
column 2 of the above table) determined according to a computed packet rate (e.g., M) for the data. The packet rate M for any given frame may be computed as the difference between the SYT value for the previous frame and that previous frame's corresponding cycle # (i.e., the cycle # at which the first packet of that previous frame was transmitted) minus a (where a=a precomputed offset). This method is summarized in FIG. 5. - As shown, at
step 200, a current packet rate (M) is used to compute a current SYT value for a frame as described above. Then, instep 202, a new Δ is determined as the difference between the current SYT value and the corresponding cycle # for the frame minus a. Based on the new Δ, a new packet rate is determined atstep 204. This new packet rate may be used to compute the next M value for the next frame, and so on until all the packets have been transmitted. - If no missed cycles had to be accounted for (i.e., if it were assured that a packet were transmitted on each cycle), the above scheme would be complete. However, sometimes a packet is not transmitted every cycle, e.g., if the transmitter is denied access to the bus on a given cycle. In this event, the “missed” packet will be transmitted in the next cycle, i.e., one cycle late. The above algorithm assumes that one packet was transmitted every cycle and would not account for the missed cycle. For example, if in the above table frame[2] actually began transmission on cycle #533 and not 532 as predicted, the actual A for frame[2] would be 0 and not 1.0. Thus, at this point M should be held at 266 to accommodate the missed cycle. Instead, however, the above algorithm predicted that A for frame[2] was 1.0 and, accordingly, changed M to 267. This causes video to be lost as shown in Table 2 below:
TABLE 2 actual cycle # M predicted cycle # to transmission (based on begin transmission Δ of frame x Δ predicted Δ) SYT[x] of frame x (predicted) began (actual) 266 SYT[0] = 2 frame[0] → 0 0 0 2 266 SYT[1] = 268.5 frame[1] → 266 0.5 266 0.5 266 SYT[2] = 535 frame[2] → 532 1.0 533* 0** 267 SYT[3] = 801.5 frame[3] → 799 0.5 800 −0.5*** - To accommodate the possibility that missed cycles may occur, the actual cycle # that a frame begins transmission on must be determined and accounted for. Current local hosts and/or their associated nodes developed to be compatible with the IEEE-1394 Serial Bus Standard include a register which maintains the current cycle time. This register can be read during transmit operations and, as a result, a track of the actual cycle time (or cycle #) that transmission of a frame is commenced may be determined. This actual frame transmission time may be compared with (or used in lieu of) the predicted transmission time to compute an appropriate M so as to maintain frame synchronization.
- Thus a scheme for controlling isochronous data communications within a digital system having a bus architecture that complies with the IEEE-1394 Standard for a High Performance Serial Bus has been described. The process is summarized in FIG. 6 as follows. At
step 300, a host is programmed to begin transmission of data on a desired cycle #, e.g.,cycle 0. The packet rate for the data is computed (or preset for the first frame as discussed above) atstep 302 and, atstep 304, the appropriate SYT value based on the computed packet rate is determined. This SYT value may be stamped into the SYT field of the first packet of the frame atstep 306. The process of determining a packet rate (e.g., based on the SYT value of a previous frame as discussed above) continues until all frames of the data have been transmitted or the process has otherwise been terminated. In the foregoing specification, the invention has been described with reference to specific exemplary embodiments thereof. It will, however, be appreciated by those skilled in the art that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention as set forth in the appended claims. The specification and drawings are accordingly, to be regarded in an illustrative rather than a restrictive sense.
Claims (5)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/027,499 US6373821B2 (en) | 1998-02-20 | 1998-02-20 | Method for setting time stamp in SYT field of packet headers for IEEE-1394 devices |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/027,499 US6373821B2 (en) | 1998-02-20 | 1998-02-20 | Method for setting time stamp in SYT field of packet headers for IEEE-1394 devices |
Publications (2)
Publication Number | Publication Date |
---|---|
US20010019561A1 true US20010019561A1 (en) | 2001-09-06 |
US6373821B2 US6373821B2 (en) | 2002-04-16 |
Family
ID=21838076
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/027,499 Expired - Lifetime US6373821B2 (en) | 1998-02-20 | 1998-02-20 | Method for setting time stamp in SYT field of packet headers for IEEE-1394 devices |
Country Status (1)
Country | Link |
---|---|
US (1) | US6373821B2 (en) |
Cited By (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6405275B1 (en) * | 1998-06-15 | 2002-06-11 | Texas Instruments Incorporated | IEEE1394 common isochronous packet (CIP) enhancements for host controllers |
US20040027457A1 (en) * | 1999-05-25 | 2004-02-12 | Kia Silverbrook | Image processor having an application specific integrated circuit for camera module |
US20040037309A1 (en) * | 2000-01-18 | 2004-02-26 | Hauck Jerrold V. | Method and apparatus for border node behavior on a full-duplex bus |
US6701371B1 (en) * | 1998-08-29 | 2004-03-02 | Samsung Electronics Co., Ltd. | Data transfer method for matching upper protocal layer to high speed serial bus |
US20050000484A1 (en) * | 2003-07-03 | 2005-01-06 | Schultz James M. | Pre-chambered type spark plug with a flat bottom being aligned with a bottom surface of a cylinder head |
US20080034137A1 (en) * | 2006-07-24 | 2008-02-07 | Colin Whitby-Strevens | Apparatus and methods for de-emphasis training on a point-to-point connection |
US7502338B1 (en) | 2003-12-19 | 2009-03-10 | Apple Inc. | De-emphasis training on a point-to-point connection |
US7650452B2 (en) | 1999-11-05 | 2010-01-19 | Apple Inc. | Method and apparatus for arbitration and fairness on a full-duplex bus using dual phases |
US7653755B1 (en) | 1999-11-02 | 2010-01-26 | Apple Inc. | Method and apparatus for determining communication paths |
US7668099B2 (en) | 2003-06-13 | 2010-02-23 | Apple Inc. | Synthesis of vertical blanking signal |
US7701966B2 (en) | 2000-02-17 | 2010-04-20 | Apple Inc | Method and apparatus for ensuring compatibility on a high performance serial bus |
US7734855B2 (en) | 2003-12-29 | 2010-06-08 | Apple Inc. | Gap count analysis for the P1394a BUS |
US7788567B1 (en) | 2003-11-18 | 2010-08-31 | Apple Inc. | Symbol encoding for tolerance to single byte errors |
US7822898B2 (en) | 2000-01-18 | 2010-10-26 | Apple Inc. | Method and apparatus for border node behavior on a full-duplex bus |
US7861025B2 (en) | 2000-04-21 | 2010-12-28 | Apple Inc. | Method and apparatus for automatic detection and healing of signal pair crossover on a high performance serial bus |
US7970926B2 (en) | 2003-06-13 | 2011-06-28 | Apple Inc. | Synchronized transmission of audio and video data from a computer to a client via an interface |
US7987381B2 (en) | 2003-12-29 | 2011-07-26 | Apple Inc. | Cyclemaster synchronization in a distributed bridge |
US7995606B1 (en) | 2003-12-03 | 2011-08-09 | Apple Inc. | Fly-by and ack-accelerated arbitration for broadcast packets |
US8250100B2 (en) | 1999-10-28 | 2012-08-21 | Apple Inc. | General purpose data container method and apparatus for implementing AV/C descriptors |
US8275910B1 (en) * | 2003-07-02 | 2012-09-25 | Apple Inc. | Source packet bridge |
US20120281704A1 (en) * | 2011-05-02 | 2012-11-08 | Butterworth Ashley I | Methods and apparatus for isochronous data delivery within a network |
US8789939B2 (en) | 1998-11-09 | 2014-07-29 | Google Inc. | Print media cartridge with ink supply manifold |
US8823823B2 (en) | 1997-07-15 | 2014-09-02 | Google Inc. | Portable imaging device with multi-core processor and orientation sensor |
US8896724B2 (en) | 1997-07-15 | 2014-11-25 | Google Inc. | Camera system to facilitate a cascade of imaging effects |
US8902333B2 (en) | 1997-07-15 | 2014-12-02 | Google Inc. | Image processing method using sensed eye position |
US8902340B2 (en) | 1997-07-12 | 2014-12-02 | Google Inc. | Multi-core image processor for portable device |
US8908075B2 (en) | 1997-07-15 | 2014-12-09 | Google Inc. | Image capture and processing integrated circuit for a camera |
US8936196B2 (en) | 1997-07-15 | 2015-01-20 | Google Inc. | Camera unit incorporating program script scanner |
US9055221B2 (en) | 1997-07-15 | 2015-06-09 | Google Inc. | Portable hand-held device for deblurring sensed images |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6418150B1 (en) * | 1998-02-20 | 2002-07-09 | Apple Computer, Inc. | Method and apparatus for calibrating an IEEE-1394 cycle master |
US6680944B1 (en) * | 1998-03-09 | 2004-01-20 | Sony Corporation | Apparatus for and method of predictive time stamping of isochronous data packets transmitted over an IEEE 1394-1995 serial bus network |
JPH11317748A (en) * | 1998-05-07 | 1999-11-16 | Pioneer Electron Corp | Transmission interface device for transmission system |
US6748421B1 (en) * | 1998-12-23 | 2004-06-08 | Canon Kabushiki Kaisha | Method and system for conveying video messages |
US7492393B2 (en) * | 1999-02-12 | 2009-02-17 | Sony Corporation | Method of and apparatus for generating a precise frame rate in digital video transmission from a computer system to a digital video device |
US6532232B1 (en) * | 1999-02-26 | 2003-03-11 | Adaptec, Inc. | Method and system for transporting audio/video data over a serial bus |
US6628607B1 (en) | 1999-07-09 | 2003-09-30 | Apple Computer, Inc. | Method and apparatus for loop breaking on a serial bus |
JP2001036549A (en) * | 1999-07-15 | 2001-02-09 | Toshiba Corp | Data processing system and time stamp generating method |
US6671768B1 (en) | 1999-11-01 | 2003-12-30 | Apple Computer, Inc. | System and method for providing dynamic configuration ROM using double image buffers for use with serial bus devices |
US6587904B1 (en) * | 1999-11-05 | 2003-07-01 | Apple Computer, Inc. | Method and apparatus for preventing loops in a full-duplex bus |
US6718497B1 (en) | 2000-04-21 | 2004-04-06 | Apple Computer, Inc. | Method and apparatus for generating jitter test patterns on a high performance serial bus |
US6816492B1 (en) * | 2000-07-31 | 2004-11-09 | Cisco Technology, Inc. | Resequencing packets at output ports without errors using packet timestamps and timestamp floors |
US6853641B2 (en) * | 2000-12-20 | 2005-02-08 | Nortel Networks Limited | Method of protecting traffic in a mesh network |
JP2007528563A (en) * | 2003-05-09 | 2007-10-11 | エルジー エレクトロニクス インコーポレーテッド | Recording medium having data structure for managing at least data area of recording medium, and recording / reproducing method and apparatus |
DE102005014273B4 (en) * | 2005-03-24 | 2012-04-05 | Dspace Digital Signal Processing And Control Engineering Gmbh | Comparison of interfaces between software components |
US7788645B2 (en) * | 2005-05-16 | 2010-08-31 | Texas Instruments Incorporated | Method for guaranteeing timing precision for randomly arriving asynchronous events |
Family Cites Families (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4506358A (en) * | 1982-06-25 | 1985-03-19 | At&T Bell Laboratories | Time stamping for a packet switching system |
US4748620A (en) * | 1986-02-28 | 1988-05-31 | American Telephone And Telegraph Company, At&T Bell Laboratories | Time stamp and packet virtual sequence numbering for reconstructing information signals from packets |
US4894823A (en) * | 1986-02-28 | 1990-01-16 | American Telephone And Telegraph Company | Time stamping for packet system nodes |
DE68920748T2 (en) * | 1989-08-09 | 1995-06-29 | Alcatel Nv | SEQUENTIAL RETURN FOR A INTERMITTENT NODE. |
DE4008080A1 (en) * | 1990-03-14 | 1991-09-19 | Standard Elektrik Lorenz Ag | ATM SWITCH |
EP0639909A1 (en) * | 1993-08-17 | 1995-02-22 | ALCATEL BELL Naamloze Vennootschap | Resequencing system |
US5469466A (en) * | 1994-01-18 | 1995-11-21 | Hewlett-Packard Company | System for highly repeatable clock parameter recovery from data modulated signals |
JP3197766B2 (en) * | 1994-02-17 | 2001-08-13 | 三洋電機株式会社 | MPEG audio decoder, MPEG video decoder and MPEG system decoder |
IT1268195B1 (en) * | 1994-12-23 | 1997-02-21 | Sip | DECODER FOR AUDIO SIGNALS BELONGING TO COMPRESSED AND CODED AUDIO-VISUAL SEQUENCES. |
US5543853A (en) * | 1995-01-19 | 1996-08-06 | At&T Corp. | Encoder/decoder buffer control for variable bit-rate channel |
US5590116A (en) * | 1995-02-09 | 1996-12-31 | Wandel & Goltermann Technologies, Inc. | Multiport analyzing, time stamp synchronizing and parallel communicating |
US5742623A (en) * | 1995-08-04 | 1998-04-21 | General Instrument Corporation Of Delaware | Error detection and recovery for high rate isochronous data in MPEG-2 data streams |
US5682384A (en) * | 1995-10-31 | 1997-10-28 | Panagiotis N. Zarros | Apparatus and methods achieving multiparty synchronization for real-time network application |
US5726989A (en) * | 1995-11-06 | 1998-03-10 | Stellar One Corporation | Method for ensuring synchronization of MPEG-1 data carried in an MPEG-2 transport stream |
US5802057A (en) * | 1995-12-01 | 1998-09-01 | Apple Computer, Inc. | Fly-by serial bus arbitration |
US5883891A (en) * | 1996-04-30 | 1999-03-16 | Williams; Wyatt | Method and apparatus for increased quality of voice transmission over the internet |
JP2930020B2 (en) * | 1996-07-18 | 1999-08-03 | 日本電気株式会社 | Communication control device |
US5838876A (en) * | 1996-09-24 | 1998-11-17 | Sony Corporation | Frame-accurate edit and playback in digital stream recording |
US5930480A (en) * | 1996-10-10 | 1999-07-27 | Apple Computer, Inc. | Software architecture for controlling data streams based on linked command blocks |
US5912880A (en) * | 1996-11-07 | 1999-06-15 | Northern Telecom, Limited | System and method for ATM CBR timing recovery |
JPH10145753A (en) * | 1996-11-15 | 1998-05-29 | Sony Corp | Receiver and its method |
US5845152A (en) * | 1997-03-19 | 1998-12-01 | Apple Computer, Inc. | Method for transmission of isochronous data with two cycle look ahead |
US5878032A (en) * | 1997-11-07 | 1999-03-02 | Northern Telecom Limited | Delay monitoring of telecommunication networks |
-
1998
- 1998-02-20 US US09/027,499 patent/US6373821B2/en not_active Expired - Lifetime
Cited By (100)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8902340B2 (en) | 1997-07-12 | 2014-12-02 | Google Inc. | Multi-core image processor for portable device |
US9544451B2 (en) | 1997-07-12 | 2017-01-10 | Google Inc. | Multi-core image processor for portable device |
US9338312B2 (en) | 1997-07-12 | 2016-05-10 | Google Inc. | Portable handheld device with multi-core image processor |
US8947592B2 (en) | 1997-07-12 | 2015-02-03 | Google Inc. | Handheld imaging device with image processor provided with multiple parallel processing units |
US9060128B2 (en) | 1997-07-15 | 2015-06-16 | Google Inc. | Portable hand-held device for manipulating images |
US8953060B2 (en) | 1997-07-15 | 2015-02-10 | Google Inc. | Hand held image capture device with multi-core processor and wireless interface to input device |
US9584681B2 (en) | 1997-07-15 | 2017-02-28 | Google Inc. | Handheld imaging device incorporating multi-core image processor |
US9560221B2 (en) | 1997-07-15 | 2017-01-31 | Google Inc. | Handheld imaging device with VLIW image processor |
US9432529B2 (en) | 1997-07-15 | 2016-08-30 | Google Inc. | Portable handheld device with multi-core microcoded image processor |
US9237244B2 (en) | 1997-07-15 | 2016-01-12 | Google Inc. | Handheld digital camera device with orientation sensing and decoding capabilities |
US9219832B2 (en) | 1997-07-15 | 2015-12-22 | Google Inc. | Portable handheld device with multi-core image processor |
US9197767B2 (en) | 1997-07-15 | 2015-11-24 | Google Inc. | Digital camera having image processor and printer |
US9191529B2 (en) | 1997-07-15 | 2015-11-17 | Google Inc | Quad-core camera processor |
US9191530B2 (en) | 1997-07-15 | 2015-11-17 | Google Inc. | Portable hand-held device having quad core image processor |
US9185247B2 (en) | 1997-07-15 | 2015-11-10 | Google Inc. | Central processor with multiple programmable processor units |
US9185246B2 (en) | 1997-07-15 | 2015-11-10 | Google Inc. | Camera system comprising color display and processor for decoding data blocks in printed coding pattern |
US9179020B2 (en) | 1997-07-15 | 2015-11-03 | Google Inc. | Handheld imaging device with integrated chip incorporating on shared wafer image processor and central processor |
US9168761B2 (en) | 1997-07-15 | 2015-10-27 | Google Inc. | Disposable digital camera with printing assembly |
US9148530B2 (en) | 1997-07-15 | 2015-09-29 | Google Inc. | Handheld imaging device with multi-core image processor integrating common bus interface and dedicated image sensor interface |
US9143636B2 (en) | 1997-07-15 | 2015-09-22 | Google Inc. | Portable device with dual image sensors and quad-core processor |
US9143635B2 (en) | 1997-07-15 | 2015-09-22 | Google Inc. | Camera with linked parallel processor cores |
US8902357B2 (en) | 1997-07-15 | 2014-12-02 | Google Inc. | Quad-core image processor |
US9137398B2 (en) | 1997-07-15 | 2015-09-15 | Google Inc. | Multi-core processor for portable device with dual image sensors |
US9137397B2 (en) | 1997-07-15 | 2015-09-15 | Google Inc. | Image sensing and printing device |
US9131083B2 (en) | 1997-07-15 | 2015-09-08 | Google Inc. | Portable imaging device with multi-core processor |
US9124736B2 (en) | 1997-07-15 | 2015-09-01 | Google Inc. | Portable hand-held device for displaying oriented images |
US9124737B2 (en) | 1997-07-15 | 2015-09-01 | Google Inc. | Portable device with image sensor and quad-core processor for multi-point focus image capture |
US8902333B2 (en) | 1997-07-15 | 2014-12-02 | Google Inc. | Image processing method using sensed eye position |
US9055221B2 (en) | 1997-07-15 | 2015-06-09 | Google Inc. | Portable hand-held device for deblurring sensed images |
US8908069B2 (en) | 1997-07-15 | 2014-12-09 | Google Inc. | Handheld imaging device with quad-core image processor integrating image sensor interface |
US8953178B2 (en) | 1997-07-15 | 2015-02-10 | Google Inc. | Camera system with color display and processor for reed-solomon decoding |
US8896720B2 (en) | 1997-07-15 | 2014-11-25 | Google Inc. | Hand held image capture device with multi-core processor for facial detection |
US8953061B2 (en) | 1997-07-15 | 2015-02-10 | Google Inc. | Image capture device with linked multi-core processor and orientation sensor |
US8947679B2 (en) | 1997-07-15 | 2015-02-03 | Google Inc. | Portable handheld device with multi-core microcoded image processor |
US8936196B2 (en) | 1997-07-15 | 2015-01-20 | Google Inc. | Camera unit incorporating program script scanner |
US8902324B2 (en) | 1997-07-15 | 2014-12-02 | Google Inc. | Quad-core image processor for device with image display |
US8937727B2 (en) | 1997-07-15 | 2015-01-20 | Google Inc. | Portable handheld device with multi-core image processor |
US8934053B2 (en) | 1997-07-15 | 2015-01-13 | Google Inc. | Hand-held quad core processing apparatus |
US8934027B2 (en) | 1997-07-15 | 2015-01-13 | Google Inc. | Portable device with image sensors and multi-core processor |
US8928897B2 (en) | 1997-07-15 | 2015-01-06 | Google Inc. | Portable handheld device with multi-core image processor |
US8922670B2 (en) | 1997-07-15 | 2014-12-30 | Google Inc. | Portable hand-held device having stereoscopic image camera |
US8922791B2 (en) | 1997-07-15 | 2014-12-30 | Google Inc. | Camera system with color display and processor for Reed-Solomon decoding |
US8913182B2 (en) | 1997-07-15 | 2014-12-16 | Google Inc. | Portable hand-held device having networked quad core processor |
US8908075B2 (en) | 1997-07-15 | 2014-12-09 | Google Inc. | Image capture and processing integrated circuit for a camera |
US8823823B2 (en) | 1997-07-15 | 2014-09-02 | Google Inc. | Portable imaging device with multi-core processor and orientation sensor |
US8913137B2 (en) | 1997-07-15 | 2014-12-16 | Google Inc. | Handheld imaging device with multi-core image processor integrating image sensor interface |
US8836809B2 (en) | 1997-07-15 | 2014-09-16 | Google Inc. | Quad-core image processor for facial detection |
US8913151B2 (en) | 1997-07-15 | 2014-12-16 | Google Inc. | Digital camera with quad core processor |
US8866926B2 (en) | 1997-07-15 | 2014-10-21 | Google Inc. | Multi-core processor for hand-held, image capture device |
US8896724B2 (en) | 1997-07-15 | 2014-11-25 | Google Inc. | Camera system to facilitate a cascade of imaging effects |
US8908051B2 (en) | 1997-07-15 | 2014-12-09 | Google Inc. | Handheld imaging device with system-on-chip microcontroller incorporating on shared wafer image processor and image sensor |
US6405275B1 (en) * | 1998-06-15 | 2002-06-11 | Texas Instruments Incorporated | IEEE1394 common isochronous packet (CIP) enhancements for host controllers |
US6701371B1 (en) * | 1998-08-29 | 2004-03-02 | Samsung Electronics Co., Ltd. | Data transfer method for matching upper protocal layer to high speed serial bus |
US8789939B2 (en) | 1998-11-09 | 2014-07-29 | Google Inc. | Print media cartridge with ink supply manifold |
US20100165141A1 (en) * | 1999-05-25 | 2010-07-01 | Silverbrook Research Pty Ltd | Image processing method for converting non-linear rgb image data to l*a*b* image data |
US7466353B2 (en) | 1999-05-25 | 2008-12-16 | Silverbrook Research Pty Ltd | Method of processing an image in a camera module to produce L*a*b* form image |
US20040212706A1 (en) * | 1999-05-25 | 2004-10-28 | Kia Silverbrook | Image processing method for digital cameras |
US8081219B2 (en) | 1999-05-25 | 2011-12-20 | Silverbrook Research Pty Ltd | Camera module with device independent data transfer |
US8866923B2 (en) | 1999-05-25 | 2014-10-21 | Google Inc. | Modular camera and printer |
US20080036874A1 (en) * | 1999-05-25 | 2008-02-14 | Silverbrook Research Pty Ltd | Modular, multimedia pen having a camera module and a printer module |
US7773124B2 (en) | 1999-05-25 | 2010-08-10 | Silverbrook Research Pty Ltd. | Modular, multimedia pen having a camera module and a printer module |
US7986357B2 (en) | 1999-05-25 | 2011-07-26 | Silverbrook Research Pty Ltd | Image processing method for converting non-linear RGB image data to L*a*b* image data |
US7576775B2 (en) * | 1999-05-25 | 2009-08-18 | Silverbrook Research Pty Ltd | Image processor having an application specific integrated circuit for camera module |
US20040027468A1 (en) * | 1999-05-25 | 2004-02-12 | Kia Silverbrook | Image processor with enhacement unit for camera module |
US20060007488A1 (en) * | 1999-05-25 | 2006-01-12 | Silverbrook Research Pty Ltd | Controller for a modular printer and image capture arrangement |
US20090278944A1 (en) * | 1999-05-25 | 2009-11-12 | Silverbrook Research Pty Ltd | Camera Module |
US20040027457A1 (en) * | 1999-05-25 | 2004-02-12 | Kia Silverbrook | Image processor having an application specific integrated circuit for camera module |
US7301567B2 (en) | 1999-05-25 | 2007-11-27 | Silverbrook Research Pty Ltd | Method of image processing in a camera module |
US8667023B2 (en) | 1999-10-28 | 2014-03-04 | Apple Inc. | General purpose data container method and apparatus for implementing AV/C descriptors |
US8250100B2 (en) | 1999-10-28 | 2012-08-21 | Apple Inc. | General purpose data container method and apparatus for implementing AV/C descriptors |
US7653755B1 (en) | 1999-11-02 | 2010-01-26 | Apple Inc. | Method and apparatus for determining communication paths |
US8140729B2 (en) | 1999-11-05 | 2012-03-20 | Apple Inc. | Method and apparatus for arbitration on a full-duplex bus using dual phases |
US7650452B2 (en) | 1999-11-05 | 2010-01-19 | Apple Inc. | Method and apparatus for arbitration and fairness on a full-duplex bus using dual phases |
US8473660B2 (en) | 1999-11-05 | 2013-06-25 | Apple Inc. | Method and apparatus for arbitration on a data bus |
US20040037309A1 (en) * | 2000-01-18 | 2004-02-26 | Hauck Jerrold V. | Method and apparatus for border node behavior on a full-duplex bus |
US7280491B1 (en) | 2000-01-18 | 2007-10-09 | Apple Inc. | Method and apparatus for border node behavior on a full-duplex bus |
US7822898B2 (en) | 2000-01-18 | 2010-10-26 | Apple Inc. | Method and apparatus for border node behavior on a full-duplex bus |
US7701966B2 (en) | 2000-02-17 | 2010-04-20 | Apple Inc | Method and apparatus for ensuring compatibility on a high performance serial bus |
US9215097B2 (en) | 2000-02-17 | 2015-12-15 | Apple, Inc. | Methods and apparatus for ensuring compatibility on a high performance serial bus |
US8295302B2 (en) | 2000-02-17 | 2012-10-23 | Apple Inc. | Methods and apparatus for ensuring compatibility on a high performance serial bus |
US7861025B2 (en) | 2000-04-21 | 2010-12-28 | Apple Inc. | Method and apparatus for automatic detection and healing of signal pair crossover on a high performance serial bus |
US7970926B2 (en) | 2003-06-13 | 2011-06-28 | Apple Inc. | Synchronized transmission of audio and video data from a computer to a client via an interface |
US7668099B2 (en) | 2003-06-13 | 2010-02-23 | Apple Inc. | Synthesis of vertical blanking signal |
US8838825B2 (en) | 2003-06-13 | 2014-09-16 | Apple Inc. | Synchronized transmission of audio and video data from a computer to a client via an interface |
US9026680B2 (en) | 2003-07-02 | 2015-05-05 | Apple Inc. | Source packet bridge |
US8275910B1 (en) * | 2003-07-02 | 2012-09-25 | Apple Inc. | Source packet bridge |
US20050000484A1 (en) * | 2003-07-03 | 2005-01-06 | Schultz James M. | Pre-chambered type spark plug with a flat bottom being aligned with a bottom surface of a cylinder head |
US7975201B2 (en) | 2003-11-18 | 2011-07-05 | Apple Inc. | Symbol encoding for tolerance to single byte error |
US8321748B2 (en) | 2003-11-18 | 2012-11-27 | Apple Inc. | Symbol encoding for tolerance to single byte errors |
US8607117B2 (en) | 2003-11-18 | 2013-12-10 | Apple Inc. | Symbol encoding for tolerance to single byte errors |
US7788567B1 (en) | 2003-11-18 | 2010-08-31 | Apple Inc. | Symbol encoding for tolerance to single byte errors |
US7995606B1 (en) | 2003-12-03 | 2011-08-09 | Apple Inc. | Fly-by and ack-accelerated arbitration for broadcast packets |
US7502338B1 (en) | 2003-12-19 | 2009-03-10 | Apple Inc. | De-emphasis training on a point-to-point connection |
US7734855B2 (en) | 2003-12-29 | 2010-06-08 | Apple Inc. | Gap count analysis for the P1394a BUS |
US7987381B2 (en) | 2003-12-29 | 2011-07-26 | Apple Inc. | Cyclemaster synchronization in a distributed bridge |
US8392742B2 (en) | 2003-12-29 | 2013-03-05 | Apple Inc. | Cyclemaster synchronization in a distributed bridge |
US20080034137A1 (en) * | 2006-07-24 | 2008-02-07 | Colin Whitby-Strevens | Apparatus and methods for de-emphasis training on a point-to-point connection |
US8483108B2 (en) | 2006-07-24 | 2013-07-09 | Apple Inc. | Apparatus and methods for de-emphasis training on a point-to-point connection |
US20120281704A1 (en) * | 2011-05-02 | 2012-11-08 | Butterworth Ashley I | Methods and apparatus for isochronous data delivery within a network |
US10992404B2 (en) | 2011-05-02 | 2021-04-27 | Apple Inc. | Methods and apparatus for isochronous data delivery within a network |
Also Published As
Publication number | Publication date |
---|---|
US6373821B2 (en) | 2002-04-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6373821B2 (en) | Method for setting time stamp in SYT field of packet headers for IEEE-1394 devices | |
US6621832B2 (en) | Method and apparatus for Improving the Accuracy of Data Transmissions in a Serial Bus Network | |
US5930480A (en) | Software architecture for controlling data streams based on linked command blocks | |
US7561576B2 (en) | Apparatus for and method of predictive time stamping of isochronous data packets transmitted over an IEEE 1394-1995 serial bus network | |
US6708233B1 (en) | Method and apparatus for direct buffering of a stream of variable-length data | |
US7103700B2 (en) | Method of and apparatus for controlling bidirectional streams of isochronous data flowing between an application and a bus structure | |
US6463060B1 (en) | Signal processing circuit | |
US6519268B1 (en) | Asynchronous data pipe for automatically managing asynchronous data transfers between an application and a bus structure | |
US6829225B2 (en) | Method for computing speed map for IEEE-1394 network | |
KR19990082226A (en) | Application programming interface for data management and bus management over the bus structure | |
EP0864984A2 (en) | Data processing apparatus | |
US20110158109A1 (en) | Method of flow control for data transported using isochronous packets over an ieee 1394-2000 serial bus network | |
JPH1069459A (en) | Serial interface controller and control method therefor | |
US20030179719A1 (en) | Method and apparatus for transmitting packets at a transfer rate that depends on a response from a destination | |
US6363428B1 (en) | Apparatus for and method of separating header information from data in an IEEE 1394-1995 serial bus network | |
KR100381647B1 (en) | Data transfer control device and electronic equipment | |
US7194548B1 (en) | Data transmission apparatus, receiving apparatus, and sending apparatus | |
US6904475B1 (en) | Programmable first-in first-out (FIFO) memory buffer for concurrent data stream handling | |
JP2001521356A (en) | Method and apparatus for detecting and controlling the transmission direction of a bus packet in an IEEE 1394 serial bus node | |
US6041286A (en) | Apparatus for and method of accurately obtaining the cycle time of completion of transmission of video frames within an isochronous stream of data transmitted over an IEEE 1394 serial bus network | |
KR19990006761A (en) | Data transmitter, data receiver, data transmitter and data transmission method | |
JP4033915B2 (en) | Data stream control method and apparatus | |
KR100464469B1 (en) | Data transfer controller and electronic device | |
US6421745B1 (en) | Asynchronous connections with scattering page tables for transmitting data from a producer device to a consumer device over an IEEE 1394 serial data bus | |
US6757773B1 (en) | System and method for determining support capability of a device coupled to a bus system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: APPLE COMPUTER, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:STAATS, ERIK P.;REEL/FRAME:009021/0404 Effective date: 19980206 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: APPLE INC., CALIFORNIA Free format text: CHANGE OF NAME;ASSIGNOR:APPLE COMPUTER, INC. A CALIFORNAIA CORPORATION;REEL/FRAME:019399/0923 Effective date: 20070109 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
FPAY | Fee payment |
Year of fee payment: 12 |