text:
1. JOHN1 MARSHALL (ALEXANDERA) was born abt. 1803 in Prince Edward Island, and died May 20, 1879 in Harrington, Argenteuil Co., Québec. He married SARAH SHEVENELL abt. 1843. She was born Bet. 1822 - 1825 in Ireland, and died Oct 15, 1901 in Harrington, Argenteuil Co., Québec.
i. ELLEN2 MARSHALL, b. abt. 1844, Ontario, Canada; d. Bet. 1880 - 1888, Troy, NY (probably); m. WILLIAM HOOPPELL, Dec 29, 1862, Harrington, Argenteuil Co., Québec; b. Dec 1844, New York, USA; d. Mar 10, 1926, Montreal, Québec, Canada.
2. ii. JOHN MARSHALL, b. Feb 8, 1846, Ontario, Canada; d. Jul 12, 1925, Harrington, Argenteuil Co., Québec, Canada.
3. iii. JANE MARSHALL, b. Mar 18, 1848, Ontario, Canada; d. Mar 28, 1930, Harrington, Argenteuil, Québec, Canada.
iv. ALEXANDER MARSHALL, b. abt. 1849, Ontario, Canada.
4. v. THOMAS MARSHALL, b. Dec 3, 1853, Québec, Canada.
5. vi. ROBERT MARSHALL, b. Apr 20, 1855, Ontario, Canada; d. Jan 17, 1918, Ontario.
6. vii. JAMES MARSHALL, b. abt. 1858, Québec, Canada; d. Nov 9, 1896, Harrington, Argenteuil Co., Québec, Canada.
2. JOHN2 MARSHALL (JOHN1, ALEXANDERA) was born Feb 8, 1846 in Ontario, Canada, and died Jul 12, 1925 in Harrington, Argenteuil Co., Québec, Canada. He married MARGARET SHAW Jun 14, 1875 in Grenville or Harrington E, Argenteuil, Québec, daughter of JOHN SHAW and SARAH MCPHAIL. She was born Mar 13, 1857 in Harrington, Argenteuil Co., Québec, Canada, and died Dec 19, 1933 in Harrington, Argenteuil Co., Québec, Canada.
7. i. JOHN ALEXANDER3 MARSHALL, b. Jun 29, 1876, Harrington E, Argenteuil Co., Québec; d. Jul 7, 1961, Lachute, Québec.
ii. CATHERINE MARSHALL, b. Jan 17, 1878, Harrington E, Argenteuil Co., Québec, Canada; d. Dec 10, 1964, Montreal, Québec; m. CHARLES TURNER, Nov 30, 1904; b. ?New York, USA.
8. iii. MALCOLM LAWRENCE MARSHALL, b. Sep 27, 1879, Harrington E, Argenteuil Co., Québec, Canada; d. Dec 2, 1919, Québec, Canada.
9. iv. SARAH ANN MARSHALL, b. Jun 16, 1881, Harrington E, Argenteuil Co., Québec; d. Oct 2, 1959, Montreal, Québec.
v. JAMES IRVINE MARSHALL, b. Dec 8, 1882, Harrington E, Argenteuil Co., Québec; d. Jun 17, 1905, Lachute, Argenteuil Co., Québec.
vi. JESSIE MARSHALL, b. Nov 7, 1884, Harrington E, Argenteuil Co., Québec; d. May 9, 1910, Harrington E, Argenteuil Co., Québec.
vii. BOY MARSHALL, b. Sep 13, 1886, Harrington E, Argenteuil Co., Québec; d. Mar 10, 1887, Harrington E, Argenteuil Co., Québec.
10. viii. MARGARET JANE GRACE MARSHALL, b. Jun 2, 1888, Harrington E, Argenteuil Co., Québec; d. Apr 21, 1957, Harrington E, Argenteuil Co., Québec.
11. ix. HANNAH EDNA MARSHALL, b. May 28, 1890, Harrington E, Argenteuil Co., Québec; d. Nov 14, 1978, Grosse Point Park, Detroit, Michigan, USA.
12. x. EMMA MABEL CORA MARSHALL, b. Apr 10, 1892, Harrington E, Argenteuil Co., Québec; d. Jan 1, 1921, Harrington E, Argenteuil Co., Québec.
xi. GIRL MARSHALL, b. Feb 25, 1894, Harrington E, Argenteuil Co., Québec; d. Mar 1, 1894, Harrington E, Argenteuil Co., Québec.
xii. BOY MARSHALL, b. Mar 12, 1896, Harrington E, Argenteuil Co., Québec; d. 1896, Harrington E, Argenteuil Co., Québec.
xiii. THOMAS LEONARD REID MARSHALL, b. Feb 7, 1898, Harrington E, Argenteuil Co., Québec; d. Sep 9, 1978, Los Angeles, California, USA.
3. JANE2 MARSHALL (JOHN1, ALEXANDERA) was born Mar 18, 1848 in Ontario, Canada, and died Mar 28, 1930 in Harrington, Argenteuil, Québec, Canada. She married ALEXANDER MACLEOD Sep 3, 1878 in Grenville Mission Presbyterian Church, Argenteuil, son of WILLIAM MCLEOD and CHRISTINA CAMPBELL. He was born Sep 30, 1850 in Harrington, Argenteuil, Québec, Canada, and died Jul 17, 1929 in Harrington, Argenteuil Co., Québec, Canada.
13. i. WILLIAM M. A.3 MACLEOD, b. Apr 29, 1878, Harrington, Argenteuil Co., Québec, Canada; d. Aug 7, 1940, Harrington, Argenteuil Co, Québec.
14. ii. ALICE ANN MACLEOD, b. Jan 6, 1880, Harrington, Argenteuil Co., Québec, Canada; d. Nov 5, 1932.
15. iii. JAMES MACLEOD, b. Oct 2, 1881, Harrington, Argenteuil Co., Québec, Canada; d. Apr 5, 1967.
16. iv. JOHN CHARLES MACLEOD, b. Jul 15, 1883, Harrington, Argenteuil Co., Québec, Canada; d. May 5, 1952, Port Arthur, Ontario, Canada.
17. v. ETHEL ALEXINA GRACE MACLEOD, b. Oct 8, 1885, Harrington, Argenteuil Co., Québec, Canada; d. Apr 21, 1924, Spearhill, Manitoba, Canada.
vi. LILLA JANE GERTRUDE MACLEOD, b. Jun 24, 1888, Harrington, Argenteuil, Québec; d. Feb 8, 1892, Harrington E, Argenteuil Co, Québec.
18. vii. EDITH CHRISTY MCLEOD, b. Apr 25, 1890, Harrington, Argenteuil Co., Québec; d. Dec 10, 1930.
viii. ALEXANDER IRVINE MARSHALL MACLEOD, b. Nov 4, 1895, Harrington, Argenteuil, Québec, Canada; d. Nov 13, 1925, Rivington, Argenteuil, Québec.
4. THOMAS2 MARSHALL (JOHN1, ALEXANDERA) was born Dec 3, 1853 in Québec, Canada. He married MARGARET JANE UNKNOWN abt. 1875. She was born Mar 28, 1861 in Québec.
19. i. ELLEN3 MARSHALL, b. May 20, 1876, Harrington, Québec.
ii. JOHN A. MARSHALL, b. Apr 20, 1879, Québec.
iii. THOMAS MARSHALL, b. Feb 24, 1885, Québec.
iv. MARGARET MARSHALL, b. Jun 11, 1888, Ontario.
v. DUNCAN MARSHALL, b. May 28, 1891, Ontario.
vi. ROBERT MARSHALL, b. Apr 24, 1894, Ontario.
vii. JAMES MARSHALL, b. Oct 31, 1896, Ontario.
5. ROBERT2 MARSHALL (JOHN1, ALEXANDERA) was born Apr 20, 1855 in Ontario, Canada, and died Jan 17, 1918 in Ontario. He married ANN SOMMERVILLE LINTON Oct 16, 1882 in the home of Neil MacRae in Harrington, Québec, daughter of ADAM LINTON and ELLEN REDPATH. She was born Feb 5, 1865 in Edinburgh, Midlothian, Scotland, and died Aug 2, 1952 in at the residence of her daughter in Kars, Ontario.
i. ALEXANDER3 MARSHALL, b. Feb 16, 1884, Québec, Canada; d. Jul 23, 1964, Toronto, Ontario.
20. ii. GEORGE LINTON MARSHALL, b. Sep 6, 1885, Québec, Canada; d. Aug 18, 1966, Toronto, Ontario.
iii. ELLEN REDPATH MARSHALL, b. Jun 9, 1887, Harrington, Québec, Canada; d. Jan 10, 1961, Civic Hospital, Ottawa, Ontario.
21. iv. SARAH ALICE MARSHALL, b. Apr 24, 1892, Québec, Canada; d. Apr 26, 1970, Cornwall, Ontario.
22. v. ROBERT GORDON MARSHALL, b. Apr 24, 1893, Québec, Canada; d. Sep 30, 1979, Englehart, Timiskaming, Ontario.
vi. JOHN MARSHALL, b. Jan 7, 1894, Chelsea, Gatineau County, Québec, Canada; d. Oct 4, 1922, the Haileybury forest fire, Evantural Twp., Timiskaming District, Ontario.
23. vii. JAMES HERBERT MARSHALL, b. Apr 14, 1896, Québec, Canada; d. Dec 17, 1986, Kirkland Lake, Ontario.
24. viii. EARL WILLIAM MARSHALL, b. Apr 16, 1898, Meech Lake, Québec, Canada; d. Jan 29, 1991.
ix. ANNE RHODA MARSHALL, b. Jun 9, 1900, Québec, Canada; d. 1989.
x. MARY AGNES MARSHALL, b. Jan 20, 1903, Meech Lake, Québec; d. Jul 4, 1988, Queensway Carlton Hospital, Ottawa, Ontario; m. HUGH FERGUSSON, 1949; b. Jul 2, 1874, Beeton, Ontario; d. Sep 22, 1968, Manotick, Ontario.
xi. CHRISTINA GERTRUDE JANE MARSHALL, b. Oct 8, 1905, Meech Lake, Québec; d. Jan 4, 2000, Nepean, Ontario.
25. xii. ALBERT EDWARD MARSHALL, b. Jul 1909, Meech Lake, Québec; d. Jan 29, 1951, Englehart, Ontario.
6. JAMES2 MARSHALL (JOHN1, ALEXANDERA) was born abt. 1858 in Québec, Canada, and died Nov 9, 1896 in Harrington, Argenteuil Co., Québec, Canada. He married GRACE ELIZABETH TODD Dec 25, 1884 in St. Andrews Presbyterian Church, Argenteuil, daughter of ANDREW TODD and MARGARET RODGER. She was born Sep 1, 1861 in Québec, Canada, and died May 29, 1947 in Lachute, Argenteuil Co., Québec, Canada.
26. i. GERTRUDE SARAH MAY3 MARSHALL, b. Nov 15, 1885, Ottawa, Ontario, Canada; d. Mar 22, 1963, Elnora, Alberta.
ii. MARGARET GRACE MARSHALL, b. Nov 15, 1885, Ottawa, Ontario, Canada; d. Jul 19, 1886.
27. iii. MARGARET JANE RODGER MARSHALL, b. Sep 29, 1888, Québec; d. Dec 19, 1963, Edison Ave..
28. iv. JOHN ANDREW GORDON MARSHALL, b. Mar 24, 1891, Lachute, Québec, Canada; d. Bef. 1975.
29. v. GRACE ELIZABETH JAMES MARSHALL, b. Jun 29, 1896, Lachute, Québec, canada; d. Apr 17, 1979, Ottawa, Ontario.
7. JOHN ALEXANDER3 MARSHALL (JOHN2, JOHN1, ALEXANDERA) was born Jun 29, 1876 in Harrington E, Argenteuil Co., Québec, and died Jul 7, 1961 in Lachute, Québec. He married MARY JANE CAMPBELL Mar 18, 1925 in Avoca-Rivington United Church, Argenteuil, daughter of WILLIAM CAMPBELL and ELIZABETH MCRAE. She was born Jan 12, 1899 in Harrington E, Argenteuil Co., Québec, and died Apr 3, 1961.
i. JAMES WILLIAM4 MARSHALL, b. Aft. 1925, Harrington E, Argenteuil Co., Québec; d. 1997; m. BARBARA BEAULAH MACRAE, Aug 12, 1950, Avoca-Rivington United Church, Argenteuil; b. Jul 29, 1931, Harrington E, Argenteuil Co., Québec.
8. MALCOLM LAWRENCE3 MARSHALL (JOHN2, JOHN1, ALEXANDERA) was born Sep 27, 1879 in Harrington E, Argenteuil Co., Québec, Canada, and died Dec 2, 1919 in Québec, Canada. He married ELLEN MAUDE DOBBIE Jun 7, 1916 in Avoca-Rivington Prebyterian Church, Argenteuil, daughter of JOHN DOBBIE and JANE MCOUAT. She was born Aug 29, 1878 in Harrington, Argenteuil Co., Québec, Canada, and died Nov 7, 1963 in Lachute, Québec, Canada.
i. JEAN LORNE4 MARSHALL, b. May 21, 1917, Harrington E, Argenteuil Co., Québec; d. May 13, 2002, Lachute, Argenteuil Co., Québec; m. ROSS WILLARD SWAIL, Aug 27, 1938, Avoca-Rivington United Church, Argenteuil, Québec; b. Dec 1, 1913, Québec; d. Dec 16, 1981.
ii. SON MARSHALL, b. Aug 13, 1918; d. Aug 13, 1918.
9. SARAH ANN3 MARSHALL (JOHN2, JOHN1, ALEXANDERA) was born Jun 16, 1881 in Harrington E, Argenteuil Co., Québec, and died Oct 2, 1959 in Montreal, Québec. She married JOHN LUNN MACKAY Sep 18, 1907 in St. Mungo's Presby., Cushing, Argenteuil, Québec, son of ROBERT MACKAY and AGNES LUNN. He was born Jan 18, 1884 in East Hawkesbury Twp, Prescott Co., Ontario, and died Jul 7, 1951 in Montreal, Québec.
i. GRACE LUNN4 MACKAY, b. Nov 24, 1909, Montreal, Québec; d. Jan 10, 1984, Osgoode, Ontario; m. LAWRENCE KENDALL SUDDARD, Dec 14, 1939, Ottawa, Ontario; b. Aug 14, 1911, Gaspé, Québec, Canada; d. Nov 21, 1988, Montreal, Québec.
ii. JOHN CLIFFORD MACKAY, b. Jan 17, 1914, Montreal, Québec; d. Feb 9, 2000, Lachute, Argenteuil, Québec; m. DORIS MAY HUTCHINSON, Jul 5, 1941, Montreal, Québec, Canada; b. Oct 16, 1918, Vankleek Hill, Prescott County, Ontario, Canada; d. Jan 18, 2003, Lachute, Argenteuil, Québec.
iii. ALLAN JAMES MACKAY, b. Sep 18, 1916, Montreal, Québec; d. May 26, 1997, Toronto, Ontario; m. MARGARET ISABEL GORDON, Sep 15, 1945, Wesley United Church, Montreal, Québec; b. Sep 5, 1918, Montreal, Québec; d. Mar 12, 2004, Toronto, Ontario.
10. MARGARET JANE GRACE3 MARSHALL (JOHN2, JOHN1, ALEXANDERA) was born Jun 2, 1888 in Harrington E, Argenteuil Co., Québec, and died Apr 21, 1957 in Harrington E, Argenteuil Co., Québec. She married RODERICK 'TOOT' MACTAVISH Aft. Jun 1911, son of DOUGALD MACTAVISH and FLORA MCRAE. He was born May 27, 1887 in Harrington, Argenteuil, Québec, and died Feb 10, 1975.
i. DELBERT RODERICK4 MACTAVISH, b. Mar 7, 1912, Boston, MA, USA; d. Oct 30, 1994, Lachute, Argenteuil, Québec; m. FLORENCE 'BUNTY' MACMILLAN, Jun 22, 1936, Henry's Pres. Church, Lachute, Québec; b. Jul 31, 1914, Montreal, Québec, Canada; d. Dec 28, 1995, Lachute, Argenteuil, Québec.
ii. FLORENCE CATHERINE GRACE MACTAVISH, b. May 20, 1913; d. Jun 27, 1991, Calumet, Argenteuil, Québec, Canada; m. KENNETH VICTOR MCHARDY, Mar 27, 1948, Lachute United Church,Argenteuil, Québec; b. Sep 7, 1907.
iii. LAWRENCE A. MACTAVISH, b. Jul 17, 1915; d. Oct 1991; m. DOROTHY C. BATES, Apr 26, 1941, Lachute or Calumet, Argenteuil, Québec; b. Aug 31, 1922; d. Apr 18, 1997.
iv. MARGARET MACTAVISH, b. abt. 1917; m. RAYMOND WARD, Jun 5, 1943, Henry's Presbyterian, Lachute, Québec; b. Nov 7, 1917; d. Oct 1983.
v. DOUGLAS M. MACTAVISH, b. Jan 10, 1920; d. Dec 26, 1984; m. HAZEL CATHERINE DEWAR, Oct 7, 1944, Rivington, Argenteuil, Québec; b. Apr 24, 1921.
vi. GORDON MACTAVISH, b. Jan 15, 1926; d. Mar 11, 1999; m. SHIRLEY MACMILLAN, Feb 22, 1947, Lachute, Argenteuil, Québec; b. Mar 6, 1931.
vii. RODERICK MACTAVISH, b. Jul 21, 1929; d. Dec 13, 1989; m. AVIS MAY MACRAE; b. May 6, 1941, Harrington, Argenteuil Co., Québec.
11. HANNAH EDNA3 MARSHALL (JOHN2, JOHN1, ALEXANDERA) was born May 28, 1890 in Harrington E, Argenteuil Co., Québec, and died Nov 14, 1978 in Grosse Point Park, Detroit, Michigan, USA. She married RONALD JOHN MCDONALD Oct 9, 1926 in New York City, USA, son of JOHN MCDONALD and ISABELLA JACKSON. He was born Oct 15, 1895 in Errol, Perthshire, Scotland, and died Jul 23, 1964 in Detroit, Michigan, USA.
i. EDNA ISABEI VIVIEN4 MCDONALD, b. Feb 22, 1928, Santo Domingo, Dominican Republic.
12. EMMA MABEL CORA3 MARSHALL (JOHN2, JOHN1, ALEXANDERA) was born Apr 10, 1892 in Harrington E, Argenteuil Co., Québec, and died Jan 1, 1921 in Harrington E, Argenteuil Co., Québec. She married RALPH B. GRAHAM Jun 21, 1916, son of JOHN GRAHAM and EMMA. He was born Nov 10, 1892 in Québec.
i. GRACE EMMA4 GRAHAM, b. Apr 23, 1917; m. AUGUST LUDWIG CARL, Jun 17, 1944; b. Nov 27, 1911; d. Feb 4, 1990, Westmount, Québec, Canada.
ii. HERBERT JOHN GRAHAM, b. Jun 24, 1918; d. Oct 23, 2003, Montreal, Québec; m. MARIAN BRAY, Jul 22, 1944; b. 1924.
iii. LORNA IRENE GRAHAM, b. Sep 13, 1919; d. Dec 7, 1991, St. Jovite, Québec, Canada; m. RAOUL EMOND, May 31, 1941; b. abt. 1916.
iv. DOREEN GRAHAM, b. abt. 1920; d. Aft. 2003.
13. WILLIAM M. A.3 MACLEOD (JANE2 MARSHALL, JOHN1, ALEXANDERA) was born Apr 29, 1878 in Harrington, Argenteuil Co., Québec, Canada, and died Aug 7, 1940 in Harrington, Argenteuil Co, Québec. He married (1) CHRISTINA (BETHUNE) BEATON. She was born Nov 13, 1882 in Québec, and died Feb 5, 1953. He married (2) SARAH CATHERINE MACLEOD Jul 26, 1904, daughter of PHILIP MCLEOD and KATHERINE MCPHAIL. She was born Feb 3, 1871 in Grenville Twp, Argenteuil, Québec, and died Aug 6, 1940 in Harrington, Argenteuil Co, Québec.
i. ALLAN4 MACLEOD, b. 1917.
ii. EARL PHILIP ALEXANDER4 MACLEOD, b. Aug 25, 1904, Harrington, Argenteuil Co, Québec; d. Mar 4, 1986, Lachute, Argenteuil, Québec, Canada; m. MARGARET FLORENCE MACRAE, Nov 25, 1923, St. Matthew's Anglican Church, Grenville, Québec; b. Nov 24, 1904, Harrington, Argenteuil Co, Québec; d. Mar 4, 2001, Lachute, Argenteuil, Québec.
iii. WILLIAM CHARLES NEIL MACLEOD, b. abt. 1908, Harrington, Argenteuil Co, Québec; d. Nov 15, 1929, Port Lachine, Québec.
14. ALICE ANN3 MACLEOD (JANE2 MARSHALL, JOHN1, ALEXANDERA) was born Jan 6, 1880 in Harrington, Argenteuil Co., Québec, Canada, and died Nov 5, 1932. She married DUNCAN CAMERON. He was born in Thunder Bay, Ontario, Canada.
ii. HAROLD ALEXANDER CAMERON, b. Dec 5, 1910.
iii. LILLA CHRISTINE JANE CAMERON, b. Jul 11, 1916, Port Arthur, Ontario, Canada; d. Sep 14, 1930, Harrington E, Argenteuil Co, Québec.
iv. WILLIAM HUGH CAMERON, b. May 29, 1919, Harrington E, Argenteuil Co, Québec; d. Sep 22, 1944, France.
15. JAMES3 MACLEOD (JANE2 MARSHALL, JOHN1, ALEXANDERA) was born Oct 2, 1881 in Harrington, Argenteuil Co., Québec, Canada, and died Apr 5, 1967. He married ANNIE MCCUTCHEON Apr 25, 1917 in Avoca Rivington Presbyterian Church. She was born Mar 31, 1897 in Rivington, Québec, Argenteuil, Québec, Canada, and died 1991.
i. MILDRED ANN4 MACLEOD, b. Oct 25, 1917, Rivington, Argenteuil, Québec; d. 1996; m. WENDELL BOYD, Nov 20, 1937; b. Jun 23, 1910, Argyle, Carleton, New Brunswick, Canada.
ii. ALDEN MACLEOD, b. Sep 12, 1921, Rivington, Argenteuil, Québec; d. Oct 15, 1955.
iii. MARGARET BERNICE MACLEOD, b. 1927; m. STANLEY STEWART POULTER, Apr 13, 1951, Hull, Québec; b. 1918.
16. JOHN CHARLES3 MACLEOD (JANE2 MARSHALL, JOHN1, ALEXANDERA) was born Jul 15, 1883 in Harrington, Argenteuil Co., Québec, Canada, and died May 5, 1952 in Port Arthur, Ontario, Canada. He married ELSIE SINCOX. She was born in Fort Frances, Ontario, Canada, and died May 12, 1976 in Thunder Bay, Ontario.
ii. CHARLES DANIEL 'DAN' MACLEOD, b. Oct 15, 1921; d. Apr 10, 1989.
17. ETHEL ALEXINA GRACE3 MACLEOD (JANE2 MARSHALL, JOHN1, ALEXANDERA) was born Oct 8, 1885 in Harrington, Argenteuil Co., Québec, Canada, and died Apr 21, 1924 in Spearhill, Manitoba, Canada. She married WILLIAM JAMES ROGERS, son of MICHAEL ROGERS and MARY UNKNOWN. He was born May 31, 1886 in Lakefield, Argenteuil, Québec, Canada, and died Oct 31, 1938 in Spearhill, Manitoba.
i. JEAN4 ROGERS, m. NEILS ERICSON.
ii. JOHN CHARLES ROGERS, b. Jun 13, 1913; d. Nov 12, 1924.
18. EDITH CHRISTY3 MCLEOD (JANE2 MARSHALL, JOHN1, ALEXANDERA) was born Apr 25, 1890 in Harrington, Argenteuil Co., Québec, and died Dec 10, 1930. She married WILLIAM PEARSON. He was born 1884 in England, and died 1963.
i. IRVINE4 PEARSON, b. Oct 19, 1919, Harrington, Argenteuil Co., Québec; d. Jul 14, 1994; m. LEONA CAMPBELL, Dec 29, 1943, Lachute United Church, Lachute, Argenteuil, Québec; b. Feb 27, 1923, Harrington, Argenteuil, Québec, Canada.
ii. MERVIN PEARSON, b. May 1921; d. 1980; m. BETTY ST. GERMAIN.
iii. GIBSON G. PEARSON, b. Oct 10, 1925; d. 1997; m. INEZ MCANDREW, Sep 3, 1955.
iv. FRANCES MARY PEARSON, b. Sep 27, 1926; Adopted child; m. ELMER WILLIAM DEWAR, May 11, 1946, Lachute United Church, Lachute, Argenteuil; b. Apr 4, 1915; d. Sep 13, 1981, Lachute, Argenteuil Co., Québec, Canada.
19. ELLEN3 MARSHALL (THOMAS2, JOHN1, ALEXANDERA) was born May 20, 1876 in Harrington, Québec. She married WILLIAM ELLIS Sep 29, 1896 in Presbyterian Manse, Petrolia, Lambton Co., Ontario, son of WILLIAM ELLIS and JANE UNKNOWN. He was born Jun 22, 1871 in Moore Twp., Lambton Co., Ontario.
i. WILLIAM4 ELLIS, b. Jul 29, 1899.
20. GEORGE LINTON3 MARSHALL (ROBERT2, JOHN1, ALEXANDERA) was born Sep 6, 1885 in Québec, Canada, and died Aug 18, 1966 in Toronto, Ontario. He married JEAN CAMERON.
i. CAMERON4 MARSHALL, m. BLANCH HIGNELL.
ii. ROBERT MARSHALL, m. MARJORIE ?.
21. SARAH ALICE3 MARSHALL (ROBERT2, JOHN1, ALEXANDERA) was born Apr 24, 1892 in Québec, Canada, and died Apr 26, 1970 in Cornwall, Ontario. She married ALEXANDER HERBERT MEYER 1914, son of FREDERICK MEYER and ELIZABETH MCNAUGHTON. He was born abt. 1885 in Québec, Canada, and died Feb 5, 1961 in 15 Rideau St., Cornwall, Ontario.
i. GEORGE4 MEYER, m. MARGARET HENLEY.
ii. ANNIE MEYER, m. SIDNEY RITCHIE.
iii. FREDERICK MEYER, m. HELEN AULT.
iv. KENNETH MEYER, m. (1) AVA MIRR; m. (2) GWEN HOGG.
v. WESLEY MEYER, m. (1) EILEEN CROSIER; m. (2) GLENDA?.
vi. GORDON MEYER, m. HELEN BALDWIN.
vii. DOUGLAS MEYER, d. Aft. Feb 2005; m. JO GLEN.
viii. DONALD PERCY MEYER, b. Nov 11, 1930, Cornwall, Ontario; d. Feb 15, 2005, Chilliwack, BC; m. (1) ZEE UNKNOWN; m. (2) MYRNA UNKNOWN.
ix. CLIFFORD MEYER, m. JANICE BROWN.
22. ROBERT GORDON3 MARSHALL (ROBERT2, JOHN1, ALEXANDERA) was born Apr 24, 1893 in Québec, Canada, and died Sep 30, 1979 in Englehart, Timiskaming, Ontario. He married OLIVE ALICE FERGUSSON Jan 31, 1935 in St. Andrews Presbyterian, New Liskeard, Timiskaming, daughter of HUGH FERGUSSON and DIANA CARR. She was born Mar 30, 1907 in Earlton, Ontario, and died Apr 17, 1993 in Englehart, Timiskaming, Ontario.
i. EDITH4 MARSHALL, b. Oct 21, 1936, Earlton, Ontario.
ii. SHIRLEY MARSHALL, b. Sep 1, 1939, Earlton, Ontario; m. WILLIAM GETTY, Dec 31, 1966, Englehart, Ontario; b. Mar 2, 1944, Wheatley.
iii. LAUREEN MARSHALL, b. Apr 22, 1941, Earlton, Ontario.
iv. JOHN A. MARSHALL, b. Aug 27, 1942, Englehart, Ontario; m. (1) HEATHER A. MACDONALD, Apr 6, 1962, Sudbury, Ontario; b. Sep 9, 1942, Toronto, Ontario; d. May 25, 1973, Sudbury, Ontario; m. (2) JANE K. ROSEBOROUGH, Dec 1, 1973, Timmins, Ontario; b. Dec 17, 1948, Timmins, Ontario.
v. ROBERT H. MARSHALL, b. Dec 25, 1943, Englehart, Ontario; m. CHRISTINE VIPOND, Aug 19, 1969, Englehart, Ontario.
vi. JUNE MARSHALL, b. May 28, 1947, Englehart, Ontario; m. SIDNEY J. WALTON, Jul 12, 1969, Englehart, Ontario; b. Mar 10, 1944, Englehart, Ontario.
vii. EVELYN MARSHALL, b. Mar 14, 1952, Englehart, Ontario; m. RANDY ROGERS, Jul 23, 1977, Englehart, Ontario; b. Jul 16, 1954, Sudbury, Ontario.
23. JAMES HERBERT3 MARSHALL (ROBERT2, JOHN1, ALEXANDERA) was born Apr 14, 1896 in Québec, Canada, and died Dec 17, 1986 in Kirkland Lake, Ontario. He married LUCY MARGARET RADMORE Oct 27, 1915 in Aylmer, Québec, daughter of WILLIAM RADMORE and FANNY FARRIS. She was born Jun 4, 1883 in Eardly, Ottawa, Québec, Canada, and died Bef. 1986.
i. GERTRUDE LUCY4 MARSHALL, m. LESLIE HUTCHERCROFT.
24. EARL WILLIAM3 MARSHALL (ROBERT2, JOHN1, ALEXANDERA) was born Apr 16, 1898 in Meech Lake, Québec, Canada, and died Jan 29, 1991. He married ESTELLA MARY GEORGE Jun 16, 1936 in Kirkland Lake, Ontario. She was born Jun 1, 1915 in Heaslip, Ontario, and died Jun 9, 2004 in North Bay, Ontario.
i. DAVID WILLIAM4 MARSHALL, b. Jun 2, 1937, Kirkland Lake, Ontario; m. (1) NORMA FAITH SHORTT, Oct 23; m. (2) JEANETTE SMITH, Jun 3, 1999.
ii. EILEEN GLENDA MARSHALL, b. Sep 12, 1938, Kirkland Lake, Ontario; d. Sep 18, 1938, Kirkland Lake, Ontario.
iii. EARL WAYNE MARSHALL, b. Feb 11, 1940, Kirkland Lake, Ontario; m. MARILYN CORCORAN, May 2, 1964.
iv. DOREEN ESTELLA MARSHALL, b. Oct 22, 1941, Englehart, Ontario; m. STANLEY DODS, Jun 24, 1967; b. Jul 17, 1934; d. Nov 12, 1991, Ottawa, Ontario.
v. KENNETH LLOYD MARSHALL, b. Jan 24, 1943, Englehart, Ontario; m. CAROLE LAURETTE FORTIN, Oct 9, 1970, Noranda, Québec.
vi. MERVYN GEORGE MARSHALL, b. Aug 16, 1945, Englehart, Ontario; m. JOYCE MCNEIL.
25. ALBERT EDWARD3 MARSHALL (ROBERT2, JOHN1, ALEXANDERA) was born Jul 1909 in Meech Lake, Québec, and died Jan 29, 1951 in Englehart, Ontario. He married GLADYS MARGARET RUDD. She died Jul 5, 1984.
i. MARGARET4 MARSHALL, m. HAROLD CAVANAGH.
26. GERTRUDE SARAH MAY3 MARSHALL (JAMES2, JOHN1, ALEXANDERA) was born Nov 15, 1885 in Ottawa, Ontario, Canada, and died Mar 22, 1963 in Elnora, Alberta. She married GORDON STEWART MACRAE Feb 14, 1912 in St. Matthew Presbyterian Church, Montreal, son of JOHN MACRAE and ELIZABETH SCOTT. He was born May 13, 1884 in Lachute, Argenteuil County, Québec, Canada, and died Feb 24, 1956 in Elnora, Alberta.
i. GEORGE HENRY4 MACRAE, b. Jun 10, 1914, Arthurvale, Ghost Pine Creek, Alberta; d. Jan 25, 1980; m. MONA BUCKLEY.
ii. JAMES MARSHALL MACRAE, b. Nov 28, 1917, Huxley, Alberta; m. (1) MARGARET NICKERSON, Nov 1943; m. (2) CATHERINE HAMM, Dec 21, 1971; d. Nov 1982.
iii. HECTOR EARL MACRAE, b. May 27, 1920, Huxley, Alberta, Canada; d. Sep 22, 1943, Germany.
27. MARGARET JANE RODGER3 MARSHALL (JAMES2, JOHN1, ALEXANDERA) was born Sep 29, 1888 in Québec, and died Dec 19, 1963 in Edison Ave.. She married WILLIAM HASLEY IRVINE Dec 31, 1913.
i. WILLIAM JAMES4 IRVINE, b. Oct 10, 1914; d. 1997; m. MARGUERITE WARRINGTON, Apr 26, 1941; b. Nov 25, 1915; d. 1997.
ii. DOUGLAS C. IRVINE, m. LOUISE RODGERS.
iii. MARGARET ELIZABETH IRVINE, m. S. BEAUDRY.
28. JOHN ANDREW GORDON3 MARSHALL (JAMES2, JOHN1, ALEXANDERA) was born Mar 24, 1891 in Lachute, Québec, Canada, and died Bef. 1975. He married STELLA MAE VALIQUETTE Sep 25, 1912 in Ottawa, Ontario, daughter of PIERRE VALIQUETTE and MARY O'BRIEN. She was born Mar 28, 1886 in Ontario, Canada, and died Jun 14, 1975.
i. ELIZABETH EILEEN4 MARSHALL, m. ERNEST NYMARK.
29. GRACE ELIZABETH JAMES3 MARSHALL (JAMES2, JOHN1, ALEXANDERA) was born Jun 29, 1896 in Lachute, Québec, canada, and died Apr 17, 1979 in Ottawa, Ontario. She married A. BRUCE TAYLOR.
i. JUNE ELIZABETH4 TAYLOR, m. L. JAMES BYRNE.

