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 .
DETAILED ACTION
Status of Claims
Claims 1-24 are subject to examination.
Claim Rejections - 35 USC § 112
The following is a quotation of the first paragraph of 35 U.S.C. 112(a):
(a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention.
The following is a quotation of the first paragraph of pre-AIA 35 U.S.C. 112:
The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor of carrying out his invention.
Claims 1-24 are rejected under 35 U.S.C. 112(a) or 35 U.S.C. 112 (pre-AIA ), first paragraph, as failing to comply with the written description requirement. The claim(s) contains subject matter which was not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor, or for applications subject to pre-AIA 35 U.S.C. 112, the inventor(s), at the time the application was filed, had possession of the claimed invention.
Claim 1 is amended as following:
PNG
media_image1.png
646
846
media_image1.png
Greyscale
Amended claim 1 contains,
determining, based on a device identifier associated with the user device determined via the first communication session, a second network identifier of a second network and one or more security parameters, the second network identifier and the one or more security parameters having been associated with the user device prior to establishment of the first communication session; and based on the determination of the second network identifier of the second network associated with the user device prior to establishment of the first communication session and the one or more security parameters, broadcasting, by the network device, the second network identifier of the second network
.
Applicant’s below remarks are noted.
Paragraph 3 explains
that "[s]ome methods and systems described herein, in one aspect, can determine the security
associated with a device and a first network, and can automatically provide that security to the
device in a second network." Paragraph 32 explains that "a user device can connect to the open
network, a computing device (e.g., gateway device, computing device, server, router, etc.) can
recognize the user device and the computing device can retrieve a second identifier associated with
a secure network and the user device," where "the second identifier can be a second SSID," and
"[t]he computing device can transmit the second identifier associated with the secure network to
the user device." Paragraph 45 describes a mapping object generated when the user device
connects to a first network: "a MAC address associated with the user device 102 can be mapped
to an IP address that is associated with the LAN (e.g., home network) to which the user device 102
is connected." Subsequently, "when the user device 102 associates (e.g., connects) with a second
network, the second network device can check a device identifier (e.g., MAC address) associated
with the user device 102 against one or more mapping objects (e.g., stored at database 114)." If
located, "the first SSID can be broadcast to the user device 102" and "communications
therebetween can be protected by the first set of security parameters."
Paragraph 66 describes a subscriber database in storage medium 313 managed by
computing device 310: "[t]he subscriber database can associate various parameters, such as, for
example, an account name, device identifier, e-mail address, e-mail password, identifiers (305,
306), passwords for identifiers (305, 306), and SSIDs 309 with a particular subscriber." Paragraph
66 further explains that "any information stored in a subscriber database associated with a
subscriber can be used as a security parameter" and "can be used to identify the subscriber and one
or more appropriate security parameters associated with the subscriber."
Paragraph 67 explains that computing device 310 communicates with network devices "for
mapping first identifiers 305 with corresponding second identifiers 306 in storage medium 313."
Paragraph 68 further explains that "storage medium 313 can store a plurality of data sets such as
mapping objects, first identifiers 305, second identifiers 306, third identifiers 308a, 308b, and/or
SSIDs 309 or other information," and that "computing device 310 can obtain the first identifier
305 from the gateway 304 and retrieve information from the storage medium 313 such as a
mapping of the first identifier 305 to the SSID 309 and/or the second identifier 306."
Paragraphs 70 and 71 provide a concrete network-device embodiment. Paragraph 70
explains that "user device 303 can establish a connection with network 315 through network device
302a, in response to network device 302a broadcasting SSID 309a," and that "[c]omputing device
310 can receive first identifier 305 associated with user device 303" and "retrieve the user or
subscriber information associated with first identifier 305, including SSID 309." Computing
device 310 then provides "network device 302a with SSID 309, so that network device 302a can
create/broadcast SSID 309 to user device 303 and require the same security parameters that are
used to connect to gateway 306 (e.g., password, etc. ...)." Paragraph 71 further explains that
"network device 302a can retrieve security parameters associated with a subscriber account
associated with first identifier 305" and that "[u]ser device 303 can establish a connection with
network device 302a using the SSID 309 utilizing the security parameters otherwise associated
with connecting to gateway 304 using SSID 309."
Paragraphs 75 and 77 describe the session sequence directly. Paragraph 75 explains that
"[t]he second network device can receive the first information from the user device, for example,
an identifier of the user device through the open connection," and that the second network device
"can transmit the first information to a computing device and request an SSID associated with the
first network device, and any associated security parameters." The "[c]omputing device can
determine the SSID associated with the first network device and the security parameters associated
with the first network device" and "can transmit the determined SSID and/or security parameters
to the second network device." Paragraph 77 then explains the result: "the user device connects to
the network device by using an SSID and security parameters that were previously configured for
the user device to connect to another network device."
Paragraphs 81 and 82 reinforce the same relationship in the Figure 10 embodiment. The
identifier is received through an open connection and mapped to stored network information that
can include an SSID and security parameters. The second network device retrieves that stored
information and uses it to create and broadcast an SSID originally associated with the first network
device, while the associated security parameters are used to secure the resulting connection.
Paragraphs 86 through 88 describe the Figure 11 embodiment. Paragraph 86 explains that
"[p]rior to connecting to the network device, the information associated with the user device can
already have been provided to the remote server," and the transmitted information includes
"security information and a third identifier" where "[t]he third identifier can be, for example, an
SSID associated with another network device with which the user device already has configured
security parameters (e.g., a home network device)." Paragraph 86 further states that "[t]he security
information and the third identifier can represent a preconfigured SSID and security parameters
used by the user device to connect to another network device (for example, a home network
device)." Paragraph 88 then confirms that "the user device connects to the network device by using
an SSID and security parameters that were previously configured for the user device to connect to
another network device."
Thus, the specification provides detailed support across multiple embodiments for a device
identifier obtained through an open or first communication session to be used to retrieve both a
second network identifier and security parameters from pre-existing associations with the user
device. Critically, these are not separate, unrelated operations. Paragraph 66 stores the SSID and
passwords together in the same subscriber record. Paragraph 86 describes the returned information
as a unit comprising "security information and a third identifier" where "[t]he security information
and the third identifier can represent a preconfigured SSID and security parameters used by the
user device to connect to another network device (for example, a home network device)." The
specification thus describes a single subscriber record from which both the network identifier and
security parameters are retrieved as a joint, pre-existing association. The disclosure distinguishes
the open first session from the prior configuration that supplies the stored SSID and security
information. This is the claimed relationship and reasonably conveys possession of the subject
matter as of the filing date.
However, as seen in the above remarks and the claims it do not contain combination of limitations, determining, based on a device identifier associated with the user device determined via the first communication session, a second network identifier of a second network and one or more security parameters, the second network identifier and the one or more security parameters having been associated with the user device prior to establishment of the first communication session; and based on the determination of the second network identifier of the second network associated with the user device prior to establishment of the first communication session and the one or more security parameters, broadcasting, by the network device, the second network identifier of the second network.
The specification does not limit what is limited to as “the second network identifier of the second network associated with the user device”. The specification does not disclose how the associated with the user device is done, what all is considered as an “associated”. The claimed “the second network identifier of the second network associated with the user device” is now includes all the associations that is beyond the specification / not supported by the specification.
As seen above, the remarks contains storing of information including the second network identifier, however, it is the stored information and not “the second network identifier of the second network associated with the user device (itself)”
As claimed,
based on establishment of the first communication session: determining, based on a device identifier associated with the user device determined via the first communication session, a second network identifier of a second network and one or more security parameters
Hence, the second network identifier of a second network and one or more security parameters are determined based on establishment of first communication session. This determining step is performed regardless.
As amended, the determining step must determine the second network identifier that has been associated with the user device prior to establishment of the first communication session and the security parameter, and then broadcasting the second network identifier is not implemented in the specification. As claimed, the determining step is subject to do the determination based on a device identifier and not based on a second device identifier.
Claims 8, and 17, claim similar limitations as of claim 1.
Claims 1-7, 9-16, 18-20 are dependent claims of claims 1, 8, 17 respectively, and hence subject to the same rejections.
Drawings
The figures submitted on the filing date of this application are noted.
Applicant’s remarks dated 4/1/24, 9/10/26, 12/20/24, Applicant respectfully submits that at least the combination of FIGs. 3, 5, and 7, along with the corresponding descriptions of each of those figures, show every feature of the invention specified in the claims. However, contrary to assertions, these figures do not show, “based on the determination of the second SSID associated with the second network previously associated with the user device, broadcasting, by the network device, the second SSID”, “broadcasting …” establishing … session …, broadcasting, by the network device, based on the network information, a second network identifier …; and establishing, based on the second network identifier, second communication session…
Applicant is reminded about figures 9-11, in which method steps of claims 1, 8, 17 do not exist, and rather contains unclaimed steps in the figures 9-11. Hence, figures 9-11 can be updated to show every feature of the invention specified in the claims.
Applicant’s remarks dated 9/19/23, Applicant respectfully submits that an express illustration of the steps of a method is not necessary for understanding by one of ordinary skill in the art of the subject matter to be patented; are noted. However, such mere arguments would not overcome the objections. The objections are based on the MPEP.
Applicant’s remarks dated 9/19/23, The Office Action is improperly interpreting the language of the Code as requiring all features of the invention to be contained in a single drawing; are noted. Applicant failed to provide a single drawing with the remarks dated 9/19/23, and rather provided there mere/incorrect statement, which do not compact the prosecution of this application.
Applicant’s remarks dated 8/7/24, Applicant respectfully submits that at least the combination of FIGs. 3, 5, and 7, along with the corresponding descriptions of each of those figures, show every feature of the invention specified in the claims. Accordingly, withdrawal of this objection is respectfully requested.
The drawings are objected to under 37 CFR 1.83(a). The drawings must show features of the invention specified in the claims. Therefore, components of the claims 1, 8, 17 must be shown or the feature(s) canceled from the claim(s). No new matter should be entered.
As seen in below figures 9-11, method steps of below claims 1, 8, 17 do not exist, rather unclaimed steps are presented in the figures 9-11. Replacement of unclaimed method steps of claims 1, 8, 17, with claimed method steps is suggested in the figures 9-11, in order to overcome the objections.
PNG
media_image2.png
485
404
media_image2.png
Greyscale
PNG
media_image3.png
658
421
media_image3.png
Greyscale
PNG
media_image4.png
771
296
media_image4.png
Greyscale
A proposed drawing correction or corrected drawings are required in reply to the Office action to avoid abandonment of the application. The amended replacement drawing sheet should include all of the figures appearing on the immediate prior version of the sheet, even if only one figure is being amended. The replacement sheet(s) should be labeled --Replacement Sheet-- in the page header (as per 37 CFR 1.84(c)) so as not to obstruct any portion of the drawing figures. If the examiner does not accept the changes, the applicant will be notified and informed of any required corrective action in the next Office action. The objection to the drawings will not be held in abeyance.
Applicant’s remarks dated 3/20/23 are noted. Regarding Applicant’s statements, “Applicant notes that, as outlined in MPEP 608.02 Drawing [R-07.2015], the statutory requirement for showing the claimed invention only requires that the “applicant shall furnish a drawing where necessary for the understanding of the subject matter to be patented...” (See 35 U.S.C. 113, See also 37 CFR §1.81(a), which states “t]he applicant for a patent is required to furnish a drawing of the invention where necessary for the understanding of the subject matter sought to be patented...”). In the pending application, Applicant respectfully submits that an express illustration of the steps of a method is not necessary for understanding by one of ordinary skill in the art of the subject matter to be patented. Accordingly, withdrawal of this objection is respectfully requested. Further, the Office Action limits its review of the drawings for Figures 9-11 and apparently ignores the remaining eleven figures. 37 C.F.R. § 1.83(a) requires the drawings “must show features of the invention.” The Office Action is improperly interpreting the language of the Code as requiring all features of the invention to be contained in a single drawing.”; the examiner respectfully disagrees. Applicant failed to mention that figures 9-11 belong to method steps that were claimed in the parent application that has been abandoned. Applicant is not required to present all features of the invention to be contained in a single drawing. Rather Applicant wants to keep the drawings for figures 9-11 method steps that do not belong to the claimed invention in this divisional application. Applicant fails to follow “t]he applicant for a patent is required to furnish a drawing of the invention where necessary for the understanding of the subject matter sought to be patented...”). One of ordinary skilled in the art, would readily know that figures 9-11 steps express illustration of the steps of a method that the applicant had claimed in the abandoned application and is not necessary for understanding of the subject matter that is not patented in the abandoned application. Rather, one of ordinary skilled in the art would readily know that the Applicant choose to provide the steps for the abandoned application and had considered to be necessary for understanding by one of ordinary skill in the art of the subject matter to be patented in the abandoned application. The Applicant is contrarily stating that the figures 9-11 should not reflect the claimed invention of this application, and rather continue to reflect the claimed invention of the abandoned application, even after filing a divisional application. Mere arguments would not overcome the objections.
Claim Rejections - 35 USC § 103
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
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 of this title, 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.
Claim(s) 1-6, 8-12, 14 is/are rejected under 35 U.S.C. 103 as being unpatentable over Kollu-Qualcomm 2016/0094662 in view of Lee KR 2014/0055857 A and Ramalingam et al., US 10038729 and CAI et al., WO 2013164032 A1.
Referring to claim 1, Kollu-Qualcomm substantially teaches a method comprising:
broadcasting, by a network device, a first network identifier of a first network (broadcast first SSID associated with LAN/WAN, etc., para 73, connection to accomplish data transfer, para 124); establishing, based on the first network identifier (using the first SSID, para 73), a first communication session (connection to accomplish data transfer, para 124) between a user device (connecting to client device, abstract) and the network device (connecting by the device with the network, abstract) via the first network (using the LAN/WAN, etc., para 73); based on establishment of the first communication session (after the connection is made using the first SSID, para 73), determining, based on a device identifier associated with the user device, network information of a second network identifier (various identifying information about the client device including MAC address, para 39, 68, 10, IP address assigned to the client device, para 39, 68, 10, SSID(s) mapped and associated with the client device identifiers including MAC address / IP address, para 68, 39, 10), determined, via the first communication session, a second network (SSID(s) mapped and associated with the client device identifiers including MAC address / IP address, para 68, 39, 10); broadcasting, by the network device of the second network, based on the network information, a second network identifier of the second network (broadcasting second SSID associated with another LAN/WAN, etc., para 73); and establishing, based on the second network identifier (using the second SSID, para 73), a second communication session (connection is created using second ssid for transfer of traffic/packets, para 39, 68, 10, 44) between the user device (client device, para 10) and the network device via the second network (device using second SSID associated with second LAN/WAN/etc, para 10, 44).
Kollu-Qualcomm does not specifically mention about, which is well-known in the art, which Lee discloses, the second network previously associated with the user device (the wireless LAN network is searched through the interworking with the access point unit 410 (S100). At this time, the access point unit 410 registers a MAC (Media Access Control) address of the terminal,
Then, the terminal 100 performs authentication for the terminal in cooperation with the authentication unit 430 (S110). At this time, the authentication unit 430 stores the MAC address of the UE and International Mobile Subscriber Identity (IMSI) information. In step S100 and step S110, it is determined whether the terminal 100 searches for a wireless LAN network and how the authentication unit 430 performs authentication for the terminal 100.
When terminal authentication is completed in step S101, the terminal 100 requests the access point 410 to use the same IP in the wireless LAN network.
The access point unit 410 requests an IP to be allocated to the terminal 100 to the network unit 420 (S103). Since the access point 410 transmits the MAC address of the already stored terminal together when requesting the IP, the network unit 420 registers the MAC address of the terminal 100 after receiving the IP request signal (6th- 12th para, page 4).
register the location of the terminal, generates an IP address to be used both on the first network and a second network in the same way, and allocates the IP address to the terminal to enable the mobility between the first network and the second network (page 1, abstract).
Therefore, it would have been obvious to one of ordinary skill in the art at the time of the effective filing date of the claimed invention to modify the invention disclosed by Kollu-Qualcomm to implement these limitations and also one of ordinary skill in the art would have been motivated to do so because it could provide utilizing well-known use of previously associated network. The registered terminal using IP address and/or MAC address would enable the device to connect and access information from the network. This would enable the mobility between the first network and the second network, abstract, 6th- 12th para, page 4.
Kollu-Qualcomm and Lee does not specifically mention about, which is well-known in the art, which Ramalingam discloses, the second network identifier and the parameter having been associated with the user device prior to the establishment of the first communication session, based on the determination of the second network identifier of the second network associated with the user device prior to the establishment of the first communication session, broadcasting the second network identifier (fig. 4
(26) The cooperative access point module 114 executing on the access point 104 may provide one or more functions. One function is providing an identifier associated with the cooperative network. For example, the access point 104 may be configured to broadcast a first service set identification (“SSID”) for the user's private network of “mybusiness” and a second SSID for “coop” which is associated with the cooperative network, col., 4, lines 61-67,
(41) In the mobile user device scenario 130, the user device 102(1) is in motion from one physical location to another. The motion may be detected based on signal strength received from the access points 104, positioning system data, accelerometer data, and so forth. One or more modules in the system 100 may use the motion to determine a predicted path 134. For example, the cooperative maintenance module 120 may be configured to use the motion information about the user device 102 to generate the predicted path 134. The predicated path 134 may be used to coordinate the activity of one or more of the cooperative maintenance module 120, the cooperative routing module 122, the cooperative participant module 110, or the cooperative access point module 114. The cooperative participant module 110 may be provided with the SSIDs or other settings or credentials needed for use of access points 104 along the predicted path 134, before coming into the communication range 106 of those access points 104. For example, shortly after starting in motion at T=0, the user device 102(1) may receive the settings or credentials for the access point 104(1) such that, at T=1 when the user device 102(1) is in communication range 106(1) of the access point 104(1), communication may be established or maintained, col., 7, lines 22-44,
(57) Other controls for setting private SSIDs 410 may also be presented. A private SSID is an SSID associated with a network other than the cooperative network. For example, the access point 104 may be configured to support multiple simultaneous SSIDs, such as a first SSID associated with the cooperative network and a second SSID associated with the private network, col., 14, lines 7-12,
(99) As described above with regard to FIG. 1B, one or more of the cooperative network server 118, the cooperative participant module 110, or the cooperative access point module 114 may be configured to maintain connectivity when relative motion occurs between the user devices 102 and the access points 104. For example, motion may be determined and used to provide communication credentials, SSIDs, and so forth to the cooperative participant module 110, the cooperative access point module 114, and so forth. For example, the user may be traveling with the user device 102, moving from the communication range 106 of one access point 104 to another. In another example, the user device 102 may be stationary while the access point 104, such as a portable hotspot, is in motion, col., 15, lines 30-45,
(76) The datastore 516 may store configuration data 518 associated with operation of the access point 104. The configuration data 518 may include SSIDs, QoS settings, and so forth. In some implementations at least a portion of the configuration data 518 may be received from the cooperative network server 118 or another device configured to remotely configure the access point 104. In some implementations the datastore 516 may include at least a portion of one or more of account data 124 or usage data 126. Other data 522 may also be stored in the datastore, such as the MAC address of the communication interfaces 506, list of network addresses provided by a dynamic host configuration protocol (“DHCP”) module, and so forth, col., 12, lines 49- 59.
Therefore, it would have been obvious to one of ordinary skill in the art at the time of the effective filing date of the claimed invention to modify the invention disclosed by Kollu-Qualcomm to implement these limitations and also one of ordinary skill in the art would have been motivated to do so because it could provide utilizing well-known stored second SSID. When the user device is in the communication range of the access point, the user device would receive the broadcasted second SSID that is associated with the range of the access point. Each time the user device that is travelling on the same path is within the access point range, the same (previous) SSID would be available for the user device to make a connection, col., 7, lines 22-44.
Kollu-Qualcom, Ramalingam and Lee does not specifically mention about, which is well-known in the art, which Cai discloses, security parameter associated with the device prior to the first communication (abstract, page 3).
Therefore, it would have been obvious to one of ordinary skill in the art at the time of the effective filing date of the claimed invention to modify the invention disclosed by Kollu-Qualcomm to implement these limitations and also one of ordinary skill in the art would have been motivated to do so because it could provide utilizing well-known security parameter. For example, the password would provide secure access since others would not be able to access information without the password. When the session terminates, the password is also requires for the upcoming/next/following session and which is provided for the network.
Note: The specification contains, the security parameters can comprise one or more of, a password, WEP encryption, WPA encryption, WPA encryption, MAC address restriction, any other security parameters, para 19
Referring to claim 2, Kollu-Qualcomm also teaches wherein the first communication session is established without a security parameter (security parameter is not used, para 73).
Referring to claim 3, Kollu-Qualcomm also teaches wherein the first network comprises a public network (internet, WAN, para 32), and wherein the second network comprises a private network (LAN, para 32, private IP addresses, para 10).
Referring to claim 4, Kollu-Qualcomm also teaches wherein the device identifier comprises at least one of a media access control (MAC) address or an Internet protocol (IP) address (various identifying information about the client device including MAC address, para 39, IP address assigned to the client device, para 10).
Referring to claim 5, Kollu-Qualcomm also teaches wherein the network information comprises at least one of a service set identifier (SSID), a password, an encryption, an Internet protocol (IP) address, or an address restriction (SSID, para 10, various identifying information IP address, para 10).
Referring to claim 6, Kollu-Qualcomm also teaches receiving, by a remote computing device, the first network identifier (first SSID, remote source/device, para 80, 81).
Referring to claim 8, Kollu-Qualcomm also teaches a method comprising: establishing a first communication session between a user device and a network device via a first network (connecting using a first SSID associated with LAN/WAN, etc., para 73, connection to accomplish data transfer, para 124); based on establishment of the first communication session (after the connection is made using the first SSID, para 73), determining based on an identifier associated with the user device, a network identifier of a second network associated with the user device (SSID(s) mapped and associated with the client device identifiers including MAC address / IP address, para 68, 73); broadcasting, by the network device, the network identifier (broadcasting second SSID associated with another LAN/WAN, etc., para 73); and establishing, based on the second network identifier (using the second SSID, para 44, 73, 10); and establishing, based on the network identifier (using the second SSID, para 44, 73, 10), a second communication session (connection is created using second ssid for transfer of traffic/packets, para 10, 44, 73) between the user device and the network device via the second network (device using second SSID associated with second LAN/WAN/etc, para 10, 44).
Kollu-Qualcomm does not specifically mention about, which is well-known in the art, which Lee discloses, the second network previously associated with the user device (the wireless LAN network is searched through the interworking with the access point unit 410 (S100). At this time, the access point unit 410 registers a MAC (Media Access Control) address of the terminal,
Then, the terminal 100 performs authentication for the terminal in cooperation with the authentication unit 430 (S110). At this time, the authentication unit 430 stores the MAC address of the UE and International Mobile Subscriber Identity (IMSI) information. In step S100 and step S110, it is determined whether the terminal 100 searches for a wireless LAN network and how the authentication unit 430 performs authentication for the terminal 100.
When terminal authentication is completed in step S101, the terminal 100 requests the access point 410 to use the same IP in the wireless LAN network.
The access point unit 410 requests an IP to be allocated to the terminal 100 to the network unit 420 (S103). Since the access point 410 transmits the MAC address of the already stored terminal together when requesting the IP, the network unit 420 registers the MAC address of the terminal 100 after receiving the IP request signal (6th- 12th para, page 4).
register the location of the terminal, generates an IP address to be used both on the first network and a second network in the same way, and allocates the IP address to the terminal to enable the mobility between the first network and the second network (page 1, abstract).
Therefore, it would have been obvious to one of ordinary skill in the art at the time of the effective filing date of the claimed invention to modify the invention disclosed by Kollu-Qualcomm to implement these limitations and also one of ordinary skill in the art would have been motivated to do so because it could provide utilizing well-known use of previously associated network. The registered terminal using IP address and/or MAC address would enable the device to connect and access information from the network. This would enable the mobility between the first network and the second network, abstract, 6th- 12th para, page 4.
Kollu-Qualcomm and Lee does not specifically mention about, which is well-known in the art, which Ramalingam discloses, the second network identifier and the parameter having been associated with the user device prior to the establishment of the first communication session, based on the determination of the second network identifier of the second network associated with the user device prior to the establishment of the first communication session, broadcasting the second network identifier (
(26) The cooperative access point module 114 executing on the access point 104 may provide one or more functions. One function is providing an identifier associated with the cooperative network. For example, the access point 104 may be configured to broadcast a first service set identification (“SSID”) for the user's private network of “mybusiness” and a second SSID for “coop” which is associated with the cooperative network, col., 4, lines 61-67,
(41) In the mobile user device scenario 130, the user device 102(1) is in motion from one physical location to another. The motion may be detected based on signal strength received from the access points 104, positioning system data, accelerometer data, and so forth. One or more modules in the system 100 may use the motion to determine a predicted path 134. For example, the cooperative maintenance module 120 may be configured to use the motion information about the user device 102 to generate the predicted path 134. The predicated path 134 may be used to coordinate the activity of one or more of the cooperative maintenance module 120, the cooperative routing module 122, the cooperative participant module 110, or the cooperative access point module 114. The cooperative participant module 110 may be provided with the SSIDs or other settings or credentials needed for use of access points 104 along the predicted path 134, before coming into the communication range 106 of those access points 104. For example, shortly after starting in motion at T=0, the user device 102(1) may receive the settings or credentials for the access point 104(1) such that, at T=1 when the user device 102(1) is in communication range 106(1) of the access point 104(1), communication may be established or maintained, col., 7, lines 22-44,
(57) Other controls for setting private SSIDs 410 may also be presented. A private SSID is an SSID associated with a network other than the cooperative network. For example, the access point 104 may be configured to support multiple simultaneous SSIDs, such as a first SSID associated with the cooperative network and a second SSID associated with the private network, col., 14, lines 7-12,
(99) As described above with regard to FIG. 1B, one or more of the cooperative network server 118, the cooperative participant module 110, or the cooperative access point module 114 may be configured to maintain connectivity when relative motion occurs between the user devices 102 and the access points 104. For example, motion may be determined and used to provide communication credentials, SSIDs, and so forth to the cooperative participant module 110, the cooperative access point module 114, and so forth. For example, the user may be traveling with the user device 102, moving from the communication range 106 of one access point 104 to another. In another example, the user device 102 may be stationary while the access point 104, such as a portable hotspot, is in motion, col., 15, lines 30-45,
(76) The datastore 516 may store configuration data 518 associated with operation of the access point 104. The configuration data 518 may include SSIDs, QoS settings, and so forth. In some implementations at least a portion of the configuration data 518 may be received from the cooperative network server 118 or another device configured to remotely configure the access point 104. In some implementations the datastore 516 may include at least a portion of one or more of account data 124 or usage data 126. Other data 522 may also be stored in the datastore, such as the MAC address of the communication interfaces 506, list of network addresses provided by a dynamic host configuration protocol (“DHCP”) module, and so forth, col., 12, lines 49- 59.
Therefore, it would have been obvious to one of ordinary skill in the art at the time of the effective filing date of the claimed invention to modify the invention disclosed by Kollu-Qualcomm to implement these limitations and also one of ordinary skill in the art would have been motivated to do so because it could provide utilizing well-known stored second SSID. When the user device is in the communication range of the access point, the user device would receive the broadcasted second SSID that is associated with the range of the access point. Each time the user device that is travelling on the same path is within the access point range, the same (previous) SSID would be available for the user device to make a connection, col., 7, lines 22-44.
Referring to claim 9, Kollu-Qualcomm also teaches wherein establishing the first communication session comprises establishing the first communication session without a security parameter (security parameter is not used in para 73, 124).
Referring to claim 10, Kollu-Qualcomm also teaches wherein the first network comprises a public network (internet, WAN, para 32), and wherein the second network comprises a private network (LAN, para 32, private IP addresses, para 10).
Referring to claim 11, Kollu-Qualcomm also teaches receiving at least one of a media access control (MAC) address or an Internet protocol (IP) address associated with the second network (various identifying information about the client device including MAC address, para 39, IP address assigned to the client device, para 10).
Referring to claim 12, Kollu-Qualcomm also teaches associating a subscriber with the user device (entity providing subscriptions for the client device, para 20, 10, 68).
Referring to claim 14, Kollu-Qualcomm also teaches wherein the network identifier comprises a service set identifier (SSID) (para 68).
Claim(s) 7 is/are rejected under 35 U.S.C. 103 as being unpatentable over Kollu-Qualcomm in view of Ramalingam, Cai, Lee and Kim 20160150298.
Referring to claim(s) 7, Kollu-Qualcomm, Cai, Ramalingam and Lee does not specifically mention about, which is well-known in the art, which Kim discloses, obtaining, by a remote computing device, the first network identifier from a gateway (ssid(s) from gateway(s) is obtained by the device, para 65). Therefore, it would have been obvious to one of ordinary skill in the art at the time of the effective filing date of the claimed invention to modify the invention disclosed by Kollu-Qualcomm to implement these limitations and also one of ordinary skill in the art would have been motivated to do so because it could provide utilizing well-known use of SSID(s). The obtained SSID would enable the device to connect and access information para 65. Kim’s multiple gateways would provide different SSID and the device would be able to connect with multiple devices using the different SSIDs and access information from different devices, para 65.
Claim(s) 13, 15, 16 is/are rejected under 35 U.S.C. 103 as being unpatentable over Kollu-Qualcomm in view of Lee, Ramalingam and Cai.
Referring to claim(s) 13, Kollu-Qualcomm, Ramalingam and Lee does not specifically mention about, which is well-known in the art, which Cai discloses, establishing the communication session based on a password, abstract. Therefore, it would have been obvious to one of ordinary skill in the art at the time of the effective filing date of the claimed invention to modify the invention disclosed by Kollu-Qualcomm to implement these limitations and also one of ordinary skill in the art would have been motivated to do so because it could provide utilizing well-known use of password. The password would provide secure access since others would not be able to access information without the password. When the session terminates the password is also reset and a (new) password of upcoming/next/following session is provided for the network, para 162.
Referring to claim(s) 15, Cai teaches establishing the second communication session based on a security parameter associated with the first network, abstract.
Referring to claim(s) 16, Cai teaches receiving, by the network device and from the user device, a security parameter (password provided by the user to the network device, abstract), wherein the second communication session is established based on the received security parameter, abstract.
Claim(s) 17-24 is/are rejected under 35 U.S.C. 103 as being unpatentable over Kollu-Qualcomm in view of Lee, Ramalingam, Cai and Persson et al., 2016/0277974.
Referring to claim 17, Kollu-Qualcomm substantially teaches a method comprising: establishing, based on a first service set identifier (SSID), a communication session between a user device and a network device via a first network (using first SSID associated with LAN/WAN, etc., para 73, connection to accomplish data transfer with client device, para 124)
based on establishment of the first communication session (after the connection is made using the first SSID, para 73), determining, based on a device identifier associated with the user device, a second SSID associated with a second network (SSID(s) mapped and associated with the client device identifiers including MAC address / IP address, para 68, 17, 10, various identifying information about the client device including MAC address, para 39, IP address assigned to the client device, para 10, 17, 68);
broadcasting, by the network device, the second SSID; (broadcasting second SSID associated with another LAN/WAN, etc., para 73, 10, 68) and
establishing, based on a parameter associated with the device identifier (using multiple client identifiers, parameters, para 68), a communication session between the user device and the network device (connection is created using second ssid for transfer of traffic/packets, para 10, 44) via the second network (device using second SSID associated with second LAN/WAN/etc, para 10, 44).
Kollu-Qualcomm does not specifically mention about, which is well-known in the art, which Cai discloses, security parameter, secure communication (session using password abstract. Therefore, it would have been obvious to one of ordinary skill in the art at the time of the effective filing date of the claimed invention to modify the invention disclosed by Kollu-Qualcomm to implement these limitations and also one of ordinary skill in the art would have been motivated to do so because it could provide utilizing well-known use of password. The password would provide secure access since others would not be able to access information without the password. When the session terminates the password a (new) password is needed upcoming/next/following session is provided for the network, abstract.
Kollu-Qualcomm and Cai does not specifically mention about, which is well-known in the art, which Lee discloses, the second network previously associated with the user device (the wireless LAN network is searched through the interworking with the access point unit 410 (S100). At this time, the access point unit 410 registers a MAC (Media Access Control) address of the terminal,
Then, the terminal 100 performs authentication for the terminal in cooperation with the authentication unit 430 (S110). At this time, the authentication unit 430 stores the MAC address of the UE and International Mobile Subscriber Identity (IMSI) information. In step S100 and step S110, it is determined whether the terminal 100 searches for a wireless LAN network and how the authentication unit 430 performs authentication for the terminal 100.
When terminal authentication is completed in step S101, the terminal 100 requests the access point 410 to use the same IP in the wireless LAN network.
The access point unit 410 requests an IP to be allocated to the terminal 100 to the network unit 420 (S103). Since the access point 410 transmits the MAC address of the already stored terminal together when requesting the IP, the network unit 420 registers the MAC address of the terminal 100 after receiving the IP request signal (6th- 12th para, page 4).
register the location of the terminal, generates an IP address to be used both on the first network and a second network in the same way, and allocates the IP address to the terminal to enable the mobility between the first network and the second network (page 1, abstract).
Therefore, it would have been obvious to one of ordinary skill in the art at the time of the effective filing date of the claimed invention to modify the invention disclosed by Kollu-Qualcomm to implement these limitations and also one of ordinary skill in the art would have been motivated to do so because it could provide utilizing well-known use of previously associated network. The registered terminal using IP address and/or MAC address would enable the device to connect and access information from the network. This would enable the mobility between the first network and the second network, abstract, 6th- 12th para, page 4.
Kollu-Qualcomm, Cai, Lee does not specifically mention about, which is well-known in the art, which Persson discloses, open communication session (open wifi for user connection, para 37).
Therefore, it would have been obvious to one of ordinary skill in the art at the time of the effective filing date of the claimed invention to modify the invention disclosed by Kollu-Qualcomm to implement these limitations and also one of ordinary skill in the art would have been motivated to do so because it could provide utilizing well-known open wifi. When the user is at a public place, like café, the user would be able to access information using the open wifi, which is good for non-secure information purpose of the user, para 176.
Kollu-Qualcomm, Persson and Lee does not specifically mention about, which is well-known in the art, which Ramalingam discloses, the second network identifier and the parameter having been associated with the user device prior to the establishment of the first communication session, based on the determination of the second network identifier of the second network associated with the user device prior to the establishment of the first communication session, broadcasting the second network identifier (fig. 4
(26) The cooperative access point module 114 executing on the access point 104 may provide one or more functions. One function is providing an identifier associated with the cooperative network. For example, the access point 104 may be configured to broadcast a first service set identification (“SSID”) for the user's private network of “mybusiness” and a second SSID for “coop” which is associated with the cooperative network, col., 4, lines 61-67,
(41) In the mobile user device scenario 130, the user device 102(1) is in motion from one physical location to another. The motion may be detected based on signal strength received from the access points 104, positioning system data, accelerometer data, and so forth. One or more modules in the system 100 may use the motion to determine a predicted path 134. For example, the cooperative maintenance module 120 may be configured to use the motion information about the user device 102 to generate the predicted path 134. The predicated path 134 may be used to coordinate the activity of one or more of the cooperative maintenance module 120, the cooperative routing module 122, the cooperative participant module 110, or the cooperative access point module 114. The cooperative participant module 110 may be provided with the SSIDs or other settings or credentials needed for use of access points 104 along the predicted path 134, before coming into the communication range 106 of those access points 104. For example, shortly after starting in motion at T=0, the user device 102(1) may receive the settings or credentials for the access point 104(1) such that, at T=1 when the user device 102(1) is in communication range 106(1) of the access point 104(1), communication may be established or maintained, col., 7, lines 22-44,
(57) Other controls for setting private SSIDs 410 may also be presented. A private SSID is an SSID associated with a network other than the cooperative network. For example, the access point 104 may be configured to support multiple simultaneous SSIDs, such as a first SSID associated with the cooperative network and a second SSID associated with the private network, col., 14, lines 7-12,
(99) As described above with regard to FIG. 1B, one or more of the cooperative network server 118, the cooperative participant module 110, or the cooperative access point module 114 may be configured to maintain connectivity when relative motion occurs between the user devices 102 and the access points 104. For example, motion may be determined and used to provide communication credentials, SSIDs, and so forth to the cooperative participant module 110, the cooperative access point module 114, and so forth. For example, the user may be traveling with the user device 102, moving from the communication range 106 of one access point 104 to another. In another example, the user device 102 may be stationary while the access point 104, such as a portable hotspot, is in motion, col., 15, lines 30-45,
(76) The datastore 516 may store configuration data 518 associated with operation of the access point 104. The configuration data 518 may include SSIDs, QoS settings, and so forth. In some implementations at least a portion of the configuration data 518 may be received from the cooperative network server 118 or another device configured to remotely configure the access point 104. In some implementations the datastore 516 may include at least a portion of one or more of account data 124 or usage data 126. Other data 522 may also be stored in the datastore, such as the MAC address of the communication interfaces 506, list of network addresses provided by a dynamic host configuration protocol (“DHCP”) module, and so forth, col., 12, lines 49- 59.
Therefore, it would have been obvious to one of ordinary skill in the art at the time of the effective filing date of the claimed invention to modify the invention disclosed by Kollu-Qualcomm to implement these limitations and also one of ordinary skill in the art would have been motivated to do so because it could provide utilizing well-known stored second SSID. When the user device is in the communication range of the access point, the user device would receive the broadcasted second SSID that is associated with the range of the access point. Each time the user device that is travelling on the same path is within the access point range, the same (previous) SSID would be available for the user device to make a connection, col., 7, lines 22-44.
Referring to claim 18, Kollu-Qualcomm also teaches wherein the device identifier comprises at least one of a media access control (MAC) address and an Internet protocol (IP) address (various identifying information about the client device including MAC address, para 39, IP address assigned to the client device, para 10).
Referring to claim(s) 19, Cai teaches wherein the security parameter comprises a password (abstract).
Referring to claim(s) 20, Cai teaches receiving, by the network device and from the user device, the security parameter (abstract).
Referring to claim(s) 21, Cai teaches determining, based on the device identifier, the security parameter (password for the user device identity, abstract).
Referring to claim 22, Kollu-Qualcomm also teaches associating, based on the device identifier, a subscriber with the user device (subscriptions for the client device, para 20, 10, 68).
Referring to claim 23, Kollu-Qualcomm also teaches wherein the first network comprises a public network (internet, WAN, para 32), and wherein the second network comprises a private network (LAN, para 32, private IP addresses, para 10).
Referring to claim 24, Kollu-Qualcomm also teaches establishing the communication session without the security parameter or another security parameter (security parameter is not used, para 73).
Response to Arguments
Applicant's arguments filed 11/21/25, pages 6-14, have been fully considered but they are not persuasive. Therefore, rejection of claims 1-24 is maintained.
Regarding Applicant’s concern for the amended limitations, of the independent claims 1, 8, 17,
The First inquiry must be into exactly what the claims define. See In re Wilder, 166 USPQ 545, 548 (CCPA 1970). What is claimed is, based on establishment of the first communication session, which is not limited to when the first communication session was established. For example, one second ago or a year ago, before the “determining …. A second network identifier ….” Is performed. The first communication session is subject to termination, which can be prior to or after “determining …. A second network identifier ….”. The outcome of “determining …. A second network identifier ….” Is same regardless of the addition of the amended limitations. The determination of the second network identifier of the second network is not limited to having the second network identifier being valid or invalid. The second network identifier is not limited to any particular size, value, etc. The second network identifier is merely associated with the user device. The second network identifier is not limited to of the user device or on the user device, etc. The second network identifier has no impact from the user device. The determining of the second network identifier would be performed regardless of what the user device is. The determining of the second network identifier would be performed regardless of what the device identifier is. The determining of the second network identifier would be performed regardless of when a second network identifier is somehow associated, as the prior to the first session means one second ago, or 1 year ago. The limitations, broadcasting, the second network identifier of the second network, do not accomplish anything. broadcasting which is not performed across anything. The broadcasting is not over a network or a plurality of networks. Mainly, not a single device receives the broadcast. Such limitations do not accomplish anything.
Regarding the amended limitations, determining, based on a device identifier associated with the user device determined via the first communication session, a second network identifier of a second network and one or more security parameters, the second network identifier and the one or more security parameters having been associated with the user device prior to establishment of the first communication session; and based on the determination of the second network identifier of the second network associated with the user device prior to establishment of the first communication session and the one or more security parameters, broadcasting, by the network device, the second network identifier of the second network.
Applicant’s below remarks are noted.
Paragraph 3 explains
that "[s]ome methods and systems described herein, in one aspect, can determine the security
associated with a device and a first network, and can automatically provide that security to the
device in a second network." Paragraph 32 explains that "a user device can connect to the open
network, a computing device (e.g., gateway device, computing device, server, router, etc.) can
recognize the user device and the computing device can retrieve a second identifier associated with
a secure network and the user device," where "the second identifier can be a second SSID," and
"[t]he computing device can transmit the second identifier associated with the secure network to
the user device." Paragraph 45 describes a mapping object generated when the user device
connects to a first network: "a MAC address associated with the user device 102 can be mapped
to an IP address that is associated with the LAN (e.g., home network) to which the user device 102
is connected." Subsequently, "when the user device 102 associates (e.g., connects) with a second
network, the second network device can check a device identifier (e.g., MAC address) associated
with the user device 102 against one or more mapping objects (e.g., stored at database 114)." If
located, "the first SSID can be broadcast to the user device 102" and "communications
therebetween can be protected by the first set of security parameters."
Paragraph 66 describes a subscriber database in storage medium 313 managed by
computing device 310: "[t]he subscriber database can associate various parameters, such as, for
example, an account name, device identifier, e-mail address, e-mail password, identifiers (305,
306), passwords for identifiers (305, 306), and SSIDs 309 with a particular subscriber." Paragraph
66 further explains that "any information stored in a subscriber database associated with a
subscriber can be used as a security parameter" and "can be used to identify the subscriber and one
or more appropriate security parameters associated with the subscriber."
Paragraph 67 explains that computing device 310 communicates with network devices "for
mapping first identifiers 305 with corresponding second identifiers 306 in storage medium 313."
Paragraph 68 further explains that "storage medium 313 can store a plurality of data sets such as
mapping objects, first identifiers 305, second identifiers 306, third identifiers 308a, 308b, and/or
SSIDs 309 or other information," and that "computing device 310 can obtain the first identifier
305 from the gateway 304 and retrieve information from the storage medium 313 such as a
mapping of the first identifier 305 to the SSID 309 and/or the second identifier 306."
Paragraphs 70 and 71 provide a concrete network-device embodiment. Paragraph 70
explains that "user device 303 can establish a connection with network 315 through network device
302a, in response to network device 302a broadcasting SSID 309a," and that "[c]omputing device
310 can receive first identifier 305 associated with user device 303" and "retrieve the user or
subscriber information associated with first identifier 305, including SSID 309." Computing
device 310 then provides "network device 302a with SSID 309, so that network device 302a can
create/broadcast SSID 309 to user device 303 and require the same security parameters that are
used to connect to gateway 306 (e.g., password, etc. ...)." Paragraph 71 further explains that
"network device 302a can retrieve security parameters associated with a subscriber account
associated with first identifier 305" and that "[u]ser device 303 can establish a connection with
network device 302a using the SSID 309 utilizing the security parameters otherwise associated
with connecting to gateway 304 using SSID 309."
Paragraphs 75 and 77 describe the session sequence directly. Paragraph 75 explains that
"[t]he second network device can receive the first information from the user device, for example,
an identifier of the user device through the open connection," and that the second network device
"can transmit the first information to a computing device and request an SSID associated with the
first network device, and any associated security parameters." The "[c]omputing device can
determine the SSID associated with the first network device and the security parameters associated
with the first network device" and "can transmit the determined SSID and/or security parameters
to the second network device." Paragraph 77 then explains the result: "the user device connects to
the network device by using an SSID and security parameters that were previously configured for
the user device to connect to another network device."
Paragraphs 81 and 82 reinforce the same relationship in the Figure 10 embodiment. The
identifier is received through an open connection and mapped to stored network information that
can include an SSID and security parameters. The second network device retrieves that stored
information and uses it to create and broadcast an SSID originally associated with the first network
device, while the associated security parameters are used to secure the resulting connection.
Paragraphs 86 through 88 describe the Figure 11 embodiment. Paragraph 86 explains that
"[p]rior to connecting to the network device, the information associated with the user device can
already have been provided to the remote server," and the transmitted information includes
"security information and a third identifier" where "[t]he third identifier can be, for example, an
SSID associated with another network device with which the user device already has configured
security parameters (e.g., a home network device)." Paragraph 86 further states that "[t]he security
information and the third identifier can represent a preconfigured SSID and security parameters
used by the user device to connect to another network device (for example, a home network
device)." Paragraph 88 then confirms that "the user device connects to the network device by using
an SSID and security parameters that were previously configured for the user device to connect to
another network device."
Thus, the specification provides detailed support across multiple embodiments for a device
identifier obtained through an open or first communication session to be used to retrieve both a
second network identifier and security parameters from pre-existing associations with the user
device. Critically, these are not separate, unrelated operations. Paragraph 66 stores the SSID and
passwords together in the same subscriber record. Paragraph 86 describes the returned information
as a unit comprising "security information and a third identifier" where "[t]he security information
and the third identifier can represent a preconfigured SSID and security parameters used by the
user device to connect to another network device (for example, a home network device)." The
specification thus describes a single subscriber record from which both the network identifier and
security parameters are retrieved as a joint, pre-existing association. The disclosure distinguishes
the open first session from the prior configuration that supplies the stored SSID and security
information. This is the claimed relationship and reasonably conveys possession of the subject
matter as of the filing date.
Similar to the above Applicant’s statements,
Ramalingam discloses, (fig. 4
(26) The cooperative access point module 114 executing on the access point 104 may provide one or more functions. One function is providing an identifier associated with the cooperative network. For example, the access point 104 may be configured to broadcast a first service set identification (“SSID”) for the user's private network of “mybusiness” and a second SSID for “coop” which is associated with the cooperative network, col., 4, lines 61-67,
(41) In the mobile user device scenario 130, the user device 102(1) is in motion from one physical location to another. The motion may be detected based on signal strength received from the access points 104, positioning system data, accelerometer data, and so forth. One or more modules in the system 100 may use the motion to determine a predicted path 134. For example, the cooperative maintenance module 120 may be configured to use the motion information about the user device 102 to generate the predicted path 134. The predicated path 134 may be used to coordinate the activity of one or more of the cooperative maintenance module 120, the cooperative routing module 122, the cooperative participant module 110, or the cooperative access point module 114. The cooperative participant module 110 may be provided with the SSIDs or other settings or credentials needed for use of access points 104 along the predicted path 134, before coming into the communication range 106 of those access points 104. For example, shortly after starting in motion at T=0, the user device 102(1) may receive the settings or credentials for the access point 104(1) such that, at T=1 when the user device 102(1) is in communication range 106(1) of the access point 104(1), communication may be established or maintained, col., 7, lines 22-44,
(57) Other controls for setting private SSIDs 410 may also be presented. A private SSID is an SSID associated with a network other than the cooperative network. For example, the access point 104 may be configured to support multiple simultaneous SSIDs, such as a first SSID associated with the cooperative network and a second SSID associated with the private network, col., 14, lines 7-12,
(99) As described above with regard to FIG. 1B, one or more of the cooperative network server 118, the cooperative participant module 110, or the cooperative access point module 114 may be configured to maintain connectivity when relative motion occurs between the user devices 102 and the access points 104. For example, motion may be determined and used to provide communication credentials, SSIDs, and so forth to the cooperative participant module 110, the cooperative access point module 114, and so forth. For example, the user may be traveling with the user device 102, moving from the communication range 106 of one access point 104 to another. In another example, the user device 102 may be stationary while the access point 104, such as a portable hotspot, is in motion, col., 15, lines 30-45,
(76) The datastore 516 may store configuration data 518 associated with operation of the access point 104. The configuration data 518 may include SSIDs, QoS settings, and so forth. In some implementations at least a portion of the configuration data 518 may be received from the cooperative network server 118 or another device configured to remotely configure the access point 104. In some implementations the datastore 516 may include at least a portion of one or more of account data 124 or usage data 126. Other data 522 may also be stored in the datastore, such as the MAC address of the communication interfaces 506, list of network addresses provided by a dynamic host configuration protocol (“DHCP”) module, and so forth, col., 12, lines 49- 59.
Regarding remarks, for a motivation to combine with references.
Applicant failed to consider, The reason or motivation to modify the reference may often suggest what the inventor has done, but for a different purpose or to solve a different problem. It is not necessary that the prior art suggest the combination to achieve the same advantage or result discovered by applicant. In re Linter, 458 F.2d 1013, 173 USPQ 560 (CCPA 1972).
Contrary to Applicant’s the primary reference is open for modifications.
Lee is merely relied upon and discloses, the second network previously associated with the user device (the wireless LAN network is searched through the interworking with the access point unit 410 (S100). At this time, the access point unit 410 registers a MAC (Media Access Control) address of the terminal,
Then, the terminal 100 performs authentication for the terminal in cooperation with the authentication unit 430 (S110). At this time, the authentication unit 430 stores the MAC address of the UE and International Mobile Subscriber Identity (IMSI) information. In step S100 and step S110, it is determined whether the terminal 100 searches for a wireless LAN network and how the authentication unit 430 performs authentication for the terminal 100.
When terminal authentication is completed in step S101, the terminal 100 requests the access point 410 to use the same IP in the wireless LAN network.
The access point unit 410 requests an IP to be allocated to the terminal 100 to the network unit 420 (S103). Since the access point 410 transmits the MAC address of the already stored terminal together when requesting the IP, the network unit 420 registers the MAC address of the terminal 100 after receiving the IP request signal (6th- 12th para, page 4).
register the location of the terminal, generates an IP address to be used both on the first network and a second network in the same way, and allocates the IP address to the terminal to enable the mobility between the first network and the second network (page 1, abstract).
Ramalingam is merely relied upon for, based on the determination of the second network identifier of the second network previously associated with the user device, broadcasting the second network identifier.
The combining of the Ramalingam and Lee do not impact the structure of the Kollu-Qualcomm. Kollu-Qualcomm is capable of but do not specifically mention about these limitations, which Ramalingam and Lee specifically show that can be performed by the Kollu-Qualcomm.
Kollu-Qualcomm substantially teaches a method comprising:
broadcasting, by a network device, a first network identifier of a first network (broadcast first SSID associated with LAN/WAN, etc., para 73, connection to accomplish data transfer, para 124); establishing, based on the first network identifier (using the first SSID, para 73), a first communication session (connection to accomplish data transfer, para 124) between a user device (connecting to client device, abstract) and the network device (connecting by the device with the network, abstract) via the first network (using the LAN/WAN, etc., para 73); based on establishment of the first communication session (after the connection is made using the first SSID, para 73), determining, based on a device identifier associated with the user device, network information of a second network identifier (various identifying information about the client device including MAC address, para 39, 68, 10, IP address assigned to the client device, para 39, 68, 10, SSID(s) mapped and associated with the client device identifiers including MAC address / IP address, para 68, 39, 10), determined, via the first communication session, a second network (SSID(s) mapped and associated with the client device identifiers including MAC address / IP address, para 68, 39, 10); broadcasting, by the network device of the second network, based on the network information, a second network identifier of the second network (broadcasting second SSID associated with another LAN/WAN, etc., para 73); and establishing, based on the second network identifier (using the second SSID, para 73), a second communication session (connection is created using second ssid for transfer of traffic/packets, para 39, 68, 10, 44) between the user device (client device, para 10) and the network device via the second network (device using second SSID associated with second LAN/WAN/etc, para 10, 44).
Kollu-Qualcomm does not specifically mention about, which is well-known in the art, which Lee discloses, the second network previously associated with the user device (the wireless LAN network is searched through the interworking with the access point unit 410 (S100). At this time, the access point unit 410 registers a MAC (Media Access Control) address of the terminal,
Then, the terminal 100 performs authentication for the terminal in cooperation with the authentication unit 430 (S110). At this time, the authentication unit 430 stores the MAC address of the UE and International Mobile Subscriber Identity (IMSI) information. In step S100 and step S110, it is determined whether the terminal 100 searches for a wireless LAN network and how the authentication unit 430 performs authentication for the terminal 100.
When terminal authentication is completed in step S101, the terminal 100 requests the access point 410 to use the same IP in the wireless LAN network.
The access point unit 410 requests an IP to be allocated to the terminal 100 to the network unit 420 (S103). Since the access point 410 transmits the MAC address of the already stored terminal together when requesting the IP, the network unit 420 registers the MAC address of the terminal 100 after receiving the IP request signal (6th- 12th para, page 4).
register the location of the terminal, generates an IP address to be used both on the first network and a second network in the same way, and allocates the IP address to the terminal to enable the mobility between the first network and the second network (page 1, abstract).
Therefore, it would have been obvious to one of ordinary skill in the art at the time of the effective filing date of the claimed invention to modify the invention disclosed by Kollu-Qualcomm to implement these limitations and also one of ordinary skill in the art would have been motivated to do so because it could provide utilizing well-known use of previously associated network. The registered terminal using IP address and/or MAC address would enable the device to connect and access information from the network. This would enable the mobility between the first network and the second network, abstract, 6th- 12th para, page 4.
Kollu-Qualcomm and Lee does not specifically mention about, which is well-known in the art, which Ramalingam discloses, the second network identifier and the parameter having been associated with the user device prior to the establishment of the first communication session, based on the determination of the second network identifier of the second network associated with the user device prior to the establishment of the first communication session, broadcasting the second network identifier (fig. 4
(26) The cooperative access point module 114 executing on the access point 104 may provide one or more functions. One function is providing an identifier associated with the cooperative network. For example, the access point 104 may be configured to broadcast a first service set identification (“SSID”) for the user's private network of “mybusiness” and a second SSID for “coop” which is associated with the cooperative network, col., 4, lines 61-67,
(41) In the mobile user device scenario 130, the user device 102(1) is in motion from one physical location to another. The motion may be detected based on signal strength received from the access points 104, positioning system data, accelerometer data, and so forth. One or more modules in the system 100 may use the motion to determine a predicted path 134. For example, the cooperative maintenance module 120 may be configured to use the motion information about the user device 102 to generate the predicted path 134. The predicated path 134 may be used to coordinate the activity of one or more of the cooperative maintenance module 120, the cooperative routing module 122, the cooperative participant module 110, or the cooperative access point module 114. The cooperative participant module 110 may be provided with the SSIDs or other settings or credentials needed for use of access points 104 along the predicted path 134, before coming into the communication range 106 of those access points 104. For example, shortly after starting in motion at T=0, the user device 102(1) may receive the settings or credentials for the access point 104(1) such that, at T=1 when the user device 102(1) is in communication range 106(1) of the access point 104(1), communication may be established or maintained, col., 7, lines 22-44,
(57) Other controls for setting private SSIDs 410 may also be presented. A private SSID is an SSID associated with a network other than the cooperative network. For example, the access point 104 may be configured to support multiple simultaneous SSIDs, such as a first SSID associated with the cooperative network and a second SSID associated with the private network, col., 14, lines 7-12,
(99) As described above with regard to FIG. 1B, one or more of the cooperative network server 118, the cooperative participant module 110, or the cooperative access point module 114 may be configured to maintain connectivity when relative motion occurs between the user devices 102 and the access points 104. For example, motion may be determined and used to provide communication credentials, SSIDs, and so forth to the cooperative participant module 110, the cooperative access point module 114, and so forth. For example, the user may be traveling with the user device 102, moving from the communication range 106 of one access point 104 to another. In another example, the user device 102 may be stationary while the access point 104, such as a portable hotspot, is in motion, col., 15, lines 30-45,
(76) The datastore 516 may store configuration data 518 associated with operation of the access point 104. The configuration data 518 may include SSIDs, QoS settings, and so forth. In some implementations at least a portion of the configuration data 518 may be received from the cooperative network server 118 or another device configured to remotely configure the access point 104. In some implementations the datastore 516 may include at least a portion of one or more of account data 124 or usage data 126. Other data 522 may also be stored in the datastore, such as the MAC address of the communication interfaces 506, list of network addresses provided by a dynamic host configuration protocol (“DHCP”) module, and so forth, col., 12, lines 49- 59.
Therefore, it would have been obvious to one of ordinary skill in the art at the time of the effective filing date of the claimed invention to modify the invention disclosed by Kollu-Qualcomm to implement these limitations and also one of ordinary skill in the art would have been motivated to do so because it could provide utilizing well-known stored second SSID. When the user device is in the communication range of the access point, the user device would receive the broadcasted second SSID that is associated with the range of the access point. Each time the user device that is travelling on the same path is within the access point range, the same (previous) SSID would be available for the user device to make a connection, col., 7, lines 22-44.
Kollu-Qualcom, Ramalingam and Lee does not specifically mention about, which is well-known in the art, which Cai discloses, security parameter associated with the device prior to the first communication (abstract, page 3).
Therefore, it would have been obvious to one of ordinary skill in the art at the time of the effective filing date of the claimed invention to modify the invention disclosed by Kollu-Qualcomm to implement these limitations and also one of ordinary skill in the art would have been motivated to do so because it could provide utilizing well-known security parameter. For example, the password would provide secure access since others would not be able to access information without the password. When the session terminates, the password is also requires for the upcoming/next/following session and which is provided for the network.
Conclusion
Lee et al., 10285058, abstract.
THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to HARESH PATEL whose telephone number is (571)272-3973. The examiner can normally be reached on M-F 9-5:30.
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, Jorge L. Ortiz-Criado, can be reached at (571) 272-7624. The fax phone number for the organization where this application or proceeding is assigned is (571) 273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/HARESH N PATEL/Primary Examiner, Art Unit 2496
Prosecution Insights