Unnamed: 0
int64 0
350k
| ApplicationNumber
int64 9.75M
96.1M
| ArtUnit
int64 1.6k
3.99k
| Abstract
stringlengths 7
8.37k
| Claims
stringlengths 3
292k
| abstract-claims
stringlengths 68
293k
| TechCenter
int64 1.6k
3.9k
|
|---|---|---|---|---|---|---|
347,200 | 16,805,691 | 3,726 | A maintenance interval adjuster and methods for improving accuracy of maintenance scheduling and changing a maintenance interval are presented. Scheduled maintenance data and unscheduled in-service maintenance data for a maintenance task are retrieved for a plurality of platforms. A distribution of lifetimes for the maintenance task in the scheduled maintenance data and unscheduled in-service maintenance data are analyzed for high variance or multiple modes. A number of conditions in sensor data of the plurality of platforms correlated to a length of the lifetimes for the maintenance task is identified, in response to identifying at least one of high variance or multiple modes in the distribution of lifetimes. The lifetimes are divided into a plurality of groups based on the number of conditions. A respective recommended maintenance interval is determined for each group of the plurality of groups based on respective lifetimes for the maintenance task of a respective group. | 1. A computer-implemented method comprising:
determining if sensor data of a platform indicates a condition affecting a frequency of a maintenance task; changing a maintenance interval for performing the maintenance task for the platform to an updated value if a condition affecting the frequency of the maintenance task is indicated in the sensor data; and performing the maintenance task at or before the maintenance interval having the updated value. 2. The method of claim 1, wherein changing the maintenance interval to the updated value decreases the maintenance interval. 3. The method of claim 1, wherein changing the maintenance interval to the updated value increases the maintenance interval. 4. The method of claim 1 further comprising:
resetting a time point counter and the maintenance interval for performing the maintenance task to default values after performing the maintenance task. 5. The method of claim 1 further comprising:
determining if the sensor data meets a time point, wherein determining if sensor data of the platform indicates a condition affecting a frequency of the maintenance task is performed in response to determining the sensor data does meet the time point. 6. The method of claim 5, wherein the time point is one of a quantity of usage cycles, an amount of usage time, or a quantity of calendar days. 7. The method of claim 1 further comprising:
determining if second sensor data of the platform indicates a second condition affecting a frequency of a second maintenance task;
changing a second maintenance interval for performing the second maintenance task for the platform to a second updated value if a second condition affecting the frequency of the second maintenance task is indicated in the second sensor data; and
performing the second maintenance task at or before the second maintenance interval having the second updated value. 8. The method of claim 7 further comprising:
determining if the second sensor data meets a second time point, wherein determining if the second sensor data of the platform indicates the second condition affecting a frequency of the second maintenance task is performed in response to determining the second sensor data does meet the second time point. 9. The method of claim 1, wherein the platform is an aircraft and the sensor data is flight sensor data. 10. A computer-implemented method of improving accuracy of maintenance scheduling, the method comprising:
retrieving scheduled maintenance data and unscheduled in-service maintenance data for a maintenance task for a plurality of platforms; analyzing a distribution of lifetimes for the maintenance task in the scheduled maintenance data and unscheduled in-service maintenance data for high variance or multiple modes; identifying, in response to identifying at least one of high variance or multiple modes in the distribution of lifetimes, a number of conditions in sensor data of the plurality of platforms correlated to a length of the lifetimes for the maintenance task; dividing the lifetimes into a plurality of groups based on the number of conditions; and determining a respective recommended maintenance interval for each group of the plurality of groups based on respective lifetimes for the maintenance task of a respective group. 11. The method of claim 10 further comprising:
retrieving the sensor data of the plurality of platforms. 12. The method of claim 10 further comprising:
calculating a time point after which an acceptable amount of sensor data is available for a platform such that an analysis can be performed to determine if the number of conditions is present for the platform. 13. The method of claim 12, wherein the time point is a minimum quantity of cycles. 14. The method of claim 10, wherein each of the respective recommended maintenance intervals is an interval of time between performances of the maintenance task that maximizes a probability that anomalies associated with a set of components are detected during preventive scheduled maintenance. 15. An apparatus comprising:
a bus system; a communications system coupled to the bus system; and a processor unit coupled to the bus system, wherein the processor unit executes computer-usable program code to retrieve scheduled maintenance data and unscheduled in-service maintenance data for a maintenance task for a plurality of platforms; analyze a distribution of lifetimes for the maintenance task in the scheduled maintenance data and unscheduled in-service maintenance data for high variance or multiple modes; identify, in response to identifying at least one of high variance or multiple modes in the distribution of lifetimes, a number of conditions in sensor data of the plurality of platforms correlated to a length of the lifetimes for the maintenance task; divide the lifetimes into a plurality of groups based on the number of conditions; and determine a respective recommended maintenance interval for each group of the plurality of groups by performing an customized maintenance program analysis on each of the plurality of groups. 16. The apparatus of claim 15, wherein the processor unit also sends analysis results of performing the customized maintenance program analysis on the plurality of groups to regulatory authorities for approval. 17. The apparatus of claim 15, wherein the communications system receives the sensor data of the plurality of platforms. 18. The apparatus of claim 15, wherein the processor unit also calculates a time point after which an acceptable amount of sensor data is available for a platform such that an analysis can be performed to determine if the number of conditions is present for the platform. 19. The apparatus of claim 18, wherein the time point is a minimum quantity of cycles. 20. The apparatus of claim 15, wherein each of the respective recommended maintenance intervals is an interval of time between performances of the maintenance task that maximizes a probability that anomalies associated with a set of components are detected on a respective platform during preventive scheduled maintenance. | A maintenance interval adjuster and methods for improving accuracy of maintenance scheduling and changing a maintenance interval are presented. Scheduled maintenance data and unscheduled in-service maintenance data for a maintenance task are retrieved for a plurality of platforms. A distribution of lifetimes for the maintenance task in the scheduled maintenance data and unscheduled in-service maintenance data are analyzed for high variance or multiple modes. A number of conditions in sensor data of the plurality of platforms correlated to a length of the lifetimes for the maintenance task is identified, in response to identifying at least one of high variance or multiple modes in the distribution of lifetimes. The lifetimes are divided into a plurality of groups based on the number of conditions. A respective recommended maintenance interval is determined for each group of the plurality of groups based on respective lifetimes for the maintenance task of a respective group.1. A computer-implemented method comprising:
determining if sensor data of a platform indicates a condition affecting a frequency of a maintenance task; changing a maintenance interval for performing the maintenance task for the platform to an updated value if a condition affecting the frequency of the maintenance task is indicated in the sensor data; and performing the maintenance task at or before the maintenance interval having the updated value. 2. The method of claim 1, wherein changing the maintenance interval to the updated value decreases the maintenance interval. 3. The method of claim 1, wherein changing the maintenance interval to the updated value increases the maintenance interval. 4. The method of claim 1 further comprising:
resetting a time point counter and the maintenance interval for performing the maintenance task to default values after performing the maintenance task. 5. The method of claim 1 further comprising:
determining if the sensor data meets a time point, wherein determining if sensor data of the platform indicates a condition affecting a frequency of the maintenance task is performed in response to determining the sensor data does meet the time point. 6. The method of claim 5, wherein the time point is one of a quantity of usage cycles, an amount of usage time, or a quantity of calendar days. 7. The method of claim 1 further comprising:
determining if second sensor data of the platform indicates a second condition affecting a frequency of a second maintenance task;
changing a second maintenance interval for performing the second maintenance task for the platform to a second updated value if a second condition affecting the frequency of the second maintenance task is indicated in the second sensor data; and
performing the second maintenance task at or before the second maintenance interval having the second updated value. 8. The method of claim 7 further comprising:
determining if the second sensor data meets a second time point, wherein determining if the second sensor data of the platform indicates the second condition affecting a frequency of the second maintenance task is performed in response to determining the second sensor data does meet the second time point. 9. The method of claim 1, wherein the platform is an aircraft and the sensor data is flight sensor data. 10. A computer-implemented method of improving accuracy of maintenance scheduling, the method comprising:
retrieving scheduled maintenance data and unscheduled in-service maintenance data for a maintenance task for a plurality of platforms; analyzing a distribution of lifetimes for the maintenance task in the scheduled maintenance data and unscheduled in-service maintenance data for high variance or multiple modes; identifying, in response to identifying at least one of high variance or multiple modes in the distribution of lifetimes, a number of conditions in sensor data of the plurality of platforms correlated to a length of the lifetimes for the maintenance task; dividing the lifetimes into a plurality of groups based on the number of conditions; and determining a respective recommended maintenance interval for each group of the plurality of groups based on respective lifetimes for the maintenance task of a respective group. 11. The method of claim 10 further comprising:
retrieving the sensor data of the plurality of platforms. 12. The method of claim 10 further comprising:
calculating a time point after which an acceptable amount of sensor data is available for a platform such that an analysis can be performed to determine if the number of conditions is present for the platform. 13. The method of claim 12, wherein the time point is a minimum quantity of cycles. 14. The method of claim 10, wherein each of the respective recommended maintenance intervals is an interval of time between performances of the maintenance task that maximizes a probability that anomalies associated with a set of components are detected during preventive scheduled maintenance. 15. An apparatus comprising:
a bus system; a communications system coupled to the bus system; and a processor unit coupled to the bus system, wherein the processor unit executes computer-usable program code to retrieve scheduled maintenance data and unscheduled in-service maintenance data for a maintenance task for a plurality of platforms; analyze a distribution of lifetimes for the maintenance task in the scheduled maintenance data and unscheduled in-service maintenance data for high variance or multiple modes; identify, in response to identifying at least one of high variance or multiple modes in the distribution of lifetimes, a number of conditions in sensor data of the plurality of platforms correlated to a length of the lifetimes for the maintenance task; divide the lifetimes into a plurality of groups based on the number of conditions; and determine a respective recommended maintenance interval for each group of the plurality of groups by performing an customized maintenance program analysis on each of the plurality of groups. 16. The apparatus of claim 15, wherein the processor unit also sends analysis results of performing the customized maintenance program analysis on the plurality of groups to regulatory authorities for approval. 17. The apparatus of claim 15, wherein the communications system receives the sensor data of the plurality of platforms. 18. The apparatus of claim 15, wherein the processor unit also calculates a time point after which an acceptable amount of sensor data is available for a platform such that an analysis can be performed to determine if the number of conditions is present for the platform. 19. The apparatus of claim 18, wherein the time point is a minimum quantity of cycles. 20. The apparatus of claim 15, wherein each of the respective recommended maintenance intervals is an interval of time between performances of the maintenance task that maximizes a probability that anomalies associated with a set of components are detected on a respective platform during preventive scheduled maintenance. | 3,700 |
347,201 | 16,873,234 | 3,786 | A wrist support board has a board with a ventral surface and an opposite dorsal surface, a smooth curve lengthwise, a proximal end to the board and an opposite distal end, a proximal strap, a distal strap, and a center strap. The proximal strap and the distal strap extend from the ventral surface and wrap a patient's arm placed upon the dorsal surface. The center strap extends through slots in the board proximate the vertex of the curve. The center strap enwraps a patient's arm slightly proximal from the patient's wrist. The proximal strap, the distal strap, and the center strap are perpendicular to the board. The three straps secure near their own centers to the board and present two free ends that wrap around a patient's arm. The wrist support board assists in the immobilizing, stabilizing, and hyper-exposure of the trans-radial artery of a patient. | 1. A medical device comprising:
a board having an elongated, curved shape, a distal end, and an opposite proximal end, said board having a length from said distal end to said proximal end; a distal strap joining to said distal end, said distal strap extending perpendicular to the length of said board; a proximal strap opposite said distal strap, said proximal strap joining to said proximal end, said proximal strap extending perpendicular to the length of said board and generally parallel to said distal strap; a center strap connecting to said board between said distal strap and said proximal strap; and, a buckle upon said center strap wherein said buckle constricts said center strap during usage; wherein said medical device secures an arm of a patient placed therein for dorsal access and for ventral access. 2. The medical device of claim 1 further comprising:
said board having a right edge and an opposite left edge, said right edge and said left edge having a mutually parallel and spaced apart orientation, said right edge and said left edge each having a greater length than said distal end. 3. The medical device of claim 1 further comprising:
said buckle having a ventral surface and an opposite dorsal surface, the ventral surface of said buckle is adapted to contact a patient's arm, and a knob upon said dorsal surface engaging said center strap when inserted beneath said knob; and,
wherein rotation of said knob clockwise constricts said center strap beneath said knob and wherein rotation of said knob counterclockwise releases said center strap. 4. The medical device of claim 2 further comprising:
two slots, each slot locating inwardly from said left edge and said right edge. 5. The medical device of claim 4 further comprising:
said slots having an elongated shape mutually parallel and parallel to said left edge and said right edge respectively. 6. The medical device of claim 2 further comprising:
said curve of said board extending along the length of said board, said curve of said board adapted to fit a wrist of a patient. 7. The medical device of claim 6 further comprising:
said curve of said board having a greater portion between said slots and said distal end and lesser portion between said slots and said proximal end. 8. The medical device of claim 2 further comprising:
said board having a ventral surface and an opposite dorsal surface; and,
a linking member upon said board joining to said ventral surface. 9. The medical device of claim 8 further comprising:
said linking member is ferromagnetic. 10. A medical device comprising:
a board having an elongated, curved shape, a distal end, and an opposite proximal end, said board having a length from said distal end to said proximal end; a distal strap joining to said distal end, said distal strap extending perpendicular to the length of said board; a proximal strap opposite said distal strap, said proximal strap joining to said proximal end, said proximal strap extending perpendicular to the length of said board and generally parallel to said distal strap; a center strap connecting to said board between said distal strap and said proximal strap; a buckle upon said center strap wherein said buckle constricts said center strap during usage, said buckle having a ventral surface and an opposite dorsal surface, the ventral surface of said buckle is adapted to contact a patient's arm, and a knob upon said dorsal surface engaging said center strap when inserted beneath said knob, and rotating said knob clockwise constricting said center strap beneath said knob and rotating said knob counterclockwise releasing said center strap; wherein said medical device secures an arm of a patient placed therein for dorsal access and for ventral access. 11. The medical device of claim 10 further comprising:
said board having a right edge and an opposite left edge, said right edge and said left edge having a mutually parallel and spaced apart orientation, said right edge and said left edge each having a greater length than said distal end;
two slots, each slot locating inwardly from said left edge and said right edge, each of said slots having an elongated rectangular shape and being mutually parallel and parallel to said left edge and said right edge respectively. 12. The medical device of claim 10 further comprising:
said curve of said board extending along the length of said board, said curve of said board adapted to fit a wrist of a patient; and,
said curve of said board having a greater portion between said slots and said distal end and lesser portion between said slots and said proximal end. 13. The medical device of claim 12 further comprising:
said board having a width and said curve of said board extending upwardly from said distal end and said proximal end a chordal height proximate the adjoining of said greater portion and said lesser portion, said chordal height being at least seventy-five percent of the width of said board. 14. The medical device of claim 13 further comprising:
said board being concave across its width for its length; and,
said board having a ventral surface and an opposite dorsal surface. 15. The medical device of claim 14 further comprising:
a linking member upon said board joining to said ventral surface. 16. The medical device of claim 15 further comprising:
said linking member having a planar form;
said linking member being one of ferromagnetic, polymer, metal, alloy, and composite. 17. A medical device comprising:
a center strap; a buckle upon said center strap wherein said buckle constricts said center strap during usage, said buckle having a ventral surface and an opposite dorsal surface, the ventral surface of said buckle is adapted to contact a patient's arm, and a knob upon said dorsal surface engaging said center strap when inserted beneath said knob, and rotating said knob clockwise constricting said center strap beneath said knob and rotating said knob counterclockwise releasing said center strap; a distal strap and a spaced apart proximal strap, said center strap locating between said distal strap and said proximal strap a board having an elongated, curved shape, a distal end, and an opposite proximal end, said board having a length from said distal end to said proximal end, said distal strap joining to said distal end, said distal strap extending perpendicular to the length of said board, said proximal strap joining to said proximal end, said proximal strap extending perpendicular to the length of said board and generally parallel to said distal strap; said board having a right edge and an opposite left edge, said right edge and said left edge having a mutually parallel and spaced apart orientation, said right edge and said left edge each having a greater length than said distal end, said board having a width and said curve of said board extending upwardly from said distal end and said proximal end a chordal height proximate the adjoining of said greater portion and said lesser portion, said chordal height being at least seventy five percent of the width of said board; two slots, each slot locating inwardly from said left edge and said right edge, each of said slots having an elongated rectangular shape and being mutually parallel and parallel to said left edge and said right edge respectively; said a center strap connecting to said board through said slots and connecting to said board between said distal strap and said proximal strap; said curve of said board extending along the length of said board, said curve of said board adapted to fit a wrist of a patient; said curve of said board having a greater portion between said slots and said distal end and lesser portion between said slots and said proximal end; wherein said medical device secures an arm of a patient placed therein for dorsal access and for ventral access. 18. The medical device of claim 17 further comprising:
said board being concave across its width for its length; and,
said board having a ventral surface and an opposite dorsal surface. | A wrist support board has a board with a ventral surface and an opposite dorsal surface, a smooth curve lengthwise, a proximal end to the board and an opposite distal end, a proximal strap, a distal strap, and a center strap. The proximal strap and the distal strap extend from the ventral surface and wrap a patient's arm placed upon the dorsal surface. The center strap extends through slots in the board proximate the vertex of the curve. The center strap enwraps a patient's arm slightly proximal from the patient's wrist. The proximal strap, the distal strap, and the center strap are perpendicular to the board. The three straps secure near their own centers to the board and present two free ends that wrap around a patient's arm. The wrist support board assists in the immobilizing, stabilizing, and hyper-exposure of the trans-radial artery of a patient.1. A medical device comprising:
a board having an elongated, curved shape, a distal end, and an opposite proximal end, said board having a length from said distal end to said proximal end; a distal strap joining to said distal end, said distal strap extending perpendicular to the length of said board; a proximal strap opposite said distal strap, said proximal strap joining to said proximal end, said proximal strap extending perpendicular to the length of said board and generally parallel to said distal strap; a center strap connecting to said board between said distal strap and said proximal strap; and, a buckle upon said center strap wherein said buckle constricts said center strap during usage; wherein said medical device secures an arm of a patient placed therein for dorsal access and for ventral access. 2. The medical device of claim 1 further comprising:
said board having a right edge and an opposite left edge, said right edge and said left edge having a mutually parallel and spaced apart orientation, said right edge and said left edge each having a greater length than said distal end. 3. The medical device of claim 1 further comprising:
said buckle having a ventral surface and an opposite dorsal surface, the ventral surface of said buckle is adapted to contact a patient's arm, and a knob upon said dorsal surface engaging said center strap when inserted beneath said knob; and,
wherein rotation of said knob clockwise constricts said center strap beneath said knob and wherein rotation of said knob counterclockwise releases said center strap. 4. The medical device of claim 2 further comprising:
two slots, each slot locating inwardly from said left edge and said right edge. 5. The medical device of claim 4 further comprising:
said slots having an elongated shape mutually parallel and parallel to said left edge and said right edge respectively. 6. The medical device of claim 2 further comprising:
said curve of said board extending along the length of said board, said curve of said board adapted to fit a wrist of a patient. 7. The medical device of claim 6 further comprising:
said curve of said board having a greater portion between said slots and said distal end and lesser portion between said slots and said proximal end. 8. The medical device of claim 2 further comprising:
said board having a ventral surface and an opposite dorsal surface; and,
a linking member upon said board joining to said ventral surface. 9. The medical device of claim 8 further comprising:
said linking member is ferromagnetic. 10. A medical device comprising:
a board having an elongated, curved shape, a distal end, and an opposite proximal end, said board having a length from said distal end to said proximal end; a distal strap joining to said distal end, said distal strap extending perpendicular to the length of said board; a proximal strap opposite said distal strap, said proximal strap joining to said proximal end, said proximal strap extending perpendicular to the length of said board and generally parallel to said distal strap; a center strap connecting to said board between said distal strap and said proximal strap; a buckle upon said center strap wherein said buckle constricts said center strap during usage, said buckle having a ventral surface and an opposite dorsal surface, the ventral surface of said buckle is adapted to contact a patient's arm, and a knob upon said dorsal surface engaging said center strap when inserted beneath said knob, and rotating said knob clockwise constricting said center strap beneath said knob and rotating said knob counterclockwise releasing said center strap; wherein said medical device secures an arm of a patient placed therein for dorsal access and for ventral access. 11. The medical device of claim 10 further comprising:
said board having a right edge and an opposite left edge, said right edge and said left edge having a mutually parallel and spaced apart orientation, said right edge and said left edge each having a greater length than said distal end;
two slots, each slot locating inwardly from said left edge and said right edge, each of said slots having an elongated rectangular shape and being mutually parallel and parallel to said left edge and said right edge respectively. 12. The medical device of claim 10 further comprising:
said curve of said board extending along the length of said board, said curve of said board adapted to fit a wrist of a patient; and,
said curve of said board having a greater portion between said slots and said distal end and lesser portion between said slots and said proximal end. 13. The medical device of claim 12 further comprising:
said board having a width and said curve of said board extending upwardly from said distal end and said proximal end a chordal height proximate the adjoining of said greater portion and said lesser portion, said chordal height being at least seventy-five percent of the width of said board. 14. The medical device of claim 13 further comprising:
said board being concave across its width for its length; and,
said board having a ventral surface and an opposite dorsal surface. 15. The medical device of claim 14 further comprising:
a linking member upon said board joining to said ventral surface. 16. The medical device of claim 15 further comprising:
said linking member having a planar form;
said linking member being one of ferromagnetic, polymer, metal, alloy, and composite. 17. A medical device comprising:
a center strap; a buckle upon said center strap wherein said buckle constricts said center strap during usage, said buckle having a ventral surface and an opposite dorsal surface, the ventral surface of said buckle is adapted to contact a patient's arm, and a knob upon said dorsal surface engaging said center strap when inserted beneath said knob, and rotating said knob clockwise constricting said center strap beneath said knob and rotating said knob counterclockwise releasing said center strap; a distal strap and a spaced apart proximal strap, said center strap locating between said distal strap and said proximal strap a board having an elongated, curved shape, a distal end, and an opposite proximal end, said board having a length from said distal end to said proximal end, said distal strap joining to said distal end, said distal strap extending perpendicular to the length of said board, said proximal strap joining to said proximal end, said proximal strap extending perpendicular to the length of said board and generally parallel to said distal strap; said board having a right edge and an opposite left edge, said right edge and said left edge having a mutually parallel and spaced apart orientation, said right edge and said left edge each having a greater length than said distal end, said board having a width and said curve of said board extending upwardly from said distal end and said proximal end a chordal height proximate the adjoining of said greater portion and said lesser portion, said chordal height being at least seventy five percent of the width of said board; two slots, each slot locating inwardly from said left edge and said right edge, each of said slots having an elongated rectangular shape and being mutually parallel and parallel to said left edge and said right edge respectively; said a center strap connecting to said board through said slots and connecting to said board between said distal strap and said proximal strap; said curve of said board extending along the length of said board, said curve of said board adapted to fit a wrist of a patient; said curve of said board having a greater portion between said slots and said distal end and lesser portion between said slots and said proximal end; wherein said medical device secures an arm of a patient placed therein for dorsal access and for ventral access. 18. The medical device of claim 17 further comprising:
said board being concave across its width for its length; and,
said board having a ventral surface and an opposite dorsal surface. | 3,700 |
347,202 | 16,805,695 | 3,732 | A shiftable backing feed is utilized with a tufting machine having reciprocating needles and gauge parts for seizing yarns at a plurality of fixed heights, wherein fabric support apparatus reciprocates in synchronization with the cycles of the needle bar to support the backing during penetration of the backing fabric yet allow backing shifts between stitches. | 1. Using a tufting machine for forming tufted fabrics, comprising:
at least one shiftable needle bar having a series of needles mounted transversely across the width of the tufting machine; backing feed rolls for feeding a backing material through a tufting zone of the tufting machine; a yarn feed mechanism for feeding a series of yarns to said needles; at least one backing shifter for shifting said a plurality of backing feed rolls transversely across the tufting zone; a fabric support beneath the backing fabric equipped for reciprocal movement; a series of gauge parts mounted below the tufting zone in a position to engage needles of said at least one needle bar as the needles are reciprocated into the backing material to form tufts of yarns in the backing material; the gauge parts being arranged in a sequence of relatively taller and relatively lower yarn seizing elements and the at least one needlebar being shiftable to align needles with said relatively taller or relatively lower yarn seizing elements; and a control system for controlling and synchronizing the backing shifter, needle drive, backing feed, and fabric support reciprocation. 2. A tufting machine for forming tufted fabrics, comprising:
at least one shiftable needle bar having a series of needles mounted transversely across the width of the tufting machine; backing feed rolls for feeding a backing material through a tufting zone of the tufting machine; a yarn feed mechanism for feeding a series of yarns to said needles; at least one backing shifter for shifting said a plurality of backing feed rolls transversely across the tufting zone; a fabric support beneath the backing fabric equipped for reciprocal movement; a series of gauge parts having a plurality of fixed heights mounted below the tufting zone in a position to engage yarns carried by needles of said at least one needle bar as the needles are reciprocated into the backing material to form tufts of yarns in the backing material; the plurality of fixed heights including a relatively greater height so that yarns are seized relatively closer to the backing fabric, and a relatively lower height so that yarns are seized relatively further away from the backing fabric; the needle bar being shiftable to engage yarns carried by the transversely mounted needles with either the greater or lower height gauge parts; and a control system for controlling and synchronizing the backing shifter, needle drive, backing feed, and fabric support reciprocation. 3. A tufting machine for forming tufted fabrics, comprising:
first and second series of needles mounted transversely across the width of the tufting machine; backing feed rolls for feeding a backing material through a tufting zone of the tufting machine; a yarn feed mechanism for feeding a series of yarns to said needles; at least one backing shifter for shifting said a plurality of backing feed rolls transversely across the tufting zone; a fabric support beneath the backing fabric equipped for reciprocal movement; a first series of gauge parts having a first fixed height mounted below the tufting zone in a position to engage yarns carried by needles of the first series as the needles are reciprocated into the backing material to form tufts of yarns in the backing material; a second series of gauge parts having a second fixed height mounted below the tufting zone in a position to engage yarns carried by needles of the second series as the needles are reciprocated into the backing material to form tufts of yarns in the backing material; a control system for controlling and synchronizing the backing shifter, needle drive, backing feed, and fabric support reciprocation. 4. The tufting machine of claim 3 wherein when yarns are fed to gauge parts of lower heights, after being fed to gauge parts of greater heights, the yarn feed amounts are computed to overfeed. 5. The tufting machine of claim 2 further comprising a second shiftable needle bar. 6. The tufting machine of claim 5 further comprising a second row of gauge parts. | A shiftable backing feed is utilized with a tufting machine having reciprocating needles and gauge parts for seizing yarns at a plurality of fixed heights, wherein fabric support apparatus reciprocates in synchronization with the cycles of the needle bar to support the backing during penetration of the backing fabric yet allow backing shifts between stitches.1. Using a tufting machine for forming tufted fabrics, comprising:
at least one shiftable needle bar having a series of needles mounted transversely across the width of the tufting machine; backing feed rolls for feeding a backing material through a tufting zone of the tufting machine; a yarn feed mechanism for feeding a series of yarns to said needles; at least one backing shifter for shifting said a plurality of backing feed rolls transversely across the tufting zone; a fabric support beneath the backing fabric equipped for reciprocal movement; a series of gauge parts mounted below the tufting zone in a position to engage needles of said at least one needle bar as the needles are reciprocated into the backing material to form tufts of yarns in the backing material; the gauge parts being arranged in a sequence of relatively taller and relatively lower yarn seizing elements and the at least one needlebar being shiftable to align needles with said relatively taller or relatively lower yarn seizing elements; and a control system for controlling and synchronizing the backing shifter, needle drive, backing feed, and fabric support reciprocation. 2. A tufting machine for forming tufted fabrics, comprising:
at least one shiftable needle bar having a series of needles mounted transversely across the width of the tufting machine; backing feed rolls for feeding a backing material through a tufting zone of the tufting machine; a yarn feed mechanism for feeding a series of yarns to said needles; at least one backing shifter for shifting said a plurality of backing feed rolls transversely across the tufting zone; a fabric support beneath the backing fabric equipped for reciprocal movement; a series of gauge parts having a plurality of fixed heights mounted below the tufting zone in a position to engage yarns carried by needles of said at least one needle bar as the needles are reciprocated into the backing material to form tufts of yarns in the backing material; the plurality of fixed heights including a relatively greater height so that yarns are seized relatively closer to the backing fabric, and a relatively lower height so that yarns are seized relatively further away from the backing fabric; the needle bar being shiftable to engage yarns carried by the transversely mounted needles with either the greater or lower height gauge parts; and a control system for controlling and synchronizing the backing shifter, needle drive, backing feed, and fabric support reciprocation. 3. A tufting machine for forming tufted fabrics, comprising:
first and second series of needles mounted transversely across the width of the tufting machine; backing feed rolls for feeding a backing material through a tufting zone of the tufting machine; a yarn feed mechanism for feeding a series of yarns to said needles; at least one backing shifter for shifting said a plurality of backing feed rolls transversely across the tufting zone; a fabric support beneath the backing fabric equipped for reciprocal movement; a first series of gauge parts having a first fixed height mounted below the tufting zone in a position to engage yarns carried by needles of the first series as the needles are reciprocated into the backing material to form tufts of yarns in the backing material; a second series of gauge parts having a second fixed height mounted below the tufting zone in a position to engage yarns carried by needles of the second series as the needles are reciprocated into the backing material to form tufts of yarns in the backing material; a control system for controlling and synchronizing the backing shifter, needle drive, backing feed, and fabric support reciprocation. 4. The tufting machine of claim 3 wherein when yarns are fed to gauge parts of lower heights, after being fed to gauge parts of greater heights, the yarn feed amounts are computed to overfeed. 5. The tufting machine of claim 2 further comprising a second shiftable needle bar. 6. The tufting machine of claim 5 further comprising a second row of gauge parts. | 3,700 |
347,203 | 29,725,936 | 3,732 | A shiftable backing feed is utilized with a tufting machine having reciprocating needles and gauge parts for seizing yarns at a plurality of fixed heights, wherein fabric support apparatus reciprocates in synchronization with the cycles of the needle bar to support the backing during penetration of the backing fabric yet allow backing shifts between stitches. | 1. Using a tufting machine for forming tufted fabrics, comprising:
at least one shiftable needle bar having a series of needles mounted transversely across the width of the tufting machine; backing feed rolls for feeding a backing material through a tufting zone of the tufting machine; a yarn feed mechanism for feeding a series of yarns to said needles; at least one backing shifter for shifting said a plurality of backing feed rolls transversely across the tufting zone; a fabric support beneath the backing fabric equipped for reciprocal movement; a series of gauge parts mounted below the tufting zone in a position to engage needles of said at least one needle bar as the needles are reciprocated into the backing material to form tufts of yarns in the backing material; the gauge parts being arranged in a sequence of relatively taller and relatively lower yarn seizing elements and the at least one needlebar being shiftable to align needles with said relatively taller or relatively lower yarn seizing elements; and a control system for controlling and synchronizing the backing shifter, needle drive, backing feed, and fabric support reciprocation. 2. A tufting machine for forming tufted fabrics, comprising:
at least one shiftable needle bar having a series of needles mounted transversely across the width of the tufting machine; backing feed rolls for feeding a backing material through a tufting zone of the tufting machine; a yarn feed mechanism for feeding a series of yarns to said needles; at least one backing shifter for shifting said a plurality of backing feed rolls transversely across the tufting zone; a fabric support beneath the backing fabric equipped for reciprocal movement; a series of gauge parts having a plurality of fixed heights mounted below the tufting zone in a position to engage yarns carried by needles of said at least one needle bar as the needles are reciprocated into the backing material to form tufts of yarns in the backing material; the plurality of fixed heights including a relatively greater height so that yarns are seized relatively closer to the backing fabric, and a relatively lower height so that yarns are seized relatively further away from the backing fabric; the needle bar being shiftable to engage yarns carried by the transversely mounted needles with either the greater or lower height gauge parts; and a control system for controlling and synchronizing the backing shifter, needle drive, backing feed, and fabric support reciprocation. 3. A tufting machine for forming tufted fabrics, comprising:
first and second series of needles mounted transversely across the width of the tufting machine; backing feed rolls for feeding a backing material through a tufting zone of the tufting machine; a yarn feed mechanism for feeding a series of yarns to said needles; at least one backing shifter for shifting said a plurality of backing feed rolls transversely across the tufting zone; a fabric support beneath the backing fabric equipped for reciprocal movement; a first series of gauge parts having a first fixed height mounted below the tufting zone in a position to engage yarns carried by needles of the first series as the needles are reciprocated into the backing material to form tufts of yarns in the backing material; a second series of gauge parts having a second fixed height mounted below the tufting zone in a position to engage yarns carried by needles of the second series as the needles are reciprocated into the backing material to form tufts of yarns in the backing material; a control system for controlling and synchronizing the backing shifter, needle drive, backing feed, and fabric support reciprocation. 4. The tufting machine of claim 3 wherein when yarns are fed to gauge parts of lower heights, after being fed to gauge parts of greater heights, the yarn feed amounts are computed to overfeed. 5. The tufting machine of claim 2 further comprising a second shiftable needle bar. 6. The tufting machine of claim 5 further comprising a second row of gauge parts. | A shiftable backing feed is utilized with a tufting machine having reciprocating needles and gauge parts for seizing yarns at a plurality of fixed heights, wherein fabric support apparatus reciprocates in synchronization with the cycles of the needle bar to support the backing during penetration of the backing fabric yet allow backing shifts between stitches.1. Using a tufting machine for forming tufted fabrics, comprising:
at least one shiftable needle bar having a series of needles mounted transversely across the width of the tufting machine; backing feed rolls for feeding a backing material through a tufting zone of the tufting machine; a yarn feed mechanism for feeding a series of yarns to said needles; at least one backing shifter for shifting said a plurality of backing feed rolls transversely across the tufting zone; a fabric support beneath the backing fabric equipped for reciprocal movement; a series of gauge parts mounted below the tufting zone in a position to engage needles of said at least one needle bar as the needles are reciprocated into the backing material to form tufts of yarns in the backing material; the gauge parts being arranged in a sequence of relatively taller and relatively lower yarn seizing elements and the at least one needlebar being shiftable to align needles with said relatively taller or relatively lower yarn seizing elements; and a control system for controlling and synchronizing the backing shifter, needle drive, backing feed, and fabric support reciprocation. 2. A tufting machine for forming tufted fabrics, comprising:
at least one shiftable needle bar having a series of needles mounted transversely across the width of the tufting machine; backing feed rolls for feeding a backing material through a tufting zone of the tufting machine; a yarn feed mechanism for feeding a series of yarns to said needles; at least one backing shifter for shifting said a plurality of backing feed rolls transversely across the tufting zone; a fabric support beneath the backing fabric equipped for reciprocal movement; a series of gauge parts having a plurality of fixed heights mounted below the tufting zone in a position to engage yarns carried by needles of said at least one needle bar as the needles are reciprocated into the backing material to form tufts of yarns in the backing material; the plurality of fixed heights including a relatively greater height so that yarns are seized relatively closer to the backing fabric, and a relatively lower height so that yarns are seized relatively further away from the backing fabric; the needle bar being shiftable to engage yarns carried by the transversely mounted needles with either the greater or lower height gauge parts; and a control system for controlling and synchronizing the backing shifter, needle drive, backing feed, and fabric support reciprocation. 3. A tufting machine for forming tufted fabrics, comprising:
first and second series of needles mounted transversely across the width of the tufting machine; backing feed rolls for feeding a backing material through a tufting zone of the tufting machine; a yarn feed mechanism for feeding a series of yarns to said needles; at least one backing shifter for shifting said a plurality of backing feed rolls transversely across the tufting zone; a fabric support beneath the backing fabric equipped for reciprocal movement; a first series of gauge parts having a first fixed height mounted below the tufting zone in a position to engage yarns carried by needles of the first series as the needles are reciprocated into the backing material to form tufts of yarns in the backing material; a second series of gauge parts having a second fixed height mounted below the tufting zone in a position to engage yarns carried by needles of the second series as the needles are reciprocated into the backing material to form tufts of yarns in the backing material; a control system for controlling and synchronizing the backing shifter, needle drive, backing feed, and fabric support reciprocation. 4. The tufting machine of claim 3 wherein when yarns are fed to gauge parts of lower heights, after being fed to gauge parts of greater heights, the yarn feed amounts are computed to overfeed. 5. The tufting machine of claim 2 further comprising a second shiftable needle bar. 6. The tufting machine of claim 5 further comprising a second row of gauge parts. | 3,700 |
347,204 | 16,805,612 | 3,732 | Provided herein is an ophthalmic composition formulated in deuterated water. Also disclosed herein are methods of treating, ameliorating, or reducing ophthalmic conditions or diseases by administering to an eye of an individual in need thereof an effective amount of an ophthalmic composition as described herein. | 1. An ophthalmic composition comprising about 0.001 wt % to about 20 wt % of pilocarpine or a pharmaceutically acceptable salt of pilocarpine and deuterated water, at a pD of about 4 to about 8. 2. The ophthalmic composition of claim 1, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of about 0.5 wt % to about 2.5 wt %, about 0.01 wt % to 0.45 wt %, or about 0.001 wt % to about 2 wt %. 3. The ophthalmic composition of claim 1, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of at least about 0.25 wt %, 0.5 wt %, or 1.0 wt %. 4. The ophthalmic composition of claim 1, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of one of: about 0.001 wt % to about 0.5 wt %, about 0.001 wt % to about 0.40 wt %, about 0.001 wt % to about 0.30 wt %, about 0.001 wt % to about 0.20 wt %, about 0.001 wt % to about 0.10 wt %, about 0.001 wt % to about 0.09 wt %, about 0.001 wt % to about 0.08 wt %, about 0.001 wt % to about 0.07 wt %, about 0.001 wt % to about 0.06 wt %, about 0.001 wt % to about 0.05 wt %, about 0.001 wt % to about 0.04 wt %, about 0.001 wt % to about 0.03 wt %, about 0.001 wt % to about 0.025 wt %, about 0.001 wt % to about 0.02 wt %, about 0.001 wt % to about 0.01 wt %, about 0.001 wt % to about 0.008 wt %, or about 0.001 wt % to about 0.005 wt %. 5. The ophthalmic composition of claim 1, wherein the ophthalmic composition comprises at least one of: about 80%, about 85%, about 90%, about 95%, about 97%, about 98%, or about 99% of the pilocarpine or the pharmaceutically acceptable salt of pilocarpine based on an initial concentration after an extended period of time under a storage condition, wherein the extended period of time is one of: about 1 week, about 2 weeks, about 3 weeks, about 1 month, about 2 months, about 3 months, about 4 months, about 5 months, about 6 months, about 8 months, about 10 months, about 12 months, about 18 months, about 24 months, about 36 months, about 4 years, or about 5 years. 6. The ophthalmic composition of claim 5, wherein the storage condition has a storage temperature of about 16° C. to about 30° C. or about 20° C. to about 25° C. 7. The ophthalmic composition of claim 1, wherein the ophthalmic composition is free of a preservative. 8. The ophthalmic composition of claim 1, wherein the ophthalmic composition further comprises ethylenediaminetetraacetic acid (EDTA). 9. The ophthalmic composition of claim 1, wherein the ophthalmic composition further comprises an osmolarity adjusting agent, a preservative, a buffering agent, a tonicity adjusting agent, a pD adjusting agent, a viscosity-enhancing agent, or a combination thereof. 10. The ophthalmic composition of claim 9, wherein the osmolarity adjusting agent is sodium chloride. 11. The ophthalmic composition of claim 9, wherein the preservative is selected from benzalkonium chloride, cetrimonium, sodium perborate, stabilized oxychloro complex, SofZia, polyquaternium-1, chlorobutanol, edetate disodium, polyhexamethylene biguanide, or combinations thereof. 12. The ophthalmic composition of claim 9, wherein the buffering agent is selected from borates, borate-polyol complexes, phosphate buffering agents, citrate buffering agents, acetate buffering agents, carbonate buffering agents, organic buffering agents, amino acid buffering agents, or combinations thereof. 13. The ophthalmic composition of claim 1, wherein the ophthalmic composition has a pD of one of: about 4.5 to about 7.5, about 5 to about 7.0, or about 6 to about 7.0. 14. The ophthalmic composition of claim 1, wherein the ophthalmic composition comprises one of: less than 10% of H2O, less than 8% of H2O, less than 6% of H2O, less than 5% of H2O, less than 4% of H2O, less than 3% of H2O, less than 2% of H2O, less than 1% of H2O, less than 0.5% of H2O, less than 0.1% of H2O, or 0% of H2O. 15. An ophthalmic composition comprising about 0.001 wt % to about 20 wt % of tropicamide or a pharmaceutically acceptable salt of tropicamide and deuterated water, at a pD of about 4 to about 8. 16. The ophthalmic composition of claim 15, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration about 0.010 wt % to about 0.1 wt % or about 0.025 wt % to about 0.1 wt %. 17. The ophthalmic composition of claim 15, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration of at least about 0.02 wt %, 0.5 wt %, or 1.0 wt %. 18. The ophthalmic composition of claim 15, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration of one of: about 0.001 wt % to about 0.5 wt %, about 0.001 wt % to about 0.40 wt %, about 0.001 wt % to about 0.30 wt %, about 0.001 wt % to about 0.20 wt %, about 0.001 wt % to about 0.10 wt %, about 0.001 wt % to about 0.09 wt %, about 0.001 wt % to about 0.08 wt %, about 0.001 wt % to about 0.07 wt %, about 0.001 wt % to about 0.06 wt %, about 0.001 wt % to about 0.05 wt %, about 0.001 wt % to about 0.04 wt %, about 0.001 wt % to about 0.03 wt %, about 0.001 wt % to about 0.025 wt %, about 0.001 wt % to about 0.02 wt %, about 0.001 wt % to about 0.01 wt %, about 0.001 wt % to about 0.008 wt %, or about 0.001 wt % to about 0.005 wt %. 19. The ophthalmic composition of claim 15, wherein the ophthalmic composition comprises at least one of: about 80%, about 85%, about 90%, about 95%, about 97%, about 98%, or about 99% of the tropicamide or the pharmaceutically acceptable salt of tropicamide based on an initial concentration after an extended period of time under a storage condition, wherein the extended period of time is one of: about 1 week, about 2 weeks, about 3 weeks, about 1 month, about 2 months, about 3 months, about 4 months, about 5 months, about 6 months, about 8 months, about 10 months, about 12 months, about 18 months, about 24 months, about 36 months, about 4 years, or about 5 years. 20. The ophthalmic composition of claim 19, wherein the storage condition has a storage temperature of about 16° C. to about 30° C. or about 20° C. to about 25° C. 21. The ophthalmic composition of claim 15, wherein the ophthalmic composition is free of a preservative. 22. The ophthalmic composition of claim 15, wherein the ophthalmic composition further comprises ethylenediaminetetraacetic acid (EDTA). 23. The ophthalmic composition of claim 15, wherein the ophthalmic composition further comprises an osmolarity adjusting agent, a preservative, a buffering agent, a tonicity adjusting agent, a pD adjusting agent, a viscosity-enhancing agent, or a combination thereof. 24. The ophthalmic composition of claim 15, wherein the ophthalmic composition comprises one of: less than 10% of H2O, less than 8% of H2O, less than 6% of H2O, less than 5% of H2O, less than 4% of H2O, less than 3% of H2O, less than 2% of H2O, less than 1% of H2O, less than 0.5% of H2O, less than 0.1% of H2O, or 0% of H2O. 25. An ophthalmic composition comprising about 0.001 wt % to about 20 wt % of pilocarpine or a pharmaceutically acceptable salt of pilocarpine, about 0.001 wt % to about 20 wt % of tropicamide or a pharmaceutically acceptable salt of tropicamide, and deuterated water, at a pD of about 4 to about 8. 26. The ophthalmic composition of claim 25, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of about 0.5 wt % to about 2.5 wt %, about 0.01 wt % to 0.45 wt %, or about 0.001 wt % to about 2 wt %. 27. The ophthalmic composition of claim 25, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of at least about 0.25 wt %, 0.5 wt %, or 1.0 wt %. 28. The ophthalmic composition of claim 25, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration about 0.010 wt % to about 0.1 wt % or about 0.025 wt % to about 0.1 wt %. 29. The ophthalmic composition of claim 25, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration of at least about 0.02 wt %, 0.5 wt %, or 1.0 wt %. 30. The ophthalmic composition of claim 25, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine or the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration of one of: about 0.001 wt % to about 0.5 wt %, about 0.001 wt % to about 0.40 wt %, about 0.001 wt % to about 0.30 wt %, about 0.001 wt % to about 0.20 wt %, about 0.001 wt % to about 0.10 wt %, about 0.001 wt % to about 0.09 wt %, about 0.001 wt % to about 0.08 wt %, about 0.001 wt % to about 0.07 wt %, about 0.001 wt % to about 0.06 wt %, about 0.001 wt % to about 0.05 wt %, about 0.001 wt % to about 0.04 wt %, about 0.001 wt % to about 0.03 wt %, about 0.001 wt % to about 0.025 wt %, about 0.001 wt % to about 0.02 wt %, about 0.001 wt % to about 0.01 wt %, about 0.001 wt % to about 0.008 wt %, or about 0.001 wt % to about 0.005 wt %. | Provided herein is an ophthalmic composition formulated in deuterated water. Also disclosed herein are methods of treating, ameliorating, or reducing ophthalmic conditions or diseases by administering to an eye of an individual in need thereof an effective amount of an ophthalmic composition as described herein.1. An ophthalmic composition comprising about 0.001 wt % to about 20 wt % of pilocarpine or a pharmaceutically acceptable salt of pilocarpine and deuterated water, at a pD of about 4 to about 8. 2. The ophthalmic composition of claim 1, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of about 0.5 wt % to about 2.5 wt %, about 0.01 wt % to 0.45 wt %, or about 0.001 wt % to about 2 wt %. 3. The ophthalmic composition of claim 1, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of at least about 0.25 wt %, 0.5 wt %, or 1.0 wt %. 4. The ophthalmic composition of claim 1, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of one of: about 0.001 wt % to about 0.5 wt %, about 0.001 wt % to about 0.40 wt %, about 0.001 wt % to about 0.30 wt %, about 0.001 wt % to about 0.20 wt %, about 0.001 wt % to about 0.10 wt %, about 0.001 wt % to about 0.09 wt %, about 0.001 wt % to about 0.08 wt %, about 0.001 wt % to about 0.07 wt %, about 0.001 wt % to about 0.06 wt %, about 0.001 wt % to about 0.05 wt %, about 0.001 wt % to about 0.04 wt %, about 0.001 wt % to about 0.03 wt %, about 0.001 wt % to about 0.025 wt %, about 0.001 wt % to about 0.02 wt %, about 0.001 wt % to about 0.01 wt %, about 0.001 wt % to about 0.008 wt %, or about 0.001 wt % to about 0.005 wt %. 5. The ophthalmic composition of claim 1, wherein the ophthalmic composition comprises at least one of: about 80%, about 85%, about 90%, about 95%, about 97%, about 98%, or about 99% of the pilocarpine or the pharmaceutically acceptable salt of pilocarpine based on an initial concentration after an extended period of time under a storage condition, wherein the extended period of time is one of: about 1 week, about 2 weeks, about 3 weeks, about 1 month, about 2 months, about 3 months, about 4 months, about 5 months, about 6 months, about 8 months, about 10 months, about 12 months, about 18 months, about 24 months, about 36 months, about 4 years, or about 5 years. 6. The ophthalmic composition of claim 5, wherein the storage condition has a storage temperature of about 16° C. to about 30° C. or about 20° C. to about 25° C. 7. The ophthalmic composition of claim 1, wherein the ophthalmic composition is free of a preservative. 8. The ophthalmic composition of claim 1, wherein the ophthalmic composition further comprises ethylenediaminetetraacetic acid (EDTA). 9. The ophthalmic composition of claim 1, wherein the ophthalmic composition further comprises an osmolarity adjusting agent, a preservative, a buffering agent, a tonicity adjusting agent, a pD adjusting agent, a viscosity-enhancing agent, or a combination thereof. 10. The ophthalmic composition of claim 9, wherein the osmolarity adjusting agent is sodium chloride. 11. The ophthalmic composition of claim 9, wherein the preservative is selected from benzalkonium chloride, cetrimonium, sodium perborate, stabilized oxychloro complex, SofZia, polyquaternium-1, chlorobutanol, edetate disodium, polyhexamethylene biguanide, or combinations thereof. 12. The ophthalmic composition of claim 9, wherein the buffering agent is selected from borates, borate-polyol complexes, phosphate buffering agents, citrate buffering agents, acetate buffering agents, carbonate buffering agents, organic buffering agents, amino acid buffering agents, or combinations thereof. 13. The ophthalmic composition of claim 1, wherein the ophthalmic composition has a pD of one of: about 4.5 to about 7.5, about 5 to about 7.0, or about 6 to about 7.0. 14. The ophthalmic composition of claim 1, wherein the ophthalmic composition comprises one of: less than 10% of H2O, less than 8% of H2O, less than 6% of H2O, less than 5% of H2O, less than 4% of H2O, less than 3% of H2O, less than 2% of H2O, less than 1% of H2O, less than 0.5% of H2O, less than 0.1% of H2O, or 0% of H2O. 15. An ophthalmic composition comprising about 0.001 wt % to about 20 wt % of tropicamide or a pharmaceutically acceptable salt of tropicamide and deuterated water, at a pD of about 4 to about 8. 16. The ophthalmic composition of claim 15, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration about 0.010 wt % to about 0.1 wt % or about 0.025 wt % to about 0.1 wt %. 17. The ophthalmic composition of claim 15, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration of at least about 0.02 wt %, 0.5 wt %, or 1.0 wt %. 18. The ophthalmic composition of claim 15, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration of one of: about 0.001 wt % to about 0.5 wt %, about 0.001 wt % to about 0.40 wt %, about 0.001 wt % to about 0.30 wt %, about 0.001 wt % to about 0.20 wt %, about 0.001 wt % to about 0.10 wt %, about 0.001 wt % to about 0.09 wt %, about 0.001 wt % to about 0.08 wt %, about 0.001 wt % to about 0.07 wt %, about 0.001 wt % to about 0.06 wt %, about 0.001 wt % to about 0.05 wt %, about 0.001 wt % to about 0.04 wt %, about 0.001 wt % to about 0.03 wt %, about 0.001 wt % to about 0.025 wt %, about 0.001 wt % to about 0.02 wt %, about 0.001 wt % to about 0.01 wt %, about 0.001 wt % to about 0.008 wt %, or about 0.001 wt % to about 0.005 wt %. 19. The ophthalmic composition of claim 15, wherein the ophthalmic composition comprises at least one of: about 80%, about 85%, about 90%, about 95%, about 97%, about 98%, or about 99% of the tropicamide or the pharmaceutically acceptable salt of tropicamide based on an initial concentration after an extended period of time under a storage condition, wherein the extended period of time is one of: about 1 week, about 2 weeks, about 3 weeks, about 1 month, about 2 months, about 3 months, about 4 months, about 5 months, about 6 months, about 8 months, about 10 months, about 12 months, about 18 months, about 24 months, about 36 months, about 4 years, or about 5 years. 20. The ophthalmic composition of claim 19, wherein the storage condition has a storage temperature of about 16° C. to about 30° C. or about 20° C. to about 25° C. 21. The ophthalmic composition of claim 15, wherein the ophthalmic composition is free of a preservative. 22. The ophthalmic composition of claim 15, wherein the ophthalmic composition further comprises ethylenediaminetetraacetic acid (EDTA). 23. The ophthalmic composition of claim 15, wherein the ophthalmic composition further comprises an osmolarity adjusting agent, a preservative, a buffering agent, a tonicity adjusting agent, a pD adjusting agent, a viscosity-enhancing agent, or a combination thereof. 24. The ophthalmic composition of claim 15, wherein the ophthalmic composition comprises one of: less than 10% of H2O, less than 8% of H2O, less than 6% of H2O, less than 5% of H2O, less than 4% of H2O, less than 3% of H2O, less than 2% of H2O, less than 1% of H2O, less than 0.5% of H2O, less than 0.1% of H2O, or 0% of H2O. 25. An ophthalmic composition comprising about 0.001 wt % to about 20 wt % of pilocarpine or a pharmaceutically acceptable salt of pilocarpine, about 0.001 wt % to about 20 wt % of tropicamide or a pharmaceutically acceptable salt of tropicamide, and deuterated water, at a pD of about 4 to about 8. 26. The ophthalmic composition of claim 25, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of about 0.5 wt % to about 2.5 wt %, about 0.01 wt % to 0.45 wt %, or about 0.001 wt % to about 2 wt %. 27. The ophthalmic composition of claim 25, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of at least about 0.25 wt %, 0.5 wt %, or 1.0 wt %. 28. The ophthalmic composition of claim 25, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration about 0.010 wt % to about 0.1 wt % or about 0.025 wt % to about 0.1 wt %. 29. The ophthalmic composition of claim 25, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration of at least about 0.02 wt %, 0.5 wt %, or 1.0 wt %. 30. The ophthalmic composition of claim 25, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine or the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration of one of: about 0.001 wt % to about 0.5 wt %, about 0.001 wt % to about 0.40 wt %, about 0.001 wt % to about 0.30 wt %, about 0.001 wt % to about 0.20 wt %, about 0.001 wt % to about 0.10 wt %, about 0.001 wt % to about 0.09 wt %, about 0.001 wt % to about 0.08 wt %, about 0.001 wt % to about 0.07 wt %, about 0.001 wt % to about 0.06 wt %, about 0.001 wt % to about 0.05 wt %, about 0.001 wt % to about 0.04 wt %, about 0.001 wt % to about 0.03 wt %, about 0.001 wt % to about 0.025 wt %, about 0.001 wt % to about 0.02 wt %, about 0.001 wt % to about 0.01 wt %, about 0.001 wt % to about 0.008 wt %, or about 0.001 wt % to about 0.005 wt %. | 3,700 |
347,205 | 29,725,944 | 3,732 | Provided herein is an ophthalmic composition formulated in deuterated water. Also disclosed herein are methods of treating, ameliorating, or reducing ophthalmic conditions or diseases by administering to an eye of an individual in need thereof an effective amount of an ophthalmic composition as described herein. | 1. An ophthalmic composition comprising about 0.001 wt % to about 20 wt % of pilocarpine or a pharmaceutically acceptable salt of pilocarpine and deuterated water, at a pD of about 4 to about 8. 2. The ophthalmic composition of claim 1, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of about 0.5 wt % to about 2.5 wt %, about 0.01 wt % to 0.45 wt %, or about 0.001 wt % to about 2 wt %. 3. The ophthalmic composition of claim 1, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of at least about 0.25 wt %, 0.5 wt %, or 1.0 wt %. 4. The ophthalmic composition of claim 1, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of one of: about 0.001 wt % to about 0.5 wt %, about 0.001 wt % to about 0.40 wt %, about 0.001 wt % to about 0.30 wt %, about 0.001 wt % to about 0.20 wt %, about 0.001 wt % to about 0.10 wt %, about 0.001 wt % to about 0.09 wt %, about 0.001 wt % to about 0.08 wt %, about 0.001 wt % to about 0.07 wt %, about 0.001 wt % to about 0.06 wt %, about 0.001 wt % to about 0.05 wt %, about 0.001 wt % to about 0.04 wt %, about 0.001 wt % to about 0.03 wt %, about 0.001 wt % to about 0.025 wt %, about 0.001 wt % to about 0.02 wt %, about 0.001 wt % to about 0.01 wt %, about 0.001 wt % to about 0.008 wt %, or about 0.001 wt % to about 0.005 wt %. 5. The ophthalmic composition of claim 1, wherein the ophthalmic composition comprises at least one of: about 80%, about 85%, about 90%, about 95%, about 97%, about 98%, or about 99% of the pilocarpine or the pharmaceutically acceptable salt of pilocarpine based on an initial concentration after an extended period of time under a storage condition, wherein the extended period of time is one of: about 1 week, about 2 weeks, about 3 weeks, about 1 month, about 2 months, about 3 months, about 4 months, about 5 months, about 6 months, about 8 months, about 10 months, about 12 months, about 18 months, about 24 months, about 36 months, about 4 years, or about 5 years. 6. The ophthalmic composition of claim 5, wherein the storage condition has a storage temperature of about 16° C. to about 30° C. or about 20° C. to about 25° C. 7. The ophthalmic composition of claim 1, wherein the ophthalmic composition is free of a preservative. 8. The ophthalmic composition of claim 1, wherein the ophthalmic composition further comprises ethylenediaminetetraacetic acid (EDTA). 9. The ophthalmic composition of claim 1, wherein the ophthalmic composition further comprises an osmolarity adjusting agent, a preservative, a buffering agent, a tonicity adjusting agent, a pD adjusting agent, a viscosity-enhancing agent, or a combination thereof. 10. The ophthalmic composition of claim 9, wherein the osmolarity adjusting agent is sodium chloride. 11. The ophthalmic composition of claim 9, wherein the preservative is selected from benzalkonium chloride, cetrimonium, sodium perborate, stabilized oxychloro complex, SofZia, polyquaternium-1, chlorobutanol, edetate disodium, polyhexamethylene biguanide, or combinations thereof. 12. The ophthalmic composition of claim 9, wherein the buffering agent is selected from borates, borate-polyol complexes, phosphate buffering agents, citrate buffering agents, acetate buffering agents, carbonate buffering agents, organic buffering agents, amino acid buffering agents, or combinations thereof. 13. The ophthalmic composition of claim 1, wherein the ophthalmic composition has a pD of one of: about 4.5 to about 7.5, about 5 to about 7.0, or about 6 to about 7.0. 14. The ophthalmic composition of claim 1, wherein the ophthalmic composition comprises one of: less than 10% of H2O, less than 8% of H2O, less than 6% of H2O, less than 5% of H2O, less than 4% of H2O, less than 3% of H2O, less than 2% of H2O, less than 1% of H2O, less than 0.5% of H2O, less than 0.1% of H2O, or 0% of H2O. 15. An ophthalmic composition comprising about 0.001 wt % to about 20 wt % of tropicamide or a pharmaceutically acceptable salt of tropicamide and deuterated water, at a pD of about 4 to about 8. 16. The ophthalmic composition of claim 15, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration about 0.010 wt % to about 0.1 wt % or about 0.025 wt % to about 0.1 wt %. 17. The ophthalmic composition of claim 15, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration of at least about 0.02 wt %, 0.5 wt %, or 1.0 wt %. 18. The ophthalmic composition of claim 15, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration of one of: about 0.001 wt % to about 0.5 wt %, about 0.001 wt % to about 0.40 wt %, about 0.001 wt % to about 0.30 wt %, about 0.001 wt % to about 0.20 wt %, about 0.001 wt % to about 0.10 wt %, about 0.001 wt % to about 0.09 wt %, about 0.001 wt % to about 0.08 wt %, about 0.001 wt % to about 0.07 wt %, about 0.001 wt % to about 0.06 wt %, about 0.001 wt % to about 0.05 wt %, about 0.001 wt % to about 0.04 wt %, about 0.001 wt % to about 0.03 wt %, about 0.001 wt % to about 0.025 wt %, about 0.001 wt % to about 0.02 wt %, about 0.001 wt % to about 0.01 wt %, about 0.001 wt % to about 0.008 wt %, or about 0.001 wt % to about 0.005 wt %. 19. The ophthalmic composition of claim 15, wherein the ophthalmic composition comprises at least one of: about 80%, about 85%, about 90%, about 95%, about 97%, about 98%, or about 99% of the tropicamide or the pharmaceutically acceptable salt of tropicamide based on an initial concentration after an extended period of time under a storage condition, wherein the extended period of time is one of: about 1 week, about 2 weeks, about 3 weeks, about 1 month, about 2 months, about 3 months, about 4 months, about 5 months, about 6 months, about 8 months, about 10 months, about 12 months, about 18 months, about 24 months, about 36 months, about 4 years, or about 5 years. 20. The ophthalmic composition of claim 19, wherein the storage condition has a storage temperature of about 16° C. to about 30° C. or about 20° C. to about 25° C. 21. The ophthalmic composition of claim 15, wherein the ophthalmic composition is free of a preservative. 22. The ophthalmic composition of claim 15, wherein the ophthalmic composition further comprises ethylenediaminetetraacetic acid (EDTA). 23. The ophthalmic composition of claim 15, wherein the ophthalmic composition further comprises an osmolarity adjusting agent, a preservative, a buffering agent, a tonicity adjusting agent, a pD adjusting agent, a viscosity-enhancing agent, or a combination thereof. 24. The ophthalmic composition of claim 15, wherein the ophthalmic composition comprises one of: less than 10% of H2O, less than 8% of H2O, less than 6% of H2O, less than 5% of H2O, less than 4% of H2O, less than 3% of H2O, less than 2% of H2O, less than 1% of H2O, less than 0.5% of H2O, less than 0.1% of H2O, or 0% of H2O. 25. An ophthalmic composition comprising about 0.001 wt % to about 20 wt % of pilocarpine or a pharmaceutically acceptable salt of pilocarpine, about 0.001 wt % to about 20 wt % of tropicamide or a pharmaceutically acceptable salt of tropicamide, and deuterated water, at a pD of about 4 to about 8. 26. The ophthalmic composition of claim 25, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of about 0.5 wt % to about 2.5 wt %, about 0.01 wt % to 0.45 wt %, or about 0.001 wt % to about 2 wt %. 27. The ophthalmic composition of claim 25, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of at least about 0.25 wt %, 0.5 wt %, or 1.0 wt %. 28. The ophthalmic composition of claim 25, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration about 0.010 wt % to about 0.1 wt % or about 0.025 wt % to about 0.1 wt %. 29. The ophthalmic composition of claim 25, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration of at least about 0.02 wt %, 0.5 wt %, or 1.0 wt %. 30. The ophthalmic composition of claim 25, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine or the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration of one of: about 0.001 wt % to about 0.5 wt %, about 0.001 wt % to about 0.40 wt %, about 0.001 wt % to about 0.30 wt %, about 0.001 wt % to about 0.20 wt %, about 0.001 wt % to about 0.10 wt %, about 0.001 wt % to about 0.09 wt %, about 0.001 wt % to about 0.08 wt %, about 0.001 wt % to about 0.07 wt %, about 0.001 wt % to about 0.06 wt %, about 0.001 wt % to about 0.05 wt %, about 0.001 wt % to about 0.04 wt %, about 0.001 wt % to about 0.03 wt %, about 0.001 wt % to about 0.025 wt %, about 0.001 wt % to about 0.02 wt %, about 0.001 wt % to about 0.01 wt %, about 0.001 wt % to about 0.008 wt %, or about 0.001 wt % to about 0.005 wt %. | Provided herein is an ophthalmic composition formulated in deuterated water. Also disclosed herein are methods of treating, ameliorating, or reducing ophthalmic conditions or diseases by administering to an eye of an individual in need thereof an effective amount of an ophthalmic composition as described herein.1. An ophthalmic composition comprising about 0.001 wt % to about 20 wt % of pilocarpine or a pharmaceutically acceptable salt of pilocarpine and deuterated water, at a pD of about 4 to about 8. 2. The ophthalmic composition of claim 1, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of about 0.5 wt % to about 2.5 wt %, about 0.01 wt % to 0.45 wt %, or about 0.001 wt % to about 2 wt %. 3. The ophthalmic composition of claim 1, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of at least about 0.25 wt %, 0.5 wt %, or 1.0 wt %. 4. The ophthalmic composition of claim 1, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of one of: about 0.001 wt % to about 0.5 wt %, about 0.001 wt % to about 0.40 wt %, about 0.001 wt % to about 0.30 wt %, about 0.001 wt % to about 0.20 wt %, about 0.001 wt % to about 0.10 wt %, about 0.001 wt % to about 0.09 wt %, about 0.001 wt % to about 0.08 wt %, about 0.001 wt % to about 0.07 wt %, about 0.001 wt % to about 0.06 wt %, about 0.001 wt % to about 0.05 wt %, about 0.001 wt % to about 0.04 wt %, about 0.001 wt % to about 0.03 wt %, about 0.001 wt % to about 0.025 wt %, about 0.001 wt % to about 0.02 wt %, about 0.001 wt % to about 0.01 wt %, about 0.001 wt % to about 0.008 wt %, or about 0.001 wt % to about 0.005 wt %. 5. The ophthalmic composition of claim 1, wherein the ophthalmic composition comprises at least one of: about 80%, about 85%, about 90%, about 95%, about 97%, about 98%, or about 99% of the pilocarpine or the pharmaceutically acceptable salt of pilocarpine based on an initial concentration after an extended period of time under a storage condition, wherein the extended period of time is one of: about 1 week, about 2 weeks, about 3 weeks, about 1 month, about 2 months, about 3 months, about 4 months, about 5 months, about 6 months, about 8 months, about 10 months, about 12 months, about 18 months, about 24 months, about 36 months, about 4 years, or about 5 years. 6. The ophthalmic composition of claim 5, wherein the storage condition has a storage temperature of about 16° C. to about 30° C. or about 20° C. to about 25° C. 7. The ophthalmic composition of claim 1, wherein the ophthalmic composition is free of a preservative. 8. The ophthalmic composition of claim 1, wherein the ophthalmic composition further comprises ethylenediaminetetraacetic acid (EDTA). 9. The ophthalmic composition of claim 1, wherein the ophthalmic composition further comprises an osmolarity adjusting agent, a preservative, a buffering agent, a tonicity adjusting agent, a pD adjusting agent, a viscosity-enhancing agent, or a combination thereof. 10. The ophthalmic composition of claim 9, wherein the osmolarity adjusting agent is sodium chloride. 11. The ophthalmic composition of claim 9, wherein the preservative is selected from benzalkonium chloride, cetrimonium, sodium perborate, stabilized oxychloro complex, SofZia, polyquaternium-1, chlorobutanol, edetate disodium, polyhexamethylene biguanide, or combinations thereof. 12. The ophthalmic composition of claim 9, wherein the buffering agent is selected from borates, borate-polyol complexes, phosphate buffering agents, citrate buffering agents, acetate buffering agents, carbonate buffering agents, organic buffering agents, amino acid buffering agents, or combinations thereof. 13. The ophthalmic composition of claim 1, wherein the ophthalmic composition has a pD of one of: about 4.5 to about 7.5, about 5 to about 7.0, or about 6 to about 7.0. 14. The ophthalmic composition of claim 1, wherein the ophthalmic composition comprises one of: less than 10% of H2O, less than 8% of H2O, less than 6% of H2O, less than 5% of H2O, less than 4% of H2O, less than 3% of H2O, less than 2% of H2O, less than 1% of H2O, less than 0.5% of H2O, less than 0.1% of H2O, or 0% of H2O. 15. An ophthalmic composition comprising about 0.001 wt % to about 20 wt % of tropicamide or a pharmaceutically acceptable salt of tropicamide and deuterated water, at a pD of about 4 to about 8. 16. The ophthalmic composition of claim 15, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration about 0.010 wt % to about 0.1 wt % or about 0.025 wt % to about 0.1 wt %. 17. The ophthalmic composition of claim 15, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration of at least about 0.02 wt %, 0.5 wt %, or 1.0 wt %. 18. The ophthalmic composition of claim 15, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration of one of: about 0.001 wt % to about 0.5 wt %, about 0.001 wt % to about 0.40 wt %, about 0.001 wt % to about 0.30 wt %, about 0.001 wt % to about 0.20 wt %, about 0.001 wt % to about 0.10 wt %, about 0.001 wt % to about 0.09 wt %, about 0.001 wt % to about 0.08 wt %, about 0.001 wt % to about 0.07 wt %, about 0.001 wt % to about 0.06 wt %, about 0.001 wt % to about 0.05 wt %, about 0.001 wt % to about 0.04 wt %, about 0.001 wt % to about 0.03 wt %, about 0.001 wt % to about 0.025 wt %, about 0.001 wt % to about 0.02 wt %, about 0.001 wt % to about 0.01 wt %, about 0.001 wt % to about 0.008 wt %, or about 0.001 wt % to about 0.005 wt %. 19. The ophthalmic composition of claim 15, wherein the ophthalmic composition comprises at least one of: about 80%, about 85%, about 90%, about 95%, about 97%, about 98%, or about 99% of the tropicamide or the pharmaceutically acceptable salt of tropicamide based on an initial concentration after an extended period of time under a storage condition, wherein the extended period of time is one of: about 1 week, about 2 weeks, about 3 weeks, about 1 month, about 2 months, about 3 months, about 4 months, about 5 months, about 6 months, about 8 months, about 10 months, about 12 months, about 18 months, about 24 months, about 36 months, about 4 years, or about 5 years. 20. The ophthalmic composition of claim 19, wherein the storage condition has a storage temperature of about 16° C. to about 30° C. or about 20° C. to about 25° C. 21. The ophthalmic composition of claim 15, wherein the ophthalmic composition is free of a preservative. 22. The ophthalmic composition of claim 15, wherein the ophthalmic composition further comprises ethylenediaminetetraacetic acid (EDTA). 23. The ophthalmic composition of claim 15, wherein the ophthalmic composition further comprises an osmolarity adjusting agent, a preservative, a buffering agent, a tonicity adjusting agent, a pD adjusting agent, a viscosity-enhancing agent, or a combination thereof. 24. The ophthalmic composition of claim 15, wherein the ophthalmic composition comprises one of: less than 10% of H2O, less than 8% of H2O, less than 6% of H2O, less than 5% of H2O, less than 4% of H2O, less than 3% of H2O, less than 2% of H2O, less than 1% of H2O, less than 0.5% of H2O, less than 0.1% of H2O, or 0% of H2O. 25. An ophthalmic composition comprising about 0.001 wt % to about 20 wt % of pilocarpine or a pharmaceutically acceptable salt of pilocarpine, about 0.001 wt % to about 20 wt % of tropicamide or a pharmaceutically acceptable salt of tropicamide, and deuterated water, at a pD of about 4 to about 8. 26. The ophthalmic composition of claim 25, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of about 0.5 wt % to about 2.5 wt %, about 0.01 wt % to 0.45 wt %, or about 0.001 wt % to about 2 wt %. 27. The ophthalmic composition of claim 25, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine is present in the ophthalmic composition at a concentration of at least about 0.25 wt %, 0.5 wt %, or 1.0 wt %. 28. The ophthalmic composition of claim 25, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration about 0.010 wt % to about 0.1 wt % or about 0.025 wt % to about 0.1 wt %. 29. The ophthalmic composition of claim 25, wherein the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration of at least about 0.02 wt %, 0.5 wt %, or 1.0 wt %. 30. The ophthalmic composition of claim 25, wherein the pilocarpine or the pharmaceutically acceptable salt of pilocarpine or the tropicamide or the pharmaceutically acceptable salt of tropicamide is present in the ophthalmic composition at a concentration of one of: about 0.001 wt % to about 0.5 wt %, about 0.001 wt % to about 0.40 wt %, about 0.001 wt % to about 0.30 wt %, about 0.001 wt % to about 0.20 wt %, about 0.001 wt % to about 0.10 wt %, about 0.001 wt % to about 0.09 wt %, about 0.001 wt % to about 0.08 wt %, about 0.001 wt % to about 0.07 wt %, about 0.001 wt % to about 0.06 wt %, about 0.001 wt % to about 0.05 wt %, about 0.001 wt % to about 0.04 wt %, about 0.001 wt % to about 0.03 wt %, about 0.001 wt % to about 0.025 wt %, about 0.001 wt % to about 0.02 wt %, about 0.001 wt % to about 0.01 wt %, about 0.001 wt % to about 0.008 wt %, or about 0.001 wt % to about 0.005 wt %. | 3,700 |
347,206 | 16,805,686 | 1,648 | A method of detecting integrated stress response activity in living cells comprising inducing UL148-marker expression, scanning the cells to determine if the UL148 is punctate or diffuse, and ranking the level of ISR activity based on how punctate the UL148 is in the cell. The marker may be a fluorescent marker. The fluorescent marker may be Green fluorescent protein. The cell may be an epithelial cell. The cells may be ARPE-19 epithelial cells carrying a doxycycline inducible gene expression cassette encoding UL148-GFP and treating the cells for 18 hours with 100 ng/mL doxycycline hyclate to induce UL148-GFP expression. The cells may have an inducible gene expression cassette encoding UL148-marker expression. The UL148-marker expression may be induced by the cell being treated with an antibiotic. The method may include adding marker to the cells. The cells may be mutated to express UL148-marker upon inducement. A kit to conduct the method. | 1. A method of detecting integrated stress response activity in living cells comprising:
inducing UL148-marker expression; scanning the cells to determine if the UL148 is punctate or diffuse; and ranking the level of ISR activity based on how punctate the UL148 is in the cell. 2. The method of claim 1 wherein the marker is a fluorescent marker. 3. The method of claim 2 wherein the fluorescent marker is Green fluorescent protein. 4. The method of claim 1 wherein the cell is an epithelial cell. 5. The method of claim 1 wherein the cells are ARPE-19 epithelial cells carrying a doxycycline inducible gene expression cassette encoding UL148-GFP and treating the cells for 18 hours with 100 ng/mL doxycycline hyclate to induce UL148-GFP expression. 6. The method of claim 1 wherein the cells have an inducible gene expression cassette encoding UL148-marker expression. 7. The method of claim 1 wherein the UL148-marker expression is induced by the cells being treated with an antibiotic. 8. The method of claim 1 further comprising adding marker to the cells. 9. The method of claim 1 wherein the cells are mutated to express UL148-marker upon inducement. 10. A kit to conduct the method of claim 1. | A method of detecting integrated stress response activity in living cells comprising inducing UL148-marker expression, scanning the cells to determine if the UL148 is punctate or diffuse, and ranking the level of ISR activity based on how punctate the UL148 is in the cell. The marker may be a fluorescent marker. The fluorescent marker may be Green fluorescent protein. The cell may be an epithelial cell. The cells may be ARPE-19 epithelial cells carrying a doxycycline inducible gene expression cassette encoding UL148-GFP and treating the cells for 18 hours with 100 ng/mL doxycycline hyclate to induce UL148-GFP expression. The cells may have an inducible gene expression cassette encoding UL148-marker expression. The UL148-marker expression may be induced by the cell being treated with an antibiotic. The method may include adding marker to the cells. The cells may be mutated to express UL148-marker upon inducement. A kit to conduct the method.1. A method of detecting integrated stress response activity in living cells comprising:
inducing UL148-marker expression; scanning the cells to determine if the UL148 is punctate or diffuse; and ranking the level of ISR activity based on how punctate the UL148 is in the cell. 2. The method of claim 1 wherein the marker is a fluorescent marker. 3. The method of claim 2 wherein the fluorescent marker is Green fluorescent protein. 4. The method of claim 1 wherein the cell is an epithelial cell. 5. The method of claim 1 wherein the cells are ARPE-19 epithelial cells carrying a doxycycline inducible gene expression cassette encoding UL148-GFP and treating the cells for 18 hours with 100 ng/mL doxycycline hyclate to induce UL148-GFP expression. 6. The method of claim 1 wherein the cells have an inducible gene expression cassette encoding UL148-marker expression. 7. The method of claim 1 wherein the UL148-marker expression is induced by the cells being treated with an antibiotic. 8. The method of claim 1 further comprising adding marker to the cells. 9. The method of claim 1 wherein the cells are mutated to express UL148-marker upon inducement. 10. A kit to conduct the method of claim 1. | 1,600 |
347,207 | 16,805,648 | 1,648 | Methods, systems, and devices for wireless communications are described. One method may include transmitting a first signal instructing a user equipment (UE) to transition a state of a secondary cell associated with the UE; determining an allocation of resources for the UE to communicate with the secondary cell; and transmitting a second signal including an indication of an active bandwidth part (BWP) used for the allocation of resources based on the determining. The active BWP and the first signal may indicate the transition of the state of the secondary cell. | 1. A method for wireless communications, comprising:
configuring a state of a secondary cell associated with a group of secondary cells; configuring in a message a bitmap comprising an indication of the state of the secondary cell; and transmitting the message including the bitmap comprising the indication of the state of the secondary cell. 2. The method of claim 1, wherein configuring the state of the secondary cell associated with the group of secondary cells comprises:
configuring the secondary cell associated with the group of secondary cells to be in a partially activated state based at least in part on an active bandwidth part comprising a zero bandwidth part, wherein the partially activated state comprises a dormant state. 3. The method of claim 2, wherein configuring the state of the secondary cell associated with the group of secondary cells comprises:
configuring the secondary cell associated with the group of secondary cells to switch to a fully activated state from the partially activated state based at least in part on a second indication in the message. 4. The method of claim 1, wherein configuring the state of the secondary cell associated with the group of secondary cells comprises:
configuring the secondary cell associated with the group of secondary cells to be in a fully activated state based at least in part on an active bandwidth part comprising a non-zero bandwidth part. 5. The method of claim 1, further comprising:
transmitting, via the secondary cell, a second indication in the message to switch the secondary cell to a zero bandwidth part. 6. The method of claim 5, wherein the second indication comprises a carrier indicator field. 7. The method of claim 1, wherein configuring the state of the secondary cell associated with the group of secondary cells comprises:
configuring the secondary cell associated with the group of secondary cells to switch to a default bandwidth part comprising a zero-bandwidth part based at least in part on a bandwidth timer expiring. 8. The method of claim 1, further comprising:
transmitting, via downlink control signaling, the message including the bitmap comprising the indication of the state of the secondary cell associated with the group of secondary cells, wherein the message comprises a downlink control information message. 9. The method of claim 1, further comprising:
transmitting, via higher layer signaling, the message including the bitmap comprising the indication of the state of the secondary cell associated with the group of secondary cells, wherein the higher layer signaling comprises radio resource control signaling or medium access control-control element signaling. 10. The method of claim 1, further comprising:
identifying a set of bits associated with the bitmap in the message, the bitmap comprising the set of bits to indicate states of secondary cells associated with the group of secondary cells, wherein a presence of the bitmap in the message is determined based at least in part on a zero-resource assignment or a dummy grant for resource allocation. 11. The method of claim 10, further comprising:
receiving a feedback message comprising an indication of a decoding result of the transmitted message, wherein the feedback message comprises an acknowledgement message or a non-acknowledgement message. 12. The method of claim 1, wherein the message comprises a downlink control information message corresponding to a downlink control information format comprising a bandwidth part identifier indicating a target bandwidth part identifier associated with a primary cell and a number of fields for a downlink grant, wherein at least one field of the number of fields comprises the bitmap indicating the state of the secondary cell associated with the group of secondary cells. 13. The method of claim 1, wherein the message comprises bandwidth part activation control information for the secondary cell associated with the group of secondary cells. 14. The method of claim 1, wherein the state comprises a fully activated state, a partially activated state, or a fully deactivated state. 15. The method of claim 1, wherein the message comprises a bandwidth part downlink control information message. 16. A method for wireless communications, comprising:
receiving a message including a bitmap comprising an indication of a state of a secondary cell associated with a group of secondary cells; identifying the state of the secondary cell based at least in part on the indication in the received message; and switching the state of the secondary cell based at least in part on the identifying. 17. The method of claim 16, wherein switching the state of the secondary cell comprise:
switching the state of the secondary cell associated with the group of secondary cells to a partially activated state based at least in part on an active bandwidth part comprising a zero bandwidth part, wherein the partially activated state comprises a dormant state. 18. The method of claim 16, wherein switching the state of the secondary cell comprise:
switching the state of the secondary cell associated with the group of secondary cells to a fully activated state based at least in part on an active bandwidth part comprising a non-zero bandwidth part, wherein the fully activated state comprises a non-dormant state. 19. The method of claim 16, further comprising:
receiving, via the secondary cell, a second indication in the message to switch the secondary cell to a zero bandwidth part, the second indication comprising a carrier indicator field, wherein switching the state of the secondary cell comprises: switching the state of the secondary cell associated with the group of secondary cells to a fully activated state from a partially activated state based at least in part on the second indication. 20. The method of claim 16, wherein receiving the message comprises:
receiving, via downlink control signaling, the message including the bitmap comprising the indication of the state of the secondary cell associated with the group of secondary cells, wherein the message comprises a downlink control information message. 21. The method of claim 16, wherein receiving the message comprises:
receiving, via higher layer signaling, the message including the bitmap comprising the indication of the state of the secondary cell associated with the group of secondary cells, wherein the higher layer signaling comprises radio resource control signaling or medium access control-control element signaling. 22. The method of claim 16, further comprising:
determining a presence of the bitmap in the received message based at least in part on a zero-resource assignment or a dummy grant for resource allocation; and identifying a set of bits associated with the bitmap in the message, the bitmap comprising the set of bits to indicate states of secondary cells associated with the group of secondary cells. 23. The method of claim 16, further comprising:
determining that the state of the secondary cell is in a dormant state; and refraining from monitoring a control channel on the secondary cell based at least in part on the state of the secondary cell being in the dormant state, wherein the control channel comprises a physical downlink control channel. 24. The method of claim 16, further comprising:
transmitting a feedback message comprising an indication of a decoding result of the transmitted message, wherein the feedback message comprises an acknowledgement message or a non-acknowledgement message. 25. The method of claim 16, wherein the message comprises a downlink control information message corresponding to a downlink control information format comprising a bandwidth part identifier indicating a target bandwidth part identifier associated with a primary cell and a number of fields for a downlink grant, wherein at least one field of the number of fields comprises the bitmap indicating the state of the secondary cell associated with the group of secondary cells. 26. The method of claim 16, wherein the message comprises bandwidth part activation control information for the secondary cell associated with the group of secondary cells. 27. The method of claim 16, wherein the state comprises a fully activated state, a partially activated, a partially deactivated state, or a fully deactivated state. 28. The method of claim 16, wherein the message comprises a bandwidth part downlink control information message. 29. An apparatus for wireless communications, comprising:
a processor, memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to:
configure a state of a secondary cell associated with a group of secondary cells;
configure in a message a bitmap comprising an indication of the state of the secondary cell; and
transmit the message including the bitmap comprising the indication of the state of the secondary cell. 30. An apparatus for wireless communications, comprising:
a processor, memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to:
receive a message including a bitmap comprising an indication of a state of a secondary cell associated with a group of secondary cells;
identify the state of the secondary cell based at least in part on the indication in the received message; and
switch the state of the secondary cell based at least in part on the identifying. | Methods, systems, and devices for wireless communications are described. One method may include transmitting a first signal instructing a user equipment (UE) to transition a state of a secondary cell associated with the UE; determining an allocation of resources for the UE to communicate with the secondary cell; and transmitting a second signal including an indication of an active bandwidth part (BWP) used for the allocation of resources based on the determining. The active BWP and the first signal may indicate the transition of the state of the secondary cell.1. A method for wireless communications, comprising:
configuring a state of a secondary cell associated with a group of secondary cells; configuring in a message a bitmap comprising an indication of the state of the secondary cell; and transmitting the message including the bitmap comprising the indication of the state of the secondary cell. 2. The method of claim 1, wherein configuring the state of the secondary cell associated with the group of secondary cells comprises:
configuring the secondary cell associated with the group of secondary cells to be in a partially activated state based at least in part on an active bandwidth part comprising a zero bandwidth part, wherein the partially activated state comprises a dormant state. 3. The method of claim 2, wherein configuring the state of the secondary cell associated with the group of secondary cells comprises:
configuring the secondary cell associated with the group of secondary cells to switch to a fully activated state from the partially activated state based at least in part on a second indication in the message. 4. The method of claim 1, wherein configuring the state of the secondary cell associated with the group of secondary cells comprises:
configuring the secondary cell associated with the group of secondary cells to be in a fully activated state based at least in part on an active bandwidth part comprising a non-zero bandwidth part. 5. The method of claim 1, further comprising:
transmitting, via the secondary cell, a second indication in the message to switch the secondary cell to a zero bandwidth part. 6. The method of claim 5, wherein the second indication comprises a carrier indicator field. 7. The method of claim 1, wherein configuring the state of the secondary cell associated with the group of secondary cells comprises:
configuring the secondary cell associated with the group of secondary cells to switch to a default bandwidth part comprising a zero-bandwidth part based at least in part on a bandwidth timer expiring. 8. The method of claim 1, further comprising:
transmitting, via downlink control signaling, the message including the bitmap comprising the indication of the state of the secondary cell associated with the group of secondary cells, wherein the message comprises a downlink control information message. 9. The method of claim 1, further comprising:
transmitting, via higher layer signaling, the message including the bitmap comprising the indication of the state of the secondary cell associated with the group of secondary cells, wherein the higher layer signaling comprises radio resource control signaling or medium access control-control element signaling. 10. The method of claim 1, further comprising:
identifying a set of bits associated with the bitmap in the message, the bitmap comprising the set of bits to indicate states of secondary cells associated with the group of secondary cells, wherein a presence of the bitmap in the message is determined based at least in part on a zero-resource assignment or a dummy grant for resource allocation. 11. The method of claim 10, further comprising:
receiving a feedback message comprising an indication of a decoding result of the transmitted message, wherein the feedback message comprises an acknowledgement message or a non-acknowledgement message. 12. The method of claim 1, wherein the message comprises a downlink control information message corresponding to a downlink control information format comprising a bandwidth part identifier indicating a target bandwidth part identifier associated with a primary cell and a number of fields for a downlink grant, wherein at least one field of the number of fields comprises the bitmap indicating the state of the secondary cell associated with the group of secondary cells. 13. The method of claim 1, wherein the message comprises bandwidth part activation control information for the secondary cell associated with the group of secondary cells. 14. The method of claim 1, wherein the state comprises a fully activated state, a partially activated state, or a fully deactivated state. 15. The method of claim 1, wherein the message comprises a bandwidth part downlink control information message. 16. A method for wireless communications, comprising:
receiving a message including a bitmap comprising an indication of a state of a secondary cell associated with a group of secondary cells; identifying the state of the secondary cell based at least in part on the indication in the received message; and switching the state of the secondary cell based at least in part on the identifying. 17. The method of claim 16, wherein switching the state of the secondary cell comprise:
switching the state of the secondary cell associated with the group of secondary cells to a partially activated state based at least in part on an active bandwidth part comprising a zero bandwidth part, wherein the partially activated state comprises a dormant state. 18. The method of claim 16, wherein switching the state of the secondary cell comprise:
switching the state of the secondary cell associated with the group of secondary cells to a fully activated state based at least in part on an active bandwidth part comprising a non-zero bandwidth part, wherein the fully activated state comprises a non-dormant state. 19. The method of claim 16, further comprising:
receiving, via the secondary cell, a second indication in the message to switch the secondary cell to a zero bandwidth part, the second indication comprising a carrier indicator field, wherein switching the state of the secondary cell comprises: switching the state of the secondary cell associated with the group of secondary cells to a fully activated state from a partially activated state based at least in part on the second indication. 20. The method of claim 16, wherein receiving the message comprises:
receiving, via downlink control signaling, the message including the bitmap comprising the indication of the state of the secondary cell associated with the group of secondary cells, wherein the message comprises a downlink control information message. 21. The method of claim 16, wherein receiving the message comprises:
receiving, via higher layer signaling, the message including the bitmap comprising the indication of the state of the secondary cell associated with the group of secondary cells, wherein the higher layer signaling comprises radio resource control signaling or medium access control-control element signaling. 22. The method of claim 16, further comprising:
determining a presence of the bitmap in the received message based at least in part on a zero-resource assignment or a dummy grant for resource allocation; and identifying a set of bits associated with the bitmap in the message, the bitmap comprising the set of bits to indicate states of secondary cells associated with the group of secondary cells. 23. The method of claim 16, further comprising:
determining that the state of the secondary cell is in a dormant state; and refraining from monitoring a control channel on the secondary cell based at least in part on the state of the secondary cell being in the dormant state, wherein the control channel comprises a physical downlink control channel. 24. The method of claim 16, further comprising:
transmitting a feedback message comprising an indication of a decoding result of the transmitted message, wherein the feedback message comprises an acknowledgement message or a non-acknowledgement message. 25. The method of claim 16, wherein the message comprises a downlink control information message corresponding to a downlink control information format comprising a bandwidth part identifier indicating a target bandwidth part identifier associated with a primary cell and a number of fields for a downlink grant, wherein at least one field of the number of fields comprises the bitmap indicating the state of the secondary cell associated with the group of secondary cells. 26. The method of claim 16, wherein the message comprises bandwidth part activation control information for the secondary cell associated with the group of secondary cells. 27. The method of claim 16, wherein the state comprises a fully activated state, a partially activated, a partially deactivated state, or a fully deactivated state. 28. The method of claim 16, wherein the message comprises a bandwidth part downlink control information message. 29. An apparatus for wireless communications, comprising:
a processor, memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to:
configure a state of a secondary cell associated with a group of secondary cells;
configure in a message a bitmap comprising an indication of the state of the secondary cell; and
transmit the message including the bitmap comprising the indication of the state of the secondary cell. 30. An apparatus for wireless communications, comprising:
a processor, memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to:
receive a message including a bitmap comprising an indication of a state of a secondary cell associated with a group of secondary cells;
identify the state of the secondary cell based at least in part on the indication in the received message; and
switch the state of the secondary cell based at least in part on the identifying. | 1,600 |
347,208 | 16,805,683 | 1,648 | A trial operations service suite system and method in a clinical trial operations system with a patient portal providing patient-directed access to clinical trial operation services, a clinician portal providing clinician-directed access to the clinical trial operation service, and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure, and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. | 1. A trial operations service suite in a clinical trial operations system, comprising:
a patient portal providing patient-directed access to clinical trial operation services; a clinician portal providing clinician-directed access to the clinical trial operation services; and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure; and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. 2. The trial operations service suite of claim 1, wherein the synchronization service synchronizes information between the clinician portal and a clinician application when the clinician application is online to the server. 3. A user application in a clinical trial operations system, comprising:
a user interface and network interface modules; user enrollment, user notification, user secure communication, user engagement, and user data capture service modules; and an offline portal proxy providing an offline portal service and data caches, allowing the user application to continue operating when offline from a server running a clinical trial operations service suite; and a synchronization capability, synchronizing information between the user application offline portal proxy and the clinical trial operations service suite when online with the server. 4. The user application of claim 3, further comprising:
a health monitoring sensor adapted for sensing a patient's health, wherein the user application is a patient application running on a patient-located computer; the offline portal proxies a patient portal of the clinical trial operations service suite, the proxied patient portal comprising:
a patient logon screen for a clinical trial;
a patient enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of an online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied patient portal is saved for online synchronization with the clinical trial operation service suite. 5. The user application of claim 4, wherein:
the user application is a clinician application running on a clinician-located computer; the offline portal proxies a clinician portal of the clinical trial operations service suite, the proxied clinician portal comprising:
a clinician logon screen for a clinical trial;
a clinician enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial, and a tracking status of the invite;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of the online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied clinician portal is saved for online synchronization with the clinical trial operation service suite. 6. The user application of claim 4, further comprising, a display of at least one of a patient survey query, a schedule of patient events, and a patient-recorded record of observations. 7. The user application of claim 4, wherein the online synchronization includes data from the health monitoring sensor. 8. The user application of claim 5, further comprising, a display of at least one of a screen allowing a clinician to compose and send a notification, a clinician survey query, a schedule of clinician events, and a clinician-recorded record of observations. 9. The user application of claim 5, further comprising, a health sensor operated by the clinician, wherein online synchronization includes data from the clinician's health sensor. 10. A method of operating a trial operations service suite in a clinical trial operations system, comprising:
running a trial operations service suite software on a computer; communicating with a user application running on a user device; displaying at least one of a service screen and user interface on the user device, the user interface querying for user input information for use in a clinical trial; receiving the user input on the user device; and synchronizing, when online with the computer, service suite information, service screen logic and user input information, collected by the user application when the user application was offline from the computer. 11. The method of claim 10, further comprising, when a data conflict arises during synchronization, wherein data changed in the user application while offline conflicts with data that has changed in the service suite since a previous synchronization, the service suite assumes the new data overrides the old data and continues synchronizing. 12. The method of claim 11, further comprising, the service suite notifying a coordinator to manually resolve the data conflict. 13. The method of claim 11, further comprising, resolving the conflict autonomously via an analytic module associated with the service suite. 14. The method of claim 10, wherein the user application is a patient application and the service suite provides a patient portal. 15. The method of claim 10, wherein the user application is a clinician application and the service suite provides a clinician portal. 16. A method of operating an application in a clinical trial operations system, comprising:
when the application is connected to a portal of a trial operations service suite, synchronizing portal and application data, service screens and logic, and data collected by the application while not connected; and when the application is not connected to the portal, using a proxy embedded in the application to continue providing service and collecting data according to a previously synchronized portal data, service screens, and service logic. 17. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in a cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with a cached service logic, the proxy stops supporting the service while offline. 18. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in the cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with the cached service logic, the proxy assumes the new data overrides the old data and continues supporting the service while offline. 19. The method of claim 16, wherein the application is a patient application and the portal is a patient portal. 20. The method of claim 16, wherein the application is a clinician application and the portal is a clinician portal. | A trial operations service suite system and method in a clinical trial operations system with a patient portal providing patient-directed access to clinical trial operation services, a clinician portal providing clinician-directed access to the clinical trial operation service, and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure, and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline.1. A trial operations service suite in a clinical trial operations system, comprising:
a patient portal providing patient-directed access to clinical trial operation services; a clinician portal providing clinician-directed access to the clinical trial operation services; and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure; and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. 2. The trial operations service suite of claim 1, wherein the synchronization service synchronizes information between the clinician portal and a clinician application when the clinician application is online to the server. 3. A user application in a clinical trial operations system, comprising:
a user interface and network interface modules; user enrollment, user notification, user secure communication, user engagement, and user data capture service modules; and an offline portal proxy providing an offline portal service and data caches, allowing the user application to continue operating when offline from a server running a clinical trial operations service suite; and a synchronization capability, synchronizing information between the user application offline portal proxy and the clinical trial operations service suite when online with the server. 4. The user application of claim 3, further comprising:
a health monitoring sensor adapted for sensing a patient's health, wherein the user application is a patient application running on a patient-located computer; the offline portal proxies a patient portal of the clinical trial operations service suite, the proxied patient portal comprising:
a patient logon screen for a clinical trial;
a patient enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of an online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied patient portal is saved for online synchronization with the clinical trial operation service suite. 5. The user application of claim 4, wherein:
the user application is a clinician application running on a clinician-located computer; the offline portal proxies a clinician portal of the clinical trial operations service suite, the proxied clinician portal comprising:
a clinician logon screen for a clinical trial;
a clinician enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial, and a tracking status of the invite;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of the online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied clinician portal is saved for online synchronization with the clinical trial operation service suite. 6. The user application of claim 4, further comprising, a display of at least one of a patient survey query, a schedule of patient events, and a patient-recorded record of observations. 7. The user application of claim 4, wherein the online synchronization includes data from the health monitoring sensor. 8. The user application of claim 5, further comprising, a display of at least one of a screen allowing a clinician to compose and send a notification, a clinician survey query, a schedule of clinician events, and a clinician-recorded record of observations. 9. The user application of claim 5, further comprising, a health sensor operated by the clinician, wherein online synchronization includes data from the clinician's health sensor. 10. A method of operating a trial operations service suite in a clinical trial operations system, comprising:
running a trial operations service suite software on a computer; communicating with a user application running on a user device; displaying at least one of a service screen and user interface on the user device, the user interface querying for user input information for use in a clinical trial; receiving the user input on the user device; and synchronizing, when online with the computer, service suite information, service screen logic and user input information, collected by the user application when the user application was offline from the computer. 11. The method of claim 10, further comprising, when a data conflict arises during synchronization, wherein data changed in the user application while offline conflicts with data that has changed in the service suite since a previous synchronization, the service suite assumes the new data overrides the old data and continues synchronizing. 12. The method of claim 11, further comprising, the service suite notifying a coordinator to manually resolve the data conflict. 13. The method of claim 11, further comprising, resolving the conflict autonomously via an analytic module associated with the service suite. 14. The method of claim 10, wherein the user application is a patient application and the service suite provides a patient portal. 15. The method of claim 10, wherein the user application is a clinician application and the service suite provides a clinician portal. 16. A method of operating an application in a clinical trial operations system, comprising:
when the application is connected to a portal of a trial operations service suite, synchronizing portal and application data, service screens and logic, and data collected by the application while not connected; and when the application is not connected to the portal, using a proxy embedded in the application to continue providing service and collecting data according to a previously synchronized portal data, service screens, and service logic. 17. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in a cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with a cached service logic, the proxy stops supporting the service while offline. 18. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in the cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with the cached service logic, the proxy assumes the new data overrides the old data and continues supporting the service while offline. 19. The method of claim 16, wherein the application is a patient application and the portal is a patient portal. 20. The method of claim 16, wherein the application is a clinician application and the portal is a clinician portal. | 1,600 |
347,209 | 16,805,677 | 1,648 | A trial operations service suite system and method in a clinical trial operations system with a patient portal providing patient-directed access to clinical trial operation services, a clinician portal providing clinician-directed access to the clinical trial operation service, and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure, and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. | 1. A trial operations service suite in a clinical trial operations system, comprising:
a patient portal providing patient-directed access to clinical trial operation services; a clinician portal providing clinician-directed access to the clinical trial operation services; and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure; and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. 2. The trial operations service suite of claim 1, wherein the synchronization service synchronizes information between the clinician portal and a clinician application when the clinician application is online to the server. 3. A user application in a clinical trial operations system, comprising:
a user interface and network interface modules; user enrollment, user notification, user secure communication, user engagement, and user data capture service modules; and an offline portal proxy providing an offline portal service and data caches, allowing the user application to continue operating when offline from a server running a clinical trial operations service suite; and a synchronization capability, synchronizing information between the user application offline portal proxy and the clinical trial operations service suite when online with the server. 4. The user application of claim 3, further comprising:
a health monitoring sensor adapted for sensing a patient's health, wherein the user application is a patient application running on a patient-located computer; the offline portal proxies a patient portal of the clinical trial operations service suite, the proxied patient portal comprising:
a patient logon screen for a clinical trial;
a patient enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of an online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied patient portal is saved for online synchronization with the clinical trial operation service suite. 5. The user application of claim 4, wherein:
the user application is a clinician application running on a clinician-located computer; the offline portal proxies a clinician portal of the clinical trial operations service suite, the proxied clinician portal comprising:
a clinician logon screen for a clinical trial;
a clinician enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial, and a tracking status of the invite;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of the online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied clinician portal is saved for online synchronization with the clinical trial operation service suite. 6. The user application of claim 4, further comprising, a display of at least one of a patient survey query, a schedule of patient events, and a patient-recorded record of observations. 7. The user application of claim 4, wherein the online synchronization includes data from the health monitoring sensor. 8. The user application of claim 5, further comprising, a display of at least one of a screen allowing a clinician to compose and send a notification, a clinician survey query, a schedule of clinician events, and a clinician-recorded record of observations. 9. The user application of claim 5, further comprising, a health sensor operated by the clinician, wherein online synchronization includes data from the clinician's health sensor. 10. A method of operating a trial operations service suite in a clinical trial operations system, comprising:
running a trial operations service suite software on a computer; communicating with a user application running on a user device; displaying at least one of a service screen and user interface on the user device, the user interface querying for user input information for use in a clinical trial; receiving the user input on the user device; and synchronizing, when online with the computer, service suite information, service screen logic and user input information, collected by the user application when the user application was offline from the computer. 11. The method of claim 10, further comprising, when a data conflict arises during synchronization, wherein data changed in the user application while offline conflicts with data that has changed in the service suite since a previous synchronization, the service suite assumes the new data overrides the old data and continues synchronizing. 12. The method of claim 11, further comprising, the service suite notifying a coordinator to manually resolve the data conflict. 13. The method of claim 11, further comprising, resolving the conflict autonomously via an analytic module associated with the service suite. 14. The method of claim 10, wherein the user application is a patient application and the service suite provides a patient portal. 15. The method of claim 10, wherein the user application is a clinician application and the service suite provides a clinician portal. 16. A method of operating an application in a clinical trial operations system, comprising:
when the application is connected to a portal of a trial operations service suite, synchronizing portal and application data, service screens and logic, and data collected by the application while not connected; and when the application is not connected to the portal, using a proxy embedded in the application to continue providing service and collecting data according to a previously synchronized portal data, service screens, and service logic. 17. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in a cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with a cached service logic, the proxy stops supporting the service while offline. 18. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in the cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with the cached service logic, the proxy assumes the new data overrides the old data and continues supporting the service while offline. 19. The method of claim 16, wherein the application is a patient application and the portal is a patient portal. 20. The method of claim 16, wherein the application is a clinician application and the portal is a clinician portal. | A trial operations service suite system and method in a clinical trial operations system with a patient portal providing patient-directed access to clinical trial operation services, a clinician portal providing clinician-directed access to the clinical trial operation service, and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure, and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline.1. A trial operations service suite in a clinical trial operations system, comprising:
a patient portal providing patient-directed access to clinical trial operation services; a clinician portal providing clinician-directed access to the clinical trial operation services; and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure; and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. 2. The trial operations service suite of claim 1, wherein the synchronization service synchronizes information between the clinician portal and a clinician application when the clinician application is online to the server. 3. A user application in a clinical trial operations system, comprising:
a user interface and network interface modules; user enrollment, user notification, user secure communication, user engagement, and user data capture service modules; and an offline portal proxy providing an offline portal service and data caches, allowing the user application to continue operating when offline from a server running a clinical trial operations service suite; and a synchronization capability, synchronizing information between the user application offline portal proxy and the clinical trial operations service suite when online with the server. 4. The user application of claim 3, further comprising:
a health monitoring sensor adapted for sensing a patient's health, wherein the user application is a patient application running on a patient-located computer; the offline portal proxies a patient portal of the clinical trial operations service suite, the proxied patient portal comprising:
a patient logon screen for a clinical trial;
a patient enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of an online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied patient portal is saved for online synchronization with the clinical trial operation service suite. 5. The user application of claim 4, wherein:
the user application is a clinician application running on a clinician-located computer; the offline portal proxies a clinician portal of the clinical trial operations service suite, the proxied clinician portal comprising:
a clinician logon screen for a clinical trial;
a clinician enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial, and a tracking status of the invite;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of the online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied clinician portal is saved for online synchronization with the clinical trial operation service suite. 6. The user application of claim 4, further comprising, a display of at least one of a patient survey query, a schedule of patient events, and a patient-recorded record of observations. 7. The user application of claim 4, wherein the online synchronization includes data from the health monitoring sensor. 8. The user application of claim 5, further comprising, a display of at least one of a screen allowing a clinician to compose and send a notification, a clinician survey query, a schedule of clinician events, and a clinician-recorded record of observations. 9. The user application of claim 5, further comprising, a health sensor operated by the clinician, wherein online synchronization includes data from the clinician's health sensor. 10. A method of operating a trial operations service suite in a clinical trial operations system, comprising:
running a trial operations service suite software on a computer; communicating with a user application running on a user device; displaying at least one of a service screen and user interface on the user device, the user interface querying for user input information for use in a clinical trial; receiving the user input on the user device; and synchronizing, when online with the computer, service suite information, service screen logic and user input information, collected by the user application when the user application was offline from the computer. 11. The method of claim 10, further comprising, when a data conflict arises during synchronization, wherein data changed in the user application while offline conflicts with data that has changed in the service suite since a previous synchronization, the service suite assumes the new data overrides the old data and continues synchronizing. 12. The method of claim 11, further comprising, the service suite notifying a coordinator to manually resolve the data conflict. 13. The method of claim 11, further comprising, resolving the conflict autonomously via an analytic module associated with the service suite. 14. The method of claim 10, wherein the user application is a patient application and the service suite provides a patient portal. 15. The method of claim 10, wherein the user application is a clinician application and the service suite provides a clinician portal. 16. A method of operating an application in a clinical trial operations system, comprising:
when the application is connected to a portal of a trial operations service suite, synchronizing portal and application data, service screens and logic, and data collected by the application while not connected; and when the application is not connected to the portal, using a proxy embedded in the application to continue providing service and collecting data according to a previously synchronized portal data, service screens, and service logic. 17. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in a cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with a cached service logic, the proxy stops supporting the service while offline. 18. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in the cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with the cached service logic, the proxy assumes the new data overrides the old data and continues supporting the service while offline. 19. The method of claim 16, wherein the application is a patient application and the portal is a patient portal. 20. The method of claim 16, wherein the application is a clinician application and the portal is a clinician portal. | 1,600 |
347,210 | 29,725,982 | 2,918 | A trial operations service suite system and method in a clinical trial operations system with a patient portal providing patient-directed access to clinical trial operation services, a clinician portal providing clinician-directed access to the clinical trial operation service, and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure, and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. | 1. A trial operations service suite in a clinical trial operations system, comprising:
a patient portal providing patient-directed access to clinical trial operation services; a clinician portal providing clinician-directed access to the clinical trial operation services; and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure; and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. 2. The trial operations service suite of claim 1, wherein the synchronization service synchronizes information between the clinician portal and a clinician application when the clinician application is online to the server. 3. A user application in a clinical trial operations system, comprising:
a user interface and network interface modules; user enrollment, user notification, user secure communication, user engagement, and user data capture service modules; and an offline portal proxy providing an offline portal service and data caches, allowing the user application to continue operating when offline from a server running a clinical trial operations service suite; and a synchronization capability, synchronizing information between the user application offline portal proxy and the clinical trial operations service suite when online with the server. 4. The user application of claim 3, further comprising:
a health monitoring sensor adapted for sensing a patient's health, wherein the user application is a patient application running on a patient-located computer; the offline portal proxies a patient portal of the clinical trial operations service suite, the proxied patient portal comprising:
a patient logon screen for a clinical trial;
a patient enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of an online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied patient portal is saved for online synchronization with the clinical trial operation service suite. 5. The user application of claim 4, wherein:
the user application is a clinician application running on a clinician-located computer; the offline portal proxies a clinician portal of the clinical trial operations service suite, the proxied clinician portal comprising:
a clinician logon screen for a clinical trial;
a clinician enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial, and a tracking status of the invite;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of the online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied clinician portal is saved for online synchronization with the clinical trial operation service suite. 6. The user application of claim 4, further comprising, a display of at least one of a patient survey query, a schedule of patient events, and a patient-recorded record of observations. 7. The user application of claim 4, wherein the online synchronization includes data from the health monitoring sensor. 8. The user application of claim 5, further comprising, a display of at least one of a screen allowing a clinician to compose and send a notification, a clinician survey query, a schedule of clinician events, and a clinician-recorded record of observations. 9. The user application of claim 5, further comprising, a health sensor operated by the clinician, wherein online synchronization includes data from the clinician's health sensor. 10. A method of operating a trial operations service suite in a clinical trial operations system, comprising:
running a trial operations service suite software on a computer; communicating with a user application running on a user device; displaying at least one of a service screen and user interface on the user device, the user interface querying for user input information for use in a clinical trial; receiving the user input on the user device; and synchronizing, when online with the computer, service suite information, service screen logic and user input information, collected by the user application when the user application was offline from the computer. 11. The method of claim 10, further comprising, when a data conflict arises during synchronization, wherein data changed in the user application while offline conflicts with data that has changed in the service suite since a previous synchronization, the service suite assumes the new data overrides the old data and continues synchronizing. 12. The method of claim 11, further comprising, the service suite notifying a coordinator to manually resolve the data conflict. 13. The method of claim 11, further comprising, resolving the conflict autonomously via an analytic module associated with the service suite. 14. The method of claim 10, wherein the user application is a patient application and the service suite provides a patient portal. 15. The method of claim 10, wherein the user application is a clinician application and the service suite provides a clinician portal. 16. A method of operating an application in a clinical trial operations system, comprising:
when the application is connected to a portal of a trial operations service suite, synchronizing portal and application data, service screens and logic, and data collected by the application while not connected; and when the application is not connected to the portal, using a proxy embedded in the application to continue providing service and collecting data according to a previously synchronized portal data, service screens, and service logic. 17. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in a cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with a cached service logic, the proxy stops supporting the service while offline. 18. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in the cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with the cached service logic, the proxy assumes the new data overrides the old data and continues supporting the service while offline. 19. The method of claim 16, wherein the application is a patient application and the portal is a patient portal. 20. The method of claim 16, wherein the application is a clinician application and the portal is a clinician portal. | A trial operations service suite system and method in a clinical trial operations system with a patient portal providing patient-directed access to clinical trial operation services, a clinician portal providing clinician-directed access to the clinical trial operation service, and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure, and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline.1. A trial operations service suite in a clinical trial operations system, comprising:
a patient portal providing patient-directed access to clinical trial operation services; a clinician portal providing clinician-directed access to the clinical trial operation services; and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure; and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. 2. The trial operations service suite of claim 1, wherein the synchronization service synchronizes information between the clinician portal and a clinician application when the clinician application is online to the server. 3. A user application in a clinical trial operations system, comprising:
a user interface and network interface modules; user enrollment, user notification, user secure communication, user engagement, and user data capture service modules; and an offline portal proxy providing an offline portal service and data caches, allowing the user application to continue operating when offline from a server running a clinical trial operations service suite; and a synchronization capability, synchronizing information between the user application offline portal proxy and the clinical trial operations service suite when online with the server. 4. The user application of claim 3, further comprising:
a health monitoring sensor adapted for sensing a patient's health, wherein the user application is a patient application running on a patient-located computer; the offline portal proxies a patient portal of the clinical trial operations service suite, the proxied patient portal comprising:
a patient logon screen for a clinical trial;
a patient enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of an online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied patient portal is saved for online synchronization with the clinical trial operation service suite. 5. The user application of claim 4, wherein:
the user application is a clinician application running on a clinician-located computer; the offline portal proxies a clinician portal of the clinical trial operations service suite, the proxied clinician portal comprising:
a clinician logon screen for a clinical trial;
a clinician enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial, and a tracking status of the invite;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of the online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied clinician portal is saved for online synchronization with the clinical trial operation service suite. 6. The user application of claim 4, further comprising, a display of at least one of a patient survey query, a schedule of patient events, and a patient-recorded record of observations. 7. The user application of claim 4, wherein the online synchronization includes data from the health monitoring sensor. 8. The user application of claim 5, further comprising, a display of at least one of a screen allowing a clinician to compose and send a notification, a clinician survey query, a schedule of clinician events, and a clinician-recorded record of observations. 9. The user application of claim 5, further comprising, a health sensor operated by the clinician, wherein online synchronization includes data from the clinician's health sensor. 10. A method of operating a trial operations service suite in a clinical trial operations system, comprising:
running a trial operations service suite software on a computer; communicating with a user application running on a user device; displaying at least one of a service screen and user interface on the user device, the user interface querying for user input information for use in a clinical trial; receiving the user input on the user device; and synchronizing, when online with the computer, service suite information, service screen logic and user input information, collected by the user application when the user application was offline from the computer. 11. The method of claim 10, further comprising, when a data conflict arises during synchronization, wherein data changed in the user application while offline conflicts with data that has changed in the service suite since a previous synchronization, the service suite assumes the new data overrides the old data and continues synchronizing. 12. The method of claim 11, further comprising, the service suite notifying a coordinator to manually resolve the data conflict. 13. The method of claim 11, further comprising, resolving the conflict autonomously via an analytic module associated with the service suite. 14. The method of claim 10, wherein the user application is a patient application and the service suite provides a patient portal. 15. The method of claim 10, wherein the user application is a clinician application and the service suite provides a clinician portal. 16. A method of operating an application in a clinical trial operations system, comprising:
when the application is connected to a portal of a trial operations service suite, synchronizing portal and application data, service screens and logic, and data collected by the application while not connected; and when the application is not connected to the portal, using a proxy embedded in the application to continue providing service and collecting data according to a previously synchronized portal data, service screens, and service logic. 17. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in a cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with a cached service logic, the proxy stops supporting the service while offline. 18. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in the cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with the cached service logic, the proxy assumes the new data overrides the old data and continues supporting the service while offline. 19. The method of claim 16, wherein the application is a patient application and the portal is a patient portal. 20. The method of claim 16, wherein the application is a clinician application and the portal is a clinician portal. | 2,900 |
347,211 | 29,725,961 | 2,918 | A trial operations service suite system and method in a clinical trial operations system with a patient portal providing patient-directed access to clinical trial operation services, a clinician portal providing clinician-directed access to the clinical trial operation service, and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure, and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. | 1. A trial operations service suite in a clinical trial operations system, comprising:
a patient portal providing patient-directed access to clinical trial operation services; a clinician portal providing clinician-directed access to the clinical trial operation services; and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure; and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. 2. The trial operations service suite of claim 1, wherein the synchronization service synchronizes information between the clinician portal and a clinician application when the clinician application is online to the server. 3. A user application in a clinical trial operations system, comprising:
a user interface and network interface modules; user enrollment, user notification, user secure communication, user engagement, and user data capture service modules; and an offline portal proxy providing an offline portal service and data caches, allowing the user application to continue operating when offline from a server running a clinical trial operations service suite; and a synchronization capability, synchronizing information between the user application offline portal proxy and the clinical trial operations service suite when online with the server. 4. The user application of claim 3, further comprising:
a health monitoring sensor adapted for sensing a patient's health, wherein the user application is a patient application running on a patient-located computer; the offline portal proxies a patient portal of the clinical trial operations service suite, the proxied patient portal comprising:
a patient logon screen for a clinical trial;
a patient enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of an online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied patient portal is saved for online synchronization with the clinical trial operation service suite. 5. The user application of claim 4, wherein:
the user application is a clinician application running on a clinician-located computer; the offline portal proxies a clinician portal of the clinical trial operations service suite, the proxied clinician portal comprising:
a clinician logon screen for a clinical trial;
a clinician enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial, and a tracking status of the invite;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of the online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied clinician portal is saved for online synchronization with the clinical trial operation service suite. 6. The user application of claim 4, further comprising, a display of at least one of a patient survey query, a schedule of patient events, and a patient-recorded record of observations. 7. The user application of claim 4, wherein the online synchronization includes data from the health monitoring sensor. 8. The user application of claim 5, further comprising, a display of at least one of a screen allowing a clinician to compose and send a notification, a clinician survey query, a schedule of clinician events, and a clinician-recorded record of observations. 9. The user application of claim 5, further comprising, a health sensor operated by the clinician, wherein online synchronization includes data from the clinician's health sensor. 10. A method of operating a trial operations service suite in a clinical trial operations system, comprising:
running a trial operations service suite software on a computer; communicating with a user application running on a user device; displaying at least one of a service screen and user interface on the user device, the user interface querying for user input information for use in a clinical trial; receiving the user input on the user device; and synchronizing, when online with the computer, service suite information, service screen logic and user input information, collected by the user application when the user application was offline from the computer. 11. The method of claim 10, further comprising, when a data conflict arises during synchronization, wherein data changed in the user application while offline conflicts with data that has changed in the service suite since a previous synchronization, the service suite assumes the new data overrides the old data and continues synchronizing. 12. The method of claim 11, further comprising, the service suite notifying a coordinator to manually resolve the data conflict. 13. The method of claim 11, further comprising, resolving the conflict autonomously via an analytic module associated with the service suite. 14. The method of claim 10, wherein the user application is a patient application and the service suite provides a patient portal. 15. The method of claim 10, wherein the user application is a clinician application and the service suite provides a clinician portal. 16. A method of operating an application in a clinical trial operations system, comprising:
when the application is connected to a portal of a trial operations service suite, synchronizing portal and application data, service screens and logic, and data collected by the application while not connected; and when the application is not connected to the portal, using a proxy embedded in the application to continue providing service and collecting data according to a previously synchronized portal data, service screens, and service logic. 17. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in a cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with a cached service logic, the proxy stops supporting the service while offline. 18. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in the cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with the cached service logic, the proxy assumes the new data overrides the old data and continues supporting the service while offline. 19. The method of claim 16, wherein the application is a patient application and the portal is a patient portal. 20. The method of claim 16, wherein the application is a clinician application and the portal is a clinician portal. | A trial operations service suite system and method in a clinical trial operations system with a patient portal providing patient-directed access to clinical trial operation services, a clinician portal providing clinician-directed access to the clinical trial operation service, and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure, and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline.1. A trial operations service suite in a clinical trial operations system, comprising:
a patient portal providing patient-directed access to clinical trial operation services; a clinician portal providing clinician-directed access to the clinical trial operation services; and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure; and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. 2. The trial operations service suite of claim 1, wherein the synchronization service synchronizes information between the clinician portal and a clinician application when the clinician application is online to the server. 3. A user application in a clinical trial operations system, comprising:
a user interface and network interface modules; user enrollment, user notification, user secure communication, user engagement, and user data capture service modules; and an offline portal proxy providing an offline portal service and data caches, allowing the user application to continue operating when offline from a server running a clinical trial operations service suite; and a synchronization capability, synchronizing information between the user application offline portal proxy and the clinical trial operations service suite when online with the server. 4. The user application of claim 3, further comprising:
a health monitoring sensor adapted for sensing a patient's health, wherein the user application is a patient application running on a patient-located computer; the offline portal proxies a patient portal of the clinical trial operations service suite, the proxied patient portal comprising:
a patient logon screen for a clinical trial;
a patient enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of an online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied patient portal is saved for online synchronization with the clinical trial operation service suite. 5. The user application of claim 4, wherein:
the user application is a clinician application running on a clinician-located computer; the offline portal proxies a clinician portal of the clinical trial operations service suite, the proxied clinician portal comprising:
a clinician logon screen for a clinical trial;
a clinician enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial, and a tracking status of the invite;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of the online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied clinician portal is saved for online synchronization with the clinical trial operation service suite. 6. The user application of claim 4, further comprising, a display of at least one of a patient survey query, a schedule of patient events, and a patient-recorded record of observations. 7. The user application of claim 4, wherein the online synchronization includes data from the health monitoring sensor. 8. The user application of claim 5, further comprising, a display of at least one of a screen allowing a clinician to compose and send a notification, a clinician survey query, a schedule of clinician events, and a clinician-recorded record of observations. 9. The user application of claim 5, further comprising, a health sensor operated by the clinician, wherein online synchronization includes data from the clinician's health sensor. 10. A method of operating a trial operations service suite in a clinical trial operations system, comprising:
running a trial operations service suite software on a computer; communicating with a user application running on a user device; displaying at least one of a service screen and user interface on the user device, the user interface querying for user input information for use in a clinical trial; receiving the user input on the user device; and synchronizing, when online with the computer, service suite information, service screen logic and user input information, collected by the user application when the user application was offline from the computer. 11. The method of claim 10, further comprising, when a data conflict arises during synchronization, wherein data changed in the user application while offline conflicts with data that has changed in the service suite since a previous synchronization, the service suite assumes the new data overrides the old data and continues synchronizing. 12. The method of claim 11, further comprising, the service suite notifying a coordinator to manually resolve the data conflict. 13. The method of claim 11, further comprising, resolving the conflict autonomously via an analytic module associated with the service suite. 14. The method of claim 10, wherein the user application is a patient application and the service suite provides a patient portal. 15. The method of claim 10, wherein the user application is a clinician application and the service suite provides a clinician portal. 16. A method of operating an application in a clinical trial operations system, comprising:
when the application is connected to a portal of a trial operations service suite, synchronizing portal and application data, service screens and logic, and data collected by the application while not connected; and when the application is not connected to the portal, using a proxy embedded in the application to continue providing service and collecting data according to a previously synchronized portal data, service screens, and service logic. 17. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in a cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with a cached service logic, the proxy stops supporting the service while offline. 18. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in the cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with the cached service logic, the proxy assumes the new data overrides the old data and continues supporting the service while offline. 19. The method of claim 16, wherein the application is a patient application and the portal is a patient portal. 20. The method of claim 16, wherein the application is a clinician application and the portal is a clinician portal. | 2,900 |
347,212 | 29,725,990 | 2,918 | A trial operations service suite system and method in a clinical trial operations system with a patient portal providing patient-directed access to clinical trial operation services, a clinician portal providing clinician-directed access to the clinical trial operation service, and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure, and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. | 1. A trial operations service suite in a clinical trial operations system, comprising:
a patient portal providing patient-directed access to clinical trial operation services; a clinician portal providing clinician-directed access to the clinical trial operation services; and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure; and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. 2. The trial operations service suite of claim 1, wherein the synchronization service synchronizes information between the clinician portal and a clinician application when the clinician application is online to the server. 3. A user application in a clinical trial operations system, comprising:
a user interface and network interface modules; user enrollment, user notification, user secure communication, user engagement, and user data capture service modules; and an offline portal proxy providing an offline portal service and data caches, allowing the user application to continue operating when offline from a server running a clinical trial operations service suite; and a synchronization capability, synchronizing information between the user application offline portal proxy and the clinical trial operations service suite when online with the server. 4. The user application of claim 3, further comprising:
a health monitoring sensor adapted for sensing a patient's health, wherein the user application is a patient application running on a patient-located computer; the offline portal proxies a patient portal of the clinical trial operations service suite, the proxied patient portal comprising:
a patient logon screen for a clinical trial;
a patient enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of an online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied patient portal is saved for online synchronization with the clinical trial operation service suite. 5. The user application of claim 4, wherein:
the user application is a clinician application running on a clinician-located computer; the offline portal proxies a clinician portal of the clinical trial operations service suite, the proxied clinician portal comprising:
a clinician logon screen for a clinical trial;
a clinician enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial, and a tracking status of the invite;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of the online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied clinician portal is saved for online synchronization with the clinical trial operation service suite. 6. The user application of claim 4, further comprising, a display of at least one of a patient survey query, a schedule of patient events, and a patient-recorded record of observations. 7. The user application of claim 4, wherein the online synchronization includes data from the health monitoring sensor. 8. The user application of claim 5, further comprising, a display of at least one of a screen allowing a clinician to compose and send a notification, a clinician survey query, a schedule of clinician events, and a clinician-recorded record of observations. 9. The user application of claim 5, further comprising, a health sensor operated by the clinician, wherein online synchronization includes data from the clinician's health sensor. 10. A method of operating a trial operations service suite in a clinical trial operations system, comprising:
running a trial operations service suite software on a computer; communicating with a user application running on a user device; displaying at least one of a service screen and user interface on the user device, the user interface querying for user input information for use in a clinical trial; receiving the user input on the user device; and synchronizing, when online with the computer, service suite information, service screen logic and user input information, collected by the user application when the user application was offline from the computer. 11. The method of claim 10, further comprising, when a data conflict arises during synchronization, wherein data changed in the user application while offline conflicts with data that has changed in the service suite since a previous synchronization, the service suite assumes the new data overrides the old data and continues synchronizing. 12. The method of claim 11, further comprising, the service suite notifying a coordinator to manually resolve the data conflict. 13. The method of claim 11, further comprising, resolving the conflict autonomously via an analytic module associated with the service suite. 14. The method of claim 10, wherein the user application is a patient application and the service suite provides a patient portal. 15. The method of claim 10, wherein the user application is a clinician application and the service suite provides a clinician portal. 16. A method of operating an application in a clinical trial operations system, comprising:
when the application is connected to a portal of a trial operations service suite, synchronizing portal and application data, service screens and logic, and data collected by the application while not connected; and when the application is not connected to the portal, using a proxy embedded in the application to continue providing service and collecting data according to a previously synchronized portal data, service screens, and service logic. 17. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in a cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with a cached service logic, the proxy stops supporting the service while offline. 18. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in the cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with the cached service logic, the proxy assumes the new data overrides the old data and continues supporting the service while offline. 19. The method of claim 16, wherein the application is a patient application and the portal is a patient portal. 20. The method of claim 16, wherein the application is a clinician application and the portal is a clinician portal. | A trial operations service suite system and method in a clinical trial operations system with a patient portal providing patient-directed access to clinical trial operation services, a clinician portal providing clinician-directed access to the clinical trial operation service, and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure, and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline.1. A trial operations service suite in a clinical trial operations system, comprising:
a patient portal providing patient-directed access to clinical trial operation services; a clinician portal providing clinician-directed access to the clinical trial operation services; and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure; and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. 2. The trial operations service suite of claim 1, wherein the synchronization service synchronizes information between the clinician portal and a clinician application when the clinician application is online to the server. 3. A user application in a clinical trial operations system, comprising:
a user interface and network interface modules; user enrollment, user notification, user secure communication, user engagement, and user data capture service modules; and an offline portal proxy providing an offline portal service and data caches, allowing the user application to continue operating when offline from a server running a clinical trial operations service suite; and a synchronization capability, synchronizing information between the user application offline portal proxy and the clinical trial operations service suite when online with the server. 4. The user application of claim 3, further comprising:
a health monitoring sensor adapted for sensing a patient's health, wherein the user application is a patient application running on a patient-located computer; the offline portal proxies a patient portal of the clinical trial operations service suite, the proxied patient portal comprising:
a patient logon screen for a clinical trial;
a patient enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of an online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied patient portal is saved for online synchronization with the clinical trial operation service suite. 5. The user application of claim 4, wherein:
the user application is a clinician application running on a clinician-located computer; the offline portal proxies a clinician portal of the clinical trial operations service suite, the proxied clinician portal comprising:
a clinician logon screen for a clinical trial;
a clinician enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial, and a tracking status of the invite;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of the online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied clinician portal is saved for online synchronization with the clinical trial operation service suite. 6. The user application of claim 4, further comprising, a display of at least one of a patient survey query, a schedule of patient events, and a patient-recorded record of observations. 7. The user application of claim 4, wherein the online synchronization includes data from the health monitoring sensor. 8. The user application of claim 5, further comprising, a display of at least one of a screen allowing a clinician to compose and send a notification, a clinician survey query, a schedule of clinician events, and a clinician-recorded record of observations. 9. The user application of claim 5, further comprising, a health sensor operated by the clinician, wherein online synchronization includes data from the clinician's health sensor. 10. A method of operating a trial operations service suite in a clinical trial operations system, comprising:
running a trial operations service suite software on a computer; communicating with a user application running on a user device; displaying at least one of a service screen and user interface on the user device, the user interface querying for user input information for use in a clinical trial; receiving the user input on the user device; and synchronizing, when online with the computer, service suite information, service screen logic and user input information, collected by the user application when the user application was offline from the computer. 11. The method of claim 10, further comprising, when a data conflict arises during synchronization, wherein data changed in the user application while offline conflicts with data that has changed in the service suite since a previous synchronization, the service suite assumes the new data overrides the old data and continues synchronizing. 12. The method of claim 11, further comprising, the service suite notifying a coordinator to manually resolve the data conflict. 13. The method of claim 11, further comprising, resolving the conflict autonomously via an analytic module associated with the service suite. 14. The method of claim 10, wherein the user application is a patient application and the service suite provides a patient portal. 15. The method of claim 10, wherein the user application is a clinician application and the service suite provides a clinician portal. 16. A method of operating an application in a clinical trial operations system, comprising:
when the application is connected to a portal of a trial operations service suite, synchronizing portal and application data, service screens and logic, and data collected by the application while not connected; and when the application is not connected to the portal, using a proxy embedded in the application to continue providing service and collecting data according to a previously synchronized portal data, service screens, and service logic. 17. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in a cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with a cached service logic, the proxy stops supporting the service while offline. 18. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in the cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with the cached service logic, the proxy assumes the new data overrides the old data and continues supporting the service while offline. 19. The method of claim 16, wherein the application is a patient application and the portal is a patient portal. 20. The method of claim 16, wherein the application is a clinician application and the portal is a clinician portal. | 2,900 |
347,213 | 29,725,979 | 2,918 | A trial operations service suite system and method in a clinical trial operations system with a patient portal providing patient-directed access to clinical trial operation services, a clinician portal providing clinician-directed access to the clinical trial operation service, and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure, and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. | 1. A trial operations service suite in a clinical trial operations system, comprising:
a patient portal providing patient-directed access to clinical trial operation services; a clinician portal providing clinician-directed access to the clinical trial operation services; and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure; and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. 2. The trial operations service suite of claim 1, wherein the synchronization service synchronizes information between the clinician portal and a clinician application when the clinician application is online to the server. 3. A user application in a clinical trial operations system, comprising:
a user interface and network interface modules; user enrollment, user notification, user secure communication, user engagement, and user data capture service modules; and an offline portal proxy providing an offline portal service and data caches, allowing the user application to continue operating when offline from a server running a clinical trial operations service suite; and a synchronization capability, synchronizing information between the user application offline portal proxy and the clinical trial operations service suite when online with the server. 4. The user application of claim 3, further comprising:
a health monitoring sensor adapted for sensing a patient's health, wherein the user application is a patient application running on a patient-located computer; the offline portal proxies a patient portal of the clinical trial operations service suite, the proxied patient portal comprising:
a patient logon screen for a clinical trial;
a patient enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of an online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied patient portal is saved for online synchronization with the clinical trial operation service suite. 5. The user application of claim 4, wherein:
the user application is a clinician application running on a clinician-located computer; the offline portal proxies a clinician portal of the clinical trial operations service suite, the proxied clinician portal comprising:
a clinician logon screen for a clinical trial;
a clinician enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial, and a tracking status of the invite;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of the online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied clinician portal is saved for online synchronization with the clinical trial operation service suite. 6. The user application of claim 4, further comprising, a display of at least one of a patient survey query, a schedule of patient events, and a patient-recorded record of observations. 7. The user application of claim 4, wherein the online synchronization includes data from the health monitoring sensor. 8. The user application of claim 5, further comprising, a display of at least one of a screen allowing a clinician to compose and send a notification, a clinician survey query, a schedule of clinician events, and a clinician-recorded record of observations. 9. The user application of claim 5, further comprising, a health sensor operated by the clinician, wherein online synchronization includes data from the clinician's health sensor. 10. A method of operating a trial operations service suite in a clinical trial operations system, comprising:
running a trial operations service suite software on a computer; communicating with a user application running on a user device; displaying at least one of a service screen and user interface on the user device, the user interface querying for user input information for use in a clinical trial; receiving the user input on the user device; and synchronizing, when online with the computer, service suite information, service screen logic and user input information, collected by the user application when the user application was offline from the computer. 11. The method of claim 10, further comprising, when a data conflict arises during synchronization, wherein data changed in the user application while offline conflicts with data that has changed in the service suite since a previous synchronization, the service suite assumes the new data overrides the old data and continues synchronizing. 12. The method of claim 11, further comprising, the service suite notifying a coordinator to manually resolve the data conflict. 13. The method of claim 11, further comprising, resolving the conflict autonomously via an analytic module associated with the service suite. 14. The method of claim 10, wherein the user application is a patient application and the service suite provides a patient portal. 15. The method of claim 10, wherein the user application is a clinician application and the service suite provides a clinician portal. 16. A method of operating an application in a clinical trial operations system, comprising:
when the application is connected to a portal of a trial operations service suite, synchronizing portal and application data, service screens and logic, and data collected by the application while not connected; and when the application is not connected to the portal, using a proxy embedded in the application to continue providing service and collecting data according to a previously synchronized portal data, service screens, and service logic. 17. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in a cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with a cached service logic, the proxy stops supporting the service while offline. 18. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in the cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with the cached service logic, the proxy assumes the new data overrides the old data and continues supporting the service while offline. 19. The method of claim 16, wherein the application is a patient application and the portal is a patient portal. 20. The method of claim 16, wherein the application is a clinician application and the portal is a clinician portal. | A trial operations service suite system and method in a clinical trial operations system with a patient portal providing patient-directed access to clinical trial operation services, a clinician portal providing clinician-directed access to the clinical trial operation service, and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure, and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline.1. A trial operations service suite in a clinical trial operations system, comprising:
a patient portal providing patient-directed access to clinical trial operation services; a clinician portal providing clinician-directed access to the clinical trial operation services; and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure; and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. 2. The trial operations service suite of claim 1, wherein the synchronization service synchronizes information between the clinician portal and a clinician application when the clinician application is online to the server. 3. A user application in a clinical trial operations system, comprising:
a user interface and network interface modules; user enrollment, user notification, user secure communication, user engagement, and user data capture service modules; and an offline portal proxy providing an offline portal service and data caches, allowing the user application to continue operating when offline from a server running a clinical trial operations service suite; and a synchronization capability, synchronizing information between the user application offline portal proxy and the clinical trial operations service suite when online with the server. 4. The user application of claim 3, further comprising:
a health monitoring sensor adapted for sensing a patient's health, wherein the user application is a patient application running on a patient-located computer; the offline portal proxies a patient portal of the clinical trial operations service suite, the proxied patient portal comprising:
a patient logon screen for a clinical trial;
a patient enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of an online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied patient portal is saved for online synchronization with the clinical trial operation service suite. 5. The user application of claim 4, wherein:
the user application is a clinician application running on a clinician-located computer; the offline portal proxies a clinician portal of the clinical trial operations service suite, the proxied clinician portal comprising:
a clinician logon screen for a clinical trial;
a clinician enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial, and a tracking status of the invite;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of the online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied clinician portal is saved for online synchronization with the clinical trial operation service suite. 6. The user application of claim 4, further comprising, a display of at least one of a patient survey query, a schedule of patient events, and a patient-recorded record of observations. 7. The user application of claim 4, wherein the online synchronization includes data from the health monitoring sensor. 8. The user application of claim 5, further comprising, a display of at least one of a screen allowing a clinician to compose and send a notification, a clinician survey query, a schedule of clinician events, and a clinician-recorded record of observations. 9. The user application of claim 5, further comprising, a health sensor operated by the clinician, wherein online synchronization includes data from the clinician's health sensor. 10. A method of operating a trial operations service suite in a clinical trial operations system, comprising:
running a trial operations service suite software on a computer; communicating with a user application running on a user device; displaying at least one of a service screen and user interface on the user device, the user interface querying for user input information for use in a clinical trial; receiving the user input on the user device; and synchronizing, when online with the computer, service suite information, service screen logic and user input information, collected by the user application when the user application was offline from the computer. 11. The method of claim 10, further comprising, when a data conflict arises during synchronization, wherein data changed in the user application while offline conflicts with data that has changed in the service suite since a previous synchronization, the service suite assumes the new data overrides the old data and continues synchronizing. 12. The method of claim 11, further comprising, the service suite notifying a coordinator to manually resolve the data conflict. 13. The method of claim 11, further comprising, resolving the conflict autonomously via an analytic module associated with the service suite. 14. The method of claim 10, wherein the user application is a patient application and the service suite provides a patient portal. 15. The method of claim 10, wherein the user application is a clinician application and the service suite provides a clinician portal. 16. A method of operating an application in a clinical trial operations system, comprising:
when the application is connected to a portal of a trial operations service suite, synchronizing portal and application data, service screens and logic, and data collected by the application while not connected; and when the application is not connected to the portal, using a proxy embedded in the application to continue providing service and collecting data according to a previously synchronized portal data, service screens, and service logic. 17. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in a cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with a cached service logic, the proxy stops supporting the service while offline. 18. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in the cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with the cached service logic, the proxy assumes the new data overrides the old data and continues supporting the service while offline. 19. The method of claim 16, wherein the application is a patient application and the portal is a patient portal. 20. The method of claim 16, wherein the application is a clinician application and the portal is a clinician portal. | 2,900 |
347,214 | 29,725,954 | 2,918 | A trial operations service suite system and method in a clinical trial operations system with a patient portal providing patient-directed access to clinical trial operation services, a clinician portal providing clinician-directed access to the clinical trial operation service, and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure, and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. | 1. A trial operations service suite in a clinical trial operations system, comprising:
a patient portal providing patient-directed access to clinical trial operation services; a clinician portal providing clinician-directed access to the clinical trial operation services; and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure; and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. 2. The trial operations service suite of claim 1, wherein the synchronization service synchronizes information between the clinician portal and a clinician application when the clinician application is online to the server. 3. A user application in a clinical trial operations system, comprising:
a user interface and network interface modules; user enrollment, user notification, user secure communication, user engagement, and user data capture service modules; and an offline portal proxy providing an offline portal service and data caches, allowing the user application to continue operating when offline from a server running a clinical trial operations service suite; and a synchronization capability, synchronizing information between the user application offline portal proxy and the clinical trial operations service suite when online with the server. 4. The user application of claim 3, further comprising:
a health monitoring sensor adapted for sensing a patient's health, wherein the user application is a patient application running on a patient-located computer; the offline portal proxies a patient portal of the clinical trial operations service suite, the proxied patient portal comprising:
a patient logon screen for a clinical trial;
a patient enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of an online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied patient portal is saved for online synchronization with the clinical trial operation service suite. 5. The user application of claim 4, wherein:
the user application is a clinician application running on a clinician-located computer; the offline portal proxies a clinician portal of the clinical trial operations service suite, the proxied clinician portal comprising:
a clinician logon screen for a clinical trial;
a clinician enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial, and a tracking status of the invite;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of the online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied clinician portal is saved for online synchronization with the clinical trial operation service suite. 6. The user application of claim 4, further comprising, a display of at least one of a patient survey query, a schedule of patient events, and a patient-recorded record of observations. 7. The user application of claim 4, wherein the online synchronization includes data from the health monitoring sensor. 8. The user application of claim 5, further comprising, a display of at least one of a screen allowing a clinician to compose and send a notification, a clinician survey query, a schedule of clinician events, and a clinician-recorded record of observations. 9. The user application of claim 5, further comprising, a health sensor operated by the clinician, wherein online synchronization includes data from the clinician's health sensor. 10. A method of operating a trial operations service suite in a clinical trial operations system, comprising:
running a trial operations service suite software on a computer; communicating with a user application running on a user device; displaying at least one of a service screen and user interface on the user device, the user interface querying for user input information for use in a clinical trial; receiving the user input on the user device; and synchronizing, when online with the computer, service suite information, service screen logic and user input information, collected by the user application when the user application was offline from the computer. 11. The method of claim 10, further comprising, when a data conflict arises during synchronization, wherein data changed in the user application while offline conflicts with data that has changed in the service suite since a previous synchronization, the service suite assumes the new data overrides the old data and continues synchronizing. 12. The method of claim 11, further comprising, the service suite notifying a coordinator to manually resolve the data conflict. 13. The method of claim 11, further comprising, resolving the conflict autonomously via an analytic module associated with the service suite. 14. The method of claim 10, wherein the user application is a patient application and the service suite provides a patient portal. 15. The method of claim 10, wherein the user application is a clinician application and the service suite provides a clinician portal. 16. A method of operating an application in a clinical trial operations system, comprising:
when the application is connected to a portal of a trial operations service suite, synchronizing portal and application data, service screens and logic, and data collected by the application while not connected; and when the application is not connected to the portal, using a proxy embedded in the application to continue providing service and collecting data according to a previously synchronized portal data, service screens, and service logic. 17. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in a cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with a cached service logic, the proxy stops supporting the service while offline. 18. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in the cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with the cached service logic, the proxy assumes the new data overrides the old data and continues supporting the service while offline. 19. The method of claim 16, wherein the application is a patient application and the portal is a patient portal. 20. The method of claim 16, wherein the application is a clinician application and the portal is a clinician portal. | A trial operations service suite system and method in a clinical trial operations system with a patient portal providing patient-directed access to clinical trial operation services, a clinician portal providing clinician-directed access to the clinical trial operation service, and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure, and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline.1. A trial operations service suite in a clinical trial operations system, comprising:
a patient portal providing patient-directed access to clinical trial operation services; a clinician portal providing clinician-directed access to the clinical trial operation services; and a coordinator portal providing coordinator-directed access to the clinical trial operation services, the coordinator portal also providing access to a trial design service wherein the trial design service is configured to allow a coordinator user to at least one of design, create, establish, and deploy a trial protocol and a participant interaction procedure; and a synchronization capability, synchronizing when online, information collected while a portal-supporting application is offline. 2. The trial operations service suite of claim 1, wherein the synchronization service synchronizes information between the clinician portal and a clinician application when the clinician application is online to the server. 3. A user application in a clinical trial operations system, comprising:
a user interface and network interface modules; user enrollment, user notification, user secure communication, user engagement, and user data capture service modules; and an offline portal proxy providing an offline portal service and data caches, allowing the user application to continue operating when offline from a server running a clinical trial operations service suite; and a synchronization capability, synchronizing information between the user application offline portal proxy and the clinical trial operations service suite when online with the server. 4. The user application of claim 3, further comprising:
a health monitoring sensor adapted for sensing a patient's health, wherein the user application is a patient application running on a patient-located computer; the offline portal proxies a patient portal of the clinical trial operations service suite, the proxied patient portal comprising:
a patient logon screen for a clinical trial;
a patient enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of an online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied patient portal is saved for online synchronization with the clinical trial operation service suite. 5. The user application of claim 4, wherein:
the user application is a clinician application running on a clinician-located computer; the offline portal proxies a clinician portal of the clinical trial operations service suite, the proxied clinician portal comprising:
a clinician logon screen for a clinical trial;
a clinician enrollment menu for the clinical trial;
an invitation option for at least one of another patient and clinician candidate to join the clinical trial, and a tracking status of the invite;
a messaging-oriented communication option to securely communicate with other clinical trial participants upon reestablishment of the online state; and
health information specific goals of the clinical trial,
wherein inputted information to the proxied clinician portal is saved for online synchronization with the clinical trial operation service suite. 6. The user application of claim 4, further comprising, a display of at least one of a patient survey query, a schedule of patient events, and a patient-recorded record of observations. 7. The user application of claim 4, wherein the online synchronization includes data from the health monitoring sensor. 8. The user application of claim 5, further comprising, a display of at least one of a screen allowing a clinician to compose and send a notification, a clinician survey query, a schedule of clinician events, and a clinician-recorded record of observations. 9. The user application of claim 5, further comprising, a health sensor operated by the clinician, wherein online synchronization includes data from the clinician's health sensor. 10. A method of operating a trial operations service suite in a clinical trial operations system, comprising:
running a trial operations service suite software on a computer; communicating with a user application running on a user device; displaying at least one of a service screen and user interface on the user device, the user interface querying for user input information for use in a clinical trial; receiving the user input on the user device; and synchronizing, when online with the computer, service suite information, service screen logic and user input information, collected by the user application when the user application was offline from the computer. 11. The method of claim 10, further comprising, when a data conflict arises during synchronization, wherein data changed in the user application while offline conflicts with data that has changed in the service suite since a previous synchronization, the service suite assumes the new data overrides the old data and continues synchronizing. 12. The method of claim 11, further comprising, the service suite notifying a coordinator to manually resolve the data conflict. 13. The method of claim 11, further comprising, resolving the conflict autonomously via an analytic module associated with the service suite. 14. The method of claim 10, wherein the user application is a patient application and the service suite provides a patient portal. 15. The method of claim 10, wherein the user application is a clinician application and the service suite provides a clinician portal. 16. A method of operating an application in a clinical trial operations system, comprising:
when the application is connected to a portal of a trial operations service suite, synchronizing portal and application data, service screens and logic, and data collected by the application while not connected; and when the application is not connected to the portal, using a proxy embedded in the application to continue providing service and collecting data according to a previously synchronized portal data, service screens, and service logic. 17. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in a cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with a cached service logic, the proxy stops supporting the service while offline. 18. The method of claim 16, further comprising, when a data conflict arises during offline operation, wherein the application either requires portal data that is not available in the cache or depends on portal data that has changed while offline in such a manner as to be inconsistent with the cached service logic, the proxy assumes the new data overrides the old data and continues supporting the service while offline. 19. The method of claim 16, wherein the application is a patient application and the portal is a patient portal. 20. The method of claim 16, wherein the application is a clinician application and the portal is a clinician portal. | 2,900 |
347,215 | 16,805,674 | 2,918 | The apparatus determines, for a CC, an active TCI state of at least one of a CORESET of a PDCCH when the CORESET is configured on the CC or a PDSCH. In addition, the apparatus determines, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a PUCCH or SRS. Further, the apparatus transmits at least one of the PUCCH or the SRS through the determined default beam on the CC. | 1. A method of wireless communication at a user equipment (UE), comprising:
determining, for a component carrier (CC), an active transmission configuration indicator (TCI) state of at least one of a control resource set (CORESET) of a physical downlink control channel (PDCCH) when the CORESET is configured on the CC or a physical downlink shared channel (PDSCH); determining, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a physical uplink control channel (PUCCH) or sounding reference signals (SRS), wherein when the CORESET is configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the CORESET of the PDCCH, wherein when the CORESET is not configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH; and transmitting at least one of the PUCCH or the SRS through the determined default beam on the CC. 2. The method of claim 1, wherein the determining the active TCI state comprises determining whether the CORESET is configured on the CC, wherein when the CORESET is configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the CORESET of the PDCCH. 3. The method of claim 2, wherein when the CORESET is not configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the PDSCH. 4. The method of claim 3, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 5. The method of claim 1, wherein the determined active TCI state is one active TCI state of active TCI states of the PDSCH, and the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH. 6. The method of claim 5, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 7. The method of claim 1, wherein the UE supports a first active TCI state and a second active TCI state for the PDCCH, where one of the first TCI state or the second TCI state is also for the PDSCH, and wherein the determined active TCI state is one of the first TCI state or the second TCI state that is also for the PDSCH. 8. The method of claim 7, wherein the UE determines the active TCI state based on an active TCI state for a CORESET of the PDCCH. 9. The method of claim 7, wherein the UE determines the active TCI state based on an indication through a medium access control (MAC) control element (CE). 10. An apparatus for wireless communication at a user equipment (UE), comprising:
a memory; and at least one processor coupled to the memory and configured to:
determine, for a component carrier (CC), an active transmission configuration indicator (TCI) state of at least one of a control resource set (CORESET) of a physical downlink control channel (PDCCH) when the CORESET is configured on the CC or a physical downlink shared channel (PDSCH);
determine, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a physical uplink control channel (PUCCH) or sounding reference signals (SRS), wherein when the CORESET is configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the CORESET of the PDCCH, wherein when the CORESET is not configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH; and
transmit at least one of the PUCCH or the SRS through the determined default beam on the CC. 11. The apparatus of claim 10, wherein to determine the active TCI state, the at least one processor is configured to determine whether the CORESET is configured on the CC, wherein when the CORESET is configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the CORESET of the PDCCH. 12. The apparatus of claim 11, wherein when the CORESET is not configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the PDSCH. 13. The apparatus of claim 12, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 14. The apparatus of claim 10, wherein the determined active TCI state is one active TCI state of active TCI states of the PDSCH, and the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH. 15. The apparatus of claim 14, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 16. The apparatus of claim 10, wherein the UE supports a first active TCI state and a second active TCI state for the PDCCH, where one of the first TCI state or the second TCI state is also for the PDSCH, and wherein the determined active TCI state is one of the first TCI state or the second TCI state that is also for the PDSCH. 17. The apparatus of claim 16, wherein the UE determines the active TCI state based on an active TCI state for a CORESET of the PDCCH. 18. The apparatus of claim 16, wherein the UE determines the active TCI state based on an indication through a medium access control (MAC) control element (CE). 19. An apparatus of wireless communication at a user equipment (UE), comprising:
means for determining, for a component carrier (CC), an active transmission configuration indicator (TCI) state of at least one of a control resource set (CORESET) of a physical downlink control channel (PDCCH) when the CORESET is configured on the CC or a physical downlink shared channel (PDSCH); means for determining, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a physical uplink control channel (PUCCH) or sounding reference signals (SRS), wherein when the CORESET is configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the CORESET of the PDCCH, wherein when the CORESET is not configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH; and means for transmitting at least one of the PUCCH or the SRS through the determined default beam on the CC. 20. The apparatus of claim 19, wherein the means for determining the active TCI state is configured to determine whether the CORESET is configured on the CC, wherein when the CORESET is configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the CORESET of the PDCCH. 21. The apparatus of claim 20, wherein when the CORESET is not configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the PDSCH. 22. The apparatus of claim 21, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 23. The apparatus of claim 19, wherein the determined active TCI state is one active TCI state of active TCI states of the PDSCH, and the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH. 24. The apparatus of claim 23, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 25. The apparatus of claim 19, wherein the UE supports a first active TCI state and a second active TCI state for the PDCCH, where one of the first TCI state or the second TCI state is also for the PDSCH, and wherein the determined active TCI state is one of the first TCI state or the second TCI state that is also for the PDSCH. 26. The apparatus of claim 25, wherein the UE determines the active TCI state based on an active TCI state for a CORESET of the PDCCH. 27. The apparatus of claim 25, wherein the UE determines the active TCI state based on an indication through a medium access control (MAC) control element (CE). 28. A non-transitory computer-readable medium storing computer executable code at a user equipment (UE), the code when executed by a processor cause the processor to:
determine, for a component carrier (CC), an active transmission configuration indicator (TCI) state of at least one of a control resource set (CORESET) of a physical downlink control channel (PDCCH) when the CORESET is configured on the CC or a physical downlink shared channel (PDSCH); determine, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a physical uplink control channel (PUCCH) or sounding reference signals (SRS), wherein when the CORESET is configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the CORESET of the PDCCH, wherein when the CORESET is not configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH; and transmit at least one of the PUCCH or the SRS through the determined default beam on the CC. | The apparatus determines, for a CC, an active TCI state of at least one of a CORESET of a PDCCH when the CORESET is configured on the CC or a PDSCH. In addition, the apparatus determines, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a PUCCH or SRS. Further, the apparatus transmits at least one of the PUCCH or the SRS through the determined default beam on the CC.1. A method of wireless communication at a user equipment (UE), comprising:
determining, for a component carrier (CC), an active transmission configuration indicator (TCI) state of at least one of a control resource set (CORESET) of a physical downlink control channel (PDCCH) when the CORESET is configured on the CC or a physical downlink shared channel (PDSCH); determining, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a physical uplink control channel (PUCCH) or sounding reference signals (SRS), wherein when the CORESET is configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the CORESET of the PDCCH, wherein when the CORESET is not configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH; and transmitting at least one of the PUCCH or the SRS through the determined default beam on the CC. 2. The method of claim 1, wherein the determining the active TCI state comprises determining whether the CORESET is configured on the CC, wherein when the CORESET is configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the CORESET of the PDCCH. 3. The method of claim 2, wherein when the CORESET is not configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the PDSCH. 4. The method of claim 3, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 5. The method of claim 1, wherein the determined active TCI state is one active TCI state of active TCI states of the PDSCH, and the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH. 6. The method of claim 5, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 7. The method of claim 1, wherein the UE supports a first active TCI state and a second active TCI state for the PDCCH, where one of the first TCI state or the second TCI state is also for the PDSCH, and wherein the determined active TCI state is one of the first TCI state or the second TCI state that is also for the PDSCH. 8. The method of claim 7, wherein the UE determines the active TCI state based on an active TCI state for a CORESET of the PDCCH. 9. The method of claim 7, wherein the UE determines the active TCI state based on an indication through a medium access control (MAC) control element (CE). 10. An apparatus for wireless communication at a user equipment (UE), comprising:
a memory; and at least one processor coupled to the memory and configured to:
determine, for a component carrier (CC), an active transmission configuration indicator (TCI) state of at least one of a control resource set (CORESET) of a physical downlink control channel (PDCCH) when the CORESET is configured on the CC or a physical downlink shared channel (PDSCH);
determine, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a physical uplink control channel (PUCCH) or sounding reference signals (SRS), wherein when the CORESET is configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the CORESET of the PDCCH, wherein when the CORESET is not configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH; and
transmit at least one of the PUCCH or the SRS through the determined default beam on the CC. 11. The apparatus of claim 10, wherein to determine the active TCI state, the at least one processor is configured to determine whether the CORESET is configured on the CC, wherein when the CORESET is configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the CORESET of the PDCCH. 12. The apparatus of claim 11, wherein when the CORESET is not configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the PDSCH. 13. The apparatus of claim 12, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 14. The apparatus of claim 10, wherein the determined active TCI state is one active TCI state of active TCI states of the PDSCH, and the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH. 15. The apparatus of claim 14, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 16. The apparatus of claim 10, wherein the UE supports a first active TCI state and a second active TCI state for the PDCCH, where one of the first TCI state or the second TCI state is also for the PDSCH, and wherein the determined active TCI state is one of the first TCI state or the second TCI state that is also for the PDSCH. 17. The apparatus of claim 16, wherein the UE determines the active TCI state based on an active TCI state for a CORESET of the PDCCH. 18. The apparatus of claim 16, wherein the UE determines the active TCI state based on an indication through a medium access control (MAC) control element (CE). 19. An apparatus of wireless communication at a user equipment (UE), comprising:
means for determining, for a component carrier (CC), an active transmission configuration indicator (TCI) state of at least one of a control resource set (CORESET) of a physical downlink control channel (PDCCH) when the CORESET is configured on the CC or a physical downlink shared channel (PDSCH); means for determining, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a physical uplink control channel (PUCCH) or sounding reference signals (SRS), wherein when the CORESET is configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the CORESET of the PDCCH, wherein when the CORESET is not configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH; and means for transmitting at least one of the PUCCH or the SRS through the determined default beam on the CC. 20. The apparatus of claim 19, wherein the means for determining the active TCI state is configured to determine whether the CORESET is configured on the CC, wherein when the CORESET is configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the CORESET of the PDCCH. 21. The apparatus of claim 20, wherein when the CORESET is not configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the PDSCH. 22. The apparatus of claim 21, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 23. The apparatus of claim 19, wherein the determined active TCI state is one active TCI state of active TCI states of the PDSCH, and the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH. 24. The apparatus of claim 23, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 25. The apparatus of claim 19, wherein the UE supports a first active TCI state and a second active TCI state for the PDCCH, where one of the first TCI state or the second TCI state is also for the PDSCH, and wherein the determined active TCI state is one of the first TCI state or the second TCI state that is also for the PDSCH. 26. The apparatus of claim 25, wherein the UE determines the active TCI state based on an active TCI state for a CORESET of the PDCCH. 27. The apparatus of claim 25, wherein the UE determines the active TCI state based on an indication through a medium access control (MAC) control element (CE). 28. A non-transitory computer-readable medium storing computer executable code at a user equipment (UE), the code when executed by a processor cause the processor to:
determine, for a component carrier (CC), an active transmission configuration indicator (TCI) state of at least one of a control resource set (CORESET) of a physical downlink control channel (PDCCH) when the CORESET is configured on the CC or a physical downlink shared channel (PDSCH); determine, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a physical uplink control channel (PUCCH) or sounding reference signals (SRS), wherein when the CORESET is configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the CORESET of the PDCCH, wherein when the CORESET is not configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH; and transmit at least one of the PUCCH or the SRS through the determined default beam on the CC. | 2,900 |
347,216 | 29,725,996 | 2,913 | The apparatus determines, for a CC, an active TCI state of at least one of a CORESET of a PDCCH when the CORESET is configured on the CC or a PDSCH. In addition, the apparatus determines, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a PUCCH or SRS. Further, the apparatus transmits at least one of the PUCCH or the SRS through the determined default beam on the CC. | 1. A method of wireless communication at a user equipment (UE), comprising:
determining, for a component carrier (CC), an active transmission configuration indicator (TCI) state of at least one of a control resource set (CORESET) of a physical downlink control channel (PDCCH) when the CORESET is configured on the CC or a physical downlink shared channel (PDSCH); determining, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a physical uplink control channel (PUCCH) or sounding reference signals (SRS), wherein when the CORESET is configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the CORESET of the PDCCH, wherein when the CORESET is not configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH; and transmitting at least one of the PUCCH or the SRS through the determined default beam on the CC. 2. The method of claim 1, wherein the determining the active TCI state comprises determining whether the CORESET is configured on the CC, wherein when the CORESET is configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the CORESET of the PDCCH. 3. The method of claim 2, wherein when the CORESET is not configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the PDSCH. 4. The method of claim 3, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 5. The method of claim 1, wherein the determined active TCI state is one active TCI state of active TCI states of the PDSCH, and the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH. 6. The method of claim 5, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 7. The method of claim 1, wherein the UE supports a first active TCI state and a second active TCI state for the PDCCH, where one of the first TCI state or the second TCI state is also for the PDSCH, and wherein the determined active TCI state is one of the first TCI state or the second TCI state that is also for the PDSCH. 8. The method of claim 7, wherein the UE determines the active TCI state based on an active TCI state for a CORESET of the PDCCH. 9. The method of claim 7, wherein the UE determines the active TCI state based on an indication through a medium access control (MAC) control element (CE). 10. An apparatus for wireless communication at a user equipment (UE), comprising:
a memory; and at least one processor coupled to the memory and configured to:
determine, for a component carrier (CC), an active transmission configuration indicator (TCI) state of at least one of a control resource set (CORESET) of a physical downlink control channel (PDCCH) when the CORESET is configured on the CC or a physical downlink shared channel (PDSCH);
determine, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a physical uplink control channel (PUCCH) or sounding reference signals (SRS), wherein when the CORESET is configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the CORESET of the PDCCH, wherein when the CORESET is not configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH; and
transmit at least one of the PUCCH or the SRS through the determined default beam on the CC. 11. The apparatus of claim 10, wherein to determine the active TCI state, the at least one processor is configured to determine whether the CORESET is configured on the CC, wherein when the CORESET is configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the CORESET of the PDCCH. 12. The apparatus of claim 11, wherein when the CORESET is not configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the PDSCH. 13. The apparatus of claim 12, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 14. The apparatus of claim 10, wherein the determined active TCI state is one active TCI state of active TCI states of the PDSCH, and the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH. 15. The apparatus of claim 14, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 16. The apparatus of claim 10, wherein the UE supports a first active TCI state and a second active TCI state for the PDCCH, where one of the first TCI state or the second TCI state is also for the PDSCH, and wherein the determined active TCI state is one of the first TCI state or the second TCI state that is also for the PDSCH. 17. The apparatus of claim 16, wherein the UE determines the active TCI state based on an active TCI state for a CORESET of the PDCCH. 18. The apparatus of claim 16, wherein the UE determines the active TCI state based on an indication through a medium access control (MAC) control element (CE). 19. An apparatus of wireless communication at a user equipment (UE), comprising:
means for determining, for a component carrier (CC), an active transmission configuration indicator (TCI) state of at least one of a control resource set (CORESET) of a physical downlink control channel (PDCCH) when the CORESET is configured on the CC or a physical downlink shared channel (PDSCH); means for determining, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a physical uplink control channel (PUCCH) or sounding reference signals (SRS), wherein when the CORESET is configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the CORESET of the PDCCH, wherein when the CORESET is not configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH; and means for transmitting at least one of the PUCCH or the SRS through the determined default beam on the CC. 20. The apparatus of claim 19, wherein the means for determining the active TCI state is configured to determine whether the CORESET is configured on the CC, wherein when the CORESET is configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the CORESET of the PDCCH. 21. The apparatus of claim 20, wherein when the CORESET is not configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the PDSCH. 22. The apparatus of claim 21, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 23. The apparatus of claim 19, wherein the determined active TCI state is one active TCI state of active TCI states of the PDSCH, and the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH. 24. The apparatus of claim 23, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 25. The apparatus of claim 19, wherein the UE supports a first active TCI state and a second active TCI state for the PDCCH, where one of the first TCI state or the second TCI state is also for the PDSCH, and wherein the determined active TCI state is one of the first TCI state or the second TCI state that is also for the PDSCH. 26. The apparatus of claim 25, wherein the UE determines the active TCI state based on an active TCI state for a CORESET of the PDCCH. 27. The apparatus of claim 25, wherein the UE determines the active TCI state based on an indication through a medium access control (MAC) control element (CE). 28. A non-transitory computer-readable medium storing computer executable code at a user equipment (UE), the code when executed by a processor cause the processor to:
determine, for a component carrier (CC), an active transmission configuration indicator (TCI) state of at least one of a control resource set (CORESET) of a physical downlink control channel (PDCCH) when the CORESET is configured on the CC or a physical downlink shared channel (PDSCH); determine, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a physical uplink control channel (PUCCH) or sounding reference signals (SRS), wherein when the CORESET is configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the CORESET of the PDCCH, wherein when the CORESET is not configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH; and transmit at least one of the PUCCH or the SRS through the determined default beam on the CC. | The apparatus determines, for a CC, an active TCI state of at least one of a CORESET of a PDCCH when the CORESET is configured on the CC or a PDSCH. In addition, the apparatus determines, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a PUCCH or SRS. Further, the apparatus transmits at least one of the PUCCH or the SRS through the determined default beam on the CC.1. A method of wireless communication at a user equipment (UE), comprising:
determining, for a component carrier (CC), an active transmission configuration indicator (TCI) state of at least one of a control resource set (CORESET) of a physical downlink control channel (PDCCH) when the CORESET is configured on the CC or a physical downlink shared channel (PDSCH); determining, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a physical uplink control channel (PUCCH) or sounding reference signals (SRS), wherein when the CORESET is configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the CORESET of the PDCCH, wherein when the CORESET is not configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH; and transmitting at least one of the PUCCH or the SRS through the determined default beam on the CC. 2. The method of claim 1, wherein the determining the active TCI state comprises determining whether the CORESET is configured on the CC, wherein when the CORESET is configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the CORESET of the PDCCH. 3. The method of claim 2, wherein when the CORESET is not configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the PDSCH. 4. The method of claim 3, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 5. The method of claim 1, wherein the determined active TCI state is one active TCI state of active TCI states of the PDSCH, and the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH. 6. The method of claim 5, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 7. The method of claim 1, wherein the UE supports a first active TCI state and a second active TCI state for the PDCCH, where one of the first TCI state or the second TCI state is also for the PDSCH, and wherein the determined active TCI state is one of the first TCI state or the second TCI state that is also for the PDSCH. 8. The method of claim 7, wherein the UE determines the active TCI state based on an active TCI state for a CORESET of the PDCCH. 9. The method of claim 7, wherein the UE determines the active TCI state based on an indication through a medium access control (MAC) control element (CE). 10. An apparatus for wireless communication at a user equipment (UE), comprising:
a memory; and at least one processor coupled to the memory and configured to:
determine, for a component carrier (CC), an active transmission configuration indicator (TCI) state of at least one of a control resource set (CORESET) of a physical downlink control channel (PDCCH) when the CORESET is configured on the CC or a physical downlink shared channel (PDSCH);
determine, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a physical uplink control channel (PUCCH) or sounding reference signals (SRS), wherein when the CORESET is configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the CORESET of the PDCCH, wherein when the CORESET is not configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH; and
transmit at least one of the PUCCH or the SRS through the determined default beam on the CC. 11. The apparatus of claim 10, wherein to determine the active TCI state, the at least one processor is configured to determine whether the CORESET is configured on the CC, wherein when the CORESET is configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the CORESET of the PDCCH. 12. The apparatus of claim 11, wherein when the CORESET is not configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the PDSCH. 13. The apparatus of claim 12, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 14. The apparatus of claim 10, wherein the determined active TCI state is one active TCI state of active TCI states of the PDSCH, and the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH. 15. The apparatus of claim 14, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 16. The apparatus of claim 10, wherein the UE supports a first active TCI state and a second active TCI state for the PDCCH, where one of the first TCI state or the second TCI state is also for the PDSCH, and wherein the determined active TCI state is one of the first TCI state or the second TCI state that is also for the PDSCH. 17. The apparatus of claim 16, wherein the UE determines the active TCI state based on an active TCI state for a CORESET of the PDCCH. 18. The apparatus of claim 16, wherein the UE determines the active TCI state based on an indication through a medium access control (MAC) control element (CE). 19. An apparatus of wireless communication at a user equipment (UE), comprising:
means for determining, for a component carrier (CC), an active transmission configuration indicator (TCI) state of at least one of a control resource set (CORESET) of a physical downlink control channel (PDCCH) when the CORESET is configured on the CC or a physical downlink shared channel (PDSCH); means for determining, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a physical uplink control channel (PUCCH) or sounding reference signals (SRS), wherein when the CORESET is configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the CORESET of the PDCCH, wherein when the CORESET is not configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH; and means for transmitting at least one of the PUCCH or the SRS through the determined default beam on the CC. 20. The apparatus of claim 19, wherein the means for determining the active TCI state is configured to determine whether the CORESET is configured on the CC, wherein when the CORESET is configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the CORESET of the PDCCH. 21. The apparatus of claim 20, wherein when the CORESET is not configured on the CC, the determined active TCI state is one active TCI state of active TCI states of the PDSCH. 22. The apparatus of claim 21, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 23. The apparatus of claim 19, wherein the determined active TCI state is one active TCI state of active TCI states of the PDSCH, and the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH. 24. The apparatus of claim 23, wherein the determined active TCI state of the PDSCH is the TCI state with a lowest TCI state identifier of the active TCI states of the PDSCH, or the determined active TCI state is indicated by a medium access control (MAC) control element (CE). 25. The apparatus of claim 19, wherein the UE supports a first active TCI state and a second active TCI state for the PDCCH, where one of the first TCI state or the second TCI state is also for the PDSCH, and wherein the determined active TCI state is one of the first TCI state or the second TCI state that is also for the PDSCH. 26. The apparatus of claim 25, wherein the UE determines the active TCI state based on an active TCI state for a CORESET of the PDCCH. 27. The apparatus of claim 25, wherein the UE determines the active TCI state based on an indication through a medium access control (MAC) control element (CE). 28. A non-transitory computer-readable medium storing computer executable code at a user equipment (UE), the code when executed by a processor cause the processor to:
determine, for a component carrier (CC), an active transmission configuration indicator (TCI) state of at least one of a control resource set (CORESET) of a physical downlink control channel (PDCCH) when the CORESET is configured on the CC or a physical downlink shared channel (PDSCH); determine, based on the determined active TCI state, a default beam on the CC for transmitting at least one of a physical uplink control channel (PUCCH) or sounding reference signals (SRS), wherein when the CORESET is configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the CORESET of the PDCCH, wherein when the CORESET is not configured on the CC, the default beam for at least one of the PUCCH or the SRS is determined based on the determined active TCI state of the PDSCH; and transmit at least one of the PUCCH or the SRS through the determined default beam on the CC. | 2,900 |
347,217 | 16,805,659 | 2,913 | A desired departure temperature is determined for a battery, having a temperature, in a vehicle based at least in part on trip information associated with a trip. A temperature controlling system is used to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. | 1. A system, comprising:
a processor; and a memory coupled with the processor, wherein the memory is configured to provide the processor with instructions which when executed cause the processor to:
determine a desired departure temperature for a battery, having a temperature, in a vehicle based at least in part on trip information associated with a trip as an input for an estimation function; and
use a temperature controlling system to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. 2. The system recited in claim 1, wherein the trip information includes one or more of the following: a trip duration, a destination, a trip distance, or a trip plan. 3. The system recited in claim 1, wherein determining the desired departure temperature is further based at least in part on one or more of the following: state of health information associated with the battery, an average cell internal resistance, a minimum cell capacity, or ambient temperature. 4. The system recited in claim 1, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip duration and the estimation function that inputs the trip duration, wherein the trip information includes the trip duration; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 5. The system recited in claim 1, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip plan and the estimation function that inputs the trip plan, wherein the trip information includes the trip plan; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 6. The system recited in claim 1, wherein determining the desired departure temperature includes:
generating, for each of a plurality of test departure temperatures, a plurality of modeled battery data using a battery model associated with the battery; evaluating each of the plurality of modeled battery data using a cost function in order to obtain an evaluated cost function wherein the cost function takes into account at least battery performance and battery degradation; and outputting that test departure temperature from the plurality of test departure temperatures which corresponds to a minimum of the evaluated cost function as the desired departure temperature. 7. The system recited in claim 1, wherein:
the trip information includes a departure time; the memory is further configured to provide the processor with instructions which when executed cause the processor to: determine a start time to start the temperature controlling system based at least in part on the departure time and the desired departure temperature; and the temperature controlling system is started at the start time. 8. A method, comprising:
providing trip information associated with a trip as an input to an estimation function; determining a desired departure temperature for a battery, having a temperature, in a vehicle based at least in part on the trip information and the estimation function; and using a temperature controlling system to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. 9. The method recited in claim 8, wherein the trip information includes one or more of the following: a trip duration, a destination, a trip distance, or a trip plan. 10. The method recited in claim 8, wherein determining the desired departure temperature is further based at least in part on one or more of the following: state of health information associated with the battery, an average cell internal resistance, a minimum cell capacity, or ambient temperature. 11. The method recited in claim 8, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip duration and the estimation function that inputs the trip duration, wherein the trip information includes the trip duration; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 12. The method recited in claim 8, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip plan and the estimation function that inputs the trip plan, wherein the trip information includes the trip plan; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 13. The method recited in claim 8, wherein determining the desired departure temperature includes:
generating, for each of a plurality of test departure temperatures, a plurality of modeled battery data using a battery model associated with the battery; evaluating each of the plurality of modeled battery data using a cost function in order to obtain an evaluated cost function wherein the cost function takes into account at least battery performance and battery degradation; and outputting that test departure temperature from the plurality of test departure temperatures which corresponds to a minimum of the evaluated cost function as the desired departure temperature. 14. The method recited in claim 8, wherein:
the trip information includes a departure time; the method further includes: determining a start time to start the temperature controlling system based at least in part on the departure time and the desired departure temperature; and the temperature controlling system is started at the start time. 15. A computer program product, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
providing trip information associated with a trip as an input to an estimation function; determining a desired departure temperature for a battery, having a temperature, in a vehicle based at least in part on the trip information and the estimation function; and using a temperature controlling system to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. 16. The computer program product recited in claim 15, wherein determining the desired departure temperature is further based at least in part on one or more of the following:
state of health information associated with the battery, an average cell internal resistance, a minimum cell capacity, or ambient temperature. 17. The computer program product recited in claim 15, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip duration and the estimation function that inputs the trip duration, wherein the trip information includes the trip duration; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 18. The computer program product recited in claim 15, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip plan and the estimation function that inputs the trip plan, wherein the trip information includes the trip plan; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 19. The computer program product recited in claim 15, wherein determining the desired departure temperature includes:
generating, for each of a plurality of test departure temperatures, a plurality of modeled battery data using a battery model associated with the battery; evaluating each of the plurality of modeled battery data using a cost function in order to obtain an evaluated cost function wherein the cost function takes into account at least battery performance and battery degradation; and outputting that test departure temperature from the plurality of test departure temperatures which corresponds to a minimum of the evaluated cost function as the desired departure temperature. 20. The computer program product recited in claim 15, wherein:
the trip information includes a departure time; the computer program product further includes computer instructions for: determining a start time to start the temperature controlling system based at least in part on the departure time and the desired departure temperature; and the temperature controlling system is started at the start time. | A desired departure temperature is determined for a battery, having a temperature, in a vehicle based at least in part on trip information associated with a trip. A temperature controlling system is used to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature.1. A system, comprising:
a processor; and a memory coupled with the processor, wherein the memory is configured to provide the processor with instructions which when executed cause the processor to:
determine a desired departure temperature for a battery, having a temperature, in a vehicle based at least in part on trip information associated with a trip as an input for an estimation function; and
use a temperature controlling system to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. 2. The system recited in claim 1, wherein the trip information includes one or more of the following: a trip duration, a destination, a trip distance, or a trip plan. 3. The system recited in claim 1, wherein determining the desired departure temperature is further based at least in part on one or more of the following: state of health information associated with the battery, an average cell internal resistance, a minimum cell capacity, or ambient temperature. 4. The system recited in claim 1, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip duration and the estimation function that inputs the trip duration, wherein the trip information includes the trip duration; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 5. The system recited in claim 1, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip plan and the estimation function that inputs the trip plan, wherein the trip information includes the trip plan; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 6. The system recited in claim 1, wherein determining the desired departure temperature includes:
generating, for each of a plurality of test departure temperatures, a plurality of modeled battery data using a battery model associated with the battery; evaluating each of the plurality of modeled battery data using a cost function in order to obtain an evaluated cost function wherein the cost function takes into account at least battery performance and battery degradation; and outputting that test departure temperature from the plurality of test departure temperatures which corresponds to a minimum of the evaluated cost function as the desired departure temperature. 7. The system recited in claim 1, wherein:
the trip information includes a departure time; the memory is further configured to provide the processor with instructions which when executed cause the processor to: determine a start time to start the temperature controlling system based at least in part on the departure time and the desired departure temperature; and the temperature controlling system is started at the start time. 8. A method, comprising:
providing trip information associated with a trip as an input to an estimation function; determining a desired departure temperature for a battery, having a temperature, in a vehicle based at least in part on the trip information and the estimation function; and using a temperature controlling system to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. 9. The method recited in claim 8, wherein the trip information includes one or more of the following: a trip duration, a destination, a trip distance, or a trip plan. 10. The method recited in claim 8, wherein determining the desired departure temperature is further based at least in part on one or more of the following: state of health information associated with the battery, an average cell internal resistance, a minimum cell capacity, or ambient temperature. 11. The method recited in claim 8, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip duration and the estimation function that inputs the trip duration, wherein the trip information includes the trip duration; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 12. The method recited in claim 8, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip plan and the estimation function that inputs the trip plan, wherein the trip information includes the trip plan; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 13. The method recited in claim 8, wherein determining the desired departure temperature includes:
generating, for each of a plurality of test departure temperatures, a plurality of modeled battery data using a battery model associated with the battery; evaluating each of the plurality of modeled battery data using a cost function in order to obtain an evaluated cost function wherein the cost function takes into account at least battery performance and battery degradation; and outputting that test departure temperature from the plurality of test departure temperatures which corresponds to a minimum of the evaluated cost function as the desired departure temperature. 14. The method recited in claim 8, wherein:
the trip information includes a departure time; the method further includes: determining a start time to start the temperature controlling system based at least in part on the departure time and the desired departure temperature; and the temperature controlling system is started at the start time. 15. A computer program product, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
providing trip information associated with a trip as an input to an estimation function; determining a desired departure temperature for a battery, having a temperature, in a vehicle based at least in part on the trip information and the estimation function; and using a temperature controlling system to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. 16. The computer program product recited in claim 15, wherein determining the desired departure temperature is further based at least in part on one or more of the following:
state of health information associated with the battery, an average cell internal resistance, a minimum cell capacity, or ambient temperature. 17. The computer program product recited in claim 15, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip duration and the estimation function that inputs the trip duration, wherein the trip information includes the trip duration; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 18. The computer program product recited in claim 15, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip plan and the estimation function that inputs the trip plan, wherein the trip information includes the trip plan; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 19. The computer program product recited in claim 15, wherein determining the desired departure temperature includes:
generating, for each of a plurality of test departure temperatures, a plurality of modeled battery data using a battery model associated with the battery; evaluating each of the plurality of modeled battery data using a cost function in order to obtain an evaluated cost function wherein the cost function takes into account at least battery performance and battery degradation; and outputting that test departure temperature from the plurality of test departure temperatures which corresponds to a minimum of the evaluated cost function as the desired departure temperature. 20. The computer program product recited in claim 15, wherein:
the trip information includes a departure time; the computer program product further includes computer instructions for: determining a start time to start the temperature controlling system based at least in part on the departure time and the desired departure temperature; and the temperature controlling system is started at the start time. | 2,900 |
347,218 | 29,725,973 | 2,924 | A desired departure temperature is determined for a battery, having a temperature, in a vehicle based at least in part on trip information associated with a trip. A temperature controlling system is used to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. | 1. A system, comprising:
a processor; and a memory coupled with the processor, wherein the memory is configured to provide the processor with instructions which when executed cause the processor to:
determine a desired departure temperature for a battery, having a temperature, in a vehicle based at least in part on trip information associated with a trip as an input for an estimation function; and
use a temperature controlling system to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. 2. The system recited in claim 1, wherein the trip information includes one or more of the following: a trip duration, a destination, a trip distance, or a trip plan. 3. The system recited in claim 1, wherein determining the desired departure temperature is further based at least in part on one or more of the following: state of health information associated with the battery, an average cell internal resistance, a minimum cell capacity, or ambient temperature. 4. The system recited in claim 1, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip duration and the estimation function that inputs the trip duration, wherein the trip information includes the trip duration; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 5. The system recited in claim 1, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip plan and the estimation function that inputs the trip plan, wherein the trip information includes the trip plan; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 6. The system recited in claim 1, wherein determining the desired departure temperature includes:
generating, for each of a plurality of test departure temperatures, a plurality of modeled battery data using a battery model associated with the battery; evaluating each of the plurality of modeled battery data using a cost function in order to obtain an evaluated cost function wherein the cost function takes into account at least battery performance and battery degradation; and outputting that test departure temperature from the plurality of test departure temperatures which corresponds to a minimum of the evaluated cost function as the desired departure temperature. 7. The system recited in claim 1, wherein:
the trip information includes a departure time; the memory is further configured to provide the processor with instructions which when executed cause the processor to: determine a start time to start the temperature controlling system based at least in part on the departure time and the desired departure temperature; and the temperature controlling system is started at the start time. 8. A method, comprising:
providing trip information associated with a trip as an input to an estimation function; determining a desired departure temperature for a battery, having a temperature, in a vehicle based at least in part on the trip information and the estimation function; and using a temperature controlling system to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. 9. The method recited in claim 8, wherein the trip information includes one or more of the following: a trip duration, a destination, a trip distance, or a trip plan. 10. The method recited in claim 8, wherein determining the desired departure temperature is further based at least in part on one or more of the following: state of health information associated with the battery, an average cell internal resistance, a minimum cell capacity, or ambient temperature. 11. The method recited in claim 8, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip duration and the estimation function that inputs the trip duration, wherein the trip information includes the trip duration; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 12. The method recited in claim 8, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip plan and the estimation function that inputs the trip plan, wherein the trip information includes the trip plan; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 13. The method recited in claim 8, wherein determining the desired departure temperature includes:
generating, for each of a plurality of test departure temperatures, a plurality of modeled battery data using a battery model associated with the battery; evaluating each of the plurality of modeled battery data using a cost function in order to obtain an evaluated cost function wherein the cost function takes into account at least battery performance and battery degradation; and outputting that test departure temperature from the plurality of test departure temperatures which corresponds to a minimum of the evaluated cost function as the desired departure temperature. 14. The method recited in claim 8, wherein:
the trip information includes a departure time; the method further includes: determining a start time to start the temperature controlling system based at least in part on the departure time and the desired departure temperature; and the temperature controlling system is started at the start time. 15. A computer program product, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
providing trip information associated with a trip as an input to an estimation function; determining a desired departure temperature for a battery, having a temperature, in a vehicle based at least in part on the trip information and the estimation function; and using a temperature controlling system to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. 16. The computer program product recited in claim 15, wherein determining the desired departure temperature is further based at least in part on one or more of the following:
state of health information associated with the battery, an average cell internal resistance, a minimum cell capacity, or ambient temperature. 17. The computer program product recited in claim 15, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip duration and the estimation function that inputs the trip duration, wherein the trip information includes the trip duration; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 18. The computer program product recited in claim 15, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip plan and the estimation function that inputs the trip plan, wherein the trip information includes the trip plan; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 19. The computer program product recited in claim 15, wherein determining the desired departure temperature includes:
generating, for each of a plurality of test departure temperatures, a plurality of modeled battery data using a battery model associated with the battery; evaluating each of the plurality of modeled battery data using a cost function in order to obtain an evaluated cost function wherein the cost function takes into account at least battery performance and battery degradation; and outputting that test departure temperature from the plurality of test departure temperatures which corresponds to a minimum of the evaluated cost function as the desired departure temperature. 20. The computer program product recited in claim 15, wherein:
the trip information includes a departure time; the computer program product further includes computer instructions for: determining a start time to start the temperature controlling system based at least in part on the departure time and the desired departure temperature; and the temperature controlling system is started at the start time. | A desired departure temperature is determined for a battery, having a temperature, in a vehicle based at least in part on trip information associated with a trip. A temperature controlling system is used to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature.1. A system, comprising:
a processor; and a memory coupled with the processor, wherein the memory is configured to provide the processor with instructions which when executed cause the processor to:
determine a desired departure temperature for a battery, having a temperature, in a vehicle based at least in part on trip information associated with a trip as an input for an estimation function; and
use a temperature controlling system to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. 2. The system recited in claim 1, wherein the trip information includes one or more of the following: a trip duration, a destination, a trip distance, or a trip plan. 3. The system recited in claim 1, wherein determining the desired departure temperature is further based at least in part on one or more of the following: state of health information associated with the battery, an average cell internal resistance, a minimum cell capacity, or ambient temperature. 4. The system recited in claim 1, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip duration and the estimation function that inputs the trip duration, wherein the trip information includes the trip duration; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 5. The system recited in claim 1, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip plan and the estimation function that inputs the trip plan, wherein the trip information includes the trip plan; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 6. The system recited in claim 1, wherein determining the desired departure temperature includes:
generating, for each of a plurality of test departure temperatures, a plurality of modeled battery data using a battery model associated with the battery; evaluating each of the plurality of modeled battery data using a cost function in order to obtain an evaluated cost function wherein the cost function takes into account at least battery performance and battery degradation; and outputting that test departure temperature from the plurality of test departure temperatures which corresponds to a minimum of the evaluated cost function as the desired departure temperature. 7. The system recited in claim 1, wherein:
the trip information includes a departure time; the memory is further configured to provide the processor with instructions which when executed cause the processor to: determine a start time to start the temperature controlling system based at least in part on the departure time and the desired departure temperature; and the temperature controlling system is started at the start time. 8. A method, comprising:
providing trip information associated with a trip as an input to an estimation function; determining a desired departure temperature for a battery, having a temperature, in a vehicle based at least in part on the trip information and the estimation function; and using a temperature controlling system to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. 9. The method recited in claim 8, wherein the trip information includes one or more of the following: a trip duration, a destination, a trip distance, or a trip plan. 10. The method recited in claim 8, wherein determining the desired departure temperature is further based at least in part on one or more of the following: state of health information associated with the battery, an average cell internal resistance, a minimum cell capacity, or ambient temperature. 11. The method recited in claim 8, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip duration and the estimation function that inputs the trip duration, wherein the trip information includes the trip duration; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 12. The method recited in claim 8, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip plan and the estimation function that inputs the trip plan, wherein the trip information includes the trip plan; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 13. The method recited in claim 8, wherein determining the desired departure temperature includes:
generating, for each of a plurality of test departure temperatures, a plurality of modeled battery data using a battery model associated with the battery; evaluating each of the plurality of modeled battery data using a cost function in order to obtain an evaluated cost function wherein the cost function takes into account at least battery performance and battery degradation; and outputting that test departure temperature from the plurality of test departure temperatures which corresponds to a minimum of the evaluated cost function as the desired departure temperature. 14. The method recited in claim 8, wherein:
the trip information includes a departure time; the method further includes: determining a start time to start the temperature controlling system based at least in part on the departure time and the desired departure temperature; and the temperature controlling system is started at the start time. 15. A computer program product, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
providing trip information associated with a trip as an input to an estimation function; determining a desired departure temperature for a battery, having a temperature, in a vehicle based at least in part on the trip information and the estimation function; and using a temperature controlling system to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. 16. The computer program product recited in claim 15, wherein determining the desired departure temperature is further based at least in part on one or more of the following:
state of health information associated with the battery, an average cell internal resistance, a minimum cell capacity, or ambient temperature. 17. The computer program product recited in claim 15, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip duration and the estimation function that inputs the trip duration, wherein the trip information includes the trip duration; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 18. The computer program product recited in claim 15, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip plan and the estimation function that inputs the trip plan, wherein the trip information includes the trip plan; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 19. The computer program product recited in claim 15, wherein determining the desired departure temperature includes:
generating, for each of a plurality of test departure temperatures, a plurality of modeled battery data using a battery model associated with the battery; evaluating each of the plurality of modeled battery data using a cost function in order to obtain an evaluated cost function wherein the cost function takes into account at least battery performance and battery degradation; and outputting that test departure temperature from the plurality of test departure temperatures which corresponds to a minimum of the evaluated cost function as the desired departure temperature. 20. The computer program product recited in claim 15, wherein:
the trip information includes a departure time; the computer program product further includes computer instructions for: determining a start time to start the temperature controlling system based at least in part on the departure time and the desired departure temperature; and the temperature controlling system is started at the start time. | 2,900 |
347,219 | 29,725,966 | 2,924 | A desired departure temperature is determined for a battery, having a temperature, in a vehicle based at least in part on trip information associated with a trip. A temperature controlling system is used to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. | 1. A system, comprising:
a processor; and a memory coupled with the processor, wherein the memory is configured to provide the processor with instructions which when executed cause the processor to:
determine a desired departure temperature for a battery, having a temperature, in a vehicle based at least in part on trip information associated with a trip as an input for an estimation function; and
use a temperature controlling system to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. 2. The system recited in claim 1, wherein the trip information includes one or more of the following: a trip duration, a destination, a trip distance, or a trip plan. 3. The system recited in claim 1, wherein determining the desired departure temperature is further based at least in part on one or more of the following: state of health information associated with the battery, an average cell internal resistance, a minimum cell capacity, or ambient temperature. 4. The system recited in claim 1, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip duration and the estimation function that inputs the trip duration, wherein the trip information includes the trip duration; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 5. The system recited in claim 1, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip plan and the estimation function that inputs the trip plan, wherein the trip information includes the trip plan; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 6. The system recited in claim 1, wherein determining the desired departure temperature includes:
generating, for each of a plurality of test departure temperatures, a plurality of modeled battery data using a battery model associated with the battery; evaluating each of the plurality of modeled battery data using a cost function in order to obtain an evaluated cost function wherein the cost function takes into account at least battery performance and battery degradation; and outputting that test departure temperature from the plurality of test departure temperatures which corresponds to a minimum of the evaluated cost function as the desired departure temperature. 7. The system recited in claim 1, wherein:
the trip information includes a departure time; the memory is further configured to provide the processor with instructions which when executed cause the processor to: determine a start time to start the temperature controlling system based at least in part on the departure time and the desired departure temperature; and the temperature controlling system is started at the start time. 8. A method, comprising:
providing trip information associated with a trip as an input to an estimation function; determining a desired departure temperature for a battery, having a temperature, in a vehicle based at least in part on the trip information and the estimation function; and using a temperature controlling system to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. 9. The method recited in claim 8, wherein the trip information includes one or more of the following: a trip duration, a destination, a trip distance, or a trip plan. 10. The method recited in claim 8, wherein determining the desired departure temperature is further based at least in part on one or more of the following: state of health information associated with the battery, an average cell internal resistance, a minimum cell capacity, or ambient temperature. 11. The method recited in claim 8, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip duration and the estimation function that inputs the trip duration, wherein the trip information includes the trip duration; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 12. The method recited in claim 8, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip plan and the estimation function that inputs the trip plan, wherein the trip information includes the trip plan; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 13. The method recited in claim 8, wherein determining the desired departure temperature includes:
generating, for each of a plurality of test departure temperatures, a plurality of modeled battery data using a battery model associated with the battery; evaluating each of the plurality of modeled battery data using a cost function in order to obtain an evaluated cost function wherein the cost function takes into account at least battery performance and battery degradation; and outputting that test departure temperature from the plurality of test departure temperatures which corresponds to a minimum of the evaluated cost function as the desired departure temperature. 14. The method recited in claim 8, wherein:
the trip information includes a departure time; the method further includes: determining a start time to start the temperature controlling system based at least in part on the departure time and the desired departure temperature; and the temperature controlling system is started at the start time. 15. A computer program product, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
providing trip information associated with a trip as an input to an estimation function; determining a desired departure temperature for a battery, having a temperature, in a vehicle based at least in part on the trip information and the estimation function; and using a temperature controlling system to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. 16. The computer program product recited in claim 15, wherein determining the desired departure temperature is further based at least in part on one or more of the following:
state of health information associated with the battery, an average cell internal resistance, a minimum cell capacity, or ambient temperature. 17. The computer program product recited in claim 15, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip duration and the estimation function that inputs the trip duration, wherein the trip information includes the trip duration; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 18. The computer program product recited in claim 15, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip plan and the estimation function that inputs the trip plan, wherein the trip information includes the trip plan; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 19. The computer program product recited in claim 15, wherein determining the desired departure temperature includes:
generating, for each of a plurality of test departure temperatures, a plurality of modeled battery data using a battery model associated with the battery; evaluating each of the plurality of modeled battery data using a cost function in order to obtain an evaluated cost function wherein the cost function takes into account at least battery performance and battery degradation; and outputting that test departure temperature from the plurality of test departure temperatures which corresponds to a minimum of the evaluated cost function as the desired departure temperature. 20. The computer program product recited in claim 15, wherein:
the trip information includes a departure time; the computer program product further includes computer instructions for: determining a start time to start the temperature controlling system based at least in part on the departure time and the desired departure temperature; and the temperature controlling system is started at the start time. | A desired departure temperature is determined for a battery, having a temperature, in a vehicle based at least in part on trip information associated with a trip. A temperature controlling system is used to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature.1. A system, comprising:
a processor; and a memory coupled with the processor, wherein the memory is configured to provide the processor with instructions which when executed cause the processor to:
determine a desired departure temperature for a battery, having a temperature, in a vehicle based at least in part on trip information associated with a trip as an input for an estimation function; and
use a temperature controlling system to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. 2. The system recited in claim 1, wherein the trip information includes one or more of the following: a trip duration, a destination, a trip distance, or a trip plan. 3. The system recited in claim 1, wherein determining the desired departure temperature is further based at least in part on one or more of the following: state of health information associated with the battery, an average cell internal resistance, a minimum cell capacity, or ambient temperature. 4. The system recited in claim 1, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip duration and the estimation function that inputs the trip duration, wherein the trip information includes the trip duration; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 5. The system recited in claim 1, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip plan and the estimation function that inputs the trip plan, wherein the trip information includes the trip plan; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 6. The system recited in claim 1, wherein determining the desired departure temperature includes:
generating, for each of a plurality of test departure temperatures, a plurality of modeled battery data using a battery model associated with the battery; evaluating each of the plurality of modeled battery data using a cost function in order to obtain an evaluated cost function wherein the cost function takes into account at least battery performance and battery degradation; and outputting that test departure temperature from the plurality of test departure temperatures which corresponds to a minimum of the evaluated cost function as the desired departure temperature. 7. The system recited in claim 1, wherein:
the trip information includes a departure time; the memory is further configured to provide the processor with instructions which when executed cause the processor to: determine a start time to start the temperature controlling system based at least in part on the departure time and the desired departure temperature; and the temperature controlling system is started at the start time. 8. A method, comprising:
providing trip information associated with a trip as an input to an estimation function; determining a desired departure temperature for a battery, having a temperature, in a vehicle based at least in part on the trip information and the estimation function; and using a temperature controlling system to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. 9. The method recited in claim 8, wherein the trip information includes one or more of the following: a trip duration, a destination, a trip distance, or a trip plan. 10. The method recited in claim 8, wherein determining the desired departure temperature is further based at least in part on one or more of the following: state of health information associated with the battery, an average cell internal resistance, a minimum cell capacity, or ambient temperature. 11. The method recited in claim 8, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip duration and the estimation function that inputs the trip duration, wherein the trip information includes the trip duration; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 12. The method recited in claim 8, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip plan and the estimation function that inputs the trip plan, wherein the trip information includes the trip plan; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 13. The method recited in claim 8, wherein determining the desired departure temperature includes:
generating, for each of a plurality of test departure temperatures, a plurality of modeled battery data using a battery model associated with the battery; evaluating each of the plurality of modeled battery data using a cost function in order to obtain an evaluated cost function wherein the cost function takes into account at least battery performance and battery degradation; and outputting that test departure temperature from the plurality of test departure temperatures which corresponds to a minimum of the evaluated cost function as the desired departure temperature. 14. The method recited in claim 8, wherein:
the trip information includes a departure time; the method further includes: determining a start time to start the temperature controlling system based at least in part on the departure time and the desired departure temperature; and the temperature controlling system is started at the start time. 15. A computer program product, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
providing trip information associated with a trip as an input to an estimation function; determining a desired departure temperature for a battery, having a temperature, in a vehicle based at least in part on the trip information and the estimation function; and using a temperature controlling system to bring the temperature of the battery towards the desired departure temperature, wherein the vehicle begins the trip with the battery at the desired departure temperature. 16. The computer program product recited in claim 15, wherein determining the desired departure temperature is further based at least in part on one or more of the following:
state of health information associated with the battery, an average cell internal resistance, a minimum cell capacity, or ambient temperature. 17. The computer program product recited in claim 15, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip duration and the estimation function that inputs the trip duration, wherein the trip information includes the trip duration; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 18. The computer program product recited in claim 15, wherein determining the desired departure temperature includes:
determining a change in battery temperature associated with the trip using a trip plan and the estimation function that inputs the trip plan, wherein the trip information includes the trip plan; and determining the desired departure temperature using the change in battery temperature associated with the trip and a desired battery temperature range. 19. The computer program product recited in claim 15, wherein determining the desired departure temperature includes:
generating, for each of a plurality of test departure temperatures, a plurality of modeled battery data using a battery model associated with the battery; evaluating each of the plurality of modeled battery data using a cost function in order to obtain an evaluated cost function wherein the cost function takes into account at least battery performance and battery degradation; and outputting that test departure temperature from the plurality of test departure temperatures which corresponds to a minimum of the evaluated cost function as the desired departure temperature. 20. The computer program product recited in claim 15, wherein:
the trip information includes a departure time; the computer program product further includes computer instructions for: determining a start time to start the temperature controlling system based at least in part on the departure time and the desired departure temperature; and the temperature controlling system is started at the start time. | 2,900 |
347,220 | 16,805,673 | 2,924 | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables. | 1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables.1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | 2,900 |
347,221 | 29,725,949 | 2,924 | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables. | 1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables.1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | 2,900 |
347,222 | 29,725,955 | 2,911 | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables. | 1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables.1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | 2,900 |
347,223 | 16,873,229 | 2,911 | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables. | 1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables.1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | 2,900 |
347,224 | 29,725,947 | 2,924 | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables. | 1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables.1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | 2,900 |
347,225 | 29,725,985 | 2,924 | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables. | 1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables.1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | 2,900 |
347,226 | 29,725,992 | 2,924 | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables. | 1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables.1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | 2,900 |
347,227 | 29,725,999 | 2,919 | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables. | 1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables.1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | 2,900 |
347,228 | 29,725,957 | 2,919 | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables. | 1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables.1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | 2,900 |
347,229 | 29,725,986 | 2,919 | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables. | 1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables.1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | 2,900 |
347,230 | 29,725,995 | 2,919 | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables. | 1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables.1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | 2,900 |
347,231 | 29,725,980 | 2,919 | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables. | 1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables.1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | 2,900 |
347,232 | 29,725,993 | 2,923 | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables. | 1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables.1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | 2,900 |
347,233 | 29,725,969 | 2,923 | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables. | 1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables.1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | 2,900 |
347,234 | 29,726,000 | 2,923 | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables. | 1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables.1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | 2,900 |
347,235 | 29,725,983 | 2,923 | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables. | 1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables.1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | 2,900 |
347,236 | 29,725,971 | 2,923 | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables. | 1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables.1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | 2,900 |
347,237 | 29,725,974 | 2,923 | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables. | 1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables.1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | 2,900 |
347,238 | 29,725,978 | 2,923 | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables. | 1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | Runtime errors in a source code program are detected in advance of execution by machine learning models. Features representing a context of a runtime error are extracted from source code programs to train a machine learning model, such as a random forest classifier, to predict the likelihood that a code snippet has a particular type of runtime error. The features are extracted from a syntax-type tree representation of each method in a program. A model is generated for distinct runtime errors, such as arithmetic overflow, and conditionally uninitialized variables.1. A system comprising:
one or more processors coupled to a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: obtain, from a source code program, features associated with a first type of runtime error in one or more program statements of the source code program; and use a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent the first type of runtime error, the second one of the classes indicates that the features do not represent the first type of runtime error. 2. The system of claim 1, wherein the first type of runtime error is use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result. 3. The system of claim 1, wherein the first type of runtime error is an arithmetic overflow of an arithmetic operation, the arithmetic operation having one or more operands, one or more operators, and an assigned-to variable. 4. The system of claim 2, wherein the features associated with the first type of runtime error includes name of the method invocation, return type of the method invocation, type of the reference parameter, and argument count. 5. The system of claim 3, wherein the features associated with the first type of runtime error includes type and size data of each of the one or more operands and the assigned-to variable, an order of the one or more operands, and name of each of the one or more operands. 6. The system of claim 1, wherein the random tree classifier includes a first stage and a second stage, wherein the first stage includes a first random forest that is trained on a first subset of the features, a second random forest that is trained on a second subset of the features, and a linear classifier that is trained on all the features, wherein the first subset and the second subset differ. 7. The system of claim 6, wherein the second stage includes a third random forest that is trained on each probability generated from the first random forest, the second random forest, and a linear classifier. 8. A method, comprising:
extracting, on a computing device having at least one processor and a memory, features that represent a context of a use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result in a source code program; inputting the extracted features into a random forest classifier model; and obtaining a label from the random forest classifier model that indicates whether or not the extracted features indicate use of the uninitialized variable represents a runtime error. 9. The method of claim 8, wherein the extracted features include method name, return type of the method invocation, type of the reference parameter, and number of parameters in the method invocation. 10. The method of claim 9, wherein the extracted features include operators of a conditional expression using a return value of the method invocation. 11. The method of claim 8, wherein the random forest classifier model is a two-stage model having a first stage and a second stage, wherein a first stage includes a first random forest that is trained on a first subset of the extracted features, a second random forest that is trained on a second subset of the extracted features, and a linear classifier that is trained on all the extracted features, wherein the first subset and the second subset differ. 12. The method of claim 11, wherein the second stage includes a third random forest that is trained on a probability generated from the first random forest, the second random forest, and the linear classifier. 13. The method of claim 8, further comprising:
generating a syntax-type tree for a function of the source code program; traversing the syntax-tree tree to find a subtree representing use of an uninitialized variable as a reference parameter in a method invocation that returns an integral result; and obtaining the extracted features from the subtree. 14. The method of claim 8, further comprising:
utilizing the random forest classifier in a software development tool. 15. A device, comprising:
a processor and a memory; wherein the processor is configured to perform actions that: obtains, from a method of a source code program, features associated with an arithmetic expression in a function of a source code program; and uses a random forest classifier to classify the features into one of two classes, wherein a first one of the classes indicates that the features represent an arithmetic overflow, the second one of the classes indicates that the features do not represent an arithmetic overflow. 16. The device of claim 15, wherein the features include one or more operand names, types for the one or more operands, sizes of the one or more operands, values of the one or more operands, order of operands, and label. 17. The device of claim 16, wherein the features further include assigned-to type, assigned-to size, and assigned-to variable name. 18. The device of claim 15, wherein the processor is further configured to perform actions that: generate a syntax tree having type information for the function; and
traverse the syntax tree to extract the features. 19. The device of claim 15, wherein the random forest classifier is part of a software development tool. | 2,900 |
347,239 | 16,805,647 | 2,923 | A computer-implemented system for correcting address information. The system may include a memory storing instructions and at least one processor configured to execute the instructions to perform operations. The operations may include requesting an address for normalization from at least one of a current address or a residential history of a user; receiving, from a user device, a user input including requested address information responsive to the request for normalization; searching, based on the user input, a cache to determine whether a refined version of the requested address is available; returning, based on a determination that a refined version of the requested address exists in the cache, a refined address as the normalized address to the user; and beginning to transport a package to the user at the normalized address, by providing instructions to a mobile device associated with a delivery worker, to transport the package to the normalized address. | 1-20. (canceled) 21. A computer-implemented system for correcting address information, the system comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from a user device, an address for normalization, wherein the address is one of a current address or a historical residential address of a user;
compare the normalized address location to a current location of a delivery worker;
if it is determined that the normalized address location does not match the current location of the delivery worker:
transmit a warning to the user device;
correct the normalized address, based on a machine learning process;
store, based on the correction, the corrected normalized address in a database;
provide instructions to the user device to deliver a package to the user at a delivery location based on the normalized address or the corrected normalized address;
generate, by the processor, a learning curve based on the corrected normalized address information,
develop, based on a determination of common differences, a corrective pattern; and
modify, based on the generation of a learning curve and the corrective pattern, a predetermined threshold for correcting inputted address information. 22. The computer-implemented system of claim 21, wherein the at least one processor is further configured to execute the instructions to:
communicate, if it is determined that the normalized address location does match the current location of the delivery worker, a notification to the user that there exist no differences between the normalized address location and the current location of the delivery worker. 23. The computer-implemented system of claim 21, wherein the at least one processor is further configured to execute the instructions to:
communicate, if it is determined that an amount of detected differences between the normalized address location and the current location of the delivery worker exceeds a predetermined threshold, a notification to the user that the normalized address location does not match the current location of the delivery worker. 24. The computer-implemented system of claim 23, wherein the predetermined threshold includes a predetermined number of differences between the normalized address location and the current location of the delivery worker, and wherein the differences include at least one of differences in numbers, street names, zip codes, city names, and district names. 25. The computer-implemented system of claim 21, wherein the location of the delivery worker includes at least one of stored location data, stored map data, region, neighborhood divisions, or a residence title. 26. The computer-implemented system of claim 21, wherein the at least one processor is further configured to execute the instructions to:
compare, while the package is in transit, the normalized address location to address information stored in a database, wherein the database includes a dictionary of address terms. 27. The computer-implemented system of claim 21, wherein the at least one processor is further configured to execute the instructions to:
develop, based on a determination of multiple differences between the normalized address and the current location of the delivery worker, a corrective pattern to correct future user input that includes address information. 28. The computer-implemented system of claim 21, wherein the at least one processor is further configured to execute the instructions to:
receive the user input including requested address information from the user from at least one of a web browser, a mobile device, or a user database. 29. A computer-implemented method for correcting address information, the method comprising:
receiving, from a user device, an address for normalization, wherein the address is one of a current address or a historical residential address of a user; comparing the normalized address location to a current location of a delivery worker; if it is determined that the normalized address location does not match the current location of the delivery worker:
transmitting a warning to the user device;
correcting the normalized address, based on a machine learning process;
storing, based on the correction, the corrected normalized address in a database;
providing instructions to the user device to deliver a package to the user at a delivery location based on the normalized address or the corrected normalized address; generating, by the processor, a learning curve based on the corrected normalized address information, developing, based on a determination of common differences, a corrective pattern; and modifying, based on the generation of a learning curve and the corrective pattern, a predetermined threshold for correcting inputted address information. 30. The computer-implemented method of claim 29, the method comprising:
communicating, if it is determined that the normalized address location does match the current location of the delivery worker, a notification to the user that there exist no differences between the normalized address location and the current location of the delivery worker. 31. The computer-implemented method of claim 29, the method comprising:
communicating, if it is determined that an amount of detected differences between the normalized address location and the current location of the delivery worker exceeds a predetermined threshold, a notification to the user that the normalized address location does not match the current location of the delivery worker. 32. The computer-implemented method of claim 29, the method comprising:
receiving the user input including requested address information from the user from at least one of a web browser, a mobile device, or a user database. 33. The computer-implemented method of claim 29, wherein the location of the delivery worker includes at least one of stored location data, stored map data, region, neighborhood divisions, or a residence title. 34. The computer-implemented method of claim 29, the method comprising:
comparing, while the package is in transit, the normalized address location to address information stored in a database, wherein the database includes a dictionary of address terms. 35. The computer-implemented method of claim 29, wherein the at least one processor is further configured to execute the instructions to:
develop, based on a determination of multiple differences between the normalized address and the current location of the delivery worker, a corrective pattern to correct future user input that includes address information. 36. The computer-implemented method of claim 29, wherein the predetermined threshold includes a predetermined number of differences between the normalized address location and the current location of the delivery worker, and wherein the differences include at least one of differences in numbers, street names, zip codes, city names, and district names. 37. A non-transitory computer readable medium comprising executable instructions that when executed by at least one processing device cause the at least one processing device to correct address information and perform operations comprising:
receiving, from a user device, an address for normalization, wherein the address is one of a current address or a historical residential address of a user; comparing the normalized address location to a current location of a delivery worker; if it is determined that the normalized address location does not match the current location of the delivery worker:
transmitting a warning to the user device;
correcting the normalized address, based on a machine learning process;
storing, based on the correction, the corrected normalized address in a database;
providing instructions to the user device to deliver a package to the user at a delivery location based on the normalized address or the corrected normalized address; generating, by the processor, a learning curve based on the corrected normalized address information, developing, based on a determination of common differences, a corrective pattern; and modifying, based on the generation of a learning curve and the corrective pattern, a predetermined threshold for correcting inputted address information. 38. The non-transitory computer readable medium of claim 37, further comprising:
communicating, if it is determined that the normalized address location does match the current location of the delivery worker, a notification to the user that there exist no differences between the normalized address location and the current location of the delivery worker. 39. The non-transitory computer readable medium of claim 37, further comprising:
communicating, if it is determined that an amount of detected differences between the normalized address location and the current location of the delivery worker exceeds a predetermined threshold, a notification to the user that the normalized address location does not match the current location of the delivery worker. 40. The non-transitory computer readable medium of claim 37, further comprising:
receiving the user input including requested address information from the user from at least one of a web browser, a mobile device, or a user database. | A computer-implemented system for correcting address information. The system may include a memory storing instructions and at least one processor configured to execute the instructions to perform operations. The operations may include requesting an address for normalization from at least one of a current address or a residential history of a user; receiving, from a user device, a user input including requested address information responsive to the request for normalization; searching, based on the user input, a cache to determine whether a refined version of the requested address is available; returning, based on a determination that a refined version of the requested address exists in the cache, a refined address as the normalized address to the user; and beginning to transport a package to the user at the normalized address, by providing instructions to a mobile device associated with a delivery worker, to transport the package to the normalized address.1-20. (canceled) 21. A computer-implemented system for correcting address information, the system comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from a user device, an address for normalization, wherein the address is one of a current address or a historical residential address of a user;
compare the normalized address location to a current location of a delivery worker;
if it is determined that the normalized address location does not match the current location of the delivery worker:
transmit a warning to the user device;
correct the normalized address, based on a machine learning process;
store, based on the correction, the corrected normalized address in a database;
provide instructions to the user device to deliver a package to the user at a delivery location based on the normalized address or the corrected normalized address;
generate, by the processor, a learning curve based on the corrected normalized address information,
develop, based on a determination of common differences, a corrective pattern; and
modify, based on the generation of a learning curve and the corrective pattern, a predetermined threshold for correcting inputted address information. 22. The computer-implemented system of claim 21, wherein the at least one processor is further configured to execute the instructions to:
communicate, if it is determined that the normalized address location does match the current location of the delivery worker, a notification to the user that there exist no differences between the normalized address location and the current location of the delivery worker. 23. The computer-implemented system of claim 21, wherein the at least one processor is further configured to execute the instructions to:
communicate, if it is determined that an amount of detected differences between the normalized address location and the current location of the delivery worker exceeds a predetermined threshold, a notification to the user that the normalized address location does not match the current location of the delivery worker. 24. The computer-implemented system of claim 23, wherein the predetermined threshold includes a predetermined number of differences between the normalized address location and the current location of the delivery worker, and wherein the differences include at least one of differences in numbers, street names, zip codes, city names, and district names. 25. The computer-implemented system of claim 21, wherein the location of the delivery worker includes at least one of stored location data, stored map data, region, neighborhood divisions, or a residence title. 26. The computer-implemented system of claim 21, wherein the at least one processor is further configured to execute the instructions to:
compare, while the package is in transit, the normalized address location to address information stored in a database, wherein the database includes a dictionary of address terms. 27. The computer-implemented system of claim 21, wherein the at least one processor is further configured to execute the instructions to:
develop, based on a determination of multiple differences between the normalized address and the current location of the delivery worker, a corrective pattern to correct future user input that includes address information. 28. The computer-implemented system of claim 21, wherein the at least one processor is further configured to execute the instructions to:
receive the user input including requested address information from the user from at least one of a web browser, a mobile device, or a user database. 29. A computer-implemented method for correcting address information, the method comprising:
receiving, from a user device, an address for normalization, wherein the address is one of a current address or a historical residential address of a user; comparing the normalized address location to a current location of a delivery worker; if it is determined that the normalized address location does not match the current location of the delivery worker:
transmitting a warning to the user device;
correcting the normalized address, based on a machine learning process;
storing, based on the correction, the corrected normalized address in a database;
providing instructions to the user device to deliver a package to the user at a delivery location based on the normalized address or the corrected normalized address; generating, by the processor, a learning curve based on the corrected normalized address information, developing, based on a determination of common differences, a corrective pattern; and modifying, based on the generation of a learning curve and the corrective pattern, a predetermined threshold for correcting inputted address information. 30. The computer-implemented method of claim 29, the method comprising:
communicating, if it is determined that the normalized address location does match the current location of the delivery worker, a notification to the user that there exist no differences between the normalized address location and the current location of the delivery worker. 31. The computer-implemented method of claim 29, the method comprising:
communicating, if it is determined that an amount of detected differences between the normalized address location and the current location of the delivery worker exceeds a predetermined threshold, a notification to the user that the normalized address location does not match the current location of the delivery worker. 32. The computer-implemented method of claim 29, the method comprising:
receiving the user input including requested address information from the user from at least one of a web browser, a mobile device, or a user database. 33. The computer-implemented method of claim 29, wherein the location of the delivery worker includes at least one of stored location data, stored map data, region, neighborhood divisions, or a residence title. 34. The computer-implemented method of claim 29, the method comprising:
comparing, while the package is in transit, the normalized address location to address information stored in a database, wherein the database includes a dictionary of address terms. 35. The computer-implemented method of claim 29, wherein the at least one processor is further configured to execute the instructions to:
develop, based on a determination of multiple differences between the normalized address and the current location of the delivery worker, a corrective pattern to correct future user input that includes address information. 36. The computer-implemented method of claim 29, wherein the predetermined threshold includes a predetermined number of differences between the normalized address location and the current location of the delivery worker, and wherein the differences include at least one of differences in numbers, street names, zip codes, city names, and district names. 37. A non-transitory computer readable medium comprising executable instructions that when executed by at least one processing device cause the at least one processing device to correct address information and perform operations comprising:
receiving, from a user device, an address for normalization, wherein the address is one of a current address or a historical residential address of a user; comparing the normalized address location to a current location of a delivery worker; if it is determined that the normalized address location does not match the current location of the delivery worker:
transmitting a warning to the user device;
correcting the normalized address, based on a machine learning process;
storing, based on the correction, the corrected normalized address in a database;
providing instructions to the user device to deliver a package to the user at a delivery location based on the normalized address or the corrected normalized address; generating, by the processor, a learning curve based on the corrected normalized address information, developing, based on a determination of common differences, a corrective pattern; and modifying, based on the generation of a learning curve and the corrective pattern, a predetermined threshold for correcting inputted address information. 38. The non-transitory computer readable medium of claim 37, further comprising:
communicating, if it is determined that the normalized address location does match the current location of the delivery worker, a notification to the user that there exist no differences between the normalized address location and the current location of the delivery worker. 39. The non-transitory computer readable medium of claim 37, further comprising:
communicating, if it is determined that an amount of detected differences between the normalized address location and the current location of the delivery worker exceeds a predetermined threshold, a notification to the user that the normalized address location does not match the current location of the delivery worker. 40. The non-transitory computer readable medium of claim 37, further comprising:
receiving the user input including requested address information from the user from at least one of a web browser, a mobile device, or a user database. | 2,900 |
347,240 | 16,805,641 | 2,923 | One or more embodiments of the present specification provide blockchain-based data processing methods and apparatuses that are applied to a blockchain network system that includes a node device of a service platform and a node device of a service provider. The method includes sending first transaction data by the blockchain node device of the service platform; obtaining, by the blockchain node device of the service platform, second transaction data where the second transaction data is generated by a blockchain node device of a service provider; checking whether the blockchain node device of the service platform receives the service processing data; executing predetermined service processing data acquisition logic or executing application logic for the service processing data if the blockchain node device of the service platform does not or does, respectively, receive the service processing data. | 1. A computer-implemented method comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 2. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 3. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 4. The computer-implemented method of claim 1, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 5. The computer-implemented method of claim 1, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 6. The computer-implemented method of claim 5, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 7. The computer-implemented method of claim 1, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 9. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 10. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 11. The non-transitory, computer-readable medium of claim 8, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 12. The non-transitory, computer-readable medium of claim 8, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 13. The non-transitory, computer-readable medium of claim 12, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 14. The non-transitory, computer-readable medium of claim 8, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising: generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 16. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 17. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 18. The computer-implemented system of claim 15, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 19. The computer-implemented system of claim 15, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 20. The computer-implemented system of claim 19, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 21. The computer-implemented system of claim 15, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 22. A computer-implemented method comprising:
obtaining, by a blockchain node device of a service provider, first transaction data as part of a first transaction from a block of a blockchain, wherein the first transaction data is generated by a blockchain node device of a service platform based on service handling data of a target service object and is sent to the blockchain, the first transaction data comprises an identifier of the target service object, and the service handling data is generated by the blockchain node device of the service platform and comprises the identifier of the target service object; checking whether the blockchain node device of the service provider receives the service handling data that corresponds to the first transaction and is sent by the blockchain node device of the service platform; executing predetermined service handling data acquisition logic if the blockchain node device of the service provider does not receive the service handling data; or executing service processing logic for the target service object based on the service handling data if the blockchain node device of the service provider receives the service handling data, to generate service processing data of the target service object, wherein the service processing data comprises the identifier of the target service object and at least one piece of attribute data of the target service object; and sending, by the blockchain node device of the service provider, second transaction data as part of a second transaction to the blockchain, wherein the second transaction data is generated based on the service processing data and comprises the identifier and the at least one piece of attribute data of the target service object, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. | One or more embodiments of the present specification provide blockchain-based data processing methods and apparatuses that are applied to a blockchain network system that includes a node device of a service platform and a node device of a service provider. The method includes sending first transaction data by the blockchain node device of the service platform; obtaining, by the blockchain node device of the service platform, second transaction data where the second transaction data is generated by a blockchain node device of a service provider; checking whether the blockchain node device of the service platform receives the service processing data; executing predetermined service processing data acquisition logic or executing application logic for the service processing data if the blockchain node device of the service platform does not or does, respectively, receive the service processing data.1. A computer-implemented method comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 2. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 3. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 4. The computer-implemented method of claim 1, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 5. The computer-implemented method of claim 1, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 6. The computer-implemented method of claim 5, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 7. The computer-implemented method of claim 1, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 9. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 10. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 11. The non-transitory, computer-readable medium of claim 8, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 12. The non-transitory, computer-readable medium of claim 8, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 13. The non-transitory, computer-readable medium of claim 12, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 14. The non-transitory, computer-readable medium of claim 8, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising: generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 16. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 17. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 18. The computer-implemented system of claim 15, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 19. The computer-implemented system of claim 15, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 20. The computer-implemented system of claim 19, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 21. The computer-implemented system of claim 15, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 22. A computer-implemented method comprising:
obtaining, by a blockchain node device of a service provider, first transaction data as part of a first transaction from a block of a blockchain, wherein the first transaction data is generated by a blockchain node device of a service platform based on service handling data of a target service object and is sent to the blockchain, the first transaction data comprises an identifier of the target service object, and the service handling data is generated by the blockchain node device of the service platform and comprises the identifier of the target service object; checking whether the blockchain node device of the service provider receives the service handling data that corresponds to the first transaction and is sent by the blockchain node device of the service platform; executing predetermined service handling data acquisition logic if the blockchain node device of the service provider does not receive the service handling data; or executing service processing logic for the target service object based on the service handling data if the blockchain node device of the service provider receives the service handling data, to generate service processing data of the target service object, wherein the service processing data comprises the identifier of the target service object and at least one piece of attribute data of the target service object; and sending, by the blockchain node device of the service provider, second transaction data as part of a second transaction to the blockchain, wherein the second transaction data is generated based on the service processing data and comprises the identifier and the at least one piece of attribute data of the target service object, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. | 2,900 |
347,241 | 29,725,997 | 2,919 | One or more embodiments of the present specification provide blockchain-based data processing methods and apparatuses that are applied to a blockchain network system that includes a node device of a service platform and a node device of a service provider. The method includes sending first transaction data by the blockchain node device of the service platform; obtaining, by the blockchain node device of the service platform, second transaction data where the second transaction data is generated by a blockchain node device of a service provider; checking whether the blockchain node device of the service platform receives the service processing data; executing predetermined service processing data acquisition logic or executing application logic for the service processing data if the blockchain node device of the service platform does not or does, respectively, receive the service processing data. | 1. A computer-implemented method comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 2. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 3. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 4. The computer-implemented method of claim 1, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 5. The computer-implemented method of claim 1, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 6. The computer-implemented method of claim 5, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 7. The computer-implemented method of claim 1, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 9. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 10. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 11. The non-transitory, computer-readable medium of claim 8, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 12. The non-transitory, computer-readable medium of claim 8, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 13. The non-transitory, computer-readable medium of claim 12, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 14. The non-transitory, computer-readable medium of claim 8, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising: generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 16. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 17. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 18. The computer-implemented system of claim 15, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 19. The computer-implemented system of claim 15, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 20. The computer-implemented system of claim 19, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 21. The computer-implemented system of claim 15, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 22. A computer-implemented method comprising:
obtaining, by a blockchain node device of a service provider, first transaction data as part of a first transaction from a block of a blockchain, wherein the first transaction data is generated by a blockchain node device of a service platform based on service handling data of a target service object and is sent to the blockchain, the first transaction data comprises an identifier of the target service object, and the service handling data is generated by the blockchain node device of the service platform and comprises the identifier of the target service object; checking whether the blockchain node device of the service provider receives the service handling data that corresponds to the first transaction and is sent by the blockchain node device of the service platform; executing predetermined service handling data acquisition logic if the blockchain node device of the service provider does not receive the service handling data; or executing service processing logic for the target service object based on the service handling data if the blockchain node device of the service provider receives the service handling data, to generate service processing data of the target service object, wherein the service processing data comprises the identifier of the target service object and at least one piece of attribute data of the target service object; and sending, by the blockchain node device of the service provider, second transaction data as part of a second transaction to the blockchain, wherein the second transaction data is generated based on the service processing data and comprises the identifier and the at least one piece of attribute data of the target service object, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. | One or more embodiments of the present specification provide blockchain-based data processing methods and apparatuses that are applied to a blockchain network system that includes a node device of a service platform and a node device of a service provider. The method includes sending first transaction data by the blockchain node device of the service platform; obtaining, by the blockchain node device of the service platform, second transaction data where the second transaction data is generated by a blockchain node device of a service provider; checking whether the blockchain node device of the service platform receives the service processing data; executing predetermined service processing data acquisition logic or executing application logic for the service processing data if the blockchain node device of the service platform does not or does, respectively, receive the service processing data.1. A computer-implemented method comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 2. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 3. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 4. The computer-implemented method of claim 1, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 5. The computer-implemented method of claim 1, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 6. The computer-implemented method of claim 5, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 7. The computer-implemented method of claim 1, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 9. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 10. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 11. The non-transitory, computer-readable medium of claim 8, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 12. The non-transitory, computer-readable medium of claim 8, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 13. The non-transitory, computer-readable medium of claim 12, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 14. The non-transitory, computer-readable medium of claim 8, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising: generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 16. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 17. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 18. The computer-implemented system of claim 15, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 19. The computer-implemented system of claim 15, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 20. The computer-implemented system of claim 19, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 21. The computer-implemented system of claim 15, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 22. A computer-implemented method comprising:
obtaining, by a blockchain node device of a service provider, first transaction data as part of a first transaction from a block of a blockchain, wherein the first transaction data is generated by a blockchain node device of a service platform based on service handling data of a target service object and is sent to the blockchain, the first transaction data comprises an identifier of the target service object, and the service handling data is generated by the blockchain node device of the service platform and comprises the identifier of the target service object; checking whether the blockchain node device of the service provider receives the service handling data that corresponds to the first transaction and is sent by the blockchain node device of the service platform; executing predetermined service handling data acquisition logic if the blockchain node device of the service provider does not receive the service handling data; or executing service processing logic for the target service object based on the service handling data if the blockchain node device of the service provider receives the service handling data, to generate service processing data of the target service object, wherein the service processing data comprises the identifier of the target service object and at least one piece of attribute data of the target service object; and sending, by the blockchain node device of the service provider, second transaction data as part of a second transaction to the blockchain, wherein the second transaction data is generated based on the service processing data and comprises the identifier and the at least one piece of attribute data of the target service object, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. | 2,900 |
347,242 | 29,726,005 | 2,919 | One or more embodiments of the present specification provide blockchain-based data processing methods and apparatuses that are applied to a blockchain network system that includes a node device of a service platform and a node device of a service provider. The method includes sending first transaction data by the blockchain node device of the service platform; obtaining, by the blockchain node device of the service platform, second transaction data where the second transaction data is generated by a blockchain node device of a service provider; checking whether the blockchain node device of the service platform receives the service processing data; executing predetermined service processing data acquisition logic or executing application logic for the service processing data if the blockchain node device of the service platform does not or does, respectively, receive the service processing data. | 1. A computer-implemented method comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 2. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 3. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 4. The computer-implemented method of claim 1, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 5. The computer-implemented method of claim 1, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 6. The computer-implemented method of claim 5, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 7. The computer-implemented method of claim 1, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 9. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 10. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 11. The non-transitory, computer-readable medium of claim 8, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 12. The non-transitory, computer-readable medium of claim 8, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 13. The non-transitory, computer-readable medium of claim 12, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 14. The non-transitory, computer-readable medium of claim 8, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising: generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 16. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 17. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 18. The computer-implemented system of claim 15, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 19. The computer-implemented system of claim 15, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 20. The computer-implemented system of claim 19, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 21. The computer-implemented system of claim 15, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 22. A computer-implemented method comprising:
obtaining, by a blockchain node device of a service provider, first transaction data as part of a first transaction from a block of a blockchain, wherein the first transaction data is generated by a blockchain node device of a service platform based on service handling data of a target service object and is sent to the blockchain, the first transaction data comprises an identifier of the target service object, and the service handling data is generated by the blockchain node device of the service platform and comprises the identifier of the target service object; checking whether the blockchain node device of the service provider receives the service handling data that corresponds to the first transaction and is sent by the blockchain node device of the service platform; executing predetermined service handling data acquisition logic if the blockchain node device of the service provider does not receive the service handling data; or executing service processing logic for the target service object based on the service handling data if the blockchain node device of the service provider receives the service handling data, to generate service processing data of the target service object, wherein the service processing data comprises the identifier of the target service object and at least one piece of attribute data of the target service object; and sending, by the blockchain node device of the service provider, second transaction data as part of a second transaction to the blockchain, wherein the second transaction data is generated based on the service processing data and comprises the identifier and the at least one piece of attribute data of the target service object, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. | One or more embodiments of the present specification provide blockchain-based data processing methods and apparatuses that are applied to a blockchain network system that includes a node device of a service platform and a node device of a service provider. The method includes sending first transaction data by the blockchain node device of the service platform; obtaining, by the blockchain node device of the service platform, second transaction data where the second transaction data is generated by a blockchain node device of a service provider; checking whether the blockchain node device of the service platform receives the service processing data; executing predetermined service processing data acquisition logic or executing application logic for the service processing data if the blockchain node device of the service platform does not or does, respectively, receive the service processing data.1. A computer-implemented method comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 2. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 3. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 4. The computer-implemented method of claim 1, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 5. The computer-implemented method of claim 1, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 6. The computer-implemented method of claim 5, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 7. The computer-implemented method of claim 1, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 9. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 10. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 11. The non-transitory, computer-readable medium of claim 8, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 12. The non-transitory, computer-readable medium of claim 8, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 13. The non-transitory, computer-readable medium of claim 12, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 14. The non-transitory, computer-readable medium of claim 8, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising: generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 16. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 17. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 18. The computer-implemented system of claim 15, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 19. The computer-implemented system of claim 15, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 20. The computer-implemented system of claim 19, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 21. The computer-implemented system of claim 15, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 22. A computer-implemented method comprising:
obtaining, by a blockchain node device of a service provider, first transaction data as part of a first transaction from a block of a blockchain, wherein the first transaction data is generated by a blockchain node device of a service platform based on service handling data of a target service object and is sent to the blockchain, the first transaction data comprises an identifier of the target service object, and the service handling data is generated by the blockchain node device of the service platform and comprises the identifier of the target service object; checking whether the blockchain node device of the service provider receives the service handling data that corresponds to the first transaction and is sent by the blockchain node device of the service platform; executing predetermined service handling data acquisition logic if the blockchain node device of the service provider does not receive the service handling data; or executing service processing logic for the target service object based on the service handling data if the blockchain node device of the service provider receives the service handling data, to generate service processing data of the target service object, wherein the service processing data comprises the identifier of the target service object and at least one piece of attribute data of the target service object; and sending, by the blockchain node device of the service provider, second transaction data as part of a second transaction to the blockchain, wherein the second transaction data is generated based on the service processing data and comprises the identifier and the at least one piece of attribute data of the target service object, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. | 2,900 |
347,243 | 29,725,967 | 2,919 | One or more embodiments of the present specification provide blockchain-based data processing methods and apparatuses that are applied to a blockchain network system that includes a node device of a service platform and a node device of a service provider. The method includes sending first transaction data by the blockchain node device of the service platform; obtaining, by the blockchain node device of the service platform, second transaction data where the second transaction data is generated by a blockchain node device of a service provider; checking whether the blockchain node device of the service platform receives the service processing data; executing predetermined service processing data acquisition logic or executing application logic for the service processing data if the blockchain node device of the service platform does not or does, respectively, receive the service processing data. | 1. A computer-implemented method comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 2. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 3. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 4. The computer-implemented method of claim 1, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 5. The computer-implemented method of claim 1, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 6. The computer-implemented method of claim 5, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 7. The computer-implemented method of claim 1, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 9. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 10. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 11. The non-transitory, computer-readable medium of claim 8, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 12. The non-transitory, computer-readable medium of claim 8, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 13. The non-transitory, computer-readable medium of claim 12, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 14. The non-transitory, computer-readable medium of claim 8, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising: generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 16. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 17. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 18. The computer-implemented system of claim 15, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 19. The computer-implemented system of claim 15, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 20. The computer-implemented system of claim 19, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 21. The computer-implemented system of claim 15, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 22. A computer-implemented method comprising:
obtaining, by a blockchain node device of a service provider, first transaction data as part of a first transaction from a block of a blockchain, wherein the first transaction data is generated by a blockchain node device of a service platform based on service handling data of a target service object and is sent to the blockchain, the first transaction data comprises an identifier of the target service object, and the service handling data is generated by the blockchain node device of the service platform and comprises the identifier of the target service object; checking whether the blockchain node device of the service provider receives the service handling data that corresponds to the first transaction and is sent by the blockchain node device of the service platform; executing predetermined service handling data acquisition logic if the blockchain node device of the service provider does not receive the service handling data; or executing service processing logic for the target service object based on the service handling data if the blockchain node device of the service provider receives the service handling data, to generate service processing data of the target service object, wherein the service processing data comprises the identifier of the target service object and at least one piece of attribute data of the target service object; and sending, by the blockchain node device of the service provider, second transaction data as part of a second transaction to the blockchain, wherein the second transaction data is generated based on the service processing data and comprises the identifier and the at least one piece of attribute data of the target service object, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. | One or more embodiments of the present specification provide blockchain-based data processing methods and apparatuses that are applied to a blockchain network system that includes a node device of a service platform and a node device of a service provider. The method includes sending first transaction data by the blockchain node device of the service platform; obtaining, by the blockchain node device of the service platform, second transaction data where the second transaction data is generated by a blockchain node device of a service provider; checking whether the blockchain node device of the service platform receives the service processing data; executing predetermined service processing data acquisition logic or executing application logic for the service processing data if the blockchain node device of the service platform does not or does, respectively, receive the service processing data.1. A computer-implemented method comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 2. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 3. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 4. The computer-implemented method of claim 1, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 5. The computer-implemented method of claim 1, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 6. The computer-implemented method of claim 5, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 7. The computer-implemented method of claim 1, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 9. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 10. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 11. The non-transitory, computer-readable medium of claim 8, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 12. The non-transitory, computer-readable medium of claim 8, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 13. The non-transitory, computer-readable medium of claim 12, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 14. The non-transitory, computer-readable medium of claim 8, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising: generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 16. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 17. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 18. The computer-implemented system of claim 15, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 19. The computer-implemented system of claim 15, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 20. The computer-implemented system of claim 19, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 21. The computer-implemented system of claim 15, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 22. A computer-implemented method comprising:
obtaining, by a blockchain node device of a service provider, first transaction data as part of a first transaction from a block of a blockchain, wherein the first transaction data is generated by a blockchain node device of a service platform based on service handling data of a target service object and is sent to the blockchain, the first transaction data comprises an identifier of the target service object, and the service handling data is generated by the blockchain node device of the service platform and comprises the identifier of the target service object; checking whether the blockchain node device of the service provider receives the service handling data that corresponds to the first transaction and is sent by the blockchain node device of the service platform; executing predetermined service handling data acquisition logic if the blockchain node device of the service provider does not receive the service handling data; or executing service processing logic for the target service object based on the service handling data if the blockchain node device of the service provider receives the service handling data, to generate service processing data of the target service object, wherein the service processing data comprises the identifier of the target service object and at least one piece of attribute data of the target service object; and sending, by the blockchain node device of the service provider, second transaction data as part of a second transaction to the blockchain, wherein the second transaction data is generated based on the service processing data and comprises the identifier and the at least one piece of attribute data of the target service object, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. | 2,900 |
347,244 | 29,725,948 | 2,919 | One or more embodiments of the present specification provide blockchain-based data processing methods and apparatuses that are applied to a blockchain network system that includes a node device of a service platform and a node device of a service provider. The method includes sending first transaction data by the blockchain node device of the service platform; obtaining, by the blockchain node device of the service platform, second transaction data where the second transaction data is generated by a blockchain node device of a service provider; checking whether the blockchain node device of the service platform receives the service processing data; executing predetermined service processing data acquisition logic or executing application logic for the service processing data if the blockchain node device of the service platform does not or does, respectively, receive the service processing data. | 1. A computer-implemented method comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 2. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 3. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 4. The computer-implemented method of claim 1, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 5. The computer-implemented method of claim 1, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 6. The computer-implemented method of claim 5, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 7. The computer-implemented method of claim 1, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 9. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 10. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 11. The non-transitory, computer-readable medium of claim 8, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 12. The non-transitory, computer-readable medium of claim 8, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 13. The non-transitory, computer-readable medium of claim 12, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 14. The non-transitory, computer-readable medium of claim 8, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising: generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 16. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 17. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 18. The computer-implemented system of claim 15, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 19. The computer-implemented system of claim 15, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 20. The computer-implemented system of claim 19, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 21. The computer-implemented system of claim 15, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 22. A computer-implemented method comprising:
obtaining, by a blockchain node device of a service provider, first transaction data as part of a first transaction from a block of a blockchain, wherein the first transaction data is generated by a blockchain node device of a service platform based on service handling data of a target service object and is sent to the blockchain, the first transaction data comprises an identifier of the target service object, and the service handling data is generated by the blockchain node device of the service platform and comprises the identifier of the target service object; checking whether the blockchain node device of the service provider receives the service handling data that corresponds to the first transaction and is sent by the blockchain node device of the service platform; executing predetermined service handling data acquisition logic if the blockchain node device of the service provider does not receive the service handling data; or executing service processing logic for the target service object based on the service handling data if the blockchain node device of the service provider receives the service handling data, to generate service processing data of the target service object, wherein the service processing data comprises the identifier of the target service object and at least one piece of attribute data of the target service object; and sending, by the blockchain node device of the service provider, second transaction data as part of a second transaction to the blockchain, wherein the second transaction data is generated based on the service processing data and comprises the identifier and the at least one piece of attribute data of the target service object, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. | One or more embodiments of the present specification provide blockchain-based data processing methods and apparatuses that are applied to a blockchain network system that includes a node device of a service platform and a node device of a service provider. The method includes sending first transaction data by the blockchain node device of the service platform; obtaining, by the blockchain node device of the service platform, second transaction data where the second transaction data is generated by a blockchain node device of a service provider; checking whether the blockchain node device of the service platform receives the service processing data; executing predetermined service processing data acquisition logic or executing application logic for the service processing data if the blockchain node device of the service platform does not or does, respectively, receive the service processing data.1. A computer-implemented method comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 2. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 3. The computer-implemented method of claim 1, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 4. The computer-implemented method of claim 1, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 5. The computer-implemented method of claim 1, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 6. The computer-implemented method of claim 5, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 7. The computer-implemented method of claim 1, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 9. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 10. The non-transitory, computer-readable medium of claim 8, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 11. The non-transitory, computer-readable medium of claim 8, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 12. The non-transitory, computer-readable medium of claim 8, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 13. The non-transitory, computer-readable medium of claim 12, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 14. The non-transitory, computer-readable medium of claim 8, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising: generating, by a blockchain node device of a service platform, service handling data of a target service object, wherein the service handling data comprises an identifier of the target service object; sending, by the blockchain node device of the service platform, first transaction data, as part of a first transaction, to a blockchain, wherein the first transaction data is generated based on the service handling data, and the first transaction data comprises the identifier of the target service object; obtaining, by the blockchain node device of the service platform, second transaction data, as part of a second transaction, from a block of the blockchain, wherein the second transaction data is generated by a blockchain node device of a service provider, the second transaction data comprising the identifier of the target service object and at least one piece of attribute data of the target service object, wherein the second transaction data is generated based on service processing data, wherein the service processing data, in turn, is generated by the blockchain node device of the service provider based on the service handling data, and wherein the service processing data comprises the identifier of the target service object and the at least one piece of attribute data of the target service object; checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider; and executing predetermined service processing data acquisition logic if the blockchain node device of the service platform does not receive the service processing data, or executing application logic for the service processing data if the blockchain node device of the service platform receives the service processing data,
wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. 16. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
sending an application for obtaining the service processing data to the blockchain node device of the service provider. 17. The computer-implemented system of claim 15, wherein executing predetermined service processing data acquisition logic comprises:
generating the service processing data based on the second transaction. 18. The computer-implemented system of claim 15, further comprising:
generating a transaction record of the target service object based on the first transaction and the second transaction, and the transaction record comprises the identifier of the target service object and transaction identifiers of the first transaction and the second transaction; and wherein, checking whether the blockchain node device of the service platform receives the service processing data that corresponds to the second transaction and is sent by the blockchain node device of the service provider comprises checking, based on the transaction record, whether the blockchain node device of the service platform receives the service processing data sent by the blockchain node device of the service provider. 19. The computer-implemented system of claim 15, wherein a third node device in the blockchain uses the first transaction data to establish a data set corresponding to the target service object in a world state database of the blockchain based on the first transaction after being recorded in a first block of the blockchain, and the data set comprises the identifier of the target service object, and
the third node device in the blockchain uses the second transaction to update the data set corresponding to the target service object in the world state database of the blockchain based on the second transaction after being recorded in a second block of the blockchain, and an updated data set comprises the identifier and the at least one piece of attribute data of the target service object. 20. The computer-implemented system of claim 19, wherein executing predetermined service processing data acquisition logic comprises generating the service processing data based on the data set corresponding to the target service object. 21. The computer-implemented system of claim 15, wherein the blockchain is a consortium blockchain, and the blockchain node device of the service platform and the blockchain node device of the service provider are node devices of consortium members in the consortium blockchain. 22. A computer-implemented method comprising:
obtaining, by a blockchain node device of a service provider, first transaction data as part of a first transaction from a block of a blockchain, wherein the first transaction data is generated by a blockchain node device of a service platform based on service handling data of a target service object and is sent to the blockchain, the first transaction data comprises an identifier of the target service object, and the service handling data is generated by the blockchain node device of the service platform and comprises the identifier of the target service object; checking whether the blockchain node device of the service provider receives the service handling data that corresponds to the first transaction and is sent by the blockchain node device of the service platform; executing predetermined service handling data acquisition logic if the blockchain node device of the service provider does not receive the service handling data; or executing service processing logic for the target service object based on the service handling data if the blockchain node device of the service provider receives the service handling data, to generate service processing data of the target service object, wherein the service processing data comprises the identifier of the target service object and at least one piece of attribute data of the target service object; and sending, by the blockchain node device of the service provider, second transaction data as part of a second transaction to the blockchain, wherein the second transaction data is generated based on the service processing data and comprises the identifier and the at least one piece of attribute data of the target service object, wherein the blockchain node device of the service platform and the blockchain node device of the service provider are part of a blockchain network system. | 2,900 |
347,245 | 16,805,672 | 2,919 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,246 | 29,725,975 | 2,919 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,247 | 29,726,046 | 2,912 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,248 | 29,726,019 | 2,912 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,249 | 29,726,020 | 2,912 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,250 | 29,726,037 | 2,912 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,251 | 29,726,039 | 2,912 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,252 | 29,725,965 | 2,912 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,253 | 29,726,026 | 2,912 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,254 | 29,725,970 | 2,912 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,255 | 29,726,022 | 2,912 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,256 | 29,726,013 | 2,912 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,257 | 29,726,042 | 2,912 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,258 | 29,726,033 | 2,926 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,259 | 29,726,029 | 2,926 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,260 | 29,726,015 | 2,926 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,261 | 29,726,031 | 2,921 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,262 | 29,725,963 | 2,921 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,263 | 29,725,960 | 2,921 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,264 | 29,725,987 | 2,921 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,265 | 29,726,003 | 2,921 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,266 | 29,726,014 | 2,915 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,267 | 16,805,676 | 2,915 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,268 | 29,725,984 | 2,915 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,269 | 29,726,048 | 2,915 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,270 | 29,726,002 | 2,911 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,271 | 29,725,988 | 2,911 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,272 | 29,725,953 | 2,911 | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element. | 1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | A cartridge may include a cartridge housing, a reservoir and a wick housing disposed inside the cartridge housing, a heating element, and a wicking element. The cartridge housing may be configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device. The reservoir may be configured to contain a vaporizable material. The heating element may include a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing. The contact portion may include cartridge contacts that form an electric coupling with receptacle contacts in the receptacle. The wicking element may be disposed within the wick housing and proximate to the heating portion of the heating element. The wicking element may be configured to draw the vaporizable material to the wick housing for vaporization by the heating element.1. A cartridge for a vaporizer device, the cartridge comprising:
a cartridge housing, the cartridge housing configured to extend below an open top of a receptacle in the vaporizer device when the cartridge is coupled with the vaporizer device; a reservoir disposed within the cartridge housing, the reservoir configured to contain a vaporizable material; a wick housing disposed within the cartridge housing; a heating element, the heating element including a heating portion disposed at least partially inside the wick housing and a contact portion disposed at least partially outside the wick housing, the contact portion including one or more cartridge contacts configured to form an electric coupling with one or more receptacle contacts in the receptacle of the vaporizer device; and a wicking element disposed within the wick housing and proximate to the heating portion of the heating element, the wicking element configured to draw the vaporizable material from the reservoir to the wick housing for vaporization by the heating element. 2. The cartridge of claim 1, wherein the contact portion is further configured to form a mechanical coupling with the receptacle of the vaporizer device, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 3. The cartridge of claim 1, wherein the receptacle comprises a first portion of a body of the vaporizer device having a smaller cross-sectional dimension than a second portion of the body of the vaporizer device, and wherein a recessed area is formed between the cartridge housing and the second portion of the body of the vaporizer device when the cartridge is coupled with the vaporizer device. 4. The cartridge of claim 3, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 5. The cartridge of claim 4, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 6. The cartridge of claim 4, wherein an interior of each of the one or more slots include at least one step formed by an inner dimension of the one or more slots being less than a dimension of the one or more slots at the bottom of the wick housing, and wherein the at least one step provides a constriction point at which a meniscus forms to prevent the vaporizable material in the wick housing from flowing out of the one or more slots. 7. The cartridge of claim 6, wherein the dimension of the one or more slots at the bottom of the wick housing is approximately 1.2 millimeters long by 0.5 millimeters wide, and wherein the inner dimension of the one or more slots is approximately 1.0 millimeters long by 0.30 millimeters wide. 8. The cartridge of claim 1, wherein the heating portion of the heating element and the contact portion of the heating element are formed by folding a substrate material, wherein the substrate material is cut to include one or more tines for forming the heating portion of the heating element, and wherein the substrate material is further cut to include one or more legs for forming the contact portion of the heating element. 9. The cartridge of claim 7, wherein the contact portion of the heating element is formed by folding each of the one or more legs to form at least a first joint, a second joint, and a third joint, wherein the first joint is disposed between the second joint and the third joint, and wherein the second joint is disposed between a tip of each of the one or more legs and the first joint. 10. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the second joint, wherein the heating element is secured to the wicking housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the first joint and the third joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the second joint and the receptacle of the vaporizer device. 11. The cartridge of claim 8, wherein the one or more cartridge contacts are disposed at the first joint, wherein the heating element is secured to the wick housing by a first mechanical coupling between an exterior of the wick housing and a portion of each of the one or more legs between the tip and the second joint, and wherein the cartridge is secured to the receptacle of the vaporizer device by a second mechanical coupling between the first joint and the receptacle of the vaporizer device. 12. The cartridge of claim 1, wherein the reservoir includes a storage chamber and a collector, wherein the collector comprises an overflow channel configured to retain a volume of the vaporizable material in fluid contact with the storage chamber, wherein one or more microfluidic features are disposed along a length of the overflow channel, and wherein each of the one or more microfluidic features are configured to provide a constriction point at which a meniscus forms to prevent air entering the reservoir from passing the vaporizable material in the overflow channel. 13. The cartridge of claim 11, wherein the cartridge housing includes an airflow passageway leading to an outlet for an aerosol that is formed by the heating element vaporizing the vaporizable material, wherein the collector includes a central tunnel in fluid communication with the airflow passageway, and wherein a bottom surface of the collector includes a flow controller configured to mix the aerosol generated by the heating element vaporizing the vaporizable material. 14. The cartridge of claim 12, wherein an interior surface of the airflow passageway includes one or more channels that extend from the outlet to the wicking element, and wherein the one or more channels are configured to collect a condensate formed by the aerosol and direct at least a portion the collected condensate towards the wicking element. 15. The cartridge of claim 12, wherein the flow controller includes a first channel and a second channel, wherein the first channel is offset from the second channel, and wherein a first interior surface of the first channel is sloped in a different direction from a second interior surface of the second channel to direct a first column of the aerosol entering the central tunnel through the first channel in a different direction than a second column of the aerosol entering the central tunnel through the second channel. 16. The cartridge of claim 12, wherein the bottom surface of the controller further includes one or more wick interfaces, wherein the one or more wick interfaces are in fluid communication with one or more wick feeds in the collector, and wherein the one or more wick feeds are configured to deliver, to the wicking element disposed in the wick housing, at least a portion of the vaporizable material contained in the storage chamber. 17. The cartridge of claim 1, wherein the wick housing is disposed at least partially inside the receptacle of the vaporizer device when the cartridge is coupled with the vaporizer device, wherein a flange is disposed at least partially around an upper perimeter of the wick housing, and wherein the flange extends over at least a portion of a rim of the cartridge receptacle. 18. A vaporizer device, the vaporizer device comprising:
a receptacle comprising a first portion of a body of the vaporizer device, the receptacle including one or more receptacle contacts, the receptacle configured to receive a wick housing of a cartridge containing a vaporizable material when the cartridge is coupled with the vaporizer device, a housing of the cartridge extending below an open top of the receptacle when the cartridge is coupled with the vaporizer device, the one or more receptacle contacts configured to form an electric coupling with one or more cartridge contacts comprising a contact portion of a heating element in the cartridge, the contact portion disposed at least partially outside the wick housing; a power source disposed at least partially within a second portion of the body of the vaporizer device; and a controller configured to control a discharge of an electric current from the power source to the heating element included in the cartridge when the cartridge is coupled with the vaporizer device, the electric current being discharged to the heating element to vaporize at least a portion of the vaporizable material saturating a wicking element disposed within the wick housing and proximate to a heating portion of the heating element. 19. The vaporizer device of claim 18, wherein the receptacle is further configured to form a mechanical coupling with the contact portion of the heating element, and wherein the mechanical coupling secures the cartridge in the receptacle of the vaporizer device. 20. The vaporizer device of claim 18, wherein the first portion of the body of the vaporizer device has a smaller cross-sectional dimension than the second portion of the body of the vaporizer device, and wherein a recessed area is formed between the second portion of the body of the vaporizer device and the cartridge housing when the cartridge is coupled with the vaporizer device. 21. The vaporizer device of claim 20, wherein the receptacle includes one or more air inlets that form a fluid coupling with one or more slots in a bottom of the wick housing when the cartridge is coupled with the vaporizer device, wherein the one or more slots are configured to allow air entering the one or more air inlets to further enter the wick housing, and wherein the one or more air inlets are disposed in the recessed area. 22. The vaporizer device of claim 20, wherein the one or more air inlets have a diameter between approximately 0.6 millimeters and 1.0 millimeters. 23. The vaporizer device of claim 18, wherein the receptacle is disposed within the first portion of the body of the vaporizer device such that a top rim of the receptacle is substantially flush with a top rim of the first portion of the body of the vaporizer device. 24. The vaporizer device of claim 23, wherein the receptacle is configured receive a portion of the wick housing such that a flange disposed at least partially around an upper perimeter of the wick housing extends over at least a portion of the top rim of the cartridge receptacle and/or the top rim of the first portion of the body of the vaporizer device. 25. The vaporizer device of claim 18, wherein the receptacle is approximately 4.5 millimeters deep. | 2,900 |
347,273 | 16,805,649 | 2,911 | A computer-implemented method includes: receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, in which the authorization request includes a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, in which the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information including the user identifier and the ledger identifier to the service end. | 1. A computer-implemented method comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 2. The computer-implemented method of claim 1, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 3. The computer-implemented method of claim 1, further comprising:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 4. The computer-implemented method of claim 3, further comprising obtaining public key information of the service end,
wherein the first data record comprises the public key information of the service end. 5. The computer-implemented method of claim 3, further comprising:
sending a hash value of the first data record to the client and to the service end. 6. The computer-implemented method of claim 1, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 7. The computer-implemented method of claim 1, further comprising:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 9. The computer-readable medium of claim 8, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 10. The computer-readable medium of claim 8, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 11. The computer-readable medium of claim 10, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 12. The computer-readable medium of claim 10, wherein the operations further comprise:
sending a hash value of the first data record to the client and to the service end. 13. The computer-readable medium of claim 8, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 14. The computer-readable medium of claim 8, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier;
determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request;
cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and
sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier;
generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request;
authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier;
configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and
sending authorization information comprising the user identifier and the ledger identifier to the service end. 16. The computer-implemented system of claim 15, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 17. The computer-implemented system of claim 15, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 18. The computer-implemented system of claim 17, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 19. The computer-implemented system of claim 15, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 20. The computer-implemented system of claim 15, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. | A computer-implemented method includes: receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, in which the authorization request includes a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, in which the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information including the user identifier and the ledger identifier to the service end.1. A computer-implemented method comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 2. The computer-implemented method of claim 1, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 3. The computer-implemented method of claim 1, further comprising:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 4. The computer-implemented method of claim 3, further comprising obtaining public key information of the service end,
wherein the first data record comprises the public key information of the service end. 5. The computer-implemented method of claim 3, further comprising:
sending a hash value of the first data record to the client and to the service end. 6. The computer-implemented method of claim 1, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 7. The computer-implemented method of claim 1, further comprising:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 9. The computer-readable medium of claim 8, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 10. The computer-readable medium of claim 8, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 11. The computer-readable medium of claim 10, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 12. The computer-readable medium of claim 10, wherein the operations further comprise:
sending a hash value of the first data record to the client and to the service end. 13. The computer-readable medium of claim 8, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 14. The computer-readable medium of claim 8, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier;
determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request;
cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and
sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier;
generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request;
authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier;
configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and
sending authorization information comprising the user identifier and the ledger identifier to the service end. 16. The computer-implemented system of claim 15, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 17. The computer-implemented system of claim 15, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 18. The computer-implemented system of claim 17, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 19. The computer-implemented system of claim 15, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 20. The computer-implemented system of claim 15, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. | 2,900 |
347,274 | 29,725,981 | 2,911 | A computer-implemented method includes: receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, in which the authorization request includes a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, in which the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information including the user identifier and the ledger identifier to the service end. | 1. A computer-implemented method comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 2. The computer-implemented method of claim 1, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 3. The computer-implemented method of claim 1, further comprising:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 4. The computer-implemented method of claim 3, further comprising obtaining public key information of the service end,
wherein the first data record comprises the public key information of the service end. 5. The computer-implemented method of claim 3, further comprising:
sending a hash value of the first data record to the client and to the service end. 6. The computer-implemented method of claim 1, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 7. The computer-implemented method of claim 1, further comprising:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 9. The computer-readable medium of claim 8, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 10. The computer-readable medium of claim 8, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 11. The computer-readable medium of claim 10, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 12. The computer-readable medium of claim 10, wherein the operations further comprise:
sending a hash value of the first data record to the client and to the service end. 13. The computer-readable medium of claim 8, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 14. The computer-readable medium of claim 8, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier;
determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request;
cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and
sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier;
generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request;
authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier;
configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and
sending authorization information comprising the user identifier and the ledger identifier to the service end. 16. The computer-implemented system of claim 15, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 17. The computer-implemented system of claim 15, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 18. The computer-implemented system of claim 17, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 19. The computer-implemented system of claim 15, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 20. The computer-implemented system of claim 15, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. | A computer-implemented method includes: receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, in which the authorization request includes a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, in which the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information including the user identifier and the ledger identifier to the service end.1. A computer-implemented method comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 2. The computer-implemented method of claim 1, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 3. The computer-implemented method of claim 1, further comprising:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 4. The computer-implemented method of claim 3, further comprising obtaining public key information of the service end,
wherein the first data record comprises the public key information of the service end. 5. The computer-implemented method of claim 3, further comprising:
sending a hash value of the first data record to the client and to the service end. 6. The computer-implemented method of claim 1, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 7. The computer-implemented method of claim 1, further comprising:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 9. The computer-readable medium of claim 8, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 10. The computer-readable medium of claim 8, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 11. The computer-readable medium of claim 10, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 12. The computer-readable medium of claim 10, wherein the operations further comprise:
sending a hash value of the first data record to the client and to the service end. 13. The computer-readable medium of claim 8, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 14. The computer-readable medium of claim 8, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier;
determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request;
cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and
sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier;
generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request;
authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier;
configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and
sending authorization information comprising the user identifier and the ledger identifier to the service end. 16. The computer-implemented system of claim 15, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 17. The computer-implemented system of claim 15, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 18. The computer-implemented system of claim 17, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 19. The computer-implemented system of claim 15, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 20. The computer-implemented system of claim 15, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. | 2,900 |
347,275 | 29,725,976 | 2,911 | A computer-implemented method includes: receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, in which the authorization request includes a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, in which the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information including the user identifier and the ledger identifier to the service end. | 1. A computer-implemented method comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 2. The computer-implemented method of claim 1, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 3. The computer-implemented method of claim 1, further comprising:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 4. The computer-implemented method of claim 3, further comprising obtaining public key information of the service end,
wherein the first data record comprises the public key information of the service end. 5. The computer-implemented method of claim 3, further comprising:
sending a hash value of the first data record to the client and to the service end. 6. The computer-implemented method of claim 1, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 7. The computer-implemented method of claim 1, further comprising:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 9. The computer-readable medium of claim 8, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 10. The computer-readable medium of claim 8, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 11. The computer-readable medium of claim 10, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 12. The computer-readable medium of claim 10, wherein the operations further comprise:
sending a hash value of the first data record to the client and to the service end. 13. The computer-readable medium of claim 8, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 14. The computer-readable medium of claim 8, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier;
determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request;
cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and
sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier;
generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request;
authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier;
configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and
sending authorization information comprising the user identifier and the ledger identifier to the service end. 16. The computer-implemented system of claim 15, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 17. The computer-implemented system of claim 15, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 18. The computer-implemented system of claim 17, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 19. The computer-implemented system of claim 15, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 20. The computer-implemented system of claim 15, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. | A computer-implemented method includes: receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, in which the authorization request includes a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, in which the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information including the user identifier and the ledger identifier to the service end.1. A computer-implemented method comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 2. The computer-implemented method of claim 1, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 3. The computer-implemented method of claim 1, further comprising:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 4. The computer-implemented method of claim 3, further comprising obtaining public key information of the service end,
wherein the first data record comprises the public key information of the service end. 5. The computer-implemented method of claim 3, further comprising:
sending a hash value of the first data record to the client and to the service end. 6. The computer-implemented method of claim 1, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 7. The computer-implemented method of claim 1, further comprising:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 9. The computer-readable medium of claim 8, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 10. The computer-readable medium of claim 8, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 11. The computer-readable medium of claim 10, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 12. The computer-readable medium of claim 10, wherein the operations further comprise:
sending a hash value of the first data record to the client and to the service end. 13. The computer-readable medium of claim 8, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 14. The computer-readable medium of claim 8, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier;
determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request;
cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and
sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier;
generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request;
authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier;
configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and
sending authorization information comprising the user identifier and the ledger identifier to the service end. 16. The computer-implemented system of claim 15, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 17. The computer-implemented system of claim 15, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 18. The computer-implemented system of claim 17, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 19. The computer-implemented system of claim 15, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 20. The computer-implemented system of claim 15, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. | 2,900 |
347,276 | 29,725,998 | 2,911 | A computer-implemented method includes: receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, in which the authorization request includes a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, in which the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information including the user identifier and the ledger identifier to the service end. | 1. A computer-implemented method comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 2. The computer-implemented method of claim 1, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 3. The computer-implemented method of claim 1, further comprising:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 4. The computer-implemented method of claim 3, further comprising obtaining public key information of the service end,
wherein the first data record comprises the public key information of the service end. 5. The computer-implemented method of claim 3, further comprising:
sending a hash value of the first data record to the client and to the service end. 6. The computer-implemented method of claim 1, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 7. The computer-implemented method of claim 1, further comprising:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 9. The computer-readable medium of claim 8, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 10. The computer-readable medium of claim 8, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 11. The computer-readable medium of claim 10, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 12. The computer-readable medium of claim 10, wherein the operations further comprise:
sending a hash value of the first data record to the client and to the service end. 13. The computer-readable medium of claim 8, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 14. The computer-readable medium of claim 8, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier;
determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request;
cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and
sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier;
generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request;
authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier;
configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and
sending authorization information comprising the user identifier and the ledger identifier to the service end. 16. The computer-implemented system of claim 15, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 17. The computer-implemented system of claim 15, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 18. The computer-implemented system of claim 17, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 19. The computer-implemented system of claim 15, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 20. The computer-implemented system of claim 15, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. | A computer-implemented method includes: receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, in which the authorization request includes a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, in which the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information including the user identifier and the ledger identifier to the service end.1. A computer-implemented method comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 2. The computer-implemented method of claim 1, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 3. The computer-implemented method of claim 1, further comprising:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 4. The computer-implemented method of claim 3, further comprising obtaining public key information of the service end,
wherein the first data record comprises the public key information of the service end. 5. The computer-implemented method of claim 3, further comprising:
sending a hash value of the first data record to the client and to the service end. 6. The computer-implemented method of claim 1, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 7. The computer-implemented method of claim 1, further comprising:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 9. The computer-readable medium of claim 8, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 10. The computer-readable medium of claim 8, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 11. The computer-readable medium of claim 10, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 12. The computer-readable medium of claim 10, wherein the operations further comprise:
sending a hash value of the first data record to the client and to the service end. 13. The computer-readable medium of claim 8, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 14. The computer-readable medium of claim 8, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier;
determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request;
cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and
sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier;
generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request;
authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier;
configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and
sending authorization information comprising the user identifier and the ledger identifier to the service end. 16. The computer-implemented system of claim 15, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 17. The computer-implemented system of claim 15, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 18. The computer-implemented system of claim 17, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 19. The computer-implemented system of claim 15, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 20. The computer-implemented system of claim 15, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. | 2,900 |
347,277 | 29,726,069 | 2,911 | A computer-implemented method includes: receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, in which the authorization request includes a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, in which the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information including the user identifier and the ledger identifier to the service end. | 1. A computer-implemented method comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 2. The computer-implemented method of claim 1, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 3. The computer-implemented method of claim 1, further comprising:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 4. The computer-implemented method of claim 3, further comprising obtaining public key information of the service end,
wherein the first data record comprises the public key information of the service end. 5. The computer-implemented method of claim 3, further comprising:
sending a hash value of the first data record to the client and to the service end. 6. The computer-implemented method of claim 1, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 7. The computer-implemented method of claim 1, further comprising:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 9. The computer-readable medium of claim 8, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 10. The computer-readable medium of claim 8, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 11. The computer-readable medium of claim 10, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 12. The computer-readable medium of claim 10, wherein the operations further comprise:
sending a hash value of the first data record to the client and to the service end. 13. The computer-readable medium of claim 8, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 14. The computer-readable medium of claim 8, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier;
determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request;
cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and
sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier;
generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request;
authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier;
configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and
sending authorization information comprising the user identifier and the ledger identifier to the service end. 16. The computer-implemented system of claim 15, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 17. The computer-implemented system of claim 15, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 18. The computer-implemented system of claim 17, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 19. The computer-implemented system of claim 15, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 20. The computer-implemented system of claim 15, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. | A computer-implemented method includes: receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, in which the authorization request includes a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, in which the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information including the user identifier and the ledger identifier to the service end.1. A computer-implemented method comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 2. The computer-implemented method of claim 1, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 3. The computer-implemented method of claim 1, further comprising:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 4. The computer-implemented method of claim 3, further comprising obtaining public key information of the service end,
wherein the first data record comprises the public key information of the service end. 5. The computer-implemented method of claim 3, further comprising:
sending a hash value of the first data record to the client and to the service end. 6. The computer-implemented method of claim 1, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 7. The computer-implemented method of claim 1, further comprising:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 9. The computer-readable medium of claim 8, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 10. The computer-readable medium of claim 8, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 11. The computer-readable medium of claim 10, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 12. The computer-readable medium of claim 10, wherein the operations further comprise:
sending a hash value of the first data record to the client and to the service end. 13. The computer-readable medium of claim 8, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 14. The computer-readable medium of claim 8, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier;
determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request;
cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and
sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier;
generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request;
authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier;
configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and
sending authorization information comprising the user identifier and the ledger identifier to the service end. 16. The computer-implemented system of claim 15, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 17. The computer-implemented system of claim 15, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 18. The computer-implemented system of claim 17, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 19. The computer-implemented system of claim 15, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 20. The computer-implemented system of claim 15, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. | 2,900 |
347,278 | 29,726,080 | 2,917 | A computer-implemented method includes: receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, in which the authorization request includes a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, in which the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information including the user identifier and the ledger identifier to the service end. | 1. A computer-implemented method comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 2. The computer-implemented method of claim 1, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 3. The computer-implemented method of claim 1, further comprising:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 4. The computer-implemented method of claim 3, further comprising obtaining public key information of the service end,
wherein the first data record comprises the public key information of the service end. 5. The computer-implemented method of claim 3, further comprising:
sending a hash value of the first data record to the client and to the service end. 6. The computer-implemented method of claim 1, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 7. The computer-implemented method of claim 1, further comprising:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 9. The computer-readable medium of claim 8, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 10. The computer-readable medium of claim 8, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 11. The computer-readable medium of claim 10, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 12. The computer-readable medium of claim 10, wherein the operations further comprise:
sending a hash value of the first data record to the client and to the service end. 13. The computer-readable medium of claim 8, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 14. The computer-readable medium of claim 8, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier;
determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request;
cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and
sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier;
generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request;
authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier;
configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and
sending authorization information comprising the user identifier and the ledger identifier to the service end. 16. The computer-implemented system of claim 15, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 17. The computer-implemented system of claim 15, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 18. The computer-implemented system of claim 17, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 19. The computer-implemented system of claim 15, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 20. The computer-implemented system of claim 15, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. | A computer-implemented method includes: receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, in which the authorization request includes a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, in which the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information including the user identifier and the ledger identifier to the service end.1. A computer-implemented method comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 2. The computer-implemented method of claim 1, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 3. The computer-implemented method of claim 1, further comprising:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 4. The computer-implemented method of claim 3, further comprising obtaining public key information of the service end,
wherein the first data record comprises the public key information of the service end. 5. The computer-implemented method of claim 3, further comprising:
sending a hash value of the first data record to the client and to the service end. 6. The computer-implemented method of claim 1, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 7. The computer-implemented method of claim 1, further comprising:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 9. The computer-readable medium of claim 8, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 10. The computer-readable medium of claim 8, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 11. The computer-readable medium of claim 10, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 12. The computer-readable medium of claim 10, wherein the operations further comprise:
sending a hash value of the first data record to the client and to the service end. 13. The computer-readable medium of claim 8, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 14. The computer-readable medium of claim 8, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier;
determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request;
cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and
sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier;
generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request;
authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier;
configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and
sending authorization information comprising the user identifier and the ledger identifier to the service end. 16. The computer-implemented system of claim 15, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 17. The computer-implemented system of claim 15, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 18. The computer-implemented system of claim 17, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 19. The computer-implemented system of claim 15, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 20. The computer-implemented system of claim 15, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. | 2,900 |
347,279 | 29,726,049 | 2,917 | A computer-implemented method includes: receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, in which the authorization request includes a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, in which the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information including the user identifier and the ledger identifier to the service end. | 1. A computer-implemented method comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 2. The computer-implemented method of claim 1, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 3. The computer-implemented method of claim 1, further comprising:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 4. The computer-implemented method of claim 3, further comprising obtaining public key information of the service end,
wherein the first data record comprises the public key information of the service end. 5. The computer-implemented method of claim 3, further comprising:
sending a hash value of the first data record to the client and to the service end. 6. The computer-implemented method of claim 1, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 7. The computer-implemented method of claim 1, further comprising:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 9. The computer-readable medium of claim 8, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 10. The computer-readable medium of claim 8, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 11. The computer-readable medium of claim 10, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 12. The computer-readable medium of claim 10, wherein the operations further comprise:
sending a hash value of the first data record to the client and to the service end. 13. The computer-readable medium of claim 8, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 14. The computer-readable medium of claim 8, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier;
determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request;
cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and
sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier;
generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request;
authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier;
configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and
sending authorization information comprising the user identifier and the ledger identifier to the service end. 16. The computer-implemented system of claim 15, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 17. The computer-implemented system of claim 15, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 18. The computer-implemented system of claim 17, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 19. The computer-implemented system of claim 15, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 20. The computer-implemented system of claim 15, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. | A computer-implemented method includes: receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, in which the authorization request includes a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, in which the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information including the user identifier and the ledger identifier to the service end.1. A computer-implemented method comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 2. The computer-implemented method of claim 1, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 3. The computer-implemented method of claim 1, further comprising:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 4. The computer-implemented method of claim 3, further comprising obtaining public key information of the service end,
wherein the first data record comprises the public key information of the service end. 5. The computer-implemented method of claim 3, further comprising:
sending a hash value of the first data record to the client and to the service end. 6. The computer-implemented method of claim 1, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 7. The computer-implemented method of claim 1, further comprising:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information comprising the user identifier and the ledger identifier to the service end. 9. The computer-readable medium of claim 8, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 10. The computer-readable medium of claim 8, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 11. The computer-readable medium of claim 10, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 12. The computer-readable medium of claim 10, wherein the operations further comprise:
sending a hash value of the first data record to the client and to the service end. 13. The computer-readable medium of claim 8, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 14. The computer-readable medium of claim 8, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier;
determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request;
cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and
sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. 15. A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:
receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier;
generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request;
authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier;
configuring a permission value of the user in the blockchain ledger, wherein the permission value determines a degree to which the service end can operate the blockchain ledger; and
sending authorization information comprising the user identifier and the ledger identifier to the service end. 16. The computer-implemented system of claim 15, wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and writing the public key information of the service end into a permission configuration file corresponding to the blockchain ledger. 17. The computer-implemented system of claim 15, wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and writing the first data record into the blockchain ledger corresponding to the ledger identifier. 18. The computer-implemented system of claim 17, wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end. 19. The computer-implemented system of claim 15, wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier and the ledger identifier is written into an operable ledger list stored at the service end. 20. The computer-implemented system of claim 15, wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises a second service end identifier and a second user identifier; determining a database de-authorization instruction based on the de-authorization request and a second ledger identifier based on the de-authorization request; cancelling, in a second blockchain ledger corresponding to the second ledger identifier, operation permissions of a second service end corresponding to the second service end identifier; and sending, to the second service end, de-authorization information comprising the second user identifier and the second ledger identifier to the service end. | 2,900 |
347,280 | 16,805,692 | 2,917 | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site. | 1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site.1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | 2,900 |
347,281 | 29,726,071 | 2,917 | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site. | 1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site.1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | 2,900 |
347,282 | 29,726,057 | 2,917 | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site. | 1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site.1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | 2,900 |
347,283 | 29,726,064 | 2,917 | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site. | 1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site.1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | 2,900 |
347,284 | 29,726,055 | 2,923 | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site. | 1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site.1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | 2,900 |
347,285 | 29,726,082 | 2,923 | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site. | 1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site.1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | 2,900 |
347,286 | 29,726,038 | 2,923 | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site. | 1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site.1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | 2,900 |
347,287 | 29,726,030 | 2,923 | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site. | 1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site.1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | 2,900 |
347,288 | 29,726,045 | 2,923 | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site. | 1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site.1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | 2,900 |
347,289 | 29,726,059 | 2,916 | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site. | 1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site.1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | 2,900 |
347,290 | 29,726,060 | 2,916 | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site. | 1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site.1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | 2,900 |
347,291 | 29,726,040 | 2,916 | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site. | 1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | Systems and methods of task acceptance are disclosed. One aspect of the present disclosure is directed to a mobile device. The mobile device comprises a display device, a scanning device, a memory storing instructions, and at least one processor configured to execute the instructions to receive a list of delivery tasks, the list of delivery tasks based on a stored set of preferences, display the list of delivery tasks, and receive, on the display device, an interaction with a user interface element to accept a delivery task; forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site for accomplishing the accepted delivery task; receive an interaction to confirm presence at the first delivery site; scan an indicia associated with the first delivery site, and determine whether the indicia matches the received code; and provide an indication that the accepted delivery task is performed at the first delivery site.1. A computer-implemented system for task acceptance, implemented on a mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the server, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task;
display a fourth graphical user interface on the display device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface displaying scanning instructions;
scan, via the scanning device, an indicia associated with the first delivery site of the distribution center, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. 2. The computer-implemented system of claim 1, wherein the scanning device captures images. 3. The computer-implemented system of claim 2, wherein the scanned indicia is a two-dimensional barcode. 4. The computer-implemented system of claim 1, wherein the indicia is compared to a copy of the received code stored on the mobile device. 5. The computer-implemented system of claim 1, wherein the plurality of selectable interface elements further comprise a preference acceptability requirement. 6. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to only accept tasks complying with the preferences; and the filtered list comprises delivery tasks that strictly comply with the preferred delivery type per task, the preferred number of packages per task, and the preferred delivery areas per task. 7. The computer-implemented system of claim 5, wherein:
the preference acceptability requirement is set to accept tasks other than those complying with the preferences; and the filtered list comprises delivery tasks that comply with at least one of the preferred delivery type per task, the preferred number of packages per task, or the preferred delivery areas per task. 8. (canceled) 9. A computer system for task acceptance comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from an internal front end system, a list of delivery tasks for acceptance, each delivery task being associated with a delivery site of a distribution center;
transmit, to a mobile device, instructions to generate a first graphical user interface, the first graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to the at least one processor upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the mobile device, delivery preferences in response to the selection of the plurality of interface elements;
generate a filtered list of delivery tasks by filtering the list of delivery tasks according to the delivery preferences, the filtered list being a portion of the list of delivery tasks;
transmit, to the mobile device, instructions to generate a second graphical user interface, the second graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list, the interactive icons being sorted based on the delivery preferences;
receive, from the mobile device upon selection of one or more of the plurality of interactive icons, a request for one or more of the delivery tasks for a delivery worker;
determine whether to approve the request; and
responsive to determining to approve the request, transmit, to the mobile device, instructions to generate a third graphical user interface, the third graphical user interface comprising a message box displaying scanning instructions. 10. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises filtering the list of delivery tasks to remove tasks that do not strictly comply with the preferences when receiving a selection of the preference acceptability requirement. 11. The computer-implemented system of claim 9, wherein:
the selectable interface elements comprises a preference acceptability requirement; and generating the filtered list comprises:
determining that the preference acceptability requirement is set to only accept tasks other than those complying with the preferences; and
filtering the list of delivery tasks to include tasks that comply with at least one of the preferences. 12. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises receiving an indication from a second system approving or declining the received acceptance. 13. The computer-implemented system of claim 9, wherein determine whether to approve the received acceptance comprises determining whether to approve the received acceptance based on delivery history associated with the delivery worker. 14. The computer-implemented system of claim 9, wherein receiving the list of delivery tasks comprises:
preparing a user interface comprising at least one element for entering information associated with the delivery tasks; forwarding the user interface to a computer system operated by an administrator associated with the delivery site; and receiving, through the user interface, the information associated with the delivery tasks. 15. The computer-implemented system of claim 9, wherein receiving a list of delivery tasks comprises:
receiving a data structure formatted to include information associated with forecasted delivery tasks; and retrieve the information associated with the forecasted delivery tasks. 16. The computer-implemented system of claim 9, wherein the list of delivery tasks comprises at least one of a delivery task, a return tasks, or a delivery/return task. 17. The computer-implemented system of claim 9, wherein each task of the list of delivery tasks comprises an acceptance window. 18. The computer-implemented system of claim 17, wherein determining whether to approve the received acceptance comprises:
determining a current time; comparing the current time to the acceptance window; approving the received acceptance if the current time is inside of the acceptance window; and declining the received acceptance otherwise. 19. The computer-implemented system of claim 9, wherein:
receiving an acceptance of a task further comprises removing the task from the list of delivery tasks; based on determining to reject the received acceptance:
forwarding a rejection message to the mobile device;
adding the task to the list of delivery tasks. 20. A computer-implemented system for task acceptance comprising a mobile device and a computing device interconnected via a network, the mobile device comprising:
a display device; a scanning device; a memory storing instructions; and at least one processor configured to execute the instructions to:
display a first graphical user interface on the display device when a user initiates an application, the first graphical user interface comprising an interactive calendar and a first button;
in response to a selection of the first button, display a second graphical user interface on the display device, the second graphical user interface displaying a plurality of selectable interface elements associated with delivery preferences, the selectable interface elements being configured to transmit delivery preferences to a server upon selection, the selectable interface elements comprising at least one of neighborhood preference, task preference, or number of packages preference;
receive, from the computing device, a filtered list of delivery tasks comprising tasks that comply with transmitted delivery preferences, the filtered list of delivery tasks being a portion of available delivery tasks received from an internal front end system;
after receiving the filtered list, generating a third graphical user interface on the display device, the third graphical user interface displaying a delivery dashboard comprising a plurality of interactive icons representing the filtered list of delivery tasks, the interactive icons being sorted based on the delivery preferences;
receive, on the display device, an interaction with at least one of the interactive icons;
responsive to receiving the interaction, forward a task identifier associated with the accepted task to the server and receive a message in response including a code associated with a first delivery site of a distribution center for accomplishing the accepted delivery task; receive, on the display device, an interaction to confirm presence at the first delivery site;
display a fourth graphical user interface on the displaying device when receiving an interaction indicating presence at the first delivery site, the fourth graphical user interface comprising a message box displaying scanning instructions;
scanning, via the scanning device, an indicia associated with the first delivery site of the distribution enter, and determine whether the indicia matches the received code; and
responsive to a determination that the indicia matches the received code, provide an indication that the accepted delivery task is performed at the first delivery site. | 2,900 |
347,292 | 16,805,684 | 2,916 | A computerized system for generating a single page user interface that includes a display, memory storing instructions, and at least one processor that may be configured to execute instructions to perform operations. The operations may include receiving an invoice ID for a customer from a first database, receiving delivery completion picture associated with the invoice ID from a second database, receiving a delivery information from a third database, generating a critical delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information. Furthermore, the system may generate a single page user interface including information from the critical delivery information set and the data analytics set. Moreover, the single page user is displayed on the display wherein the single page user interface is configured to receive inputs from a user, and update the user interface in response to the received inputs. | 1. A computer-implemented system for auditing delivery completion, the system comprising:
a display; a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user;
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 2. The system of claim 1, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 3. The system of claim 1, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 4. The system of claim 1, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 5. (canceled) 6. (canceled) 7. (canceled) 8. The system of claim 1, wherein the search criteria view includes a target search box configured to receive, from the user, an input of at least one invoice ID. 9. (canceled) 10. The system of claim 1, wherein the invoice delivery view further enables audit of the delivery completion picture. 11. A computer-implemented method for delivery completion audit tool, the method comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database; receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address; receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address; generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information; generating a single page user interface including information from the delivery information set and the data analytics set; displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user; and
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 12. The method of claim 11, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 13. The method of claim 11, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 14. The method of claim 11, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 15. (canceled) 16. (canceled) 17. (canceled) 18. The method of claim 11, wherein the search criteria view includes a target search box configured to receive, from a user, an input of at least one invoice ID. 19. (canceled) 20. A computer-implemented system for delivery completion audit tool, the system comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a-delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying a oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view;
wherein the first list view includes the delivery completion picture and an audit status;
wherein the single page user interface is configured to receive from the user at least one click on the delivery completion picture of the first list view to change the audit status, and update the audit status associated with the invoice ID in the user interface in response to the user at least one click; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 21. The system of claim 1, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. 22. The computer-implemented method of claim 11, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. | A computerized system for generating a single page user interface that includes a display, memory storing instructions, and at least one processor that may be configured to execute instructions to perform operations. The operations may include receiving an invoice ID for a customer from a first database, receiving delivery completion picture associated with the invoice ID from a second database, receiving a delivery information from a third database, generating a critical delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information. Furthermore, the system may generate a single page user interface including information from the critical delivery information set and the data analytics set. Moreover, the single page user is displayed on the display wherein the single page user interface is configured to receive inputs from a user, and update the user interface in response to the received inputs.1. A computer-implemented system for auditing delivery completion, the system comprising:
a display; a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user;
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 2. The system of claim 1, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 3. The system of claim 1, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 4. The system of claim 1, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 5. (canceled) 6. (canceled) 7. (canceled) 8. The system of claim 1, wherein the search criteria view includes a target search box configured to receive, from the user, an input of at least one invoice ID. 9. (canceled) 10. The system of claim 1, wherein the invoice delivery view further enables audit of the delivery completion picture. 11. A computer-implemented method for delivery completion audit tool, the method comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database; receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address; receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address; generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information; generating a single page user interface including information from the delivery information set and the data analytics set; displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user; and
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 12. The method of claim 11, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 13. The method of claim 11, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 14. The method of claim 11, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 15. (canceled) 16. (canceled) 17. (canceled) 18. The method of claim 11, wherein the search criteria view includes a target search box configured to receive, from a user, an input of at least one invoice ID. 19. (canceled) 20. A computer-implemented system for delivery completion audit tool, the system comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a-delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying a oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view;
wherein the first list view includes the delivery completion picture and an audit status;
wherein the single page user interface is configured to receive from the user at least one click on the delivery completion picture of the first list view to change the audit status, and update the audit status associated with the invoice ID in the user interface in response to the user at least one click; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 21. The system of claim 1, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. 22. The computer-implemented method of claim 11, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. | 2,900 |
347,293 | 29,726,070 | 2,916 | A computerized system for generating a single page user interface that includes a display, memory storing instructions, and at least one processor that may be configured to execute instructions to perform operations. The operations may include receiving an invoice ID for a customer from a first database, receiving delivery completion picture associated with the invoice ID from a second database, receiving a delivery information from a third database, generating a critical delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information. Furthermore, the system may generate a single page user interface including information from the critical delivery information set and the data analytics set. Moreover, the single page user is displayed on the display wherein the single page user interface is configured to receive inputs from a user, and update the user interface in response to the received inputs. | 1. A computer-implemented system for auditing delivery completion, the system comprising:
a display; a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user;
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 2. The system of claim 1, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 3. The system of claim 1, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 4. The system of claim 1, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 5. (canceled) 6. (canceled) 7. (canceled) 8. The system of claim 1, wherein the search criteria view includes a target search box configured to receive, from the user, an input of at least one invoice ID. 9. (canceled) 10. The system of claim 1, wherein the invoice delivery view further enables audit of the delivery completion picture. 11. A computer-implemented method for delivery completion audit tool, the method comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database; receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address; receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address; generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information; generating a single page user interface including information from the delivery information set and the data analytics set; displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user; and
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 12. The method of claim 11, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 13. The method of claim 11, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 14. The method of claim 11, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 15. (canceled) 16. (canceled) 17. (canceled) 18. The method of claim 11, wherein the search criteria view includes a target search box configured to receive, from a user, an input of at least one invoice ID. 19. (canceled) 20. A computer-implemented system for delivery completion audit tool, the system comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a-delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying a oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view;
wherein the first list view includes the delivery completion picture and an audit status;
wherein the single page user interface is configured to receive from the user at least one click on the delivery completion picture of the first list view to change the audit status, and update the audit status associated with the invoice ID in the user interface in response to the user at least one click; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 21. The system of claim 1, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. 22. The computer-implemented method of claim 11, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. | A computerized system for generating a single page user interface that includes a display, memory storing instructions, and at least one processor that may be configured to execute instructions to perform operations. The operations may include receiving an invoice ID for a customer from a first database, receiving delivery completion picture associated with the invoice ID from a second database, receiving a delivery information from a third database, generating a critical delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information. Furthermore, the system may generate a single page user interface including information from the critical delivery information set and the data analytics set. Moreover, the single page user is displayed on the display wherein the single page user interface is configured to receive inputs from a user, and update the user interface in response to the received inputs.1. A computer-implemented system for auditing delivery completion, the system comprising:
a display; a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user;
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 2. The system of claim 1, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 3. The system of claim 1, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 4. The system of claim 1, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 5. (canceled) 6. (canceled) 7. (canceled) 8. The system of claim 1, wherein the search criteria view includes a target search box configured to receive, from the user, an input of at least one invoice ID. 9. (canceled) 10. The system of claim 1, wherein the invoice delivery view further enables audit of the delivery completion picture. 11. A computer-implemented method for delivery completion audit tool, the method comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database; receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address; receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address; generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information; generating a single page user interface including information from the delivery information set and the data analytics set; displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user; and
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 12. The method of claim 11, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 13. The method of claim 11, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 14. The method of claim 11, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 15. (canceled) 16. (canceled) 17. (canceled) 18. The method of claim 11, wherein the search criteria view includes a target search box configured to receive, from a user, an input of at least one invoice ID. 19. (canceled) 20. A computer-implemented system for delivery completion audit tool, the system comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a-delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying a oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view;
wherein the first list view includes the delivery completion picture and an audit status;
wherein the single page user interface is configured to receive from the user at least one click on the delivery completion picture of the first list view to change the audit status, and update the audit status associated with the invoice ID in the user interface in response to the user at least one click; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 21. The system of claim 1, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. 22. The computer-implemented method of claim 11, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. | 2,900 |
347,294 | 29,726,052 | 2,924 | A computerized system for generating a single page user interface that includes a display, memory storing instructions, and at least one processor that may be configured to execute instructions to perform operations. The operations may include receiving an invoice ID for a customer from a first database, receiving delivery completion picture associated with the invoice ID from a second database, receiving a delivery information from a third database, generating a critical delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information. Furthermore, the system may generate a single page user interface including information from the critical delivery information set and the data analytics set. Moreover, the single page user is displayed on the display wherein the single page user interface is configured to receive inputs from a user, and update the user interface in response to the received inputs. | 1. A computer-implemented system for auditing delivery completion, the system comprising:
a display; a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user;
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 2. The system of claim 1, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 3. The system of claim 1, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 4. The system of claim 1, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 5. (canceled) 6. (canceled) 7. (canceled) 8. The system of claim 1, wherein the search criteria view includes a target search box configured to receive, from the user, an input of at least one invoice ID. 9. (canceled) 10. The system of claim 1, wherein the invoice delivery view further enables audit of the delivery completion picture. 11. A computer-implemented method for delivery completion audit tool, the method comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database; receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address; receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address; generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information; generating a single page user interface including information from the delivery information set and the data analytics set; displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user; and
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 12. The method of claim 11, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 13. The method of claim 11, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 14. The method of claim 11, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 15. (canceled) 16. (canceled) 17. (canceled) 18. The method of claim 11, wherein the search criteria view includes a target search box configured to receive, from a user, an input of at least one invoice ID. 19. (canceled) 20. A computer-implemented system for delivery completion audit tool, the system comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a-delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying a oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view;
wherein the first list view includes the delivery completion picture and an audit status;
wherein the single page user interface is configured to receive from the user at least one click on the delivery completion picture of the first list view to change the audit status, and update the audit status associated with the invoice ID in the user interface in response to the user at least one click; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 21. The system of claim 1, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. 22. The computer-implemented method of claim 11, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. | A computerized system for generating a single page user interface that includes a display, memory storing instructions, and at least one processor that may be configured to execute instructions to perform operations. The operations may include receiving an invoice ID for a customer from a first database, receiving delivery completion picture associated with the invoice ID from a second database, receiving a delivery information from a third database, generating a critical delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information. Furthermore, the system may generate a single page user interface including information from the critical delivery information set and the data analytics set. Moreover, the single page user is displayed on the display wherein the single page user interface is configured to receive inputs from a user, and update the user interface in response to the received inputs.1. A computer-implemented system for auditing delivery completion, the system comprising:
a display; a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user;
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 2. The system of claim 1, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 3. The system of claim 1, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 4. The system of claim 1, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 5. (canceled) 6. (canceled) 7. (canceled) 8. The system of claim 1, wherein the search criteria view includes a target search box configured to receive, from the user, an input of at least one invoice ID. 9. (canceled) 10. The system of claim 1, wherein the invoice delivery view further enables audit of the delivery completion picture. 11. A computer-implemented method for delivery completion audit tool, the method comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database; receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address; receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address; generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information; generating a single page user interface including information from the delivery information set and the data analytics set; displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user; and
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 12. The method of claim 11, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 13. The method of claim 11, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 14. The method of claim 11, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 15. (canceled) 16. (canceled) 17. (canceled) 18. The method of claim 11, wherein the search criteria view includes a target search box configured to receive, from a user, an input of at least one invoice ID. 19. (canceled) 20. A computer-implemented system for delivery completion audit tool, the system comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a-delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying a oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view;
wherein the first list view includes the delivery completion picture and an audit status;
wherein the single page user interface is configured to receive from the user at least one click on the delivery completion picture of the first list view to change the audit status, and update the audit status associated with the invoice ID in the user interface in response to the user at least one click; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 21. The system of claim 1, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. 22. The computer-implemented method of claim 11, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. | 2,900 |
347,295 | 29,726,007 | 2,924 | A computerized system for generating a single page user interface that includes a display, memory storing instructions, and at least one processor that may be configured to execute instructions to perform operations. The operations may include receiving an invoice ID for a customer from a first database, receiving delivery completion picture associated with the invoice ID from a second database, receiving a delivery information from a third database, generating a critical delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information. Furthermore, the system may generate a single page user interface including information from the critical delivery information set and the data analytics set. Moreover, the single page user is displayed on the display wherein the single page user interface is configured to receive inputs from a user, and update the user interface in response to the received inputs. | 1. A computer-implemented system for auditing delivery completion, the system comprising:
a display; a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user;
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 2. The system of claim 1, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 3. The system of claim 1, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 4. The system of claim 1, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 5. (canceled) 6. (canceled) 7. (canceled) 8. The system of claim 1, wherein the search criteria view includes a target search box configured to receive, from the user, an input of at least one invoice ID. 9. (canceled) 10. The system of claim 1, wherein the invoice delivery view further enables audit of the delivery completion picture. 11. A computer-implemented method for delivery completion audit tool, the method comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database; receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address; receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address; generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information; generating a single page user interface including information from the delivery information set and the data analytics set; displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user; and
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 12. The method of claim 11, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 13. The method of claim 11, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 14. The method of claim 11, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 15. (canceled) 16. (canceled) 17. (canceled) 18. The method of claim 11, wherein the search criteria view includes a target search box configured to receive, from a user, an input of at least one invoice ID. 19. (canceled) 20. A computer-implemented system for delivery completion audit tool, the system comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a-delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying a oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view;
wherein the first list view includes the delivery completion picture and an audit status;
wherein the single page user interface is configured to receive from the user at least one click on the delivery completion picture of the first list view to change the audit status, and update the audit status associated with the invoice ID in the user interface in response to the user at least one click; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 21. The system of claim 1, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. 22. The computer-implemented method of claim 11, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. | A computerized system for generating a single page user interface that includes a display, memory storing instructions, and at least one processor that may be configured to execute instructions to perform operations. The operations may include receiving an invoice ID for a customer from a first database, receiving delivery completion picture associated with the invoice ID from a second database, receiving a delivery information from a third database, generating a critical delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information. Furthermore, the system may generate a single page user interface including information from the critical delivery information set and the data analytics set. Moreover, the single page user is displayed on the display wherein the single page user interface is configured to receive inputs from a user, and update the user interface in response to the received inputs.1. A computer-implemented system for auditing delivery completion, the system comprising:
a display; a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user;
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 2. The system of claim 1, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 3. The system of claim 1, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 4. The system of claim 1, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 5. (canceled) 6. (canceled) 7. (canceled) 8. The system of claim 1, wherein the search criteria view includes a target search box configured to receive, from the user, an input of at least one invoice ID. 9. (canceled) 10. The system of claim 1, wherein the invoice delivery view further enables audit of the delivery completion picture. 11. A computer-implemented method for delivery completion audit tool, the method comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database; receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address; receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address; generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information; generating a single page user interface including information from the delivery information set and the data analytics set; displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user; and
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 12. The method of claim 11, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 13. The method of claim 11, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 14. The method of claim 11, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 15. (canceled) 16. (canceled) 17. (canceled) 18. The method of claim 11, wherein the search criteria view includes a target search box configured to receive, from a user, an input of at least one invoice ID. 19. (canceled) 20. A computer-implemented system for delivery completion audit tool, the system comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a-delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying a oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view;
wherein the first list view includes the delivery completion picture and an audit status;
wherein the single page user interface is configured to receive from the user at least one click on the delivery completion picture of the first list view to change the audit status, and update the audit status associated with the invoice ID in the user interface in response to the user at least one click; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 21. The system of claim 1, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. 22. The computer-implemented method of claim 11, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. | 2,900 |
347,296 | 29,726,034 | 2,924 | A computerized system for generating a single page user interface that includes a display, memory storing instructions, and at least one processor that may be configured to execute instructions to perform operations. The operations may include receiving an invoice ID for a customer from a first database, receiving delivery completion picture associated with the invoice ID from a second database, receiving a delivery information from a third database, generating a critical delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information. Furthermore, the system may generate a single page user interface including information from the critical delivery information set and the data analytics set. Moreover, the single page user is displayed on the display wherein the single page user interface is configured to receive inputs from a user, and update the user interface in response to the received inputs. | 1. A computer-implemented system for auditing delivery completion, the system comprising:
a display; a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user;
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 2. The system of claim 1, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 3. The system of claim 1, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 4. The system of claim 1, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 5. (canceled) 6. (canceled) 7. (canceled) 8. The system of claim 1, wherein the search criteria view includes a target search box configured to receive, from the user, an input of at least one invoice ID. 9. (canceled) 10. The system of claim 1, wherein the invoice delivery view further enables audit of the delivery completion picture. 11. A computer-implemented method for delivery completion audit tool, the method comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database; receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address; receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address; generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information; generating a single page user interface including information from the delivery information set and the data analytics set; displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user; and
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 12. The method of claim 11, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 13. The method of claim 11, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 14. The method of claim 11, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 15. (canceled) 16. (canceled) 17. (canceled) 18. The method of claim 11, wherein the search criteria view includes a target search box configured to receive, from a user, an input of at least one invoice ID. 19. (canceled) 20. A computer-implemented system for delivery completion audit tool, the system comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a-delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying a oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view;
wherein the first list view includes the delivery completion picture and an audit status;
wherein the single page user interface is configured to receive from the user at least one click on the delivery completion picture of the first list view to change the audit status, and update the audit status associated with the invoice ID in the user interface in response to the user at least one click; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 21. The system of claim 1, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. 22. The computer-implemented method of claim 11, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. | A computerized system for generating a single page user interface that includes a display, memory storing instructions, and at least one processor that may be configured to execute instructions to perform operations. The operations may include receiving an invoice ID for a customer from a first database, receiving delivery completion picture associated with the invoice ID from a second database, receiving a delivery information from a third database, generating a critical delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information. Furthermore, the system may generate a single page user interface including information from the critical delivery information set and the data analytics set. Moreover, the single page user is displayed on the display wherein the single page user interface is configured to receive inputs from a user, and update the user interface in response to the received inputs.1. A computer-implemented system for auditing delivery completion, the system comprising:
a display; a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user;
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 2. The system of claim 1, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 3. The system of claim 1, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 4. The system of claim 1, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 5. (canceled) 6. (canceled) 7. (canceled) 8. The system of claim 1, wherein the search criteria view includes a target search box configured to receive, from the user, an input of at least one invoice ID. 9. (canceled) 10. The system of claim 1, wherein the invoice delivery view further enables audit of the delivery completion picture. 11. A computer-implemented method for delivery completion audit tool, the method comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database; receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address; receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address; generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information; generating a single page user interface including information from the delivery information set and the data analytics set; displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user; and
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 12. The method of claim 11, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 13. The method of claim 11, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 14. The method of claim 11, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 15. (canceled) 16. (canceled) 17. (canceled) 18. The method of claim 11, wherein the search criteria view includes a target search box configured to receive, from a user, an input of at least one invoice ID. 19. (canceled) 20. A computer-implemented system for delivery completion audit tool, the system comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a-delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying a oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view;
wherein the first list view includes the delivery completion picture and an audit status;
wherein the single page user interface is configured to receive from the user at least one click on the delivery completion picture of the first list view to change the audit status, and update the audit status associated with the invoice ID in the user interface in response to the user at least one click; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 21. The system of claim 1, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. 22. The computer-implemented method of claim 11, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. | 2,900 |
347,297 | 29,726,036 | 2,924 | A computerized system for generating a single page user interface that includes a display, memory storing instructions, and at least one processor that may be configured to execute instructions to perform operations. The operations may include receiving an invoice ID for a customer from a first database, receiving delivery completion picture associated with the invoice ID from a second database, receiving a delivery information from a third database, generating a critical delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information. Furthermore, the system may generate a single page user interface including information from the critical delivery information set and the data analytics set. Moreover, the single page user is displayed on the display wherein the single page user interface is configured to receive inputs from a user, and update the user interface in response to the received inputs. | 1. A computer-implemented system for auditing delivery completion, the system comprising:
a display; a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user;
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 2. The system of claim 1, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 3. The system of claim 1, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 4. The system of claim 1, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 5. (canceled) 6. (canceled) 7. (canceled) 8. The system of claim 1, wherein the search criteria view includes a target search box configured to receive, from the user, an input of at least one invoice ID. 9. (canceled) 10. The system of claim 1, wherein the invoice delivery view further enables audit of the delivery completion picture. 11. A computer-implemented method for delivery completion audit tool, the method comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database; receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address; receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address; generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information; generating a single page user interface including information from the delivery information set and the data analytics set; displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user; and
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 12. The method of claim 11, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 13. The method of claim 11, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 14. The method of claim 11, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 15. (canceled) 16. (canceled) 17. (canceled) 18. The method of claim 11, wherein the search criteria view includes a target search box configured to receive, from a user, an input of at least one invoice ID. 19. (canceled) 20. A computer-implemented system for delivery completion audit tool, the system comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a-delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying a oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view;
wherein the first list view includes the delivery completion picture and an audit status;
wherein the single page user interface is configured to receive from the user at least one click on the delivery completion picture of the first list view to change the audit status, and update the audit status associated with the invoice ID in the user interface in response to the user at least one click; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 21. The system of claim 1, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. 22. The computer-implemented method of claim 11, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. | A computerized system for generating a single page user interface that includes a display, memory storing instructions, and at least one processor that may be configured to execute instructions to perform operations. The operations may include receiving an invoice ID for a customer from a first database, receiving delivery completion picture associated with the invoice ID from a second database, receiving a delivery information from a third database, generating a critical delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information. Furthermore, the system may generate a single page user interface including information from the critical delivery information set and the data analytics set. Moreover, the single page user is displayed on the display wherein the single page user interface is configured to receive inputs from a user, and update the user interface in response to the received inputs.1. A computer-implemented system for auditing delivery completion, the system comprising:
a display; a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user;
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 2. The system of claim 1, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 3. The system of claim 1, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 4. The system of claim 1, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 5. (canceled) 6. (canceled) 7. (canceled) 8. The system of claim 1, wherein the search criteria view includes a target search box configured to receive, from the user, an input of at least one invoice ID. 9. (canceled) 10. The system of claim 1, wherein the invoice delivery view further enables audit of the delivery completion picture. 11. A computer-implemented method for delivery completion audit tool, the method comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database; receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address; receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address; generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information; generating a single page user interface including information from the delivery information set and the data analytics set; displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user; and
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 12. The method of claim 11, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 13. The method of claim 11, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 14. The method of claim 11, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 15. (canceled) 16. (canceled) 17. (canceled) 18. The method of claim 11, wherein the search criteria view includes a target search box configured to receive, from a user, an input of at least one invoice ID. 19. (canceled) 20. A computer-implemented system for delivery completion audit tool, the system comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a-delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying a oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view;
wherein the first list view includes the delivery completion picture and an audit status;
wherein the single page user interface is configured to receive from the user at least one click on the delivery completion picture of the first list view to change the audit status, and update the audit status associated with the invoice ID in the user interface in response to the user at least one click; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 21. The system of claim 1, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. 22. The computer-implemented method of claim 11, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. | 2,900 |
347,298 | 29,726,043 | 2,924 | A computerized system for generating a single page user interface that includes a display, memory storing instructions, and at least one processor that may be configured to execute instructions to perform operations. The operations may include receiving an invoice ID for a customer from a first database, receiving delivery completion picture associated with the invoice ID from a second database, receiving a delivery information from a third database, generating a critical delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information. Furthermore, the system may generate a single page user interface including information from the critical delivery information set and the data analytics set. Moreover, the single page user is displayed on the display wherein the single page user interface is configured to receive inputs from a user, and update the user interface in response to the received inputs. | 1. A computer-implemented system for auditing delivery completion, the system comprising:
a display; a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user;
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 2. The system of claim 1, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 3. The system of claim 1, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 4. The system of claim 1, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 5. (canceled) 6. (canceled) 7. (canceled) 8. The system of claim 1, wherein the search criteria view includes a target search box configured to receive, from the user, an input of at least one invoice ID. 9. (canceled) 10. The system of claim 1, wherein the invoice delivery view further enables audit of the delivery completion picture. 11. A computer-implemented method for delivery completion audit tool, the method comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database; receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address; receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address; generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information; generating a single page user interface including information from the delivery information set and the data analytics set; displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user; and
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 12. The method of claim 11, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 13. The method of claim 11, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 14. The method of claim 11, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 15. (canceled) 16. (canceled) 17. (canceled) 18. The method of claim 11, wherein the search criteria view includes a target search box configured to receive, from a user, an input of at least one invoice ID. 19. (canceled) 20. A computer-implemented system for delivery completion audit tool, the system comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a-delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying a oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view;
wherein the first list view includes the delivery completion picture and an audit status;
wherein the single page user interface is configured to receive from the user at least one click on the delivery completion picture of the first list view to change the audit status, and update the audit status associated with the invoice ID in the user interface in response to the user at least one click; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 21. The system of claim 1, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. 22. The computer-implemented method of claim 11, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. | A computerized system for generating a single page user interface that includes a display, memory storing instructions, and at least one processor that may be configured to execute instructions to perform operations. The operations may include receiving an invoice ID for a customer from a first database, receiving delivery completion picture associated with the invoice ID from a second database, receiving a delivery information from a third database, generating a critical delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information. Furthermore, the system may generate a single page user interface including information from the critical delivery information set and the data analytics set. Moreover, the single page user is displayed on the display wherein the single page user interface is configured to receive inputs from a user, and update the user interface in response to the received inputs.1. A computer-implemented system for auditing delivery completion, the system comprising:
a display; a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user;
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 2. The system of claim 1, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 3. The system of claim 1, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 4. The system of claim 1, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 5. (canceled) 6. (canceled) 7. (canceled) 8. The system of claim 1, wherein the search criteria view includes a target search box configured to receive, from the user, an input of at least one invoice ID. 9. (canceled) 10. The system of claim 1, wherein the invoice delivery view further enables audit of the delivery completion picture. 11. A computer-implemented method for delivery completion audit tool, the method comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database; receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address; receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address; generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information; generating a single page user interface including information from the delivery information set and the data analytics set; displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user; and
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 12. The method of claim 11, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 13. The method of claim 11, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 14. The method of claim 11, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 15. (canceled) 16. (canceled) 17. (canceled) 18. The method of claim 11, wherein the search criteria view includes a target search box configured to receive, from a user, an input of at least one invoice ID. 19. (canceled) 20. A computer-implemented system for delivery completion audit tool, the system comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a-delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying a oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view;
wherein the first list view includes the delivery completion picture and an audit status;
wherein the single page user interface is configured to receive from the user at least one click on the delivery completion picture of the first list view to change the audit status, and update the audit status associated with the invoice ID in the user interface in response to the user at least one click; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 21. The system of claim 1, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. 22. The computer-implemented method of claim 11, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. | 2,900 |
347,299 | 29,726,081 | 2,924 | A computerized system for generating a single page user interface that includes a display, memory storing instructions, and at least one processor that may be configured to execute instructions to perform operations. The operations may include receiving an invoice ID for a customer from a first database, receiving delivery completion picture associated with the invoice ID from a second database, receiving a delivery information from a third database, generating a critical delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information. Furthermore, the system may generate a single page user interface including information from the critical delivery information set and the data analytics set. Moreover, the single page user is displayed on the display wherein the single page user interface is configured to receive inputs from a user, and update the user interface in response to the received inputs. | 1. A computer-implemented system for auditing delivery completion, the system comprising:
a display; a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user;
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 2. The system of claim 1, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 3. The system of claim 1, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 4. The system of claim 1, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 5. (canceled) 6. (canceled) 7. (canceled) 8. The system of claim 1, wherein the search criteria view includes a target search box configured to receive, from the user, an input of at least one invoice ID. 9. (canceled) 10. The system of claim 1, wherein the invoice delivery view further enables audit of the delivery completion picture. 11. A computer-implemented method for delivery completion audit tool, the method comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database; receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address; receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address; generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information; generating a single page user interface including information from the delivery information set and the data analytics set; displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user; and
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 12. The method of claim 11, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 13. The method of claim 11, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 14. The method of claim 11, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 15. (canceled) 16. (canceled) 17. (canceled) 18. The method of claim 11, wherein the search criteria view includes a target search box configured to receive, from a user, an input of at least one invoice ID. 19. (canceled) 20. A computer-implemented system for delivery completion audit tool, the system comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a-delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying a oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view;
wherein the first list view includes the delivery completion picture and an audit status;
wherein the single page user interface is configured to receive from the user at least one click on the delivery completion picture of the first list view to change the audit status, and update the audit status associated with the invoice ID in the user interface in response to the user at least one click; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 21. The system of claim 1, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. 22. The computer-implemented method of claim 11, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. | A computerized system for generating a single page user interface that includes a display, memory storing instructions, and at least one processor that may be configured to execute instructions to perform operations. The operations may include receiving an invoice ID for a customer from a first database, receiving delivery completion picture associated with the invoice ID from a second database, receiving a delivery information from a third database, generating a critical delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information. Furthermore, the system may generate a single page user interface including information from the critical delivery information set and the data analytics set. Moreover, the single page user is displayed on the display wherein the single page user interface is configured to receive inputs from a user, and update the user interface in response to the received inputs.1. A computer-implemented system for auditing delivery completion, the system comprising:
a display; a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user;
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 2. The system of claim 1, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 3. The system of claim 1, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 4. The system of claim 1, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 5. (canceled) 6. (canceled) 7. (canceled) 8. The system of claim 1, wherein the search criteria view includes a target search box configured to receive, from the user, an input of at least one invoice ID. 9. (canceled) 10. The system of claim 1, wherein the invoice delivery view further enables audit of the delivery completion picture. 11. A computer-implemented method for delivery completion audit tool, the method comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database; receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address; receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address; generating a delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information; generating a single page user interface including information from the delivery information set and the data analytics set; displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view by the user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying an oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a first audit view is configured to dynamically display an audit history view based on a selection in the invoice delivery view by the user; and
wherein the single page user interface is configured to receive inputs from the user in the search criteria view, the delivery view, and the first audit view, and update the user interface in response to the received inputs; and converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 12. The method of claim 11, wherein the delivery information set includes at least one of an invoice ID, an order ID, a delivery completion picture, and the delivery information. 13. The method of claim 11, wherein the data analytics set includes at least one of a percentage of successful deliveries, a percentage of unsuccessful deliveries, and a total number of completed deliveries by dates. 14. The method of claim 11, wherein at least one of the delivery information set and the data analytics set is dynamically updateable based on at least one of new and revised delivery information, a new invoice ID, and a new delivery completion picture. 15. (canceled) 16. (canceled) 17. (canceled) 18. The method of claim 11, wherein the search criteria view includes a target search box configured to receive, from a user, an input of at least one invoice ID. 19. (canceled) 20. A computer-implemented system for delivery completion audit tool, the system comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to perform steps comprising:
receiving an invoice ID of a customer based on a delivery address of the customer from a first database;
receiving a delivery completion picture associated with the invoice ID from a second database, wherein the delivery completion picture is of a desired location at the customer delivery address;
receiving delivery information from a third database, the delivery information including the desired location at the customer delivery address;
generating a-delivery information set and a data analytics set based on the invoice ID, the delivery completion picture, and the delivery information;
generating a single page user interface including information from the delivery information set and the data analytics set;
displaying the single page user interface on the display, wherein the single page user interface comprises:
a search criteria view configured with user interface elements to narrow a search in the delivery information set by a user;
a picture focused view wherein the picture focus view further enables audit of the delivery completion picture; and wherein the delivery completion picture indicates an audit status by displaying a oval shape having one of a plurality of colors respectively corresponding to different audit statuses; and
a delivery view configured to dynamically display a first list view based on the search in the delivery information set from the user interface elements in the search criteria view, and further dynamically display an invoice delivery view based on a selection in the first list view;
wherein the first list view includes the delivery completion picture and an audit status;
wherein the single page user interface is configured to receive from the user at least one click on the delivery completion picture of the first list view to change the audit status, and update the audit status associated with the invoice ID in the user interface in response to the user at least one click; and
converting at least one of the invoice ID, the delivery completion picture, the delivery information, the delivery information set, and the data analytics set from an original format to a conversion format for manipulation. 21. The system of claim 1, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. 22. The computer-implemented method of claim 11, wherein manipulation includes indexing data, rearranging data, filtering data, transforming data, and standardizing data. | 2,900 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.