Description:DESCRIPTION
Technical Field
[001] The present disclosure relates generally to network management, and more specifically, but not exclusively, to Service Set Identifier (SSID) portability across networks in Multi-Dwelling Environments (MDUs) and system and method thereof.

Background
[002] In modern residential and multi-tenant environments, such as apartment complexes, student housing, and other Multi-Dwelling Units (MDUs), property managers and network administrators often deploy multiple Wireless Local Area Networks (WLANs) to provide connectivity to residents. Typically, such deployments include a community-wide Service Set Identifier (SSID) that is accessible to all residents, as well as individual personal SSIDs that are secured using an enhanced Pre-Shared Key (ePSK) unique to each residential unit. In such deployments, the network administrators generally provision Access Points (APs) through a centralized management portal where Virtual Local Area Networks (VLANs) are assigned to provide network segmentation and resident-level isolation.
[003] However, managing separate ePSKs and VLAN mappings for both the community SSID and the personal SSIDs introduces configuration complexity and increases the likelihood of mismatches or errors. Further, ensuring consistent VLAN assignment across both community SSID and personal SSIDs, while simultaneously maintaining secure per-resident traffic isolation, presents operational challenges. These operational challenges become increasingly difficult to address in large-scale deployments, where scalability, security, and administrative efficiency are critical requirements.
[004] Therefore, the present invention is directed to overcome one or more limitations stated above or any other limitations associated with the known arts.
SUMMARY
[005] In accordance with a first aspect of the disclosure there is provided a method for managing a Service Set Identifier (SSID) portability across networks. The method may include receiving, by a network device, a personal SSID configuration request from a user device associated with a user belonging to a residential unit within a Multi-Dwelling Environment (MDU). It may be noted that the personal SSID configuration request includes an existing personal SSID and a pre-defined user password associated with the existing personal SSID. The method may further include automatically synchronizing, by the network device, the pre-defined user password associated with the existing personal SSID with a community SSID pre-configured for the MDU, in response to receiving the personal SSID configuration request. The method may further include enabling, by the network device, an access of the network to the user device via one of the existing personal SSID or the pre-configured community SSID based on the pre-defined user password.
[006] In accordance with a second aspect of the disclosure there is provided a network device for managing a Service Set Identifier (SSID) portability across networks. The network device may include a processor, and a memory communicably coupled to the processor and comprising processor instructions that when executed by the processor, cause the processor to receive a personal SSID configuration request from a user device associated with a user belonging to a residential unit within a Multi-Dwelling Environment (MDU). It may be noted that the personal SSID configuration request includes an existing personal SSID and a pre-defined user password associated with the existing personal SSID. The processor instructions may further cause the processor to automatically synchronize the pre-defined user password associated with the existing personal SSID with a community SSID pre-configured for the MDU, in response to receiving the personal SSID configuration request. The processor instructions may further cause the processor to enable an access of the network to the user device via one of the existing personal SSID or the pre-configured community SSID based on the pre-defined user password.
[007] In accordance with a third aspect of the disclosure there is provided a system managing a Service Set Identifier (SSID) portability across networks. The system may include a server, configured to receive a personal SSID configuration request from a user device associated with a user belonging to a residential unit within a Multi-Dwelling Environment (MDU). It may be noted that the personal SSID configuration request includes an existing personal SSID and a pre-defined user password associated with the existing personal SSID. The server may be further configured to automatically synchronize the pre-defined user password associated with the existing personal SSID with a community SSID pre-configured for the MDU, in response to receiving the personal SSID configuration request. The system may further include an Access Point (AP) communicatively coupled to the server. The AP may enable the user device to access the network through the server via one of the existing personal SSID or the pre-configured community SSID based on the pre-defined user password.
[008] Further features of the disclosure will be apparent from the following description of preferred embodiments of the disclosure, which are given by way of example only.
BRIEF DESCRIPTION OF THE DRAWINGS
[009] The present application can be best understood by reference to the following description taken in conjunction with the accompanying drawing figures, in which like parts may be referred to by like numerals.
[010] FIG. 1 depicts an exemplary network where various embodiments may be employed.
[011] FIG. 2 depicts an exemplary block diagram of a system configured to manage a Service Set Identifier (SSID) portability across networks, in an embodiment of the disclosure.
[012] FIG. 3 depicts an exemplary functional block diagram of a network device configured to manage a SSID portability across networks, in an embodiment of the disclosure.
[013] FIG. 4 illustrates a flowchart of an exemplary method for managing a SSID portability across networks, in an embodiment of the disclosure.
[014] FIG. 5 illustrate an exemplary flow diagram depicting communication flow between a network device and a user device, in an embodiment of the disclosure.
[015] FIG. 6 illustrates an exemplary ePSK-VLAN ID database, in accordance with an embodiment.
[016] FIG. 7 illustrates a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure.
DETAILED DESCRIPTION
[017] The following description is presented to enable a person of ordinary skill in the art to make and use the disclosure and is provided in the context of particular applications and their requirements. Various modifications to the embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the disclosure. Moreover, in the following description, numerous details are set forth for the purpose of explanation. However, one of ordinary skill in the art will realize that the disclosure might be practiced without the use of these specific details. In other instances, well-known structures and devices are shown in block diagram form in order not to obscure the description of the disclosure with unnecessary detail. Thus, the disclosure is not intended to be limited to the embodiments shown but is to be accorded the widest scope consistent with the principles and features disclosed herein.
[018] Exemplary embodiments are described with reference to the accompanying drawings. Wherever convenient, the same reference numbers are used throughout the drawings to refer to the same or like parts. While examples and features of disclosed principles are described herein, modifications, adaptations, and other implementations are possible without departing from the spirit and scope of the disclosed embodiments. It is intended that the following detailed description be considered as exemplary only, with the true scope and spirit being indicated by the following claims.
[019] Referring now to FIG. 1, an exemplary network 100 where various embodiments may be deployed is illustrated, in accordance with some embodiments. The network 100 may be configured for wireless communication through a wireless networking technology (for example, a Wireless Fidelity (Wi-Fi), Light Fidelity (Li-Fi), or the like) and wired communication through a wired networking technology (for example, Ethernet). The network 100 may be implemented in a Multi-Dwelling Unit (MDU) 102. In an embodiment, the MDU 102 may correspond to a building or a complex including multiple separate residential units or commercial units within a single structure, where each unit is occupied by a different tenant or a user. The MDU 102 may include shared common areas and infrastructure, necessitating centralized management of utilities and network services while maintaining isolation for individual residential units. For example, the MDU 102 may be a building complex, a residential society, an apartment building, a condominium, a boarding house, a hostel, a hotel, a school, a hospital, a government office, a business complex (such as a business park, an enterprise complex, an enterprise office space, a coworking space, etc.), or similar multi-unit structures.
[020] The MDU 102 may include a plurality of property units. For example, when the MDU 102 is the residential society, the plurality of property units may be a plurality of residential units (such as a residential unit 104 and a residential unit 106), and one or more common spaces (for example, a pool area 108, a community center gym 110, or the like). By way of an example, each of the plurality of residential units may correspond to a housing unit, a commercial unit, or a pre-defined area within the MDU 102. Other examples of the one or more common spaces may include, but may not be limited to, a lounge area, a reception area, a common room, a waiting room, a guest room, a meeting room, a cafeteria, a food court, or the like.
[021] In an embodiment, a residential unit within the MDU 102 may be occupied by one or more users. For example, a user may be an owner of the residential unit, a caretaker of the residential unit, a tenant in the residential unit, or a frequent visitor at the residential unit. For example, the residential unit 104 may be occupied by a first user and the residential unit 106 may be occupied by a second user. In an embodiment, there may be more than one user residing in a single residential unit, such as a group of tenants, a resident family, employees, etc. For ease of explanation, the first user and the second user correspond to an individual user.
[022] In an embodiment, each of the one or more users may have one or more user devices. For example, a user device may be a smartphone, a tablet, a laptop, a desktop, a smart speaker, a smartwatch, an Internet of Things (IoT) device, or the like. For example, the first user associated with the residential unit 104 may possess two user devices, i.e., a user device 112A and a user device 112B. The second user associated with the residential unit 106 may possess two user devices, i.e., a user device 114A and a user device 114B. The user may access the network 100 for internet-based services via one of associated user devices. Examples of the internet-based services may include, but are not limited to, browsing services, streaming services, internet voice calling services, video calling services, online banking services, and the like.
[023] The network 100 may further include a plurality of Access Points (APs), such as an AP 116, an AP 118, an AP 120, an AP 122, an AP 124, and an AP 126, strategically deployed within both residential units and common areas. For example, the residential unit 104 may include the AP 116 and the residential unit 104 may include the AP 118. The AP 116 and the AP 118 may provide wireless connectivity to the one or more user devices when a user is within an associated residential unit via an existing personal SSID or a community SSID preconfigured for the MDU 102. Further, APs in common areas (e.g., the AP 124 in the community center gym 110 and the AP 126 near the pool 108) may provide network access to the one or more user devices when a user is present in these common areas. Each AP includes wireless network interfaces (e.g., Wireless Fidelity (Wi-Fi) radios) and may include wired interfaces (e.g., Ethernet ports), enabling the one or more user devices to connect either wirelessly or through a wired connection.
[024] The network 100 may further include a remote server 128, a gateway 130, and one or more switches (such as a switch 132 and a switch 134) communicatively connected to the gateway 130. The plurality of APs may be communicatively connected to the one or more switches. For example, the AP 118, the AP 120, and the AP 126 may be communicatively connected to the switch 132, and the AP 116, the AP 122, and the AP 124 may be communicatively connected to the switch 134.
[025] In an embodiment, the remote server 128 may be a remote network management server (e.g., cnMaestro™) of a network administrator (e.g., a Managed Service Provider Administrator (MSP) administrator) of the network 100. The remote server 128 may deploy, monitor, and manage the network 100 through cloud. In other words, the remote server 128 may manage internet access to user devices in the MDU 102. It should be noted that for efficient network management, the network 100 may be logically divided into a plurality of Virtual Local Area Networks (VLANs). Typically, a VLAN is defined by the network administrator for the wireless network interface of each of the plurality APs in the MDU 102. For each of the APs located inside the plurality of residential units, a unique VLAN is defined for the wireless network interface of the associated residential unit. Each of the plurality of VLANs may include a VLAN ID provisioned for an AP serving a corresponding residential unit. The gateway 130 may route data traffic (or internet traffic) between the internet (not shown in figure) and various network devices (i.e., the one or more switches and the plurality of APs) in the MDU 102 through the one or more switches. The one or more switches may route the internet traffic to the one or more user devices of appropriate VLANs.
[026] To elaborate, a single VLAN may be defined for the wireless network interface and the wired network interface of an AP in a residential unit. There may be one or more dedicated VLANs for guests/visitors in the MDU 102. By way of an example, the AP 116, associated with the first user (occupant of the residential unit 104), may be assigned a VLAN 100 as the VLAN ID. Similarly, the AP 118, associated with the second user (occupant of the residential unit 106), may be assigned a VLAN 200 as the VLAN ID. This is further depicted and explained in conjunction with FIG. 6.
[027] In an embodiment, the remote server 128 may also manage SSID portability for the one or more user devices, enabling the users to connect to either a personal SSID or a pre-configured community SSID using a shared credential such as a pre-defined user password (i.e., an enhanced Pre-Shared Key (ePSK)). In an embodiment, upon receiving a personal SSID configuration request from a user device, the remote server 128 may synchronize the pre-defined user password with the community SSID pre-configured for the MDU 102. Further, the remote server 128 may map the pre-defined user password with an appropriate VLAN ID. This mapping ensures that network traffic from ther user device is routed through a correct VLAN regardless of whether a connection is made via the personal SSID or the pre-configured community SSID. The gateway 130 and the one or more switches route the network traffic (also referred to as internet traffic) between the network 100 and appropriate VLANs and the or more user devices in the MDU 102.
[028] Referring now to FIG. 2, an exemplary block diagram of a system 200 configured to manage a SSID portability across networks is depicted, in an embodiment of the disclosure. FIG. 2 is explained in conjunction with FIG. 1. In order to manage the SSID portability across the networks, the system 200 may include a network device 202. In particular, the network device 202 may be configured to manage the SSID portability across the networks. The SSID may be a name assigned to a wireless network that enables user devices (i.e., the one or more user devices) to identify and connect to a specific Wi-Fi AP. Each SSID may be configured with a unique password (i.e., the pre-defined user password) and security settings, and multiple SSIDs can coexist within the same physical network infrastructure. For example, in an MDU (e.g., the MDU 102), each residential unit may include a personal SSID. For example, the personal SSID associated with a residential unit 206 may be ‘unit_206’. Additionally, the common areas, such as a community center 210 associated with the MDU environment may have a community SSID, for example, MDU_community_WiFi.
[029] Examples of the network device 202 may include, but is not limited to, a Wireless Local Area Network (LAN) Controller (WLC), a cloud-based network management server, a local gateway, an edge router, and the like. In an embodiment, the network device 202 may be implemented as a single device or a combination of two or more of the above components, depending on deployment requirements of the MDU.
[030] To manage the SSID portability across the networks, the network device 202 may be configured to receive the personal SSID configuration request from a user device 204 associated with a user belonging to the residential unit 206 within the MDU. Examples of the user device 204 may include, the laptop, the desktop, the tablet, the smart speakers, and the like. In an embodiment, as depicted via FIG. 2, there may be one or more user devices present within the residential unit 206. With reference to FIG. 1, the MDU may correspond to the MDU 102. The residential unit 206 may correspond to the residential unit 104. Further, the user device 204 may correspond to the user device 112A.
[031] In an embodiment, the personal SSID configuration request may include an existing personal SSID and a pre-defined user password associated with the existing personal SSID. For example, the existing personal SSID may be ‘unit_204_WiFi’ and the pre-defined user password may be ‘password234’. In an embodiment, the user may send the personal SSID configuration request via an application installed on the user device 204. The application may be, for example, a mobile application. The user may download the mobile application from a marketplace (e.g., a play store or an app store). In some embodiments, the application may be a web application that is accessible to the user via a web browser of the user device 204.
[032] Upon receiving the personal SSID configuration request, the network device 202 may be configured to automatically synchronize the pre-defined user password associated with the existing personal SSID with a community SSID pre-configured for the MDU. In continuation to above example, the predefined user password, i.e., the ‘password234’ associated with the existing personal SSID ‘unit_204_WiFi’ may be synchronized with the community SSID, i.e., ‘MDU_community_WiFi’. In other words, the ‘password234’ associated with the ‘unit_204_WiFi’ may be linked with the ‘MDU_community_WiFi’, in response to receiving the personal SSID configuration request.
[033] Once the synchronization is done, the network device 102 may enable the user to access the network (e.g., the network 100) via the user device 204. The user device 204-2 may access the network via one of the existing personal SSID or the pre-configured community SSID based on the pre-defined user password. In other words, the user may choose any SSID to connect to the network for accessing the internet for internet-based services using the same pre-defined user password. The pre-defined user password may be the ePSK associated with the residential unit within the MDU.
[034] To facilitate the network access to the user device 204-2, the network device 202 may map the pre-defined user password to a VLAN ID provisioned for an AP 208 serving the residential unit 206. The mapping of the pre-defined user password with the VLAN ID may enable the AP 208 to route the network traffic from the user device 204 through a VLAN associated with the VLAN ID, independent of whether the user device 204 establishes a connection with the network using the existing personal SSID or the pre-configured community SSID.
[035] For example, when the user is present in the community center 210. The user may be able to access the network via the user device 204 by establishing a connection using the pre-configured community SSID. In this case, the network traffic from the user device 204 may be routed through the VLAN associated with the VLAN ID. In particular, an AP 212 may recognize the user device 204 based on the synchronization and applies the mapping provisioned by the network device 202. This routing of the network traffic through the VLAN associated with the VLAN ID ensures that even though the connection occurs through the AP 212 of the community center 210, the user device 204 may be securely tunneled into the same VLAN as in the residential unit 206, maintaining consistent network policies, security, and service quality. As depicted in the FIG. 2, the community center 210 may include one or more user devices associated with one or more users belonging to different residential units present within the MDU. Further, each user device may establish the connection via a corresponding VLAN of an associated residential unit.
[036] In an embodiment, the one or more user devices (e.g., the user device 204-2) may be able to communicate with the network device 202 over a network 214. The network 214 may be any wired or wireless communication network and the examples may include, but may not be limited to, the Internet, Wireless Local Area Network (WLAN), Wi-Fi, Long Term Evolution (LTE), Worldwide Interoperability for Microwave Access (WiMAX), and General Packet Radio Service (GPRS).
[037] Referring now to FIG. 3, an exemplary functional block diagram 300 of the network device 202 configured to manage the SSID portability across the networks is depicted, in an embodiment of the disclosure. FIG. 3 is explained in conjunction with FIGS. 1 and 2. In some embodiment, the network device 202 may correspond to a server. With reference to FIG. 2, the server may be the remote server 128. The network device 202 may be connected to an AP 316. The AP 316 may correspond to the AP 208. It should be noted that the network device 202 may be communicably connected to the AP 204 through one or more other devices, such as gateways, switches, and the like. The AP 316 may be deployed within a residential unit (e.g., the residential unit 206) of the MDU (e.g., the MDU 102). The AP 316 may be communicatively connected to one or more user devices 318 present within the residential unit.
[038] The network device 202 may include a wireless network interface 302, a wired network interface 304, and a processor 306. The network device 202 may further include a memory 308. The memory 308 may be a non-volatile memory or a volatile memory. Examples of the non-volatile memory may include but are not limited to, a flash memory, a Read Only Memory (ROM), a Programmable ROM (PROM), Erasable PROM (EPROM), and Electrically EPROM (EEPROM) memory. Examples of the volatile memory may include but are not limited to, Dynamic Random Access Memory (DRAM), and Static Random-Access memory (SRAM).
[039] The processor 306 is communicatively coupled to each of the wireless network interface 302, the wired network interface 304, and the memory 308. Thus, the network device 202 may facilitate both a wireless connection and a wired connection with the one or more user devices 318 via the AP 316. By way of an example, the one or more user devices 318 may be wirelessly connected to the network device 202 through the wireless network interface 302. Additionally, the one or more user devices 318 may be connected to the network device 202 through a wired connection via the wired network interface 304. In an embodiment, the memory 308 may store instructions that, when executed by the processor 306, may cause the processor 306 to manage the SSID portability across the networks. The memory 308 may further include a receiving module 310, a synchronizing module 312, and an accessibility management module 314.
[040] In order to manage the SSID portability across the networks, initially, the receiving module 310 may be configured to receive the personal SSID configuration request from a user device of the one or more user devices 318. In particular, the user of the user device may send the personal SSID configuration request to the network device 202 via the application installed on the user device. The application, for example, may be the web application or the mobile application. Further, the application installed on the user device may enable the user to perform one or more actions. The one or more actions, for example, may be, enabling or disabling the existing personal SSID, updating the pre-defined user password, selecting a SSID and a frequency bandwidth for connecting one or more user devices to the network, and managing access policies corresponding to the one or more user devices associated with the residential unit. The one or more actions performed by the user of the user device are further explained in detail in conjunction with FIG. 4.
[041] In an embodiment, the personal SSID configuration request may include the existing personal SSID and the pre-defined user password associated with the existing personal SSID. The pre-defined user password may be the ePSK associated with the residential unit within the MDU. For example, a user device, e.g., a laptop, may transmit the personal SSID configuration request to register the existing personal SSID (e.g., “unit_XYZ_WiFi”) along with the pre-defined user password (e.g., password246).
[042] Upon receiving the personal SSID configuration request, the synchronizing module 312 may be configured to synchronize the pre-defined user password associated with the personal SSID with the pre-configured community SSID (e.g., ‘community_WiFi’) that is shared across the common areas within the MDU. For instance, the synchronizing module 312 may ensure that the password ‘password246’ of the existing personal SSID, i.e., unit_XYZ_WiFi associated with the residential unit can also be used for the community SSID, enabling seamless roaming between the residential unit and the common areas. In particular, synchronizing the pre-defined user password associated with the personal SSID with the pre-configured community SSID may correspond to associating the same ePSK of a user’s home network (i.e., the personal SSID) with a community network, i.e., the community SSID. This synchronization may allow the user device to connect to the network seamlessly at both places, i.e., the residential unit or the common areas, without needing a separate password.
[043] Upon synchronization, the accessibility management module 314 may be configured to enable the access of the network to the user device via one of the existing personal SSID or the pre-configured community SSID based on the pre-defined user password, i.e., the ePSK. To enable the access of the network, the accessibility management module 314 may be configured to map the pre-defined user password to the VLAN ID provisioned for the AP 316 serving the residential unit including the one or more user devices 318. The VLAN ID is a unique numerical tag assigned to a network segment that separates and isolates network traffic within a larger physical network. This ensures that the one or more user devices 318 sharing the same VLAN ID communicate as if each user device is on a private network, even when connected through shared infrastructure. In an embodiment, usually, the network administrator (e.g., the MSP administrator) or a network controller (such as a WLAN Controller, a gateway, or a management server) assigns the VLAN ID during network configuration. To guarantee that every residential unit is mapped to a separate, isolated virtual network, the VLAN ID is provisioned during a setup of APs or user profiles. After that, the APs may receive a corresponding VLAN ID, enabling proper routing and tagging of user network traffic. In an embodiment, the mapping of the pre-defined user password with the VLAN ID enables the AP to route the network traffic from the user device through the VLAN associated with the VLAN ID, independent of whether the user device establishes the connection using the existing personal SSID or the pre-configured community SSID.
[044] It should be noted that all such aforementioned modules 310-314 may be represented as a single module or a combination of different modules. Further, as will be appreciated by those skilled in the art, each of the modules 310-314 may reside, in whole or in parts, on one device or multiple devices in communication with each other. In some embodiments, each of the modules 310-314 may be implemented as dedicated hardware circuit comprising custom application-specific integrated circuit (ASIC) or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. Each of the modules 310-314 may also be implemented in a programmable hardware device such as a field programmable gate array (FPGA), programmable array logic, programmable logic device, and so forth. Alternatively, each of the modules 310-314 may be implemented in software for execution by various types of processors (e.g., the processor 306). An identified module of executable code may, for instance, include one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, function, or other construct. Nevertheless, the executables of an identified module or component need not be physically located together, but may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose of the module. Indeed, a module of executable code could be a single instruction, or many instructions, and may even be distributed over several different code segments, among different applications, and across several memory devices.
[045] As will be appreciated by one skilled in the art, a variety of processes may be employed for managing the SSID portability across the networks. For example, the network device 202 may manage the SSID portability across the networks by the processes discussed herein. In particular, as will be appreciated by those of ordinary skill in the art, control logic and/or automated routines for performing the techniques and steps described herein may be implemented by the network device 202 either by hardware, software, or combinations of hardware and software. For example, suitable code may be accessed and executed by the one or more processors on the network device 202 to perform some or all of the techniques described herein. Similarly, application specific integrated circuits (ASICs) configured to perform some, or all of the processes described herein may be included in the one or more processors on the network device 202.
[046] Referring now to FIG. 4, a flowchart of an exemplary method 400 for managing the SSID portability across the networks is illustrated, in an embodiment of the disclosure. FIG. 4 is explained in conjunction with FIGS. 1, 2, and 3.
[047] In order to manage the SSID portability across the network, at step 402, the personal SSID configuration request may be received from the user device. The user device (e.g., the user device 204) may be associated with the residential unit (e.g., the residential unit 206) within the MDU. In an embodiment, the MDU 102 may correspond to a building or a complex including multiple separate residential units or commercial units within a single structure, where each unit is occupied by a different tenant or a user. Additionally, the MDU may include shared common areas and infrastructure, necessitate centralized management of utilities and network services while maintain isolation for individual residential units. For example, the MDU may be the building complex, the residential society, the apartment building, the condominium, the boarding house, the hostel, the hotel, the school, the hospital, the government office, the business complex (such as the business park, the enterprise complex, the enterprise office space, the coworking space, etc.), or similar multi-unit structures.
[048] By way of an example, consider a scenario where a user may have recently shifted to an apartment A1 (i.e., the residential unit) with a residential society (e.g., regency towers). In this scenario, suppose the user may want to configure his user devices for accessing the network for internet-based services. In such scenario, initially, the user may download the application from the marketplace (e.g., the play Store) on one of his user devices, e.g., a smartphone. In some embodiments, the user may directly open the application using the web browser on the smartphone. After downloading the application, the user may register with the application by creating his unique profile by entering user credentials (e.g., a username, a password, an email Identifier (ID), a phone number, an apartment number, etc.).
[049] Once the user is registered, the user may send the personal SSID configuration request. The personal SSID configuration request may include the existing personal SSID and the pre-defined user password associated with the existing personal SSID. The existing personal SSID may be any SSID that the user may have been previously using before shifting to the apartment A1. For example, the existing personal SSID may be ‘user_WiFi’. Further, the pre-defined user password associated with the existing personal SSID may ‘user12345’. The personal SSID configuration request informs the network device 202 about the existing personal SSID and the pre-defined user password of the user. In an embodiment, the pre-defined user password may be the ePSK associated with the residential unit within the MDU. The ePSK may correspond to a unique cryptographic key assigned to a specific user, a user device, or a residential unit within the MDU to enable secure authentication and enhanced network security.
[050] In response to receiving the personal SSID configuration request, at step 404, the pre-defined user password associated with the existing personal SSID may be automatically synchronized with the community SSID pre-configured for the MDU. In continuation to above example, the password ‘user12345’ linked to the existing personal SSID ‘user_WiFi’ may be synchronized with the pre-configured community SSID, e.g., ‘regency_community_WiFi’ available in the residential society ‘regency towers’. As a result, the same pre-defined user password (i.e., ‘user12345’) may now be used by the user via the user device, e.g., the smartphone, to seamlessly connect not only within the apartment A1 but also in the common areas such as the community center, the gym, or the lobby of the residential society. This synchronization may eliminate the need for the user to manually configure or remember a separate password for the community network, thereby ensuring effortless roaming and uninterrupted connectivity across different APs (e.g., the AP associated with the apartment A1, the AP associated with the community center, and the like) within the MDU.
[051] Further, at step 406, the access to the network may be enabled for the user device via one of the existing personal SSID or the pre-configured community SSID based on the pre-defined user password. In other words, the user device may establish the connection with the network to access the internet-based services through either the personal SSID or the pre-configured community SSID using the same pre-defined user password, i.e., the same ePSK. By way of an example, when the user is at the apartment A1, the user device may connect to ‘unit_XYZ_WiFi’ using the pre-defined user password, i.e., ‘user12345’. Similarly, when the user in the community center or the gym, the same user device may connect to ‘regency_community_WiFi’ using the pre-defined user password, i.e., ‘user12345’.
[052] In an embodiment, in order to enable the user device to access the network via one of the personal SSID or the pre-configured community SSID, at step 408, the pre-defined user password, i.e., the ePSK, may be mapped to the VLAN ID that has been provisioned for the AP serving the residential unit, i.e., the apartment A1. The mapping of the pre-defined user password with the VLAN ID may enable the AP to route the network traffic from the user device through the VLAN associated with the VLAN ID, independent of whether the user device establishes the connection using the existing personal SSID or the pre-configured community SSID.
[053] In continuation to the above example, assume that a VLAN ID 25 is provisioned for the apartment A1 within the regency towers. In this scenario, when the user device (e.g., the smartphone) connects to the network using the personal SSID ‘unit_WiFi” at the apartment A1, the ePSK ‘user12345’ may be mapped to the VLAN ID 25, ensuring that all traffic from the user device is routed through the VLAN associated with the VLAN ID 25 dedicated to the apartment A1.
[054] Further, when the user may visit the common area, e.g., the community center, the smartphone of the user may connect via the pre-configured community SSID, i.e., ‘regency_community_WiFi’ using the same ePSK, i.e., ‘user12345’. In this case, an AP in the community center (e.g., an AP 212) may recognize the user device (i.e., the smartphone) and applies the VLAN ID mapping to the ePSK (i.e., the VLAN ID 25 with ‘user12345’) to route the network traffic of the user device via the VLAN associated with the VLAN ID 25. In this scenario, even though a physical connection occurs through a different AP, the network traffic of the user device may be securely tunneled back to the VLAN ID 25, which is dedicated to the apartment A1.
[055] This mapping of the VLAN-ID with the ePSK may ensure that the user continues to experience the same network policies, security configurations, and quality of service (QoS) that would have been available if the user device were connected from within the apartment A1 itself. For example, parental controls configured for the apartment A1, bandwidth limits, or access restrictions to certain resources remain consistently enforced regardless of whether the user device is connected in the apartment A1, the lobby, or the community center of the regency towers.
[056] In this way, the method 400 may ensure that users can move between their personal residential units and shared community areas while enjoying seamless Wi-Fi connectivity. In particular, the method 400 may automatically manage the SSID synchronization and VLAN ID based network traffic routing, preserving both ease of use and network isolation.
[057] In an embodiment, the application installed on the user device, e.g., the smartphone, may enable the user to perform the one or more actions based on the user requirements. For example, the one or more actions may include enabling or disabling the existing personal SSID, updating the pre-defined user password, selecting the SSID and the frequency bandwidth for connecting one or more user devices to the network, and managing access policies corresponding to the one or more user devices associated with the residential unit.
[058] For example, the user may disable their existing personal SSID ‘unit_WiFi’ when leaving for vacation to prevent unauthorized access, and re-enable the existing personal SSID, upon return from the vacation. By way of another example, the user may update the password ‘user12345” to ‘secure@aptA1’ through the application to enhance security after sharing temporary access with a guest. By way of yet another example, the user may configure a smart Television (TV) to connect via the personal SSID on a 5 gigahertz (GHz) bandwidth for high-speed streaming, while the user may connect other IoT devices (e.g., a smart speaker) on the 2.4 GHz bandwidth for better range. By way of yet another example, the user (e.g., a parent) may restrict a user device of their child, e.g., a tablet, to only access educational websites after 9 PM by configuring device-specific policies through the application. Other examples of the access policies may include time-based access control, user device prioritization for bandwidth, content filtering, guest access restrictions, usage quotas, application-specific controls, and the like.
[059] Referring now to FIG. 5, an exemplary flow diagram 500 depicting communication flow between a network device and a user device is illustrated, in an embodiment of the disclosure. FIG. 5 is explained in conjunction with FIGS. 1, 2, 3, and 4. With reference to FIG. 2, the network device may correspond to the network device 202. The user device may correspond to the user device 204.
[060] Initially, at step 502, the user device 204 may send the personal SSID configuration request to the network device 202. The personal SSID configuration request may include the existing personal SSID and the pre-defined user password (i.e., the ePSK) associated with the personal SSID. The personal SSID configuration request may be generated through the application (e.g., the mobile application or the web application) installed on the user device.
[061] Upon receiving the personal SSID configuration request, at step 504, the network device 202 may be configured to automatically synchronize the pre-defined user password with the community SSID that is pre-configured for the MDU. In other words, the network device 202 may be configured to link the pre-defined user password associated with the personal SSID with the pre-configured community SSID. Further, at step 506, the network device 202 may be further configured to map the pre-defined user password (i.e., the ePSK) to the VLAN ID provisioned for the AP serving the residential unit of the user. This mapping of the ePSK to the VLAN ID may ensure that the network traffic from the user device is routed through a correct VLAN (i.e., the VLAN associated with the VLAN ID), regardless of whether the connection is made via the personal SSID or the community SSID.
[062] Once the mapping is created, at step 508, the network device 202 may send a response back to the user device 204 to allow the user device 204 to access the network via one of the personal SSID or the pre-configured community SSID. In other words, the user device 204 may establish the connection with the network using either the personal SSID or the pre-configured community SSID via the same ePSK. In an embodiment, the response, for example, may include a notification ‘connected to the network’. This method 500 may enable the user device 204 to seamlessly access internet-based services and internal resources while maintaining consistent security, isolation, and quality of service across different locations (i.e., the associated residential unit or the common areas) within the MDU.
[063] Referring now to FIG. 6, an exemplary ePSK-VLAN ID database 600 is illustrated, in accordance with an embodiment. FIG. 6 is explained in conjunction with FIGS. 1, 2, 3, 4, and 5. In particular, the ePSK-VLAN ID database 600 mmay correspond to a database associated with the network device 202. In the ePSK-VLAN ID database 600, a first column ‘residential units 602’ may represent a plurality of residential units (e.g., three residential units) present within the MDU. In particular, each row of the first column ‘residential units 602’ may represent a single residential unit represented using a unique residential ID (e.g., Unit A1, Unit A2, Unit A3). Further, each row of a second column ‘personal SSID 604’ may represent a personal SSID associated with the corresponding residential unit. For example, Unit A1 may have a personal SSID as ‘Unit_A1’. Further, each column of a third row ‘ePSK 606’ may represent a pre-defined user password (i.e., the ePSK) associated with the personal SSID of the corresponding residential unit. For example, the pre-defined user password ‘abc123’ may be associated with the personal SSID ‘Unit_A1’ of the residential unit, i.e., ‘Unit A1’. In an embodiment, the personal SSI and the pre-defined user password may be received from the user device 204 as an input via the personal SSID configuration request.
[064] Further, each row of a fourth column ‘AP 608’ may represent an AP provisioned for the corresponding residential unit. In an embodiment, the AP may be provisioned for the corresponding residential unit by the network administrator during an installation or an onboarding phase of the network (e.g., the network 100) associated with the MDU. The provisioning may include associating the AP with a unique VLAN ID assigned to the residential unit. In some embodiments, the AP provisioning may include synchronization of the AP with the ePSK-VLAN ID database 600 such that the AP can authenticate user devices within the residential units 602 using either the personal SSID 604 or the community SSID 612 and route the corresponding network traffic through a VLAN ID 610 assigned to the residential unit. For example, an AP1 may be provisioned for the residential unit ‘Unit A1’.
[065] Further, each row of a fifth column ‘VLAN ID 610’ may indicate the VLAN allocated to the corresponding residential unit. The VLAN ID assigned to each residential unit may enable segregation of the network traffic of the user devices belonging to a corresponding residential unit independent of the personal SSID or the community SSID selected for establishing the connection. For example, the VLAN ID ‘VLAN 10’ may indicate the VLAN allocated to the residential unit ‘Unit A1’. In an embodiment, to enable the segregation of the network traffic associated with the user devices belonging to the corresponding residential unit independent of the personal SSID or the community SSID, the pre-defined user password, i.e., ‘abc123’ may be mapped with the VLAN ID ‘VLAN 10’ provisioned for the ‘AP1’ of the residential unit ‘Unit A1’.
[066] Further, each row of a sixth column ‘community SSID 612’ may represent the community SSID pre-configured for the MDU. The community SSID may be shared across all residential units to provide seamless connectivity. Further, the community SSID may be synchronized with the pre-defined user password associated with the corresponding residential unit. For example, the community SSID ‘Community_WiFi’ may be synchronized with the pre-defined user password, i.e., ‘abc123’ associated with the residential unit ‘Unit A1’. This synchronization of the community SSID with the pre-defined user password may enable the user device to access the network for the internet-based services via one of the existing personal SSID or the pre-configured community SSID.
[067] The disclosed methods and systems may be implemented on a conventional or a general-purpose computer system, such as a personal computer (PC) or server computer. Referring now to FIG. 7, an exemplary computing system 700 that may be employed to implement processing functionality for various embodiments (e.g., as a Single Instruction, Multiple Data (SIMD) device, client device, server device, one or more processors, or the like) is illustrated. Those skilled in the relevant art will also recognize how to implement the invention using other computer systems or architectures. The computing system 700 may represent, for example, a user device such as a desktop, a laptop, a mobile phone, personal entertainment device, Digital Video Recorder (DVR), and so on, or any other type of special or general-purpose computing device as may be desirable or appropriate for a given application or environment. The computing system 700 may include one or more processors, such as a processor 702 that may be implemented using a general or special purpose processing engine such as, for example, a microprocessor, microcontroller or other control logic. In this example, the processor 702 is connected to a bus 704 or other communication medium. In some embodiments, the processor 702 may be an Artificial Intelligence (AI) processor, which may be implemented as a Tensor Processing Unit (TPU), or a graphical processor unit, or a custom programmable solution Field-Programmable Gate Array (FPGA).
[068] The computing system 700 may also include a memory 706 (main memory), for example, Random Access Memory (RAM) or other dynamic memory, for storing information and instructions to be executed by the processor 702. The memory 706 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by the processor 702. The computing system 700 may likewise include a Read Only Memory ("ROM") or other static storage device coupled to bus 704 for storing static information and instructions for the processor 702.
[069] The computing system 700 may also include a storage devices 708, which may include, for example, a media drive 710 and a removable storage interface. The media drive 710 may include a drive or other mechanism to support fixed or removable storage media, such as a hard disk drive, a floppy disk drive, a magnetic tape drive, an Secure Digital (SD) card port, a Universal Serial Bus (USB) port, a micro USB, an optical disk drive, a Compact Disc (CD) or Digital Versatile Disc (DVD) drive (R or Rewritable (RW)), or other removable or fixed media drive. A storage media 712 may include, for example, a hard disk, magnetic tape, flash drive, or other fixed or removable medium that is read by and written to by the media drive 710. As these examples illustrate, the storage media 712 may include a computer-readable storage medium having stored therein particular computer software or data.
[070] In alternative embodiments, the storage devices 708 may include other similar instrumentalities for allowing computer programs or other instructions or data to be loaded into the computing system 700. Such instrumentalities may include, for example, a removable storage unit 714 and a storage unit interface 716, such as a program cartridge and cartridge interface, a removable memory (for example, a flash memory or other removable memory module) and memory slot, and other removable storage units and interfaces that allow software and data to be transferred from the removable storage unit 714 to the computing system 700.
[071] The computing system 700 may also include a communications interface 718. The communications interface 718 may be used to allow software and data to be transferred between the computing system 700 and external devices. Examples of the communications interface 718 may include a network interface (such as an Ethernet or other NIC card), a communications port (such as for example, a USB port, a micro-USB port), Near field Communication (NFC), etc. Software and data transferred via the communications interface 718 are in the form of signals which may be electronic, electromagnetic, optical, or other signals capable of being received by the communications interface 718. These signals are provided to the communications interface 718 via a channel 720. The channel 720 may carry signals and may be implemented using a wireless medium, wire or cable, fiber optics, or other communications medium. Some examples of the channel 720 may include a phone line, a cellular phone link, an Radio Frequency (RF) link, a Bluetooth link, a network interface, a local or wide area network, and other communications channels.
[072] The computing system 700 may further include Input/Output (I/O) devices 722. Examples may include, but are not limited to a display, keypad, microphone, audio speakers, vibrating motor, Light Emitting Diode (LED) lights, etc. The I/O devices 722 may receive input from a user and also display an output of the computation performed by the processor 702. In this document, the terms "computer program product" and "computer-readable medium" may be used generally to refer to media such as, for example, the memory 706, the storage devices 708, the removable storage unit 714, or signal(s) on the channel 720. These and other forms of computer-readable media may be involved in providing one or more sequences of one or more instructions to the processor 702 for execution. Such instructions, generally referred to as "computer program code" (which may be grouped in the form of computer programs or other groupings), when executed, enable the computing system 700 to perform features or functions of embodiments of the present invention.
[073] In an embodiment where the elements are implemented using software, the software may be stored in a computer-readable medium and loaded into the computing system 700 using, for example, the removable storage unit 714, the media drive 710 or the communications interface 718. The control logic (in this example, software instructions or computer program code), when executed by the processor 702, causes the processor 702 to perform the functions of the invention as described herein.
[074] Thus, the disclosed method and system try to overcome the technical problem of managing a SSID portability across networks. The method and system may receive a personal SSID configuration request from a user device associated with a user belonging to a residential unit within a MDU. The personal SSID configuration request may include an existing personal SSID and a pre-defined user password associated with the existing personal SSID. Further, the method and system may automatically synchronize the pre-defined user password associated with the existing personal SSID with a community SSID pre-configured for the MDU, in response to receiving the personal SSID configuration request. Thereafter, the method and system may enable an access of the network to the user device via one of the existing personal SSID or the pre-configured community SSID based on the pre-defined user password.
[075] As will be appreciated by those skilled in the art, the techniques described in the various embodiments discussed above are not routine, or conventional, or well understood in the art. The techniques discussed in the present disclosure for managing the SSID portability across networks address the challenges faced in multi-dwelling deployments requiring seamless access and consistent segmentation. The techniques may include simplified operations. The simplified operations may eliminate separate VLAN-key mapping workflows, i.e., VLAN-ID and ePSK mapping workflows, thereby reducing administrative overhead. The techniques may further provide consistent segmentation. The consistent segmentation may guarantee that the network traffic from both the community SSID and the personal SSID remains within the same VLAN boundary per an AP. The techniques may further provide scalability to enable seamless expansion for large deployments by integrating centralizing password management and VLAN management in one system (e.g., the system 100). The techniques may further provide enhanced security to maintain isolation at a network layer, while offering flexible SSID (i.e., the personal SSID or the community SSID) choices to end users.
[076] The above embodiments are to be understood as illustrative examples of the disclosure. It is to be understood that any feature described in relation to any one embodiment may be used alone, or in combination with other features described, and may also be used in combination with one or more features of any other of the embodiments, or any combination of any other of the embodiments. Furthermore, equivalents and modifications not described above may also be employed without departing from the scope of the disclosure, which is defined in the accompanying claims.
[077] It will be appreciated that, for clarity purposes, the above description has described embodiments of the disclosure with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processors or domains may be used without detracting from the disclosure. For example, functionality illustrated to be performed by separate processors or controllers may be performed by the same processor or controller. Hence, references to specific functional units are only to be seen as references to suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.
[078] Although the present disclosure has been described in connection with some embodiments, it is not intended to be limited to the specific form set forth herein. Rather, the scope of the present disclosure is limited only by the claims. Additionally, although a feature may appear to be described in connection with particular embodiments, one skilled in the art would recognize that various features of the described embodiments may be combined in accordance with the disclosure.
[079] Furthermore, although individually listed, a plurality of means, elements or process steps may be implemented by, for example, a single unit or processor. Additionally, although individual features may be included in different claims, these may possibly be advantageously combined, and the inclusion in different claims does not imply that a combination of features is not feasible and/or advantageous. Also, the inclusion of a feature in one category of claims does not imply a limitation to this category, but rather the feature may be equally applicable to other claim categories, as appropriate. , Claims:CLAIMS
WE Claim:

