KR101248954B1 - Multicast support method for distributed mobility management network - Google Patents

Abstract

PURPOSE: A multicast supporting method for a distribution type of a mobility management network is provided to supply a handoff process of a mobile terminal for supporting IP(Internet Protocol) multicast and a method thereof, which selects an agent and a network for receiving multicast data corresponding to an anchor agent. CONSTITUTION: When a channel which is connected to an MMAA(Mobility Management Anchor Agent)1(130) and an MMAA2(140) exists, or another mobile terminal which is received in the MMAA exists, a tunnel is formed between the MMAA1 and the MMAA2. Received data is forwarded to the MMAA2 through the tunnel. A current received multicast channel, a transmission agent, or network information are received and registered. The current received multicast channel, the transmission agent, or the network information are transmitted from the MMAA2 by an MMIS(Mobility Management Information Server)(150). [Reference numerals] (100) Distribution type of a mobility management network; (110) Mobile terminal 1(MN1); (130) Mobility management anchor agent 1(MMAA1); (140) Mobility management anchor agent 2(MMAA2); (150) Mobility management information server(MMIS); (200) Content provider network; (AA) Handoff of MN1 from MMAA1 to MMAA2; (BB) Binding cache update request; (CC) Terminal registration request; (DD) Binding cache update response; (EE) Terminal registration response("G", agent or content providing network); (FF) Multicast data; (GG) Received channel registration("G", content provider network); (HH) Received channel response("G", content provider network);

Description

Multicast support method for Distributed Mobility Management Network

The present invention relates to network mobility management for a distributed mobility management network. In particular, an agent and network selection for handoff procedure of a mobile terminal for IP multicast support and multicast data reception for each anchor agent in a distributed mobility management network. It is about a method.

In the existing Internet, the host is assigned an IP (Internet Protocol) address, which consists of a network identifier and a host identifier. The network identifier is information for uniquely indicating the network to which the host is connected, and the host identifier is a host in the network. Information for uniquely identifying.

Thus, the host creates a socket address using the IP address and the force number of the transport layer, and establishes a connection with other hosts using the socket address. If a host establishes a connection with another host, the same IP address must remain static while the connection is established.

If a host moves from one network to another, the IP address assigned to the host must be changed because the network identifier must be changed. Since changing the IP address means changing the socket address, the previously established connection is terminated and the connection must be retried.

In order to solve the problem of disconnection when the host accesses the Internet by changing the network, the mobile node (MN) can maintain the existing connection even if the user changes his location. Mobile IP technology has been proposed. In the mobile IP protocol, when a mobile terminal detects that it has moved from one network to another network, the mobile terminal performs an operation defined in the mobile IP protocol. In other words, the mobile IP protocol may be referred to as a mobile terminal-based mobility support protocol.

On the other hand, a mobile terminal that does not implement the mobile IP function, a problem arises that each time to move from one network to another network must terminate the existing connection and open a new one. In order to prevent this, a technology for supporting mobility of a mobile terminal in an access network has been proposed to maintain a connection established even when a mobile terminal having no mobile IP function is moved. It is called network-based mobility management technique.

1 is a configuration diagram illustrating an example of a system to which a conventional network mobility management method is applied, and illustrates a system to which a mobility management method is applied in a centralized mobility management protocol.

As shown in FIG. 1, the network mobility management system includes an anchor router 10 which is a type of anchor for managing mobility of a mobile terminal, an access router 20 and 30 which is a type of access gateway to which a mobile terminal makes a connection request; Mobile terminals 40 and 50.

In this case, the mobile terminal 40, 50 is a device including a wireless transceiver, an antenna, a control device, and includes a mobile communication terminal, PDA, notebook, etc. capable of wireless communication through a wireless transceiver. The mobile terminals 40 and 50 are connected to the access routers 20 and 30 through a wireless connection with the base station in the centralized mobility management protocol to receive a network access service.