matches: v. v. v. v. v. v. v. v. v. v.


text:
A present technology intelligently retargets invitational content to a user by maintaining a user profile that includes data descriptive of the user's interaction with invitational content previously presented to the user and making decisions regarding retargeting based on an analysis of the user profile. The information in the user profile is not limited to whether or not the user completed a conversion action associated with invitational content presented. Rather, the profile is expanded to include such information as where on the conversion continuum the user abandoned the process and details of how the invitational content was presented to the user, e.g. colors used, situation, and message. When presented with a request for invitational content, the system uses the profile information to influence which content is selected and how it is presented to the user. This enables the system to re-present invitational content in a form and/or situation where the user is more likely to complete the conversion action.
The present disclosure relates to electronic content delivery and more specifically to intelligent targeting of invitational content to a user based on the user's previous activities.
Targeted content delivery has long been an accepted means of conveying a desired message to an audience. Instead of creating a single message and delivering it to every member of the general public, content providers will attempt to identify the intended audience and shape the message so that it appeals to that audience. Once the content provider determines the intended audience they can target that audience by selecting the best content delivery channels. For example, if their intended audience is the residents of a particular city then delivering the message through the local newspaper or on a billboard in the city may be the appropriate channel. However, if their audience is a smaller subset of the population or is more geographically diverse such a delivery channel will be suboptimal. Content providers will also often target the content delivery by sculpting the content and appearance of the message for the intended audience. These techniques enable content providers to optimize their resources.
The development of digital content has enabled new techniques of targeting content to an audience. However, these techniques are often overly simplistic because targets are often selected based on a limited number of inputs. For example, if a user purchases a particular item on a website, additional related items can be suggested, or if a user visits a travel website, travel related content can be presented. Such methods are overly simplistic and fail to consider other important factors when targeting content to an audience.
The presently disclosed technology intelligently retargets invitational content to a user, and in some specific embodiments the user is a user of a device configured to communicate via a mobile network, i.e., a device that can be characterized in part by its use of a non-persistent connection, or multiple connections. It does so by first identifying a user on a network and analyzing usage data associated with that user. The usage data includes data describing contextual characteristics, which can be any data related to the user's network usage in one or more contexts such as usage data with respect to a presented item of invitational content, usage data with respect to favorite content, usage data with respect to temporal considerations, and other data which is more fully described herein.
The collective data can be used to create one or more user profiles, which can be analyzed and used to allow a content delivery system to more intelligently select content for a user. In some embodiments, the more intelligently selected the content is, the more efficient it is at eliciting a desired user response. For example, data can be collected regarding a user's responsiveness to a presented item of invitational content, and based on an analysis of that data, and the other data in the user profile, the item of invitational content can be re-presented to the user in a modified form or different context and accordingly, be more likely to elicit the invited response.
In one example, an item of invitational content that was previously presented and failed to gain the desired response can be re-presented on a different channel, e.g. website, application, groups of websites or applications having similar content, a device used to present content, or any other hardware or software used to present content to a user. In such examples, the different channel can be a channel on which the user previously converted a different item of invitational content; the channel can be a favorite channel which the user visits/uses more often; the channel can be one which is associated with a content category for which the user is known to have previously converted an item of invitational content; and the channel can be one which other users have been more likely to convert the same or a different item of invitational content.
In another example, an item of invitational content that was previously presented and failed to gain the desired response can be re-presented in a modified form. In such examples, the modified form comprises a different color scheme; the modified form comprises an incentive to accept the terms of the invitation; the modified form comprises less onerous requirements to perform a conversion action; the modified form can include other changes to the requested action by the user; and the modified form can include a modified product offering, etc.
In another example, an item of invitational content that was previously presented and failed to gain the desired response can be re-presented at a different time or when the user is in a different place. In such examples, the different time can be a time when it is more likely that the user will consider the invitational content, such as perhaps the weekend as opposed to working hours. The different place likewise can be a place where it is more likely that the user will consider the invitational content, such as on a train or bus or at home as opposed to while driving or at work.
The examples provided above are merely illustrative of some of the ways in which the user's profile is used to inform decisions to retarget content such as invitational content.
FIG. 5 illustrates an example system embodiment.
Various embodiments of the disclosure are discussed in detail below. While specific implementations are discussed, it should be understood that this is done for illustration purposes only. A person skilled in the relevant art will recognize that other components and configurations may be used without parting from the spirit and scope of the disclosure. The present disclosure addresses the need in the art for improved methods of selecting invitational content presented to a user based on the user's interactions with previously presented invitational content.
The presently disclosed system and method is particularly useful for assembling and delivering targeted content to a user. An exemplary system configuration 100 is illustrated in FIG. 1 wherein electronic devices communicate via a network for purposes of exchanging content and other data. The system can be configured for use on a local area network such as that illustrated in FIG. 1. However, the present principles are applicable to a wide variety of network configurations that facilitate the intercommunication of electronic devices. For example, each of the components of system 100 in FIG. 1 can be implemented in a localized or distributed fashion in a network.
In system 100, a content package is delivered to user terminals 102 1 . . . 102 n (collectively “102”) connected to a network 104 by direct and/or indirect communications with a content delivery system 106. In particular, the content delivery system 106 receives a request for an electronic content, such as a web page, an application, or media, etc., from one of user terminals 102. Thereafter, the content delivery system 106 assembles a content package in response to the request and transmits the assembled content package to the requesting one of user terminals 102. In some embodiments, the server has preassembled the content package before the request is received. The content in the assembled content package can include text, graphics, audio, video, executable code or any combination thereof. Further, the assembled content packages can include invitational content designed to inform or elicit a pre-defined response from the user and that can vary over time. The content delivery system can include a communications interface 107 to facilitate communications with the user terminals 102 and any other components familiar to those of ordinary skill in the art.
The content delivery system 106 includes a content management module 108 that facilitates generation of the assembled content package that includes invitational content. Specifically, the content management module can combine content from one or more primary content providers 110 1 . . . 110 n (collectively “110”) and content from one or more secondary content providers 114 1 . . . 114 n (collectively “114”) to generate the assembled content package for the user terminals 102. In some embodiments, the content management module can create a package from only secondary content, or only secondary content. The package need not contain both primary and secondary content.
Although, primary and secondary providers 110, 114 are presented herein as discrete, separate entities, this is for illustrative purposes only. In some cases, the primary and secondary providers 110, 114 can be the same entity. Thus, a single entity may define and provide both primary and secondary content. Although, both the primary and secondary content can comprise invitational content, in most instances, the secondary content will comprise the invitational content portion.
For example, in the case of a web page delivered to a requesting one of user terminals 102, the content management module 108 can assemble a content package by requesting the data for the web page from one of the primary content providers 110 maintaining the web page. Then the time-varying invitational content on the web page, which is provided by the secondary content providers 114, is obtained according to the arrangement between the primary and secondary content providers 110 and 114. For example, the invitational content from the secondary providers 114 can be selected based on a guaranteed number of impressions. Alternatively, the invitational content from the secondary providers 114 can be selected based on the context of the web page. In another example arrangement, the primary content can be sent separately, from a source other than the content delivery system disclosed here, or the primary content can have been previously downloaded and cached on the user terminal 102 requesting the content. In such instances, the content delivery system can send a content package containing time-varying invitational content for use, or display with, or related to, the primary content. However, any other arrangements and configuration for selecting invitational content from the secondary providers 110 can also be used.
Although the content management module 108 can be configured to request that data be sent directly from content providers 110 and 114, a cached arrangement can also be used to improve performance of the content delivery system 106 and improve overall user experience. That is, the content delivery system 106 can include a content database 112 for locally storing/caching content maintained by content providers 110 and 114. The data in the content database 112 can be refreshed or updated on a regular basis to ensure that the content in the database 112 is up to date at the time of a request from a user terminal. However, in some cases, the content management module 108 can be configured to retrieve data directly from content providers 110 and 114 if the metadata associated with the data in content database 112 appears to be outdated or corrupted.
In the various embodiments, the content delivery system 106 can also include a unique user identifier (UUID) database 115 that can be used for managing sessions with the various user terminal devices 102. The UUID database 115 can be used with a variety of session management techniques. For example, the content delivery system 106 can implement an HTTP cookie or any other conventional session management method (e.g., IP address tracking, URL query strings, hidden form fields, window name tracking, authentication methods, and local shared objects) for user terminals 102 connected to content delivery system 106 via a substantially persistent network session. However, other methods can be used as well. For example, in the case of handheld communications devices, e.g. mobile phones, smart phones, tablets, or other types of user terminals connecting using multiple or non-persistent network sessions, multiple requests for content from such devices may be assigned to a same entry in the UUID database 115. Such an assignment can be provided by analyzing requesting device attributes in order to determine whether such requests can be attributed to the same device. Such attributes can include device or group-specific attributes.
As described above, content maintained by the content providers 110 and 114 can be combined and/or presented according a predefined arrangement between the two content providers, which can be embodied as a set of rules. In an arrangement where the content delivery system assembles the content package from multiple content providers, these rules can be stored in a rules database 116 in content delivery system 106 and content management module 108 can be configured to assemble the content package for user terminals 102 based on these rules. The rules can specify how to select content from secondary content providers 114 and the primary content providers 110 in response to a request from one of user terminals 102. For example, in the case of a web page maintained by one of primary providers 110 and including variable advertisement portions, the rules database 116 can specify rules for selecting one of the secondary providers 114. The rules can also specify how to select specific content from the selected one of secondary providers 114 to be combined with the content provided by one of primary providers 110. Once assembled, the assembled content package can be sent to a requesting one of user terminals. However, the content package is not limited to the content from content providers 110 and 114. Rather, the content package can include other data generated at the content delivery system 106.
As described above, arrangements between the content providers 110 and 114 can result in content from one of primary content providers 110 being combined with invitational content from multiple ones of secondary content providers 114, based on the rules database 116. Although the rules database 116 can be accessed each time a request is received from one of user terminals 102, such a configuration can limit performance. Therefore, in many cases, the rules in rules database 116 are used to define at least one pool of invitational content from the secondary providers 114. Thus, when the content management module 108 assembles a content package, the content management module 108 first constructs and/or retrieves the pool. Thereafter, the content management module 108 can select an invitational content from one of the secondary content providers from the pool and form the assembled content package.
As used herein, the term “contextual characteristics” refers to the characteristics of a particular content package as related to a particular audience in the network 104 associated with one or more of user terminals 102. Contextual characteristics can include channel characteristics, demographic characteristics, behavioral characteristics, and spatial-temporal characteristics. Channel characteristics can define the specific delivery channel being used to deliver a content package. For example, channel characteristics can include a type of electronic content, a type of device or user terminal, a carrier or network provider, or any other characteristic that defines a specific delivery channel for the content package. Spatial-temporal characteristics can define a location, a date, a time, or any other characteristic that defines a geographic location and/or a time for delivery of the content package. Demographic characteristics can define personal and/or socio-economic characteristics of the user requesting the content package. Behavioral characteristics can define user behaviors for one or more different types of content, separately or in combination with any other contextual characteristics. That is, different behavioral characteristics may be associated with different channel, demographic, or spatial temporal characteristics. For example, users may be associated with higher conversion or response rates for some types of delivery channels.
One concern with the arrangements typically entered into by secondary content providers 114 is that they can result in invitational content of little or no interest being presented to users many times. As a result, even though a desired number of impressions can be achieved, the rate of response to such invitational content may be low and/or the resulting targeted audience may be incorrect or suboptimal. As a result, content providers 110 and 114 can be negatively impacted. For example, if the primary content providers 110 receive compensation based on the number or rate of conversions of invitational content provided by secondary content providers 114, the resulting low conversion rate will result in lower revenues for the primary content providers 110. At the same time, the lower number or rate of conversions of invitational content can result in lower exposure or sales for the secondary content provider 114. In the case of an arrangement based on the number of impressions, the primary content provider 110 would be compensated, but the lower number or rate of conversions of invitational content can result in lower exposure or sales for the secondary content provider 114. As a result, such secondary content providers 114 may opt to pursue relationships with other primary content providers 110, resulting in potential loss of revenues for some primary content providers 110.
The various embodiments therefore provide systems and methods for improving audience targeting by managing the presentation of invitational content from such secondary content providers 114. In particular, systems and methods are provided for adjusting invitational content within content delivery system 106 in order to provide invitational content at a user terminal that is of greater interest to an associated user. As a result, improved targeting of users is provided, which generally correlates to an increase in desired responses or conversions. In the various embodiments, the invitational content is adjusted based on the user's interactions with previously presented invitational content. As a result, the invitational content is presented in a manner and/or at a time that will likely elicit greater response from the requesting user.
In some embodiments, delivery system 106 can provide an invitational content retargeting module 128 for retargeting invitational content previously presented. The invitational content retargeting module 128 receives the invitational content, a context associated with a request, and identifying information for the user associated with the request. For example, such information can be received from the content management module 108 or other components in system 100. Thereafter, the invitational content retargeting module 128 can access a user profile database 124 to retrieve a user profile of previously presented invitational content and adjust the invitational content accordingly. The retargeted invitational content can then be provided, for example, to the content management module 108, which can thereafter assemble and deliver a content package to the requesting user terminal. Such a method is described in greater detail below with respect to FIG. 2.
In operation, delivery system 106 can provide a pool processing module 122 for creating a user-specific pool of invitational content. A pool-processing module 122 receives contextual characteristics and identifying information for the user associated with the request. Such information can be received from the content management module 108 or other components in system 100. The pool-processing module 122 operates on a pool of invitational content. The pool-processing module 122 can receive the pool along with the content and user identification or, alternatively, it can construct the pool. The pool processing module 122 can construct the pool by retrieving invitational content from the content database 112, the content management module 108, or directly from content providers 110 and 114. If the pool of invitational content has not already been adjusted to eliminate content not applicable to the contextual characteristics, the pool-processing module 122 can make this adjustment. Thereafter, the pool-processing module 122 can access a user-profile database 124, which can be constructed based at least in part on recorded contextual characteristics related to the user, to retrieve a user profile of previously presented invitational content to create the user-specific pool. The user-specific pool can then be provided, for example, to the content management module 108, which can thereafter assemble and deliver a content package to the requesting user terminal. Such a method is described in greater detail below with respect to FIG. 3.
In the various embodiments, the user-profile database 124 can be updated using a user-profile-update module 126. In some cases, the user-profile-update-module 126 can be configured to add additional profile data to the profile database 124. However, in other cases, an extended profile of user interactions with invitational content may not accurately reflect a current interest of users. Accordingly, update module 126 can also be configured to maintain the profile database 124 to include only more recently acquired data. For example, the update module 126 can be configured to maintain the profile database 124 to include only data from the last two to three months. However, the update module 126 can be configured to adjust the data in profile database 124 to cover any span of time. In some instances the update module 126 can update the profile database 124 in real-time. In some instances, the update module 126 can update the profile database 124 at least every week, or every day.
In the various embodiments, the system can include one or more additional databases implemented using various data structures such as, but not limited to, a relational database (RDB) 130, a graph database 132, a hierarchical database 134, a key/values stores database 136, and a distributed stores database 140.
FIG. 2 is a flowchart illustrating steps in an exemplary method 200 for retargeting invitational content based on a user's past interactions with invitational content. For the sake of clarity, this method is discussed in terms of an exemplary system such as is shown in FIG. 1. Although specific steps are shown in FIG. 2, in other embodiments a method can have more or less steps than shown. First, the content delivery system 106 identifies the user associated with the user terminal (202). This identification can be performed in a variety of ways. For example, as described above, when the delivery system 106 receives a request for a content package, the request can include some identifying information, associated with the requesting user terminal or the associated user. This information can then be correlated to an entry in the UUID database 115 to retrieve an identity of the user. In other configurations, the user can be identified by analyzing the requesting device's attributes in order to determine whether such requests can be attributed to a same device, also as described above. Other methods can also be used.
Meanwhile, the content delivery system 106 collects data descriptive of the user's interaction with one or more other items of invitational content within the network (204). The collected data can include any number of characteristics associated with a user's interaction with invitational content or any contextual characteristics such as channel, demographic, behavioral, and/or special-temporal characteristics. For example, the information can include where on the conversion continuum the user abandoned the process: did the user take the first step of maybe clicking on a supplied link or did the user make it all the way to placing an item in their electronic shopping cart. Additionally, information can be collected about the invitational content itself, e.g. colors, size, font, or what was actually offered. Alternatively, the system can make use of the relationship between the primary and secondary content, e.g. were the two tightly related or completed unrelated. The information can further include the channel, the device the user was using, the time of day, and/or day of week. A more extensive data set, both in terms of what is collected and for how many items of invitational content, can lead to more effective retargeting.
As discussed above, the delivery system 106 includes a user profile database 124. In some embodiments, the collected data can be stored in the user profile database 124. The delivery system 106 can receive a direct request to update one or more user profiles. The update request can come directly from the user or any other device capable of communicating with the delivery system 106, such as other content delivery networks or websites. The update request can occur at any time. The update request can include any of the collected data described above such as characteristics of one or more user's interaction with invitational content and/or contextual characteristics. Alternatively, the request for a content package can include the collected data. Once received, the collected data can be supplied to the user-profile-update module 126, which will update the user profiles for the users identified in the request.
The content delivery system 106 retargets the first item of invitational content previously presented based on an analysis of the collected data (206). In some embodiments, the collected data along with either the invitational content or a description of the invitational content is supplied to the invitational content retargeting module 128. The retargeting module 128 analyzes the data and reformulates the invitational content such that when presented to the user, the user is more likely to complete the associated conversion action. The reformulation can include such actions as altering the presentation of the content, e.g. changing the colors, fonts, etc.; adding to the invitational content; switching the invitational content for one that is similar; or switching the invitational content for one that is entirely different. Once retargeted, the invitational content can be used in the content package presented to the user.
In some embodiments, the content delivery system 106 retargets invitational content by re-presenting the first item of invitational content on a channel that that the user is known to have previously converted other items of invitational content. Often users are more likely to complete a conversion on invitational content presented through one channel rather than another. For example, a user may be more likely to purchase an advertised item when it is presented to them on a social networking site, but will not click the link for the item when it is presented to them on a news site. However, that same user may be willing to fill out an informational survey on the news site, but not the social networking site. An analysis of the collected data could reveal this propensity, thus, the user can be retargeted in a channel where the user is more likely to complete a conversion for the type of invitational content being offered.
In some embodiments, the content delivery system 106 retargets invitational content by re-presenting the first item of invitational content with an added incentive to complete the associated conversion action. For example, in many cases users will be presented with an advertisement to purchase a particular item only to abandon the purchase just prior to completing the transaction. In some cases this may occur because the user decided to comparison shop. An analysis of the collected data could reveal that the failed conversion resulted from comparison shopping. Based on this information the secondary content provider can retarget the user with an advertisement for the same item, but now the advertisement could include a discount or a bonus item.
In some embodiments, the content delivery system 106 retargets invitational content by re-presenting the first item of invitational content at a time when the user is more likely to complete the associated conversion action. Some items of invitational content can be timing sensitive. That is, content which when presented during a specific time of day or on a specific day of the week is more likely to fail to result in a conversion. However, if the very same item of invitational content is presented at a different time or on a different day, the rate of conversion is significantly higher. For example, if the user is presented with an invitation to watch a sporting event during their workday, they are unlikely to complete the conversion. However, if the user was presented with the same invitational content outside of their workday, e.g. in the evening, their rate of conversion increases. Furthermore, their rate of conversion may still further increase if the same invitational content is presented on their weekend. This limitation of presenting invitational content could be addressed by assuming a conventional workweek. However, more accurate retargeting can be achieved through the presently disclosed method by analyzing the collected data.
In some embodiments, the content delivery system 106 retargets invitational content by presenting a similar item of invitational content that has a lower conversion value than the first item of invitational content. For example, initially the user was presented with an offer to purchase the full version of a mobile phone application. At the time of the initial offer, the user may not have been convinced that the application would be worth the cost. In this situation, the content delivery system 106 can retarget the user by presenting a lite version of the application at either a reduced cost or for free. Additionally, whether the lite version is offered at a reduced cost or for free could be based on an analysis of the collected data.
Retargeting at a lower conversion value can also take the form of a conversion that requires less user action. For example, a possible conversion action could be getting a user to complete a form that requests a variety of contact information such as name, address, phone number, email address, etc. The user may be unwilling to complete such an extensive form either because of the amount of time required to complete the form or because they do not want to provide that much personal information. Analysis of the collected data could indicate that the user would likely complete the conversion if only required to supply a name and email address. This can have a lower conversion value for the secondary content provider, but a greater value than a completely failed conversion.
In some embodiments, the content delivery system 106 retargets invitational content by presenting a similar item of invitational content that has a higher conversion value than the first item of invitational content. For example, initially the user was presented with an offer for a lite version of a mobile phone application either for free or for a reduced price in comparison with the full version of the application. At the time of the initial offer, the user installed the lite version of the application. Analysis of the collected data could indicate first that the user downloaded and installed the lite version and second whether the user has used the lite version of the application. If so, the content delivery system 106 can retarget the user by presenting a full version of the application.
FIG. 3 is a flowchart illustrating steps in an exemplary method 300 for creating the user-specific pool of possible invitational content that can be used in a content package presented to the user. For the sake of clarity, this method is discussed in terms of an exemplary system such as is shown in FIG. 1. Although specific steps are shown in FIG. 3, in other embodiments a method can have more or less steps than shown. To create a user-specific pool, the content delivery system 106 identifies the user associated with the user terminal (302). This identification can be performed in a variety of ways. For example, as described above, when the delivery system 106 receives a request for a content package, the request can include some identifying information, associated with the requesting user terminal or the associated user. This information can then be correlated to an entry in the UUID database 115 to retrieve an identity of the user. In other configurations, the user can be identified by analyzing the requesting device's attributes in order to determine whether such requests can be attributed to a same device, also as described above. Other methods can also be used.
The content delivery system 106 obtains a pool of invitational content as candidates for distribution to the user (304). The pool can consist of the actual invitational content and/or references to invitational content. This pool of content can be obtained in a number of ways. For example, as described above, the delivery system 106 can include a content database 112 where content is locally stored/cached. Alternatively, the content management module 108 can be configured to retrieve data directly from content providers 110 and 114.
In one embodiment, the obtained pool could contain all invitational content known by the delivery system 106. Alternatively, the obtained pool could be a subset of all invitational content based on contextual characteristics such as channel, demographic, behavioral, and/or spatial-temporal characteristics. As described above, when the delivery system 106 receives a request for a content package the request can include contextual characteristics. Then these characteristics can be used by the content management module to select only content applicable to the contextual characteristics from the content database 112 or to only retrieve data from one or more of content providers 110 and 114 that are associated with the contextual characteristics. For example, if the primary content can only be packaged with invitational content from a single secondary content provider, then the initial pool would only include invitational content supplied by that secondary content provider. Alternatively, if invitational content is designed to target particular demographics of users then only content matching the demographic of the user would be included.
Meanwhile, the delivery system 106 records completed conversion actions by the user associated with at least one of the invitational content (306). As described above, the delivery system 106 includes a user-profile database 124. In some embodiments, the delivery system 106 can receive a direct request to update one or more user profiles. The update request can come directly from the user or any other device capable of communicating with the delivery system 106, such as other content delivery networks or websites. The update request can occur at any time with respect to the conversion. For example, as the conversion occurs an update request can be sent or one or more completed conversions can be stored and sent at a later time. The request can include a record of completed conversion actions for the specified users. Alternatively, the request for a content package can include a record of completed conversion actions by the requesting user. The record of completed conversion actions can be supplied to the user-profile-update module 126, which will update the user profiles for the users identified in the request.
The content delivery system 106 designates the invitational content that has a completed conversion associated therewith as exempt from distribution to the user (308). In one embodiment this can be performed by the pool-processing module 122. As described above, the pool-processing module 122 receives a context and identifying information for the user associated with the request. The pool-processing module 122 also either receives or creates a pool of invitational content. The pool-processing module accesses the user profile database 124 to retrieve the most up to date user profile of completed conversion actions for previously presented invitational content. The pool-processing module 122 examines the invitational content and if the user profile indicates a completed conversion for any particular invitational content then it excludes the content from the user-specific pool. The user-specific pool can be the same pool as the original candidate pool where the invitational content is marked as included and/or excluded. For example, the processing pool module 122 could check, for each invitational content in the pool, the user profile for a completed conversion. If the profile indicates a completed conversion, the invitational content is designated excluded. Once the pool-processing module 122 designates all invitational content for which the user has completed the conversion action as excluded, any of the non-designated invitational content can be used in the content package presented to the user. Alternatively, the user-specific pool can be an entirely separate pool that only includes invitational content for which the user has yet to complete the conversion action. Then any of the invitational content in the resulting user-specific pool can be used in the content package presented to the user.
In some embodiments, invitational content that was previously excluded from the user-specific pool can be re-included. The user-profile-update module 126 can be configured to adjust the data in user-profile database 124 so that a completed conversion expires after a specified period of time. That is, even if the user has completed the conversion action for the invitational content, after a specified period of time it is considered that the user has yet to complete the conversion. In some embodiments, rather than relying on expiring conversions, the user-profile-update module can learn directly from the user terminal 102 or a content provider that the conversion has been reversed. This can happen, for example, if a conversion required download of a program, but the user uninstalled the program.
When a completed conversion action is noted as reversed, the pool-processing module 122 can either update the user-specific pool or create a new user-specific pool. For example, if the user-specific pool is simply the original-invitational-content pool with the content marked as excluded, then the pool-processing module 122 can update the pool by removing the exclude designation. Alternatively, if the user-specific pool is a completely separate pool then the pool-processing module 122 can update the user-specific pool by adding in the invitational content that is no longer considered to have a completed conversion action.
The disclosure now turns to an illustrative example of selecting an invitational content when audience exclusion is enabled. In this illustration, the invitational content takes the form of an advertisement. FIG. 4 illustrates an exemplary configuration of devices and a network (400). Content provider 404 is an electronic commerce retailer that sells a mobile phone as well as a variety of accessories for the phone. Content provider 404 has contracted with primary content providers 406 and 408 to display advertisements for content provider 404's mobile phone and/or the associated accessories on their websites. Content provider 404 has deposited a variety of advertisements with the content delivery system 410 along with usage criteria for each advertisement. These advertisements are stored in the content database.
The user of mobile phone 402 visits the website of primary content provider 406. When this occurs, a request is sent to the content delivery system 410 for a content package. The request includes a set of criteria that specifies the known information about the user 402 and the contextual characteristics. Based on the supplied context, the delivery system obtains the pool of advertisements supplied by content provider 404 from the content database. Because there are multiple possible advertisements, the delivery system obtains the user profile for user 402 from the user profile database. The user profile indicates that user 402 has yet to complete any of the conversion actions associated with the possible advertisements. Thus, the pool processing module makes no changes to the pool of candidate advertisements. Content provider 404 supplied a usage criteria for this scenario to instruct the delivery system 410 to select a general advertisement for the content provider 404's e-commerce website.
The selected advertisement is presented to the user 402 in the form of a banner ad on primary content provider 406's website. The user 402, sees the advertisement, clicks on it, and is redirected to content provider 404's website. Once at content provider 404's website, the user 402 ultimately completes a conversion by purchasing the offered mobile phone. Upon completing the conversion action associated with the advertisement, an update request is sent to the delivery system 410 instructing it to update the user profile for the user 402, which is handled by the user profile update module.
After purchasing the mobile phone, the user 402 navigates to the website for primary content provider 408. As with content provider 406, a request for an advertisement is sent to the delivery system 410 that includes the content and the known information about the user 402. Again the system content delivery system 410 obtains the pool of possible advertisements for content provider 404 from the content database. This time when the delivery system 410 checks the user profile for the user 402, it discovers the mobile phone purchase conversion. Based on this information, the pool processing module removes the advertisements that have an associated conversion action of mobile phone purchase from the pool of possible advertisements. The delivery system 410 then selects an advertisement from the remaining pool of candidate advertisements, which in this case is a general advertisement for accessories for content provider 404's mobile phone. The selected advertisement is presented to the user 402 on content provider 408's website.
With reference to FIG. 5, an exemplary system 500 includes a general-purpose computing device 500, including a processing unit (CPU or processor) 520 and a system bus 510 that couples various system components including the system memory 530 such as read only memory (ROM) 540 and random access memory (RAM) 550 to the processor 520. The system 500 can include a cache 522 of high speed memory connected directly with, in close proximity to, or integrated as part of the processor 520. The system 500 copies data from the memory 530 and/or the storage device 560 to the cache 522 for quick access by the processor 520. In this way, the cache 522 provides a performance boost that avoids processor 520 delays while waiting for data. These and other modules can be configured to control the processor 520 to perform various actions. Other system memory 530 may be available for use as well. The memory 530 can include multiple different types of memory with different performance characteristics. It can be appreciated that the disclosure may operate on a computing device 500 with more than one processor 520 or on a group or cluster of computing devices networked together to provide greater processing capability. The processor 520 can include any general purpose processor and a hardware module or software module, such as module 1 562, module 2 564, and module 3 566 stored in storage device 560, configured to control the processor 520 as well as a special-purpose processor where software instructions are incorporated into the actual processor design. The processor 520 may essentially be a completely self-contained computing system, containing multiple cores or processors, a bus, memory controller, cache, etc. A multi-core processor may be symmetric or asymmetric.
The system bus 510 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. A basic input/output (BIOS) stored in ROM 540 or the like, may provide the basic routine that helps to transfer information between elements within the computing device 500, such as during start-up. The computing device 500 further includes storage devices 560 such as a hard disk drive, a magnetic disk drive, an optical disk drive, tape drive or the like. The storage device 560 can include software modules 562, 564, 566 for controlling the processor 520. Other hardware or software modules are contemplated. The storage device 560 is connected to the system bus 510 by a drive interface. The drives and the associated computer readable storage media provide nonvolatile storage of computer readable instructions, data structures, program modules and other data for the computing device 500. In one aspect, a hardware module that performs a particular function includes the software component stored in a non-transitory computer-readable medium in connection with the necessary hardware components, such as the processor 520, bus 510, display 570, and so forth, to carry out the function. The basic components are known to those of skill in the art and appropriate variations are contemplated depending on the type of device, such as whether the device 500 is a small, handheld computing device, a desktop computer, or a computer server.
Although the exemplary embodiment described herein employs the hard disk 560, it should be appreciated by those skilled in the art that other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, digital versatile disks, cartridges, random access memories (RAMs) 550, read only memory (ROM) 540, a cable or wireless signal containing a bit stream and the like, may also be used in the exemplary operating environment. Non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.
To enable user interaction with the computing device 500, an input device 590 represents any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech and so forth. An output device 570 can also be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems enable a user to provide multiple types of input to communicate with the computing device 500. The communications interface 580 generally governs and manages the user input and system output. There is no restriction on operating on any particular hardware arrangement and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.
For clarity of explanation, the illustrative system embodiment is presented as including individual functional blocks including functional blocks labeled as a “processor” or processor 520. The functions these blocks represent may be provided through the use of either shared or dedicated hardware, including, but not limited to, hardware capable of executing software and hardware, such as a processor 520, that is purpose-built to operate as an equivalent to software executing on a general purpose processor. For example the functions of one or more processors presented in FIG. 5 may be provided by a single shared processor or multiple processors. (Use of the term “processor” should not be construed to refer exclusively to hardware capable of executing software.) Illustrative embodiments may include microprocessor and/or digital signal processor (DSP) hardware, read-only memory (ROM) 540 for storing software performing the operations discussed below, and random access memory (RAM) 550 for storing results. Very large scale integration (VLSI) hardware embodiments, as well as custom VLSI circuitry in combination with a general purpose DSP circuit, may also be provided.
The logical operations of the various embodiments are implemented as: (1) a sequence of computer implemented steps, operations, or procedures running on a programmable circuit within a general use computer, (2) a sequence of computer implemented steps, operations, or procedures running on a specific-use programmable circuit; and/or (3) interconnected machine modules or program engines within the programmable circuits. The system 500 shown in FIG. 5 can practice all or part of the recited methods, can be a part of the recited systems, and/or can operate according to instructions in the recited non-transitory computer-readable storage media. Such logical operations can be implemented as modules configured to control the processor 520 to perform particular functions according to the programming of the module. For example, FIG. 5 illustrates three modules Mod1 562, Mod2 564 and Mod3 566 which are modules controlling the processor 520 to perform particular steps or a series of steps. These modules may be stored on the storage device 560 and loaded into RAM 550 or memory 530 at runtime or may be stored as would be known in the art in other computer-readable memory locations.
retargeting the same item of invitational content responsive to a failure by the user to convert the same item of invitational content when previously presented, wherein retargeting comprises re-presenting the same item of invitational content according to the one or more modifications.
retargeting the same item of invitational content using the different delivery channel having the higher conversion rate.
3. The method of claim 1, wherein the retargeting includes re-presenting the same item of invitational content to the device with an added incentive to convert the same item of invitational content, the incentive comprising at least one of a discount and a bonus item.
4. The method of claim 1, wherein the retargeting includes re-presenting the same item of invitational content to the device associated with the user on a channel associated with a content category for which the user is known to have previously converted other items of invitational content which is known from the analysis of the contextual-characteristics data.
5. The method of claim 1, wherein the retargeting comprises re-presenting the same item of invitational content to the device on a different website or application than a website or application previously used to present the same item of invitational content to the device, the different website or application being selected based on a determination that the different website or application has been previously accessed by the device with a greater frequency than the website or application previously used to present the same item of invitational content to the device .
6. The method of claim 1, wherein the contextual-characteristics data further includes data descriptive of a population of users' conversion habits across the network of application-delivery channels.
7. The method of claim 6, wherein the retargeting includes re-presenting the same item of invitational content on a channel for which it is known from the analysis of the contextual-characteristics data that other users are more likely to convert the same item of invitational content.
8. The method of claim 6, wherein the retargeting includes re-presenting the same item of invitational content on a channel for which it is known from the analysis of the contextual-characteristics data that the same item of invitational content is associated with a category of content and that category of content is associated with a higher conversion rate than the channel on which the same item of invitational content is being represented.
9. The method of claim 6, wherein the retargeting includes re-presenting the same item of invitational content on a channel for which it is known from the analysis of the contextual-characteristics data that the same item of invitational content, which is associated with a first category, is more likely to be converted because other items of invitational content that are associated with a second-related category have demonstrated higher conversion rates.
10. The method of claim 6, wherein the retargeting includes re-presenting the same item of invitational content during a period during which the invitational content is more likely to be converted as determined from the analysis of the contextual-characteristics data.
11. The method of claim 1, wherein the retargeting includes first presenting a different item of invitational content for which a conversion requires a lesser valued conversion, and second re-presenting the same invitational content after a conversion is recorded for the different item of invitational content.
12. The method of claim 11, wherein a conversion of the different item of invitational content requires a download of a lesser-version of an application and the same item of invitational content requires download of a full version of the application.
13. The method of claim 11, wherein the conversion of the different item of invitational content requires less user information than the same item of invitational content.
re-presenting the invitational content according to one or more modifications of a presentation of the invitational content, the one or more modifications having a higher likelihood of conversion as determined based on an analysis of the user profile, wherein the one or more modifications comprise a modified form of the invitational content on a different network channel, wherein the different network channel comprises a different website or a different digital media channel.
15. The non-transitory computer-readable medium of claim 14, wherein the one or more modifications comprise a different channel on which the user is known to have previously converted other items of invitational content.
16. The non-transitory computer-readable medium of claim 14, wherein the one or more modifications further comprise an added incentive to convert the invitational content, the added incentive comprising at least one of a discount and a bonus item.
17. The non-transitory computer-readable medium of claim 14, wherein the one or more modifications comprise a different channel that is associated with a content category for which the user is known to have previously converted other items of invitational content.
18. The non-transitory computer-readable medium of claim 14, wherein the one or more modifications comprise a different channel in which the user is known to frequently visit.
19. The non-transitory computer-readable medium of claim 14, wherein the re-presenting the invitational content according to the one or more modifications is further based on an analysis of other users' profiles.
20. The non-transitory computer-readable medium of claim 19, wherein the one or more modifications comprise a different period during which the invitational content is more likely to be converted as determined from the analysis of the other users' profiles.
retargeting a first item of invitational content previously presented to the user responsive to a failure by the user to convert the first item of invitational content, wherein the first item is retargeted according to one or more modifications comprising a modified form of the first item of invitational content delivered on a different network channel, wherein the different network channel comprises a different website or a different digital media channel.
22. The system of claim 21, wherein the retargeting includes first presenting an item of invitational content for which a conversion requires a lesser valued conversion, and second re-presenting a previously presented item of the invitational content after a conversion is recorded for the item of invitational content.
23. The system of claim 22, wherein a conversion of the item of invitational content requires a download of a lesser-version of an application and the previously presented item of invitational content requires download of a full version of the application.
24. The system of claim 22, wherein the conversion of the item of invitational content requires less user information than the previously presented item of invitational content.
25. The system of claim 21, wherein the retargeting includes re-presenting the invitational content to the user with an added incentive to convert the invitational content, the added incentive comprising at least one of a discount and a bonus item.
26. The method of claim 1, wherein the modification comprises presenting the first item in a different delivery channel from a first presentation of the first item, the different delivery channel having a higher response rate than a delivery channel associated with the first presentation.
"Baugher et al", The Secure Real-Time Transport Protocol (SRTP) , Mar. 2004, Network Working Group Request for Comments:3711, p. 1-53.
"Communication Pursuant to Article 94(3) EPC dated Feb. 10, 2009", European Patent Office in related European Patent Application No. 07 118 601.9 (3 pages), Feb. 10, 2009.
"Communication Pursuant to Article 94(3) EPC dated Oct. 19, 2009", European Patent Application No. 08 153 258.2 (5 pages), Oct. 19, 2009.
"Communication Pursuant to Article 94(3) EPC issued Jun. 25, 2009", European Patent Application No. 08 159 331.1 (3 pages), Jun. 25, 2009.
"Digital Rights Management in the Mobile Environment", Y.Raivio &S. Luukkainen, Proceedings of the International Conference on E-Business and Telecommunication, ICETE 2006, Aug. 7, 2006.
"DRM Architecture Approved Version 2.0", OMA-AD-DRM-V2-0-20060303-A (Open Mobile Alliance, Ltd.), Mar. 3, 2006.
"English translation of First Office Action issued by State Intellectual Property Office of People's Republic of China", Chinese Application No. 200480033236.X (8pages), Dec. 4, 2009.
"English Translation of First Office Action issued by the Chinese Patent Office", Chinese Application No. 200480019404.X, Aug. 19, 2008.
"European Examination Report dated Nov. 3, 2008", European Patent Application EP 08159333.7, Nov. 3, 2008.
"European Examination Report dated Nov. 3, 2008", European Patent Application No. EP 08159331.1, Nov. 3, 2008.
"European Search Report dated Apr. 18, 2008", European Patent Application No. 08101188.4, Apr. 18, 2008.
"European Search Report dated Apr. 7, 2010", European Patent Application No. EP 10153358.6 (6 pages).
"European Search Report dated Jul. 18, 2008", European Patent Office in related EPO Application No. 08 15 3658, Jul. 18, 2008.
"European Search Report dated Jul. 18, 2008", European Patent Office in related EPO Application No. EP 08 15 3656, Jul. 18, 2008.
"European Search Report dated Jul. 22, 2008", European Patent Office in related EPO Application No. EP 08153651.8, Jul. 22, 2008.
"European Search Report dated Jul. 23, 2008", European Patent Office in related EPO Application No. EP 08153654.2, Jul. 23, 2008.
"European Search Report dated Mar. 19, 2008", European Patent Office in counterpart European Application No. EP 07 11 8601, Mar. 19, 2008.
"European Search Report dated Nov. 5, 2008", European Patent Application No. EP 08159333.7, Nov. 5, 2008.
"European Search Report Jul. 22, 2008 issued by European Patent Office", EPO Application No. EP 08153651.8, Jul. 22, 2008.
"European Search Report Nov. 5, 2008", European Patent Application No. EP 08159331.1, Nov. 5, 2008.
"Extended European Search Report dated Dec. 2, 2008", European Patent Office in counterpart EPO Application No. EP 07120620.5, Dec. 2, 2008.
"Extended European Search Report dated Dec. 29, 2008", European Patent Office in counterpart EPO Application No. EP 07120480.4, Dec. 29, 2008.
"Ghassan Chaddoud, et al.", Dynamic Group Communication Security, pp. 49-56, IEEE 2001, 2001.
"International Search Report and Written Opinion of the International Search Authority", International Patent Application No. PCT/EP2008/051229, May 8, 2008.
"International Search Report and Written Opinion of the International Searching Authority", International Application PCT/EP2008/054911, Nov. 11, 2008.
"International Search Report for International Application", PCT/FI2006/050467, dated Jul. 25, 2007.
"International Search Report in PCT Application No. PCT/GB2004/003890", Apr. 5, 2005.
"Office Action (Notice of Allowance)", USPTO dated Jun. 11, 2009 in U.S. Appl. No. 12/079,312 (5 pages).
"Office Action dated Apr. 6, 2009 in related U.S. Appl. No. 12/156,335 (17 pages)", Apr. 6, 2009.
"Office Action dated Apr. 6, 2009", U.S. Appl. No. 10/555,543 (14 pages), Apr. 6, 2009.
"Office Action dated Feb. 5, 2009", U.S. Appl. No. 12/079,312 (12 pages), Feb. 5, 2009.
"Office Action dated Jan. 28, 2009 in U.S. Appl. No. 10/571,709", Jan. 28, 2009.
"Office Action dated Jun. 21, 2010", U.S. Appl. No. 10/555,543 (17 pages), Jun. 21, 2010.
"Office Action dated Mar. 22, 2010", U.S. Appl. No. 12/431,961 (19 pages), Mar. 22, 2010.
"Office Action dated Mar. 9, 2011", Issued in related U.S. Appl. No. 12/477,766 (27 pages).
"Office Action from British Intellectual Property Office", British Application No. GB0712281.5 (5 pages), Oct. 9, 2008.
"Office Action issued Apr. 22, 2010", U.S. Appl. No. 12/156,335 (16 pages), Apr. 22, 2010.
"Office Action issued by USPTO dated Nov. 20, 2009", U.S. Appl. No. 10/571,709 (20 pages), Nov. 20, 2009.
"Office Action issued from the USPTO dated Aug. 14, 2009", U.S. Appl. No. 12/431,961 (12 pages), Aug. 14, 2009.
"Office Action issued from the USPTO dated Nov. 4, 2010", U.S. Appl. No. 12/431,961 (22 pages), Nov. 4, 2010.
"Office Action issued from the USPTO dated Sep. 23, 2009", U.S. Appl. No. 12/156,335 (19 pages), Sep. 23, 2009.
"Office Action Issued from USPTO dated Oct. 5, 2009", U.S. Appl. No. 10/571,709 (26 pages), Oct. 5, 2009.
"Office Action issued from USPTO", in related U.S. Appl. No. 10/555,543 (29 pages), Oct. 20, 2009.
"Office Action Issued Jan. 12, 2011 by the USPTO", U.S. Appl. No. 12/484,454 (10 pages).
"Office Action Issued Mar. 29, 2011 by the USPTO", U.S. Appl. No. 10/555,543 (17 pages), Mar. 29, 2011.
"Office Action Mar. 24, 2009", U.S. Appl. No. 12/156,335, Mar. 24, 2009.
"Office Action", U.S. Appl. No. 12/002,452 (20 pages), Apr. 9, 2009.
"Official Action from the European Patent Office", European Application No. 08 717 428.0 (4 pages), Apr. 1, 2009.
"PCT International Preliminary Report on Patentability and Written Opinion", Issued by the International Bureau of WIPO EP2008/054911, dated Oct. 27, 2009 (1 page), Oct. 27, 2009.
"PCT International Search Report (Form PCT/ISA/210)", International Application PCT/EP2008/052678, Jul. 4, 2008.
"PCT International Search Report issued by PCT International Searching Authority", International Searching Authority in connection with the related PCT International Application No. PCT/NL2004/000335 (2 pages), Sep. 24, 2004.
"Schulzrinne et al, "RTP: A Transport Protocol for Real-Time Applications"", Network Working Group Request for Comments: 3550, p. 1-98, Jul. 1, 2003.
"Search Report under Section 17 dated May 20, 2008", British Patent Office in counterpart UK Application No. GB0807153.2, May 20, 2008.
"Text of Second Office Action (English Translation)", Jun. 12, 2009 in corresponding Chinese Patent Application No. 200480019404.X (2 pages).
"U.K. Combined Search and Examination Report under Sections 17 and 18(3)", U.K. Application No. GB0802177.6, May 13, 2008.
"U.K. Further Search Report under Section 17", U.K. Application No. GB0710853.3, Dec. 5, 2007.
"U.K. Patent Office Examination Report under Section 18(3)", U.K Application No. GB0315984.5, Mar. 29, 2006.
"U.K. Search Report under Section 17 dated Mar. 3, 2005", U.K Application Serial No. GB0420339.4, Mar. 3, 2005.
"U.K. Search Report under Section 17", U.K. Application No. GB0710853.3, Oct. 3, 2007.
"United Kingdom Search Report under Section 17", GB 0712281.5 (2 pages), Oct. 24, 2007.
"Wallner et al., "Key Management for Multicast: Issues and Architectures"", National Security Agency Network Working Group Request for Comments: 2627, p. 1-22, Jun. 1, 1999.
Levine, Robert , "New Model For Sharing: Free Music with Ads", The New York Times (On-Line Edition), Apr. 23, 2007.