1. A method (400) for managing a Service Set Identifier (SSID) portability across networks, the method (400) comprising:
receiving (402), by a network device (202), a personal SSID configuration request from a user device (204) associated with a user belonging to a residential unit within a Multi-Dwelling Environment (MDU) (102), wherein the personal SSID configuration request comprises an existing personal SSID and a pre-defined user password associated with the existing personal SSID;
in response to receiving the personal SSID configuration request, automatically synchronizing (404), by the network device (202), the pre-defined user password associated with the existing personal SSID with a community SSID pre-configured for the MDU (102); and
enabling (406), by the network device (202), an access of the network to the user device (204) via one of the existing personal SSID or the pre-configured community SSID based on the pre-defined user password.

2. The method (400) as claimed in claim 1, wherein the pre-defined user password is an enhanced Pre-Shared Key (ePSK) associated with the residential unit within the MDU (102).

3. The method (400) as claimed in claim 1, wherein enabling (406) the access of the network to the user device (204) comprises:
mapping (408), by the network device (202), the pre-defined user password to a Virtual Local Area Network (VLAN) Identifier (ID) provisioned for an Access Point (AP) serving the residential unit.

4. The method (400) as claimed in claim 3, wherein mapping the pre-defined user password with the VLAN ID enables the AP to route network traffic from the user device (204) through a VLAN associated with the VLAN ID, independent of whether the user device (204) establishes a connection using the existing personal SSID or the pre-configured community SSID.

