EP2001178A2 - Architektur für MANET über Bluetooth - Google Patents

Architektur für MANET über Bluetooth Download PDF

Info

Publication number
EP2001178A2
EP2001178A2 EP08157754A EP08157754A EP2001178A2 EP 2001178 A2 EP2001178 A2 EP 2001178A2 EP 08157754 A EP08157754 A EP 08157754A EP 08157754 A EP08157754 A EP 08157754A EP 2001178 A2 EP2001178 A2 EP 2001178A2
Authority
EP
European Patent Office
Prior art keywords
bluetooth
manet
service layer
module
operable
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.)
Withdrawn
Application number
EP08157754A
Other languages
English (en)
French (fr)
Other versions
EP2001178A3 (de
Inventor
Mohan Reddy Duggi
Niranjan
Guoxin Fan
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.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
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 claimed from US11/760,123 external-priority patent/US8625481B2/en
Application filed by Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Publication of EP2001178A2 publication Critical patent/EP2001178A2/de
Publication of EP2001178A3 publication Critical patent/EP2001178A3/de
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/24—Radio transmission systems, i.e. using radiation field for communication between two or more posts
    • 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/02—Terminal devices

Definitions

  • LANs Traditional local area networks
  • LANs typically have a central server that acts as a controller and coordinator for data traffic among the clients in the network. Communication between clients in a traditional LAN typically does not occur directly from one client to another. Instead, data might be sent from a client to the server and then from the server to another client.
  • the server might also handle the logging in of clients, the synchronization of the activities of the clients, and other centralized control functions.
  • MANET mobile ad hoc network
  • a mobile ad hoc network (MANET) device has an architecture comprising a Bluetooth adaptation layer for wireless communication according to a Bluetooth convention, a MANET service layer, a scatternet module, a routing module, and a flow control manager in the MANET service layer.
  • the scattemet module and the routing module are in communication with the MANET service layer.
  • the MANET service layer is independent of the topology protocol of the scattemet module and independent of a routing rules of the routing module.
  • a method for MANET over Bluetooth includes providing a Bluetooth adaptation layer for wireless communication according to a Bluetooth standard, providing a MANET service layer coupled to communicate with the Bluetooth adaptation layer, and providing a scatternet module and a routing module in communication with but independent from the MANET service layer.
  • a device for establishing a MANET using a Bluetooth communications standard includes a Bluetooth host stack, a Bluetooth adaptation layer, a MANET service layer, a scattemet module, and a routing module.
  • the Bluetooth host stack is operable to implement the Bluetooth communications standard and send the Bluetooth-based data to the Bluetooth adaptation layer.
  • the Bluetooth adaptation layer is operable to receive the Bluetooth-based data, convert the Bluetooth-based data into a format recognizable by the MANET service layer, convert the converted Bluetooth-based data into an event recognizable by the MANET service layer, and send the event to the MANET service layer.
  • the MANET service layer promotes managing and storing the event.
  • Figure 1 is a diagram of an architecture for a MANET over Bluetooth according to an embodiment of the disclosure.
  • Figure 2 is a diagram of a method for MANET over Bluetooth according to an embodiment of the disclosure.
  • Figure 3 is a diagram of a wireless communications system including a handset operable for some of the various embodiments of the disclosure.
  • Figure 4 is a block diagram of a handset operable for some of the various embodiments of the disclosure.
  • Figure 5 is a diagram of a software environment that may be implemented on a handset operable for some of the various embodiments of the disclosure.
  • a mobile ad hoc network can be defined as a group of wireless computing devices capable of communicating directly with one another without a server acting as a central coordinator or scheduler for the data traffic between the devices.
  • a MANET typically comprises a plurality of wireless devices such as laptop computers, handheld computers, mobile phones or mobile handsets, personal digital assistants, and similar devices. The devices might be capable of communicating with one another via any of several well known wireless data transfer protocols.
  • a MANET in which the wireless devices communicate with one another via the Bluetooth protocol is known as a piconet and a group of connected piconets is known as a scatternet.
  • a scatternet is connection-oriented, meaning that a device must establish a connection with another device before the two devices can exchange data.
  • a connection topology typically needs to be formed to establish which devices are connected to which other devices.
  • the paths over which data will be transmitted through the connection topology typically need to be determined.
  • the flow of data through the connection topology might be monitored and/or controlled.
  • a software architecture for establishing and maintaining a scattemet is provided.
  • the architecture provides a module for forming a connection topology for a scattemet and a module for routing data in a scatternet. Management of data flow in a scattemet is also provided.
  • Components in the architecture are arranged in a layered, modular framework that allows the components to function independently of one another and to be replaced without significantly impacting other components.
  • Bluetooth devices which traditionally communicate in a one-hop fashion with a single other device, can communicate through a topology established by this architecture with multiple other Bluetooth devices.
  • FIG. 1 illustrates an embodiment of an architecture 10 for scattemet formation and maintenance.
  • the architecture 10 includes a Bluetooth (BT) host stack 20, an OS/platform 30, a Bluetooth (BT) adaptation layer 40, a Bluetooth MANET (BT-MANET) service layer 50, and a Bluetooth MANET (BT-MANET) core 60.
  • the BT-MANET service layer 50 includes a connection manager 51, a data manager 53, and a flow control manager 55.
  • the BT-MANET core 60 includes a scattemet module 70, a routing module 80, and an application adaptation module 90.
  • the BT adaptation layer 40, the BT-MANET service layer 50, and the BT-MANET core 60 collectively comprise an overall BT-MANET solution 100.
  • the Bluetooth host stack 20 might be a commercial, off-the-shelf component that implements the Bluetooth communications standards. Providers of the Bluetooth host stack 20 might implement the component in hardware, firmware, software, or any combination thereof. The Bluetooth host stack 20 can be considered the component that is responsible for the transmission and reception of data between Bluetooth-capable devices.
  • the OS/platform 30 might be a commercial, off-the-shelf operating system and/or platform used by a device in which the architecture is installed.
  • the BT adaptation layer 40 handles interprocess communications between the BT host stack 20 and the BT-MANET service layer 50. That is, the BT adaptation layer 40 is capable of receiving data in the format used by the BT host stack 20 and converting the data into a format usable by the BT-MANET service layer 50.
  • This abstraction of Bluetooth dependencies provides a generic Bluetooth application programming interface to the BT-MANET service layer 50 and allows easy substitution of different BT host stacks 20 from different manufacturers.
  • the BT adaptation layer 40 can be implemented using a Bluetooth application programming interface provided by the BT host stack 20. Therefore, the BT adaptation layer 40 may need to be replaced or modified when a different implementation of the BT host stack 20 is used.
  • the BT-MANET service layer 50 stores information about the active connections among the devices in a scatternet. Information regarding the roles of those devices, that is, which devices are acting as masters and which devices are acting as slaves, is also retained in the BT-MANET service layer 50.
  • the BT-MANET service layer 50 also stores state information for the devices in a scattemet or attempting to enter a scatternet. This information can be used by the scattemet module 70 and the routing module 80 to create a connection topology and establish the routing for data in a scatternet.
  • the BT host stack 20 When a new device connects to a scatternet, the BT host stack 20, via the BT adaptation layer 40, informs the BT-MANET service layer 50 of the new connection by sending a connection indication to the BT-MANET service layer 50.
  • the BT-MANET service layer 50 Upon receiving the connection indication, the BT-MANET service layer 50 performs a role discovery procedure on the new device to determine whether the new device is a master or a slave. The BT-MANET service layer 50 then stores this role information for use by the scatternet module 70 and the routing module 80.
  • the BT-MANET service layer 50 also provides a mapping between a device's Bluetooth Media Access Control (MAC) address and the connection handlers in any applications that might need to communicate with that device. This allows the applications on one device to communicate via Bluetooth with similar applications on another device.
  • MAC Media Access Control
  • the BT-MANET service layer 50 also manages data packet handling procedures wherein certain application threads can be placed in a blocked, unblocked, or best effort status and manages multiplexing/demultiplexing procedures for the data exchanged between applications. Examples of appropriate data packet handling procedures and multiplexing/demultiplexing procedures can be found in U.S. provisional patent application number 60/913,641, filed 04/24/2007 , entitled “Application Design Framework for MANET over Bluetooth", (Attorney Docket 4133-09600), which is herein incorporated by reference for all purposes.
  • connection-related functions in the BT-MANET service layer 50 are performed by the connection manager 51 and data-related functions are performed by the data manager 53.
  • the decoupling of the connection-related functions and the data-related functions in this manner provides flexibility and allows different connection managers 51 and data managers 53 to be easily substituted in the BT-MANET service layer 50.
  • the flow control manager 55 controls the flow of data in a scatternet on a hop-by-hop basis.
  • the flow control manager 55 might monitor data flow in a scatternet and redirect data when inefficiencies in the flow are found.
  • the flow control manager 55 can act independently of the other components in the architecture 10. Therefore, various different flow control protocols and techniques, which are well known to those skilled in the art, may be preferred for use in the present system depending on the circumstances.
  • the decoupled configuration of the flow control manager 55 relative to the other components of the architecture 10 provides the flexibility to efficiently use different flow control protocols or change flow control protocols without impacting the remaining architecture 10. For example, a first flow control manager 55 might be used in a first implementation of the architecture 10 and a second flow control manager 55 might be used in a second implementation of the architecture 10.
  • the scatternet module 70 forms a connection topology for the devices in a scatternet. That is, the scattemet module 70 determines which devices will form connections with other devices, how many hops away the devices will be from one another, and which devices will be masters and which devices will be slaves.
  • the scatternet module 70 can store information about the topology it has formed in the BT-MANET service layer 50 for use by the routing module 80.
  • An example of a connection topology procedure that could be used by the scattemet module 70 can be found in U.S. provisional patent application number 60/913,630, filed 04/24/2007 , entitled “Automatic Discovery and Connectivity Protocol for Bluetooth Scatternet Formation", (Attorney Docket 4133-09500), which is herein incorporated by reference for all purposes.
  • the present architecture 10 provides the scattemet module 70 as a separate module decoupled from the BT-MANET service layer 50.
  • the scattemet module 70 may be thought of as a generic module, since any protocol with any unique features may be used in its place without impacting the remaining components of the present architecture. Therefore, the present configuration allows the scattemet module 70 to be readily replaced, for example if a more efficient, improved, or more widely accepted protocol comes along, without impacting other portions of the system.
  • a first scatternet module 70 might communicate with the BT-MANET service layer 50 in a first implementation of the architecture 10 and a second scattemet module 70 might communicate with the BT-MANET service layer 50 in a second implementation of the architecture 10.
  • the routing module 80 determines the paths that data packets will take when being exchanged between devices in a scatternet. After the scattemet module 70 has formed a connection topology for the devices and stored information about the topology in the BT-MANET service layer 50, the routing module 80 can retrieve the information. The routing module 80 can then determine an efficient path for data through the topology. The scattemet module 70 and the routing module 80 can act independently of one another, allowing either of these modules to be easily replaced without significantly impacting the remaining architecture components. This allows different routing protocols to be employed without impacting the overall architecture, since different routing techniques may be available and preferred depending upon, for example, the deployment environment. For example, a first routing module 80 might communicate with the BT-MANET service layer 50 in a first implementation of the architecture 10 and a second routing module 80 might communicate with the BT-MANET service layer 50 in a second implementation of the architecture 10.
  • the application adaptation module 90 might contain application programming interfaces or similar interfaces that allow interaction between the BT-MANET solution 100 and one or more external applications 110. Multiple instances of the application adaptation module 90 might be present for different types of applications. For example, one set of interfaces might deal with File Transfer Protocol-related applications, another set of interfaces might deal with Transmission Control Protocol/Internet Protocol-related applications, and so on.
  • the applications 110 might provide device users with functions that are typically found on mobile devices, such as chat functions and data transfer functions. Chat, data transfer, and other functions might also be combined into a single one of the applications 110.
  • the applications 110 might be designed specifically for the BT-MANET solution 100 or the application adaptation module 90 might include interfaces that allow previously existing applications 110 to be ported to the BT-MANET solution 100.
  • each of the applications 110 can include independent modules capable of exchanging a particular type of data or event with a corresponding module in a corresponding application on a different device. For example, one module might handle chat-related data and another module might handle data transfer events. Corresponding modules register with one another to specify the types of events that they will generate and listen for.
  • the BT-MANET service layer 50 can maintain a list of events that the modules can register for and the applications 110 can consult this list when registering for events.
  • appropriate interfaces might exist between the layers of the MANET over Bluetooth architecture 10 to allow communication between the different layers.
  • standard Bluetooth interfaces may be present between the BT host stack 20 and the BT adaptation layer 40.
  • a device management service access point, BT-DM-SAP 22 might mediate device-related communications between the BT host stack 20 and the BT adaptation layer 40.
  • a logical link controller and adaptation protocol service access point, BT-L2CAP-SAP 24, might mediate connection-related communication between the BT host stack 20 and the BT adaptation layer 40.
  • a BT-MANET-BT-SAP 26 interface may be present between the BT host stack 20 and the BT MANET solution 100 and a BT-MANET-OS-SAP 32 interface may be present between the OS/platform 30 and the BT MANET solution 100.
  • a BT adaptation layer service access point, BTAL-SAP 42 might act as an interface between the BT adaptation layer 40 and the BT-MANET service layer 50.
  • the BTAL-SAP 42 might handle indications of events received from the BT host stack 20 such as indications of the connection or disconnection of devices, indications of the discovery of devices, indications of the switching of roles, and indications of link quality.
  • the BTAL-SAP 42 might decouple such events from the Bluetooth host stack 20 by converting the events into events recognizable by the BT-MANET service layer 50.
  • the BTAL-SAP 42 might also initialize and configure Bluetooth parameters and settings.
  • a BT-MANET service layer connection manager service access point BMSL-CM-SAP 57
  • a BT-MANET service layer data service access point BMSL-DATA-SAP 59
  • a BT-MANET application service access point, BT-MANET-APP-SAP 92 might act as an interface between the BT-MANET core 60 and the applications 110.
  • Figure 2 illustrates a method 300 for MANET over Bluetooth.
  • a Bluetooth adaptation layer is provided for wireless communication according to a Bluetooth standard.
  • a MANET service layer coupled to communicate with the Bluetooth adaptation layer is provided.
  • a scatternet module and a routing module are provided. The scatternet module and the routing module are in communication with but independent from the MANET service layer.
  • FIG. 3 shows a wireless communications system including a handset 400 that may be operable for implementing aspects of the present disclosure, but the present disclosure should not be limited to these implementations.
  • the handset 400 may take various forms including a wireless handset, a pager, a personal digital assistant (PDA), a portable computer, a tablet computer, or a laptop computer. Many suitable handsets combine some or all of these functions.
  • the handset 400 is not a general purpose computing device like a portable, laptop or tablet computer, but rather is a special-purpose communications device such as a mobile phone, wireless handset, pager, or PDA.
  • the handset 400 includes a display 402 and a touch-sensitive surface or keys 404 for input by a user.
  • the handset 400 may present options for the user to select, controls for the user to actuate, and/or cursors or other indicators for the user to direct.
  • the handset 400 may further accept data entry from the user, including numbers to dial or various parameter values for configuring the operation of the handset 400.
  • the handset 400 may further execute one or more software or firmware applications in response to user commands. These applications may configure the handset 400 to perform various customized functions in response to user interaction.
  • a web browser which enables the display 402 to show a web page.
  • the web page is obtained via wireless communications with a cell tower 406, a wireless network access node, or any other wireless communication network or system.
  • the cell tower 406 (or wireless network access node) is coupled to a wired network 408, such as the Internet.
  • the handset 400 Via the wireless link and the wired network, the handset 400 has access to information on various servers, such as a server 410.
  • the server 410 may provide content that may be shown on the display 402.
  • FIG. 4 shows a block diagram of the handset 400.
  • the handset 400 includes a digital signal processor (DSP) 502 and a memory 504.
  • the handset 400 may further include an antenna and front end unit 506, a radio frequency (RF) transceiver 508, an analog baseband processing unit 510, a microphone 512, an earpiece speaker 514, a headset port 516, an input/output interface 518, a removable memory card 520, a universal serial bus (USB) port 522, an infrared port 524, a vibrator 526, a keypad 528, a touch screen liquid crystal display (LCD) with a touch sensitive surface 530, a touch screen/LCD controller 532, a charge-coupled device (CCD) camera 534, a camera controller 536, and a global positioning system (GPS) sensor 538.
  • RF radio frequency
  • the DSP 502 or some other form of controller or central processing unit operates to control the various components of the handset 400 in accordance with embedded software or firmware stored in memory 504.
  • the DSP 502 may execute other applications stored in the memory 504 or made available via information carrier media such as portable data storage media like the removable memory card 520 or via wired or wireless network communications.
  • the application software may comprise a compiled set of machine-readable instructions that configure the DSP 502 to provide the desired functionality, or the application software may be high-level software instructions to be processed by an interpreter or compiler to indirectly configure the DSP 502.
  • the antenna and front end unit 506 may be provided to convert between wireless signals and electrical signals, enabling the handset 400 to send and receive information from a cellular network or some other available wireless communications network.
  • the RF transceiver 508 provides frequency shifting, converting received RF signals to baseband and converting baseband transmit signals to RF.
  • the analog baseband processing unit 510 may provide channel equalization and signal demodulation to extract information from received signals, may modulate information to create transmit signals, and may provide analog filtering for audio signals. To that end, the analog baseband processing unit 510 may have ports for connecting to the built-in microphone 512 and the earpiece speaker 514 that enable the handset 400 to be used as a cell phone.
  • the analog baseband processing unit 510 may further include a port for connecting to a headset or other hands-free microphone and speaker configuration.
  • the DSP 502 may send and receive digital communications with a wireless network via the analog baseband processing unit 510.
  • these digital communications may provide Internet connectivity, enabling a user to gain access to content on the Internet and to send and receive e-mail or text messages.
  • the input/output interface 518 interconnects the DSP 502 and various memories and interfaces.
  • the memory 504 and the removable memory card 520 may provide software and data to configure the operation of the DSP 502.
  • the interfaces may be the USB interface 522 and the infrared port 524.
  • the USB interface 522 may enable the handset 400 to function as a peripheral device to exchange information with a personal computer or other computer system.
  • the infrared port 524 and other optional ports such as a Bluetooth interface or an IEEE 802.11 compliant wireless interface may enable the handset 400 to communicate wirelessly with other nearby handsets and/or wireless base stations.
  • the input/output interface 518 may further connect the DSP 502 to the vibrator 526 that, when triggered, causes the handset 400 to vibrate.
  • the vibrator 526 may serve as a mechanism for silently alerting the user to any of various events such as an incoming call, a new text message, and an appointment reminder.
  • the keypad 528 couples to the DSP 502 via the interface 518 to provide one mechanism for the user to make selections, enter information, and otherwise provide input to the handset 400.
  • Another input mechanism may be the touch screen LCD 530, which may also display text and/or graphics to the user.
  • the touch screen LCD controller 532 couples the DSP 502 to the touch screen LCD 530.
  • the CCD camera 534 enables the handset 400 to take digital pictures.
  • the DSP 502 communicates with the CCD camera 534 via the camera controller 536.
  • the GPS sensor 538 is coupled to the DSP 502 to decode global positioning system signals, thereby enabling the handset 400 to determine its position.
  • Various other peripherals may also be included to provide additional functions, e.g., radio and television reception.
  • FIG. 5 illustrates a software environment 602 that may be implemented by the DSP 502.
  • the DSP 502 executes operating system drivers 604 that provide a platform from which the rest of the software operates.
  • the operating system drivers 604 provide drivers for the handset hardware with standardized interfaces that are accessible to application software.
  • the operating system drivers 604 include application management services ("AMS") 606 that transfer control between applications running on the handset 400.
  • AMS application management services
  • Also shown in Figure 5 are a web browser application 608, a media player application 610, and Java applets 612.
  • the web browser application 608 configures the handset 400 to operate as a web browser, allowing a user to enter information into forms and select links to retrieve and view web pages.
  • the media player application 610 configures the handset 400 to retrieve and play audio or audiovisual media.
  • the Java applets 612 configure the handset 400 to provide games, utilities, and other functionality.
  • a component 614 might provide functionality related to transmitting and receiving data packets in a scatternet.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
EP08157754A 2007-06-08 2008-06-06 Architektur für MANET über Bluetooth Withdrawn EP2001178A3 (de)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US11/760,123 US8625481B2 (en) 2006-12-15 2007-06-08 Architecture for MANET over Bluetooth

Publications (2)

Publication Number Publication Date
EP2001178A2 true EP2001178A2 (de) 2008-12-10
EP2001178A3 EP2001178A3 (de) 2013-01-09

Family

ID=39787865

Family Applications (1)

Application Number Title Priority Date Filing Date
EP08157754A Withdrawn EP2001178A3 (de) 2007-06-08 2008-06-06 Architektur für MANET über Bluetooth

Country Status (2)

Country Link
EP (1) EP2001178A3 (de)
KR (1) KR20080108024A (de)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102384871B1 (ko) 2014-12-02 2022-04-08 삼성전자주식회사 복수의 디바이스들간에 통신을 하는 방법 및 호스트 디바이스

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050078672A1 (en) * 2003-10-09 2005-04-14 Alaattin Caliskan Ad Hoc wireless node and network

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050078672A1 (en) * 2003-10-09 2005-04-14 Alaattin Caliskan Ad Hoc wireless node and network

Also Published As

Publication number Publication date
KR20080108024A (ko) 2008-12-11
EP2001178A3 (de) 2013-01-09

Similar Documents

Publication Publication Date Title
US8442549B2 (en) Automatic discovery and connectivity protocol for bluetooth scatternet formation
EP2196040B1 (de) Aushandlung von parametern für die drahtlose kommunikation mit kurzer reichweite unter verwendung von durch rfid empfangenen konfigurationsdaten
KR101202094B1 (ko) 교대 전송들을 통해 서비스 발견을 제공하기 위한 장치 및 방법
US20040162027A1 (en) Bluetooth wireless communication apparatus and method of notifying users of devices connectable to ad-hoc networks to establish effective connections based on a user's selection
CN107196964B (zh) 用于实现多频段服务发现的系统和方法
KR101240551B1 (ko) 블루투스 기반의 채팅 시스템 및 방법
US20050135286A1 (en) Wireless extended proximity networks: systems, methods and program products
US20020164953A1 (en) Bluetooth adaptor
US20090061775A1 (en) Systems and methods for multiport communication distribution
US20060227760A1 (en) Telephone for PSTN and internet
US20160191642A1 (en) Low power digital radio range extension
EP1290829B1 (de) Anrufsteuerungsgerät zur verbindung eines drahtlosen kommunikationsgerätes mit einem kommunikationsnetz
JP2004112225A (ja) 情報通信装置
JP7345062B2 (ja) 中継接続確立方法及び機器
US8625481B2 (en) Architecture for MANET over Bluetooth
CN114697929A (zh) 连接建立方法及电子设备
US8161121B2 (en) Application design framework for MANET over a short range communication protocol
JP2012100171A (ja) 通信装置、その制御方法及びプログラム
JP2002345039A (ja) データ端末機器及びファイル共有方法
JP2001144827A (ja) 通信制御装置及び方法
EP2001178A2 (de) Architektur für MANET über Bluetooth
JP2013157809A (ja) 通信装置、および、その制御方法、プログラム
EP3241403B1 (de) Digitale funkreichweitenerweiterung mit niedriger leistungsaufnahme
NO338828B1 (no) Forbedret løsning for konnektivitet
JP2004356950A (ja) 無線端末及び無線アクセスシステム

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20080606

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA MK RS

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: SAMSUNG ELECTRONICS CO., LTD.

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA MK RS

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 84/18 20090101AFI20121203BHEP

Ipc: H04W 88/02 20090101ALN20121203BHEP

17Q First examination report despatched

Effective date: 20130104

AKX Designation fees paid

Designated state(s): DE FR GB

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20150505