Netsurfing in voip calls by means of managed handovers (mhos)

ES 2 368 019 T3

DESCRIPTION

Web browsing on VolP calls via managed handover (MHOS)

Object of the invention

This patent application discloses a network navigation procedure for an A0 terminal system, with a virtual or real A0-homeIAD0 and an A0 connection to a second Z0 terminal, for its managed handover, MHO, to a real IADx of a network WLANx or to a virtual IADx for a mobile phone network x (IAD = integrated access device). The MHO is supported by A0-homeIAD0.

An A0 connection is often relieved through an MHO module, MHOM, which is controlled by the MHO, MHOS, specification of A0-homeAD0. This offers benefits both to the operators of the sharedIADx / A0homeIAD0 and to the users of their local end systems.

An MHOM (including or excluding MHOS) differs in essence from a "home agent" of mobile Internet technology and can therefore also support current WiFi-iFMC phones. In other words, the procedure for navigating the network is oriented in the short term to VoIP telephony, although it is not limited to it.

A. Limitation of the handover state of the art, HO, with respect to the network navigation procedure

Document US 2006/0099948 A1 sets out, in its section on the background of the invention, the state of the art in the case of imperceptible handover (“seamless HO) and in the description of its procedure precisely, especially in the case of a "medium independent handover" (MIH). The different technical variants of HO are discussed (more extensively documented) in the "IEEE802.21 overview publication document" by V. Gupta et al. (DCN 06-21-0706-00-0000), as well as UCLA CSD-TR # 040012 by LJ Chen, as well as GA Mills-Tetty et al. ("Mobile Voice over IP, (MVOIP) ..." Proc. Of the 21. IEEE International Performance, Computing and Communications Conference, 2002), in the same way as that of E. Edvardsen et al. (“Open Access Networks”, Telenor Research and Development 2002) or H. Almus (“Open Broadband Access Networks” TERENA Networking Conference 2006) or PA Frangoulis ("Experimental evaluation of community-based WLAN voice and data services", ICST 978-963-06-2670-5). The complete instrumentation of mobile Internet technology for a future OH technique is discussed in the relevant, no-omission, general presentation of the book by J. Schiller ("Mobile Communications" Addison-Wesley 2003).

These works describe the state of the art of HO meticulously and thus show that the innovative characteristics of the web browsing procedure are not reflected in said state of the art, that is, they do not show that its characteristics are adequate:

for the MHO support of the current WiFi or FMC telephones and sharedWLAN-IADs due to its renunciation of the (still) currently uncommon technique of WiFi / FMC telephones and in particular for the production of advantages for the operator of the homeIAD / sharedIAD and for the user of the terminal system, hiding these advantages or uses from the rest of the network operators.

GB 2287614 A describes handover of a voice channel. The user receives from his mobile station a message that the voice channel has to be changed and then the user chooses by means of a handover configuration button, whether the handover should be prevented or not. Furthermore, the mobile station receives after each terminated call a message with the information on the expenditure incurred from the network and calculates the accumulated costs of the calls.

The present invention solves the problem in the current state of the art according to the characteristics of claim 1 of the method and of claim 8 of the device corresponding thereto.

With regard to Internet technology on the move and with regard to the "HOCIS procedure" (document WO 2008/064918), the web browsing procedure has at least one additional technical characteristic in each case, that is, its replacement, possibly without tunnels. (that is, the first characteristic above) or its technical communication for the realization of a commercial action of a homeIAD-IShared-IAD operator, which as a general rule is carried out with respect to both users of the terminal systems of a VoIP call, as a general rule by means of different messages to both and specifically personalized on the occasion of the HO of one of them and then it is correlated with the information of convenience, (ie the second feature above). Both technical characteristics, the relay without tunnels or an additional (commercial) communication technically correlated with the "convenience information", do not materialize either in the state of the art of HO or of the technique of the Internet in mobility, (the latter with their documents WO 2006/031379 A1 and WO 2006/031384 A1, which go in a similar direction, and which nevertheless, among other things, clearly exclude a telephony / VoIP application) neither in the HOCIS procedure nor in a sponsored-call procedure (see, for example, ”Rich Multimedia Applications

ES 2 368 019 T3 on IMS Framework ”, August 2007, or“ ALGELA Multimedia Sponsored Call White Paper ”on the respective Web pages).

B. Basic description of the invention by means of the simplest examples

The present patent application discloses a network navigation procedure for an A0 terminal system, with a virtual or real A0-homeIAD0 and an A0 connection to a second Z0 terminal, for its managed handover, MHO, to a real IADx in a WLANx network or to a virtual IADx for a mobile phone network x (IAD = integrated access device). The MHO is supported by A0-homeIAD0.

An A0 connection is often relieved through an MHO module, MHOM, which is controlled according to an MHO specification, MHOS, in the A0-homeIAD0 (in both distributed and local implementations), which offers advantages to the operator of the sharedIADx / A0homeIAD0 and the user of their local terminal systems. The MHOS is private for the operator of the A0-homeIAD0 and possibly individual for the local terminal system. This relay control offers advantages:

to a sharedIADx operator in relation to someone who browses the network on A0: the latter does not pose a legal risk, since homeIAD0 is identifiable for A0 and thus his operator will be legally liable in the event of abuse on the Internet of A0.

to an operator of homeIAD0 and to all operators of sharedIADx that cooperate with it, for example, o the MHO variants of IAD0- / sharedIADx local terminal system network navigation and the considerable possibilities associated with reducing costs and increasing the quality of its operation or business possibilities for the operator homeIAD0- / sharedWLANx through the “ CI "correlation of your messages with the" HOCIS "information that generates sympathy and good reception and eventually the delivery of these not only to the person who browses the net but also to his interlocutor and specifically respectively conceived in technology and content to satisfy the needs, that is, differentiated, or security of use of these advantages, (that is, their use eventually leaves third parties aside, it is even invisible for them, for example, for network operators intermediates) but that does not exclude a support of the web browsing procedure of others, for example, a network operator.

to the users of the terminal systems, because, due to the reasons mentioned above, they may find sharedWLANs more open and their MHOs among other things these sharedWLANs are more comfortable than to date mainly due to their “CI correlation”.

The functionality of an MHOM (including or excluding MHOS), with respect to the “home agent”, of the mobile Internet technology is extended / limited to layers 3-7 of the OSI model to be able to put into practice this HO management also with current WiFi-FMC phones and sharedWLANs that are not specialized in any suitable tunneling and / or to be able to take advantage of the advantages mentioned above. This means that the network navigation procedure is directed in the short term to VOIP telephony and more specifically to “navigation through WLAN networks” also known as “WSurfing” of VoIP calls, which characterizes the examples in this section. B, to your security / privacy (see section C) and to your commercial use, but not limited to anything similar.

To underline this, reference will be made to the possibilities of use of the WSurfing procedure, for example, in the context of an IP television transmission, instead of a VoIP transmission or associated with it, or for example in the context of a monitoring. A0 user real-time security-oriented. In all these communication applications all subsequent embodiments are equally applicable to web browsing / WSurfing, as in the case of the VoIP communication application. The latter can therefore be seen as representative of all these many other possibilities of application of the method or device according to the invention, for which reason they will only be recalled occasionally in what follows.

A small homeIAD can at least make it easier for a terminal system (for example a telephone and its user) to access at least one network and support it in the sense described above, for example the Internet and / or the public switched network of telephony, PSTN, through an access to itself, the latter taking place:

or by a wireless network and in it an arbitrarily definable region (for example, the region of accessibility of an IAD or any region, possibly the entire region, of a GSM network), or by physical connection (for example, cable of phone or coaxial cable).

The implementation of a WLAN in the sense of this document can be supported on the basis of, for example, the technology "RFI" or "Bluetooth" or "Femtocell" or "DECT" or "Wimax" or "GSM / CDMA / UMTS / GPRS / HSDPA etc., in particular “Wifi” technology, and may eventually include

ES 2 368 019 T3