5. The method (400) as claimed in claim 1, wherein the personal SSID configuration request is received via an application installed on the user device (204), and wherein the application allows the user to perform one or more actions based on user requirements.

6. The method (400) as claimed in claim 5, wherein the one or more actions comprises enabling or disabling the existing personal SSID, updating the pre-defined user password, selecting a SSID and a frequency bandwidth for connecting one or more user devices to the network, and managing access policies corresponding to the one or more user devices associated with the residential unit.

7. A network device (202) for managing a Service Set Identifier (SSID) portability across networks, the network device (202) comprising:
a processor (306); and
a memory (308) communicatively coupled to the processor (306), wherein the memory (308) stores processor instructions, which when executed by the processor (306), cause the processor (306) to:
receive (402) a personal SSID configuration request from a user device (204) associated with a user belonging to a residential unit within a Multi-Dwelling Environment (MDU) (102), wherein the personal SSID configuration request comprises an existing personal SSID and a pre-defined user password associated with the existing personal SSID;
in response to receiving the personal SSID configuration request, automatically synchronize (404) the pre-defined user password associated with the existing personal SSID with a community SSID pre-configured for the MDU (102); and
enable (406) an access of the network to the user device (204) via one of the existing personal SSID or the pre-configured community SSID based on the pre-defined user password.