matches:
Application No. 07
Application No. 08
Application No. 08
Application No. 200480033236
Application No. 200480019404
Application No. 08101188
Application No. 08
Application No. 08
Application No. 200480019404


text:
Publié le 25 Mars 2018 à 10h16 - 1572 v.
Often, when we grow up, we notice a lot of gaps in our life. This is because adults have not been able to introduce us to the difficulties and realities of life from an early age. Only by growing up can you notice that some things can be difficult to live with and others can be so easy to acquire. Therefore, do not make the same mistakes and prepare your child for future challenges. The more prepared he is, the more he will have a bright future.
You can not directly imbue your child with the different realities of life. It must be done step by step. That's why workplace dynamics exist to help your child be more independent, more responsible and adaptable to any situation. That's why the many fun activities are there: to help your child take the step, to support him and guide him towards the easiest solution, push him to be more autonomous and dynamic. Through games, entertainment, lessons or others, your child will be able to overcome any ordeal in the future, he will easily acquire the maturity once he is big, he will understand the difficulties you are enduring . A prepared child will be tomorrow's future.
To imbue them seems complex and yet it is not impossible. It's not forcing him to understand that you're going to get there. For this, discussions, illustrations, examples and other practices exist to easily initiate them to future challenges. At first, it will be difficult for them to assimilate, but as you know how to dissuade them, you will notice that it will be child's play. Register your child for workshops that will allow her to escape and learn a little more. This will reinforce his motivation to know new horizons, boost his energy, give him the audacity to overcome each obstacle. It may seem risky enough for you but many parents have opted for this quick and effective solution. And today, their children have become responsible little adults and able to face the world in case of a glitch. And yours ? What will it be in the future?
Les publications similaires de "All you need for your child"
1 Avril 2019Get your childrens to know the sea17 v.
7 Mars 2019Make your own style!85 v.
21 Fév. 2019How to rent a boat while on holiday with a child71 v.
28 Oct. 2018Why passing on your passions from a young age is good !301 v.
28 Juil. 2018A look into health and welfare policies533 v.
8 Janv. 2018The best nutrition for your pets872 v.
How to be a good mom ?
Why passing on your passions from a young age is good !

