Note: Descriptions are shown in the official language in which they were submitted.
WO 2019/046083
PCT/US2018/047644
WRAPPING CONTINUATION TOKENS TO SUPPORT PAGING FOR MULTIPLE
SERVERS ACROSS DIFFERENT GEOLOCATIONS
CROSS-REFERENCE
[0001] This application claims priority to U.S. non-provisional patent
application Ser.
No. 15/688,252, filed on August 28, 2017, entitled WRAPPING CONTINUATION
TOKENS TO SUPPORT PAGING FOR MULTIPLE SERVERS ACROSS
DIFFERENT GEOLOCATIONS .
TECHNICAL FIELD
[0002] Aspects of the disclosure relate to computer hardware and software. In
particular, one or more aspects of the disclosure generally relate to computer
hardware and software for big data storage and retrieval across multiple
geolocations.
BACKGROUND
[0003] A virtual environment may provide storage for globally distributed,
multi-
model big data segmented in multiple geolocations of a cloud-based
environment.
In particular, such data-centric systems may have a need for storage and
retrieval of
unstructured and structured data in schema-less databases, such as key-value
stores
and document stores. As enterprises in the cloud expand their services, the
volume,
variety and velocity at which data arrives increase drastically across
multiple
geolocations. As a result, conventional systems might not be able to meet
these
challenges with efficiency, performance, seamlessness and scalability.
SUMMARY
[0004] The following presents a simplified summary of various aspects
described
herein. This summary is not an extensive overview, and is not intended to
identify
key or critical elements or to delineate the scope of the claims. The
following
summary merely presents some concepts in a simplified form as an introductory
prelude to the more detailed description provided below.
- -
Date Recue/Date Received 2021-07-28
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
[0005] To overcome limitations in the prior art described above, and to
overcome other
limitations that will be apparent upon reading and understanding the present
specification, aspects described herein are directed towards wrapping
continuation
tokens to support paging for multiple servers across different geolocations.
[0006] In accordance with one or more aspects of the disclosure, an enterprise
server
having at least one processor, memory, and a communication interface may
receive,
from a client device, a first request for a plurality of records, and the
first request
may request a quantity of records exceeding a page size limit. In response to
receiving the first request, the enterprise server may retrieve a first set of
records
comprising a first number of records equal to the page size limit.
Subsequently, the
enterprise server may generate a first wrapped continuation token, which may
comprise location information identifying a geographic location of a first
server
where a next set of records is to be retrieved. Thereafter, the enterprise
server may
send, to the client device, the first set of records and the first wrapped
continuation
token, and sending the first wrapped continuation token to the client device
may
cause the client device to process the first set of records.
[0007] In some instances, after the enterprise server sends the first set of
records and
the first wrapped continuation token to the client device, the enterprise
server may
receive, from the client device, the first wrapped continuation token. For
example,
the enterprise server may identify a second set of records associated with the
plurality of the records to retrieve based on the first wrapped continuation
token,
and the second set of records may comprise a second number of records less
than
the page size limit. In another example, in response to identifying the second
set
of records, the enterprise server may retrieve the second set of records.
[0008] In some instances, after retrieving the second set of records, the
enterprise server
may send a second request to a first new geo data server to retrieve a third
set of
records comprising a third number of records, and a sum of the second number
of
records and the third number of records may equal the page size limit. In some
instances, the enterprise server may receive the third set of records and a
second
wrapped continuation token from the first new geo data server. In some
instances,
the second wrapped continuation token may comprise location information
identifying a geographic location of the first new geo data server where a
next set
of records in the plurality of the records is to be retrieved. As a result,
the enterprise
- 2 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
server may send the second set of records, the third set of records, and the
second
wrapped continuation token to the client device, where sending the second
wrapped
continuation token to the client device may cause the client device to process
the
second set of records and the third set of records.
[0009] In some instances, after sending the second and the third set of
records, and the
second wrapped continuation token, the enterprise server may receive, from the
client device, the second wrapped continuation token. Subsequently, the
enterprise
server may send the second wrapped continuation token to the first new geo
data
server based on the geographic location associated with the second wrapped
continuation token.
[0010] In some instances, in response to sending the second wrapped
continuation
token to the first new geo data server, the enterprise server may receive,
from the
first new geo data server, a fourth set of records, where the fourth set of
records
may comprise a fourth number of records less than the page size limit. In some
instances, the enterprise server may send a third request to a second new geo
data
server to retrieve additional records in the plurality of records. As such,
the
enterprise server may receive, from the second new geo data server, a fifth
set of
records comprising a fifth number of records, where a sum of the fourth number
of
records and the fifth number of records may be less than the page size limit.
[0011] In some instances, the enterprise server may identify that there is no
additional
record in the plurality of records to be retrieved and send, to the client
device, the
fourth and fifth set of records, which may cause the client device to process
the
fourth set of records and the fifth set of records. In some instances, the
enterprise
server may be configured to host a data store which may comprise data for a
specific
geographic area.
[0012] These and additional aspects will be appreciated with the benefit of
the
disclosures discussed in further detail below.
BRIEF DESCRIPTION OF THE DRAWINGS
[0013] A more complete understanding of aspects described herein and the
advantages
thereof may be acquired by referring to the following description in
consideration
of the accompanying drawings, in which like reference numbers indicate like
features, and wherein:
- 3 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
[0014] Figure 1 depicts an illustrative computer system architecture that may
be used
in accordance with one or more illustrative aspects described herein.
[0015] Figure 2 depicts an illustrative remote-access system architecture that
may be
used in accordance with one or more illustrative aspects described herein.
[0016] Figure 3 depicts an illustrative virtualized (hypervisor) system
architecture that
may be used in accordance with one or more illustrative aspects described
herein.
[0017] Figure 4 depicts an illustrative cloud-based system architecture that
may be used
in accordance with one or more illustrative aspects described herein.
[0018] Figure 5 depicts an illustrative enterprise mobility management system.
[0019] Figure 6 depicts another illustrative enterprise mobility management
system.
[0020] Figure 7 depicts an illustrative computing environment for wrapping
continuation tokens to support paging for multiple servers across different
geolocations in accordance with one or more illustrative aspects described
herein.
[0021] Figures 8A-8D depict an example event sequence for wrapping
continuation
tokens to support paging for multiple servers across different geolocations in
accordance with one or more illustrative aspects described herein.
[0022] Figure 9 depicts an example method of wrapping continuation tokens to
support
paging for multiple servers across different geolocations in accordance with
one or
more illustrative aspects described herein.
DETAILED DESCRIPTION
[0023] In the following description of the various embodiments, reference is
made to
the accompanying drawings identified above and which form a part hereof, and
in
which is shown by way of illustration various embodiments in which aspects
described herein may be practiced. It is to be understood that other
embodiments
may be utilized and structural and functional modifications may be made
without
departing from the scope described herein. Various aspects are capable of
other
embodiments and of being practiced or being carried out in various different
ways.
[0024] It is to be understood that the phraseology and terminology used herein
are for
the purpose of description and should not be regarded as limiting. Rather, the
phrases and terms used herein are to be given their broadest interpretation
and
- 4 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
meaning. The use of "including" and "comprising" and variations thereof is
meant
to encompass the items listed thereafter and equivalents thereof as well as
additional
items and equivalents thereof The use of the terms -mounted," -connected,"
"coupled," "positioned," "engaged" and similar terms, is meant to include both
direct and indirect mounting, connecting, coupling, positioning and engaging.
[0025] COMPUTING ARCHITECTURE
[0026] Computer software, hardware, and networks may be utilized in a variety
of
different system environments, including standalone, networked, remote-access
(aka, remote desktop), virtualized, and/or cloud-based environments, among
others.
FIG. 1 illustrates one example of a system architecture and data processing
device
that may be used to implement one or more illustrative aspects described
herein in
a standalone and/or networked environment. Various network nodes 103, 105,
107,
and 109 may be interconnected via a wide area network (WAN) 101, such as the
Internet. Other networks may also or alternatively be used, including private
intranets, corporate networks, local area networks (LAN), metropolitan area
networks (MAN), wireless networks, personal networks (PAN), and the like.
Network 101 is for illustration purposes and may be replaced with fewer or
additional computer networks. A local area network 133 may have one or more of
any known LAN topology and may use one or more of a variety of different
protocols, such as Ethernet. Devices 103, 105, 107, and 109 and other devices
(not
shown) may be connected to one or more of the networks via twisted pair wires,
coaxial cable, fiber optics, radio waves, or other communication media.
[0027] The term "network" as used herein and depicted in the drawings refers
not only
to systems in which remote storage devices are coupled together via one or
more
communication paths, but also to stand-alone devices that may be coupled, from
time to time, to such systems that have storage capability. Consequently, the
term
"network- includes not only a "physical network" but also a "content network,"
which is comprised of the data¨attributable to a single entity¨which resides
across all physical networks.
[0028] The components may include data server 103, web server 105, and client
computers 107, 109. Data server 103 provides overall access, control and
administration of databases and control software for performing one or more
- 5 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
illustrative aspects describe herein. Data server 103 may be connected to web
server
105 through which users interact with and obtain data as requested.
Alternatively,
data server 103 may act as a web server itself and be directly connected to
the
Internet. Data server 103 may be connected to web server 105 through the local
area
network 133, the wide area network 101 (e.g., the Intemet), via direct or
indirect
connection, or via some other network. Users may interact with the data server
103
using remote computers 107, 109, e.g., using a web browser to connect to the
data
server 103 via one or more externally exposed web sites hosted by web server
105.
Client computers 107, 109 may be used in concert with data server 103 to
access
data stored therein, or may be used for other purposes. For example, from
client
device 107 a user may access web server 105 using an Internet browser, as is
known
in the art, or by executing a software application that communicates with web
server
105 and/or data server 103 over a computer network (such as the Internet).
[0029] Servers and applications may be combined on the same physical machines,
and
retain separate virtual or logical addresses, or may reside on separate
physical
machines. FIG. 1 illustrates just one example of a network architecture that
may be
used, and those of skill in the art will appreciate that the specific network
architecture and data processing devices used may vary, and are secondary to
the
functionality that they provide, as further described herein. For example,
services
provided by web server 105 and data server 103 may be combined on a single
server.
[0030] Each component 103, 105, 107, 109 may be any type of known computer,
server, or data processing device. Data server 103, e.g., may include a
processor
111 controlling overall operation of the data server 103. Data server 103 may
further
include random access memory (RAM) 113, read only memory (ROM) 115,
network interface 117, input/output interfaces 119 (e.g., keyboard, mouse,
display,
printer, etc.), and memory 121. Input/output (I/O) 119 may include a variety
of
interface units and drives for reading, writing, displaying, and/or printing
data or
files. Memory 121 may further store operating system software 123 for
controlling
overall operation of the data processing device 103, control logic 125 for
instructing
data server 103 to perform aspects described herein, and other application
software
127 providing secondary, support, and/or other functionality which may or
might
not be used in conjunction with aspects described herein. The control logic
may also
- 6 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
be referred to herein as the data server software 125. Functionality of the
data server
software may refer to operations or decisions made automatically based on
rules
coded into the control logic, made manually by a user providing input into the
system, and/or a combination of automatic processing based on user input
(e.g.,
queries, data updates, etc.).
[0031] Memory 121 may also store data used in performance of one or more
aspects
described herein, including a first database 129 and a second database 131. In
some
embodiments, the first database may include the second database (e.g., as a
separate
table, report, etc.). That is, the information can be stored in a single
database, or
separated into different logical, virtual, or physical databases, depending on
system
design. Devices 105, 107, and 109 may have similar or different architecture
as
described with respect to device 103. Those of skill in the art will
appreciate that
the functionality of data processing device 103 (or device 105, 107, or 109)
as
described herein may be spread across multiple data processing devices, for
example, to distribute processing load across multiple computers, to segregate
transactions based on geographic location, user access level, quality of
service
(QoS), etc.
[0032] One or more aspects may be embodied in computer-usable or readable data
and/or computer-executable instructions, such as in one or more program
modules,
executed by one or more computers or other devices as described herein.
Generally,
program modules include routines, programs, objects, components, data
structures,
etc. that perform particular tasks or implement particular abstract data types
when
executed by a processor in a computer or other device. The modules may be
written
in a source code programming language that is subsequently compiled for
execution, or may be written in a scripting language such as (but not limited
to)
HyperText Markup Language (HTML) or Extensible Markup Language (XML).
The computer executable instructions may be stored on a computer readable
medium such as a nonvolatile storage device. Any suitable computer readable
storage media may be utilized, including hard disks, CD-ROMs, optical storage
devices, magnetic storage devices, and/or any combination thereof In addition,
various transmission (non-storage) media representing data or events as
described
herein may be transferred between a source and a destination in the form of
electromagnetic waves traveling through signal-conducting media such as metal
- 7 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
wires, optical fibers, and/or wireless transmission media (e.g., air and/or
space).
Various aspects described herein may be embodied as a method, a data
processing
system, or a computer program product. Therefore, various functionalities may
be
embodied in whole or in part in software, firmware, and/or hardware or
hardware
equivalents such as integrated circuits, field programmable gate arrays
(FPGA), and
the like. Particular data structures may be used to more effectively implement
one
or more aspects described herein, and such data structures are contemplated
within
the scope of computer executable instructions and computer-usable data
described
herein.
[0033] With further reference to FIG. 2, one or more aspects described herein
may be
implemented in a remote-access environment. FIG. 2 depicts an example system
architecture including a computing device 201 in an illustrative computing
environment 200 that may be used according to one or more illustrative aspects
described herein. Computing device 201 may be used as a server 206a in a
single-
server or multi-server desktop virtualization system (e.g., a remote access or
cloud
system) configured to provide virtual machines for client access devices. The
computing device 201 may have a processor 203 for controlling overall
operation
of the server and its associated components, including RAM 205, ROM 207,
Input/Output (I/O) module 209, and memory 215.
[0034] I/O module 209 may include a mouse, keypad, touch screen, scanner,
optical
reader, and/or stylus (or other input device(s)) through which a user of
computing
device 201 may provide input, and may also include one or more of a speaker
for
providing audio output and one or more of a video display device for providing
textual, audiovisual, and/or graphical output. Software may be stored within
memory 215 and/or other storage to provide instructions to processor 203 for
configuring computing device 201 into a special purpose computing device in
order
to perform various functions as described herein. For example, memory 215 may
store software used by the computing device 201, such as an operating system
217,
application programs 219, and an associated database 221.
[0035] Computing device 201 may operate in a networked environment supporting
connections to one or more remote computers, such as terminals 240 (also
referred
to as client devices). The terminals 240 may be personal computers, mobile
devices,
laptop computers, tablets, or servers that include many or all of the elements
- 8 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
described above with respect to the computing device 103 or 201. The network
connections depicted in FIG. 2 include a local area network (LAN) 225 and a
wide
area network (WAN) 229, but may also include other networks. When used in a
LAN networking environment, computing device 201 may be connected to the
LAN 225 through a network interface or adapter 223. When used in a WAN
networking environment, computing device 201 may include a modem 227 or other
wide area network interface for establishing communications over the WAN 229,
such as computer network 230 (e.g., the Internet). It will be appreciated that
the
network connections shown are illustrative and other means of establishing a
communications link between the computers may be used. Computing device 201
and/or terminals 240 may also be mobile terminals (e.g., mobile phones,
smartphones, personal digital assistants (PDAs), notebooks, etc.) including
various
other components, such as a battery, speaker, and antennas (not shown).
[0036] Aspects described herein may also be operational with numerous other
general
purpose or special purpose computing system environments or configurations.
Examples of other computing systems, environments, and/or configurations that
may be suitable for use with aspects described herein include, but are not
limited
to, personal computers, server computers, hand-held or laptop devices,
multiprocessor systems, microprocessor-based systems, set top boxes,
programmable consumer electronics, network personal computers (PCs),
minicomputers, mainframe computers, distributed computing environments that
include any of the above systems or devices, and the like.
[0037] As shown in FIG. 2, one or more client devices 240 may be in
communication
with one or more servers 206a-206n (generally referred to herein as "server(s)
206-). In one embodiment, the computing environment 200 may include a network
appliance installed between the server(s) 206 and client machine(s) 240. The
network appliance may manage client/server connections, and in some cases can
load balance client connections amongst a plurality of backend servers 206.
[0038] The client machine(s) 240 may in some embodiments be referred to as a
single
client machine 240 or a single group of client machines 240, while server(s)
206
may be referred to as a single server 206 or a single group of servers 206. In
one
embodiment a single client machine 240 communicates with more than one server
206, while in another embodiment a single server 206 communicates with more
- 9 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
than one client machine 240. In yet another embodiment, a single client
machine
240 communicates with a single server 206.
[0039] A client machine 240 can, in some embodiments, be referenced by any one
of
the following non-exhaustive terms: client machine(s); client(s); client
computer(s);
client device(s); client computing device(s); local machine; remote machine;
client
node(s); endpoint(s); or endpoint node(s). The server 206, in some
embodiments,
may be referenced by any one of the following non-exhaustive terms: server(s),
local machine; remote machine; server farm(s), or host computing device(s).
[0040] In one embodiment, the client machine 240 may be a virtual machine. The
virtual machine may be any virtual machine, while in some embodiments the
virtual
machine may be any virtual machine managed by a Type 1 or Type 2 hypervisor,
for example, a hypervisor developed by Citrix Systems, IBM, VMware, or any
other
hypervisor. In some aspects, the virtual machine may be managed by a
hypervisor,
while in other aspects the virtual machine may be managed by a hypervisor
executing on a server 206 or a hypervisor executing on a client 240.
[0041] Some embodiments include a client device 240 that displays application
output
generated by an application remotely executing on a server 206 or other
remotely
located machine. In these embodiments, the client device 240 may execute a
virtual
machine receiver program or application to display the output in an
application
window, a browser, or other output window. In one example, the application is
a
desktop, while in other examples the application is an application that
generates or
presents a desktop. A desktop may include a graphical shell providing a user
interface for an instance of an operating system in which local and/or remote
applications can be integrated. Applications, as used herein, are programs
that
execute after an instance of an operating system (and, optionally, also the
desktop)
has been loaded.
[0042] The server 206, in some embodiments, uses a remote presentation
protocol or
other program to send data to a thin-client or remote-display application
executing
on the client to present display output generated by an application executing
on the
server 206. The thin-client or remote-display protocol can be any one of the
following non-exhaustive list of protocols: the Independent Computing
Architecture (ICA) protocol developed by Citrix Systems, Inc. of Ft.
Lauderdale,
- 10 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
Florida; or the Remote Desktop Protocol (RDP) manufactured by the Microsoft
Corporation of Redmond, Washington.
[0043] A remote computing environment may include more than one server 206a-
206n
such that the servers 206a-206n are logically grouped together into a server
farm
206, for example, in a cloud computing environment. The server farm 206 may
include servers 206 that are geographically dispersed while and logically
grouped
together, or servers 206 that are located proximate to each other while
logically
grouped together. Geographically dispersed servers 206a-206n within a server
farm
206 can, in some embodiments, communicate using a WAN (wide), MAN
(metropolitan), or LAN (local), where different geographic regions can be
characterized as: different continents; different regions of a continent;
different
countries; different states; different cities; different campuses: different
rooms; or
any combination of the preceding geographical locations. In some embodiments
the
server farm 206 may be administered as a single entity, while in other
embodiments
the server farm 206 can include multiple server farms.
[0044] In some embodiments, a server farm may include servers 206 that execute
a
substantially similar type of operating system platform (e.g., WINDOWS, UNIX,
LINUX, i OS, ANDROID, SYMBIAN, etc.) In other embodiments, server farm 206
may include a first group of one or more servers that execute a first type of
operating
system platform, and a second group of one or more servers that execute a
second
type of operating system platform.
[0045] Server 206 may be configured as any type of server, as needed, e.g., a
file server,
an application server, a web server, a proxy server, an appliance, a network
appliance, a gateway, an application gateway, a gateway server, a
virtualization
server, a deployment server, a Secure Sockets Layer (SSL) VPN server, a
firewall,
a web server, an application server or as a master application server, a
server
executing an active directory, or a server executing an application
acceleration
program that provides firewall functionality, application functionality, or
load
balancing functionality. Other server types may also be used.
[0046] Some embodiments include a first server 206a that receives requests
from a
client machine 240, forwards the request to a second server 206b (not shown),
and
responds to the request generated by the client machine 240 with a response
from
- 11 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
the second server 206b (not shown.) First server 206a may acquire an
enumeration
of applications available to the client machine 240 and well as address
information
associated with an application server 206 hosting an application identified
within
the enumeration of applications. First server 206a can then present a response
to the
client's request using a web interface, and communicate directly with the
client 240
to provide the client 240 with access to an identified application. One or
more
clients 240 and/or one or more servers 206 may transmit data over network 230,
e.g., network 101.
[0047] FIG. 3 shows a high-level architecture of an illustrative desktop
virtualization
system. As shown, the desktop virtualization system may be single-server or
multi-
server system, or cloud system, including at least one virtualization server
301
configured to provide virtual desktops and/or virtual applications to one or
more
client access devices 240. As used herein, a desktop refers to a graphical
environment or space in which one or more applications may be hosted and/or
executed. A desktop may include a graphical shell providing a user interface
for an
instance of an operating system in which local and/or remote applications can
be
integrated. Applications may include programs that execute after an instance
of an
operating system (and, optionally, also the desktop) has been loaded. Each
instance
of the operating system may be physical (e.g., one operating system per
device) or
virtual (e.g., many instances of an OS running on a single device). Each
application
may be executed on a local device, or executed on a remotely located device
(e.g.,
remoted).
[0048] A computer device 301 may be configured as a virtualization server in a
virtualization environment, for example, a single-server, multi-server, or
cloud
computing environment. Virtualization server 301 illustrated in FIG. 3 can be
deployed as and/or implemented by one or more embodiments of the server 206
illustrated in FIG. 2 or by other known computing devices. Included in
virtualization server 301 is a hardware layer that can include one or more
physical
disks 304, one or more physical devices 306, one or more physical processors
308,
and one or more physical memories 316. In some embodiments, firmware 312 can
be stored within a memory element in the physical memory 316 and can be
executed
by one or more of the physical processors 308. Virtualization server 301 may
further
include an operating system 314 that may be stored in a memory element in the
- 12 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
physical memory 316 and executed by one or more of the physical processors
308.
Still further, a hypervisor 302 may be stored in a memory element in the
physical
memory 316 and can be executed by one or more of the physical processors 308.
[0049] Executing on one or more of the physical processors 308 may be one or
more
virtual machines 332A-C (generally 332). Each virtual machine 332 may have a
virtual disk 326A-C and a virtual processor 328A-C. In some embodiments, a
first
virtual machine 332A may execute, using a virtual processor 328A, a control
program 320 that includes a tools stack 324. Control program 320 may be
referred
to as a control virtual machine, Dom0, Domain 0, or other virtual machine used
for
system administration and/or control. In some embodiments, one or more virtual
machines 332B-C can execute, using a virtual processor 328B-C, a guest
operating
system 330A-B.
[0050] Virtualization server 301 may include a hardware layer 310 with one or
more
pieces of hardware that communicate with the virtualization server 301. In
some
embodiments, the hardware layer 310 can include one or more physical disks
304,
one or more physical devices 306, one or more physical processors 308, and one
or
more physical memory 316. Physical components 304, 306, 308, and 316 may
include, for example, any of the components described above. Physical devices
306
may include, for example, a network interface card, a video card, a keyboard,
a
mouse, an input device, a monitor, a display device, speakers, an optical
drive, a
storage device, a universal serial bus connection, a printer, a scanner, a
network
element (e.g., router, firewall, network address translator, load balancer,
virtual
private network (VPN) gateway, Dynamic Host Configuration Protocol (DHCP)
router, etc.), or any device connected to or communicating with virtualization
server
301. Physical memory 316 in the hardware layer 310 may include any type of
memory. Physical memory 316 may store data, and in some embodiments may store
one or more programs, or set of executable instructions. FIG. 3 illustrates an
embodiment where firmware 312 is stored within the physical memory 316 of
virtualization server 301. Programs or executable instructions stored in the
physical
memory 316 can be executed by the one or more processors 308 of virtualization
server 301.
[0051] Virtualization server 301 may also include a hypervisor 302. In some
embodiments, hypervisor 302 may be a program executed by processors 308 on
- 13 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
virtualization server 301 to create and manage any number of virtual machines
332.
Hypervisor 302 may be referred to as a virtual machine monitor, or platform
virtualization software. In some embodiments, hypervisor 302 can be any
combination of executable instructions and hardware that monitors virtual
machines
executing on a computing machine. Hypervisor 302 may be Type 2 hypervisor,
where the hypervisor executes within an operating system 314 executing on the
virtualization server 301. Virtual machines may then execute at a level above
the
hypervisor. In some embodiments, the Type 2 hypervisor may execute within the
context of a user's operating system such that the Type 2 hypervisor interacts
with
the user's operating system. In other embodiments, one or more virtualization
servers 301 in a virtualization environment may instead include a Type 1
hypervisor
(not shown). A Type 1 hypervisor may execute on the virtualization server 301
by
directly accessing the hardware and resources within the hardware layer 310.
That
is, while a Type 2 hypervisor 302 accesses system resources through a host
operating system 314, as shown, a Type 1 hypervisor may directly access all
system
resources without the host operating system 314. A Type 1 hypervisor may
execute
directly on one or more physical processors 308 of virtualization server 301,
and
may include program data stored in the physical memory 316.
[0052] Hypervisor 302, in some embodiments, can provide virtual resources to
operating systems 330 or control programs 320 executing on virtual machines
332
in any manner that simulates the operating systems 330 or control programs 320
having direct access to system resources. System resources can include, but
are not
limited to, physical devices 306, physical disks 304, physical processors 308,
physical memory 316, and any other component included in virtualization server
301 hardware layer 310. Hypervisor 302 may be used to emulate virtual
hardware,
partition physical hardware, virtualize physical hardware, and/or execute
virtual
machines that provide access to computing environments. In still other
embodiments, hypervisor 302 may control processor scheduling and memory
partitioning for a virtual machine 332 executing on virtualization server 301.
Hypervisor 302 may include those manufactured by VMWare, Inc., of Palo Alto,
California; the XENPROJECT hypervisor, an open source product whose
development is overseen by the open source XenProject.org community; HyperV,
VirtualServer or virtual PC hypervisors provided by Microsoft, or others. In
some
- 14 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
embodiments, virtualization server 301 may execute a hypervisor 302 that
creates
a virtual machine platform on which guest operating systems may execute. In
these
embodiments, the virtualization server 301 may be referred to as a host
server. An
example of such a virtualization server is the XENSERVER provided by Citrix
Systems, Inc., of Fort Lauderdale, FL.
[0053] Hypervisor 302 may create one or more virtual machines 332B-C
(generally
332) in which guest operating systems 330 execute. In some embodiments,
hypervisor 302 may load a virtual machine image to create a virtual machine
332.
In other embodiments, the hypervisor 302 may execute a guest operating system
330 within virtual machine 332. In still other embodiments, virtual machine
332
may execute guest operating system 330.
[0054] In addition to creating virtual machines 332, hypervisor 302 may
control the
execution of at least one virtual machine 332. In other embodiments,
hypervisor
302 may present at least one virtual machine 332 with an abstraction of at
least one
hardware resource provided by the virtualization server 301 (e.g., any
hardware
resource available within the hardware layer 310). In other embodiments,
hypervisor 302 may control the manner in which virtual machines 332 access
physical processors 308 available in virtualization server 301. Controlling
access to
physical processors 308 may include determining whether a virtual machine 332
should have access to a processor 308, and how physical processor capabilities
are
presented to the virtual machine 332.
[0055] As shown in FIG. 3, virtualization server 301 may host or execute one
or more
virtual machines 332. A virtual machine 332 is a set of executable
instructions that,
when executed by a processor 308, may imitate the operation of a physical
computer
such that the virtual machine 332 can execute programs and processes much like
a
physical computing device. While FIG. 3 illustrates an embodiment where a
virtualization server 301 hosts three virtual machines 332, in other
embodiments
virtualization server 301 can host any number of virtual machines 332.
Hypervisor
302, in some embodiments, may provide each virtual machine 332 with a unique
virtual view of the physical hardware, memory, processor, and other system
resources available to that virtual machine 332. In some embodiments, the
unique
virtual view can be based on one or more of virtual machine permissions,
application of a policy engine to one or more virtual machine identifiers, a
user
- 15 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
accessing a virtual machine, the applications executing on a virtual machine,
networks accessed by a virtual machine, or any other desired criteria. For
instance,
hypervisor 302 may create one or more unsecure virtual machines 332 and one or
more secure virtual machines 332. Unsecure virtual machines 332 may be
prevented
from accessing resources, hardware, memory locations, and programs that secure
virtual machines 332 may be permitted to access. In other embodiments,
hypervisor
302 may provide each virtual machine 332 with a substantially similar virtual
view
of the physical hardware, memory, processor, and other system resources
available
to the virtual machines 332.
[0056] Each virtual machine 332 may include a virtual disk 326A-C (generally
326)
and a virtual processor 328A-C (generally 328.) The virtual disk 326, in some
embodiments, is a virtualized view of one or more physical disks 304 of the
virtualization server 301, or a portion of one or more physical disks 304 of
the
virtualization server 301. The virtualized view of the physical disks 304 can
be
generated, provided, and managed by the hypervisor 302. In some embodiments,
hypervisor 302 provides each virtual machine 332 with a unique view of the
physical disks 304. Thus, in these embodiments, the particular virtual disk
326
included in each virtual machine 332 can be unique when compared with the
other
virtual disks 326.
[0057] A virtual processor 328 can be a virtualized view of one or more
physical
processors 308 of the virtualization server 301. In some embodiments, the
virtualized view of the physical processors 308 can be generated, provided,
and
managed by hypervisor 302. In some embodiments, virtual processor 328 has
substantially all of the same characteristics of at least one physical
processor 308.
In other embodiments, virtual processor 308 provides a modified view of
physical
processors 308 such that at least some of the characteristics of the virtual
processor
328 are different than the characteristics of the corresponding physical
processor
308.
[0058] With further reference to FIG. 4, some aspects described herein may be
implemented in a cloud-based environment. FIG. 4 illustrates an example of a
cloud
computing environment (or cloud system) 400. As seen in FIG. 4, client
computers
411-414 may communicate with a cloud management server 410 to access the
computing resources (e.g., host servers 403a-403b (generally referred herein
as
- 16 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
"host servers 403"), storage resources 404a-404b (generally referred herein as
"storage resources 404"), and network resources 405a-405b (generally referred
herein as -network resources 405")) of the cloud system.
[0059] Management server 410 may be implemented on one or more physical
servers.
The management server 410 may run, for example, CLOUDPLATFORM by Citrix
Systems, Inc. of Ft. Lauderdale, FL, or OPENSTACK, among others. Management
server 410 may manage various computing resources, including cloud hardware
and
software resources, for example, host computers 403, data storage devices 404,
and
networking devices 405. The cloud hardware and software resources may include
private and/or public components. For example, a cloud may be configured as a
private cloud to be used by one or more particular customers or client
computers
411-414 and/or over a private network. In other embodiments, public clouds or
hybrid public-private clouds may be used by other customers over an open or
hybrid
networks.
[0060] Management server 410 may be configured to provide user interfaces
through
which cloud operators and cloud customers may interact with the cloud system
400.
For example, the management server 410 may provide a set of application
programming interfaces (APIs) and/or one or more cloud operator console
applications (e.g., web-based or standalone applications) with user interfaces
to
allow cloud operators to manage the cloud resources, configure the
virtualization
layer, manage customer accounts, and perform other cloud administration tasks.
The management server 410 also may include a set of APIs and/or one or more
customer console applications with user interfaces configured to receive cloud
computing requests from end users via client computers 411-414, for example,
requests to create, modify, or destroy virtual machines within the cloud.
Client
computers 411-414 may connect to management server 410 via the Internet or
some
other communication network, and may request access to one or more of the
computing resources managed by management server 410. In response to client
requests, the management server 410 may include a resource manager configured
to select and provision physical resources in the hardware layer of the cloud
system
based on the client requests. For example, the management server 410 and
additional components of the cloud system may be configured to provision,
create,
and manage virtual machines and their operating environments (e.g.,
hypervisors,
- 17 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
storage resources, services offered by the network elements, etc.) for
customers at
client computers 411-414, over a network (e.g., the Internet), providing
customers
with computational resources, data storage services, networking capabilities,
and
computer platform and application support. Cloud systems also may be
configured
to provide various specific services, including security systems, development
environments, user interfaces, and the like.
[0061] Certain clients 411-414 may be related, for example, different client
computers
creating virtual machines on behalf of the same end user, or different users
affiliated
with the same company or organization. In other examples, certain clients 411-
414
may be unrelated, such as users affiliated with different companies or
organizations.
For unrelated clients, information on the virtual machines or storage of any
one user
may be hidden from other users.
[0062] Referring now to the physical hardware layer of a cloud computing
environment, availability zones 401-402 (or zones) may refer to a collocated
set of
physical computing resources. Zones may be geographically separated from other
zones in the overall cloud of computing resources. For example, zone 401 may
be
a first cloud datacenter located in California, and zone 402 may be a second
cloud
datacenter located in Florida. Management server 410 may be located at one of
the
availability zones, or at a separate location. Each zone may include an
internal
network that interfaces with devices that are outside of the zone, such as the
management server 410, through a gateway. End users of the cloud (e.g.,
clients
411-414) might or might not be aware of the distinctions between zones. For
example, an end user may request the creation of a virtual machine having a
specified amount of memory, processing power, and network capabilities. The
management server 410 may respond to the user's request and may allocate the
resources to create the virtual machine without the user knowing whether the
virtual
machine was created using resources from zone 401 or zone 402. In other
examples,
the cloud system may allow end users to request that virtual machines (or
other
cloud resources) are allocated in a specific zone or on specific resources 403-
405
within a zone.
[0063] In this example, each zone 401-402 may include an arrangement of
various
physical hardware components (or computing resources) 403-405, for example,
physical hosting resources (or processing resources), physical network
resources,
- 18 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
physical storage resources, switches, and additional hardware resources that
may be
used to provide cloud computing services to customers. The physical hosting
resources in a cloud zone 401-402 may include one or more computer servers
403,
such as the virtualization servers 301 described above, which may be
configured to
create and host virtual machine instances. The physical network resources in a
cloud
zone 401 or 402 may include one or more network elements 405 (e.g., network
service providers) comprising hardware and/or software configured to provide a
network service to cloud customers, such as firewalls, network address
translators,
load balancers, virtual private network (VPN) gateways, Dynamic Host
Configuration Protocol (DHCP) routers, and the like. The storage resources in
the
cloud zone 401-402 may include storage disks (e.g., solid state drives (SSDs),
magnetic hard disks, etc.) and other storage devices.
[0064] The example cloud computing environment shown in FIG. 4 also may
include
a virtualization layer (e.g., as shown in FIGS. 1-3) with additional hardware
and/or
software resources configured to create and manage virtual machines and
provide
other services to customers using the physical resources in the cloud. The
virtualization layer may include hypervisors, as described above in FIG. 3,
along
with other components to provide network virtualizations, storage
virtualizations,
etc. The virtualization layer may be as a separate layer from the physical
resource
layer, or may share some or all of the same hardware and/or software resources
with
the physical resource layer. For example, the virtualization layer may include
a
hypervisor installed in each of the virtualization servers 403 with the
physical
computing resources. Known cloud systems may alternatively be used, e.g.,
WINDOWS AZURE (Microsoft Corporation of Redmond Washington),
AMAZON EC2 (Amazon. corn Inc. of Seattle, Washington), IBM BLUE CLOUD
(IBM Corporation of Armonk, New York), or others.
[0065] ENTERPRISE MOBILITY MANAGEMENT ARCHITECTURE
[0066] FIG. 5 represents an enterprise mobility technical architecture 500 for
use in a
"Bring Your Own Device" (BYOD) environment. The architecture enables a user
of a mobile device 502 to both access enterprise or personal resources from a
mobile
device 502 and use the mobile device 502 for personal use. The user may access
such enterprise resources 504 or enterprise services 508 using a mobile device
502
that is purchased by the user or a mobile device 502 that is provided by the
- 19 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
enterprise to the user. The user may utilize the mobile device 502 for
business use
only or for business and personal use. The mobile device 502 may run an iOS
operating system, an Android operating system, or the like. The enterprise may
choose to implement policies to manage the mobile device 502. The policies may
be implemented through a firewall or gateway in such a way that the mobile
device
502 may be identified, secured or security verified, and provided selective or
full
access to the enterprise resources (e.g., 504 and 508.) The policies may be
mobile
device management policies, mobile application management policies, mobile
data
management policies, or some combination of mobile device, application, and
data
management policies. A mobile device 502 that is managed through the
application
of mobile device management policies may be referred to as an enrolled device.
[0067] In some embodiments, the operating system of the mobile device 502 may
be
separated into a managed partition 510 and an unmanaged partition 512. The
managed partition 510 may have policies applied to it to secure the
applications
running on and data stored in the managed partition 510. The applications
running
on the managed partition 510 may be secure applications. In other embodiments,
all applications may execute in accordance with a set of one or more policy
files
received separate from the application, and which define one or more security
parameters, features, resource restrictions, and/or other access controls that
are
enforced by the mobile device management system when that application is
executing on the mobile device 502. By operating in accordance with their
respective policy file(s), each application may be allowed or restricted from
communications with one or more other applications and/or resources, thereby
creating a virtual partition. Thus, as used herein, a partition may refer to a
physically partitioned portion of memory (physical partition), logicallya
partitioned
portion of memory (logical partition), and/or a virtual partition created as a
result
of enforcement of one or more policies and/or policy files across multiple
applications as described herein (virtual partition). Stated differently, by
enforcing
policies on managed applications, those applications may be restricted to only
be
able to communicate with other managed applications and trusted enterprise
resources, thereby creating a virtual partition that is impenetrable by
unmanaged
applications and devices.
- 20 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
[0068] The secure applications may be email applications, web browsing
applications,
software-as-a-service (SaaS) access applications, Windows Application access
applications, and the like. The secure applications may be secure native
applications
514, secure remote applications 522 executed by a secure application launcher
518,
virtualization applications 526 executed by a secure application launcher 518,
and
the like. The secure native applications 514 may be wrapped by a secure
application
wrapper 520. The secure application wrapper 520 may include integrated
policies
that are executed on the mobile device 502 when the secure native application
514
is executed on the mobile device 502. The secure application wrapper 520 may
include meta-data that points the secure native application 514 running on the
mobile device 502 to the resources hosted at the enterprise (e.g., 504 and
508) that
the secure native application 514 may require to complete the task requested
upon
execution of the secure native application 514. The secure remote applications
522
executed by a secure application launcher 518 may be executed within the
secure
application launcher 518. The virtualization applications 526 executed by a
secure
application launcher 518 may utilize resources on the mobile device 502, at
the
enterprise resources 504, and the like. The resources used on the mobile
device 502
by the virtualization applications 526 executed by a secure application
launcher 518
may include user interaction resources, processing resources, and the like.
The user
interaction resources may be used to collect and transmit keyboard input,
mouse
input, camera input, tactile input, audio input, visual input, gesture input,
and the
like. The processing resources may be used to present a user interface,
process data
received from the enterprise resources 504, and the like. The resources used
at the
enterprise resources 504 by the virtualization applications 526 executed by a
secure
application launcher 518 may include user interface generation resources,
processing resources, and the like. The user interface generation resources
may be
used to assemble a user interface, modify a user interface, refresh a user
interface,
and the like. The processing resources may be used to create information, read
information, update information, delete information, and the like. For
example, the
virtualization application 526 may record user interactions associated with a
graphical user interface (GUI) and communicate them to a server application
where
the server application will use the user interaction data as an input to the
application
operating on the server. In such an arrangement, an enterprise may elect to
maintain
the application on the server side as well as data, files, etc. associated
with the
-21 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
application. While an enterprise may elect to "mobilize" some applications in
accordance with the principles herein by securing them for deployment on the
mobile device 502, this arrangement may also be elected for certain
applications.
For example, while some applications may be secured for use on the mobile
device
502, others might not be prepared or appropriate for deployment on the mobile
device 502 so the enterprise may elect to provide the mobile user access to
the
unprepared applications through virtualization techniques. As another example,
the
enterprise may have large complex applications with large and complex data
sets
(e.g., material resource planning applications) where it would be very
difficult, or
otherwise undesirable, to customize the application for the mobile device 502
so the
enterprise may elect to provide access to the application through
virtualization
techniques. As yet another example, the enterprise may have an application
that
maintains highly secured data (e.g., human resources data, customer data,
engineering data) that may be deemed by the enterprise as too sensitive for
even the
secured mobile environment so the enterprise may elect to use virtualization
techniques to permit mobile access to such applications and data. An
enterprise may
elect to provide both fully secured and fully functional applications on the
mobile
device 502 as well as a virtualization application 526 to allow access to
applications
that are deemed more properly operated on the server side. In an embodiment,
the
virtualization application 526 may store some data, files, etc. on the mobile
device
502 in one of the secure storage locations. An enterprise, for example, may
elect to
allow certain information to be stored on the mobile device 502 while not
permitting
other information.
[0069] In connection with the virtualization application 526, as described
herein, the
mobile device 502 may have a virtualization application 526 that is designed
to
present GUIs and then record user interactions with the GUI. The
virtualization
application 526 may communicate the user interactions to the server side to be
used
by the server side application as user interactions with the application. In
response,
the application on the server side may transmit back to the mobile device 502
a new
GUI. For example, the new GUI may be a static page, a dynamic page, an
animation,
or the like, thereby providing access to remotely located resources.
[0070] The secure applications 514 may access data stored in a secure data
container
528 in the managed partition 510 of the mobile device 502. The data secured in
the
- 22 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
secure data container may be accessed by the secure native applications 514,
secure
remote applications 522 executed by a secure application launcher 518,
virtualization applications 526 executed by a secure application launcher 518,
and
the like. The data stored in the secure data container 528 may include files,
databases, and the like. The data stored in the secure data container 528 may
include
data restricted to a specific secure application 530, shared among secure
applications 532, and the like. Data restricted to a secure application may
include
secure general data 534 and highly secure data 538. Secure general data may
use a
strong form of encryption such as Advanced Encryption Standard (AES) 128-bit
encryption or the like, while highly secure data 538 may use a very strong
form of
encryption such as ABS 256-bit encryption. Data stored in the secure data
container
528 may be deleted from the mobile device 502 upon receipt of a command from
the device manager 524. The secure applications (e.g., 514, 522, and 526) may
have
a dual-mode option 540. The dual mode option 540 may present the user with an
option to operate the secured application in an unsecured or unmanaged mode.
In
an unsecured or unmanaged mode, the secure applications may access data stored
in an unsecured data container 542 on the unmanaged partition 512 of the
mobile
device 502. The data stored in an unsecured data container may be personal
data
544. The data stored in an unsecured data container 542 may also be accessed
by
unsecured applications 546 that are running on the unmanaged partition 512 of
the
mobile device 502. The data stored in an unsecured data container 542 may
remain
on the mobile device 502 when the data stored in the secure data container 528
is
deleted from the mobile device 502. An enterprise may want to delete from the
mobile device 502 selected or all data, files, and/or applications owned,
licensed or
controlled by the enterprise (enterprise data) while leaving or otherwise
preserving
personal data, files, and/or applications owned, licensed or controlled by the
user
(personal data). This operation may be referred to as a selective wipe. With
the
enterprise and personal data arranged in accordance to the aspects described
herein,
an enterprise may perform a selective wipe.
[0071] The mobile device 502 may connect to enterprise resources 504 and
enterprise
services 508 at an enterprise, to the public Internet 548, and the like. The
mobile
device 502 may connect to enterprise resources 504 and enterprise services 508
through virtual private network connections. The virtual private network
- 23 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
connections, also referred to as microVPN or application-specific VPN, may be
specific to particular applications 550, particular devices, particular
secured areas
on the mobile device 552, and the like. For example, each of the wrapped
applications in the secured area of the mobile device 502 may access
enterprise
resources through an application specific VPN such that access to the VPN
would
be granted based on attributes associated with the application, possibly in
conjunction with user or device attribute information. The virtual private
network
connections may carry Microsoft Exchange traffic, Microsoft Active Directory
traffic, HyperText Transfer Protocol (HTTP) traffic, HyperText Transfer
Protocol
Secure (HTTPS) traffic, application management traffic, and the like. The
virtual
private network connections may support and enable single-sign-on
authentication
processes 554. The single-sign-on processes may allow a user to provide a
single
set of authentication credentials, which are then verified by an
authentication
service 558. The authentication service 558 may then grant to the user access
to
multiple enterprise resources 504, without requiring the user to provide
authentication credentials to each individual enterprise resource 504.
[0072] The virtual private network connections may be established and managed
by an
access gateway 560. The access gateway 560 may include performance
enhancement features that manage, accelerate, and improve the delivery of
enterprise resources 504 to the mobile device 502. The access gateway 560 may
also re-route traffic from the mobile device 502 to the public Internet 548,
enabling
the mobile device 502 to access publicly available and unsecured applications
that
run on the public Internet 548. The mobile device 502 may connect to the
access
gateway via a transport network 562. The transport network 562 may be a wired
network, wireless network, cloud network, local area network, metropolitan
area
network, wide area network, public network, private network, and the like.
[0073] The enterprise resources 504 may include email servers, file sharing
servers,
SaaS applications, Web application servers, Windows application servers, and
the
like. Email servers may include Exchange servers, Lotus Notes servers, and the
like.
File sharing servers may include ShareFile servers, and the like. SaaS
applications
may include Salesforce, and the like. Windows application servers may include
any
application server that is built to provide applications that are intended to
run on a
local Windows operating system, and the like. The enterprise resources 504 may
be
- 24 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
premise-based resources, cloud-based resources, and the like. The enterprise
resources 504 may be accessed by the mobile device 502 directly or through the
access gateway 560. The enterprise resources 504 may be accessed by the mobile
device 502 via the transport network 562.
[0074] The enterprise services 508 may include authentication services 558,
threat
detection services 564, device manager services 524, file sharing services
568,
policy manager services 570, social integration services 572, application
controller
services 574, and the like. Authentication services 558 may include user
authentication services, device authentication services, application
authentication
services, data authentication services, and the like. Authentication services
558 may
use certificates. The certificates may be stored on the mobile device 502, by
the
enterprise resources 504, and the like. The certificates stored on the mobile
device
502 may be stored in an encrypted location on the mobile device 502, the
certificate
may be temporarily stored on the mobile device 502 for use at the time of
authentication, and the like. Threat detection services 564 may include
intrusion
detection services, unauthorized access attempt detection services, and the
like.
Unauthorized access attempt detection services may include unauthorized
attempts
to access devices, applications, data, and the like. Device management
services 524
may include configuration, provisioning, security, support, monitoring,
reporting,
and decommissioning services. File sharing services 568 may include file
management services, file storage services, file collaboration services, and
the like.
Policy manager services 570 may include device policy manager services,
application policy manager services, data policy manager services, and the
like.
Social integration services 572 may include contact integration services,
collaboration services, integration with social networks such as Facebook,
Twitter,
and LinkedIn, and the like. Application controller services 574 may include
management services, provisioning services, deployment services, assignment
services, revocation services, wrapping services, and the like.
[0075] The enterprise mobility technical architecture 500 may include an
application
store 578. The application store 578 may include unwrapped applications 580,
pre-
wrapped applications 582, and the like. Applications may be populated in the
application store 578 from the application controller 574. The application
store 578
may be accessed by the mobile device 502 through the access gateway 560,
through
- 25 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
the public Internet 548, or the like. The application store 578 may be
provided with
an intuitive and easy to use user interface.
[0076] A software development kit 584 may provide a user the capability to
secure
applications selected by the user by wrapping the application as described
previously in this description. An application that has been wrapped using the
software development kit 584 may then be made available to the mobile device
502
by populating it in the application store 578 using the application controller
574.
[0077] The enterprise mobility technical architecture 500 may include a
management
and analytics capability 588. The management and analytics capability 588 may
provide information related to how resources are used, how often resources are
used, and the like. Resources may include devices, applications, data, and the
like.
How resources are used may include which devices download which applications,
which applications access which data, and the like. How often resources are
used
may include how often an application has been downloaded, how many times a
specific set of data has been accessed by an application, and the like.
[0078] FIG. 6 is another illustrative enterprise mobility management system
600. Some
of the components of the mobility management system 500 described above with
reference to FIG. 5 have been omitted for the sake of simplicity. The
architecture
of the system 600 depicted in FIG. 6 is similar in many respects to the
architecture
of the system 500 described above with reference to FIG. 5 and may include
additional features not mentioned above.
[0079] In this case, the left hand side represents an enrolled mobile device
602 with a
client agent 604, which interacts with gateway server 606 (which includes
Access
Gateway and application controller functionality) to access various enterprise
resources 608 and services 609 such as Exchange, Sharepoint, public-key
infrastructure (PKI) Resources, Kerberos Resources, Certificate Issuance
service,
as shown on the right hand side above. Although not specifically shown, the
mobile
device 602 may also interact with an enterprise application store (StoreFront)
for
the selection and downloading of applications.
[0080] The client agent 604 acts as the UI (user interface) intermediary for
Windows
apps/desktops hosted in an Enterprise data center, which are accessed using
the
High-Definition User Experience (HDX)/ICA display remoting protocol. The
client
- 26 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
agent 604 also supports the installation and management of native applications
on
the mobile device 602, such as native iOS or Android applications. For
example,
the managed applications 610 (mail, browser, wrapped application) shown in the
figure above are all native applications that execute locally on the mobile
device
602. Client agent 604 and application management framework of this
architecture
act to provide policy driven management capabilities and features such as
connectivity and SSO (single sign on) to enterprise resources/services 608.
The
client agent 604 handles primary user authentication to the enterprise,
normally to
Access Gateway (AG) 606 with SSO to other gateway server components. The
client agent 604 obtains policies from gateway server 606 to control the
behavior
of the managed applications 610 on the mobile device 602.
[0081] The Secure InterProcess Communication (IPC) links 612 between the
native
applications 610 and client agent 604 represent a management channel, which
may
allow a client agent to supply policies to be enforced by the application
management
framework 614 "wrapping- each application. The IPC channel 612 may also allow
client agent 604 to supply credential and authentication information that
enables
connectivity and SSO to enterprise resources 608. Finally, the IPC channel 612
may
allow the application management framework 614 to invoke user interface
functions implemented by client agent 604, such as online and offline
authentication.
[0082] Communications between the client agent 604 and gateway server 606 are
essentially an extension of the management channel from the application
management framework 614 wrapping each native managed application 610. The
application management framework 614 may request policy information from
client agent 604, which in turn may request it from gateway server 606. The
application management framework 614 may request authentication, and client
agent 604 may log into the gateway services part of gateway server 606 (also
known
as NETSCALER ACCESS GATEWAY). Client agent 604 may also call supporting
services on gateway server 606, which may produce input material to derive
encryption keys for the local data vaults 616, or may provide client
certificates
which may enable direct authentication to PKI protected resources, as more
fully
explained below.
- 27 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
[0083] In more detail, the application management framework 614 "wraps" each
managed application 610. This may be incorporated via an explicit build step,
or
via a post-build processing step. The application management framework 614 may
"pair" with client agent 604 on first launch of an application 610 to
initialize the
Secure IPC channel 612 and obtain the policy for that application. The
application
management framework 614 may enforce relevant portions of the policy that
apply
locally, such as the client agent login dependencies and some of the
containment
policies that restrict how local OS services may be used, or how they may
interact
with the managed application 610.
[0084] The application management framework 614 may use services provided by
client agent 604 over the Secure IPC channel 612 to facilitate authentication
and
internal network access. Key management for the private and shared data vaults
616
(containers) may be also managed by appropriate interactions between the
managed
applications 610 and client agent 604. Vaults 616 may be available only after
online
authentication, or may be made available after offline authentication if
allowed by
policy. First use of vaults 616 may require online authentication, and offline
access
may be limited to at most the policy refresh period before online
authentication is
again required.
10085] Network access to internal resources may occur directly from individual
managed applications 610 through Access Gateway 606. The application
management framework 614 may be responsible for orchestrating the network
access on behalf of each managed application 610. Client agent 604 may
facilitate
these network connections by providing suitable time limited secondary
credentials
obtained following online authentication. Multiple modes of network connection
may be used, such as reverse web proxy connections and end-to-end VPN-style
tunnels 618.
[0086] The Mail and Browser managed applications 610 have special status and
may
make use of facilities that might not be generally available to arbitrary
wrapped
applications. For example, the Mail application 610 may use a special
background
network access mechanism that allows it to access an Exchange server 608 over
an
extended period of time without requiring a full AG logon. The Browser
application
610 may use multiple private data vaults 616 to segregate different kinds of
data.
- 28 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
[0087] This architecture may support the incorporation of various other
security
features. For example, gateway server 606 (including its gateway services) in
some
cases may not need to validate active directory (AD) passwords. It can be left
to the
discretion of an enterprise whether an AD password may be used as an
authentication factor for some users in some situations. Different
authentication
methods may be used if a user is online or offline (i.e., connected or not
connected
to a network).
[0088] Step up authentication is a feature wherein gateway server 606 may
identify
managed native applications 610 that are allowed to have access to highly
classified
data requiring strong authentication, and ensure that access to these
applications is
only permitted after performing appropriate authentication, even if this means
a re-
authentication is required by the user after a prior weaker level of login.
[0089] Another security feature of this solution is the encryption of the data
vaults 616
(containers) on the mobile device 602. The vaults 616 may be encrypted so that
all
on-device data including files, databases, and configurations are protected.
For on-
line vaults, the keys may be stored on the server (gateway server 606), and
for off-
line vaults, a local copy of the keys may be protected by a user password or
biometric validation. If or when data is stored locally on the mobile device
602 in
the secure container 616, it may be preferred that a minimum of AES 256
encryption
algorithm be utilized.
[0090] Other secure container features may also be implemented. For example, a
logging feature may be included, wherein security events happening inside a
managed application 610 may be logged and reported to the backend. Data wiping
may be supported, such as if or when the managed application 610 detects
tampering, associated encryption keys may be written over with random data,
leaving no hint on the file system that user data was destroyed. Screenshot
protection may be another feature, where an application may prevent any data
from
being stored in screenshots. For example, the key window's hidden property may
be set to YES. This may cause whatever content is currently displayed on the
screen
to be hidden, resulting in a blank screenshot where any content would normally
reside.
- 29 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
[0091] Local data transfer may be prevented, such as by preventing any data
from being
locally transferred outside the application container, e.g., by copying it or
sending
it to an external application. A keyboard cache feature may operate to disable
the
autocorrect functionality for sensitive text fields. SSL certificate
validation may be
operable so the application specifically validates the server SSL certificate
instead
of it being stored in the keychain. An encryption key generation feature may
be used
such that the key used to encrypt data on the mobile device 602 is generated
using
a passphrase or biometric data supplied by the user (if offline access is
required). It
may be X0Red with another key randomly generated and stored on the server side
if offline access is not required. Key Derivation functions may operate such
that
keys generated from the user password use KDFs (key derivation functions,
notably
Password-Based Key Derivation Function 2 (PBKDF2)) rather than creating a
cryptographic hash of it. The latter makes a key susceptible to brute force or
dictionary attacks.
[0092] Further, one or more initialization vectors may be used in encryption
methods.
An initialization vector will cause multiple copies of the same encrypted data
to
yield different cipher text output, preventing both replay and cryptanalytic
attacks.
This will also prevent an attacker from decrypting any data even with a stolen
encryption key if the specific initialization vector used to encrypt the data
is not
known. Further, authentication then decryption may be used, wherein
application
data is decrypted only after the user has authenticated within the
application.
Another feature may relate to sensitive data in memory, which may be kept in
memory (and not in disk) only when it's needed. For example, login credentials
may be wiped from memory after login, and encryption keys and other data
inside
objective-C instance variables are not stored, as they may be easily
referenced.
Instead, memory may be manually allocated for these.
[0093] An inactivity timeout may be implemented, wherein after a policy-
defined
period of inactivity, a user session is terminated.
[0094] Data leakage from the application management framework 614 may be
prevented in other ways. For example, if or when a managed application 610 is
put
in the background, the memory may be cleared after a predetermined
(configurable)
time period. When backgrounded, a snapshot may be taken of the last displayed
- 30 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
screen of the application to fasten the foregrounding process. The screenshot
may
contain confidential data and hence should be cleared.
[0095] Another security feature may relate to the use of an OTP (one time
password)
620 without the use of an AD (active directory) 622 password for access to one
or
more applications. In some cases, some users do not know (or are not permitted
to
know) their AD password, so these users may authenticate using an OTP 620 such
as by using a hardware OTP system like SecurID (OTPs may be provided by
different vendors also, such as Entrust or Gemalto). In some cases, after a
user
authenticates with a user ID, a text may be sent to the user with an OTP 620.
In
some cases, this may be implemented only for online use, with a prompt being a
single field.
[0096] An offline password may be implemented for offline authentication for
those
managed applications 610 for which offline use is permitted via enterprise
policy.
For example, an enterprise may want StoreFront to be accessed in this manner.
In
this case, the client agent 604 may require the user to set a custom offline
password
and the AD password is not used. Gateway server 606 may provide policies to
control and enforce password standards with respect to the minimum length,
character class composition, and age of passwords, such as described by the
standard Windows Server password complexity requirements, although these
requirements may be modified.
[0097] Another feature may relate to the enablement of a client side
certificate for
certain applications 610 as secondary credentials (for the purpose of
accessing PKI
protected web resources via the application management framework micro VPN
feature). For example, a managed application 610 may utilize such a
certificate. In
this case, certificate-based authentication using ActiveSync protocol may be
supported, wherein a certificate from the client agent 604 may be retrieved by
gateway server 606 and used in a keychain. Each managed application 610 may
have one associated client certificate, identified by a label that is defined
in gateway
server 606.
[0098] Gateway server 606 may interact with an enterprise special purpose web
service
to support the issuance of client certificates to allow relevant managed
applications
to authenticate to internal PKI protected resources.
-31-
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
[0099] The client agent 604 and the application management framework 614 may
be
enhanced to support obtaining and using client certificates for authentication
to
internal PM protected network resources. More than one certificate may be
supported, such as to match various levels of security and/or separation
requirements. The certificates may be used by the Mail and Browser managed
applications 610, and ultimately by arbitrary wrapped applications 610
(provided
those applications use web service style communication patterns where it is
reasonable for the application management framework to mediate HTTPS
requests).
[0100] Application management client certificate support on iOS may rely on
importing a public-key cryptography standards (PKCS) 12 BLOB (Binary Large
Object) into the iOS keychain in each managed application 610 for each period
of
use. Application management framework client certificate support may use a
HTTPS implementation with private in-memory key storage. The client
certificate
may not be present in the iOS keychain and may not be persisted except
potentially
in "online-only" data value that is strongly protected.
[0101] Mutual SSL may also be implemented to provide additional security by
requiring that a mobile device 602 is authenticated to the enterprise, and
vice versa.
Virtual smart cards for authentication to gateway server 606 may also be
implemented.
[0102] Both limited and full Kerberos support may be additional features. The
full
support feature relates to an ability to do full Kerberos login to Active
Directory
(AD) 622, using an AD password or trusted client certificate, and obtain
Kerberos
service tickets to respond to HTTP Negotiate authentication challenges. The
limited
support feature relates to constrained delegation in Citrix Access Gateway
Enterprise Edition (AGEE), where AGEE supports invoking Kerberos protocol
transition so it can obtain and use Kerberos service tickets (subject to
constrained
delegation) in response to HTTP Negotiate authentication challenges. This
mechanism works in reverse web proxy (aka corporate virtual private network
(CVPN)) mode, and when HTTP (but not HTTPS) connections are proxied in VPN
and MicroVPN mode.
- 32 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
[0103] Another feature may relate to application container locking and wiping,
which
may automatically occur upon jail-break or rooting detections, and occur as a
pushed command from administration console, and may include a remote wipe
functionality even when a managed application 610 is not running.
[0104] A multi-site architecture or configuration of enterprise application
store and an
application controller may be supported that allows users to be serviced from
one
of several different locations in case of failure.
[0105] In some cases, managed applications 610 may be allowed to access a
certificate
and private key via an API (for example, OpenSSL). Trusted managed
applications
610 of an enterprise may be allowed to perform specific Public Key operations
with
an application's client certificate and private key. Various use cases may be
identified and treated accordingly, such as if or when an application behaves
like a
browser and no certificate access is required, if or when an application reads
a
certificate for "who am I," if or when an application uses the certificate to
build a
secure session token, and if or when an application uses private keys for
digital
signing of important data (e.g. transaction log) or for temporary data
encryption.
[0106] WRAPPING CONTINUATION TOKENS TO SUPPORT PAGING FOR MULTIPLE
SERVERS ACROSS DIFFERENT GEOLOCATIONS
[0107] As discussed above, aspects of the disclosure relate to wrapping
continuation
tokens to support paging for multiple servers across different geolocations.
In
addition, one or more aspects of the disclosure may incorporate, be embodied
in,
and/or be implemented using one or more of the computer system architecture,
remote-access system architecture, virtualized (hypervisor) system
architecture,
cloud-based system architecture, and/or enterprise mobility management systems
discussed above in connection with FIGS. 1-6.
[0108] Figure 7 depicts an illustrative computing environment for wrapping
continuation tokens to support paging for multiple servers across different
geolocations in accordance with one or more illustrative aspects described
herein.
Referring to FIG. 7, computing environment 700 may include an enterprise
server
710, a first enterprise geo data server 720, a second enterprise geo data
server 730,
client devices 740 and 750, and an enterprise network 760. Enterprise server
710,
first enterprise geo data server 720, second enterprise geo data server 730,
and client
- 33 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
devices 740 and 750 may include one or more physical components, such as one
or
more processors, memories, communication interfaces, and/or the like.
[0109] Enterprise server 710 may include processor 711, memory 712,
communication
interface 713 and data store 714. Processor 711 may execute instructions
stored in
memory 712 to cause enterprise server 710 to perform one or more functions,
such
as generating a first continuation token and wrapping the first continuation
token
with a geolocation-server identifier to produce a first wrapped continuation
token.
Communication interface 713 may include one or more network interfaces via
which enterprise server 710 can communicate with one or more other systems
and/or devices in computing environment 700, such as , first enterprise geo
data
server 720, second enterprise geo data server 730, and client devices 740 and
750.
Memory 712 may include a token store (not shown) which may store the
continuation tokens and the wrapped continuation tokens temporarily before
they
are transmitted to and from client device 740 and client device 750.
Enterprise 710
may host data store 714, which may provide storage of big data in the cloud
computing environment. In some examples, data store 714 may include a schema-
less database or non-SQL databases, such as key-value stores and document
stores,
which may focus on the storage and retrieval of large volumes of unstructured,
semi-structured, or structured data. Such
database systems may achieve
performance gain by doing away with certain of the restrictions traditionally
associated with conventional databases, such as read-write consistency, in
exchange
for scalability and distributed processing spanning over multiple
geolocations. In
some examples, data store 714 may not impose certain form of schemas, data-
models, or formats which may hinder the process to read or instantiate data
quickly.
In alternative arrangements, data store 714 may not enforce data type
limitations on
individual values pertaining to one single column type. For example, data
store 714
may not need pre-setting data types in the repository, which may reduce time
to set
up a data repository. In some embodiments, data store 714 may eliminate the
need
to introduce additional layers (such as Object-Relational Mapping (ORM) layer)
to
abstract the relational model and expose it in an object oriented format. As a
result,
data store 714 may store data with different characteristics and tolerate
changes to
the data definition without having to plan for complex outages and changes and
may
eliminate complex schema migrations. In some embodiments, data store 714 may
- 34 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
not need complex and proprietary infrastructure with excessive capital and
operational expenditure to scale. For example, a relative small instance may
be
scaled easily with simple operations, while some traditional databases may
offer
this feature but the rigidity of the schema may impose limits. Given that
scalability
may not merely be the ability to shard the data, it may also be the ability to
adapt to
changing schema with speed, data store 714 may implement on-demand scalability
seamlessly and may implement the deployment on relative less expensive
commodity hardware.
[0110] In some examples, as illustrated in FIG. 7, data store 714 may reside
on
enterprise server 710. In alternative arrangements, enterprise server 710 and
data
store 714 may reside on the separate computing devices, and data store 714 may
be
managed by enterprise server 710 remotely.
[0111] Enterprise server 710 may be associated with an enterprise organization
and
may send and receive information to client device 740 and client device 750
and
other computing devices of computing environment 700. Enterprise server 710
may
manage client device 740 and client device 750. Enterprise users may access
system
resources through client device 740 and client device 750. Client device 740
and
client device 750 may be any type of computing device including, for example,
a
server, computer, laptop, tablet, smartphone, or other client device that
includes a
processor (e.g., computing device 201). Client devices 740 and 750 may
communicate, via their communication interfaces (e.g., wireless interfaces,
LAN
interfaces, WLAN interfaces), with other devices and/or entities such as
enterprise
server 710, first enterprise geo data server 720, and second enterprise geo
data
server 730, as discussed in greater detail below. Client devices 740 and 750
may
also communicate with various network nodes described herein.
[0112] Enterprise network 760 may include one or more wide area networks
and/or
local area networks and may interconnect one or more systems and/or devices
included in computing environment 700. For example, enterprise network 760 may
interconnect enterprise server 710, first enterprise geo data server 720,
second
enterprise geo data server 730, and client devices 740 and 750.
[0113] Environment 700 may include first enterprise geo data server 720 and
second
enterprise geo data server 730, which may each include a processor, a memory,
a
- 35 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
communication interface, and a data store similar to that residing on
enterprise
server 710. In some examples, the data stores of first enterprise geo data
server 720
and second enterprise geo data server 730 may host schema-less databases
similar
to those on enterprise server 710. Enterprise server 710, first enterprise geo
data
server 720 and second enterprise geo data server 730 may be responsible for
generating and managing wrapped continuation tokens to facilitate data storage
and
retrieval spanning multiple geolocations. In some examples, enterprise server
710
may manage a predetermined list of servers including first enterprise geo data
server
720 and second enterprise geo data server 730, and direct requests for data
retrieval
to first enterprise geo data server 720 and second enterprise geo data server
730
based on a predetermined order. In alternative arrangements, enterprise server
710
may manage first enterprise geo data server 720 and second enterprise geo data
server 730, and direct requests for data retrieval to first enterprise geo
data server
720 and second enterprise geo data server 730 based on a random order. In
still
other arrangements, enterprise server 710 may manage and balance the load on
first
enterprise geo data server 720 and second enterprise geo data server 730, and
direct
requests for data retrieval to first enterprise geo data server 720 and second
enterprise geo data server 730 based on the load on the systems. In some
examples,
enterprise server 710 may direct the requests for data retrieval to first
enterprise geo
data server 720 and second enterprise geo data server 730 based on the
location
information included in and/or otherwise associated with the wrapped
continuation
token corresponding to the geographical locations of first enterprise geo data
server
720 and second enterprise geo data server 730. Although only two enterprise
geo
data servers are illustrated in FIG. 7, environment 700 may include one or
more
enterprise geo data servers suitable for the enterprises in the cloud
computing
environment.
[0114] FIGS. 8A-8D depict an example event sequence for wrapping continuation
tokens to support paging for multiple servers across different geolocations in
accordance with one or more illustrative aspects described herein. The
communications between components illustrated in FIGS. 8A-8D may be encrypted
via Transport Layer Security (TLS) cryptographic protocols or Internet
Protocol
Security (IPsec) tunnels that provide communications security over a computer
network.
- 36 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
[0115] Referring to FIG. 8A, at step 801, a client device may send a first
request to an
enterprise geo data server such as an enterprise server to retrieve a
plurality of
records. For example, client device 740 may send requests to enterprise server
710
to retrieve a plurality of records via enterprise network 760. In some
examples, the
client device may send a request for data retrieval to a cluster of enterprise
geo data
servers in a virtual, cloud-based enterprise system, where enterprise server
710 may
be responsible to interact with client device 740 directly. In some examples,
enterprise server 710 may assume a managerial role in the cluster of
enterprise geo
data servers to receive and process the requests on behalf of the cluster.
[0116] At step 802, the enterprise server may determine that the first request
for the
plurality of records may request a quantity of records exceeding a page size
limit.
In some examples, when the query in the first request is executed in the table
storage
of the data store, a large amount of data may be returned, which may exceed a
page
size limit of the system. For example, some systems may specify a page size
limit
of 1,000 records or table rows in a single request. Due to the incomplete
fulfillment
of the query in a single iteration, enterprise 710 may need to execute a
series of
consecutive data segment reads and aggregate the result.
[0117] In some examples, the records requested by the client device may be
segmented
in partitions across multiple geolocations. Segmentation may be implemented to
support data sovereignty subject to the laws of the country in which data may
be
located. For example, in a multi-geolocations scenario, data may be segmented
so
that, in each geolocation, the data partition may contain data originated in
that
geographic area. For instance, data originated in the U.S. may be separated
from
data originated in Europe and may reside in different data partitions.
[0118] At step 803, the enterprise server may retrieve a first set of records
comprising
a first number of records equal to the page size limit. For example, in a
query to
list all the customer data, which may exceed the page size limit of 1,000
records,
enterprise server 710 may retrieve a first set of records that contains 1,000
records
from its data store.
[0119] At step 804, the enterprise server may generate a first wrapped
continuation
token comprising location information identifying a geographic location of a
first
server where a next set of records may be retrieved. The continuation token
may
- 37 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
be used to go back and forth through the data sets as a mechanism to providing
paging support. In the example illustrated above, data store 714 of enterprise
server
710 may implement a continuation token, when the client device query a large
amount of data, as a mechanism to provide consistent response time per request
and
avoid time-out. In some examples, the continuation token may be used when the
corresponding query responses exceed the maximum allowed rows per call. For
instance, enterprise server 710 may return the first 1,000 records with a
continuation
token, which may be used to retrieve the next set of records. In some
examples, the
continuation token may be used when the corresponding queries span across
multiple partitions. In alternative arrangements, the continuation token may
be used
when the corresponding queries takes more than a predetermined time limit
(such
as 5 seconds) to execute on enterprise server 710.
10120] In some examples, to support paging across multiple geolocations,
enterprise
server 710 may wrap the continuation token in a way that may identify which
particular geolocation may be mined. For example, the continuation token may
be
an XML structure that may hold information for retrieving the next set of
records.
Enterprise server 710 may add an additional field in the XML structure to
indicate
the location information identifying a geographic location of a server where a
next
set of records may be retrieved. In some examples, the continuation token may
be
an integer or other type of data to identify a location of the next set of
records to be
retrieved. For instance, enterprise server 710 may wrap the continuation token
with
an additional element to the data structure of the continuation token to
indicate the
data store where the continuation token may be originated from. For instance,
a
data element may be added to the continuation token as an indicator to the
name of
the data server, where the client may request the next set of records from. In
this
case, the name may be the name of the geographical location. For example, the
wrapped continuation token may take the form of "[Geo:1, token: xxxl" to
identify
which geo to call, where "xxx" may be the name of the token, and Geo:1 may be
an
indication of a general location, such as "US" or "Europe" to indicate where
the
data store may reside in.
10121] At step 805, the enterprise server may send, to the client device, a
first set of
records and the first wrapped continuation token. For example, enterprise
server
710 may send the first set of 1,000 records and the newly generated wrapped
- 38 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
continuation token to client device 740. At step 806, the client device may
process
the first set of records.
[0122] Turning to FIG. 8B, at step 807, the client device may send the first
wrapped
continuation token to the enterprise server. For example, client device 740
may
send the first wrapped continuation token to enterprise server 710. The
existence
of the first wrapped continuation token may indicate to the client device that
there
may be additional set of data to be retrieved and the first wrapped
continuation
token may indicate the name of the server where to request this additional set
of
data.
[0123] At step 808, the enterprise server may identify a second set of records
associated
with the plurality of the records to retrieve based on the first wrapped
continuation
token. For example, based on the location information and internal data
structure
of the wrapped continuation token, enterprise server 710 may start retrieving
the
second set of data records from the data store residing on enterprise server
710.
[0124] At step 809, in response to identifying the second set of records, the
enterprise
server may retrieve the second set of records comprising a second number of
records
less than the page size limit. For example, enterprise server 710 may retrieve
a set
of records corresponding to a second number of records. If the second number
of
records is less than the page size limit, this may be an indication that
enterprise
server 710 may need to go to the next data store to retrieve the next set of
records.
In some examples, there may be an explicit or predetermined order of the
enterprise
geo data servers, so enterprise server 710 may direct the requests for
additional
records to the next enterprise geo data server in the predetermined order. In
some
alternative arrangements, the client device may be aware of this predetermined
order and may know where to go to request next set of records.
[0125] In some examples, upon a determination that there is not more data to
be
retrieved from the data store on the enterprise server, the enterprise server
may call
the next enterprise geo data server on the pre-established order. As such, at
step
810, the enterprise server may send a second request to enterprise geo data
server
720 to retrieve a third set of records comprising a third number of records.
[0126] At step 811, in response to a determination that there are additional
records to
be retrieved from enterprise geo data server 720, the first enterprise geo
data server
- 39 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
may retrieve the third set of records and at step 812, enterprise geo data
server 720
may generate a second wrapped continuation token. Likewise, the second wrapped
continuation token may include location information identifying a geographic
location of enterprise geo data server 720 where a next set of records in the
plurality
of the records is to be retrieved.
[0127] At step 813 in FIG. 8C, enterprise geo data server 720 may send the
third set of
records and the second wrapped continuation token to the enterprise server.
Subsequently, at step 814, the enterprise may send the second set of records
retrieved from the enterprise server, the third set of records and the second
wrapped
continuation token received from enterprise geo data server 720 to the client
device.
[0128] At step 815, the client device may process the second and third set of
records.
In some examples, the client device may aggregate the first, second and third
set of
records together. In this manner, data retrieved from multiple servers may be
aggregated and presented to the client device with persistency to avoid
timeout.
[0129] At step 816, the client device may send the second wrapped continuation
token
to the enterprise server. In some embodiments, given that enterprise server
710 may
manage the cluster of enterprise geo data servers, the enterprise server may
act as
an intermediate between the communications of the client device with the
enterprise
geo data servers.
[0130] At step 817, the enterprise server may forward the second wrapped
continuation
token to enterprise geo data server 720 based on the geographic location
associated
with the second wrapped continuation token. In some examples, the second
wrapped continuation token may include location information identifying
enterprise
geo data server 720.
[0131] At step 818, enterprise geo data server 720 may retrieve the fourth set
of records
from enterprise geo data server 720, and the fourth set of records may
comprise a
fourth number of records less than the page size limit. For example, the
fourth set
of records may contain less than 1,000 records. At step 819 as illustrated in
FIG.
8D. enterprise geo data server 720 may send the fourth set of records to the
enterprise server.
101321 At step 820, the enterprise server may send a third request to
enterprise geo data
server 730 to retrieve additional records in the plurality of records. In some
- 40 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
examples, the enterprise server may follow a predetermined order of the list
of the
servers and identify enterprise geo data server 730 as the next server on the
list.
[0133] At step 821, enterprise geo data server 730 may retrieve a fifth set of
records to
be retrieved from enterprise geo data server 730 comprising a fifth number of
records, and a sum of the fourth number of records and the fifth number of
records
may be less than the page size limit. At step 822, enterprise geo data server
730
may send the fifth set of records to the enterprise server.
[0134] At step 823, the enterprise server may determine that there may be no
additional
records in the plurality of the records. In some examples, the enterprise
server may
determine that the ordered list of the enterprise geo data servers have been
exhausted, and take this as an indication that there may be no additional
records to
be retrieved.
[0135] At step 824, the enterprise server may send the fourth and the fifth
set of records
to the client device and finally at step 825, the client device may process
the fourth
set and the fifth set of records. For example, the client device may aggregate
the
fourth and the fifth set of records. As such, the client device may access and
aggregate set of records from different servers, while the client device may
not need
to know that the fourth and the fifth set of records may be retrieved from
data stores
across geolocations.
[0136] FIG. 9 depicts an illustrative method for wrapping continuation tokens
to
support paging across for multiple servers across different geolocations in
accordance with one or more example embodiments. Referring to FIG. 9, at step
902, an enterprise server (e.g. enterprise server 710) having at least one
processor,
a communication interface, and memory, may receive, via the communication
interface and from a client device, a first request for a plurality of
records, and the
first request for the plurality of records may request a quantity of records
exceeding
a page size limit. At step 904, in response to receiving the first request for
the
plurality of records, the enterprise server may retrieve a first set of
records
comprising a first number of records equal to the page size limit. At step
906, the
server may generate a first wrapped continuation token comprising location
information identifying a geographic location of a first server where a next
set of
records is to be retrieved. At step 908, the enterprise server may send, via
the
-41 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
communication interface and to the client device, the first set of records and
the first
wrapped continuation token. Accordingly, sending the first wrapped
continuation
token to the client device may cause the client device to process the first
set of
records.
[0137] One or more aspects of the disclosure may be embodied in computer-
usable data
or computer-executable instructions, such as in one or more program modules,
executed by one or more computers or other devices to perfofin the operations
described herein. Generally, program modules include routines, programs,
objects,
components, data structures, and the like that perform particular tasks or
implement
particular abstract data types when executed by one or more processors in a
computer or other data processing device. The computer-executable instructions
may be stored as computer-readable instructions on a computer-readable medium
such as a hard disk, optical disk, removable storage media, solid-state
memory,
RAM, and the like. The functionality of the program modules may be combined or
distributed as desired in various embodiments. In addition, the functionality
may
be embodied in whole or in part in firmware or hardware equivalents, such as
integrated circuits, application-specific integrated circuits (ASICs), field
programmable gate arrays (FPGA), and the like. Particular data structures may
be
used to more effectively implement one or more aspects of the disclosure, and
such
data structures are contemplated to be within the scope of computer executable
instructions and computer-usable data described herein.
[0138] Various aspects described herein may be embodied as a method, an
apparatus,
or as one or more computer-readable media storing computer-executable
instructions. Accordingly, those aspects may take the form of an entirely
hardware
embodiment, an entirely software embodiment, an entirely firmware embodiment,
or an embodiment combining software, hardware, and firmware aspects in any
combination. In addition, various signals representing data or events as
described
herein may be transferred between a source and a destination in the form of
light or
electromagnetic waves traveling through signal-conducting media such as metal
wires, optical fibers, or wireless transmission media (e.g., air or space). In
general,
the one or more computer-readable media may be and/or include one or more non-
transitory computer-readable media.
- 42 -
CA 03073068 2020-02-13
WO 2019/046083
PCT/US2018/047644
[0139] As described herein, the various methods and acts may be operative
across one
or more computing servers and one or more networks. The functionality may be
distributed in any manner, or may be located in a single computing device
(e.g., a
server, a client computer, and the like). For example, in alternative
embodiments,
one or more of the computing platforms discussed above may be implemented in
one or more virtual machines that are provided by one or more physical
computing
devices. In such arrangements, the various functions of each computing
platform
may be performed by the one or more virtual machines, and any and/or all of
the
above-discussed communications between computing platforms may correspond to
data being accessed, moved, modified, updated, and/or otherwise used by the
one
or more virtual machines.
[0140] Aspects of the disclosure have been described in terms of illustrative
embodiments thereof Numerous other embodiments, modifications, and variations
within the scope and spirit of the appended claims will occur to persons of
ordinary
skill in the art from a review of this disclosure. For example, one or more of
the
steps depicted in the illustrative figures may be performed in other than the
recited
order, and one or more depicted steps may be optional in accordance with
aspects
of the disclosure.
[0141] Although the subject matter has been described in language specific to
structural
features and/or methodological acts, it is to be understood that the subject
matter
defined in the appended claims is not necessarily limited to the specific
features or
acts described above. Rather, the specific features and acts described above
are
described as example implementations of the following claims.
- 43 -