The access routers 20 and 30 are devices that support the mobility of the mobile terminals 40 and 50 in place of the mobile terminals 40 and 50, and detect the movement of the mobile terminals 40 and 50. The binding message is transmitted to the anchor router 10. The anchor router 10 processes the binding message and informs the access router 20, 30 of the network prefix information of the mobile terminal when the network registration of the mobile terminal is successfully processed.

The anchor router 10 operates as a kind of home agent for the mobile terminals 40 and 50 in the network. The home agent refers to an agent that binds and stores a CoA address (Care-of address) and an original address (HoA, Home Address) temporarily representing the location of mobile terminals moving in the mobile IP technology. The anchor router 10 receives a binding message from the access routers 20 and 30 with information on which access router the connection path is set, and updates the binding information, and updates the binding information based on the binding information. 50) and establish, maintain and terminate connection paths.

As such, the existing network mobility management scheme is a centralized mobility management scheme for managing mobility of the mobile terminal around the anchor router 10 as shown in FIG. 1, and the mobile terminal moves to a new access router 20, 30. In order to provide continuity of an IP session every time it moves, the anchor router 10 which is a router logically located in the access router 20 and 30 is configured to perform an anchor function. In this centralized mobility management scheme, since all packets are concentrated to the anchor router 10 which is one anchor node, overload and stability problems of data processing are caused.

The present invention has been made to solve the above problems, and provides a handoff procedure of the mobile terminal for IP multicast support in a distributed mobility management network and an agent and a network selection method for receiving multicast data for each anchor agent. Its purpose is to provide a multicast support method for distributed mobility management networks.

Another object of the present invention is to provide a mobility management support method combined with IP multicasting technology for providing a real-time multimedia service in a distributed mobility management structure environment in which the currently connected access router plays an anchor role whenever a mobile terminal moves. It is.

A multicast support method for a distributed mobility management network according to the present invention for achieving the above object is characterized in that the first mobility management anchor agent (MMAA) and the second according to the movement of the mobile terminal receiving the multicast streaming; Information about the mobility management anchor agent that supports the mobility of the mobile terminal when the handoff occurs between the mobility management anchor agent (MMAA) and the agent or network that transmits the multicast channel and data currently received by the mobility management anchor agent. In the method for providing network-based mobility consisting of a receiving mobility management information server, (A) a second sensing the connection of the first mobile terminal as the first mobile terminal moves from the first MMAA to the second MMAA The terminal registration request message including the ID of the connected first mobile terminal by the MMAA. Message delivered to the mobility management information server (MMIS) to request registration; (B) the MMIS requests a binding cache update to a first MMAA to which a first mobile terminal was previously registered, and thereby the first mobile terminal; Updating the cache entry of the first mobile terminal through (C) updating the cache entry of the first mobile terminal by the MMIS and confirming that the first mobile terminal is a multicast receiving node. Transmitting to the second MMAA along with the terminal registration response message according to the terminal registration request message; and (D) checking whether there is a channel connected to the second MMAA currently connected to the first MMAA by the MMIS. Determining step 1, and (E) the MMIS determines whether there is another mobile terminal that the first mobile terminal 110 is receiving in the first MMAA even after handoff. Is a second determination step, and (F) as a result of the first determination step and the second determination step, there is no channel connected to the second MMAA currently connected to the first MMAA, and another mobile terminal receiving the first MMAA. If it is confirmed that there is no, the first delivery step of the MLD Report message synthesized by the second MMAA is delivered to the content provider network, (G) as a result of the first determination step and the second determination step, the first MMAA and the present If it is determined that there is a channel connected to the connected second MMAA, or that there is another mobile terminal receiving at the first MMAA, a tunnel is established between the first MMAA and the currently connected second MMAA to remove the received data. A second forwarding step forwarding to the 2 MMAA, and (H) receiving and registering the current receiving multicast channel and transmission agent or network information transmitted from the second MMAA by the MMIS. Over there makin it has done.

