US9271329B2 - Systems and methods for enabling stations to connect to wireless hotspots using non-unicode service set identification information - Google Patents

Systems and methods for enabling stations to connect to wireless hotspots using non-unicode service set identification information Download PDF

Info

Publication number
US9271329B2
US9271329B2 US13/750,915 US201313750915A US9271329B2 US 9271329 B2 US9271329 B2 US 9271329B2 US 201313750915 A US201313750915 A US 201313750915A US 9271329 B2 US9271329 B2 US 9271329B2
Authority
US
United States
Prior art keywords
character set
field
wireless
access point
information element
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related, expires
Application number
US13/750,915
Other languages
English (en)
Other versions
US20130201980A1 (en
Inventor
Jammula Rahul
Deepak Jindal Kumar
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US13/750,915 priority Critical patent/US9271329B2/en
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to KR1020147024810A priority patent/KR20140123086A/ko
Priority to EP13705669.3A priority patent/EP2813106B1/en
Priority to PCT/US2013/024833 priority patent/WO2013119599A1/en
Priority to JP2014555846A priority patent/JP6239530B2/ja
Priority to CN201380007980.1A priority patent/CN104094641B/zh
Assigned to QUALCOMM INCORPORATED reassignment QUALCOMM INCORPORATED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KUMAR, Jindal Deepak, RABUL, JAMMULA
Publication of US20130201980A1 publication Critical patent/US20130201980A1/en
Assigned to QUALCOMM INCORPORATED reassignment QUALCOMM INCORPORATED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KUMAR, DEEPAK JINDAL, RAHUL, Jammula
Application granted granted Critical
Publication of US9271329B2 publication Critical patent/US9271329B2/en
Expired - Fee Related legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • G06F17/2223—
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/12—Use of codes for handling textual entities
    • G06F40/126—Character encoding
    • G06F40/129—Handling non-Latin characters, e.g. kana-to-kanji conversion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]