matches: v. v. v. v. v. v. v.


1. The judgment being erroneous on the merits, the Court abstains from inquiring whether this suit to enjoin a subordinate federal officer from alleged invasion of plaintiff's rights under color of a federal statute but without authority, is a suit against the United States, or whether the Secretary of the Interior should have been joined as a necessary party defendant, or whether the state court was without power to enjoin a federal officer. P. 313 U. S. 359.
2. In administering the Taylor Grazing Act of June 28, 1934, the Secretary of the Interior, relying on the broad powers conferred by § 2, issued temporary licenses to stockowners for the grazing of their livestock upon the public lands within grazing districts, and charged a uniform price per head, rather than have the grazing lands go unregulated pending the lengthy period required for instituting the plan, contemplated by § 3, of renewable term permits at reasonable fees adjusted to each case, etc. With full knowledge of this, Congress repeatedly appropriated part of the money thus brought into the Treasury for expenditure by the Secretary in improvement of the ranges.
Congress in the administration of the Act was thereby ratified. P. 313 U. S. 360.
60 Nev. 219; 106 P.2d 755, reversed.
Certiorari, 312 U.S. 674, to review the affirmance of a decree of injunction, entered upon the overruling of a demurrer to the bill.
shortly thereafter, the defendant, Brooks, who was acting as Regional Grazier of the United States, notified the respondents that, unless they paid the installments and obtained licenses by June 15th, they would be considered in trespass under the terms of the Act of 1934, and would be punished by fine as provided in the Act. The respondents alleged with particularity the urgent necessity in the conduct of their business that they be permitted in graze their cattle to public lands and that, unless they can do so, they will suffer irreparable and serious damage due to the destruction of their businesses. The bill charges that, although the Secretary, in promulgating the rules with respect to temporary licenses, purported to act under the authority of § 2 of the Act of 1934, that section confers upon him no power so to do, and that grazing fees specified by the rules were fixed without any attempt to determine their amounts as required by § 3 of the Act, and in violation of conditions prescribed by § 3.
The petitioner demurred, and assigned as reasons that the complaint failed to state facts sufficient to constitute a cause of action against him; that there was a defect of parties defendant for failure to join the Secretary of the Interior; that, as the United States, an indispensable party, had not consented to be sued, the court was without jurisdiction, and that the subject matter of the complaint was exclusively within the political power of the United States, and not subject to judicial review. The court overruled the demurrer, with leave to answer. The petitioner elected to stand upon his demurrer, and the court thereupon entered a decree in favor of the respondents, which the Supreme Court of Nevada affirmed. [Footnote 3] We granted certiorari, 312 U.S. 674, because of the importance of the questions involved.
"The Secretary of the Interior shall make provision for the protection, administration, regulation, and improvement of such grazing districts as may be created under the authority of the foregoing section, and he shall make such rules and regulations and establish such service, enter into such cooperative agreements, and do any and all things necessary to accomplish the purposes of this Act and to insure the objects of such grazing districts, namely, to regulate their occupancy and use, to preserve the land and its resources from destruction or unnecessary injury, to provide for the orderly use, improvement, and development of the range; . . . and any willful violation of the provisions of this Act or of such rules and regulations thereunder after actual notice thereof shall be punishable by a fine of not more than $500."
than ten years subject to the preferential right of the permittee to renewal in the discretion of the Secretary. There are other provisions for adjustment of the amount of grazing to be permitted under the permits and a corresponding adjustment of the grazing fees in the case of the occurrence of range depletion due to natural causes.
authorities. Since the jurisdiction and the procedure of the court below is sustained by decisions of this Court, we are unwilling to base our judgment upon a resolution of asserted conflict touching issues of so grave consequence where, as here, the bill fails to make a case upon the merits.
The respondents say that, under the Act of 1934, the Secretary is powerless to grant temporary licenses and charge fees therefor; that his sole authority is to issue permanent permits for specified periods not to exceed ten years at fees adjusted to the circumstances of individual permittees, and with preferential rights of renewal. If this view be correct, it might well be years before the Secretary could place the users of lands in any district under permits. The petitioner asserts that it was not the intent of Congress that the grazing lands should go unregulated and without license for any such extensive period as would be required for the issue of permits under § 3. He relies on the broad powers conferred by § 2, and points out that the section is a replica of the statute involved in United States v. Grimaud, 220 U. S. 506, and there held to authorize similar rules and regulations.
See Buford v. Houtz, 133 U. S. 320; Omaechevarria v. Idaho, 246 U. S. 343.
C. 865, 48 Stat. 1269, as amended by Act of June 26, 1936, c. 842, 46 Stat. 1976, 43 U.S.C.Supp. V, § 315 et seq.
By § 11, provision is made for disposition of moneys received from districts located on Indian lands. Twenty-five percent. is made available, when appropriated for expenditure by the Secretary for range improvement.
Cunningham v. Macon & Brunswick R. Co., 109 U. S. 446, 109 U. S. 451.
"For construction, purchase, and maintenance of range improvements within grazing districts, pursuant to the provisions of sections 10 and 11 of the Act of June 28, 1934 (48 Stat., p. 1269), and not including contributions under section 9 of said Act, $250,000: Provided, That expenditures hereunder in any grazing district shall not exceed 25 percentum of all moneys received under the provisions of said Act from such district during the fiscal years 1936 and 1937."
Annual Report Secretary of the Interior 1936, pp. 16-17. Id., 1937, pp. xii, 102, 105-107. Id., 1938, pp. xv, 107.
Hearings Subcommittee of House Committee on Appropriations on H.R. 10,630, 74th Cong., 2d Sess., pp. 13-15; Hearings Subcommittee of House Committee on Appropriations on H.R. 6958, 75th Cong., 1st Sess., pp. 80, 83, 89; Hearings Subcommittee of House Committee on Appropriations on H.R. 9621, 75th Cong., 3d Sess., pp. 65, 70, 71; Hearing Subcommittee of Senate Committee on Appropriations on H.R. 9621, 75th Cong., 3d Sess., pp. 3, 28, 29.
81 Cong.Rec. part 4, pp. 4570, 4571; 83 Cong.Rec. part 11, p. 2376; 84 Cong.Rec. part 13, pp. 2931, 2932, 2933.
Wells v. Nickles, 104 U. S. 444, 104 U. S. 447.
Isbrandtsen-Moller Co. v. United States, 300 U. S. 139, 300 U. S. 147.