ES2395638A1 - Procedure and system for monitoring, management and control of wireless networks multi-technology (Machine-translation by Google Translate, not legally binding) - Google Patents

Abstract

Procedure and monitoring system, management and control of multi-technology wireless networks. The invention consists in the design of a new multi-technology and multi-manufacturer wireless network management, monitoring and control system using the functionalities and information exchange structure provided by the ieee 802.21 standard. The invention foresees using an existing signaling standard for other purposes, being fully compatible with devices that already implement the standard, both clients and access points. Additionally, the use of an mih client in the user devices is proposed, so that it is possible to implement a network-controlled link management, unlike the networks based on the ieee wireless standards family, where the control of the connectivity is executed in the client, since it is he who initiates the process of association and re-association to the access points, as well as the beginning of the handover process. These improvements have an impact on a lower cost of investment and operation on the part of telecommunications operators, since they can simplify the management of their systems, unifying the control and monitoring systems of the different transmission technologies used. (Machine-translation by Google Translate, not legally binding)

Description

Procedure and system for monitoring, management and control of multi-technology wireless networks

SECTOR OF THE TECHNIQUE

The invention falls within the technical sector of radiocommunications, and more specifically, in the field of wireless communications and mobile communication systems.

STATE OF THE TECHNIQUE

The IEEE 802.21 standard is intended to improve the experience of mobile users, facilitating handover (hereinafter) transfer between heterogeneous networks. This includes networks belonging to the 3rd Generation Partnership Project (3GPP), 3GPP2 and both wired and wireless media of the IEEE 802 family of standards. The IEEE 802.21 standard provides intelligence at the network layer level, as well as other information from the network related to higher layers to optimize these handover procedures between systems.

This standard also supports the cooperative use of the information available in the mobile node and in the network infrastructure. In this sense, the mobile node is optimally located to detect the available networks, while the network infrastructure is better prepared to store the global information of the network or networks, such as lists of adjacent or neighboring cells, location of the mobile nodes , or the availability of service in higher layers.

In general, both the mobile node and the base stations or access points can be multi-modal, that is, capable of supporting multiple standards of radio access and simultaneous connections to more than one radio interface. Under this scenario, both the mobile node and the network make decisions about connectivity.

The network, broadly understood, can include different technologies and transmission protocols, as well as a mix of cells of different sizes, such as those that implement IEEE 802.11, IEEE 802.15, IEEE 802.16, 3GPP and 3GPP2 technologies, with coverage overlay . The handover process can be initiated at the mobile node or at the initiative of the network itself, usually after performing certain measurements of the radio interface. Radio measurement reports may include data such as signal quality, synchronization time differences or transmission error rates. Specifically, the standard includes the following entities:

a) Media Independent Handover User (MIH User). This logical entity is responsible for the management tasks, either of several elements that make up a complex network or of a specific device independent of the network. Therefore, its implementation depends on the intelligence required by the device. The MIH User sends command messages with local or remote MIH Link destination. If the message is destined for the local MIH Link, the message passes through the MIHF by acting as a bridge. On the other hand, if it is destined for a remote MIH Link, the MIHF behaves like a router towards the remote MIHF. When a MIH User generates a command, it is automatically subscribed to the associated event message. Thus, when MIH Link launches the associated event, the recipient is ready to receive and treat it.

b) Media Independent Handover Function (MIHF). It is in charge of communicating the MIH User with the MIH Link. It is a management entity that obtains network information from different protocols, relaying it to the upper layers of the protocol so that they can make appropriate decisions. Message retransmission is possible because the MIHF stores the command messages that the MIH User sends to the MIH Link, either local or remote, in a database. Together with the command message, the associated event message must be stored. In this way, when it is received from a MIH Link to a MIH User, the MIHF will be able to retransmit the message in a correct way, taking into account that in order to act as a message router, each MIHF must have knowledge of network topology

c) Media Independent Handover Link (MIH Link). Acquires the data at the link layer level of the different technologies and generates the event messages requested by the MIH User. Its implementation in a device is optional and depends on the role that the device takes within the network. In order to receive and handle the events that the MIH Link generates, the MIHF and the MIH User must have previously subscribed to them. If the MIHF has not registered for the event, it will arrive but will not be relayed to higher layers. If it is the MIH User that has not registered, the event received will be left untreated.

In addition to the definition of logical entities, the IEEE 802.21 MIH standard consists of the following elements:

a) A logical and conceptual structure that allows the continuity of the service while a mobile node (MN) transfers between heterogeneous technologies at the link layer level. The operating framework is based on the presence of a stack of mobility management protocols within the

ES 2 395 638 Al

network elements that support the handover. This framework defines reference models Media Independent

Handover (MIH) for the different link layer technologies supported.

b) A set of enabling functions of the handover within the protocol stacks of the network elements. This logical entity controls the handover process and, by definition, supports centralized or distributed decision-making architectures.

c) A Media Independent Handover Service Access Point (MIH_SAP) and associated primitives defined to provide MIH users with access to MIHF services. The MIHF offers the following services:

1) The media independent event event: Detects changes in the properties of the link layer and initiates appropriate events (triggers) from local and remote interfaces.

2) The media independent command service: Provides a set of commands for MIH users that allow you to control the link properties that are relevant to the handover and switch between links if necessary.

3) The media independent information service: Provides information about the different networks and their services, allowing a decision to be made as effective as possible through heterogeneous networks.

d) The definition of new access points at the link layer level (SAPs) and the associated primitives for each link layer technology. The new primitives help the MIHF to obtain the information of the links and control the behavior of the link during the handover. If applicable, it is recommended to implement the SAPs as modifications of the standards for the respective link layer technologies.

The following patents have declared systems that structure and order handover processes:

•

"Mechanism to discover 802.21 remote events and information services" by Stefano M. Faccin, a patent assigned to Nokia Corporation.

•

"Seamless handoff across heterogeneous access networks using a handoff controller in a service control point" patent assigned to Telecordia Technologies Inc.

•

"Method and Apparatus for media independent messaging over the internet" patent assigned to Interdigital Technology Corporation.

•

"Method and Apparatus for facilitating inter-network handover" patent assigned to Interdigital Technology Corporation.

•

"Apparatus and Method for providing service for media independent handover" by Eun-Ah Kim, Jong-Hwa Yi and Jung-Hoong Jee.

•

"System and Method for implementing a media independent handover" patent assigned to Interdigital Technology Corporation.

•

"Wireless Communication Method and System for implementing media independent handover between technologically diversified access networks" patent assigned to Interdigital Technology Corporation.

In general, these systems focus on structuring only the handover processes between different networks, without addressing the management, monitoring and control of the networks or aspects of service quality.

The present invention focuses on the design of a new multi-technology and multi-manufacturer wireless network management, monitoring and control system using the functionalities and information exchange structure provided by the IEEE 802.21 standard. In this sense, one of the most important improvements that this invention develops is to use an existing signaling standard for other purposes, being fully compatible with devices that already implement the standard, both clients and access points.

In addition, the use of a MIH client in user devices is proposed, so that it is possible to implement a network-controlled link management, unlike networks based on the IEEE family of wireless standards, where the control of the connectivity is executed in the client, since it is this one that initiates the process of association and re-association to the access points, as well as the beginning of the handover process.

These improvements have a lower cost of investment and operation on the part of telecommunications operators, since they can simplify the management of their systems, unifying the control and monitoring systems of the different transmission technologies used.

Therefore, the object of this patent covers the different architectures contemplated by the Multi-technology Wireless Monitoring, Management and Control System based on the IEEE 802.21 Standard, which includes a centralized variant and a distributed variant, as well as the different configurations possible.

DETAILED DESCRIPTION OF THE INVENTION

The present invention is a Wireless Network Monitoring, Management and Control System based on the IEEE 802.21 standard, with the ability to manage multiple technologies and implement transfers between different networks.

As described above, the proposed system supports a centralized implementation with a hierarchical structure based on three levels (Figure 1), and a two-level structure for the case of distributed architecture (Figure 2). In the latter case, one or more Service Points (PoS) can be configured as MIHF nodes that perform the distributed monitoring, management and control functions.

To support the centralized structure, a new entity fully compatible with that specified in the IEEE 802.21 standard, the Media Independent Handover Super User (MIH S-User), has been defined. The MIH S-User is responsible for making global management and control decisions and centralizes the monitoring functions of the system.

In the case of centralized architecture, from a hierarchical point of view, the highest level is occupied by the entity called the central controller, which implements the MIH S-User. The central controller is responsible for the monitoring, management and control of the elements hierarchically located below it, which implement a MIHF entity in accordance with the IEEE 802.21 standard in charge of sending all signaling traffic to the MIHF located in the controller central. In the second level are the PoS, that is to say the wireless service points, base stations or access points, segmented in networks of different wireless technologies, which also implement the IEEE 802.21 standard. Finally, in the third hierarchical level are the mobile nodes MN or wireless clients, which can be managed and monitored from the controller. MNs can implement the IEEE 802.21 protocol or not. If implemented, they can be managed much more precisely in addition to being able to control transfers between PoS of the same network (in the case of WiFi) or even between networks with different radio technologies. A detailed outline of the centralized hierarchy proposed by this invention is shown in Figure 3 and an example of implementation is shown in Figure 5.

In the case of distributed architecture, from a hierarchical point of view, the highest level is occupied by the PoS that implement the IEEE 802.21 standard. These nodes cooperate with each other by exchanging signaling information to control the associated mobile nodes in a coordinated and consistent manner. In the second hierarchical level are the MNs, which in case of implementing the IEEE 802.21 standard, can be managed much more precisely, also controlling the transfers between PoS. A detailed scheme of the defined hierarchy is shown in Figure 4 and an example of implementation is shown in Figure 6.

To generate the monitoring, management and control messages, the system makes use of the services defined by the IEEE 802.21 standard, allowing the system to be compatible with equipment from various manufacturers that support said standard. In addition, a new entity is defined, fully compatible with those specified in the IEEE 802.21 protocol, to ensure backward compatibility of the control and monitoring system with respect to MIH devices:

• Media Independent Handover Super User (MIH S-User). In the centralized architecture, this logical entity is responsible for all control and monitoring tasks of those elements that make up the network or networks supported by the central controller. As in the case of the MIH User entity, the MIH S-User sends command messages to a local or remote MIH Link.

The scheme of operation of the control and monitoring protocol has been represented in Figure 7. It shows the centralized version of the system, where the central controller periodically receives messages from each of the nodes of the network, decodes them and processes them. , storing the information related to each of them together with certain statistical information in a database.

The wireless client management strategy begins by discriminating those that are compatible with IEEE 802.21 and those that are not, since the controller initially segments customers by defining those on which it can manage and make transfer decisions and that are capable of generate MIH messages, and those clients that do not support the IEEE 802.21 standard.

This process is shown in Figure 8. Depending on the response, registration of the mobile node (MN) in the PoS occurs as MN MIH or is simply associated to the PoS, without being IEEE 802.21 compatible, obtaining the necessary data for the System management directly from the PoS.

ES 2 395 638 Al

From this moment the system is able to monitor, manage and control the network, terminating communication and sensing in the PoS if the MN does not implement a MIH User, or terminating communication and sensing in the MN if it implements a MIH User.

From the point of view of its structure, the implemented protocol contemplates three layers. These three layers are represented in Figure 9, where the messages that follow the IEEE 802.21 standard and the messages that are specific to the proposed control and monitoring protocol are specified. The three layers are detailed below precisely:

•

User layer: Implements network intelligence. It only runs on the node that acts as the central controller in the centralized case and on all nodes in the distributed case. Performs the processing of the information received to store it with the appropriate structure in a database for analysis. The main function of the user layer is to collect all the information received from the different elements that make up the network, taking into account that each message received contains the information of the node, the information of each PoS of the node and the information of each connected user to each PoS. The user layer receives information from the transport layer of the different wireless service points belonging to the network. In order to receive simultaneous information from different points of the network, it is proposed to use parallel programming, supporting multiple processing threads, which allows the different teams to send the data asynchronously.

•

Transport layer: It is the one that is responsible for the distribution of messages both to the local entities (upper and lower layer of the protocol) and to the remote ones (transport layer of another node). This layer is responsible for routing traffic to different entities, whether local or remote, although it does not have its own intelligence.

•

Network layer: This layer is responsible for obtaining the radio interface information of each equipment. It is responsible for obtaining the PoS information and entering it in the messages that are sent to the user layer. With the information that this layer provides, the control and monitoring of the network is carried out.

The system, as defined, is fully scalable and can support from small deployments to large multi-technology wireless deployments. Thus, a modular structure is proposed that, from a basic configuration, can grow in process capacity, supported technologies and the need for connectivity management, as shown in Figure 10. In this way a Control and Monitoring Center may exist. remote, which allows managing multiple deployments simultaneously.

The following points focus on highlighting the way in which the monitoring, management and control system makes use of the IEEE 802.21 communication protocol.

Registry

Following the procedure defined in the standard, the MIH User entity of the PoS registers to the Central Controller through a MIH_Regiser.request procedure. This message will include the list of supported radio interfaces as well as their address. The complete registration procedure is reflected in Figure 11. It is important to note that this procedure does not differ at all from the standard and therefore any PoS that implements a MIH protocol can support it. Similarly, MNs that have a MIH User entity incorporated will make a conventional registration with the Central Controller.

In case of working with a distributed architecture, the MN will register with its PoS, while these will not be registered with any higher hierarchy entity.

Monitoring

The central controller will obtain information from both the PoS and the MN, in case the latter implements MIH. If so, the MIH S-User will operate in a conventional manner for the management of Handovers. In addition, the MIH S-User will obtain additional information from the MN by properly configuring the measures taken by the MIH Link through the MIH_Link_Configuration_Threshold.request message. Specifically, the MIH S-User must send as many messages as MNs that you want to monitor. The type of measurements to be performed will strictly follow the standard, including power, quality and packet loss rate values. The periodicity of the measurements can be set using the TIMER_INTERVAL field. Figure 12 shows the exchange of messages contemplated by the standard for obtaining this information.

On the other hand, the central controller will obtain information directly from the PoS using either the MIH_Get_Information procedure or the MIH_Push_Information. In the first case, the central controller requests information from the PoS as shown in Figure 13. The PoS will reply by sending information that may be useful for network management and control. For the sending of this additional information, the standard includes variables of the “Vendor Specific” type in which it is proposed to send a list of associated users the PoS, channel used, security policy applied, signal level received, quality, rate transmitted and received as well as other parameters that can be extracted from the specific radio interface.

ES 2 395 638 Al