Preferably, after step (H), the terminal registration request message including the ID of the second mobile terminal connected by the second mobility management anchor agent (MMAA) is transmitted to the mobility management information server (MMIS) to request registration. And receiving the terminal registration response message registered from the MMIS by the second MMAA and transmitting an MLD Query message to the registered second mobile terminal to provide multicast channel information that can be received to the connected second mobile terminal. Confirming whether to subscribe to a multicast channel, and receiving multicast channel information desired to be received in an MLD Report message, which is a response to the MLD Query message, by the second MMAA through the second mobile terminal; Checks the current MLD proxy database and sends a comprehensive MLD Report message for that channel between the first MMAA and the second MMAA currently connected. Transmitting to the first MMAA by using the established tunnel to provide a multicast service, and receiving and registering the currently received multicast channel and transmission agent or network information transmitted from the second MMAA by the MMIS. Characterized in that comprises a.

Preferably, after the step (H), if an event occurs in which the first MMAA withdraws all mobile terminals received for the corresponding channel, providing the MLD Report withdrawal message to the MMIS by the first MMAA; Delivering the uplink access multicast agent information changed by the MMIS to the second MMAA through a reception channel registration response message; and including the reception channel registration response message by the second MMAA to the content provider network. Sending a report message to change the multicast data path so that the second MMAA is directly received without passing through the first MMAA, and the multicast data without tunnel between the first MMAA and the second MMAA 140. Received between a second MMAA and a content provider network, and currently received from the second MMAA by the MMIS and And receiving and registering the multicast channel and transmission agent or network information.

As described above, the multicast support method for the distributed mobility management network according to the present invention provides a real-time multimedia transmission method using the IP multicast scheme in the distributed mobility management network, and uses the current multicast transmission node information for each channel. By calculating and transmitting the appropriate transmitting node information, it is possible to provide effective multicast delivery without unnecessary packet duplication, thereby preventing bandwidth waste due to unnecessary data delivery. That is, each mobility management agent provides a method for determining whether to receive a higher transmission agent for receiving multicast data or a multicast network.

1 is a configuration diagram showing an example of a system to which a conventional network mobility management method is applied;
2 is a block diagram showing the structure of a mobility management system for a distributed mobility management network according to an embodiment of the present invention.
3 is a flowchart illustrating an initial access procedure when a mobile terminal accesses a distributed mobility management network according to the present invention.
4 is a flowchart illustrating a handoff procedure of a mobile terminal according to the present invention.
5 is a flowchart illustrating a multicast service providing procedure when a new mobile terminal is connected with a handoff procedure of a mobile terminal according to the present invention.
6 is a flowchart illustrating a procedure of changing a multicast data path according to a binding update procedure of a mobile terminal according to the present invention.

Other objects, features and advantages of the present invention will become apparent from the detailed description of the embodiments with reference to the accompanying drawings.

A preferred embodiment of a multicast support method for a distributed mobility management network according to the present invention will be described with reference to the accompanying drawings. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. It is provided to let you know. Therefore, the embodiments described in the present specification and the configurations shown in the drawings are merely the most preferred embodiments of the present invention and are not intended to represent all of the technical ideas of the present invention. Therefore, various equivalents It should be understood that water and variations may be present.

2 is a block diagram showing the structure of a mobility management system for a distributed mobility management network according to an embodiment of the present invention.

As shown in FIG. 2, the mobility management system includes a mobile terminal 110 and 120, a mobility management anchor agent 130, and a 140, a mobility management information server 150, and a plurality of distributed mobility management networks 100. Represents an environment comprised of a multicast routable content provider network 200 that includes content sources and provides content.