Heterogeneous IADs (incorrectly called APs, (AP = access point), and / or BS of a mobile phone network (BS = base station) and spans an accessibility region, defined as it is, of an IAD or of a BS. A large local IAD / local server can facilitate network access to thousands of endpoint systems and support them in the aforementioned sense, that is, for example, it can be an Internet server or a system on this network or who is on this network.

An MHOM consists of abstract (functional) HW-ISW components. You do not have to use abstract HW components exclusively for your MHOM functionality, aka web browsing functionality, but rather it is suitable for sharing your abstract use with at least one non-functional MHOM ("abstract resource sharing ”) between these modules, see section C). In this regard, an MHOM can be mounted on each "material" host system, for example, it can be housed in an IAD or material system of / in a network, without the latter needing a material HW extension to do so (see end of section C). Also the SW components of an MHOM (on its host system) can be present anywhere else in encoded form, but in such a way that, before a function is requested from one of these SW components whose party is responsible for this function, they can be translated into semantically equivalent code and loaded onto the host system and thus executable by the HW MHOM components mentioned above. This conception of an MHOM is too strict for the discussion that follows and will be further subdivided in section C, although it is sufficient for the moment. The person skilled in the art knows these terms / concepts.

The network navigation procedure is a communication application (according to MHOS) that is generally located in layer 7, L7, of the connection OSI, OCO, (see below) between A0 and Z0. Regardless of whether this MHOM functionality is partially or fully implemented in a WLAN0 (then, for example, in the IAD0 that controls it) or outside (then, for example, in an Internet server or in a network system and therefore outside of the IAD0 that controls it) can be supported with the functions of the terminal systems A0 and / or Z0, which generally increases the comfort of web browsing but can also be waived.

The aforementioned legal certainty of the way of using the sharedWLAN for web browsing (for example of a mobile phone A0 in its call to Z0 occurs because its request according to the invention, for example of a sharedIAD of it, remains limited to its use exclusively as a router exclusively towards a MHOM with a fixed IP address, that is, to a known operator. This MHOM operator can undoubtedly identify a person in charge of an OCO relieved by himself (in case he carries out the relief, and then, for example, at the beginning of the call or before, which is irrelevant in this case, but for which the person skilled in the art knows adequate procedures). Thus, this MHOM operator is responsible for verifying the identity of a user of a wireless telephone in a sharedIAD, and not the operator of the latter. It should be noted: deviating from this, that the MHOM should facilitate the access of A0 to the Internet that has been directed to it, (and thus to your VoIP call to Z0), in case it is an emergency call ( even though this is pending legal clarification).

Exemplary embodiments of this legal aspect of the way of using sharedIAD network navigation are outlined at the end of this section B. First, however, the user's vision exclusively of the HO technical core of the Wsurfing procedure based on concrete examples in which the MHOM0 is integrated in a local IAD0 / local server 0 of an A0 terminal system. Variants of separation of functionalities implemented in this regard are discussed in Figures 6-8 and their explanations in section D. The core business of the web browsing procedure and its "CI correlation" are clarified in section C.

The simplest scenario of WSurfing or web surfing is shown in figure 1. An immediate or indirect MHO of the A0 mobile terminal system of a technical process of communications, PTC, (see section C), for example, an FMC telephone and its user, from its local WLAN0, abbreviated W0, which means the same as local iAD0, on the W1 or W2 not disjoint with respect to it or the W1 or W2 disjointed by path 1 or 2. The layer 7 connection, L7, of a possibly existing OCO, in this respect, between a0 and Z0 leaves it without touching the MHO on path 1 or 2. At least one layer 3 connection, L3, on the A0-OC0 However, when the terminal system A0 is in W1 or W2, it is revealed by the corresponding IAD1 / IAD2 (according to the invention through an MHOMO in the local IAD0 of W0. Additional features are known in the Internet technique in mobility (see section A).

Note that in this case it is by no means limited in which way the respective layer 3 connection, L3, (segment s) is established between the mobile terminal system A0 in W1 or W2 and the local IAD0 / local server 0 of W0 during an MHO. This patent application therefore comprises all the possible different variants of this establishment of the layer 3 connection, L3, between the layer 3 entity, L3, of A0 and that of the MHOMO. If the A0 is, for example, a telephone, this layer 3 connection, L3, may then occur in particular via your call to MHOMO or vice versa, or it may exist beforehand (the technical details favoring this are irrelevant here) . This also applies to the case of a "complete reset" of a phone call from a current WÍFÍ / fMc A0 phone going out of a WLANx to Z0, for which MHOMO implementation has to be properly conceived in layer 7, L7, ( in the IAD0).

ES 2 368 019 T3

After this discussion of an "immediate MHO", that is to say from one WLAN immediately to another WLAN, it is obvious how an "indirect MHO" works according to the invention, in which therefore both WLANs between which the end system A0 switches, they do not overlap each other spatially or temporally (see WLANs W0 and W2 as well as path 2 in Figure 1).

Two cases must be distinguished:

In the spatial or temporal region where there is no “no WLAN”, A0 (for administrative or technical reasons) also cannot use any network. In this case, an information transmission cannot be carried out on A0-OC0 to Z0, since it does not have a direct layer 3, L3 connection between A0 and Z0. The layer 4-7, L4-L7, connections of the A0-OC0 are however independent and may eventually continue to exist so that the current communication between A0 and Z0 through the A0-OC0 (that is, the suspended PTC) can continue to exist and continue to be carried out, as soon as A0 enters a WLANx, a “Wsurfing connection” can be established for connection A0OC0, through its IADx, between A0 and the local IAD0 / local server 0, (and its MHOMO).

in this region where there is no “no WLAN” A0 can use another network, so to speak, a substitute network for Wsurfing, for example a mobile phone network based on GSM / CDMA / GPRS / HSDPA ... or a network landline. If we stick with the first example and assume that A0 is an FMC phone and that it has access (see below) to this mobile phone network, a Wsurfing connection for A0 can be established between A0 and the local IAD0 / local server 0 , (via your MHOM0) over this mobile phone network, which again can be left untouched in detail in this case. In the subsequent entry and registration of A0 in W2 then (possibly after a security test in MHOMO according to the invention) this mobile network-based Wsurfing connection for A0 is replaced by an Internet-based Wsurfing connection for A0.

After these detailed discussions of A0's "MHO terminal system calling", that is, the "supported network navigation for the caller", as shown in figure 1, it is clear that there is an MHO for the system as well. terminal receiving the call, that is, the “supported network navigation for the recipient of the call from A0” (see figure 2). For the last variant of web browsing, what has been said in the previous paragraph applies in the same way, in this case the MHOM M 'may be located, for example, in an IAD' between the Internet and the terminal system Z0. The M 'enables the switching of WLAN networks of A0 and the Wsurfing connection between A0 and M' by means of exactly the same MHO functionality as in M, that is to say M 'is also an MHOM, however, eventually, with reduction of the protection of Internet abuse described above.

Finally, it is observed that the OC0 between A0 and Z0 can of course also receive support in both terminal systems through each MHOM, that is, MHOM0 and M '(see figure 3). In this case, both MHOMs can carry out a procedure, if necessary, possibly autonomously, of “rerouting” of the layer 3 connection, L3, of the OC0, among themselves to, for example, reduce or improve the price of another way your PTC.

Let us return to the previous statement that the procedure for browsing the network in the case of browsing the network supported for the caller makes fraudulent use of the Internet significantly more difficult and more generally we return to some technical aspects of communication (related to security ) of the method according to the invention.

This claim that fraudulent use of the Internet is hindered is correct since each fraudulent use can seriously harm the operator of the MHOM M0, which is more easily identifiable (because, for example, it is stationary for a longer period) so that the operator will protect itself from similar abuses by granting access to its MHOM only to sufficiently known persons. Additionally, for this, a variant of embodiment could be used in which, for example, only the MHOM M0 can initiate a Wsurfing connection of A0, after it has been informed of the direction in some different way, perhaps by means of a “tracking system A0 ”or actively by A0 via GPRS or SMS etc., so that a sharedIADI does not even have the possibility to establish a successful Wsurfing connection, because to start each of those attempts you will be notified as denied by the MHOM M0 of the local IAD0, or an unknown mobile terminal device in IAD1, in this case for example A0, when you want to use the IAD1 for Wsurfing, you cannot set your individual MHOM0 (eg by a short initial "blind" call to it), rather, the IAD1 forwards all the requests that are stereotypically unknown to it to an identity verification server that it trusts and this is then the one that eventually establishes the layer 3 connection, L3, through itself with the MHOMO, putting this identity check available to IAD1 for shared use for example through a credit card institute or an Internet operator or a chain of stores, etc.

The network navigation procedure therefore allows the implementation of procedures totally

ES 2 368 019 T3 which exempts a sharedAD operator from all legal risks of "VolPsurfing" or "IPTVsurfing", whatever the technique according to the invention may be called. The relevant safety-oriented dependent method claims specify this by way of example. It is seen that the protection scope of the Wsurfing procedure allows for special embodiments that eliminate these known risks of WLANsharing practically completely.

In this context, we will refer to finish the state of KS communication. This can be modified for example, temporarily / spatially / by remote control so to speak "autonomously" and thus also the permissibility / inadmissibility / direction of a web browsing connection between A0 and its local IAD0, even if A0 does not exist. varied its position at all. Towards the end, section C contains more on this.

C. Clarification of the terms / concepts and description of the OSI model of the network navigation procedure as well as its MHO, GeMaMHO and its “CI correlation”

The descriptions of the method or device according to the invention herein are, like the terms and concepts, purely functional, that is, completely abstract, that is, absolutely independent of a material implementation. However, for reasons of intelligibility, some possible material implementations of this procedure, of this device and its notions / concepts / terms are also occasionally explained. In this regard, it should be noted that the following clarifications of these terms / concepts only serve (in the general sense of the OSI model) only for the clarification (of the essence) of the device or method according to the invention, that is, no fundamental clarification other types of communication technology issues.

A handover (HO) or an HO process of a terminal system and its PTC process, that is, its switching, occurs between at least two communication networks or access points of a network or service characteristics in an access point of a network. The present invention therefore contemplates not only the "vertical" HOs, that is to say HO between different networks, but also the HOs between access points and / or service characteristics of the same network, known as "horizontal" HOs and all the combinations of the forms of HO mentioned above.

Conceptually (that is, in a purely functional, completely abstract way) an "abstract communications process" or "telecommunications process, PTC" occurs between several of its "participants" (TLN) who may or may not be people, who in turn are "users", or their representatives / partial functionalities / complementary functionalities, such as, for example, answering machine, mailbox, MP3 players, IVR systems, processors / generators for typewriting / handwriting / graphics / symbols, speech / DTMF generators / DTMF recognizers / Interpreters / filters of active and / or passive type, in general: they are “communication application systems” (see more below) of "terminal systems" (see below) and belong to them, these terminal systems having access to at least one network. The networks / terminal systems / users jointly achieve the abstract realization of PTC.

In this respect it is called:

or a communications process, or PTC, ❖ “potential” in case for it at least in a participating PTC terminal system a specific action has been applied but not yet in any device of its PTC terminal system, (ie, only in at least one PCT-TLN in at least one of these PTC terminal systems and these can be in the same still arbitrarily vague, that is, for example, an intention of it or even just the wish or the need), ❖ “current” in case this has already happened in at least one terminal device of this type and ❖ “initialized” or “started” in each of the two cases, ❖ “retrospective” or “finished” if not no more concrete action occurs for it in any PTC terminal device that participates in it, ❖ that is, “exists” or “is present” in all these cases.

Note that a PTC will have been started or started at the latest when at least one terminal device (for example, a telephone) of one of its terminal systems has at least initiated / started an action that affects it, for example, pick up the telephone handset or local data input or output or even just local dialing of the telephone number of the

ES 2 368 019 T3 person you want to call through a participant in some way in the PTC, or the manual or automatic start of a timer that upon expiration leads to a call etc.) or a current PTC ❖ while it is “setting up the connection” until the TLN data exchange has started in it, ❖ “started” as soon as the TLN data exchange has started and ❖ “baptizing” as soon as the information exchange TLN has started, the data "exchange" having started as soon as the exchange of at least one "TLN data" or one "TLN information" of a PTC TLN between at least one PTC terminal system and at least one network currently used by it has started. In this regard, a TLN data or a TLN information is information that the TLN can capture / generate at destination / origin that through this terminal system reaches the TLN or is sent by the TLN (whether it is a person or not) or that was selected. The difference between a TLN data and a TLN information is that either the TLN data is generally only exchanged for the eventually necessary management (establishment, interruption or termination) of a PTC or its OSI connection or its Li connections, that is, In general, during a Li connection establishment and / or its start-up, on the other hand, or the TLN information is exchanged to fulfill the objective of a PTC, that is, during its operation, that is, not during the establishment or technical management as in the previous case;

in both cases between their (possibly respective) TLNs or the representatives / partial functionalities etc. mentioned above ..

All communication technology notions / terms / concepts used in this patent application are defined in the international standard "ISO 7498-1 Information technology - Open Systems Interconnection - Basic Reference Model: the basic model" for short ISO / OSI reference model u OSI-RM. For the person skilled in the art it forms the binding intellectual / conceptual foundations of this patent application. Despite their wording in "natural pseudo-language", the terms of the network navigation device / method according to the invention in most of the claims are supported by the concepts / terminology defined in the OSI-RM, they have therefore experienced and to the details and limitations of communications technology that eliminate many of the uncertainties of a meaning "purely natural language." The description of the network navigation method / device according to the invention goes even further and uses concepts / terms from the OSI-RM model, such as for example OSI connection / PDU / SDU / Layers / Li connections etc., belonging to the “Artificial” OSI model terminology or concepts, that is, they have been avoided in the terms / meanings of the natural pseudo-language of the claims. Thus, the description makes use of the unambiguous ability to articulate the person skilled in the art via artificial concepts / terms of the OSI-RM (of which some, for example, have just been named). This will be helpful to the person skilled in the art to ensure a correct understanding of the essence of the natural pseudo-language description of the web browsing method / device in their respective independent claims.

For the use in the following of the OSI terminology / concepts and especially for the artificial terms / concepts of the OSI model it is noted in advance in this document that the claims regarding the description or on the one hand cannot recapitulate it. completely, so that instead it refers to the international standard mentioned above and in case of doubt this document is the reference one I on the other hand in some places in relation to the eventualities in case of an MHO has been somewhat simplified or has been explained more roughly (see below and section D).

And finally, it is emphasized that resorting to the terminology / concepts of the OSI model in this patent application is essential: the "Internet jargon" that today dominates in practice does not have or is close to the desirable conceptual precision of legal documents, in order to achieve it, and improve with respect to the conceptual or linguistic confusion in communications technology that has always been present habitually in the last instance the OSI model was developed. The conceptual details of this patent application serve not only to establish the substance of the independent claims but also for understanding, to facilitate or clarify their

ES 2 368 019 T3 descriptions of the procedure / device according to the invention and above all to prevent possible attempts to circumvent the requested scope of protection that would consist of wanting to reduce it by means of limitations just because in this patent application they are not exposed as illegal just from this description. For the rest, it should not be confused what is highlighted in the previous paragraph or the essential of resorting to the OSI model or with the knowledge that is also the basis of the OSI model that it requires a clear description of a complex system, from any source, and yet its abstraction of its multiple implementation details (material) and its unconditional focus on its functionality (of abstraction = abstract),

Rather, based only on these fundamentals, that is, when the requirement mentioned last is observed, the OSI model could and can define the notions, concepts and elementary terms that are very useful or even necessary for a clear description of many aspects, especially communication systems.

in each "n-point communication process" n> = 2 between two of its arbitrary end systems, eg A0 and Z0, there is an abstract "OSI connection", which also extends to communication application systems in these two systems as explained below. Each OSI connection is fundamentally subdivided according to the OSI model into seven abstract “Li connections” (1 <= i <= 7) “one on top of the other” by means of which this PTC is made between these two terminal systems A0 and Z0 (“L” represents "layer").

The OSI model thus defines, based on its “7 layers” always in principle an “abstraction semantics” equal to its Li connections in each OSI connection, the “OSI communications architecture”, which in turn is based on this “ 7-layer structure ”of the semantics of the fundamental abstraction of all OSI connections. These 7 fundamental layers of abstraction of your communications architecture are called by the OSI model totally independently of the individual OSI connections, obviously respectively “Li” 1 <= i <= 7.

In an individual OSI connection for each "i" there can be several Li connections. Each of these Li connections must always use at least one Lj connection of the same OSI connection for its materialization, where j <i without taking into account that:

or an L7 connection (ie i = 7) can use another L7 connection and or an L1 connection usually uses a “physical medium”, being able to use the Lk connection (1 <= k <= 7) for several OSI connections or in an OSI connection of several connections Lk + i (1 <= i <= 7-k).

An L7 connection of an OSI connection is often referred to as a “communication connection” since it is only “communication” of importance in the sense of the specific TC process that is the basis of this OSI connection or the “application system. communications ”that supports it (the latter located in at least both terminal systems of the OSI connection). That is, an L7 connection completely abstracts the modes of information transmission (L1 to L4 functionality) used in this communication (from a system of communications applications, which are eventually manipulated by people in it), the structuring of the information (functionality L5) and the presentation of information (L6 functionality). An L7 connection only knows the "interactions" in the "communications application" communication.

This OSI connection "exists" between A0 and Z0 and the terminal as a TLN of the PTC, in one of its two terminal systems (PTC) A0 and Z0 this PTC has started, that is, as soon as the PTC exists, that is, both (OCO and its PTC0) can be "potential" at this time (see above). From that moment there exists, namely, between A0 and Z0 the L7 connection of these A0-OCO-Z0 for this PTC0. It will continue to exist until both TLNs of the PTC consider this PTC terminated (which in the OSI model would be understood as termination of this L7 connection and of the OSI connection). The PTC continues to exist thereafter as a “retrospective” PTC (see above) in relation to its original OSI modeling so to speak.

In other words, an OSI connection (of a PTC) “exists” or spatially not only between the two terminal systems (PTC) A0 and Z0, more precisely, between these two terminal systems A0 and Z0 there is the L3 connection of this OSI connection, but through its L7 connection it also exists between the communication application systems even between the TLNs of the PTC in the two terminal systems A0 and Z0, and

ES 2 368 019 T3 or temporarily as long as this PTC has started in one of its TLNs, in particular the L7 connection of this OSI connection exists from that moment between the TLNs of this PTC, and continues to exist until these TLNs consider this PTC finished.

According to this, this OSI connection exists at the latest from the moment any action for him / her takes place in a terminal device of the TLN terminal system (PTC) that creates him / her in A0 or Z0. According to the OSI standard and in the sense of the present patent application, it is undoubtedly existing from the moment in which a TLN of the PTC on which it is based has been undertaken and even if only prophylactically, for example for its own verification explicit or implicit accessibility of an emergency call number (for example 110 or 112) or its accessibility to those who call you.

However, any of the Li connections (1 <= i <= 7) of this OSI connection does not need to be made or can be made (abstractly) at this time. The existence of a Li connection then implies not its realization or its possibility of realization (abstract). More generally: together with an OSI connection there are also its at least 7 Li connections of which however for no j 1 <= j <= 7 an Lj connection, and their cooperation with the other Li connections of this OSI connection, you need be made abstractly (material implementations / realizations are not contemplated by the OSI model anyway). An (abstract) realization of a Li connection only needs to exist as long as it is given a current (abstract) use.

This implies that the OSI connection between both terminal systems A0 and Z0 for this PTC continues to exist even in particular when at least the at least one L3 connection for the transmission of the L3 data of the participants between A0 and Z0 of this OSI connection (abstractly and / or materially) is not realized, as is often the case in HOs. That the L7 connection of an OSI connection in the case of an HO continues to exist (at least its abstract realization or eventually also its material realization) can be ensured by means of the "HOCIS procedure" mentioned above (see section A and below the "CI correlation").

The abstract "terminal systems" contain in addition to their abstract human users, and / or their abstract non-human users (user-automaton) and / or their representatives / partial functionalities, all must be understood as TLN PTC, abstract "terminal devices" whose set in a terminal system below and is occasionally also referred to as "terminal device", that is groups of non-human functions such as LAN, WLAN, supercomputers, databases, PBX, RAS, firewalls, switches of all kinds but also network access, IAD, input-output devices. Groups of non-human functions (abstract or material implementations) in terminal systems are hereinafter often designated by modules.

abstract individual "terminal devices" of a terminal system can be considered separately, in particular or a "participant terminal device" with its electronic / physical / acoustic / optical / "logical" user surface (here often mobile phone, for example in a mobile phone), or a “non-terminal terminal device” with a network-specific “terminal adapter” (TA) for “network termination” (NT = network terminator, “Network terminatof) of this network, or by cooperating non-terminal terminal devices and participant terminals of a terminal system through physical / communication technology interfaces and / or other terminal devices of which usually only some are standardized and or a non-terminal terminal device (and even your TA and your NT) in particular a terminal mobile terminal device (for example, a mobile phone) can be integrated so that the former is also mobile.

It is observed from this type of subdivision of terminal systems conforming to the OSI model into abstract people and abstract devices that the OSI model at first glance avoids the subdivision of terminal systems but ultimately it is implicit although it is quite clear that it does so. The cause of this is the conceptual need for the subdivision of the communications applications that are generally located in the L7 of the terminal systems to understand them in their essence. This need in the conventions for L7 (in the relevant international standard ISO / IEC 7498 of 1994 and in the identical ITU-T X200 recommendation, among others, pages 32/33 and its corresponding international standard such as ISO / IEC 9545 of 1994 and its identical recommendation ITU-T X.207) led to the definition of the functional structure of abstract communications applications conforming to the OSI model that logically implies the functional subdivision corresponding to it of the terminal systems that host it, in any case, within the scope of these applications that host it. The aforementioned subdivision of OSI terminal systems in this patent application is a special and particularly simple functional subdivision according to the OSI model (with correspondingly simplified terminology and which has been introduced above or will be introduced later for this subdivision) of OSI terminal systems in people and terminal devices of different types.

ES 2 368 019 T3

The abstract "servers" or "server terminal systems" or "terminal systems without a human participant in the PTC" are groups of functions of a network or in a network, under the management of its network operator or not, which in this document they are also considered as terminal systems or terminal devices, the latter however are not subdivided into terminal / non-terminal.

The abstract "systems" are either terminal systems / terminal devices or network-integrated computers.

At least one of these non-terminal devices of a terminal system and thus the latter has "access" to more than one network (or to a network access point of a network or to a network service feature in an access point to the network of a network), so that it can run an HO, see below, and more specifically through a respective "access point" of a network. Since these two terms are often misinterpreted (known to the person skilled in the art) your senses will be clarified first (at least with enough detail for this patent application):

This definition of "access" by the person skilled in the art (plainly) reads: a terminal system or a terminal device has a "functional access to its network" at an instant of time when at that instant of time in the OSI layers 1 to 3 of its connection it can communicate with the functional access point of this network, in the sense that it can manage the transmission of data in particular with all the terminal systems / terminal devices of this network that at this instant of time also have functional access to it. It follows that the terminal system / terminal device of a network does not necessarily have to have permanent access to it, as is known to often happen in the case of terminal systems / terminal devices of mobile networks.

An “access point” to this network is, in this respect, a place of the transfer of the economic or technical legal responsibility (for the functional capacity of these three layers in the data transmission sections (DÜA) of this connection) of the operator of this network to those responsible for these terminal systems / terminal devices and their DÜA. The abstract terminator on the network side of this DÜA at the access point is called the "network terminator" ("network terminate? NT), the abstract terminator on the user side of this DÜA at the point of access. access is called "terminal adapter" ("terminal adapt? TA)." In a physical implementation of a network access point, both the conceptual function units, NT and TA, can be integrated in the broadest way as in the case of a mobile phone in general. (Especially for mobile phones it is to be noted that: when this capability of a mobile network phone for the direct HO of mobile network refers to a GSM / CDMA / satellite network on the one hand and on the other hand refers to a WLAN network today is often called FMC telephone (FMC = fixed mobile conversion): it then specifically supports in a telephone call the use of both the technology currently called colloquially of fixed networks, WLAN VolP, and the technology that is called mobile network, GSM / CDMA / satellite). After this clarification of the concepts of network "access" and network "access point" referred to how they are usually legally understood by the expert in the field (he also knows that these terms can be illustrated with other concepts that then if they need the explicit naming of each respective reference model (see J. Schiller, section A)) it is clear that a terminal system / mobile terminal device that may be involved in a direct HO, in particular a mobile phone, generally comprises one terminal device and at least three non-terminals:

or its terminal terminal device serves as defined primarily for the realization of the mechanical / optical / acoustic user functional layer of a communications process or its three non-terminal terminal devices are generally required for it to cooperate with the two networks / different access points / service features during an HO: they are present in a functional "switch" to functionally provide data between its terminal terminal device on the one hand and on the other hand each functional TA / NT for or of the respective mobile network (s).

This clarification of the concept of access point should finally eliminate a confusion of concept in this patent application, which has been produced by the concept of wireless access point ("Wireless access point", WAP) of the new technical publications of the Internet technology in mobility in relation to two aspects:

or on the one hand, this concept of "wireless access point" (WAP) is erroneously used as a synonym for "integrated access device" (IAD), that is, as a synonym for a device. A device (abstract or material), however, is conceptually something totally different from a set of handover points of relevant legal responsibility in the Li layers of an OSI connection, that is, an "access point" of this application for patent.

or on the other hand, the acronym “WAP” represents for years anyway something totally different in the field of wireless technology, specifically “Wireless Application Protocol” which has nothing to do with it. do with the concept of "access point" because the applications are located on the L7 while the network access points

ES 2 368 019 T3 of the different possible directions are generally located in the L1-L3 layers (and in the physical environment that are below them).

It is called an “HO” or “HO process” of a terminal system and its PTC (and its two OCs), in analogy with the meaning of the previous PTC (see details there), or “potential” when they have not been realized for the same still its switching actions in a terminal device but at least one other action for it in it (for irrelevant reasons in this case and irrelevant here) and / or has already been directed to a terminal system, I "current" when a switching action has already taken place in the terminal device, this terminal / PTC system being called "affected" by this HO meanwhile and "switching" designates a change in a network used by this terminal system (and your PTC and your two OCs) and / or the network access point and / or the network service feature during HO. In this respect, a potential HO becomes actual as soon as for it in at least one of its terminal devices "starting" or "starting" at least such a change action and a current HO is "running" after this. until the completion of all similar switching actions (successful or unsuccessful).

Both end systems of an OSI connection of a PTC can belong to two different networks (as shown in Figure 1) so that an abstract “OSI transit system” “relieves” (“redirects”, “switches”) this OSI connection between these two networks. The present patent application considers this abstract "relay system" often as a terminal system of both networks and in any case as a "transit system" of the OSI connections relayed through it. This abstract "relay" is carried out according to the invention for at least one of the abstract Li connections, 1 <= i <= 7, of an OSI connection, in the case that in this relay system more relayed Li connections are produced than the OSI connection whose relay is individual and / or common. It must be considered in this case that the relay functionality of a transit system can also be extended to at least one potential OSI connection, that is, in particular, to the creation of an (abstract and / or material) implementation of at least one of your at least 7 Li connections.

An example of such a relay system is the commonly known VoIP gateway between the Internet and the public switched telephone network (PSTN) / ISDN / UMTS through which a call or telephone conversation between A0 and Z0 (at least partly) when terminal system A0 is on the Internet and terminal system Z0 is on PSTN / ISDN / UMTS. The person skilled in the art also knows that the Li connections of an OSI connection between A0 and Z0 (temporarily or permanently) can pass through several relay systems: in this example in addition to the VoIP gateway, for example through a SIP server . Another example of such a relay system is the WLAN IAD on the Internet. It communicates in the L1-L3 layers with the WLAN terminal systems by means of the "air interface WLAN" protocols of this IAD while it uses the corresponding Internet protocols of the L1- for communication with the Internet terminal systems. L3, which can require considerable “data and protocol conversions” in the corresponding Li connections of an OSI connection surveyed by such an IAD. For its L4-L7 connections, the IAD can also modify the protocols and data when doing the relay or not.

The person skilled in the art knows all this and also knows in particular that Li connections can have a "tunnel" to produce "IP addresses with end-to-end meaning" (despite the mobility of at least one of the terminal systems of their OSI connection, see section A). In case of dispensing with the meaning of these end-to-end IP addresses, it opens the possibility of being able to place functionalities of the most different types in a relay, such as intermixing several PTCs with different TLNs in the relay, for example, the important and appropriate overlap for the present invention of the voice channels of this PTC (more information later) for the user of a terminal system, that is, the TLN of this PTC, that is to say in case of dispensing with a mixing capacity of this type in this terminal system (among other reasons because today FMC telephones or PDAs or the like do not have a functionality of this type). For this reason, it is necessary to distinguish whether the (eventual) changeover of an OSI connection has to do or not with a tunnel of this type, so that it is also necessary to distinguish between a “tunneling changeover” with its limited functionality and a “ relay without tunnels ”. A system can use or contain for one or more OSI connections several relays of different types and then, eventually, implement these two relay techniques in parallel. Correspondingly, a differentiation is made between two types of MHO, "MHO without tunnels" and "MHO with tunneling" depending on whether an MHO needs a relay without tunnels or no relay or tunneling relay.

Implicitly it has been said that the present invention fundamentally (just as described in the HOCIS procedure) "intermixes" in a "primary PTC" of a terminal system A with a terminal system Z at least one "secondary PTC" for the system A with usually at least one other system Y. The simplest examples would be A's IPTV PTC with Z's TV server as primary PTC and in the meantime an incoming VoIP call to A from Y as secondary PTC. If you want

ES 2 368 019 T3 implement the network navigation procedure with current FMC telephones, that is, execute an MHO for example to another WLAN in this situation, this mix has to be deployed in the relay in this sense "without tunnels ”mentioned above for the primary PTC, which does not preclude the use in the network navigation procedure of tunneling technology that offers greatly simplifications through systems capable of this. More about mixing at least one primary PTC with at least one secondary PTC follows after the subsequent introduction of "MHO actions." Finally, bear in mind that an MHOM of an IAD or similar can use instead of an Internet access an access to another network, for example, an access to the PSTN network or an access to another WLAN network through one of its IADs . The tunneling technique can theoretically be used as long as the information that is exchanged through the network is in packets, regardless, in particular, of the transmission technology of this network.

a “specification of managed HO, MHOS” is always or just associated with a real or virtual local IAD (see below) or local server or local system that is designated with the unique acronym “homeMIAD”, that is, it does not need to be contained in it (belonging to a local MIAD (“homeMIAD) a set of local terminal systems that can be defined as such only by the local MIAD manager, so that this acronym reminds us of the security / privacy aspect of the MHOS) , or only its manager can assign the MHOS to the local MIAD and define the MHOS, or at least it knows two classes of "actions managed by HO, MHOMa", which through a local terminal system controlled by it are executed in its MHO and more specifically by a local MIAD that contains the MHOS by itself or under its control by another system of which at least one type causes a user communication and / or specifies the cooperation of its actions, MHOMa, in a realization of an MHO, being said from now on for the sake of simplicity occasionally local IAD, rather than local MIAD. In the sense of the above primary and secondary PTC concepts and terminology of the HOCIS procedure each MHOMa embodiment that produces at least one user communication is a secondary PTC.

In an application of the web browsing procedure, not all HOs in a PTC on which it is based have to be MHO, but the MHOS produces at least one MHO in this PTC. This is always controlled by at least one MHOS, that is, several MHOS may be involved in its control, perhaps defined differently. Conversely, a local MIAD can contain multiple MHOS.

It is a matter for an MHOS of a local MIAD to determine which of these local terminal systems controls in which MHO in relation to which actions of these, that is, which of these actions for this end system in this MHO as well as in cooperation with other actions for it. are produced. In Figures 6 to 8 of section D distributed implementations of an MHOS (and momentary MHOM) and their implementation possibilities aspects are discussed.

To the MHO-Ma classes of an MHOS belongs in this patent application:

o an optional type of MHO-Ma, the “MHO control actions, KoMa”, performs and controls the granting of permits and surveillance of the use of a network x (Netx) of a local terminal system in an MHO and eventually the creation or the proper management of a connection or a navigation relay without tunnels (see below and above) for A0 and this Netx, ie for an MHO without tunnels.

o With another optional type of MHO-Ma, with the “actions HOCIS MHO, HOCISMa” (HOCIS = “HO with support of convenience information”, see section B) the support shares of the most diverse class in relation to their potential and current HOs.

or for the so-called “GeMa-MHO”, which can eventually be produced without tunnels, at least one type of “MHO commercial action, GeMa” of MHO-Ma is essential, while for MHO it is optional. In both cases, a local MIAD can materialize with the control of the realization of a GeMa for its operator (and eventually for the operators that cooperate commercially of the sharedIADs) the commercial actions of the most varied type, for example, of an advertising type, during a MHO or a GeMa-MHO. In this case, the performance of a commercial action always materializes a communication from the PTC-TLN, whose local terminal system has just been affected by an HO, the latter having to find out or not about this communication (that is, somehow confirm).

o Other types of optional MHO-Ma actions for an MHOS or in an MHOS are arbitrarily definable or specifiable, for example, to allow a mix of the most different type of PTC IP TV in a PTC VoIP (or vice versa) and to leave the control to whoever it is.

o For reasons of simplification, the HO itself will also be considered, that is, the basic process for an MHO, as optional “MHO-HO, HOMa” actions.

ES 2 368 019 T3

An individual and specific MHO action of this type will in the following generally be marked by a "0" termination (for example, as in "GeMa0" or "HOMa0") and to confirm with the MHO prefix. Each GeMa-MHO is “CI correlated” (CI = “convenience information”) in the following sense: this GeMa-MHO characteristic characterizes the circumstances that during the performance of a GeMa-MHO action, the performance of its at least one action Associated MHO-GeMa occurs, implicitly or explicitly, in the context of performing an optional MHO-Ma action. A GeM in an MHO without tunnels does not need to be CI-correlated but it can be.

This correlation characteristic that intuitively perhaps seems to be immediately understood, of an MHO-GeMa realization with at least one realization of an optional MHO-Ma action in a GeMaMHO, that is, for example, “that of a GeMa with that of a HOMa and / or KoMa and / or HOCISMa ... ”will be described in more detail below for the avoidance of doubt.

It is necessary to differentiate first of all between such an implicit CI correlation and an explicit one, both types of CI correlations being completely independent of each other. A specific MHO-GeMa0 (and thus the network navigation procedure they use) as at least one of these optional MHO-Ma0, (both in the same network navigation procedure):

or will be called "explicitly correlated" (independent of the GeMa0 realization sequence specified below in relation to at least one specific optional Ma0 realization sequence) when the at least one GeMa0 or this Ma0 realization notice (during its realizations) communicated to at least one TLN describes or refers to such a context of any kind and will be called "implicitly correlated" when the following applies: for the network navigation procedure there is a PTC such that for one of its TLNs and an HO (potential and / or current) of its terminal system there is at least one realization of both this Ma0 and this GeMa0 and the starting time of this realization GeMa0 and / or its announcement to the TLN is as follows:

> after 30 seconds before the starting point of the realization of Ma0 and> not after 30 seconds of the end point of the latter, being irrelevant if / when / how the TLN perceives this realization Ma0.

By means of similar correlations of a GeMa, which the local operator performs, more specifically its MHOS, for at least one system managed by him / her (and its user), the associated GeMa communication is hosted in the PTC (which is the basis of the application of the web browsing procedure eventually in a VoIP call), “as far as possible”. And this, as far as possible, advantageous hosting of such commercial communication (which was not originally requested by the TLN and therefore possibly interpreted by it as a nuisance) occurs within the framework of HO processes. In this case, more specifically, it can be conceived in such a way that it not only bothers the TLN / PTC, “as little as possible” due to commercial communication, but that they consider it even helpful at this time, which decisively improves acceptance. or effectiveness of or with the client of these commercial communications. And causing these "favorable moments" as much as possible for all HOs is the task of HOCIS activities properly conceived for it. Due to its CI correlation characteristic, which in turn accepts all the optional MHO-Ma actions as a correlation basis, the network navigation procedure therefore makes it possible in an easy way to transform the supposed potential nuisance of an HO on a VoIP call on the business and convenience potential just discussed in this HO. In other words, this GeMa-MHO CI correlation could be considered as creator of convenience (hence its name) even if it is for its "optimal display of productivity" in a web browsing procedure usually a HOCISMa correlation. To end this discussion of GeMa-MHO, it should be mentioned that the authors of this patent application expect that in the future most of the MHOs of web browsing (that is, also in the cases where that a GeMa or its CI correlation can be waived (see claim 2)) should put into practice the commercial use just discussed of HOs for GeMa since their costs, uses, balances for all participants speak in their favor . The last something more concrete: this MHOS / GeMa-MHO technique performs the two fundamentals of the Wsurfing procedure according to the invention:

or, on the one hand, the rather commercial basis of making the local IAD internal to the company a springboard for an economic activity, meaningful and novel in the framework, above all, of VoIP calls, as far as possible with the participation of public sharedIAD I on the other hand the rather social foundation, make available to anyone the most comfortable and best-performing communications technology in all urban agglomeration areas in the short term and more economically for their future multimedia terminal systems (in particular for

ES 2 368 019 T3 the use of its IP-TV) as it is only possible today through mobile network technology (based on GSM, CDMA, UMTS, Wimax ... and their derivatives), maintaining these "standby technologies" high availability wherever sharedWLAN technology is not available or inexpensive.

Several simple examples and comments about the MHOS / GeMa-MHO technology that is CI correlated can illustrate this. Through a:

o MHOS0 / optional function1, associated to a local MIAD0, this decides before starting or at the beginning of an HO of a WiFi telephone A0 (which is a local terminal system of the local MIAD0) whether to this with its current PTC / OC0 to another telephone Z0 (which is relieved through an MHOM0) is allowed to execute an MHO to an IAD1 (MHO-KoMa), or optional MHOS0 / function2, also associated with the local MIAD0, This informs before the beginning or at the beginning of the HO prior to the two TLNs of this PTC about the execution of the potential or current HO (MHO-HOCISMa), or for a GeMa-MHO, MHOS / mandatory function 3 also associated with the local MIAD0, the latter implements (or its MHOS) a commercial action, for example the communication of an advertising note to the user of the local terminal system-local MIAD0 involved in this HO or to both TLNs of its PTC, this additional technical communication occurring before or during or after the previous decision (which is irrelevant here) one or several times and at any time (which is also irrelevant here) (MHO-GeMa).

This small example makes it clear that the realization of this MHO-GeMa occurs with the most favorable CI correlation together with the realization of the previous MHO-KoMa (this CI correlation not requiring that the realization of this MHO-KoMa be communicated to one of the TLN of the PTC), although above all with the previous MHO-HOCISMa, making use of the CI correlation usually now, First of all in VoIP calls that the realization of this MHO-HOCISMa usually anyway always communicates with both TLN-PTC.

This does not mean, however, that the use of the web browsing procedure can only be possible when the HOCIS procedure is also possible: the first seen technologically is completely independent of the second and the MHOs of the navigation procedure are also conceivable in terms of content. by the network in which a CI correlation of a MHO-GeMa with a MHOHOCISMa makes little sense.

In this regard:

or it is possible to interactively conceive both such inquiries for the decision (based on such MHO-KoMa) of the local MIAD0 as well as its HOCIS and commercial actions definitely communicative in the sense, for example of what is commonly known as an IVR system, for example Interactive example both with users of the terminal systems in the shareIADs supported by the local MIAD0s and with their other business partners.

or the MHOS can at least foresee a communications state and this can be evaluated / modified / recorded by a local MIAD0 (for example by means of its MHO-Ma) and maybe taken into consideration in the decision mentioned above and this KS can have the effect described in such decision.

o these MHO-Ma controlled by local MIAD0 MHOS may be designed to be context sensitive (i.e. perhaps during a potential PTC / OC be conceived differently than during an ongoing PTC / OC) and / or multimedia type (that is, perhaps after or at the same time as a sound signal to a TLN, to copy graphic or textual information in your terminal system in parallel and eventually without affecting the VoIP audio information).

or in each abstract and / or material implementation of each MHO-Ma, all types of MHO-Ma may be most closely intertwined in such a way that they are not identifiable as such individual types by a user of a terminal system affected by them I the operator of the local IAD can, at least for one and / or all the entities of its local terminal system (for example those of its OCs and those of this same), establish MHOS respectively the same or different in terms of content and differentiate them accordingly or conceive them in a very simple way. The latter means: in an MHO-KoMa they always specify only trivial limitations (such as: “New host system MHOM = local IAD” and “new terminal system = local terminal system”) and in an MHO-GeMa they always prescribe only trivial user communications (such as ❖ “in case of risk of HO for system Ax> a short beep signal ”and a“ current sharedIAD operator id blink ”and a“ signal strength blink ”❖“ in case of HO start for the terminal system Ax> twice a short beep signal ” and a "sound goodbye warning, Operator ID of the current sharedIAD ”and a“ blink of signal transfer ”

ES 2 368 019 T3 ❖ “in case of an HO termination for a terminal system Ax> three times a short beep signal” and a “hello beep, new shared IAD operator ID” and a “power blink new signal ”❖“ in case of an HO error for the terminal system Ax> seven times a short beep signal ”and“ three times a long beep signal ”).

While the communication of the long and short sound signals can be valued as HOCISMa, the sharedIAD Operator Id sound notices are definitely (rudimentary) advertising information communications. These MHO-Ma can be specified globally for all local end systems or selectively for particular local end systems and the latter can already be configured in advance without the possibility of change (which here is completely irrelevant, since these questions are of the configuration and material implementation of the invention).

The person skilled in the art knows that the MHOS of an operator of a virtual or real local MIAD in a material implementation (embodiment) of the Wsurfing procedure is a specification of this local MIAD, that the operator partially or totally introduces in it in some way or / and is already contained in it and the operator only configures it and / or is pre-set in it without the possibility of change and the MHO-Ma of this local MIAD ( belonging to this MHOS) is done through the interpretation of this MHOS by this local MIAD. Also know that any special MHOGeMa and their special CI correlations do not belong to the essence of the invention, but only the fact that they are both in each MHOS (according to claim 1) so that in any case each GeMa-MHO is characterized by the very special technical characteristic of a communication "limited by CI correlation" between the user of the terminal system "MHO" and his local MIAD for the realization of an MHO-GeMa of this type, although other MHOs can also present this characteristic.

the attribute "private homeMIAd" of the MHOS serves only to highlight the "privacy" of these MHO management actions characterized above for and only for the operator of this and only this local MIAD. Comment in this regard: the operator of the abstract local MIAD can be realized by means of two different material persons, an abstract "operator" can represent a "material human operator and / or a material human manager".

This privacy excludes, therefore, that a second operator in addition to this local MIAD operator as first, perceives the private MHOS of the local MIAD or fixes or modifies it without the first knowing and consenting to it. If this second is in particular an operator and / or manager of a network of some kind (which is not the network of this local MIAD) or of a service (which is not the service of this local MIAD) then these MHOS are inaccessible and incomprehensible. This privacy does not mean, however, that a second did not know or could know which MHOS a local MIAD operator can associate with it fundamentally in some way. There will be no additional encryption of TLN data that is ultimately necessary and known.

there are two types of local MIAD: a "real and a virtual local MIAD" type, both types eventually in both the material and abstract implementation. For each local MIAD (for a real or virtual MIAD) there is conceptually just a “logical” manager and a “physical” operator. In the case of a real local MIAD, its manager and operator are identical, which in both interpretations does not have to be the same.

It is already obvious from the previous linguistic use that in this document both the concepts / terms "MHO", "MHO procedure" and "MHO process" as well as "MHO-PDU" and "PDU" (PDU protocol data unit) are used respectively occasionally as synonyms, the terminology then somewhat simplified in the sense of its little loss of precision, (although this in the first case is not allowed in itself since an abstract "process" is always an abstract application of an abstract "procedure", that is, its abstract "instantiation of the application").

now the clarification of some concepts / terms more adapted to the eventualities of this patent application is finally being carried out.

or "homeWLAN" or "homeNet": in this document an A0 terminal system is administratively associated with a local WLAN or homeNet and its at least one real or virtual local MIAD according to the invention. A0 is for this local WLAN / homeNet / MIAD a "local end system". The simplest example of a local MIAD / local WLAN / homeNet according to the invention can be realized by means of a WiFi-IAD / WLAN and its local terminal system A0 (a private individual with a WiFi telephone). This WiFi phone A0 can then by means of an arbitrary sharedWiFi-WLAN Wx or Netx surf the network / Wsurfing according to the invention provided that A0 can be "registered" (see below) in Wx / Netx and the local MIAD of A0 contains an MHOS / MHOM (and this is already prepared to handle a Wsurfing connection with the Wx / Netx IAD). This generally known concept of

ES 2 368 019 T3

Local WLAN / homeNet is extended in this patent application first of all to the concept used here WLAN / Net (see section B). Secondly, it also extends to the possible associated "not true" local terminal systems, for example telephones such as the one mentioned above A0, this local "not true" characteristic of a terminal system may be induced to any server / IAD by means of a KS (see below), for example your own system, like that of your OC or your PTC or that of your other terminal system or the entire local WLAN network or this IAD / Server etc. In other words, a KS can also cause it to be relieved or even to be relieved by an IAD / server, an OC of a terminal system or PTC, for example with the “really associated” MHOM or even if this system is not a "real" local terminal system of this MHOM / IAD / server (in the sense mentioned above). In this patent application the local WLAN / homeNet / MIAD belongs to both its local “real” and “not real” terminal systems.

o “Registration”: an A0 terminal system that receives an electronic signal from eg a WiFi WLAN network or another network, can use this for communication, in particular over the Internet, usually only after it has requested to at least one (possibly several) of your IADs or base stations, etc., the permission to use this network. If granted, then terminal A0 is registered with this network. The procedures or protocols between A0 and this IAD / base station according to which this application and grant or also offer / acceptance of permits for the use of a network occurs, for this patent application are irrelevant. However, it is still defined: A0 is “accessible” on a Netx when A0 is registered or can be registered. Eventually it is sufficient that A0, is registered or can register for Wsurfing, as explained in section D, being possible modalities and implementations of a limitation of registration or a limited possibility of registration irrelevant in this patent application.

o “Netsurfing connection” (NSC): this is at least one L3 connection of an OCO segment of the OC0 between A0 and Z0, specifically between A0 and an S0 system of / in a WLANx / Netx that is different from local WLAN0 / homeNet0 of A0.

o "KS communication status": It has already been explained before that an OC / PTC of a specific communications application based on the Wsurfing procedure (for example in the case of the PTC with specific characteristics such as the emergency call or reduced cost calls of all kinds or calls to the center customer service or calls to monitor, or calls from minors or calls from remote Fem networks or WLAN or places or events of / in specific moments) can be characterized by the characteristics that in Wsurfing of an A0 terminal system lead to preferential treatment, for example, by being able to relieve their 0C or even have to be relieved, by whoever, as long as it is technically adequate (not considering the commercial or legal or other basis, of the necessity or meaning of this preference in this patent application, but only the fact that it may or may not be present).

However, this KS can also maintain a replacement treatment of another type or that harms an OC, through which its IAD / server, and as always, up to the denial of relief, that is, the rejection of a "home" feature for the entity.

The system of the method / device according to the invention or of the entities of an OCO (see below) then impair the sets of relay characteristics of the OCs.

o "Entities of an OCO": they will be understood as both the Li entities of their connections and the Li connections themselves, the at least one network necessary for its realization and eventually another element necessary for it.

The flow chart of Figure 4 shows the steps of the method of independent claim 1. Figure 5 shows the HW / SW components of the abstract media of a device according to the invention according to claims 14 to 16. To the bus (1) are generally connected: the memory (2) for storing, among others, the MHOM software module that contains the MHOMS, the processor (3) for performing, among other things, this MHOM functionality in accordance with the MHOS, the input / output devices of data (4) for the reception and transmission of MHO PDUs over at least one network, the data input / output devices (5) for the exchange of at least one MHO PDU between the MHOM and at least one functional local non-MHO module (optionally through a local coupling device implemented with a means of the claim main device).

Correspondingly, this document considers in particular that its abstract device for web browsing consists of abstract function HW / SW components, this association of a functional network navigation device component to the HW or SW being totally irrelevant. . What is important is only that the abstract realization of the functional components of an abstract network navigation device can occur by means of functional autonomous HW / SW components of the network navigation device or IAD / terminal system HW / SW components. the same function and / or functionally suitable or HW / SW components of the same function and / or functionally suitable from other systems (for example from an operating system and functional HW components managed by it).

Apart from the first case, there is then an “abstract HW / SW resource allocation” between the components

ES 2 368 019 T3 of the Wsurfing device and the functional components of the other mentioned systems. This abstract HW / SW resource sharing may or may not be found again in a material implementation or embodiment of this Wsurfing device and is called in the first case "material HW / SW resource sharing". That is: an abstract realization of a network navigation device in an IAD / abstract terminal system of the network navigation device can in that case respectively share abstract HW / SW components of the same or suitable function by abstract resource sharing for a function, for example an operating system (and the abstract HW components managed by it).

Concluding in reverse: an abstract implementation of a network navigation device to be completed by an abstract terminal system / IAD that is to be supported by a network navigation procedure does not possibly need any HW extension of this IAD / terminal system for this purpose, since its abstract HW components are sufficient for this implementation, that is, it can be achieved by allocating abstract HW resources, with the IAD / abstract terminal system to support. This can then also be applied to a hardware implementation of this IAD / terminal system of the network navigation device by means of an IAD / hardware terminal system and its hardware HW components.

The above discussion of the modeling of the abstract HW / SW components of the medium of a network navigation device serves to clarify the purely functional type of the element according to the terms / meaning of the claim, by virtue of which materialization by means of forms of realization of specific "suspicious web browsing" it has to be decided whether the second invades the scope of protection of this document or not.

This patent application relates primarily first of all to embodiments of the network navigation method / device which in relation to their material HW components are fully implemented by means of material HW components of the IAD / material terminal systems to which support is (should) be given by these embodiments, that is, together they only comprise additional material SW components (depending on the web navigation device / procedure). The material implementation of such a network navigation device is consequently based on its material resource sharing of its material HW components with those of the supported material IADs / terminal systems.

That the material implementation of the network navigation procedure is completely possible by means of material SW components is elementary for the person skilled in the art. And he also instantly perceives that all the means of a network navigation device claim are implementable by means of material SW components, insofar as they are not based on the abstract HW components of figure 5, which in turn are implementable to through the allocation of material resources (see above). However, the scope of protection of this patent application is not limited to such special embodiments, but these should optionally contain additional HW components specific for web browsing.

D. Detailed description of the invention

This section D should help to avoid that the meaning and / or scope of protection of this patent application is determined from its very limited example embodiments and is limited to them, which although it is unchecked from the "logic of patents" and that above all patent law strictly does not allow, However, it has happened to the authors of this document in other of their patents in legal disputes and that is why the wording of this patent application is marked a lot, and not based on the terms of the claims intentionally put in a very abstract way and therefore more far-reaching. The form of interpretation that should prevail, that is, the procedure for determining the meaning of a patent based on its expressions (with respect to all other possibilities of interpreting a procedure, determining the meaning or form of interpretation of a patent ) is specifically set forth without equivocation in all patent law rules.

For these two reasons section D below describes the essence of the invention of the present patent application also by means of a somewhat extensive clarification of the process claims. A repetitive and comparable length comment on the claims of the device is therefore not necessary. Section D is therefore a part of the description of the method / device according to the invention.

To begin, remember three aspects that have already been partially covered in this document:

The individual characteristics of the method or device according to the invention are not subject to any limitation not mentioned herein, in particular to any limitation of a "common context" of the individual characteristics of the method or device according to the invention, whoever the that it conceived a “common context” of this type and how it was constructed, since it could not be justified from any word in this document.

ES 2 368 019 T3

Since all the terms or meanings of the claims of this patent application define these characteristics of the method or device according to the invention solely and exclusively in its essence, the present document does not touch on anything at all of the variants of implementation of these characteristics in any rather, these characteristics are "functional" or "abstract", that is to say purely conceptual.

In the present document (including its claims) the word “one” (in the event that “at least” does not exist) and all its conjugations, declensions or variations represent “at least one”, being possible a substitution with some type of sense.

Regarding claims 1 and 2: its first paragraph establishes the fundamental characteristics and terms of the PT arrangement with which the network navigation procedure works.

For this, let us first remember that in this patent application an OC0 according to claim 1 or 2 (see section C) only needs to be potential. A known example of this is an OSI connection that is conceptually established at the latest with the decision of a TLN to initiate a call to any emergency number, for example 110 or 112, that is, it exists (in the potential sense) from the moment in which the TLN (abstract) (as part of the A0 terminal system) thinks to call it. Another example of this is a potential OSI connection between TLN A0 and a potential TLN Z0 accessible to the first when the second calls it, considering as the time of the MHO the one in which there was already a TLN Z0, an assumption whose authorization is irrelevant here , (but not unauthorized). In the case of the use of the IP-TV communication application, its potential OC0 exists at the latest as soon as the A0 user then makes a “program selection”.

In this case, a reduction of the terms in this patent that have no effect is also indicated: when speaking of a PTC between A0 and Z0, one must always understand “a PTC between each of its at least one TLN in A0 and Z0” .

Secondly, in this case, the characteristics or in claim 1 of an "MHO-GeMa" and / or in claim 2 of the A0-OC0 relay are already mentioned that do not materialize any of the state-of-the-art procedures of HO or of Internet technology in mobility: these HO management features were not known at all until now (see section A and C).

Brief clarifications are also made with respect to steps a) -b) of claim 1 and 2, in which it should be clear that there are other steps, not mentioned in a) -b) but evident to the person skilled in the art. , and therefore are not considered, which requires web browsing ..

