EP2384590B1 - Method for device capability advertising and discovery in a wireless network. - Google Patents

Method for device capability advertising and discovery in a wireless network. Download PDF

Info

Publication number
EP2384590B1
EP2384590B1 EP09839081.8A EP09839081A EP2384590B1 EP 2384590 B1 EP2384590 B1 EP 2384590B1 EP 09839081 A EP09839081 A EP 09839081A EP 2384590 B1 EP2384590 B1 EP 2384590B1
Authority
EP
European Patent Office
Prior art keywords
network
role
capability
type
message
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.)
Active
Application number
EP09839081.8A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP2384590A4 (en
EP2384590A1 (en
Inventor
Mika Kasslin
Janne Marin
Jarkko Kneckt
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.)
Nokia Technologies Oy
Original Assignee
Nokia Technologies Oy
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
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Priority to PL09839081T priority Critical patent/PL2384590T3/pl
Publication of EP2384590A1 publication Critical patent/EP2384590A1/en
Publication of EP2384590A4 publication Critical patent/EP2384590A4/en
Application granted granted Critical
Publication of EP2384590B1 publication Critical patent/EP2384590B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • 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]
    • 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

Definitions

  • the present application relates generally to wireless communication systems, methods, devices and computer programs and, more specifically, relate to device capability advertising and discovery such as in ad-hoc or point-to-point or infrastructure wireless communication networks, such as for example wireless local networks and broadband wireless access networks.
  • a device in wireless communication network uses service discovery to get information of the offered services in another device or network.
  • Service discovery in WLAN networks may be done at layer 3 (L3) and above. It may be based on the MAC-level GAS procedure and relying on the protocols which run on top of the IP layer.
  • the most widely used service discovery protocols are the ones specified in UPnP and Zeroconf (Zero Configuration Networking): namely SSDP and DNS-SD. Use of these protocols requires the client device to connect to the WLAN network and configure its IP layer. This is both time and power consuming. This has resulted in proposals to allow service discovery before network selection, which requires service information to be available at the WLAN MAC level, i.e. at layer 2.
  • a STA may initiate service discovery by sending a GAS initial request frame.
  • the STA may send the GAS initial request frame because the service information is not included in the beacon or probe response(s). Thus, the STA needs to complete a message exchange sequence to obtain the service information.
  • an AP can inform a STA as to whether or not the AP supports GAS.
  • the IEEE 802.11 specification defines a capability information field that is available in multiple frames to indicate MAC and PHY capabilities for the network and the mode that are in use at the time frame in which that capability information was transmitted. Other devices remain unaware of any other capabilities for which the transmitting device may be capable, apart from those that are active in the transmitted frame.
  • US 2008/0062945 discloses a technique for forming networks based on services offered or provided by particular leader nodes.
  • Client nodes in the network can select a particular leader node based on a desired service offered or provided by the particular leader node.
  • the client nodes can become a part of a different structured network such that the client nodes can have access to a desired service provided, either directly or indirectly, by the particular leader node.
  • a method that comprises receiving from a device a capability advertisement message which comprises role capabilities of the device; in response to the capability advertisement message, sending to the device on a bearer an activation message which comprises a request for at least one role capability of the capability advertisement message; and in response to the activation message, receiving from the device on the bearer a notification message which indicates whether the role capability of the activation message was accepted.
  • a computer readable memory storing a program of computer executable instructions that when executed by a processor result in actions comprising: In response to receiving from a device a capability advertisement message which comprises role capabilities of the device, sending to the device on a bearer an activation message which comprises a request for at least one role capability of the capability advertisement message; and determining from a notification message received on the bearer from the device in response to the activation message whether the role capability of the activation message was accepted.
  • an apparatus that includes an apparatus comprising: a receiver configured to receive from a device a capability advertisement message which comprises role capabilities of the device; and a transmitter configured, in response to the receiver receiving the capability advertisement message, to send to the device on a bearer an activation message which comprises a request for at least one role capability of the capability advertisement message.
  • the receiver is further configured to receive from the device on the bearer, in response to the activation message, a notification message which indicates whether the role capability of the activation message was accepted.
  • an apparatus that includes receive means (for example a receiver) and sending means (for example, a transmitter).
  • receive means for example a receiver
  • sending means for example, a transmitter.
  • the receive means is for receiving from a device a capability advertisement message which comprises role capabilities of the device.
  • the sending means is for sending to the device on a bearer, in response to the receive means receiving the capability advertisement message, an activation message which comprises a request for at least one role capability of the capability advertisement message.
  • a method that comprises: sending a capability advertisement message which comprises role capabilities; in response to the capability advertisement message, receiving from a device on a bearer an activation message which comprises a request for at least one role capability of the capability advertisement message; and in response to receiving the activation message, sending to the device on the bearer a notification message which indicates whether the role capability of the activation message is accepted.
  • a computer readable memory storing a program of computer executable instructions that when executed by a processor result in actions comprising: sending a capability advertisement message which comprises role capabilities; in response to the capability advertisement message, receiving from a device on a bearer an activation message which comprises a request for at least one role capability of the capability advertisement message; and in response to receiving the activation message, sending to the device on the bearer a notification message which indicates whether the role capability of the activation message is accepted.
  • an apparatus that includes a transmitter and a receiver.
  • the transmitter is configured to send a capability advertisement message which comprises role capabilities.
  • the receiver is configured to receive, on a bearer from a device in response to the transmitter sending the capability advertisement message, an activation message which comprises a request for at least one role capability of the capability advertisement message.
  • the transmitter is further configured, in response to the receiver receiving the activation message, to send to the device on the bearer a notification message which indicates whether the role capability of the activation message is accepted.
  • an apparatus that includes receive means (for example, a receiver) and sending means (for example, a transmitter).
  • the sending means is for sending a capability advertisement message which comprises role capabilities.
  • the receive means is for receiving, on a bearer from a device in response to the sending means sending the capability advertisement message, an activation message which comprises a request for at least one role capability of the capability advertisement message.
  • the sending means is further, in response to the receive means receiving the activation message, for sending to the device on the bearer a notification message which indicates whether the role capability of the activation message is accepted.
  • the device that receives capability information from another device in its network is termed the discovering apparatus, device, UE, MP or STA;
  • the device that sends/advertises its own capability information is termed the reporting apparatus, device, MP or STA; and there may be a third device that is brought into the network of the discovering device via the reporting device, or alternatively that is linked to the discovering device via the reporting device via two networks anchored by the reporting device. This will simply be termed a third apparatus, device, UE, MP or STA.
  • a MP in a mesh or STA in ad-hoc network may also be an AP and may take on any of the device roles as termed above.
  • a non-AP STA in a BSS may operate as an AP in another BSS. Any individual device may act as discovering, reporting, or third devices at different times, and at certain times may take on two or all three of those functions simultaneously depending on its interaction/message exchanges with other entities.
  • the exemplary capability advertising and discovery mechanisms presented herein include a MAC layer protocol and related MAC frames to support networking and related device role capability advertising, detection and activation of those prior non-active capabilities.
  • activation request frames/messages and activation response frames/messages detailed below.
  • beacon and probe response frames/messages may be used to distribute that information in network.
  • Figure 1 illustrates a schematic diagram of an exemplary environment in which the below teachings may be used.
  • Three devices are shown of which a first device 101 is a discovering device, a second device 102 is a reporting device, and there is also a third device 103.
  • the coverage area of a first network 101a in which the first device 101 and the second device 102 are currently active does not extend to the third device 103.
  • a theoretical coverage area of a second network 102a which is not yet set up in this embodiment, is shown by dashed line and represents the extent of a network for which the second device 102 would be the AP if the second device 102 takes on that role. Stipulate that the coverage area of the second network 102a would include the first device 101 if that second network 102a were set up.
  • FIG. 2 is a signaling diagram that illustrates two exemplary embodiments for how that happens.
  • the reporting device 102 sends at 201 its beacon frame or beacon message, which may be considered a broadcast frame or message, which is received and read by the discovering device 101.
  • the beacon frame 201 includes information elements that indicate the transmitting device's 102 capability or capabilities to operate in different network types (in addition to or other than the first network 101a which is active). Examples of different network types include an infrastructure-type network, a peer-to-peer type network, an ad hoc-type network, a mesh-type network or the like.
  • the transmitting device indicates its role capabilities in at least some of the networks.
  • the network-type information is specified to include the active network type(s) as well as the inactive type capabilities, there is in an exemplary embodiment an indication whether that particular network type is in use by the reporting device 102 at the time the beacon 201 is transmitted.
  • the beacon 201 may also include an indication of the number of concurrent networks for which the reporting device 102 is capable of supporting, and the specific device roles that it can assume.
  • the above information elements may be sent by the reporting device 102 in a probe response frame 203, which the reporting device 102 may send automatically in reply to receiving from the discovering device 101 a probe frame 202. In this manner the discovering device 101 can get the capability information of the reporting device 102 through a normal scanning procedure.
  • only some of the information elements detailed above may be sent in the beacon frame 201, and other more particularized information elements (for example, number of concurrent networks the reporting device 102 is capable of supporting and/or the specific device roles that it can assume) are sent only in the probe response message 203.
  • Various combinations of the above may be used to minimize control signaling overhead, based on how frequent such information may be needed and/or on how common is a multi-network capability of devices in wireless local networks or broadband wireless access networks.
  • the beacon message 201 and the probe response message 203 which may carry the capabilities information detailed above may be considered more generically to be a capability advertisement message that may be transmitted by the reporting device 102 and received by the discovering device 101. This may be considered the scanning phase 210, and the beacon message 201 and the probe response message 203 may be sent on bearers already set up in the existing network 101a.
  • the discovering device would like the reporting device 102 to take on a new role or network combination that the discovering device 101 sees from the received capability advertisement message that the reporting device 102 is capable of performing.
  • the scanning phase 210 there may be an activation phase 220 in which the discovering device 101 requests the reporting device 102 to start operating in one of its capability-advertised roles in a capability-advertised network (where the reporting device 102 was not active in the requested role, network, or role/network combination during the scanning phase 210).
  • the discovering device 101 then begins the activation phase 220 by sending an activation request message 204 (activation request frame) to the reporting device 102 which requests that the reporting device 102 to start operating in a certain role in a given network type.
  • the reporting device 102 may be considered a requested device; and the discovering device 101 may be considered as the requesting device.
  • the discovering/requesting device 101 is restricted to requesting only one role and network type combination in a single activation request frame 204.
  • the discovering or requesting device 101 specifies what is the network type (for example infrastructure, peer-to-peer, ad hoc or mesh) to be used between it and the reporting or requested device 102 and, if applicable, what role (for example AP or client) the reporting or requested device 102 should take in that requested network. Additionally the discovering or requesting device 101 may include in exemplary embodiment information (for example SSID, BSSID and frequency channel) about the requested network within the activation request message 204.
  • the network type for example infrastructure, peer-to-peer, ad hoc or mesh
  • the reporting or requested device 102 should take in that requested network.
  • the discovering or requesting device 101 may include in exemplary embodiment information (for example SSID, BSSID and frequency channel) about the requested network within the activation request message 204.
  • the devices 101, 102 understand that the values for the network information are proposed values and the reporting or requested device 102 is not bound by those values; it has the authority to change them while setting up the requested network-type for which it may be the AP.
  • the reporting or requested device 102 When the reporting or requested device 102 receives the activation request frame 204, it processes the frame and decides on whether to accept the request.
  • the reporting or requested device 102 replies in an exemplary embodiment with an activation response message 205 or activation response frame, which is directed to the discovering or requesting device 101 and which indicates whether the request was accepted. If the request was such that the reporting/requested device 102 was requested to take an AP role either in an infrastructure-type network or in a peer-to-peer-type network, the reporting/requested device 102 needs to decide on the network parameters.
  • the reporting/requested device 102 indicates the network parameters of the available network in the activation response message 205.
  • the proposed values which were received in the activation request frame 204 from the discovering/requesting device 101 should be taken into account when fixing the parameter values for the new network.
  • the activation response frame 205 only includes the parameter values that differ from those which the discovering/requesting device 101 sent in the activation request frame 204.
  • the activation response frame 205 includes the parameter values for the new network regardless of those which were requested in the activation request frame 204.
  • the reporting device 102 Upon transmitting the activation response message 205 with positive response, the reporting device 102 either may start a new network of the requested type or may start looking for the network to be started by the discovering device 101.
  • the reporting device 102 may start the new network if it was requested to take an AP role in an infrastructure-type or peer-to-peer-type network, or if it is requested to take an MP role in a mesh-type network. In other cases the reporting device 102 may start looking for the network that may be created by the discovering device 101.
  • the reporting/requested device 102 may change its network-type while it is in an AP role with a third device 103, and end its AP role in its pre-existing network 102a with the third device 103.
  • device 102 may also know the inactive capabilities of the third device 103 via the same scanning phase 201 as was detailed above between the first device 101 and the second device 102. It may be that all the devices (device 103 shown) for which the second device 102 is acting as AP during the described scanning phase 210 between the first 101 and second 102 devices are also capable for the new network-type, and so the second device 102 knows it can change the network-type while remaining as AP and still serve those other devices 103 as AP in the new network. In this case the second device 102 may send a new network setup message 206 to the third device 103 (and other similarly-capable devices) with the values for the new network parameters.
  • FIG. 2 and the above description detail an overview of the signaling process.
  • Figures 3A through 5 are detailed exemplary embodiments of how those new capability-information elements may be disposed in the described frames, in a manner that may be readily implemented with WLAN frame structures.
  • FIG. 3A illustrates an exemplary IE with element ID 302, length in bits 304 and capability fields 306.
  • Figure 3B illustrates an exemplary embodiment of the capability fields 306. Specific embodiments may use less than all of those illustrated fields, or only one of them or some combination of some but not all of them. Figure 3B is seen to be comprehensive and certain network types may be rare enough that L3 discovery may be used for their setup.
  • the bit values below are exemplary and may be changed to have other of the described meanings without departing from these teachings, so long as both discovering/requesting device 101 and reporting/requested device 102 both understand a priori the same meaning for bit values.
  • An available network instance number field 306a is by example two bits in length and indicates number of free/available network instances in the device 102. It may be set to a value that indicates how many network instances other than the existing ones the device may have. Value 00 may identify that there are no free instance resources, and so a new network would necessarily mean that an existing one needs to be closed. This field 306a may only be used in the capability detection phase and may have no role in capability activation.
  • an infrastructure AP capability and status field 306b which is two bits in length and represents the reporting device's 102 capability to operate as AP in an infrastructure network and whether the capability is currently in use/active.
  • Exemplary values for the two bits of the capability and status field may be:
  • an infrastructure non-AP STA capability and status field 306c may be two bits in length and which may represent the reporting device's 102 capability to operate as a non-AP STA (i.e. a client terminal) in an infrastructure network and whether the capability is currently in use/active.
  • the four values may be similar as those noted above for the infrastructure AP capability and status field 306b.
  • Peer-To-Peer P2P
  • P2P Peer-To-Peer
  • status field 306d which may be two bits in length and which may represent the reporting device's 102 capability to operate as an AP in a peer-to-peer-type network and whether the capability is currently in use/active.
  • the four values may be similar as those noted above for the infrastructure AP capability and status field 306b.
  • Peer-To-Peer non-AP STA capability and status field 306e which may be two bits in length and which may represent the reporting device's 102 capability to operate as non-AP STA in Peer-To-Peer network and whether the capability is currently in use/active.
  • the four values may be similar as those noted above for the infrastructure AP capability and status field 306b.
  • IBSS capability and status field 306f which may be two bits in length and which may represent the reporting device's 102 capability to operate in IBSS, and whether the reporting device 102 is currently operating in IBSS.
  • the four values may be similar as those noted above for the infrastructure AP capability and status field 306b.
  • MP capability and status field 306g which may be two bits in length and which may represent the reporting device's 102 capability to operate as MP and whether the reporting device 102 is currently operating as MP.
  • the four values may be similar as those noted above for the infrastructure AP capability and status field 306b.
  • Field 306h is two bits but is not currently proposed for a specific meaning in the above scanning 210 / activation 220 signaling. This field could be used for future purposes.
  • Figure 4A illustrates how the beacon frame 201 and probe response frame 203 may be modified to account for the network type capability IE, with order 402, information element name 404 and notes 406 which may be stipulated in a WLAN specification. It is noted that in the notes column 406, the term "dotl 1NetworkTypeInterworking" is a master information block (MIB) variable that is used to specify conditions for frame field presence.
  • MIB master information block
  • FIG. 4B illustrates different fields of the action frame format for the activation request message 204 and the activation response message 205.
  • the conventional action frame is a specific MAC management frame that is a kind of protocol message container to be used for various MAC protocols. For example, unicasted probe request and probe response frames may be used as activation request and response frames.
  • the fields Figure 4B may be used in both the activation request message 204 and in the activation response message 205.
  • a category field 404a there may be a category field 404a, an action value field 404b, a dialog token field 404c, a network type capability field 404d, a BSSID field 404e, a regulatory class field 404f, and/or a channel number field 404g.
  • the category field 404a and the action value fields 404b are set to values indicating the activation response frame 205.
  • the value of dialog token field 404c in an activation request action frame may be arbitrary.
  • the value of the dialog token field in an activation response frame may be copied from each activation request action frame.
  • the network type capability IE 404d may be detailed above for its various fields with respect to Figure 3B for the same IE that was described for the beacon 201 and/or probe response 203 frames.
  • the BSSID field 404e may give the basic service set identifier for the new network being setup; the regulatory class field 404f may give the channel set for which the channel number field 404g applies. Together the regulatory class 404f and channel number 404g fields specify the channel frequency and spacing for the channel to be used in the new network.
  • the acknowledge/proposed type available field 404h may indicate to the reporting device if it is capable to operate in the proposed role.
  • Figures 5A-B are logic flow diagrams that illustrates the exemplary operation of a method, and a result of execution of computer program instructions, in accordance with the exemplary embodiments of this invention. Exemplary messages noted at Figures 5A-B are detailed at Figure 2 .
  • Figure 5A illustrates from the perspective of the discovering/requesting device 101 and Figure 5B illustrates from the perspective of the reporting/requested device 102.
  • the discovering device 101 receives a capability advertisement message from the reporting device 102. Both devices 101, 102 are peer devices.
  • the capability advertisement message is sent on a bearer and includes role capabilities of the reporting device 102.
  • the received capability advertisement message may be a beacon frame, and at block 504 the capability advertisement message is a probe response which the discovering device 101 receives in reply to receiving from the reporting device 102 the discovery device's probe request frame.
  • the probe request and probe responses are both communicated on the same bearer.
  • the discovering device 101 in response to receiving from the reporting device 102 the capability announcement message, the discovering device 101 sends to the reporting device 102 an activation message on a bearer (same bearer in the case of probe request/response at block 506), and this activation message includes a request for at least one of the reported capabilities which was in the received capability advertisement message. If the requested capability is not inactive, the discovering device 101 may get the network parameters of the already available network or the requested device 102 joins or creates a network with network parameters indicated in the activation request frame.
  • the discovering device 102 receives from the reporting device 102 (on the same bearer as it sent the activation message at block 508) a notification message, and the discovering device 101 determines from that notification message whether the role capability of the activation message was accepted by the reporting device 102.
  • a new network is set up and the notification message include parameters for the new network which are based on (may or may not be identical to) the parameters which the requesting device 101 sent in the activation message of block 508.
  • the reporting device 102 sends a capability advertisement message which indicates role capabilities of the reporting device 102. This may be sent in a beacon frame at block 514, or as in block 516 it may be a probe response which the reporting device 102 sends to the discovering device 101 in response to receiving the discovery device's probe request frame. Both devices 101, 102 are peer devices. For the case of block 516, the probe request and probe responses are both communicated on the same bearer.
  • the reporting device 102 receives from the discovering device 101 an activation message on a bearer (same bearer in the case of probe request/response at block 516), and this activation message includes a request for at least one of the reported capabilities which was in the reporting device's capability advertisement message. If the requested capability is not inactive for the reporting device 102, the reporting device 102 may send to the discovering device 101 the network parameters of the already available network or the reporting device 102 may join or create a network with network parameters based on parameters in the activation request frame.
  • the reporting device 101 sends to the discovering device 101 (on the same bearer as it received the activation message at block 518) a notification message which indicates whether the reporting device 102 has accepted the role capability of the activation message.
  • the reporting device 102 sets up a new network and the notification message include parameters for the new network which are based on (may or may not be identical to) the parameters which were in the activation message that the reporting device 102 received at block 518.
  • FIG. 5A-B may be viewed as method steps, and/or as operations that result from operation of computer program code, and/or as a plurality of coupled logic circuit elements constructed to carry out the associated function(s). It is noted that the entire signaling protocol of Figures 2 and 5A-B are in the MAC layer, and the two devices 101, 102 are peer devices in a WLAN network or similar wireless networks during the scanning phase 210.
  • FIG. 6A illustrates a simplified block diagram of various electronic devices and/or apparatus that are suitable for use in practicing the exemplary embodiments of this invention.
  • a wireless communication network (for example mesh or ad-hoc or the like) is adapted for communication over a wireless link 11 between an apparatus, such as a mobile communication device which may be referred to as a UE 10, and another device as MP 12 which may also be a UE itself.
  • the other MP 12 may include a gateway functionality shown in Figure 6A which provides connectivity with a broader network 14 such as the Internet or some other data communications network.
  • the UE 10 includes a controller, such as a computer or a data processor (DP) 10A, a computer-readable memory medium embodied as a memory (MEM) 10B that stores a program of computer instructions (PROG) 10C, and a suitable radio frequency (RF) transceiver 10D for bidirectional wireless communications with the other MP 12 via one or more antennas 10E.
  • the other MP 12 also includes a controller, such as a computer or a data processor (DP) 12A, a computer-readable memory medium embodied as a memory (MEM) 12B that stores a program of computer instructions (PROG) 12C, and a suitable RF transceiver 12D for communication with the UE 10 via one or more antennas 12E.
  • DP computer or a data processor
  • PROG program of computer instructions
  • RF radio frequency
  • the other MP 12 when acting as access point for the mesh network 9, is coupled via a data path 13 to the broader network 14.
  • the UE 10 and the other MP 12 may also be coupled to other elements of the system 9 such as further MPs (for example, device 103 in Figure 2 ) to which they are linked via direct single-hops or only via multi-hops.
  • At least one of the PROGs 10C and 12C is assumed to include program instructions that, when executed by the associated DP, enable the device to operate in accordance with the exemplary embodiments of this invention, as detailed above.
  • Either of the MPs 10, 12 may be in the position of either of the devices 101, 102 during the scanning phase 210.
  • the message exchange detailed above may cause the non-mesh AP to change itself to a mesh AP.
  • the message exchange detailed above may cause the non-AP MP 12 to change itself to an AP.
  • the exemplary embodiments of this invention may be implemented at least in part by computer software executable by the DP 10A of the UE 10 and/or by the DP 12A of the other MP 12, or by hardware, or by a combination of software and hardware (and firmware).
  • the various embodiments of the UE 10 can include, but are not limited to, cellular telephones, personal digital assistants (PDAs) having wireless communication capabilities, portable computers having wireless communication capabilities, image capture devices such as digital cameras having wireless communication capabilities, gaming devices having wireless communication capabilities, music storage and playback appliances having wireless communication capabilities, Internet appliances permitting wireless Internet access and browsing, as well as portable units or terminals that incorporate combinations of such functions.
  • PDAs personal digital assistants
  • portable computers having wireless communication capabilities
  • image capture devices such as digital cameras having wireless communication capabilities
  • gaming devices having wireless communication capabilities
  • music storage and playback appliances having wireless communication capabilities
  • Internet appliances permitting wireless Internet access and browsing, as well as portable units or terminals that incorporate combinations of such functions.
  • the computer readable MEMs 10B and 12B may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
  • the DPs 10A and 12A may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multicore processor architecture, as non-limiting examples.
  • Figure 6B illustrates further details of an exemplary embodiment of an UE or a MP in both plan view (left) and sectional view (right), and the invention may be embodied in one or some combination of those more function-specific components.
  • the UE 10 has a graphical display interface 20 and a user interface 22 illustrated as a keypad but understood as also encompassing touch-screen technology at the graphical display interface 20 and voice-recognition technology received at the microphone 24.
  • a power actuator 26 controls the device being turned on and off by the user.
  • the exemplary UE 10 may have a camera 28 which is shown as being forward facing (for example, for video calls) but may alternatively or additionally be rearward facing (for example, for capturing images and video for local storage).
  • the camera 28 is controlled by a shutter actuator 30 and optionally by a zoom actuator 30 which may alternatively function as a volume adjustment for the speaker(s) 34 when the camera 28 is not in an active mode.
  • the antennas 36 may be multi-band for use with other radios in the UE. There might be embodiments where only a single antenna may be used.
  • the power chip 38 controls power amplification and outputs the amplified received signal to the radio-frequency (RF) chip 40 which demodulates and down-converts the signal for baseband processing.
  • the baseband (BB) chip 42 detects the signal which is then converted to a bit-stream and finally decoded. Similar processing occurs in reverse for signals generated in the apparatus 10 and transmitted from it.
  • Signals to and from the camera 28 may be passing through an image/video processor 44 which encodes and decodes the various image frames.
  • a separate audio processor 46 may also be present controlling signals to and from the speakers 34 and the microphone 24.
  • the graphical display interface 20 may be refreshed from a frame memory 48 as controlled by a user interface chip 50 which may process signals to and from the display interface 20 and/or additionally process user inputs from the keypad 22 and elsewhere.
  • Certain embodiments of the UE 10 may also include one or more further radios for example a wireless local area network radio WLAN 37 and Bluetooth® radio 39. Either or both of these radios may incorporate an antenna on-chip or be coupled to an off-chip antenna.
  • a wireless local area network radio WLAN 37 and Bluetooth® radio 39 Either or both of these radios may incorporate an antenna on-chip or be coupled to an off-chip antenna.
  • various memories such as random access memory RAM 43, read only memory ROM 45 (and in some embodiments removable memory such as the illustrated memory card 47) on which the various programs 10C are stored. All of these components within the UE 10 may be powered by a portable power supply such as a battery 49.
  • the aforesaid processors 38, 40, 42, 44, 46, 50 if embodied as separate entities in a UE 10 may operate in a slave relationship to the main processor 10A, which may then be in a master relationship to them.
  • the exemplary embodiments of this invention may be relevant to the WLAN chip 37, and in some embodiments the functionality added by these teachings may be implemented in the main processor 10A. For an example of the latter, these teachings may in some cases be implemented within WLAN MAC management that uses the WLAN service access point (SAP), which is sometimes located in the main processor 10A.
  • SAP WLAN service access point
  • BB baseband
  • WLAN Wireless Fidelity
  • main processor 10A main processor
  • Similar function-specific components that are directed toward communications over a mesh or ad-hoc network or the like may also be disposed in exemplary embodiments of the other MP 12, which may have one or more antennas not necessarily the same number as shown for the UE 10.
  • the various chips for example, 38, 40, 42, etc.
  • the various chips may be combined into a fewer number than described and, in a most compact case, may all be embodied physically within a single chip.
  • Exemplary embodiments of the invention may be embodied within the baseband chip 42 where the various messages are opened and decoded and responses are compiled or in the main DP 10A, or in some combination of chips. Any other functional and operational splitting may be applicable including other processors, parts, module or combinations in an apparatus.
  • the various exemplary embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the exemplary embodiments of the invention is not limited thereto.
  • While various aspects of the exemplary embodiments of this invention may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the integrated circuit, or circuits may comprise circuitry (as well as possibly firmware) for embodying at least one or more of a data processor or data processors, a digital signal processor or processors, baseband circuitry and radio frequency circuitry that are configurable so as to operate in accordance with the exemplary embodiments of this invention.
  • the exemplary embodiments have been described above in the context of a WLAN system, it should be appreciated that the exemplary embodiments of this invention are not limited for use with only this one particular type of wireless communication system, and that they may be used to advantage in any other mesh or ad-hoc wireless communication systems or broadband wireless access systems, such as for example WiMAX and Bluetooth as non-limiting other environments.
  • beacon frame for example beacon frame, probe response, etc.
  • probe response for example beacon frame, probe response, etc.
  • connection means any connection or coupling, either direct or indirect, between two or more elements, and may encompass the presence of one or more intermediate elements between two elements that are “connected” or “coupled” together.
  • the coupling or connection between the elements can be physical, logical, or a combination thereof.
  • two elements may be considered to be “connected” or “coupled” together by the use of one or more wires, cables and/or printed electrical connections, as well as by the use of electromagnetic energy, such as electromagnetic energy having wavelengths in the radio frequency region, the microwave region and the optical (both visible and invisible) region, as several non-limiting and non-exhaustive examples.