8. The network device (202) as claimed in claim 7, wherein the pre-defined user password is an enhanced Pre-Shared Key (ePSK) associated with the residential unit within the MDU (102).

9. The network device (202) as claimed in claim 7, wherein, to enable (406) the access of the network to the user device (204), the processor instructions, on execution, cause the processor (306) to:
map (408) the pre-defined user password to a Virtual Local Area Network (VLAN) Identifier (ID) provisioned for an Access Point (AP) serving the residential unit.

10. The network device (202) as claimed in claim 9, wherein mapping the pre-defined user password with the VLAN ID enables the AP to route network traffic from the user device (204) through a VLAN associated with the VLAN ID, independent of whether the user device (204) establishes a connection using the existing personal SSID or the pre-configured community SSID.

11. The network device (202) as claimed in claim 7, wherein the personal SSID configuration request is received via an application installed on the user device (204), and wherein the application allows the user to perform one or more actions based on user requirements.

12. The network device (202) as claimed in claim 11, wherein the one or more actions comprises enabling or disabling the existing personal SSID, updating the pre-defined user password, selecting a SSID and a frequency bandwidth for connecting one or more user devices to the network, and managing access policies corresponding to the one or more user devices associated with the residential unit.

13. A system (200) for managing a Service Set Identifier (SSID) portability across networks, the system (200) comprising:
a server configured to:
receive (402) a personal SSID configuration request from a user device (204) associated with a user belonging to a residential unit within a Multi-Dwelling Environment (MDU) (102), wherein the personal SSID configuration request comprises an existing personal SSID and a pre-defined user password associated with the existing personal SSID; and
in response to receiving the personal SSID configuration request, automatically synchronize (404) the pre-defined user password associated with the existing personal SSID with a community SSID pre-configured for the MDU (102); and
an Access Point (AP) communicatively coupled to the server, wherein the AP enables (406) the user device (204) to access the network through the server via one of the existing personal SSID or the pre-configured community SSID based on the pre-defined user password.

14. The system (200) as claimed in claim 13, wherein the pre-defined user password is an enhanced Pre-Shared Key (ePSK) associated with the residential unit within the MDU (102).

15. The system (200) as claimed in claim 13, wherein, to enable (406) the access of the network to the user device (204), the server is configured to:
map (408) the pre-defined user password to a Virtual Local Area Network (VLAN) Identifier (ID) provisioned for the AP serving the residential unit.

16. The system (200) as claimed in claim 15, wherein mapping the pre-defined user password with the VLAN ID enables the AP to route network traffic from the user device (204) through a VLAN associated with the VLAN ID, independent of whether the user device (204) establishes a connection using the existing personal SSID or the pre-configured community SSID.

17. The system (200) as claimed in claim 13, wherein the personal SSID configuration request is received via an application installed on the user device (204), and wherein the application allows the user to perform one or more actions based on user requirements.

18. The system (200) as claimed in claim 17, wherein the one or more actions comprises enabling or disabling the existing personal SSID, updating the pre-defined user password, selecting a SSID and a frequency bandwidth for connecting one or more user devices to the network, and managing access policies corresponding to the one or more user devices associated with the residential unit.