The mobile terminals 110 and 120 are devices including a wireless transceiver, an antenna, and a control device, and include a mobile communication terminal, a PDA, a notebook, and the like, which can perform wireless communication through the wireless transceiver. The mobile terminals 110 and 120 access the mobility management anchor agent 130 and 140 through a wireless connection with a base station in a distributed mobility management network to receive a network access service. The mobile terminal 110, 120 receives the advertisement message of the mobility management anchor agent 130, 140 and sets its IP address.

The mobility management anchor agent 130, 140 is a device that supports the mobility of the mobile terminal 110, 120 in place of the mobile terminal 110, 120, when the mobile terminal 110, 120 moves The mobility management anchor agent 130 and 140 currently connected to each other play an anchor role. That is, by transmitting an advertisement message to the mobile terminal 110, 120, to detect the movement of the mobile terminal 110, 120, and includes information that the connection path of the mobile terminal 110, 120 is set The binding message is generated and updated, and the connection path of the mobile terminal 110 or 120 is set, maintained, and terminated based on the binding information.

The mobility management information server 150 receives and registers and updates information on an agent or a network that transmits a multicast channel and data currently being received by the mobility management anchor agent 130 and 140. The mobility management information server 150 checks whether the mobility management anchor agent 130 or 140 currently receives the corresponding channel, and controls the content providing network 200 to change the multicast channel reception.

The mobility management method for the distributed mobility management network according to the present invention configured as described above will be described in detail with reference to the accompanying drawings. The same reference numerals as those in Fig. 2 designate the same members performing the same function.

3 is a flowchart illustrating an initial access procedure when a mobile terminal according to the present invention accesses a distributed mobility management network. Referring to FIG. 3, FIG. 3 illustrates a mobile terminal for receiving IP multicast-based streaming in a distributed mobility management network. The initial access procedure of is as follows.

First, when the first mobile terminal 110 accesses the first mobility management anchor agent (MMAA) 130, the first MMAA 130 loads the ID of the first mobile terminal 110 in the terminal registration request message. It transmits to the management information server (MMIS) 150, and receives the terminal registration response message accordingly. For reference, it is assumed that the first MMAA 130 and the second MMAA 140 have the MLD proxy function specified in the IETF RFC 4605.

Accordingly, the first MMAA 130 transmits an MLD Query message (advertisement message) to the first mobile terminal 110 registered in the MMIS 150, and thus, the first mobile terminal 110 connected to the first MMAA 130. By providing multicast channel information that can be received by), it is confirmed whether to subscribe to the multicast channel.

Then, the first mobile terminal 110 transmits the multicast channel information desired to be received to the first MMAA 130 through an MLD Report message which is a response according to the MLD Query message, and the first MMAA 130. Transmits the aggregated MLD Report message to the content provider network 200.

Subsequently, the first MMAA 130 transmits a multicast channel and a transmission agent or network information currently received to the MMIS 150, and the MMIS 150 transmits a multicast channel transmitted from the first MMAA 130. Registers the sending agent or network information and performs update by comparing with the registered contents.

4 is a flowchart illustrating a handoff procedure of a mobile terminal according to a preferred embodiment of the present invention, in which a first mobile terminal 110 receiving multicast streaming in a distributed mobility management network with reference to FIG. A procedure of handoff from the MMAA 130 to the second MMAA 140 will be described below.