The realization of an A0 MHO in a Netx according to claim 1/2 begins in the realization at least once of the verification step a) through which determination of the "presence of an accessibility signal of A0 in the Netx. Since the previous descriptions of the invention do not limit this in any way, the content of the meaning of these terms a) is precisely what is intuitively evident: there is a signal, of any type and detected wherever and however it may be, whose presence says that A0 can communicate, since a0 can register or is registered in the Netx, through its IAD or BSx and its local MIAD0 with the terminal systems on the whole of the Internet and is accessible on the Netx (see the beginning of section B and the end of session C).

An abstract or material implementation of steps a) and b) can effect an arbitrary time overlap, the skilled person knows for example that a separate pre-check procedure from a) is not necessary to execute a) and b). In particular, depending on the meaning or terminology, a test a) can be performed once or several times.

The embodiment according to claim 1 or 2 of an MHO can use, imply or presuppose a material implementation, in addition to steps a) -b), of other steps that may eventually occur automatically and / or comprise other alternative MHO-Ma optional like maybe the use of IP TV. That is to say: claims 1 and 2 say absolutely nothing about any questions of the material implementation of their procedures, for example when and how and under what conditions the effective registration of A0 in the Netx can and / or has to take place. It is clear to the person skilled in the art, however, that eventually none of the procedural steps necessary for registration have to be executed so that the MHO can be started and / or executed and / or terminated according to a) -b) ( as in particular it should be possible in the case of the implementation of the Internet protocol IPv6 in terminal systems / IAD / BS). That is to say: the Wsurfing / web browsing procedure can take place completely and several times even though the surfer or his terminal system is not registered anywhere or in any case not in the real or virtual IAD / BS that eventually carry out the registration prophylactically. and implemented in a distributed or local way. The same applies for