The standard offers us a second option and is to use MIH_Push_Information. For this, the sequence of configuration messages is more complex but once configured it will be the PoS who decides when to send a message. The configuration sequence is as follows. MIH S-User sends a MIH_Link_Configuration_Threshold with the initial thresholds to be monitored followed by a MIH_Event_Unsubscribe to not receive MIH Link events from the PoS. Previously, the MIH User of the PoS has been associated with the MIH_Link_Parameters_Report event using the MIH_Event_Subscribe message. In this way, when the threshold configured in the MIH Link of the PoS expires, the message will be received by the MIH User of the PoS. Once alerted of the expiration of a threshold, the MIH User of the PoS will send the required information using the MIH_Push_Information procedure.

Control

The MIH S-User of the central controller may manage the MN handovers (inter and intra technology) that have the MIH protocol available using the conventional procedures defined in the standard.

On the other hand, to indicate to the PoS the performance of certain actions such as the change of radio transmission channel, load balancing disconnecting users, as well as other actions that are useful to improve the performance of the system, this patent proposes two possible options based in the extension of two standard messages: MIH_Link_Action and MIH_Push_Information. The MIH_Link_Action command has 252 free-of-use commands that will be used to perform these actions. Figure 14 shows the control procedure. The second option uses the MIH_Push_Information command, which has vendor specific variables that will allow you to perform the required actions. Figure 15 shows the control sequence.

BRIEF DESCRIPTION OF THE DRAWINGS

To complement the above description and in order to help a better understanding of the design and operation of the Signaling Protocol and Monitoring System, Management and Control of Multi-technology Wireless Networks based on the IEEE 802.21 Standard, this descriptive report is attached , as an integral part of it, some figures, diagrams and diagrams where the following has been represented as illustrative and not limited:

-

Figure 1 shows the hierarchical structure of the system for a centralized architecture.

-

Figure 2 shows the hierarchical structure of the system for a distributed architecture.

-

Figure 3 shows a detail of the hierarchical structure of the system for a centralized architecture.

-

Figure 4 shows a detail of the hierarchical structure of the system for a distributed architecture.

-

Figure 5 shows an example of system implementation for a centralized architecture.

-

Figure 6 shows an example of system implementation for a distributed architecture.

-

Figure 7 shows the scheme of operation of the protocol for the centralized case, with the communication flows between the entities defined in the control and monitoring protocol.

-

Figure 8 shows the flowchart of the process of associating a client to a PoS of the system, in which it is determined whether it is a MIH client compatible with the IEEE 802.21 standard or not and the following actions that the system performs to give high a new MN.

-

Figure 9 shows the three layers of the protocol and the associated messaging for communication between the different layers of the protocol, specifying the communication flows that make use of the IEEE 802.21 standard and the specific communication flows of the proposed control and monitoring protocol.

-

Figure 10 shows the scalability of the system, which, being fully modular, can be expanded according to the needs via software licenses or via new hardware aggregation that expands the process capacity and bandwidth management capacity of the system.

-

Figure 11 shows the exchange of necessary messages in the process of registering a PoS with the Central Controller.

-

Figure 12 shows how the Central Controller configures the monitoring to be performed by the MN and it sends the reports of measurements made.

-

Figure 13 shows how the Central Controller, using the MIH_Get_Information procedure, obtains status information from the PoS.

-

Figure 14 shows the procedure followed for the Central Controller to send control orders to the PoS.

ES 2 395 638 Al

-

Figure 15 shows another option to perform control actions on the PoS by the Central Controller.

DESCRIPTION OF A PREFERRED EMBODIMENT

In the description of a preferred embodiment that follows, the terminology "Service Point" PoS "refers to any type of device connected to the distribution system and acts as a wireless hub of different mobile nodes using a compatible radio interface at the layer level of link with the technologies supported by the MIH standard. This concept includes 3GPP base stations, IEEE 802.16 WiMAX base stations or IEEE 802.11 WiFi access points (APs). The terminology "Wireless Node (WN)" refers to any type of device that incorporates one or more PoS of one or more radio technologies, such as a base station that supports WiMAX and WiFi over different radios. This WN behaves like a wireless router by integrating at least one MIHF entity that manages communications with the MIH S-User. The terminology "Mobile Node MN", "Wireless Client" or "User Equipment (UE)" refers to any type of device capable of connecting to a PoS through one or more wireless interfaces. These devices can optionally integrate a MIHF entity.

Figure 1 shows the hierarchical structure of the system for a centralized architecture, so that at the highest level is the entity called Central Controller (101) that incorporates the logical entities MIHF and MIH S-User, previously defined in the document. In the second level, there are the wireless nodes that integrate the PoS (102) of the system. In the third level, there are the wireless clients (103) or mobile MN nodes that are associated with the different PoS of the system. The position of an element within the hierarchy is related to the associated control and monitoring capacity, the highest being that of the element that is at the highest level.

Figure 2 shows the hierarchical structure of the system for a distributed architecture, so that at the highest level are the wireless nodes that integrate the PoS (202) of the system. These nodes integrate a MIHF and a MIH User and are able to share information and use it in a coordinated manner, cooperating so that each node can apply control decisions consistent with the state of the network at a given time. In the second level, there are the wireless clients (203) or MN that are associated with the different PoS of the system. As before, the position of an element within the hierarchy is related to the associated control and monitoring capacity, the highest being that of the element that is at the highest level.