EP09839081.8A 2009-01-30 2009-12-14 Method for device capability advertising and discovery in a wireless network. Active EP2384590B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PL09839081T PL2384590T3 (pl) 2009-01-30 2009-12-14 Sposób rozgłaszania i odnajdywania funkcji urządzenia w sieci bezprzewodowej

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US12/322,360 US8577999B2 (en) 2009-01-30 2009-01-30 Method for WLAN network and device role activation
PCT/IB2009/055732 WO2010086699A1 (en) 2009-01-30 2009-12-14 Method for device capability advertising and discovery in a wireless network.

Publications (3)

Publication Number Publication Date
EP2384590A1 EP2384590A1 (en) 2011-11-09
EP2384590A4 EP2384590A4 (en) 2015-01-21
EP2384590B1 true EP2384590B1 (en) 2019-05-22

Family

ID=42395139

Family Applications (1)

Application Number Title Priority Date Filing Date
EP09839081.8A Active EP2384590B1 (en) 2009-01-30 2009-12-14 Method for device capability advertising and discovery in a wireless network.

Country Status (9)

Country Link
US (1) US8577999B2 (ru)
EP (1) EP2384590B1 (ru)
KR (1) KR101329957B1 (ru)
CN (1) CN102301761B (ru)
MY (1) MY162848A (ru)
PL (1) PL2384590T3 (ru)
RU (1) RU2494571C2 (ru)
TR (1) TR201911181T4 (ru)
WO (1) WO2010086699A1 (ru)