ES 2 368 019 T3 your establishment and / or prophylactic maintenance of a complete or partial NSSC0 network navigation connection for A0 and the A0-OCO and / or the IP TV connection and / or other optional MHO-Ma connections for A0 ( for example for any relevant advice for the security to its user and / or security guarantor in another place) before registering and / or deregistering A0 in the Netx, knowing the user A0 the prophylaxis of this type and / or making use or not Of the same).

That is, for the person skilled in the art, none of the variants of the method of this type according to the invention, of which only some have been mentioned here by way of example, is excluded from the terms or meaning of claim 1 or 2 and its description in this patent application. In other words, the meaning or terms of claim 1 or 2, at least for this description of the process according to the invention, comprise all similar variants.

The Wsurfing method according to claim 1 makes it possible to use both relay methods (both relay without tunnels and relay with tunnels, see claim 3), therefore it does not contain any limitation of the "tunnel freedom" . However its MHO is subject to a limitation with respect to claim 2, in that it has to materialize a GeMa and its CI correlation. These limitations do not appear in practice as such a phenomenon, but rather as an advantage of the network navigation procedure (see section C for the advantages of a GeMa and its CI correlation in an MHO).

An abstract relay refers to each of the bits transmitted to A0-OC0. But it is clear that each material implementation of the network navigation procedure will proceed in such a way that it only needs to guarantee the materialization of this relay feature without tunnels for certain conditions (for example, the volume of information transmitted to A0-OC0). The person skilled in the art knows how this occurs and under what conditions and why this is reasonable.