Definitions

  • the present teachings relate to systems and methods for enabling stations to connect to wireless hotspots using non-Unicode service set identification information.
  • the present teachings more particularly relate to platforms and techniques for enabling the specification of a character set which a wireless router or other WiFiTM access point is using to broadcast available service sets to wireless devices in range of that access point
  • This default processing of character sets results in anomalous behavior if the SSID is encoded in a coding format other than Unicode.
  • wireless routers or other access point devices may be encoded in non-Unicode formats in many regions of the world, including as noted China, as well as other locations.
  • the SSID information is presented in an SSID Information Element identified by Element Id: 0, in a structure which is illustrated in FIG. 1 .
  • the SSID IE shown is mandated by industry standards published by the Institute of Electrical and Electronics Engineers, or “IEEE.”. As per this SSID IE which is defined by the IEEE standards, the only significant information conveyed is the SSID name and the length of the SSID. There is no additional information that is available to assist in identifying the character set, associated language, or other extended characteristics of a WiFiTM access point.
  • a scenario can likewise be considered in which there are two access points transmitting and announcing their SSID's, which might be in English and Chinese, respectively, within a local broadcast range.
  • the SSID IE's broadcast the SSID's, but the English SSID is encoded according to ASCII code set, whereas the Chinese SSID might be encoded according to the official Guo Biou (GB) code set promulgated for Chinese character processing.
  • GB Guo Biou
  • the smart phone supplicant module which interfaces between the JavaTM framework and the underlying WLAN driver and other transceiver logic, receives these two SSID IE's from the WLAN interface.
  • the supplicant module passes both of them on to the AndroidTM graphical user interface (GUI) framework.
  • GUI graphical user interface
  • That GUI framework handles the responsibility of appropriately decoding the SSID name and displaying it in the smart phone's WiFiTM scan window or other display.
  • the Chinese SSID which is encoded in the separate GB code is assumed to be represented UTF-8 compatible code, causing it to be decoded incorrectly by the AndroidTM JavaTM framework, since that framework attempts to decode the GB code assuming the character set information is available in UTF-8 format.
  • This information can be passed to the AndroidTM operating system, JavaTM framework, and/or other logic which can then accurately and reliably parse the SSID based on a variety of different character coding schemes, providing visibility into WiFiTM networks by users of a variety of languages.
  • FIG. 1 illustrates a service set information element as used in known WiFiTM systems
  • FIG. 2 illustrates an overall wireless WiFiTM network in which systems and methods for enabling stations to connect to wireless hotspots using non-Unicode service set identification information can operate, according to various embodiments;
  • FIG. 3 illustrates features of an individual smart phone or other WiFiTM station, according to various embodiments
  • FIGS. 4A-4C illustrate various character set encoding schemes that can be used in stations to connect to wireless hotspots using non-Unicode service set identification information, in which an SSID IE structure is extended according to the present teachings, according to various embodiments;
  • FIGS. 5A and 5B illustrate possible formats that can be adopted for allowing stations to connect to wireless hotspots using non-Unicode service set identification information, in which a vendor-specific IE is added to the beacon frame that can carry the character set encoding information, according to various embodiments;
  • FIG. 6 illustrates overall character set encoding operations that can be used in configuring stations to connect to wireless hotspots using non-Unicode service set identification information, according to various embodiments.
  • FIG. 7 illustrates exemplary hardware, software, and other resources that can be used in enabling stations to connect to wireless hotspots using non-Unicode service set identification information, according to various embodiments.
  • Embodiments of the present teachings relate to systems and methods for enabling stations to connect to wireless hotspots using non-Unicode service set identification information. More particularly, embodiments relate to platforms and techniques for generating and embedding native character set information into the beacon information broadcast by wireless routers and/or other access points in a WiFiTM and/or other wireless networks. According to aspects, an identification of the character set, and/or associated language, used by an access point can be inserted into SSID information elements and/or otherwise built into extended encoding schemes transmitted by the access point broadcasting to one or more smart phones and/or other stations within operating range of that wireless device.
  • Each receiving smart phone or other station can be configured to locate and decode the embedded character set information in the beacon, to allow a user to view and select access points in their intended operating language. That can be accomplished whether that character set and/or language is encoded in the Unicode format, or other formats. Enhanced portability, reliability, and usability of WiFiTM routers and operations can thereby be achieved.
  • FIG. 2 illustrates an overall network environment 100 in which systems and methods for enabling stations to connect to wireless hotspots using non-Unicode service set identification information can operate, according to aspects.
  • an access point 108 can broadcast a wireless network signal to a set of stations 102 within range.
  • the access point 108 can be or include a wireless router, hub, extender, and/or other network access point, and can in embodiments be configured to operate using the WiFiTM wireless standard, specified by IEEE specification 802.11b, 802.11g, 802.11n, and/or other existing or future standards.
  • the access point 108 when operating as a WiFiTM access point, can for instance operate in the 2.4 GHz frequency band. It will be appreciated however that in implementations, other wireless access standards, channels, protocols, and/or frequencies can be used.
  • each device or station in the set of stations 102 can be or include any wireless-network enabled device, such as a WiFiTM-equipped smart phone, touch pad device, media player device, GPS (global positioning system) device, and/or other device or network-enabled platform.
  • each individual station 118 in the set of stations 102 can be configured with one or more hardware, software, service, and/or other resources.
  • a station 118 can comprise various hardware, software, and other resources, including an operating system 112 , a display 110 which can for instance be or include a graphical user interface (GUI) of the operating system 112 , and a radio frequency antenna 150 (or multiple antennas).
  • GUI graphical user interface
  • the operating system 112 can comprise a mobile device operating system such as the AndroidTM operating system available from Google Inc., Mountain View, Calif., U.S. or others.
  • the operating system 112 as noted can comprise a graphical user interface (GUI), as well as file management, power management, communications, security, and/or other logic, services, and/or resources to operate each station 118 .
  • GUI graphical user interface
  • each individual station 118 can likewise host applications, services, logic, and/or modules including a supplicant module 114 used to establish connections to access points and/or other channels.
  • Each individual station 118 can likewise incorporate a JavaTM framework 116 , used to support the execution of JavaTM-based services and applications on the station 118 .
  • any one or more of the set of stations 102 can in general be connected, or available to be connected, to the access point 108 at one time.
  • the access point 108 can broadcast beacon information 104 to the set of stations 102 .
  • the beacon information 104 can in general include a service set identification (SSID) information element (IE) 106 indicating the name, connection type, occupied and/or available channels, and other network information and services provided by the access point 108 to any station within its wireless connection range.
  • SSID service set identification
  • IE information element
  • the beacon information 104 broadcast by the access point 108 can comprise not just the standard SSID IE 106 , but also character set information 120 indicating or encoding the type of character set formatting or encoding used to broadcast the SSID IE 106 , and/or other information.
  • each smart phone or other station 118 in the set of stations 102 can receive, decode, and display that information about the access point 108 , regardless of whether the SSID IE 106 is stored or encoded in the Unicode format, and/or other proprietary or distinct character set encoding schemes.
  • the character set information 120 which identifies the character set encoding scheme can be embedded in the beacon information 104 in various ways, according to various embodiments. However, it will be appreciated that all implementations permit the use of non-Unicode or propriety character sets by the access point 108 , and the recognition of those character sets by the set of stations 102 . More specifically and as for instance illustrated in FIGS. 4A-4C , the character set information 120 can be encoded within the standard SSID IE 106 format by either adding additional fields, or “borrowing” or “stealing” selected bits from the existing fields, of that information element.
  • the character set information 120 and/or portions thereof can be encoded in an additional field labeled “Encoding” added to the SSID IE 106 .
  • the Encoding field can be stored in a variety of formats and/or lengths, such as a one-byte or two-byte value indicating the character set to be used, for instance, via a look-up table and/or other reference. According to aspects, and as for example further shown in FIG.
  • the character set information 120 and/or portions thereof can instead be encoded in selected bits of the existing Length (L) field (this legacy 1 byte Length (L) field may also be referred to herein as an encoding (E) and length (L) field, since it carries both encoding and length information) of the standard SSID IE 106 .
  • the first two bits of the encoding (E) and length (L) field can be re-assigned or re-interpreted as the specification of the character set used by the access point 108 , thereby allowing four independent character sets to be specified and used.
  • the character set information 120 and/or portions thereof can alternatively be encoded in last two bits of the encoding (E) and length (L) field.
  • E encoding
  • L length
  • the use of encoding schemes or types as illustrated in FIGS. 4B and 4C result in particularly compact encoding formats, since the overall length of the SSID IE 106 is not enlarged to accommodate the character set information 120 . It will be appreciated, however, that other bit combinations and/or positions can be used to encode the character set information 120 , as desired.
  • the character set information 120 can also be encoded or embedded in other positions in the SSID IE 106 or related information, such as a vendor-specific information element (IE) 122 which is added to or specified in the beacon information 104 , but which is not incorporated in the base SSID IE 106 .
  • the vendor-specific information element (IE) 122 can be configured as a Cisco-compatible extension (CCX), illustratively labeled “Type 1,” having an illustrative format as shown in that figure, including an Element ID field, a length field, an organizationally unique identifier (OUI) field, a version field, and a separate CCX version field.
  • CCX Cisco-compatible extension
  • Type 1 having an illustrative format as shown in that figure, including an Element ID field, a length field, an organizationally unique identifier (OUI) field, a version field, and a separate CCX version field.
  • the vendor-specific information element (IE) 122 can be configured in a non-CCX based format, labeled as “Type 2,” including an Element ID field, a length field, an organizationally unique identifier (OUI) field, and a data field (illustratively two bytes). Any one or more of the foregoing fields or combinations of fields, and/or other fields or combinations can be used consistent with implementations shown in FIGS. 5A and 5B to encode or specify the character set used by the access point 108 and/or SSID IE 106 being broadcast by that access point, which can again be identified or determined via a look-up table and/or other reference.
  • implementations as shown in FIGS. 5A and 5B may hold advantages in terms of backward compatibility with existing WiFiTM access point and station hardware. This can be the case because devices configured according to the existing industry standards can continue to operate in the usual or expected manner, even when those devices operate in the presence of platforms equipped with encoding schemes according to the present teachings. More particularly, implementations using a vendor-specific information element (IE) 122 enjoy an advantage compared to other solutions involving the extension of the SSID IE 106 , since backward compatibility is ensured. In implementations using a vendor-specific information element (IE) 122 , various scenarios can be compatibly or transparently handed, from the perspective of a user of a station 118 or other device.
  • IE vendor-specific information element
  • a station 118 which is not adapted or upgraded according to the present teachings and/or cannot parse or understand the vendor-specific information element (IE) 122 which has encoding information may be referred to as an “old station.”
  • a station which is adapted or upgraded to use features of the present teachings and can parse or understand the vendor-specific information element (IE) 122 which has character set encoding information may be referred to as a “new station.”
  • an access point which is not adapted or upgraded to support features of sending a vendor-specific information element (IE) 122 with encoded character set information may be referred to as an “old access point,” while an access point which is adapted or upgraded to support features of sending a vendor-specific information element (IE) 122 with encoded character set information can be referred to as a “new access point.”
  • the new station 118 can parse the encoding information located in the vendor-specific information element (IE) 122 , as described herein.
  • IE vendor-specific information element
  • the access point 108 therefore transmits the beacon information 104 incorporating character set information 120 including encoding information which serves to identify the encoding logic, character set, language, and/or other formatting or logic used by the access point 108 to pack the SSID IE 106 in the beacon information 104 .
  • the supplicant module 114 of any individual receiving station 118 can then parse the correct data field from the appropriate information element and/or field of the beacon information 104 (e.g., extended or altered fields of the standard SSID IE 106 and/or vendor-specific information element (IE) 122 ) which gives the encoding value.
  • IE vendor-specific information element
  • the supplicant module 114 can then pass this encoding value to the JavaTM framework 116 , along with the SSID data, including the constituent fields and/or IEs that it communicates to the JavaTM framework 116 in current implementations not employing platforms and techniques described herein.
  • the JavaTM framework 116 can then decode the raw SSID data based on the specified encoding information. According to aspects, once a character set is identified, the JavaTM framework 116 can for instance look up and/or otherwise retrieve that character set, for instance, from local memory or storage, and/or from remote sources.
  • the JavaTM framework 116 can accordingly display the SSID and/or other information to the user via display 110 of the station 118 in a properly decoded character set and/or language.
  • the JavaTM framework 116 may only understand Unicode (UTF-8 or other) encoding, so that any ultimately identified character set encoding has to be eventually decoded and/or translated to equivalent UTF-8 code set.
  • the JavaTM framework 116 of the station 118 can then display the appropriate fonts in the display 110 via a graphical user interface (GUI) screen and/or other interface, assuming support for necessary fonts is in place.
  • GUI graphical user interface
  • the JavaTM framework 116 can exchange the necessary information with the supplicant module 114 via a “SET_NETWORK” or other command. Based on the information passed to the supplicant module 114 , the supplicant module 114 will be able to choose the correct access point 108 from the list of scanned access points available to the station 118 which the supplicant module 114 is aware of. The supplicant module 114 can then for instance transmit an authorization frame, the first frame that gets exchanged between a station and access point when a new connection is initiated according to WiFiTM standards, essentially ensuring the connection of the station 118 to the access point 108 .
  • the user of station 118 is thereby enabled to not only see the access point 108 in the scan window in the correct language, but is also ensured to be able to successfully connect to the access point 108 , as well.
  • Those abilities represent a significant improvement over the non-standard language scenario in systems not equipped with platforms and techniques described herein.
  • the systems and methods discussed herein are not limited to the above types or categories of use case scenarios, but can also be implemented in any related or other scenarios where association activities or other operations on a wireless network (WLAN or other) system become paralyzed or are otherwise affected because of the use of a non-Unicode character set. For instance, consider an access point 108 which is configured with a non-English SSID and which is configured or established as having a “Hidden” status. Such an access point 108 cannot transmit beacon information 104 .
  • a station in the set of stations 102 desiring access will be forced to send a Unicast Probe Request, with the appropriate SSID information in an encoding format understandable to the access point 108 , to be able to attempt to connect to the access point 108 . If the station can not send a Probe Request with SSID information encoded in the format expected by the access point 108 , then the requesting station may never be able to connect to the access point 108 .
  • the supplicant module 114 can be configured to incorporate character set encoding, platforms, and/or techniques as described herein.
  • GUI graphical user interface
  • beacon information 104 not just the beacon information 104 itself, but also any Probe Request transmitted by a station 118 , resulting Probe Response frames from the access point 118 , and/or other frames, fields, data, elements, and/or information can include the character set encoding information 120 , the SSID information identifying or employing the correct encoding set, and/or other associated information or data.
  • WiFiTM hotspots become more common in different regions of the world, and as more users move to smart phones in regions where English is not the native language. Smart phone users and users of other devices can therefore connect to an available access point, regardless of what language the SSID is configured in.
  • FIG. 6 illustrates a flowchart of character set encoding and other processing that can be performed in systems and methods for enabling stations to connect to wireless hotspots using non-Unicode service set identification information, according to aspects.
  • processing can begin.
  • an access point 108 can be configured with one or more extended character set encoding schemes encoded in the beacon information 104 , according to various implementations of the present teachings.
  • the access point 108 can broadcast the beacon information 104 , including character set encoding information 120 , to a set of stations 102 within range of the access point 108 .
  • the type of character set encoding and/or other information can be identified in a receiving station 118 (or stations), using the identified extended encoding scheme.
  • the beacon information 104 can contain fields and/or information elements, including those illustrated herein, indicating an encoding of character sets in the SSID IE 106 , and/or in a vendor-specific information element (IE) 122 .
  • the receiving station 118 (or stations) can decode and/or display the SSID IE 106 of the broadcasting access point 108 , for instance using the supplicant module 114 , JavaTM framework 116 , operating system 112 , and/or other software, logic, module, and/or service.
  • the SSID IE 106 and/or other information can be displayed in the character set and/or language indicated in the character set encoding information 120 , for instance in a scan window of station 118 .
  • the access point 108 can receive a user selection, authorization frame from the communicating station 118 (or stations), and/or other “handshake” or transaction between the access point 108 and communicating station 118 .
  • a network connection for instance, to the Internet and/or other public or private network, can be established via the selected access point 108 .
  • processing can repeat, return to a prior processing point, jump to a further processing point, or end.
  • FIG. 7 illustrates various hardware, software, and other resources that can be used in implementations of enabling stations to connect to wireless hotspots using non-Unicode service set identification information, according to embodiments.
  • the access point 108 can comprise features of a processor 142 communicating with memory 144 , such as electronic random access memory, as well as with a network interface, such as an EthernetTM and/or other wired or wireless connection to the Internet and/or other networks.
  • the processor 140 can be programmed or configured to carry out character set encoding operations, network connectivity operations, and other operations according to the present teachings.
  • the processor 140 can also communicate with a local data store 146 , such as a local hard disk and/or other storage, as well as to a wireless interface 148 , such as a WiFiTM-compatible chipset, including radio frequency chip set(s) and associated hardware and software, which may be connected to a radio frequency antenna 152 (or multiple antennas).
  • a local data store 146 such as a local hard disk and/or other storage
  • a wireless interface 148 such as a WiFiTM-compatible chipset, including radio frequency chip set(s) and associated hardware and software, which may be connected to a radio frequency antenna 152 (or multiple antennas).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Artificial Intelligence (AREA)
  • Computational Linguistics (AREA)
  • General Health & Medical Sciences (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
US13/750,915 2012-02-06 2013-01-25 Systems and methods for enabling stations to connect to wireless hotspots using non-unicode service set identification information Expired - Fee Related US9271329B2 (en)

Priority Applications (6)

Application Number Priority Date Filing Date Title
US13/750,915 US9271329B2 (en) 2012-02-06 2013-01-25 Systems and methods for enabling stations to connect to wireless hotspots using non-unicode service set identification information
EP13705669.3A EP2813106B1 (en) 2012-02-06 2013-02-06 Systems and methods for enabling stations to connect to wireless hotspots using non-unicode service set identification information
PCT/US2013/024833 WO2013119599A1 (en) 2012-02-06 2013-02-06 Systems and methods for enabling stations to connect to wireless hotspots using non-unicode service set identification information
JP2014555846A JP6239530B2 (ja) 2012-02-06 2013-02-06 非ユニコード・サービス・セット識別情報を使用して局が無線ホットスポットに接続することを可能にするためのシステムおよび方法
KR1020147024810A KR20140123086A (ko) 2012-02-06 2013-02-06 스테이션들이 비-유니코드 서비스 세트 식별 정보를 사용하여 무선 핫스팟들에 연결하는 것을 가능하게 하기 위한 시스템들 및 방법들
CN201380007980.1A CN104094641B (zh) 2012-02-06 2013-02-06 用于使各站能连接到使用非统一码服务集标识信息的无线热点的系统和方法

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201261595291P 2012-02-06 2012-02-06
US13/750,915 US9271329B2 (en) 2012-02-06 2013-01-25 Systems and methods for enabling stations to connect to wireless hotspots using non-unicode service set identification information

Publications (2)

Publication Number Publication Date
US20130201980A1 US20130201980A1 (en) 2013-08-08
US9271329B2 true US9271329B2 (en) 2016-02-23

Family

ID=48902840

Family Applications (1)

Application Number Title Priority Date Filing Date
US13/750,915 Expired - Fee Related US9271329B2 (en) 2012-02-06 2013-01-25 Systems and methods for enabling stations to connect to wireless hotspots using non-unicode service set identification information

Country Status (6)

Country Link
US (1) US9271329B2 (enrdf_load_stackoverflow)
EP (1) EP2813106B1 (enrdf_load_stackoverflow)
JP (1) JP6239530B2 (enrdf_load_stackoverflow)
KR (1) KR20140123086A (enrdf_load_stackoverflow)
CN (1) CN104094641B (enrdf_load_stackoverflow)
WO (1) WO2013119599A1 (enrdf_load_stackoverflow)

Families Citing this family (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20130125276A (ko) * 2012-05-08 2013-11-18 한국전자통신연구원 Ｓｈｏｒｔ Ｐｒｏｂｅ Ｒｅｓｐｏｎｓｅ를 이용한 효율적인 스캐닝 방법
US9585109B2 (en) 2013-03-14 2017-02-28 Vivint, Inc. Simultaneous channel switching within a mesh network
GB201319591D0 (en) * 2013-11-06 2013-12-18 Microsoft Corp Network Access
CN104661285B (zh) * 2013-11-18 2018-06-01 联想(北京)有限公司 一种信息的处理方法、装置及电子设备
GB2522044A (en) * 2014-01-10 2015-07-15 Samsung Electronics Co Ltd Provisioning apparatus and methods therefor
US9860762B2 (en) 2014-03-11 2018-01-02 Vivint, Inc. Simultaneous channel switching within a mesh network
CN104932873B (zh) * 2014-03-19 2018-05-25 联发科技（新加坡）私人有限公司 档案处理方法以及电子装置
CN104540126A (zh) * 2014-05-16 2015-04-22 生迪光电科技股份有限公司 多个wi-fi设备自动接入指定接入点ap的方法及系统
CN104135754A (zh) * 2014-08-05 2014-11-05 广东欧珀移动通信有限公司 一种添加并连接隐藏中文wifi热点的方法及装置
US9311811B1 (en) 2014-10-08 2016-04-12 Google Inc. Alarm profile for a fabric network
CN104283642B (zh) * 2014-10-22 2018-07-24 小米科技有限责任公司 无线局域网中发布服务集标识ssid的方法及装置
US9820218B2 (en) * 2014-12-05 2017-11-14 Qualcomm Incorporated Systems and methods for efficient access point discovery
CN104853401B (zh) * 2015-04-20 2019-01-04 小米科技有限责任公司 控制接入的方法和装置
CN104853403B (zh) * 2015-04-20 2019-02-12 小米科技有限责任公司 控制智能设备接入的方法和装置
CN105282823A (zh) * 2015-09-18 2016-01-27 普联技术有限公司 智能设备的网络接入方法及装置
CN105163372A (zh) * 2015-09-18 2015-12-16 普联技术有限公司 智能家电的网络接入方法及装置
CN105430712A (zh) * 2015-10-30 2016-03-23 上海斐讯数据通信技术有限公司 服务集标识的编码方法、编码装置、解码方法及解码装置
US9838956B2 (en) * 2016-03-02 2017-12-05 Sr Technologies, Inc. Identification of mobile nodes in WLAN communications
CN105933899B (zh) * 2016-04-14 2019-07-09 北京小米移动软件有限公司 无线接入点的接入方法和装置
CN106068028B (zh) * 2016-07-04 2019-09-20 青岛海信宽带多媒体技术有限公司 终端中处理无线网络名称乱码的方法和终端
US20200014656A1 (en) * 2017-03-13 2020-01-09 Huawei Technologies Co., Ltd. Service Set Identifier Processing Method and Apparatus, and Terminal
CN107708183B (zh) * 2017-10-23 2021-06-01 Oppo广东移动通信有限公司 解码算法确定方法、装置、终端及存储介质
CN107797976A (zh) * 2017-10-23 2018-03-13 广东欧珀移动通信有限公司 解码算法确定方法、装置、终端及存储介质
CN107729302B (zh) * 2017-10-23 2021-10-15 Oppo广东移动通信有限公司 解码算法确定方法、装置、终端及存储介质
CN108235249B (zh) * 2018-01-16 2020-11-17 Oppo广东移动通信有限公司 编码方式的确定方法、装置、存储介质及终端
CN109211259B (zh) * 2018-09-28 2021-08-10 Oppo广东移动通信有限公司 轨迹路线的显示方法、装置、终端及存储介质
CN112672400A (zh) * 2020-12-15 2021-04-16 成都新潮传媒集团有限公司 数据交互控制方法、设备及存储介质
EP4398546A4 (en) * 2021-09-01 2025-05-07 LG Electronics Inc. DISPLAY DEVICE AND WIRELESS CONNECTION CONTROL METHOD THEREFOR

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030215074A1 (en) 2002-05-14 2003-11-20 Wrobel Charles C. Dual language caller ID with asian language support
US7415500B2 (en) 1999-08-04 2008-08-19 Aol Llc Facilitating negotiations between users of a computer network through messaging communications enabling user interaction
US20090175250A1 (en) * 2004-10-20 2009-07-09 Saurabh Mathur Method for mobile terminal access to wireless lan based on access point services and service parameters
US7657234B2 (en) 2004-02-05 2010-02-02 Qualcomm Incorporated Transparent broadcast services for a multi-mode wireless device
US20120257536A1 (en) * 2011-04-08 2012-10-11 Research In Motion Limited Configuring Mobile Station According to Type of Wireless Local Area Network (WLAN) Deployment

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005184681A (ja) * 2003-12-22 2005-07-07 Nec Corp 携帯端末機器とそれを用いた通信システム
JP2008219482A (ja) * 2007-03-05 2008-09-18 Nec Corp 無線パケット通信システムにおける情報配信システム、情報配信方法及び情報配信装置
EP2372987B1 (en) * 2010-04-02 2013-07-17 Research In Motion Limited Solving character display ambiguities

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7415500B2 (en) 1999-08-04 2008-08-19 Aol Llc Facilitating negotiations between users of a computer network through messaging communications enabling user interaction
US20030215074A1 (en) 2002-05-14 2003-11-20 Wrobel Charles C. Dual language caller ID with asian language support
US7657234B2 (en) 2004-02-05 2010-02-02 Qualcomm Incorporated Transparent broadcast services for a multi-mode wireless device
US20090175250A1 (en) * 2004-10-20 2009-07-09 Saurabh Mathur Method for mobile terminal access to wireless lan based on access point services and service parameters
US20120257536A1 (en) * 2011-04-08 2012-10-11 Research In Motion Limited Configuring Mobile Station According to Type of Wireless Local Area Network (WLAN) Deployment

Non-Patent Citations (9)

* Cited by examiner, † Cited by third party
Title
"Android-Issue 8035-WiFi association fails for SSIDs with spaces them", Apr. 29, 2010, XP055063104, Retrieved from the Internet: URL:http://code.google.com/p/android/issues/detail?id=8035&can=1&q=ssid%20utf&colspec=ID%20Type%20Status%200wner%20Summary%20Stars [retrieved on Sep. 3, 2015].
3GPP TS 23.038, "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Alphabets and Language-specific Information," (Release 10), V10.0.0, Mar. 2011, 56 Pages.
3GPP TS 23.041, "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Technical realization of Cell Broadcast Service (CBS)," (Release 10), V10.3.0, Mar. 2012, 51 Pages.
Chromium-Issue 190935-non-ASCII Wifi SSID is not displayed correctly, Nov. 2, 2010, XP055063103, Retrieved from the Internet: URL:http://code.google.com/p/chromium/issues/detail?id=190935&can=1&q=unicode%20SSID&colspec=ID%20Pri%20M%20Iteration%20ReleaseBlock%20Cr%20Status%200wner%20Summary%200S%20Modified [retrieved on Sep. 3, 2015].
Chromium-OS, "Issue 8563: non-ASCII Wifi SSID is not displayed correctly-the open source project behind google chrome OS", Google Project Hosting, 2011, [retrieved on Dec. 19, 2012]. Retrieved from the Internet:, 5 pages.
Chromium-OS, "Issue 8563: non-ASCII Wifi SSID is not displayed correctly-the open source project behind google chrome OS", Google Project Hosting, 2011, [retrieved on Dec. 19, 2012]. Retrieved from the Internet:< URL: http://code.google.com/p/chromium-os/issues/detailed?id=8563>, 5 pages.
International Search Report and Written Opinion-PCT/US2013/024833-ISA/EPO-May 31, 2013.
Research in Motion, "Clarifying the requirements for the CJKV language ambiguity with the NITZ feature", C1-102429, 3GPP CT1-65 Meeting, Jun. 28-Jul. 2, 2010. *
Research in Motion: "Clarifying the requirements for the CJKV language ambiguity with the NITZ feature", 3GPP Draft; C1-102429, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre; 650, Route Des Lucioles; F-06921 Sophia-Antipolis Cedex; France, vol. CT WGI, no. Dublin; Jul. 2, 2010 , XP050443156, [retrieved on Jul. 5, 2010].

Also Published As

Publication number Publication date
US20130201980A1 (en) 2013-08-08
KR20140123086A (ko) 2014-10-21
JP2015513242A (ja) 2015-04-30
WO2013119599A1 (en) 2013-08-15
CN104094641B (zh) 2018-09-04
CN104094641A (zh) 2014-10-08
JP6239530B2 (ja) 2017-11-29
EP2813106B1 (en) 2018-10-10
EP2813106A1 (en) 2014-12-17

Similar Documents

Publication Publication Date Title
US9271329B2 (en) Systems and methods for enabling stations to connect to wireless hotspots using non-unicode service set identification information
US20180184294A1 (en) Methods and systems for enabling communication with a receiver device in a network
US9398624B2 (en) Wireless communication
US8014529B2 (en) In-band device enrollment without access point support
EP2988534A2 (en) Method of configuring wireless connection via near field communication function and image forming apparatus for performing the method
US10425980B2 (en) Method and apparatus for connecting to access point in portable terminal
US9572190B2 (en) Device and method for associating with WiFi networks
US9635604B2 (en) System and method for online sign up provider selection
EP2222103B1 (en) System and method for scanning when operating in different regulatory domains
US9191771B2 (en) Convenient use of push button mode of WPS (Wi-Fi protected setup) for provisioning wireless devices
US8856876B2 (en) Apparatus and method for identifying wireless network provider in wireless communication system
EP3078164A1 (en) Data communication via data packet headers
WO2016173177A1 (zh) 基于无线热点的Wi-Fi配置方法和装置
EP3585106A1 (en) Method and apparatus for processing service set identifier, and terminal
US9357479B2 (en) Communication system, communication control system, communication apparatus, communication method, and connection program
US20160323740A1 (en) Authentication commands
US7836445B2 (en) Technique for installing a station device driver
US10863346B2 (en) Wireless profile sharing method
KR20170078967A (ko) 다중 주파수 대역을 지원하는 액세스 포인트 및 상기 액세스 포인트에서의 통신 수행 방법
US8307377B2 (en) Systems and methods for efficient operations of components in a wireless communications device
WO2019109890A1 (zh) 基于Cell ID的通信方法、存储介质以及移动终端
HK1188885B (en) Displaying characters and images based on support
HK1188885A1 (zh) 基於支持来显示字符和图像

Legal Events

Date Code Title Description
AS Assignment

Owner name: QUALCOMM INCORPORATED, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:RABUL, JAMMULA;KUMAR, JINDAL DEEPAK;REEL/FRAME:029775/0744

Effective date: 20130206

AS Assignment

Owner name: QUALCOMM INCORPORATED, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:RAHUL, JAMMULA;KUMAR, DEEPAK JINDAL;REEL/FRAME:034500/0948

Effective date: 20141127

STCF Information on status: patent grant

Free format text: PATENTED CASE

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

LAPS Lapse for failure to pay maintenance fees

Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20200223