First, as the first mobile terminal 110 moves from the first MMAA 130 to the second MMAA 140, the second MMAA 140 that detects the connection of the first mobile terminal 110 is a first mobile terminal ( The ID of 110 is included in the terminal registration request message, and the terminal registration request message is sent to the mobility management information server (MMIS) 150.

The MMIS 150 then requests the first MMAA 130 to which the first mobile terminal 110 is registered to update the binding cache, thereby updating the cache entry of the first mobile terminal 110. Through this process, the MMIS 150 confirms that the first mobile terminal 110 is a multicast receiving node, and loads upper access agent information for multicast data reception in a terminal registration response message to the second MMAA 140. Delivered.

Meanwhile, in FIG. 3, when the second MMAA 140 currently connected to the first MMAA 130 does not have a mobile terminal receiving a channel “G”, the second MMAA 140 may synthesize the MLD Report. The message is delivered to the content provider network 200.

However, if the second MMAA 140 already has a mobile terminal receiving for the channel currently connected with the first MMAA 130, or the first MMAA 130 even after the first mobile terminal 110 is handed off. If there is a mobile terminal receiving the MMIS 150 to prevent unnecessary redundant transmission to the content provider network 200 informs the agent address to receive the multicast data. Therefore, if there is existing multicast data received from the content provider network 200 to form a tunnel between the mobility management anchor agent 130, 140 to forward the received data. The second MMAA 140 registers the MMIS 150 with information on the agent or network that transmits the currently received multicast channel and data.

FIG. 5 is a flowchart illustrating a multicast service providing procedure when a new mobile terminal is connected with a handoff procedure of a mobile terminal according to the present invention. Referring to FIG. 5, a first mobile terminal 110 in a distributed mobility management network is described. The IP multicast support procedure when the new second mobile terminal 160 is connected with this handoff procedure will be described as follows.

First, it is assumed that there are mobile terminals that receive the multicast channel “G” received by the first mobile terminal 110 in the first MMAA 130. Accordingly, the first mobile terminal 110 receives the second MMAA ( When handing off to 140 and receiving multicast data, a MLD Report message synthesized to the first MMAA 130 and not to the content provider network 200 is determined by the MMIS 150 policy decision. Forming a tunnel between the mobility management anchor agent 130, 140 by transmitting the, and receives the multicast data using the formed tunnel.

Then, when the new second mobile terminal 120 accesses the second MMAA 140, the second MMAA 140 performs a terminal registration request to the MMIS 150 to receive a terminal registration response message. In addition, since the second MMAA 140 receives a multicast channel request like the first mobile terminal 110, the second MMAA 140 checks the current MLD proxy database and sends a comprehensive MLD Report message for the corresponding channel to the first MMAA 130. send. The multicast data is received from the first MMAA 130 using a tunnel.

In addition, the second MMAA 140 receiving the MLD Report message registers the received channel information and the agent or network information for transmitting the multicast data for the corresponding channel to the MMIS 150.

FIG. 6 is a flowchart illustrating a procedure for changing a multicast data path according to a binding update procedure of a mobile terminal according to the present invention. Referring to FIG. 6, a multicast data path switching method using a terminal binding update procedure will be described below. same.

First, when the second mobile terminal 120 receives the MLD Query message from the second MMAA 140 performing the MLD proxy function, the second mobile terminal 120 responds with an MLD Report message. In addition, the second MMAA 140 updates the MMIS 150 from time to time with the multicast channel currently received and the agent or network information transmitted for the channel.

In addition, the first MMAA 130 provides an MLD Report Withdrawal message to the MMIS 150 when an event occurs in which all mobile terminals receiving the corresponding channel are withdrawn. Accordingly, the MMIS 150 checks whether the corresponding channel is currently received by the first MMAA 130, and then confirms that the first MMAA 130 no longer receives the corresponding channel.

Thereafter, the MMIS 150 transmits the changed upper access multicast agent information to the second MMAA 140 through the reception channel registration response message, and the second MMAA 140 registers the reception channel with the content provider network 200. The aggregated MLD Report message including the response message is transmitted to allow the second MMAA 140 to directly receive the multicast data without passing through the first MMAA 130.

Accordingly, the second MMAA 140 receives the multicast data between the second MMAA 140 and the content provider network 200 without the tunnel between the first MMAA 130. This reduces the propagation delay caused by unnecessary tunneling overhead and data bypass.

The second MMAA 140 registers with the MMIS 150 the channel information that is received for each channel and the agent or network information that transmits the multicast data for the corresponding channel.

Although the technical spirit of the present invention described above has been described in detail in a preferred embodiment, it should be noted that the above-described embodiment is for the purpose of description and not of limitation. In addition, those skilled in the art will understand that various embodiments are possible within the scope of the technical idea of the present invention. Accordingly, the true scope of the present invention should be determined by the technical idea of the appended claims.

Claims (3)

A mobility management anchor agent supporting mobility of the mobile terminal when a handoff occurs between the first mobility management anchor agent (MMAA) and the second mobility management anchor agent (MMAA) according to the movement of the mobile terminal receiving the multicast streaming; A method of providing a network-based multicast support method comprising a mobility management information server receiving information on a multicast channel currently being received by a mobility management anchor agent and an agent transmitting data or a network,
(A) As the first mobile terminal moves from the first MMAA to the second MMAA, the terminal registration request message including the ID of the connected first mobile terminal is generated by the second MMAA that detects the connection of the first mobile terminal. Requesting registration by forwarding to a mobility management information server (MMIS);
(B) requesting, by the MMIS, a binding cache update from a first MMAA to which a first mobile terminal is registered, updating a cache entry of the first mobile terminal;
(C) confirming that the first mobile terminal is a multicast receiving node by updating the cache entry of the first mobile terminal by the MMIS, and obtaining upper access agent information for receiving multicast data according to the terminal registration request message; Passing the registration response message to the second MMAA;
(D) a first determination step of checking whether there is a channel connected to a second MMAA currently connected to the first MMAA by the MMIS;
(E) a second determination step of determining whether there is another mobile terminal which the first mobile terminal 110 receives in the first MMAA even after the handoff by the MMIS;
(F) If it is determined that there is no channel connected to the second MMAA currently connected to the first MMAA and there is no other mobile terminal receiving the first MMAA, as a result of the first and second determination steps, A first delivery step of delivering the MLD Report message synthesized by the second MMAA to the content provider network;
(G) If it is determined that there is a channel connected to the second MMAA currently connected to the first MMAA or another mobile terminal receiving the first MMAA, as a result of the first and second determination steps, A second forwarding step of forming a tunnel between the first MMAA and the currently connected second MMAA to forward the received data to the second MMAA;
(H) receiving and registering the current receiving multicast channel and transmission agent or network information transmitted from the second MMAA by the MMIS, and multicasting for distributed mobility management network. How to apply. According to claim 1, After the step (H),
Transmitting a terminal registration request message including an ID of the second mobile terminal connected by the second mobility management anchor agent (MMAA) to the mobility management information server (MMIS) to request registration;
Receiving the terminal registration response message registered from the MMIS by the second MMAA, and transmits the MLD Query message to the registered second mobile terminal to provide multicast channel information that can be received to the connected second mobile terminal to multicast Check whether you've joined the channel,
The second MMAA receives the multicast channel information desired to be included in the MLD Report message, which is a response to the MLD Query message, through the second mobile terminal, and checks the current MLD proxy database to synthesize the corresponding channel. Providing the multicast service by transmitting the received MLD Report message to the first MMAA using a tunnel formed between the first MMAA and the second MMAA currently connected;
Receiving and registering the currently receiving multicast channel and a transmission agent or network information transmitted from the second MMAA by the MMIS. According to claim 1, After the step (H),
Providing an MLD Report withdrawal message to the MMIS by the first MMAA when an event occurs in which the first MMAA withdraws all mobile terminals receiving the corresponding channel;
Transmitting, to the second MMAA, the upper access multicast agent information changed by the MMIS through a reception channel registration response message;
Sending the aggregated MLD Report message including the receiving channel registration response message to the content provider network by the second MMAA to send multicast data directly so that the second MMAA is directly received without passing through the first MMAA. To make changes,
Receiving multicast data between the second MMAA and the content provider network without a tunnel between the first MMAA and the second MMAA 140;
Receiving and registering the currently receiving multicast channel and a transmission agent or network information transmitted from the second MMAA by the MMIS.

Images