Patent Application
20240130278
In an agricultural setting, harvested product is gathered and collected in the field by a harvester, such as a combine, and the harvester's load is periodically offloaded into a field cart that is hauled by a tractor. Further, the field carts are typically transported to the edge of the field where an over-the-road truck-trailer container waits to receive and haul the aggregated grain from the carts. The trailer container can then haul the grain to a storage or processing facility. Each harvester, grain cart, and on-road trailer container has a target load weight and volume. Further, certain harvesting operations can be impacted by the environmental conditions, such a soil moisture and type of soil, which may be impacted by weight. As such, certain harvesting-related operations in field may have a target weight to mitigate field compaction, to optimize operations, and provide for efficiency.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key factors or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. that can operably couple with
One or more techniques and systems are described herein for to improve loading of grain hauling containers to target load weight, to help evenly distribute loads in a container, and to make it easier for operators to achieve optimal fills on carts and container. Further, the techniques and systems described herein can help operations that want to improve efficiency, while reducing field compaction and other issues related to weather or environmental conditions. Loading operations (e.g., offloading to a target container) rates can be monitored and automatic alerts and/or shut-offs can be provided based on pre-determined threshold levels. Real-time data from the vehicles (e.g., combine, cart, trailer container) can be monitored, including scale weights, flow rates, speed of equipment, and more, to determine when the desired threshold is met. The pre-determined threshold can be adjusted to accommodate target circumstances, and can be automatically adjusted based on the target container into which the product is being loaded.
In one implementation of a method for automatically filling a target container to a desired weight during collection of an agricultural product, a second predetermined level of product can be identified for a target truck-trailer container for hauling the product offsite. Further in this implementation, an optimized fill method for transferring the product from a field from which the product is collected to the target truck-trailer container can be determined using a mobile transport container. Additionally, a sensor array, which detects an amount of the product disposed in the mobile transport container during transfer, can be used to fill the mobile transport container to a first predetermined level based at least on the optimized fill method. In this implementation, the mobile transport container used to fill the target truck-trailer container to the second predetermined level of product for a target truck-trailer container.
To the accomplishment of the foregoing and related ends, the following description and annexed drawings set forth certain illustrative aspects and implementations. These are indicative of but a few of the various ways in which one or more aspects may be employed. Other aspects, advantages and novel features of the disclosure will become apparent from the following detailed description when considered in conjunction with the annexed drawings.
The claimed subject matter is now described with reference to the drawings, wherein like reference numerals are generally used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the claimed subject matter. It may be evident, however, that the claimed subject matter may be practiced without these specific details. In other instances, structures and devices are shown in block diagram form in order to facilitate describing the claimed subject matter.
As described herein, a system can be devised that provides for an automatic fill to a target weight of harvested product transferred in-field during a harvesting operation. In one aspect, the system can be used to support automatic retrieval of scale data (e.g., weight) to support target fill weights for target vehicle (e.g., harvesters, field carts, trailer containers, storage facilities, etc.). The example systems can provide information to support in-field decisions by Tractor/Cart operators and Truck/Trailer operators, such as when and how much to fill to meet a pre-determined threshold, to provide for improved scheduling and logistics, etc. Further, the information gathered can be automatically used for after the fact accountability of amount of product. As an example, this may reduce or eliminate manual entry of load weight information, and mitigate overfills, under-fills, and loss of efficiency. That is, in this aspect, truck/trailer container can achieve their target load weight more easily for efficient grain transport. In-field grain carts can be optimally filled to achieve effective and efficient grain transport, and grain load thresholds can be met, such as to mitigate soil compaction or reduce field conditions issues with the transport vehicles.
In some implementations, in this aspect, the system can monitor unloading rates to both the truck container from the grain cart, and to the grain cart from the harvester; or from a storage vehicle to a transport cart, to the target dispersion vehicle (e.g., seeder, chemical sprayer). As an example, an alert can be provided to the operator, and/or the system can automatically shut off the offloading mechanism when targeted or threshold weight is met (e.g., or cart is full, whichever comes first). For example, real-time data from a target vehicle can be used for a scale sensor, which can control the offloading equipment, such as to turn off the loader when a desired target weight is reached. In some implementations, the control of the offloading equipment could be achieved by controlling the loading rate over time, or the state of the unloading mechanism directly (e.g., on/off). As an illustrative example, a single grain cart can service multiple harvesters operating in the field, and could fill to the same weight each time, regardless of which combine is unloading into the cart. In this example, the target weight may be one specified for that particular cart, for the particular soil conditions, and/or to meet a specific load weight and target load efficiency for a waiting trailer container.
In some implementations, in this aspect, scale weight on a target vehicle (e.g., grain cart, trailer container) can be used to calibrate flow rates coming from the offloading vehicle (e.g., harvester, grain cart). As an example, using the harvester's on-board machine sensors and known state, the harvester auger (e.g., or belt) flow rate can be accurately predicted. For example, data collected from the harvester that may be used to determine the predicted flow rate can include, the on-board tank fill level, harvester mass flow rate into tank, machine attitude (e.g., pitch and roll), engine load, auger power, speed and torque, etc. Further, in this example, the tractor and grain cart sensors may be used to accurately predict flow rate coming into or out of the grain cart. For example, the cart scale weight, machine attitude, PTO speed, torque, engine load, etc., may be used to identify flow rate. In this implementation, the predicted flow rate(s) can be compared with the known scale weight to help calibrate the flow rate for more accurate predictions.
In some aspects the fill to weight system may comprise a plurality of modes. In one implementation, a grain cart monitoring mode may be utilized that comprises several options. In this implementation, for example, an optimized fill level weight for a particular grain cart can be identified. In this example the optimized fill level weight can comprise an integer that is a division of a target truck/trailer's container weight. That is, X number of cart loads can be used to fill the target truck/trailer's container to its target weight, where Xis a whole number. In this way, specific carts, with their optimized fill weights, can be automatically associated with target trailers to optimize the loading process. That is, for example, the cart unloads into target truck/trailer, which is coordinated for unload amongst various grain cart operators.
Additionally, as an example in this implementation, individual grain cart loads can be filled to their so called max load, at least until enough grain carts have unloaded or queued to unload into the target truck container to reach target weight. In this example, the last grain cart can have a target fill weight that allows it to meet the target quantity remaining for the trailer container, which may be a partial load for the cart.
In another implementation, a truck/trailer container weight monitoring mode can be utilized. In this implementation, for example, when monitoring truck container weight as each grain cart unloads, the system will, in real time, monitor the aggregate weight of the truck container and alert grain cart operator(s) when full or at least near target weight, or the information can be used to automatically shut off unloading auger into the truck-trailer container.
As another example, a target dispersion vehicle (e.g., or fleet of vehicles), such as a seeder that is planting grains, or a chemical depositing vehicle (e.g., sprayer, fertilizer, etc.) may need to be refilled during operation (e.g., using level sensors). In this example, similar data can be used to identify when the dispersion vehicle has reached a target level of product being dispersed (e.g., low level). An alert can be provided that activates deployment of a mobile transport to move to a product storage (e.g., truck-trailer with product, or storage container) for loading of the product from the product storage to the mobile transport. In this example, the fill-to-weight process can be used to transfer an appropriate amount of product from the storage container to the target dispersion vehicle.
As an illustrative example,
During the course of a harvesting operation, the on-board storage container 102 is filled with the agricultural product 150 harvested from the field. In order to allow for continued harvesting, when the amount of agricultural product 150 in the on-board storage container 102 reaches a pre-selected level, the agricultural product 150 can be offloaded. As illustrated in
In some implementations, as illustrated in
As an example, much like with the harvester 100 offloading to the cart 200, the cart 200 can offload to the truck-trailer container 300. That is, in this example, the cart comprises a cart product dispenser 204 (e.g., an auger device, a conveyor device, or the like), which is configured to offload product 150 from the cart storage container 202 through a cart dispenser outlet. As such, for a product transfer, the cart 200 can be pulled up alongside the truck-trailer container 300, such that the outlet of the cart product dispenser 204 is aligned with the trailer storage container 302. In this way, the agricultural product 150 can be transferred from the cart storage container 202 to the trailer storage container 302.
As an example, as described above, the agricultural product in the mobile storage container (e.g., grain cart) is unloaded into truck-trailer containers for over-the-road transport (e.g., to a storage or processing facility). Truck-trailer containers and/or mobile storage container may have loading limits based on carrying capacity of the vehicle, road weight restrictions, field conditions, environmental conditions, etc. As such, the amount of agricultural product transferred to the mobile storage container and from the mobile storage container to the truck-trailer container can be limited based on these load limits, which can help determine the number of mobile storage container fills, and the amount filled in each one. In some implementations, the mobile storage container may be transported over a road. In these implementations, the weight of the agricultural product in the mobile storage container may be limited to that of the road weight restrictions, or filed conditions when transported over a field, or limits of the vehicle itself. Further, the site on which the collection and transfer of product may have soil conditions that merit reduction of weight, such as to mitigate soil compaction. In this example, the fill level, or first predetermined level can be determined based on soil conditions and amount of soil compaction reduction desired. Thus, an amount of agricultural material transferred from the harvester to the mobile storage container, the number of grain carts in operation, and the amount of material transferred from the mobile storage container to the truck-trailer container can be controlled in order, for example, to comply with these loading restrictions.
As an illustrative example, the unloading rates or fill rates to both truck container from grain cart and grain cart from combine can be monitored, and may be pre-set based on known weight limits, and other conditions, such as provided by the operator or automatically based on known data. In some implementations, an alert can be provided to an operator, or the transfer can automatically shut off when targeted weight is met or the cart is full, whichever comes first. Further, real-time data can be used from a vehicle with a scale sensor to control the unloading equipment in order to turn off the transfer when a desired target weight is reached. For example, this could be achieved by controlling the rate over time, or controlling the state of the unloading mechanism directly. For example, a single grain cart can service multiple combines and routinely fill to a weight regardless of which combine is unloading into the cart. Additionally, a scale weight on grain cart can be used to calibrate the flow rate coming out of a combine. In this example, combine machine sensors and its state can be used to accurately predict combine auger flow rate. This may include, but is not limited to, a combine tank fill level, combine mass flow rate into tank, machine attitude (pitch and roll), engine load, auger power, speed and torque, etc. For example, tractor and grain cart sensors can be used to accurately predict flow rate coming into or out of the grain cart. This may include, but is not limited to, a scale weight, a machine attitude, PTO speed, torque, engine load, etc.
In some implementations, an inventory of vehicles can be provided, that identifies respective limits and other specifications for each vehicle that is targeted for a particular operation. That is, for example, a farm operation may have a fleet of vehicle available for a target operation (e.g., harvesting, planting, fertilizing, etc.), including harvesters, planters, chemical carts, grain carts, and over-the-road vehicles, etc. In this example, each vehicle may have specifications and limits that may impact the target operation, such as carrying capacity, weight limits, vehicle speed, transfer rates, etc. Further, environmental and site conditions may also have an impact on the target operation, such as soil conditions, type of target product harvested/deposited, weather, etc. In this example, a database can include each vehicle along with their specifications, and/or another database can include the site conditions, target product, and weather predictions. In these implementations, the target operation can be managed and planned using the information provided by these databases. That is, for example, the target operation may have a preferred schedule (e.g., timing), and target size, rate, and other parameters. Using the information provided, the appropriate vehicles may be selected to meet the target parameters, and a target date/time can be selected based on the site conditions, etc. In this way, the efficiency of the target operation can be improved using the conditions and equipment provided.
At 504, in
At 506, The mobile transport container (e.g., grain cart) can be filled to the predetermined level. As an example, the mobile transport container can have a weight sensor (e.g., scale) and/or a volume/level sensor (e.g., optical sensor) that identifies when the weight/volume meets the predetermined level, based at least on the selected optimized fill method.
At 606, the first predetermined level (e.g., fill level or full load level) can be determined for the mobile transport container (e.g., grain cart). As an example, the first predetermined level can comprise a weight limit for the product in the container, and/or can be a volume limit for the product in the container. That is, for example, depending on the characteristics of the product, such as average weight per kernel (e.g., based on moisture level, etc.) and average size of the kernels, a volume limit for a container may comprise different weights. In this example, a container may have a certain weight limit, and/or the operator of the harvesting may have desired soil compaction limits that are directly affected by the weight of container transiting the harvesting site. In some cases, soil conditions may help determine a weight limit, such as in wet conditions, in certain types, and other conditions where it is desirable to mitigate soil compaction (e.g., where soil compaction can lead to poor plant growth, or damage to a site).
Additionally, in some implementations, as described above, determining an optimized fill method for transferring the product from a field comprises determining an efficient fill method, which may result in different predetermined fill levels. As such, in this implementation, a first predetermined level (e.g., container fill level) may be a full weight limit for the container and conditions (e.g., or volume limit), or may be a partially full weight limit or volume limit depending on the optimization method selected for filling a target truck trailer (over-the-road trailer).
At 608, a flow rate for the transfer of the product from the harvester to the mobile container, and/or from the container to the tractor trailer container, can be identified. That is, for example, one or more of the sensors can comprise a scale that identifies the weight of the product as it is transferred into the mobile container and/or the truck trailer. As the product is transferred over time period, the amount of time can be correlated to the weight to identify the flow rate. In some implementations, the identified flow rate con comprise an estimated flow rate, and/or an average flow rate selected from a plurality of flow rate samplings. As an example, flow rate may differ depending on the type of equipment used for the transfer (e.g., auger, conveyor, air flow, etc.), and/or the operation of the equipment (e.g., speed, rate, power, etc.). In some implementations, the determined flow rate can be calibrated accordingly, based on the conditions, type of product, type of equipment, etc., to get a more accurate flow rate. In this way, the flow rate can be used to determine when the transfer has reached the first predetermined fill level. That is, the flow rate (e.g., volume or weight transferred over time) can be used to determine the amount of product transferred.
At 610, the optimized loading method for the loading of the target truck trailer can be identified. As described above, depending on the type and amount of equipment used for a given harvesting site, an optimized method can be selected to provide a more efficient transfer of the product from the field to the truck trailer.
At 612, one or more mobile transport containers (e.g., grain carts) can be deployed into the field to a target harvester. As described above, typically the grain carts are deployed to a harvester when they need to offload their harvest (e.g., when they are approaching full). As an example, this can be timed according to an automated system that detects harvesting rates/levels and deploys the cart automatically, and/or by notifying an operator.
At 614, once the mobile container is aligned with the harvester's transfer system, transfer of the harvested product can commence. In some implementations, the transfer can continue at least until the first predetermined level of product in the mobile container is reached. That is, for example, as described above, the grain is transferred to the mobile cart until the cart is “full.” In some implementations, the earlier determined transfer rate can be used to identify when the grain in the cart has reached the first predetermined level, for example, by transferring at the known rate for a known period of time, to reach a known weight and/or volume. In other implementations, one or more sensors (e.g., weight or volume sensors) can be used to determine when the mobile container is “full.” In this implementation, once the first predetermined level is reached the transfer can be stopped.
At 614, the mobile transport container can be deployed from the harvester to the truck trailer. As an example, once the transfer is completed a system may provide a notice to an operator to move the container to the location of the truck trailer; or an automated system may automatically move the mobile container from the harvester to the truck trailer. In these implementations, the mobile container can move to a transfer location at the truck trailer, deploy a transfer device, and transfer the product from the mobile container into the truck trailer container, offloading the product at 618. Further, this deployment and offloading of product may be performed by an operator, and/or may be performed automatically by an automated system.
At 620, a product loading system (e.g., comprising a processor and memory with stored instructions that are processed for performing the tasks), and/or an operator, can determine whether the truck trailer container is full, and has reached a second predetermined level. As an example, as described above, the truck trailer is configured for transporting the product over the road (e.g., or similar) to a storage or processing facility. In this example, the truck trailer container can also have a load limit (e.g., weight and/or volume) that limits the amount of product contained therein (e.g., due to vehicle limits, road limits, environmental conditions, soil condition, etc.). As further described above, the optimized loading for the truck trailer can be predetermined, based on the conditions, and once that second predetermined level is reached, the trailer may be considered “full.” At 620, if the truck trailer is not full, the mobile transport container can be redeployed to a harvester to collect another load of the product (e.g., full or partial load depending on present fill level of the truck trailer).
Alternately, if the truck trailer is full, the exemplary method 600 can end at 622. As an example, the truck trailer can then be deployed to a processing or storage facility where the product can be offloaded from the truck trailer. Additionally, the amount of product disposed in the truck trailer container can be known, as the amount of product disposed in each mobile transport container is known (e.g., from the know flow rate).
In another implementation, in some situations the operator (e.g., or automated filling system) may have a desired target weight or volume for the target truck/trailer. As an example, target truck/trailer could be capable of carrying a 50,000 lb load, which may be its high limit. In this example, however, due to some outside conditions, such as road restrictions or environmental conditions, target storage/processing location conditions, etc., the operator (e.g., or system) may request a less than high limit weight, which would be the desired target weight. Similarly, in some implementations, the mobile transport container (e.g., grain cart) could also have a desired target load (e.g., less than “full limit”), and the operator (e.g., or automated system) may communicate this to the harvester, which would then shut off the unloading system (e.g., auger) once the desired setpoint has been reached. In these implementations, the communication of the target or desired weight or volume may be directed from machine to machine (e.g., local area network), from operator to machine, from operator to operator, and from machine to a remote (e.g., cloud) communications network to machine. It is anticipated that various wireless communication pathways could be utilized for this type of communication.
The computer 702 can serve in a role as a client, a network component, a server, a database, a persistency, or components of a computer system for performing the subject matter described in the present disclosure. The illustrated computer 702 is communicably coupled with a network 730. In some implementations, one or more components of the computer 702 can be configured to operate within different environments, including cloud-computing-based environments, local environments, global environments, and combinations of environments.
At a high level, the computer 702 is an electronic computing device operable to receive, transmit, process, store, and manage data and information associated with the described subject matter. According to some implementations, the computer 702 can also include, or be communicably coupled with, an application server, an email server, a web server, a caching server, a streaming data server, or a combination of servers.
The computer 702 can receive requests over network 730 from a client application (for example, executing on another computer 702). The computer 702 can respond to the received requests by processing the received requests using software applications. Requests can also be sent to the computer 702 from internal users (for example, from a command console), external (or third) parties, automated applications, entities, individuals, systems, and computers.
Each of the components of the computer 702 can communicate using a system bus 703. In some implementations, any or all of the components of the computer 702, including hardware or software components, can interface with each other or the interface 704 (or a combination of both), over the system bus 703. Interfaces can use an application programming interface (API) 712, a service layer 713, or a combination of the API 712 and service layer 713. The API 712 can include specifications for routines, data structures, and object classes. The API 712 can be either computer-language independent or dependent. The API 712 can refer to a complete interface, a single function, or a set of APIs.
The service layer 713 can provide software services to the computer 702 and other components (whether illustrated or not) that are communicably coupled to the computer 702. The functionality of the computer 702 can be accessible for all service consumers using this service layer. Software services, such as those provided by the service layer 713, can provide reusable, defined functionalities through a defined interface. For example, the interface can be software written in JAVA, C++, or a language providing data in extensible markup language (XML) format. While illustrated as an integrated component of the computer 702, in alternative implementations, the API 712 or the service layer 713 can be stand-alone components in relation to other components of the computer 702 and other components communicably coupled to the computer 702. Moreover, any or all parts of the API 712 or the service layer 713 can be implemented as child or sub-modules of another software module, enterprise application, or hardware module without departing from the scope of the present disclosure.
The computer 702 includes an interface 704. Although illustrated as a single interface 704 in
The computer 702 includes a processor 705. Although illustrated as a single processor 705 in
The computer 702 also includes a database 706 that can hold data for the computer 702 and other components connected to the network 730 (whether illustrated or not). For example, database 706 can be an in-memory, conventional, or a database storing data consistent with the present disclosure. In some implementations, database 706 can be a combination of two or more different database types (for example, hybrid in-memory and conventional databases) according to particular needs, desires, or particular implementations of the computer 702 and the described functionality. Although illustrated as a single database 706 in
The computer 702 also includes a memory 707 that can hold data for the computer 702 or a combination of components connected to the network 730 (whether illustrated or not). Memory 707 can store any data consistent with the present disclosure. In some implementations, memory 707 can be a combination of two or more different types of memory (for example, a combination of semiconductor and magnetic storage) according to particular needs, desires, or particular implementations of the computer 702 and the described functionality. Although illustrated as a single memory 707 in
The application 708 can be an algorithmic software engine providing functionality according to particular needs, desires, or particular implementations of the computer 702 and the described functionality. For example, application 708 can serve as one or more components, modules, or applications. Further, although illustrated as a single application 708, the application 708 can be implemented as multiple applications 708 on the computer 702. In addition, although illustrated as internal to the computer 702, in alternative implementations, the application 708 can be external to the computer 702.
The computer 702 can also include a power supply 714. The power supply 714 can include a rechargeable or non-rechargeable battery that can be configured to be either user- or non-user-replaceable. In some implementations, the power supply 714 can include power-conversion and management circuits, including recharging, standby, and power management functionalities. In some implementations, the power-supply 714 can include a power plug to allow the computer 702 to be plugged into a wall socket or a power source to, for example, power the computer 702 or recharge a rechargeable battery.
There can be any number of computers 702 associated with, or external to, a computer system containing computer 702, with each computer 702 communicating over network 730. Further, the terms “client,” “user,” and other appropriate terminology can be used interchangeably, as appropriate, without departing from the scope of the present disclosure. Moreover, the present disclosure contemplates that many users can use one computer 702 and one user can use multiple computers 702.
Described implementations of the subject matter can include one or more features, alone or in combination.
Additionally, in some implementations, the data can be collected at regular intervals (e.g., or continually) and curated into a remote operations center, and loaded to a database with spatial and temporal indexing capabilities. As one example, the data may be analyzed as it is collected for unload begin and end signals, and then, in combination with the location and time information, and the data records, determine which product transport container (e.g., grain cart or trailer) was positioned at a location at that time given known equipment dimensions and characteristics. In this example, once a match is identified, a “Virtual Load” record may be created or extended for the equipment receiving the load that contains pre-determined load metrics and characteristics, such as weight, volume, load time, condition of the product, and much more. As an example, this collection and curation of the data can be done automatically based on the load signals, location, and time match without need for operator intervention. Further, if the target transport container, such as a cart, already contains one or more portions of another load at the time of collection, the load quality information for all of the contained, partially filled loads can be aggregated together as appropriate for the circumstances.
The word “exemplary” is used herein to mean serving as an example, instance or illustration. Any aspect or design described herein as “exemplary” is not necessarily to be construed as advantageous over other aspects or designs. Rather, use of the word exemplary is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. Further, at least one of A and B and/or the like generally means A or B or both A and B. In addition, the articles “a” and “an” as used in this application and the appended claims may generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Also, although the disclosure has been shown and described with respect to one or more implementations, equivalent alterations and modifications will occur to others skilled in the art based upon a reading and understanding of this specification and the annexed drawings. The disclosure includes all such modifications and alterations and is limited only by the scope of the following claims. In particular regard to the various functions performed by the above described components (e.g., elements, resources, etc.), the terms used to describe such components are intended to correspond, unless otherwise indicated, to any component which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations of the disclosure. In addition, while a particular feature of the disclosure may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application. Furthermore, to the extent that the terms “includes,” “having,” “has,” “with,” or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising.”
The implementations have been described, hereinabove. It will be apparent to those skilled in the art that the above methods and apparatuses may incorporate changes and modifications without departing from the general scope of this invention. It is intended to include all such modifications and alterations in so far as they come within the scope of the appended claims or the equivalents thereof.
