Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/0005—Control or signalling for completing the hand-off
  • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/0005—Control or signalling for completing the hand-off
  • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
  • H04W36/0019—Control or signalling for completing the hand-off for data sessions of end-to-end connection adapted for mobile IP [MIP]
• • 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/14—WLL [Wireless Local Loop]; RLL [Radio Local Loop]

Definitions

• the MHO is supported by the AO-homelADO.
• An AO connection is often relayed via a MHO module MHOM, which is controlled by the MHO specification MHOS in the AO homelADO. This provides benefits to both sharedlADx / AO-homelADO and users whose home-end-systems.
• a MHOM (one or only MHOS) differs significantly from a "home agent" of the Internet mobility technology and can therefore also support today's WiFi- / FMC telephones, ie the netsurfing procedure is short-term to the VolP Telephony turned off - but not limited.
• the netsurfing method has referred to the Internet mobility technique and the "HOCIS method" (PCT / EP2007 / 010485, filed Jun. 3, 2007, the contents of which are incorporated by reference into the present application, "Incorporation by Reference”).
• at least one additional technical feature each: This is his possibly tunnel-free relaying (ie the above first feature) or his technical communication for the realization of a business measure of a homelAD / shared IAD operator - which is usually to both end-system users in a VoIP call, usually by means of different messages to both, specifically on the occasion of the HOs of one of them and then convenience information correlated (ie the second feature above).
• the MHO is supported by the AO-homelADO.
• An AO link is often relayed via an MHO module MHOM, controlled according to a MHO MHOS specification in the AO homelADO (distributed in both implementations or local), which provides benefits to sharedlADx / AO homelADO operators and users to their home end systems.
• the MHOS is AO homelADO operator-private and possibly home-end-system-individual. This relay control offers advantages:
• the functionality of an MHOM is limited / extended over that of the "home agent" of the Internet mobility technology on the L3-L7 of the OSI-RM, to this HO management also with today's WiFi- / FMC -Telephones and sharedWLANs to practice, which do not master a suitable tunneling, and / or to be able to use the above-mentioned advantages, ie:
• the Netsurfing method aims at short notice on the Vo! P-Te efonie and more specifically on the "WLAN surfing” Also known as "wsurfing" in VolP calls, which shapes the examples in this section B.
• Security / Privacy see Section C.
• its business use but is not limited to any such thing.
• a small homelAD may allow at least one end system (e.g., a telephone and its user) access to at least one network, and in the o.g. Support senses, e.g. to the Internet and / or PSTN via an access to itself, the latter taking place either by wireless network and therein an arbitrarily definable region (e.g.
• Support senses e.g. an internet server or system on / in one of these networks.
• a MHOM may reside in any "material" host system - eg, be hosted by a material IAD or material system in or on a network - without the need for material HW expansion (see the end of Section C).
• the SW components of an MHOM in its host system
• the netsurfing method is a communication application (according to the MHOS) 1 which is usually located on the L7 of the OSI connection OCO (see below) between A0 and Z0. Regardless of whether this MHOM functionality partially or wholly in a WLAN (then eg in the IADO controlling it) or outside (then eg in an Internet server or a network system, .and thus outside the it / him controlling IADO) is implemented by functions in the
• End systems AO and / or ZO are supported - what i.d.R.
• the comfort of Netsurfing increases, but is also dispensable.
• WHERE synonymous hornelADO
• At least one L3 connection in the AO-OCO will however - if the end system AO is located in W1 or W2 - relayed by the corresponding IAD1 / IAD2 according to the invention via the MHOMO in the homelADO of the WO.
• Specifics are known from the Internet Mobility Technique (see Section A.).
• another network can be used by AO, so to speak a replacement wsurfing network, such as a GSM / CDMA / GPRS / HSPDA / ... -based mobile network
• Wsurfing connection for AO replaced with an Internet-based wsurfing connection for AO.
• the OCO between AO and ZO can of course also be supported in both end systems by one MHOM each, ie MHOM0 and M '(see Figure 3).
• these two MHOMs may self-responsibly "reroute" the L3 link of the OCO between them, for example, to cheapen or otherwise improve their TKV.
• Netsurfing makes the misuse of the Internet considerably more difficult and more general to some communication (security) technical aspects of the method according to the invention.
• a mobile terminal unknown to the IAD1 here eg AO 1 if it wants to use the IAD1 for wsurfing, does not specify its individual MHOMO (eg by an initial short "blind” Call this), but that IAD1 forwards all such requests to an unknown identity verification server in an unknown manner and only if this one establishes the L3 connection to the MHOMO over it - whereby this identity verification server sends the IAD 1 approximately from a credit card server. Institute or an ISP or a chain of custody or ... is made available for shared use.
• the netsurfing method thus allows the implementation of very different methods that a sharedlAD operator of all legal risks in "VolPsurfing" or "IP-TV surfing", as one could also call the inventive technique fr eistellen.
• subordinate security-oriented procedural claims substantiate this. It will be appreciated that the scope of the Wsurfing method allows specific embodiments thereof that virtually eliminate these known WLAN sharing risks.
• the communication status KS is finally pointed out: this can be determined, for example, by temporally / locally / externally controlled so to speak "independently” change - and thus also the admissibility / inadmissibility / meaningfulness of a Netsurfing connection between AO and its homelADO, even if AO locally does not change.
• Termini / terms - consistently in the sense of the OSI-RMs - merely serve to clarify (the essence) of the method / device according to the invention, that is to say no basic clarification of other communication-related questions.
• a handover aka an HO operation of an end system and its TKV - ie its change - occurs between at least two of either communication networks or access points of a network or features at an access point of a network.
• the present invention contemplates not only “vertical” HOs, ie, HOs between different networks, but also HOs between access points and / or features of the same network, so-called “horizontal” HOs, and any mixture between all the above mentioned HO species.
• TKV telecommunication process
• TNNs human and / or non-human “participants”
• proxies e.g. Answering machines, mailboxes, MP3 players, IVR systems, SchrifWHandschrift- /Grafik-/Symbol-/Sprache-/...-/DTMF-Erctioner/DTMF-Knokker/lnterpreter/Filte ⁇ active and / or passive type, in general: "Communication Application Systems” (see below) - are from and belong to "end systems” (see below), which end systems have access to at least one network. Networks / end systems / users jointly manage the (abstract) technical implementations of TKVs.
• a TKV has therefore been started / started at the latest when at least one device (eg a telephone) of one of its end systems has been started / started (eg picking up the telephone receiver, or local input / output or even only the local selection of a telephone number of a person to be called by someone involved in the TKV, or the manual or automatic start of a timer at the end of which a call is made, or ).
• at least one device eg a telephone
• the end systems eg picking up the telephone receiver, or local input / output or even only the local selection of a telephone number of a person to be called by someone involved in the TKV, or the manual or automatic start of a timer at the end of which a call is made, or .
• a TLN-date or a TLN-information is an ultimately / originally TLN-aware / producible information, which is output by means of this end-system to / from this (non-human or human) TLN or has been entered or selected ,
• OSI-RM Termini / Terms such as. OSl-Connections / PDUs / SDUs / Layers / Li-Connections / ... that belong to the "artificial" terminology / terminology of the OSI-RM - thus avoided in the pseudo-natural-linguistic verbal / meaning content of the claims the description use of the incomprehensibility of the
• OSI-RM could and can only on this basis - thus respecting the latter requirement - define the elementary concepts, terms and terms that are very helpful or even necessary for a clear description of many aspects especially of communication systems.
• the OSI-RM defines - due to its "7-layers" always basically the same
• An L7 connection of an OSI connection is often referred to as a "communication connection”, since in it the only meaning is the “communication” in the sense of the specific TK procedure underlying this OSI connection or of the “communication application system” supporting it. (the latter is located in at least the two end systems of the OSI connection), ie an L7 connection completely abstracts from the
• This OSI connection "exists" between AO and ZO as soon as one of the TKV-TLNs in one of its two (TKV) end systems AO and ZO has started this TKV, as soon as this TKV exists - ie: both (OCO and their TKVO) can still be “potential" at this point in time (see above) Ah then, between AO and ZO, the L7 connection of this A0-OC0-Z0 exists for this TKVO. It remains in existence until these two TKV-TLNs regard this TKV as terminated (which in the OSI-RM as terminating this L7 connection and OSl connection to would understand). The TKV also persists after that, as a "retrospective" TKV (see above), so it is original compared to its modeling by OSI-RM.
• An OSI connection (of a TKV) "exists" locally not only between the two (TKV) end systems AO and ZO, more precisely: between these two end systems AO and ZO there is the L3 connection of this OSI connection - But by means of their L7 connection between the communication application systems and even the TKV-TLNs in these end systems AO and ZO, and o time as soon as this TKV has begun in one of its TLNs - especially from this point on the L7 connection of this OSI Connection between the TLNs of this TKV - and remains in effect until these two TLNs consider this TKV to be terminated.
• this OSI connection exists at the latest from the time at which any action is taken for him / her in a terminal of the end system of the creating (TKV) TLNs in AO or ZO.
• OSI-RM and in the sense of this patent application, it is unequivocally existent already from the time at which it was tackled in a TLN of the underlying TKV, even if only prophylactically - e.g. by his explicit or implicit self-assurance of the availability of an emergency number (about 110 or 112) or his accessibility for him callers.
• the existence of a Li connection does not therefore imply its (abstract) realization or realizability.
• An (abstract) realization of a Li connection only needs to be given during its current (abstract) use.
• modules Non-human (abstract or material implementations of) functional groups in end systems are often referred to as "modules” below.
• TA Terminal Adapter
• Network Terminator of this network, wherein subscriber-terminal and non-terminal terminals of an end system work together via physical / communication interfaces and / or other terminals, i.d.R. only a few are standardized, and o a non-terminal terminal (and even its TA and its NT) may be particularly integrated into a mobile terminal (e.g., a mobile) - so the former is then also mobile.
• a mobile terminal e.g., a mobile
• ⁇ are abstract "servers” alias "server end systems” alias “end systems-without-human-TK-process-participants” function groups in or on a network - under the management of whose network operator (s) standing or not - in this document also are considered end systems / terminals, but the latter are not considered to be subdivided into terminal / non-terminal.
• ⁇ Has at least one of these non-terminal terminals of an end system and thus this "access" to more than one network (or a network access point of a network or a
• This expert "access” definition (in simple words) is: An end system / terminal will have “access to its network” functionally at one time, if at that time on the OSI layers L1-L3 of its connection to a functional access point of that network Network can communicate in the sense that it can in particular with all end systems / terminals of this network, which also have functional access to him at this time, can carry data transmission, which means that a terminal system / terminal of a network does not have permanent access to this needs - as it is in end systems / terminals of
• An "access point" to this network is a point of transfer of legal / business / technical responsibility - for the operability of these three layers on the data links (DÜAs) of that connection - from the operator of that network to the controller of that end system / terminal and his DÜAs:
• the network-side abstract termination device of these DÜAs at the access point is called "Network Termination”.
• Network terminator (“Network terminator” .NT), the user-side abstract terminator of this DUA at the access point is called “terminal adapter”, TA.
• terminal adapter the user-side abstract terminator of this DUA at the access point.
• these two conceptual functional units, NT and TA be as integrated as possible - as is usually the case with mobile phones.
• FMC Fixed Mobile Conversion
• Mobile phone i.d.R.
• a terminal and at least three non-terminal terminals include:
• its terminal terminal primarily serves to realize the functional acoustic / optical / mechanical user interface of a communication process
• o its three non-terminal terminals are i.d.R. required to work with the two different networks / access points / features in a HO: they consist of a functional "switch" for functional communication between its terminal terminal on the one hand and a functional one on the other hand
• Wired Access Point Wired Access Point
• IAD Integrated Access Device
• WAP has for some years already meant something completely different in the field of wireless technology, namely for “Wireless Application Protocol” - which has nothing to do with any “access poinf” concept, because applications on the L7 are located, while network Wersp ⁇ gspu ⁇ kte the various possible contents are usually located on the layers L1-L3 (and the underlying physical medium).
• ⁇ is called a "HO” alias "HO-process" of an end system and its TKVs (and their both OC) - analogous to the above TKV (details see there) - o "potential”, if for him / her not yet one of his changes -Measures was carried out in a terminal, but at least one other measure for it (for irrelevant reasons and here irrelevant way) and / or already addressed in an end system, and o "current”, if for such a change measure already in this case, this end system / TKV is meanwhile "affected” by this HO and "change” means a change in a network and / or network access point used by this end system (and its TKV and their two OCs) and / or network service feature during the HO.
• a potential HO becomes current as soon as at least one such change measure is "started” / "started” for him in at least one of his terminals, and a current HO "runs” thereafter until all such change measures are carried out - successfully or unsuccessfully - Are completed.
• this relaying functionality of a transit system can also extend to at least one potential OSI connection, ie in particular to the production of an (abstract and / or material) implementation of at least one of its at least 7 Li compounds.
• An example of such a relay system is the well-known VoIP gateway between Internet and PSTN / ISDN / UMTS, via which a telephone call / call between AO and ZO (at least partially) is relayed, if AO end system on the Internet and ZO end system on PSTN / ISDN / UMTS.
• the person skilled in the art also knows that Li connections of an OSI connection between AO and ZO-temporarily or permanently-can run over several relay systems: in this example in addition to the VoIP gateway, for example via a SIP server.
• Another example of such a relay system is a WLAN IAD on the Internet.
• Connections of an OSI connection relayed via such an IAD may require significant "protocol and data conversions.”
• the IAD may or may not modify the protocols and data during relaying.
• Connections may have a "tunnel" to establish "IP Address End-to-End Significance" (despite mobility of at least one of the end systems of their OSI connection, see Section A.).
• IP Address End-to-End Significance despite mobility of at least one of the end systems of their OSI connection, see Section A.
• the elimination of this IP address end-to-end significance opens up the possibility of being able to locate a wide variety of functionalities in a relay - such as "mixing together several TKVs with different TLNs in the relay, eg that for the present invention important .appropriate superimpositions of the audio channels of these TKVs 1 (more on this below) "for the user of an end system, ie TLN of these TKVs - ie waiving such a” mixing ability "in the end system (among other things because even today's FMC phones or PDAs or the like do not have such functionality).
• End system Z at least one "secondary TKV (STKV)" for end system A with i.d.R. at least one other system Y "interferes".
• STKV secondary TKV
• the simplest examples would be an IP TV TKV of
• An MHOM of an IAD or similar. may use another network access instead of an Internet access, e.g. a PSTN access or access to another WLAN via one of its IADs.
• tunneling technology can always be used if the information exchanged over a network is packetized - in particular, in particular, by the switching technology of this network.
• MHOS Managed HO Specification, MHOS is always associated with exactly one real or virtual (see below) homelAD or homeServer or homeSystem - for which the unified acronym “homeMIAD” stands for, ie not to be included in it needs (to a homeMIAD a lot of
• MHO measures Managed HO measures
• a homeMIAD can contain multiple MHOS.
• HOCISMa "HO Convenience Information Support”, see section B.
• a homeMIAD may be responsible for the execution control of a GeMa for its operator - and, if applicable, for its co-operating operators of sharedlADs - during of a MHO or GeMa-MHOs realize the most different O business measures, eg advertising kind
• VoIP TKV (or vice versa) to allow and - by whom ever - to let control.
• the HO itself will also be the basic one for a MHO
• MHO-HO-measure HOMa
• MHO e.g. "That of a GeMa with that of a HOMa and / or KoMa and / or HOCISMa " will be described in more detail below for the sake of safety.
• a specific MHO GeMaO (and thus the netsurfing method using it) is said to be "explicitly correlated" with at least one of these optional MHO MaOs - both in the same netsurfing method - independently of the GeMaO execution specified below. Sequence regarding at least one optional specific MaO execution order - if those submitted by GeMaO or by this MaO (during its
• At least one message communicated to or related to at least one TLN o denotes "implicitly correlated" if:
• TKV for that netsurfing method such that for one of its TLNs and a (potential and / or current) HO of its end system
• Netsurfing method application is based around in a VoIP call). And this most convenient way of accommodating such business communications (which the TLNs did not originally request, and therefore may be perceived as a nuisance), takes place during HO operations. In fact, here it can be designed not only to interfere with the TKV-TLN / s "as little as possible" through these business communications, but to actually help them at that moment - what the Customer acceptance / effectiveness of such business communications significantly improved.
• Patent application is expected that in the future, most MHOs of Netsurfing - so even in the cases in which a GeMa or their Cl correlation is dispensable (see claim 2) - the just discussed business use of HOs for GeMa should practice, because 5 whose cost / benefit balances speak in favor of all those involved.
• This MHOS / GeMa-MHO technology realizes the two bases of the Wsurfing method according to the invention: o
• MHO technology can illustrate this.
• both such decision-making (on the basis of such MHO-CoMa) of the homeMIADO and its definitely communicative HOCIS and business measures can be designed interactively in the sense that is generally known by an IVR system, for example interactively with end-system users on the sharedMIADO-supported sharedlADs as well as its other business partners.
• the MHOS can provide at least one communication status and this can be recorded / modified / evaluated by the homeMIADO - eg by means of its MHO measure and taken into consideration in the above-mentioned decision, for example, and these KS have the effect on such a decision described below.
• MHO species are intimately interwoven such that they are not identifiable by one of their end users concerned as such individual species, and o a homelAD operator can be identified for at least one and / or all entities of its home end systems ( eg their OCs and those themselves) in each case set the same content or different MHOS and differentiate accordingly or very simply.
• MHO-Ma can be globally specified for all or selectively for individual home-end-systems in a MHOS, and the latter can also be predefined set 5 (which, however, is irrelevant here as this involves design and material issues)
• O can be realized by two different material persons - an abstract "operator" can stand for a "material operator person and / or a material manager person”.
• PDU protocol data unit
• an end system AO is administratively associated with a homeWLAN alias homeNet and its according to the invention at least one real or virtual homeMIAD.
• AO is a "home end system” for this homeWLAN / homeNet / homeMIAD The simplest example of a homeMIAD / home-
• WLAN / homeNet can be realized by means of a WiFi IAD / WLAN and its home end system AO (an individual with WiFi telephone). According to the invention, this WiFi telephone AO can then surf / surf according to the invention by means of any shared WiFi WLAN Wx alias Netx, if AO can only "check in” at Wx / Netx (see below) and the homeMIAD of AO contains according to the invention a MHOS / MHOM (and this one with the IADx from Wx / Netx one
• this well-known homeWLAN / homeNet term in this patent application is extended to the WLAN / Net term used here (see Section B.).
• a KS can thus cause an OC of an end system or TKVs from an IAD / server, eg with actually responsible
• MHOM can be relayed or even must, even if this end system is not the actual home end system of this MHOMs / IADs / Servers (in the sense mentioned above).
• IADs / Servers in the sense mentioned above.
• this patent application belong to a homeWLAN / homeNet / homeMIAD / MHOM both its actual and improper home-end-systems.
• An end system AO which receives the electronic signal, eg of a WiFi-WLAN or other network, can usually only use it for communication, in particular via the Internet, after it has at least one of its (possibly several) IADs or Base Stations, or ... has been granted permission to use this network, and if granted, AO will be checked in.
• the procedures or protocols between AO and this LAD / Base Station will govern this application Giving or accepting / accepting rights of use of a network is irrelevant to this patent application.
• AO is considered “reachable” on a Netx if AO is checked in or checked in to this Netx, if necessary it is sufficient that AO is "checked-in / check-in” there, as explained in section D. - taking possible modalities and Implementations of such a check in or restricted check in feature in this patent application are irrelevant.
• Networksurfing connection This is at least one L3 connection of an OCO segment of the OCO between AO and ZO, namely that between AO and a system SO in / on a WLANx / Netx, which is different from the homeWLANO / homeNetO from AO.
• TKV / OC of a specific communication application based on the wsurfing method may be characterized by features which, when wsurfing an end system AO, result in it being treated preferentially - eg by being able to or even have to have its OC relayed by whom, if it is only technically suitable (the commercial or legal or other justification for the necessity / meaningfulness of this preference is not considered in this patent application, but only the Fact that it may or may not be present).
• this CS can also be a discriminatory or otherwise relaying treatment of an OC - by which IAD / server and whatever, up to a total relaying refusal, i. Withdrawal of a "home" entity feature.
• the CS of a method / device according to the invention or the entities of an OCO thus impairs such feature amounts of the relaying of OCs.
• Entities of an OCO here they mean both the Li entities of their Li compounds, as well as the Li compounds themselves, the implementation of which required at least one network and, if necessary, additional resources.
• FIG. 5 shows the HW / SW components of the abstract means of a device according to the invention according to claims 14-16.
• the bus (1) are usually connected: the memory (2) for storing ⁇ A the MHOM SW modules containing the MHOS, the processor (3) for realizing uA this MHOM functionality according to MHOS, the output / input Devices (4) for MHO PDU sending / receiving via at least one network., The output / input devices (5) for exchanging at least one MHO PDU between the MHOM and at least one local non-MHO functional module (optionally implemented via a local link device with means of device main claims).
• this document specifically regards its abstract netsurfing device as consisting of abstract HW / SW function components, this assignment of a functional netsurfing device component to the HW / SW being completely irrelevant. It is only important that the abstract realization of the functional components of an abstract netsurfing device by means of
• an abstract implementation of a netsurfing device in an abstract netsurfing device end system / IAD can share functionally equivalent or functionally suitable abstract HW / SW components of, for example, an operating system (and abstract HW components managed by the latter) by abstract resource sharing ,
• an abstract implementation of a netsurfing device which should complement an abstract end system / IAD to be supported by the netsurfing method, may also require this.
• Section D. describes the essence of the invention of the present patent application also by means of a somewhat elaborate explanation of its method claims.
• a second and comparably elaborate comment on the device claims does not appear to be necessary afterwards. Section D. is therefore part of the description of the method / device according to the invention.
• steps a) -b) can perform their arbitrary temporal overlap - the relevant expert knows, for example, that a separate preliminary check in a) is not required to execute a) and b). In particular, wording
• the claim 1-compliant Wsurfing method allows both relaying methods to be used (both the tunnel-free relaying and the tunnel relaying, see claim 3), thus contains no "tunnel-freedom" restriction therefor.
• its MHO is subject to a limitation over claim 2 in that it must realize a GeMa and its Cl correlation.
• these limitations do not appear in practice as such, but rather as an advantage of the netsurfing method (see Section C for the convenience of a GeMa and its Cl correlation in a MHO).
• ⁇ is still limited in terms of the network it uses (ie can use a different network than the one it uses anyway).
• a homeMIAD into a network - be it a TK network or a large WLAN - or e.g. in a network server, because so a "functional upgrade" of many
• FIG. 6e shows this TK arrangement with a large WLAN and a single virtual homeMIAD server get the desired "homeMIAD privacy" in this case - ie to make sure that the network or server operator / manager hosting the virtual homeMIAD server does not have access to the hostMIADs hosted virtual
• Figures 6 thus outline possible separations - i. possible distributed implementations - only the GeMa required for MHOs from other MHO Ma functionalities.
• Figures 7a-e outline for each of them a possible separation - i. possible distributed implementation - its homeMIADO control function from an associated executing function module in an O other system, so not all yet distributing the implementation of the MHOS.
• Figures 8a-e therefore outline for each of the MHO-Ma functionalities a possible separation of their homeMIADO control functions from at least one controlling part of the MHOS, by distributing them to two systems. In this sense, at least a part of a MHOS can be considered as executable, at least it can be interpreted.
• Such suitable distributed - ultimately physical - implementations facilitate operators of large networks or Internet servers, based on the method according to the invention, the most diverse innovative multimedia TK services in all possible cooperations, e.g. with sharedWLAN operators and / or IP TV program providers.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Mobile Radio Communication Systems (AREA)
• Artificial Filaments (AREA)
• Peptides Or Proteins (AREA)
• Telephonic Communication Services (AREA)

Priority Applications (6)

Applications Claiming Priority (52)

Publications (2)

Family

ID=39683547

Family Applications (1)

Country Status (8)

Cited By (3)

Families Citing this family (9)

Family Cites Families (23)

• 2008
  • 2008-01-04 PT PT08700985T patent/PT2027747E/pt unknown
  • 2008-01-04 CN CN201410315885.4A patent/CN104093175B/zh not_active Expired - Fee Related
  • 2008-01-04 WO PCT/EP2008/000037 patent/WO2008098642A2/de not_active Ceased
  • 2008-01-04 EP EP08700985A patent/EP2027747B1/de active Active
  • 2008-01-04 PL PL08700985T patent/PL2027747T3/pl unknown
  • 2008-01-04 US US11/969,388 patent/US8014364B2/en active Active
  • 2008-01-04 EP EP11161021A patent/EP2365710A1/de not_active Ceased
  • 2008-01-04 AT AT08700985T patent/ATE513441T1/de active
  • 2008-01-04 JP JP2009548592A patent/JP5222306B2/ja not_active Expired - Fee Related
• 2011
  • 2011-07-06 US US13/177,346 patent/US8351395B2/en not_active Expired - Fee Related

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events