DETAILED ACTION
Priority
This action is in response to the U.S. filing dated 23 August 2023 which is a national stage entry of PCT/CN2022/079115, dated 03 March 2022, which claims a foreign priority date, of 25 April 2021. A preliminary amendment was submitted on 23 August 2023. Claims 3-6, 8, 10, 11, 14-18 and 20 are amended. Claims 19 and 21-22 have been cancelled. Claim 23 has been added. Claims 1-18, 20 and 23 are pending and have been considered below.
Receipt is acknowledged of certified copies of papers required by 37 CFR 1.55.
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Information Disclosure Statement
The information disclosure statement (IDS) submitted on 23 August 2023 has been received, entered into the record, and considered. The submission is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner.
Claim Objections
Claims 3, 7 and 14 objected to because of the following informalities: claims 3, 7 and 14 use “and/or” terminology. Examiner does however note that, “A and/or B” does have a meaning and that meaning is A alone, B alone, or A and B together. The “preferred verbiage” should be more simply “at least one of A and B.” Further, giving the claim limitation the broadest reasonable interpretation, the examiner will use the broader “or” recitation. Appropriate correction is required.
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claims 1, 2, 6-9, 12-15, 17, 18, 20 and 23 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Aluvala et al. (US 2017/0339142 A1).
As for independent claim 1, Aluvala discloses a method comprising:
displaying a platform list in an interface of a terminal device, wherein the platform list comprises a platform identifier corresponding to at least one platform [(e.g. see Aluvala paragraph 0071 and Fig. 3) ”Continuing with the example of FIG. 3, the GUI 305 can display a list 320 of virtual machines 140 associated with the user. The list 320 can identify virtual machines 324 and a status 326 for each of the virtual machines 324”].
displaying an operation and maintenance page of a first platform on the interface of the terminal device in response to a selection operation of a user on the platform identifier of the first platform, wherein the operation and maintenance page comprises at least one of a stream-pushing page, a controlling page and a monitoring page [(e.g. see Aluvala paragraphs 0040, 0053, 0065, 0066) ”at stage 250, the user device 110 can present a GUI for selecting the virtual machines 140 to load at the terminal 120 … The user can select one or more of the virtual machines 140 for loading at the terminal 120 … At stage 280, the virtual machine server 242 can send the virtual machine data to the VM player 122. This allows the VM player 122 to display the virtual machine 140 at stage 285. The virtual machine data can be the complete virtual machine 140 in one example. The virtual machine 140 can be loaded by the VM player 122 or other application and executed on the terminal 120. Alternatively, the virtual machine data can include an application for executing locally and graphics information. As yet another alternative, the virtual machine data can include graphics information, such as pixels, vectors, or frames … As explained with regard to FIG. 1, the virtual machine 140 can buffer graphics information in a frame buffer and send the frames to the VM player 122 for display … the virtual machine 140 can execute remotely from the user device 110 and supply graphics frames as they are generated on a virtual machine server. This can allow the virtual machines 140 to be platform agnostic with regard to the user device 110 or terminal 120”]. Examiner notes the use of “at least one of” language. Examiner further notes that, as described by applicant’s specification at paragraph 0052, “stream-pushing” can be interface content sent from one platform to another.
As for dependent claim 2, Aluvala discloses the method as described in claim 1 and Aluvala further discloses:
wherein the displaying the operation and maintenance page of the first platform on the interface of the terminal device in response to the selection operation of the user on the platform identifier of the first platform, comprises: sending an acquisition request for the operation and maintenance page of the first platform to a second platform in response to the selection operation of the user on the platform identifier of the first platform [(e.g. see Aluvala paragraph 0056) ”At stage 260, the terminal 120 can then request the user's profile 132 by authenticating at the management server 130 using the SAML token. The management server 130 can validate the user based on the SAML token and locate the corresponding profile(s) 132. In one example, if the terminal 120 identifies selected virtual machines 140, the management server 130 can determine whether the terminal 120 has the security and technical attributes needed to launch the identified virtual machines 140. The management server 130 can further validate that the identified virtual machines 140 are associated with the user”].
acquiring a configuration data sent by the second platform according to the acquisition request for the operation and maintenance page [(e.g. see Aluvala paragraph 0059) ”At stage 265, the management server 130 can send the profile(s) 132 to the terminal 120 for use in configuring the virtual machine(s) 140. The terminal 120 can then implement the user's settings, files, and other configurations so that using the virtual machines 140 is a consistent experience between the terminal 120 and the user device 110. The management server 130 can send some or all of the profiles 132 associated with the user to the terminal 120. In one example, the profiles 132 sent to the terminal 120 are based on which virtual machines 140 the terminal 120 will load. In one example, the profiles 132 can configure the user's desktop at the terminal 120”].
displaying the operation and maintenance page of the first platform on the interface of the terminal device according to the configuration data [(e.g. see Aluvala paragraphs 0061, 0063) ”the terminal 120 can launch a VM player 122 for viewing the selected virtual machines 140. This can include providing the VM player 122 with access to the SAML token, configuration information from the profile 132, and the virtual machine information 134 … The virtual machine 140 can host a guest application that is configured based on the profile 132. For example, the profile 132 can specify what functionality is available within the guest application, such as which file repositories the guest application can access. The profile 132 can also set the guest application to reflect user preferences. For example, default repositories for storing a file can be adjusted. Recent document and bookmark lists can be populated. By supplying this sort of user information, the profile 132 can allow the guest application to present a consistent work environment each time the user uses the virtual machine 140”].
As for dependent claim 6, Aluvala discloses the method as described in claim 1 and Aluvala further discloses:
wherein the operation and maintenance page further comprises at least one controlling component, and the controlling component comprises at least one of the following components: a page size adjustment component, a volume adjustment component, a page direction adjustment component, a notification bar controlling component, a stream-pushing data schedule adjustment component, a menu page controlling component, a screen recording component, a screen capture controlling component and a page switching component [(e.g. see Aluvala paragraph 0042) ”The frames in the frame buffer can be sized to match a window or screen size of the VM player 122 executing on the user device 110 or terminal 120. In another example, the frame size is a fixed size that is set to fill the screen of the user device 110 or terminal 120. Information regarding the frame size corresponding to a user device 110 or terminal 120 can be maintained at the management server 130. In still another example, the frame size can be changed based on user interface (“UI”) action events generated at the VM player 122 when the user resizes the VM player 122 window”].
wherein the information display method further comprises: adjusting the stream-pushing page according to a triggering operation of the user on the controlling component or adjusting stream-pushing data in the stream-pushing page according to the triggering operation in response to the triggering operation [(e.g. see Aluvala paragraph 0042) ”The frames in the frame buffer can be sized to match a window or screen size of the VM player 122 executing on the user device 110 or terminal 120. In another example, the frame size is a fixed size that is set to fill the screen of the user device 110 or terminal 120. Information regarding the frame size corresponding to a user device 110 or terminal 120 can be maintained at the management server 130. In still another example, the frame size can be changed based on user interface (“UI”) action events generated at the VM player 122 when the user resizes the VM player 122 window”].
As for dependent claim 7, Aluvala discloses the method as described in claim 6 and Aluvala further discloses:
wherein the adjusting the stream-pushing page according to the triggering operation of the user on the controlling component or adjusting the stream-pushing data in the stream-pushing page according to the triggering operation in response to the triggering operation, comprises: sending controlling information corresponding to the controlling component to a second platform in response to the triggering operation of the user on the controlling component, wherein the controlling information is used to instruct to adjust the stream-pushing page on the second platform and/or instruct to adjust the stream-pushing data in the stream-pushing page on the second platform [(e.g. see Aluvala paragraphs 0042, 0044) ”As the VM player 122 displays the graphics information locally at the user device 110 or terminal 120, the VM player 122 can listen for UI events. UI events can include mouse movements, typing, clicking, touch screen events, or any user input within the VM player 122. Capturing UI events can include tracking a UI event type. Additionally, in one example the VM player 122 can capture timing information and location information, such as coordinates, related to the UI event. The VM player 122 can send information associated with the UI events to the virtual machine 140, which in turn can perform corresponding events … The frames in the frame buffer can be sized to match a window or screen size of the VM player 122 executing on the user device 110 or terminal 120. In another example, the frame size is a fixed size that is set to fill the screen of the user device 110 or terminal 120. Information regarding the frame size corresponding to a user device 110 or terminal 120 can be maintained at the management server 130. In still another example, the frame size can be changed based on user interface (“UI”) action events generated at the VM player 122 when the user resizes the VM player 122 window”].
displaying an adjusted stream-pushing page on the terminal device, and/or displaying an adjusted stream-pushing data on the terminal device [(e.g. see Aluvala paragraph 0042) ”The frames in the frame buffer can be sized to match a window or screen size of the VM player 122 executing on the user device 110 or terminal 120. In another example, the frame size is a fixed size that is set to fill the screen of the user device 110 or terminal 120. Information regarding the frame size corresponding to a user device 110 or terminal 120 can be maintained at the management server 130. In still another example, the frame size can be changed based on user interface (“UI”) action events generated at the VM player 122 when the user resizes the VM player 122 window”].
As for dependent claim 8, Aluvala discloses the method as described in claim 1 and Aluvala further discloses:
further comprising: displaying a configuration page of the first platform on the terminal device, wherein the configuration page comprises multiple configuration components, and the configuration components comprise at least one of the following: a size of the operation and maintenance page, a resolution of the operation and maintenance page and a pattern of the operation and maintenance page [(e.g. see Aluvala paragraphs 0042, 0080) ”This can cause the virtual machine 140 to display the user's identity, or use or display favorites and recent files of the user. It can also cause the virtual machine 140 to arrange a menu or task bar in accordance with a configuration previously saved by the user … the frame size can be changed based on user interface (“UI”) action events generated at the VM player 122 when the user resizes the VM player 122 window”].
configuring an operation and maintenance page to be configured according to a triggering operation of the user on the configuration components in response to the triggering operation [(e.g. see Aluvala paragraph 0044) ”As the VM player 122 displays the graphics information locally at the user device 110 or terminal 120, the VM player 122 can listen for UI events. UI events can include mouse movements, typing, clicking, touch screen events, or any user input within the VM player 122. Capturing UI events can include tracking a UI event type. Additionally, in one example the VM player 122 can capture timing information and location information, such as coordinates, related to the UI event. The VM player 122 can send information associated with the UI events to the virtual machine 140, which in turn can perform corresponding events”].
determining that a current operation and maintenance page to be configured is the operation and maintenance page of the first platform in response to a configuration completion operation of the user [(e.g. see Aluvala paragraph 0042) ”The frames in the frame buffer can be sized to match a window or screen size of the VM player 122 executing on the user device 110 or terminal 120. In another example, the frame size is a fixed size that is set to fill the screen of the user device 110 or terminal 120. Information regarding the frame size corresponding to a user device 110 or terminal 120 can be maintained at the management server 130. In still another example, the frame size can be changed based on user interface (“UI”) action events generated at the VM player 122 when the user resizes the VM player 122 window”].
displaying the operation and maintenance page of the first platform on the interface of the terminal device [(e.g. see Aluvala paragraph 0042) ”The frames in the frame buffer can be sized to match a window or screen size of the VM player 122 executing on the user device 110 or terminal 120. In another example, the frame size is a fixed size that is set to fill the screen of the user device 110 or terminal 120. Information regarding the frame size corresponding to a user device 110 or terminal 120 can be maintained at the management server 130. In still another example, the frame size can be changed based on user interface (“UI”) action events generated at the VM player 122 when the user resizes the VM player 122 window”].
As for dependent claim 9, Aluvala discloses the method as described in claim 8 and Aluvala further discloses:
wherein the configuring the operation and maintenance page to be configured according to the triggering operation of the user on the configuration components in response to the triggering operation, comprises: sending configuration information corresponding to the triggering operation to a second platform in response to the triggering operation of the user on the configuration components, wherein the configuration information is used to instruct the first platform to configure the operation and maintenance page [(e.g. see Aluvala paragraph 0011, 0023) ”The user can set up their virtual machines with specific configurations. The profile information and virtual machine information identifying the virtual machines and configurations are then stored at a management server. The user can then access the virtual machines based on receiving the profile and virtual machine information from the management server … A management server can track profiles that correspond to different users or enrolled user devices, such as cell phones, tablets, or laptops. A profile can include configurations for one or more virtual machines that can execute for display at the user device”].
receiving an operation and maintenance page to be configured corresponding to a current triggering operation [(e.g. see Aluvala paragraph 0059) ”At stage 265, the management server 130 can send the profile(s) 132 to the terminal 120 for use in configuring the virtual machine(s) 140. The terminal 120 can then implement the user's settings, files, and other configurations so that using the virtual machines 140 is a consistent experience between the terminal 120 and the user device 110. The management server 130 can send some or all of the profiles 132 associated with the user to the terminal 120. In one example, the profiles 132 sent to the terminal 120 are based on which virtual machines 140 the terminal 120 will load. In one example, the profiles 132 can configure the user's desktop at the terminal 120”].
As for independent claim 12, Aluvala discloses a method comprising:
sending a platform list to a terminal device, wherein the platform list comprises a platform identifier corresponding to at least one platform [(e.g. see Aluvala paragraphs 0036, 0053) ”The management server 130 can provide a list of available terminals 120 to the user device 110 … he GUI can list the virtual machines 140 currently associated with the user. These virtual machines 140 are identified in the virtual machine information 134 received from the management server 130 in an example”].
receiving an acquisition request for an operation and maintenance page of a first platform sent by the terminal device [(e.g. see Aluvala paragraph 0056) ”At stage 260, the terminal 120 can then request the user's profile 132 by authenticating at the management server 130 using the SAML token. The management server 130 can validate the user based on the SAML token and locate the corresponding profile(s) 132. In one example, if the terminal 120 identifies selected virtual machines 140, the management server 130 can determine whether the terminal 120 has the security and technical attributes needed to launch the identified virtual machines 140. The management server 130 can further validate that the identified virtual machines 140 are associated with the user”].
acquiring the operation and maintenance page corresponding to the first platform according to the acquisition request for the operation and maintenance page, and sending the operation and maintenance page corresponding to the first platform to the terminal device, wherein the operation and maintenance page comprises at least one of a stream-pushing page, a controlling page and a monitoring page [(e.g. see Aluvala paragraph 0065) ”At stage 280, the virtual machine server 242 can send the virtual machine data to the VM player 122. This allows the VM player 122 to display the virtual machine 140 at stage 285. The virtual machine data can be the complete virtual machine 140 in one example. The virtual machine 140 can be loaded by the VM player 122 or other application and executed on the terminal 120. Alternatively, the virtual machine data can include an application for executing locally and graphics information. As yet another alternative, the virtual machine data can include graphics information, such as pixels, vectors, or frames”]. Examiner notes the use of “at least one of” language. Examiner further notes that, as described by applicant’s specification at paragraph 0052, “stream-pushing” can be interface content sent from one platform to another.
As for dependent claim 13, Aluvala discloses the method as described in claim 12 and Aluvala further discloses:
wherein the sending the operation and maintenance page corresponding to the first platform to the terminal device according to the acquisition request for the operation and maintenance page, comprises: acquiring configuration data of the first platform according to the acquisition request for the operation and maintenance page [(e.g. see Aluvala paragraph 0011, 0023) ”The user can set up their virtual machines with specific configurations. The profile information and virtual machine information identifying the virtual machines and configurations are then stored at a management server. The user can then access the virtual machines based on receiving the profile and virtual machine information from the management server … A management server can track profiles that correspond to different users or enrolled user devices, such as cell phones, tablets, or laptops. A profile can include configurations for one or more virtual machines that can execute for display at the user device”].
sending the configuration data to the terminal device, wherein the configuration data is used for displaying the operation and maintenance page of the first platform on an interface of the terminal device [(e.g. see Aluvala paragraph 0059) ”At stage 265, the management server 130 can send the profile(s) 132 to the terminal 120 for use in configuring the virtual machine(s) 140. The terminal 120 can then implement the user's settings, files, and other configurations so that using the virtual machines 140 is a consistent experience between the terminal 120 and the user device 110. The management server 130 can send some or all of the profiles 132 associated with the user to the terminal 120. In one example, the profiles 132 sent to the terminal 120 are based on which virtual machines 140 the terminal 120 will load. In one example, the profiles 132 can configure the user's desktop at the terminal 120”].
As for dependent claim 14, Aluvala discloses the method as described in claim 12 and Aluvala further discloses:
further comprising: acquiring an acquisition request for stream-pushing data sent by the terminal device [(e.g. see Aluvala paragraph 0056) ”At stage 260, the terminal 120 can then request the user's profile 132 by authenticating at the management server 130”].
sending a data channel information and a security credential to the terminal device and the first platform according to the acquisition request for the stream-pushing data [(e.g. see Aluvala paragraph 0056) ”The management server 130 can validate the user based on the SAML token and locate the corresponding profile(s) 132. In one example, if the terminal 120 identifies selected virtual machines 140, the management server 130 can determine whether the terminal 120 has the security and technical attributes needed to launch the identified virtual machines 140. The management server 130 can further validate that the identified virtual machines 140 are associated with the user”].
wherein the data channel information and the security credential are used for the terminal device and the first platform to enter a data channel corresponding to the data channel information, and the data channel is used for the terminal device to acquire stream-pushing data sent by the first platform, and the stream-pushing data comprises at least one of the following: an audio data and/or a video data [(e.g. see Aluvala paragraphs 0061, 0064) ”the terminal 120 can launch a VM player 122 for viewing the selected virtual machines 140. This can include providing the VM player 122 with access to the SAML token, configuration information from the profile 132, and the virtual machine information 134 … the VM player 122 uses the SAML token to authenticate with the virtual machine. After authentication, the virtual machine sends virtual machine data, such as graphics, to the VM player 122. This can allow the virtual machine 140 to send the virtual machine data to the correct device between the user device 110 and the terminal 120”].
As for dependent claim 15, Aluvala discloses the method as described in claim 12 and Aluvala further discloses:
before the sending the platform list to the terminal device, further comprising: sending a configuration page of the first platform to the terminal device, wherein the configuration page comprises multiple configuration components, and the configuration components comprise at least one of the following: a size of the operation and maintenance page, a resolution of the operation and maintenance page and a pattern of the operation and maintenance page [(e.g. see Aluvala paragraph 0011, 0023, 0042) ”The user can set up their virtual machines with specific configurations. The profile information and virtual machine information identifying the virtual machines and configurations are then stored at a management server. The user can then access the virtual machines based on receiving the profile and virtual machine information from the management server … A management server can track profiles that correspond to different users or enrolled user devices, such as cell phones, tablets, or laptops. A profile can include configurations for one or more virtual machines that can execute for display at the user device … the frame size is a fixed size that is set to fill the screen of the user device 110 or terminal 120. Information regarding the frame size corresponding to a user device 110 or terminal 120 can be maintained at the management server 130”].
receiving configuration information corresponding to a current triggering operation sent by the terminal device [(e.g. see Aluvala paragraphs 0042, 0044) ”the frame size can be changed based on user interface (“UI”) action events generated at the VM player 122 when the user resizes the VM player 122 window … As the VM player 122 displays the graphics information locally at the user device 110 or terminal 120, the VM player 122 can listen for UI events. UI events can include mouse movements, typing, clicking, touch screen events, or any user input within the VM player 122. Capturing UI events can include tracking a UI event type. Additionally, in one example the VM player 122 can capture timing information and location information, such as coordinates, related to the UI event. The VM player 122 can send information associated with the UI events to the virtual machine 140, which in turn can perform corresponding events”].
sending the configuration information to the first platform, wherein the configuration information is used to instruct the first platform to configure the operation and maintenance page according to the configuration information [(e.g. see Aluvala paragraph 0059) ”At stage 265, the management server 130 can send the profile(s) 132 to the terminal 120 for use in configuring the virtual machine(s) 140. The terminal 120 can then implement the user's settings, files, and other configurations so that using the virtual machines 140 is a consistent experience between the terminal 120 and the user device 110. The management server 130 can send some or all of the profiles 132 associated with the user to the terminal 120. In one example, the profiles 132 sent to the terminal 120 are based on which virtual machines 140 the terminal 120 will load. In one example, the profiles 132 can configure the user's desktop at the terminal 120”].
As for independent claim 17, Aluvala discloses an apparatus. Claim 17 discloses substantially the same limitations as claim 1. Therefore, it is rejected with the same rational as claim 1.
As for dependent claim 18, Aluvala discloses an apparatus comprising at least one processor and memory; wherein the memory has a computer-executable instruction stored therein; and the at least one processor executed the computer-executed instruction stored in the memory to enable the at least one processor to perform the information display method according to claim 12; further, claim 18 discloses substantially the same limitations as claim 12. Therefore, it is rejected with the same rational as claim 12.
As for dependent claim 20, Aluvala discloses a non-transitory computer-readable storage medium in which a computer-executable instruction is stored, wherein when the computer-executable instruction is executed by a processor, the information display method according to claim 1 is implemented; further, claim 20 discloses substantially the same limitations as claim 1. Therefore, it is rejected with the same rational as claim 1.
As for dependent claim 23, Aluvala discloses the apparatus as described in claim 17; further, claim 23 discloses substantially the same limitations as claim 2. Therefore, it is rejected with the same rational as claim 2.
Claim Rejections - 35 USC § 103
This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention.
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
Claims 3-5 are rejected under 35 U.S.C. 103 as being unpatentable over Aluvala et al. (US 2017/0339142 A1) in view of Koushik et al. (US 2016/0132214 A1) and further in view of Botzer (US 2015/0106728 A1).
As for dependent claim 3, Aluvala teaches the method as described in claim 1 and Aluvala further teaches:
further comprising: displaying stream-pushing data in the stream-pushing page when the operation and maintenance page comprises the stream-pushing page, wherein the stream-pushing data comprises audio data and/or video data [(e.g. see Aluvala paragraphs 0065, 0066) ”the virtual machine server 242 can send the virtual machine data to the VM player 122. This allows the VM player 122 to display the virtual machine 140 at stage 285. The virtual machine data can be the complete virtual machine 140 in one example. The virtual machine 140 can be loaded by the VM player 122 or other application and executed on the terminal 120. Alternatively, the virtual machine data can include an application for executing locally and graphics information. As yet another alternative, the virtual machine data can include graphics information, such as pixels, vectors, or frames … the virtual machine 140 can buffer graphics information in a frame buffer and send the frames to the VM player 122 for display”].
Aluvala does not specifically teach displaying service information of the first platform on the controlling page when the operation and maintenance page comprises the controlling page, wherein the service information comprises at least one of an application list, a controlling portal and file management. However, in the same field of invention or solving similar problems, Koushik teaches:
displaying service information of the first platform on the controlling page when the operation and maintenance page comprises the controlling page, wherein the service information comprises at least one of an application list, a controlling portal and file management [(e.g. see Koushik paragraph 0074 and Fig. 5A) ”an end user has chosen to view applications that are assigned to the end user or are part of a catalog of applications made available to the end user and/or one or more other end users by an IT administrator in the same business, enterprise, or organization (“my desktop applications”). In response to this selection, a list of applications is presented to the end user. In this example, the list of applications indicates, for each application, an application name, the vendor from which the application is sourced, and an available action that can be taken for the application (e.g., “install”, for an application that is not currently installed on the end user's computing resource instance, or “uninstall”, for some of the applications that are currently installed on the end user's computing resource instance)”].
Therefore, considering the teachings of Aluvala and Koushik, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to add displaying service information of the first platform on the controlling page when the operation and maintenance page comprises the controlling page, wherein the service information comprises at least one of an application list, a controlling portal and file management, as taught by Koushik, to the teachings of Aluvala because it allows applications to be deployed on-demand and at scale while maintaining centralized control, security and compliance from an easy-to use management console which improves efficiency (e.g. see Koushik paragraph 0238).
Aluvala and Koushik do not specifically teach displaying operation data of the first platform in the monitoring page when the operation and maintenance page comprises the monitoring page. However, in the same field of invention or solving similar problems, Botzer teaches:
displaying operation data of the first platform in the monitoring page when the operation and maintenance page comprises the monitoring page [(e.g. see Botzer paragraphs 0018, 0020 and Fig. 4) ”the remote dashboard console 104 includes a remote dashboard client interface 105 that allows a user (e.g., a user 101 such as an administrator permitted to access, manage, monitor, etc. the remote device 120 in the computing environment 100, a remote device user 130, etc.) to execute and run one or more remote device applications 126 (e.g., applications existing on the remote device 120) … The performance tracking applications ("remote dashboard performance trackers") may include any application for tracking, monitoring, measuring, viewing, etc. information associated with the performance of the remote device 120. For example, the remote dashboard performance trackers may include software for collecting performance statistics, trends, and/or metrics (e.g., information relating to CPU usage, memory usage, network information, applications, processes, storage (I/O), connection status, resources, events, logs, input/output device information, and/or location information associated with the remote device 120) for display to the user 101 as a gauge or other visualization via the remote dashboard client interface 105”].
Therefore, considering the teachings of Aluvala, Koushik and Botzer, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to add displaying operation data of the first platform in the monitoring page when the operation and maintenance page comprises the monitoring page, as taught by Botzer, to the teachings of Aluvala and Koushik because it allows a user to efficiently manage a remote device (e.g. see Botzer paragraph 0033).
As for dependent claim 4, Aluvala, Koushik and Botzer teach the method as described in claim 3 and Aluvala further teaches:
wherein the displaying the stream-pushing data in the stream-pushing page when the operation and maintenance page comprises the stream-pushing page, comprises: displaying the stream-pushing data on the stream-pushing page in response to a triggering operation of the user to acquire the stream-pushing data at the terminal device [(e.g. see Aluvala paragraphs 0065, 0075) ”the virtual machines 324 can be selected with radio buttons or other selection mechanisms. After the user has picked one or more of the virtual machines 324, the user can select a button 330 to load the virtual machines 324 at the terminal 120 … At stage 280, the virtual machine server 242 can send the virtual machine data to the VM player 122. This allows the VM player 122 to display the virtual machine 140 at stage 285. The virtual machine data can be the complete virtual machine 140 in one example. The virtual machine 140 can be loaded by the VM player 122 or other application and executed on the terminal 120. Alternatively, the virtual machine data can include an application for executing locally and graphics information. As yet another alternative, the virtual machine data can include graphics information, such as pixels, vectors, or frames.”].
As for dependent claim 5, Aluvala, Koushik and Botzer teach the method as described in claim 4 and Aluvala further teaches:
wherein the displaying the stream-pushing data on the stream-pushing page in response to the triggering operation of the user to acquire the stream-pushing data at the terminal device comprises: sending an acquisition request for the stream-pushing data to a second platform in response to the triggering operation of the user to acquire the stream-pushing data at the terminal device [(e.g. see Aluvala paragraph 0054) ”at stage 255 the user device 110 can send the SAML token and the virtual machine information 134 corresponding to the selected virtual machines 140 to the terminal 120. The virtual machine information 134 sent to the terminal 120 can be a subset of the total virtual machine information 134 at the user device 110, based on which virtual machines 140 the user selects to load at the terminal 120. If the user selects only one virtual machine 140, then the user device 110 sends the virtual machine information 134 that corresponds to that selected virtual machine 140”].
acquiring data channel information and a security credential sent by the second platform according to the acquisition request for the stream-pushing data [(e.g. see Aluvala paragraph 0056) ”At stage 260, the terminal 120 can then request the user's profile 132 by authenticating at the management server 130 using the SAML token. The management server 130 can validate the user based on the SAML token and locate the corresponding profile(s) 132. In one example, if the terminal 120 identifies selected virtual machines 140, the management server 130 can determine whether the terminal 120 has the security and technical attributes needed to launch the identified virtual machines 140. The management server 130 can further validate that the identified virtual machines 140 are associated with the user”].
joining a data channel corresponding to the data channel information according to the data channel information and the security credential; and acquiring stream-pushing data sent by the first platform through the data channel, and displaying the stream-pushing data on the stream-pushing page [(e.g. see Aluvala paragraphs 0061, 0064) ”the terminal 120 can launch a VM player 122 for viewing the selected virtual machines 140. This can include providing the VM player 122 with access to the SAML token, configuration information from the profile 132, and the virtual machine information 134 … the VM player 122 uses the SAML token to authenticate with the virtual machine. After authentication, the virtual machine sends virtual machine data, such as graphics, to the VM player 122. This can allow the virtual machine 140 to send the virtual machine data to the correct device between the user device 110 and the terminal 120”].
Claims 10, 11 and 16 are rejected under 35 U.S.C. 103 as being unpatentable over Aluvala et al. (US 2017/0339142 A1) in view of Koushik et al. (US 2016/0132214 A1).
As for dependent claim 10, Aluvala teaches the method as described in claim 1, but does not specifically teach further comprising: displaying an application program management page on the interface of the terminal device in response to a triggering operation of the user for an application program management in the terminal device, displaying an identifier corresponding to an application program to be processed in the operation and maintenance page or deleting the identifier corresponding to the application program to be processed in the operation and maintenance page in response to a controlling operation of the user on the application program to be processed or wherein the controlling operation comprises an installation operation or an uninstallation operation. However, in the same field of invention or solving similar problems, Koushik teaches:
further comprising: displaying an application program management page on the interface of the terminal device in response to a triggering operation of the user for an application program management in the terminal device [(e.g. see Koushik paragraph 0074) ”FIG. 5A. In this example, an end user has chosen to view applications that are assigned to the end user or are part of a catalog of applications made available to the end user and/or one or more other end users by an IT administrator in the same business, enterprise, or organization … In response to this selection, a list of applications is presented to the end user.”].
displaying an identifier corresponding to an application program to be processed in the operation and maintenance page or deleting the identifier corresponding to the application program to be processed in the operation and maintenance page in response to a controlling operation of the user on the application program to be processed [(e.g. see Koushik paragraph 0074 and Fig. 5A) ”In this example, the list of applications indicates, for each application, an application name, the vendor from which the application is sourced, and an available action that can be taken for the application (e.g., “install”, for an application that is not currently installed on the end user's computing resource instance, or “uninstall”, for some of the applications that are currently installed on the end user's computing resource instance)”].
wherein the controlling operation comprises an installation operation or an uninstallation operation [(e.g. see Koushik paragraph 0074 and Fig. 5A) ”In this example, the list of applications indicates, for each application, an application name, the vendor from which the application is sourced, and an available action that can be taken for the application (e.g., “install”, for an application that is not currently installed on the end user's computing resource instance, or “uninstall”, for some of the applications that are currently installed on the end user's computing resource instance)”].
Therefore, considering the teachings of Aluvala and Koushik, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to add further comprising: displaying an application program management page on the interface of the terminal device in response to a triggering operation of the user for an application program management in the terminal device, displaying an identifier corresponding to an application program to be processed in the operation and maintenance page or deleting the identifier corresponding to the application program to be processed in the operation and maintenance page in response to a controlling operation of the user on the application program to be processed and wherein the controlling operation comprises an installation operation or an uninstallation operation, as taught by Koushik, to the teachings of Aluvala because it allows applications to be deployed on-demand and at scale while maintaining centralized control, security and compliance from an easy-to use management console which improves efficiency (e.g. see Koushik paragraph 0238).
As for dependent claim 11, Aluvala and Koushik teach the method as described in claim 10, but Aluvala does not specifically teach the following limitations. However, Koushik teaches:
wherein the displaying the identifier corresponding to the application program to be processed in the operation and maintenance page or deleting the identifier corresponding to the application program to be processed in the operation and maintenance page in response to the controlling operation of the user on the application to be processed, comprises: sending controlling data to a second platform in response to the controlling operation of the user on the application program to be processed, wherein the controlling data is used to instruct to install the application program to be processed in the first platform or to instruct to uninstall the application program to be processed in the first platform [(e.g. see Koushik paragraph 0073) ”an application (which is sometimes referred to herein as a desktop application management module) may be installed on an end user's machine or on a virtual desktop instance that provides an interface to virtualized desktop applications delivered from an application fulfillment platform. In some embodiments, this application may also provide an interface through which applications that are (or can be) physically installed on the end user's machine may be installed or launched. For example, after launching the desktop application management module (e.g., by selecting an icon or shortcut on the desktop or on a virtual desktop), an end user may, through a graphical user interface of the desktop application management module, log into the desktop application management module using their identity, view a list of applications that are available for their use (e.g., applications that they have permission to purchase, lease or subscribe to, install, and/or execute) or that may be made available for their use (e.g., applications for which they may be able to request permission to purchase, lease or subscribe to, install, and/or execute) and select on option to purchase, lease or subscribe to, install, and/or execute one of the listed applications”].
displaying an identifier corresponding to the application program to be processed in the operation and maintenance page if the controlling operation is the installation operation [(e.g. see Koushik paragraph 0074 and Fig. 5A) ”In this example, the list of applications indicates, for each application, an application name, the vendor from which the application is sourced, and an available action that can be taken for the application (e.g., “install”, for an application that is not currently installed on the end user's computing resource instance, or “uninstall”, for some of the applications that are currently installed on the end user's computing resource instance)”].
deleting the identifier corresponding to the application program to be processed in the operation and maintenance page if the controlling operation is the uninstall operation [(e.g. see Koushik paragraph 0074 and Fig. 5A) ”In this example, the list of applications indicates, for each application, an application name, the vendor from which the application is sourced, and an available action that can be taken for the application (e.g., “install”, for an application that is not currently installed on the end user's computing resource instance, or “uninstall”, for some of the applications that are currently installed on the end user's computing resource instance)”].
The motivation to combine is the same as that used for claim 10.
As for dependent claim 16, Aluvala teaches the method as described in claim 12, but does not specifically teach the following limitations. However, Koushik teaches:
further comprising: receiving controlling information corresponding to a triggering operation for an application program management sent by the terminal device [(e.g. see Koushik paragraph 0074) ”an end user has chosen to view applications that are assigned to the end user or are part of a catalog of applications made available to the end user and/or one or more other end users by an IT administrator in the same business, enterprise, or organization”].
sending an application program management page to the terminal device, wherein the application program management page is used for the terminal device to manage an application program to be processed [(e.g. see Koushik paragraph 0073) ”In response to this selection, a list of applications is presented to the end user. In this example, the list of applications indicates, for each application, an application name, the vendor from which the application is sourced, and an available action that can be taken for the application”].
receiving controlling data corresponding to a controlling operation sent by the terminal device [(e.g. see Koushik paragraph 0073) ”an end user may, through a graphical user interface of the desktop application management module, log into the desktop application management module using their identity, view a list of applications that are available for their use (e.g., applications that they have permission to purchase, lease or subscribe to, install, and/or execute) or that may be made available for their use (e.g., applications for which they may be able to request permission to purchase, lease or subscribe to, install, and/or execute) and select on option to purchase, lease or subscribe to, install, and/or execute one of the listed applications”].
installing the application program to be processed in the first platform or uninstalling the application program to be processed in the first platform according to the controlling data [(e.g. see Koushik paragraph 0073, 0074) ”the list of applications indicates, for each application, an application name, the vendor from which the application is sourced, and an available action that can be taken for the application (e.g., “install”, for an application that is not currently installed on the end user's computing resource instance, or “uninstall”, for some of the applications that are currently installed on the end user's computing resource instance) … an application (which is sometimes referred to herein as a desktop application management module) may be installed on an end user's machine or on a virtual desktop instance that provides an interface to virtualized desktop applications delivered from an application fulfillment platform. In some embodiments, this application may also provide an interface through which applications that are (or can be) physically installed on the end user's machine may be installed or launched. For example, after launching the desktop application management module (e.g., by selecting an icon or shortcut on the desktop or on a virtual desktop), an end user may, through a graphical user interface of the desktop application management module, log into the desktop application management module using their identity, view a list of applications that are available for their use (e.g., applications that they have permission to purchase, lease or subscribe to, install, and/or execute) or that may be made available for their use (e.g., applications for which they may be able to request permission to purchase, lease or subscribe to, install, and/or execute) and select on option to purchase, lease or subscribe to, install, and/or execute one of the listed applications”].
The motivation to combine is the same as that used for claim 10.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
U.S. PGPub 2016/0188170 A1 issued to Miao et al. on 30 June 2016. The subject matter disclosed therein is pertinent to that of claims 1-18, 20 and 23 (e.g. connecting remote host devices to particular areas of a display).
U.S. Patent 11,734,032 B1 issued to Brinkhoff et al. on 22 August 2023. The subject matter disclosed therein is pertinent to that of claims 1-18, 20 and 23 (e.g. virtual desktop switcher menu).
Contact Information
Any inquiry concerning this communication or earlier communications from the examiner should be directed to CHRISTOPHER J FIBBI whose telephone number is (571)-270-3358. The examiner can normally be reached Monday - Thursday (8am-6pm).
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, William Bashore can be reached at (571)-272-4088. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/CHRISTOPHER J FIBBI/Primary Examiner, Art Unit 2174