In relation to the meaning and terminology of claim 1/2 it is finally mentioned still that or the variants of the abstract or material implementation of a "management according to MHOS0 of an implementation of HO (under the control of the real or virtual local MIAD0 implemented in a distributed or local way and their respective MHOS parts) at least according to the preceding clarifications are known to the person skilled in the art and therefore irrelevant, that is, in relation to its abstract or material implementation it is not limited in any way whatsoever and the “additional commercial communication ❖ does not require an additional exchange of PDUs (but can be produced by the exchange of PDUs which is still required), ❖ nor is it limited in relation to the network used for it (you can use a different network than the one you use anyway).

With regard to the scope of protection of claim 1 or 2 this implies in particular: that insofar as an embodiment determines by means of any non-MHOM (assumption) (which is not limited in any way here) the presence of a signal according to a) and thus causing the successful execution of stage b) in any way, enters (together with this non-MHOM) within its scope of protection.

The five figures 6a-e also make fundamental clarifications with respect to the PT provisions, in which the procedure for browsing the network, Wsurfing is applicable, in which your MHOM and / or your real or virtual local MIAD and / or your MHOS are implemented in a distributed and abstract or material manner. For simplicity, it is assumed in figure 6a that an S0 system with a part of a virtual local MIAD could control and eventually execute only the KoMa and an S1 system with another part of a virtual local MIAD could only control and eventually execute GeMa (both both completely). The three figures 6 bd differ from the same only in that as in figures 6 bc each of the two types and in figure 6d both types of MHO-Ma are located in a real local MIAD0. In this regard, it is observed that S0 and / or S1 and their virtual local MIAD parts (in Figures 6a-c) can be located in a PT network whose operator then supports the Wsurfing procedure, so that in these cases it is possible to place functionally in a simpler way another real local MIAD, as in figure 6d, in particular it can be a sharedIAD of the ones currently installed (see below). Of course there are a multiplicity of hybrid forms of these prototypical PT arrangements for a web browsing device or method, which are apparent from the terminology or sense of claim 1 or 2 and the foregoing description. Summarizing this: all the forms or structures of the distributed abstract and / or material implementations of the method according to the invention are collected for the person skilled in the art with this description of the meaning or terms of claims 1 or 2.