Figure 3 shows a detail of the hierarchical structure of the system for a centralized architecture in a central controller (301), where management has been segmented by technologies at the link layer level. In a preferred embodiment, each of the networks will constitute a manageable subsystem (304,304 ', 304' ', 304' '' ...) with own and individualized policies, as shown in the figure, allowing in the case IEEE 802.11 networks that each SSID constitutes a fully manageable subsystem independently. To each of these subsystems, an indeterminate number of PoS (305,305 ’, 305’ ’, ...) will be associated, each of them integrating a MIHF. In addition, as can be seen in this figure, a set of wireless clients (303) that can optionally incorporate a MIHF, constituting MIH clients, will be associated to each PoS.

Figure 4 shows a detail of the hierarchical structure of the system for a distributed architecture, where management has been segmented by technologies at the link layer level. As before, in a preferred embodiment, each of the networks will constitute a manageable subsystem (404,404 ', 404' ', 404' '...) with its own individualized policies, as shown in the figure . Each of these subsystems will be associated with an undetermined number of PoS (405,405 ’, 405’ ’, ...) each of them integrating a MIHF. Again, a set of wireless clients (403) that can optionally incorporate a MIHF will be associated to each PoS, constituting MIH clients.

Figure 5 shows an example of system implementation for a centralized architecture, where it is possible to observe data and signaling traffic, as specified by the legend. The central controller (501), which implements the MIHF and the MIH S-User, controls internet access (510) of the different wireless nodes (502) of the network, although internet access (510) could be distributed from so that only signaling traffic (505) is routed to the central controller. In this implementation, the wireless clients (503) that incorporate a MIH client are capable of sending both the data traffic and the signaling traffic of the control and monitoring protocol (505) via the wireless medium (504). One or more of these PoS will be connected to the distribution system (508) or trunk of the network through a wired link (506), which connects the wireless node to a switch (507) belonging to this backbone network. Finally, in this preferred implementation, after the central controller, there would be a router (509) that would interconnect the infrastructure with the internet (510).

Figure 6 shows an example of system implementation for a distributed architecture, where it is possible to observe data and signaling traffic, as specified by the legend. In this case, the different wireless nodes (601) of the network, which implement a MIHF, control the internet access (609) of the wireless clients (602). In this implementation, the wireless clients (602) that incorporate a MIH client are capable of sending both the data traffic and the signaling traffic of the control and monitoring protocol (604) via the wireless medium (603). One or more of these PoS, will be connected to the distribution system (607) or trunk of the network through a wired link (605), which connects the wireless node to a switch (606) belonging to this

Trunk network. Finally, in this preferred implementation, there would be a router (608) that would interconnect the infrastructure with the internet (609).

Figure 7 shows the scheme of operation of the protocol for the centralized case, where they are shown with the communication flows between the different entities defined in the control and monitoring protocol. In this scheme, particularized for a WiFi application scenario, the MIHF (702) resides in both the wireless node, a WiFi AP (709), which integrates one or more PoS, in the form of one or more IEEE 802.11 interfaces, as in the mobile nodes (711) that integrate a MIH client. The communication flow of the protocol (704) is established between the MIHF (702) of the UE and the MIHF (702) of the PoS through the wireless medium (710), and between the MIHF (702) of the PoS and the MIHF (705 ) of the central controller (708), while the local communication (703) is established between the MIHF (702) and the MIH User (701), and between the MIHF (705) and the MIH S-User (707) in those nodes that incorporate intelligence. This scheme also incorporates user equipment that does not incorporate MIH (712), but which can also be managed by the system.

Figure 8 shows the flowchart of the association process (801) of a client to a PoS of the system, in which it is determined whether it is a MIH client compatible with the IEEE 802.21 standard or not and the following actions that the system performs to register a new MN. The client, in the first place, is associated at the MAC (802) level to the device, since this procedure is defined in each of the wireless communications standards supported by the IEEE 802.21 standard. Once the client device is associated with the system, it can begin to interrogate it

(803) in relation to its compatibility with the MIH standard. If you have the MIH entity (804), with at least one MIHF

(805) and a MIH network entity, the system can send control and monitoring messages to the device, registering (806) a status variable in the system about its MIH compatibility. If the IEEE 802.21 standard is not supported, the MN is associated (807) to the PoS without MIH, registered (808) as a NO-MIH MN and (809) the MAC is registered as a NO-MIH client and its connectivity needs (QoS).

Figure 9 shows the three layers of the protocol and the associated messaging for communication between the different layers of the protocol, specifying the communication flows that make use of the IEEE 802.21 standard and the specific communication flows of the proposed control and monitoring protocol, in The following elements participate:

-

Database (901)

-

User (902)

-

Network associated with the central controller (904)

-

Network associated with service points (905)

-

Transport associated with the central controller (903)

-

Transportation associated with service points (906)

-

Standard Messages (907)

-

Proprietary Messages (908)

For its part, Figure 10 shows the possibilities of scalability of the system, which, being fully modular, can be expanded according to the needs via software licenses or via aggregation of new hardware that expands process capacity and capacity System bandwidth management, according to the following elements:

-

AP’s or single nodes Remote Control (1001)

-

Small deployments, Unique access technology (1002)

-

Medium deployments, Unique access technology (1003)

-

Medium / Large deployments Multiple access technologies (1004)

-

Large deployments Multiple access technologies (1005)

-

Wireless network monitoring and control center (1006)

-

Central Wireless Network Controller (1007-1007 ’)

-

Central controller of wireless networks with multiple nodes (1008-1008 ’)

ES 2 395 638 Al

Figure 11 shows the procedure for registering a PoS (1101) with the Central Controller (1102). The MIH User (1103) of the PoS (1101) initiates the procedure by sending a MIH_Register.request (1107) message to the MIH S-User (1106). The MIHF entity of the PoS (1104) will route the MIH_Register.request (1108) to the MIHF entity of the Central Controller (1105). Next, the MIH-F of the Central Controller (1105) will send a MIH_Register.indication (1109) to the MIH S-User (1106). In response to the registration request, the messages MIH_Register.response (1110) and MIH_Register.confirm (1112) will be sent.

Figure 12 shows the exchange of messages contemplated by the standard for the configuration and sending of measurements made by an MN (1202). First, the Central Controller (1201) configures the monitoring parameters. For this, the MIH S-User entity (1203) sends a MIH_Link_Configure_Threshold.request (1208) message that is routed by its MIHF entity (1204) until it reaches the MIHF of the MN (1205). With a Link_Configure_Threshold.request (1210) message, the MIHF entity tells the MIH Link (1207) what measures to take and what are the thresholds that will trigger the sending of reports to the Central Controller. The MIH Link (1207) confirms the reception of the message with a Link_Configure_Threshold.confirm (1211). In case of exceeding any of the thresholds configured, the MN (1202), specifically its MIH Link (1207), will send a Link_Parameters_Report.indication (1214) message to the MIHF entity of the MN (1205), which in turn will route it to the MIHF of the Central Controller (1204). Finally, the MIHF will send a MIH_Link_Parameters_Report.indication (1216) message to the MIH S-User (1203).

Figure 13 shows the procedure by which the Central Controller (1301) obtains monitoring information from a PoS (1302). The MIH User (1303) of the Central Controller (1301) initiates the procedure by sending a MIH_Get_Information.request (1307) message to the MIH User (1306) of the PoS. The MIHF entity of the Central Controller (1304) will route the request using an Information Service Transport message (1308) to the MIHF entity of the PoS (1305). Next, the MIH-F of the PoS (1305) will send a MIH_Get_Information.indication (1309) to the MIH User (1306) that will answer with a MIH_Get_Information.response (1310). This message will again be transferred between MIHF entities using an Information Service Transport (1311) message. Finally, the MIH S-User will receive a MIH_Get_Information.confirm (1312) with all the requested information.

Figure 14 shows an option for the Central Controller (1401) to execute control actions on the PoS (1402) using the MIH_Link_Action procedure. The MIH User (1403) of the Central Controller (1401) will send a MIH_Link_Action.request (1407) message to the MIH Link (1406) of the PoS. The MIHF entity of the Central Controller (1404) will send the request to the MIHF entity of the PoS (1405) which, in turn, will send a Link_Action.request (1409) to the MIH Link (1406). The MIH Link (1406) will confirm receipt of the order by sending a Link_Action.confirm (1410) that will reach the MIH S-User (1403) after passing through the corresponding MIHF entities.

Figure 15 shows another option to perform control actions on the PoS (1502) by the Central Controller (1501). For this, the message MIH_Push_Information is used. The procedure is as follows, the MIH User (1503) of the Central Controller (1501) sends the message MIH_Push_Information.request (1507) to the MIH_User (1506) of the PoS. To do this, first pass the message through the MIHF (1504) of the Central Controller (1501) that relays it to the MIHF (1505) of the PoS (1502). Received in the PoS, it is sent to the local MIH User (1506). The MIH User (1506) of the PoS (1502) creates the response message MIH_Push_Information.indication (1510) to the MIH User (1503) of the Central Controller. This second message passes through the MIHF (1505) of the PoS and is transmitted to the MIHF (1504) of the Central Controller, which will finally send it to your local MIH User (1503).

The devices on which the system is implemented, and in particular the central controller, are based on the use of a dedicated real-time operating system, capable of synchronizing the different managed elements, so that it is possible to establish transfers between PoSs of different link layer technologies or between Access Points of the IEEE 802.11 family of standards.

The materials, shape, size and arrangement of the elements will be subject to variation as long as they do not alter the essentiality of the invention.

The terms in which this report has been described must always be taken in a broad and non-limiting sense.

ES 2 395 638 Al

Claims (2)

1st.- Procedure for monitoring, management and control of multi-technology wireless networks, characterized in that it consists in the use of the IEEE 802.21 protocol in the processes of monitoring, management and control of wireless networks. 2nd.- Procedure for monitoring, management and control of multi-technology wireless networks, according to claim 1, characterized in that, in addition to the logical entities defined in the IEEE 802.21 standard, a new MIH entity called MIH S-User is defined " Media Independent Handover Super User ”responsible for making the global control and centralization decisions of the system monitoring functions. 3.- System for monitoring, management and control of multi-technology wireless networks, according to claims 1 and 2, characterized in that a plurality of mobile nodes (MN), a series of service points (PoS), and a number plurality of wireless communications networks with different radio access technologies, as well as means to implement transfers between said networks, with the particularity that the aforementioned wireless networks are monitored, managed and controlled through the use of the IEEE 802.21 protocol. 4th.- System for monitoring, management and control of multi-technology wireless networks, according to claim 3, characterized in that it has a centralized architecture, in which the MIH S-User entity is implemented in a Central Network Controller that centralizes the connection of decisions and globally monitors the network. 5th.- Multi-technology wireless network monitoring, management and control system, according to claim 3, characterized in that it has a distributed architecture, where the different wireless nodes or wireless service points (PoS) that implement the MIHF entity exchange information on the network and the clients associated to these nodes cooperatively to make distributed control decisions, taking into account the global state of the network. 6th. Multi-technology wireless network monitoring, management and control system, according to claims 4 and 5, characterized in that it incorporates specific communication mechanisms to provide the necessary information to a MIH S-User or MIH User entity and the associated logic to be able to take network control decisions that include handover control, link control, load balancing, association control and customer disassociation and management of customer service quality or service profiles or service flows through CQIs or other mechanisms designed for this purpose. 7th.- System for monitoring, management and control of multi-technology wireless networks, according to claims 4 and 5, characterized in that the system incorporates means of management of the standard measurements performed on the radio interface by the MNs as well as the extension "Vendor Specific ”for sending specific information by the PoS. 8th.- Multi-technology wireless network monitoring, management and control system, according to claims 4 and 5, characterized in that the system incorporates specific communication mechanisms to provide the necessary information to a MIH S-User or MIH User entity and the associated logic to be able to display the relevant network information in a monitoring service. 9th.- Multi-technology wireless network monitoring, management and control system, according to claims 4 and 5, characterized in that the system incorporates means to make use of the free-of-use commands available in the MIH_Link_Action procedure or of the variables "Vendor Specific ”Of the MIH_Push_Information message, and that allows the execution of control actions on the PoS. 10.- System for monitoring, management and control of multi-technology wireless networks, according to previous claims, characterized in that it incorporates a mechanism for managing user equipment that integrates a MIH client, so that their control depends on the PoS or of the Central Controller, depending on whether a centralized or distributed architecture is implemented, which yield their decisions at the link layer level to the MIH User of the PoS or to the MIH S-User of the Central Controller. SPANISH OFFICE OF THE PATENTS AND BRAND Application no .: 201231539 SPAIN Date of submission of the application: 05.10.2012 Priority Date: REPORT ON THE STATE OF THE TECHNIQUE 51 Int. Cl.: H04W36 / 00 (2009.01) RELEVANT DOCUMENTS

Category

56 Documents cited Claims Affected

X

US 2008305799 A1 (ZUNIGA JUAN CARLOS ET AL.) 12/11/2008, figures 5, 10 paragraphs [28-46]; 1-4

Y

5-7

Y

WO 2012021079 A1 (PORTUGAL TELECOM INOVACAO S A ET AL.) 02/16/2012, 5-7

TO

GAVRILOVSKA and ATANASOVSKI, Fac. Of Electronic Engineering and Information Technology, Univ. In Skopje, Macedonia; "Resource Management in Wireless Heterogeneous Networks (WHNs)", TELSIKS 2009, 9th International Conference - 7-9 October 2009; Pages 97-106. URL: // http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=5339398 1-8

Category of the documents cited X: of particular relevance Y: of particular relevance combined with other / s of the same category A: reflects the state of the art O: refers to unwritten disclosure P: published between the priority date and the date of priority submission of the application E: previous document, but published after the date of submission of the application

This report has been prepared • for all claims • for claims no:

Date of realization of the report 16.01.2013

Examiner B. Pérez García Page 1/5

REPORT OF THE STATE OF THE TECHNIQUE Application number: 201231539 Minimum documentation sought (classification system followed by classification symbols) H04W, H04Q Electronic databases consulted during the search (name of the database and, if possible, terms of search used) INVENES, EPODOC, INSPEC, WPI State of the Art Report Page 2/5  WRITTEN OPINION Application number: 201231539 Date of Completion of Written Opinion: 01.01.2013 Statement

Novelty (Art. 6.1 LP 11/1986)

Claims Claims 4-8 1-3 IF NOT

Inventive activity (Art. 8.1 LP11 / 1986)

Claims Claims 4-8 IF NOT

The application is considered to comply with the industrial application requirement. This requirement was evaluated during the formal and technical examination phase of the application (Article 31.2 Law 11/1986).  Opinion Base.- This opinion has been made on the basis of the patent application as published. State of the Art Report Page 3/5  WRITTEN OPINION Application number: 201231539  1. Documents considered.- The documents belonging to the state of the art taken into consideration for the realization of this opinion are listed below.

Document

Publication or Identification Number publication date

D01

US 2008305799 A1 (ZUNIGA JUAN CARLOS et al.) 11.12.2008

D02

WO 2012021079 A1 (PORTUGAL TELECOM INOVACAO S A et al.) 02/16/2012

D03

GAVRILOVSKA and ATANASOVSKI, Fac. Of Electronic Engineering and Information Technology, Univ. In Skopje, Macedonia; "Resource Management in Wireless Heterogeneous Networks (WHNs)". 09.10.2009

 2. Statement motivated according to articles 29.6 and 29.7 of the Regulations for the execution of Law 11/1986, of March 20, on Patents on novelty and inventive activity; quotes and explanations in support of this statement D01 is considered the prior art prior to the object of the invention document. Following the wording of claim 1, document D01 describes a monitoring, management and control system for multitechnology wireless networks (for example between 3G networks and non-3G networks), characterized by being based on the use of IEEE 802.21 protocol in the processes of monitoring, management and control of wireless networks, in which additionally to the logical entities that are defined in the IEEE 802.21 standard, a new MIH entity called MIH is specified Server responsible for making global control decisions and centralizing system monitoring functions (See paragraph 37, MIH Server acts as a Network Controller to make delivery decisions and establish the resources of the delivery network), with the particularity that a plurality of mobile nodes (WTRU / MN) participate in the system, a series of service / access points (AP) -see figure 10- and a plurality of wireless communications networks with different radio access technologies (Inter-RAT communications), as well as means to implement transfers between said networks (MIHF) which are managed and controlled by the IEEE 802.21 protocol -see paragraph 38-. No differences were found between the two documents and it is considered that the first claim does not meet the requirement of novelty, according to Art. 6 of the Spanish Patent Law. The second claim indicates that the monitoring system has a centralized architecture in which the MIH S-User entity is implemented in a central network controller that decides and monitors the network globally. The MIH Server element of D01 is considered equivalent to the MIH S-User entity of the request. In paragraph 37 of D01, it is indicated that said MIH Server acts on behalf of or representing the Network Controller to make decisions of the delivery and set the resources of the destination network. That is, this claim is also novel. Claim three specifies that the monitoring has a distributed architecture where the PoS implement a MIHF that exchange network and customer information to cooperatively decide on network control. Figure 10 of D01 shows the architecture of the mobile nodes (WTRU) and the access points (AP / PoS). Sayings PoS and WTRU each have a MIHF and have the ability to communicate with the central entity MIH Server to that decides on the handover of the network. In summary, this claim, like the previous ones, is not new. The fourth claim adds that monitoring includes handover control, link control, load balancing, association control and customer disassociation and QoS profile management ... D01 only indicates that the WTRU can take measures to send reports to the MIH Server and that it decides on the network and handover control, resource management ... although it does not indicate exactly what parameters are measured. These parameters are common to manage in a radio access technology and therefore, its measurement to manage the network as it is done in D01, does not imply inventive activity for an expert in the field, according to Art. 8 of Law 11/1986. By way of illustration, document D03 citing a system for managing resources in wireless networks is cited heterogeneous, which can work with the IEEE 802.21. This article explains the principles of resource management. A Typical architecture for this resource management is the JRRM. On page 5, second column, the Features that each radio access technology needs: traffic volume, load control, admission control ... State of the Art Report Page 4/5  WRITTEN OPINION Application number: 201231539 The fifth claim also incorporates the Vendor Specific extension to send specific information. Claims 6 and 7 indicate that specific communication mechanisms are used to give the necessary information to the entities and that free commands of the MIH_Link_Action or MIH_Push_Information procedure are used. D01 does not indicate which specific mechanisms are used to provide the information and therefore, the technical problem is how to deliver the information for management. D02 presents a system to manage the resources of the link layer for MIH where specific commands are introduced to the MICS (Media Independent Command Service) with the objective of allocating and releasing resources in the link layer. It acts on MIH_Link_Action. In summary, it is considered that these claims 5-7 lack inventive activity for a person skilled in the art who could use the system described in D01 with the specific mechanisms detailed in D02. The eighth claim clarifies that the system incorporates a MIH user equipment management mechanism, such that the control depends on the PoS or the central controller depending on whether the architecture is centralized or distributed. The system described in D01 incorporates a MIH function in the client devices, as can be seen in Figure 10. Being able to work with a centralized architecture (thanks to the MIH Server) or distributed (by the MIH of the PoS), It is obvious that the MIH client will adapt to one architecture or another according to the degree of integration desired (paragraph 30). This claim is not considered to meet the requirement of inventive activity. In summary, the application has no novelty for claims 1-3 or inventive activity for claims 4-8, according to Arts. 6 and 8 of the Spanish Patent Law. State of the Art Report Page 5/5