Families Citing this family (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8943552B2 (en) * 2009-04-24 2015-01-27 Blackberry Limited Methods and apparatus to discover authentication information in a wireless networking environment
US8769108B2 (en) * 2009-06-24 2014-07-01 Intel Corporation Peer-to-peer negotiation in a wireless network
US8619735B2 (en) 2009-07-16 2013-12-31 Blackberry Limited Methods and apparatus to register with external networks in wireless network environments
US8417253B2 (en) 2010-02-23 2013-04-09 Intel Corporation Bandwidth and channel notification for wide-channel wireless communication
US8644276B2 (en) 2010-05-13 2014-02-04 Research In Motion Limited Methods and apparatus to provide network capabilities for connecting to an access network
US8665842B2 (en) 2010-05-13 2014-03-04 Blackberry Limited Methods and apparatus to discover network capabilities for connecting to an access network
US8467359B2 (en) 2010-05-13 2013-06-18 Research In Motion Limited Methods and apparatus to authenticate requests for network capabilities for connecting to an access network
US9369947B2 (en) 2010-11-03 2016-06-14 Lg Electronics Inc. Method for searching for device and communication device using same
US9542203B2 (en) 2010-12-06 2017-01-10 Microsoft Technology Licensing, Llc Universal dock for context sensitive computing device
US8923770B2 (en) 2010-12-09 2014-12-30 Microsoft Corporation Cognitive use of multiple regulatory domains
US8792429B2 (en) 2010-12-14 2014-07-29 Microsoft Corporation Direct connection with side channel control
US8589991B2 (en) 2010-12-14 2013-11-19 Microsoft Corporation Direct connection with side channel control
US9294545B2 (en) 2010-12-16 2016-03-22 Microsoft Technology Licensing, Llc Fast join of peer to peer group with power saving mode
US8948382B2 (en) 2010-12-16 2015-02-03 Microsoft Corporation Secure protocol for peer-to-peer network
US20120158839A1 (en) * 2010-12-16 2012-06-21 Microsoft Corporation Wireless network interface with infrastructure and direct modes
US8971841B2 (en) 2010-12-17 2015-03-03 Microsoft Corporation Operating system supporting cost aware applications
WO2012087078A2 (ko) * 2010-12-24 2012-06-28 삼성전자 주식회사 와이파이 다이렉트 통신 방식에서의 컨텐트 보호를 위한 방법 및 장치
JP5691748B2 (ja) * 2011-03-31 2015-04-01 富士通株式会社 プログラム、情報通信機器および連携方法
US9357406B2 (en) * 2011-05-18 2016-05-31 Lg Electronics Inc. Mode conversion method for client cooperation in wireless communication system and device thereof
US9445438B2 (en) 2011-10-28 2016-09-13 Qualcomm Incorporated Systems and methods for fast initial network link setup
US9402243B2 (en) 2011-10-28 2016-07-26 Qualcomm Incorporated Systems and methods for fast initial network link setup
US9338732B2 (en) 2011-10-28 2016-05-10 Qualcomm Incorporated Systems and methods for fast initial network link setup
US9814085B2 (en) 2011-10-28 2017-11-07 Qualcomm, Incorporated Systems and methods for fast initial network link setup
US9185725B2 (en) * 2011-12-15 2015-11-10 Nokia Technologies Oy Request-response procedure for wireless network
WO2013168992A1 (ko) * 2012-05-09 2013-11-14 엘지전자 주식회사 멀티 네트워크에서의 디바이스 디스커버리 및 콘텐트 다운로드 방법, 장치 및 시스템
US20130329600A1 (en) * 2012-06-11 2013-12-12 Samsung Electronics Co., Ltd. Method and apparatus for negotiating capabilities in a wireless communication network environment
US9258704B2 (en) 2012-06-27 2016-02-09 Advanced Messaging Technologies, Inc. Facilitating network login
US10547693B2 (en) * 2012-09-07 2020-01-28 Avigilon Corporation Security device capability discovery and device selection
WO2014123383A1 (ko) * 2013-02-08 2014-08-14 엘지전자 주식회사 무선 통신 시스템에서 세션 수립 방법 및 장치
KR102207987B1 (ko) * 2013-07-10 2021-01-26 주식회사 케이티 무선랜 시스템에서 데이터 전송 방법 및 장치
KR102311514B1 (ko) 2014-03-06 2021-10-13 삼성전자주식회사 시커 디바이스와 목표 디바이스 간의 접속을 설정하는 방법 및 시스템
EP2916513A1 (en) * 2014-03-07 2015-09-09 VOVB en Partners B.V. Method for providing peer-to-peer communication using a request-response protocol
JP2017131319A (ja) * 2016-01-26 2017-08-03 株式会社Ｊｖｃケンウッド 生体センサ装置、管理装置、通信システム、及び通信方法
EP3908021B1 (en) 2018-05-30 2023-10-25 Telefonaktiebolaget LM Ericsson (publ) Determining extensible capability feature sets for a user equipment

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI103165B (fi) * 1997-02-12 1999-04-30 Nokia Mobile Phones Ltd Menetelmä ja järjestely tiedonsiirtoparametrien asettamiseksi tiedonsi irtojärjestelmässä
US20010026538A1 (en) * 2000-01-10 2001-10-04 Jorg Bruss Method and system for exchange of multicall capabilities between terminal and network
US6539030B1 (en) * 2000-02-07 2003-03-25 Qualcomm Incorporated Method and apparatus for providing configurable layers and protocols in a communications system
US7716492B1 (en) * 2000-05-09 2010-05-11 Oracle America, Inc. Method and apparatus to obtain service capability credentials
US20020122429A1 (en) * 2001-03-05 2002-09-05 Griggs Theodore Leon Mechanism and method for user selection of dynamic quality of service in telephony
US20040171386A1 (en) * 2001-09-04 2004-09-02 Enric Mitjana Method for identifying a station with specific functions in a wireless-based ad-hoc network, and a substation for carrying out the method
EP1533949B1 (en) * 2003-11-19 2006-12-27 Sony Deutschland GmbH Communication subsystem controlled information dissemination
WO2005114913A1 (en) 2004-05-21 2005-12-01 Nokia Corporation Device and method for automated functionality-based selective establishing of wireless data communication connections
US8135835B2 (en) * 2005-05-12 2012-03-13 International Business Machines Corporation Hardware and processing request brokerage
US20070026866A1 (en) * 2005-05-27 2007-02-01 Govindarajan Krishnamurthi Mobile node, method and computer program product for handing off from one type of network to another type of network
US7471200B2 (en) * 2005-06-30 2008-12-30 Nokia Corporation RFID optimized capability negotiation
CN101347029A (zh) 2005-11-16 2009-01-14 诺基亚公司 用于建立独立于承载且安全的连接的系统和方法
JP5306824B2 (ja) 2006-01-11 2013-10-02 クゥアルコム・インコーポレイテッド 無線端末のビーコン信号の使用を含むタイミングおよび／または同期に関連する方法および装置
US8149843B2 (en) 2006-06-28 2012-04-03 Cisco Technology, Inc. Capability exchange between network entities in WiMAX
CN101971561A (zh) * 2006-07-09 2011-02-09 90度软件股份有限公司 用于管理网络的系统和方法
US8106742B2 (en) * 2006-08-04 2012-01-31 Tegic Communications, Inc. Remotely controlling one or more client devices detected over a wireless network using a mobile device
US7801027B2 (en) * 2006-08-30 2010-09-21 Mellanox Technologies Ltd. Auto-negotiation by nodes on an infiniband fabric
US20080062945A1 (en) * 2006-09-11 2008-03-13 Motorola, Inc. Selecting a leader node for an ad hoc network based on services
KR20100005040A (ko) 2007-03-22 2010-01-13 노키아 코포레이션 양방향 데이터를 스케줄링하기 위한 제어기(호스트)와 참여자(장치) 간의 장치들의 역할 교환
US20090063622A1 (en) * 2007-08-29 2009-03-05 International Business Machines Corporation Apparatus, system, and method for cooperation between a browser and a server to package small objects in one or more archives
CN101960779A (zh) * 2007-10-01 2011-01-26 惠普开发有限公司 用于管理分布在不同网络上的虚拟协作系统的系统和方法
US20090265450A1 (en) * 2008-04-17 2009-10-22 Darren Helmer Method and apparatus for managing computing resources of management systems
US8270414B2 (en) * 2008-08-20 2012-09-18 Intel Corporation Apparatus and method to dynamically handover master functionality to another peer in a wireless network
US8392496B2 (en) * 2008-12-19 2013-03-05 Watchguard Technologies, Inc. Cluster architecture for network security processing
EP2422551B1 (en) * 2009-04-21 2013-07-03 Nokia Corp. Wireless station connectivity information distribution

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
CN102301761B (zh) 2015-04-22
US20100198952A1 (en) 2010-08-05
RU2494571C2 (ru) 2013-09-27
RU2011135622A (ru) 2013-03-10
WO2010086699A1 (en) 2010-08-05
MY162848A (en) 2017-07-31
US8577999B2 (en) 2013-11-05
KR101329957B1 (ko) 2013-11-14
EP2384590A4 (en) 2015-01-21
EP2384590A1 (en) 2011-11-09
CN102301761A (zh) 2011-12-28
PL2384590T3 (pl) 2019-10-31
KR20110111315A (ko) 2011-10-10
TR201911181T4 (tr) 2019-08-21

Similar Documents

Publication Publication Date Title
EP2384590B1 (en) Method for device capability advertising and discovery in a wireless network.
US10966268B2 (en) Method for using legacy Wi-Fi and Wi-Fi P2P simultaneously
US9426228B2 (en) Cross layer service discovery for wireless networks
US9521589B2 (en) Wi-Fi direct service method using NFC and device therefor
EP2497286B1 (en) Peer discovery in a wireless communication network
EP2517505B1 (en) Method and system for discoverability of power saving p2p devices
US20130148643A1 (en) Enhanced discovery procedures in peer-to-peer wireless local area networks (wlans)
US20130148642A1 (en) Enhanced discovery procedures in peer-to-peer wireless local area networks (wlans)
JP2017537526A (ja) ネットワーク発見
US9736766B2 (en) Method for finding instrument for wi-fi direct P2P (peer to peer) communication and apparatus therefor
US10820375B2 (en) Method and apparatus for turning on Wi-Fi infrastructure using BLE interface in wireless communication system
JP2014504065A (ja) ダイレクトリンク接続のためのプローブメッセージング
JP6579883B2 (ja) 通信装置、制御方法、及びプログラム
JP6674347B2 (ja) 通信装置、その制御方法、およびプログラム
CN107852590B (zh) 在无线通信系统中执行发现的方法和装置
JP2020053867A (ja) 通信装置、通信装置の制御方法、およびプログラム
KR102200775B1 (ko) 통신 장치, 통신 방법, 및 프로그램
US11064003B2 (en) Method and apparatus for receiving streaming via transport protocol in wireless communication system
JP2017103687A (ja) 通信装置、その制御方法、およびプログラム
CN115550957A (zh) 网络管理方法及装置
KR102208987B1 (ko) 통신 장치, 통신 방법, 및 프로그램
CN101496317A (zh) 便携式媒体播放器设备的无线支持
JP2018014648A (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: 20110621

AK Designated contracting states

Kind code of ref document: A1

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 MK MT NL NO PL PT RO SE SI SK SM TR

DAX Request for extension of the european patent (deleted)
RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA CORPORATION

A4 Supplementary search report drawn up and despatched

Effective date: 20150105

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 84/18 20090101ALN20141218BHEP

Ipc: H04W 8/00 20090101AFI20141218BHEP

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

Owner name: NOKIA TECHNOLOGIES OY

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20180220

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602009058536

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0008220000

Ipc: H04W0008000000

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 8/00 20090101AFI20181024BHEP

Ipc: H04W 84/18 20090101ALN20181024BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20181211

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

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 MK MT NL NO PL PT RO SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602009058536

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1137570

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190615

RAP2 Party data changed (patent owner data changed or rights of a patent transferred)

Owner name: NOKIA TECHNOLOGIES OY

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20190522

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190522

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190522

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190922

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190522

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190522

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190522

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190822

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190522

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190823

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190822

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190522

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1137570

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190522

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190522

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190522

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190522

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190522

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190522

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190522

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602009058536

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190522

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20200225

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190522

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20191231

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190522

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20191214

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20191214

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20191214

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20191214

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20191231

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190522

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190922

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190522

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20091214

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190522

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: CH

Payment date: 20230101

Year of fee payment: 14

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: TR

Payment date: 20231213

Year of fee payment: 15

Ref country code: IT

Payment date: 20231110

Year of fee payment: 15

Ref country code: FR

Payment date: 20231108

Year of fee payment: 15

Ref country code: DE

Payment date: 20231031

Year of fee payment: 15

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: PL

Payment date: 20231115

Year of fee payment: 15

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: CH

Payment date: 20240101

Year of fee payment: 15