Of obvious economic interest, as mentioned above, is the complete integration in terms of the method according to the invention of a local MIAD in a network, be it a PT network or a large WLAN, or for example in a network server, since thus a “functional equipment” of many IADs can be achieved

ES 2 368 019 T3 without Wsurfing capability already installed with easy web browsing functionality (full “virtual local MIAD server”). Figure 6e shows this PT arrangement with a large WLAN network and only a single virtual local MIAD server. In order to achieve the desired "local MIAD privacy" in this case, that is, to guarantee that the network operator / manager of the server hosting the virtual local MIAD server does not gain access to the hosted virtual local MIADs, the communication of an operator or manager of such a local MIAD must be equally unintelligible for the operator or manager of the network / server as, for reasons of this communication, the MHOS stored in a virtual local MIAD of this type for it. The person skilled in the art knows how this can be achieved both in an abstract implementation and in a distributed or centralized material implementation of a procedure or device for navigating the network, that is to say from your local MIAD, your MHOS, your MHOM, and of the modules that execute the functions.

Figures 6 therefore describe possible divisions, that is to say possible distributed implementations, (only of the GeMa necessary for the MHOs) from other MHO-Ma functionalities. Figures 7a-e represent for each one of them a possible separation, that is, a possible distributed implementation, of its control function of the local MIAD0 of a module of the function to be executed in another system, that is, everything that does not distribute still the implementation of the MHOS. Figures 8a-e therefore describe for each MHO-Ma functionality a possible separation of its local MIAD0 control functions from at least a part of the MHOS that controls them by distributing them in two systems. In this sense, at least a part of the MHOS itself can be considered as achievable, or at least it is open to interpretation.

Suitable, ultimately material, distributed implementations of this type make it easier for operators of large networks or Internet servers to offer, on the basis of the method according to the invention, innovative PT multimedia services of the most varied in all possible partnerships. , for example with sharedWLAN operators and / or program producers for IP TV.

After this it is particularly clear that "presents" in the terms of the claims should not be limited to "contains" or "comprises" at the "present time" but rather that for a "presents" all the other possibilities of interpretation apply. of natural language that make sense in this context, for example "related to" and / or "to observe / follow", and this also includes the future.