WO2007121675A1 - Procédé, dispositif et système de mise en oeuvre de découverte de capacité de mih - Google Patents

Procédé, dispositif et système de mise en oeuvre de découverte de capacité de mih Download PDF

Info

Publication number
WO2007121675A1
WO2007121675A1 PCT/CN2007/001327 CN2007001327W WO2007121675A1 WO 2007121675 A1 WO2007121675 A1 WO 2007121675A1 CN 2007001327 W CN2007001327 W CN 2007001327W WO 2007121675 A1 WO2007121675 A1 WO 2007121675A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
request
mih
capability
type
Prior art date
Application number
PCT/CN2007/001327
Other languages
English (en)
Chinese (zh)
Inventor
Yan Peng
Junxiang Guo
Jiang Li
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2007121675A1 publication Critical patent/WO2007121675A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/005—Control or signalling for completing the hand-off involving radio access media independent information, e.g. MIH [Media independent Hand-off]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method, device, and system for implementing media independent handover (MIH) capability discovery.
  • MIH media independent handover
  • heterodyne networks There are many heterogeneous networks, such as IEEE ( Institute of Electrical and Electronic Engineers) 802.3, IEEE 802.11 and IEEE 802.16, and 3GPP (3rd Generation Partnership Project).
  • IEEE Institute of Electrical and Electronic Engineers
  • 3GPP 3rd Generation Partnership Project
  • a terminal that supports multiple access technologies, ie, supports multiple heterogeneous networks has a problem that must be addressed: How the terminal seamlessly switches and roams among the heterogeneous networks it supports.
  • MIP Mobile IP Protocol
  • the existing Mobile IP Protocol (MIP) technology can be considered to have achieved Layer 3 mobility, so that the terminal can guarantee the upper layer after the network address changes, that is, after the heterogeneous network handover occurs.
  • Business continuity However, the use of the MIP technology still has a period in which the terminal and the network's underlying link are completely disconnected, and thus affects the QoS (Quality of Service) performance of the service, such as QoS delay and jitter.
  • QoS Quality of Service
  • IEEE 802.21 In view of the above problems, the current purpose of IEEE 802.21 is to help implement network switching at the link layer, and to minimize the QoS performance of the service during the handover process to improve the user's mobile experience.
  • IEEE 802.21 introduces a new protocol function layer in the existing mobility management protocol stack, namely media independent switching function (MIHF, MIH Function).
  • MIHF media independent switching function
  • MIHF It mainly provides some key services, namely MIH, Media Independent Event Service, MIH, Media Independent Command Service and MIH, Media Independent Information. Service) to help the terminal to switch.
  • MIHF is logically defined as a thin layer in the mobility management protocol stack of the terminal and network, acting as a helper and booster in the handover decision.
  • MIHF provides the necessary information to the upper layer that needs to make handover decisions and how to effectively make handover decisions.
  • the upper layer makes handover decisions and link selection based on MIHF input and context, so that seamless handover can be achieved.
  • the location of MIHF and its key services in the protocol stack is shown in Figure 1.
  • the MIH protocol used for MIHF layer communication between different network elements includes MIH capability discovery, MIH remote registration, and MIH message interaction.
  • MIH capability discovery process each network element in the communication system can determine which other network element can support MIHF and its support level. The degree of support is usually indicated by the MIH capability list, and the MIH capability discovery process includes capability discovery handshake and capability announcement.
  • MIH Remote Registration Protocol MIHFs in different network elements can register with each other to accept media-independent switching messages and remote events.
  • the MIH message interaction protocol specifies the format of the packet, the message format, and the message.
  • the reason why the MIH capability discovery process is required is that if the network elements in the communication system do not know each other's MIH capabilities and other information, the communication information will be confused when interpreting the interaction information, thereby affecting the interoperability of the communication system.
  • the network element in the communication system includes a terminal and a network entity such as a Point of Attachment (PoA), an Access Router (A, Access Router), and the network elements in the communication system usually come from different vendors. It is difficult for each other to know in advance whether they can support MIHF and their respective support for MIHF. Therefore, in order to realize the handover of a heterogeneous network, the network element in the communication system first needs to find out which network element can support MIHF and the degree of support to MIHF through the MIH capability discovery process.
  • PoA Point of Attachment
  • A Access Router
  • a network element in a communication system broadcasts its own MIH capability through a media medium, for example, can broadcast its own MIH capability through a beacon (beacon) in 802.11 and a DCD (downlink channel descriptor) in 802.16. .
  • a beacon beacon
  • DCD downlink channel descriptor
  • Another implementation is to define request and response messages for MH capability discovery, and corresponding message interaction flows. The following describes the message and interaction process of the solution.
  • MIH_Capability_ Discover request a capability discovery request message
  • MIH-capability-recovery response MIHF-capable network elements can use these two messages to complete MIH capability discovery.
  • For the network element that initiates the request if you know the address of other network elements that you want to discover, you can fill in the address of other network elements in the destination address field of the capability discovery request message and perform unicast; if you don't know, You can fill in the address of the source address field of the capability discovery request message and then broadcast it.
  • the network element that received the request message returns a response message.
  • the network element may also actively send the MIH-Capability-Review response message in a broadcast manner, and notify other network elements of the MIH capability of the local network element.
  • the above MIH-Capability-Discover request message has the same structure as the MIH-Capability-Execution response message, as shown in Table 1. Both of these messages include four fields, where SupportedEventList represents a list of supported events, SupportedCommandList represents a list of supported commands, SupportedTransportList represents the manner in which supported MIH messages are transmitted, and SupportedlSQueryTypeList represents a supported type of information service query.
  • the terminal discovers which network element in the communication system supports MIHF by using the MIH-Capability-Expo request message, and the timing of the message flow is as shown in FIG. 2.
  • the terminal sends an MIH-Capability-Experiment request message to the PoA 1 directly connected to itself.
  • the PoA 1 is the PoS (Point of Service) of the service network, and the PoS is the MN in the network.
  • Mobile Node, mobile node Provides the network element of the MIH service.
  • PoA 1 directly forwards the message to other surrounding network PoAs, including PoA 2, PoA 3, and AR.
  • the PoS may be in the AR, and the AR in FIG. 2 is The AR of the PoS is set.
  • PoA 3 is not a PoS and does not have MIH capability, so it will not reply.
  • PoA 2 and AR are PoSs with MIH capability, thus returning MIH—Capability—Discover response message.
  • PoA 1 forwards the received MIH-Capability-Experience response message to the terminal.
  • Figure 2 shows only one signal flow that may occur in accordance with the prior art.
  • a network element may receive multiple processing after receiving the MIH-Capability-Exam request message.
  • One is to broadcast to other network elements that it knows, as shown by PoA 1 in Figure 2, after receiving the MIH-Capability-Experience request message sent by the terminal, PoAl sends PoA 2, PoA 3 and AR
  • the message is forwarded and the received MIH_Capability-Experience response message is forwarded to the terminal.
  • the other is to return the MIH_Capability-Discover response message directly to the sender.
  • PoA 2 and AR in Figure 2 directly return the response message.
  • the received request message may be forwarded to other network elements by broadcast, and the related information of the MIHF may be returned by the response message.
  • the terminal After the terminal wants to receive the request message, the terminal broadcasts the message to obtain the MIH capability of other network elements in the geographical location of the terminal, but the service PoA may only return its own MIH capability, and the terminal cannot obtain the terminal. Its required MIH capability information. For example, the terminal only needs the non-serving PoA to return its own MIH capability, and the non-serving PoA may broadcast the request message to other network elements, which may cause a network storm.
  • the embodiments of the present invention provide a method and apparatus for implementing MIH capability discovery in a heterogeneous network handover, so that the network element can obtain desired MIH capability information while reducing the possibility of a broadcast storm.
  • a method for implementing media-independent handover capability discovery includes: receiving a capability discovery request of a peer network element carrying a request type, where the request type indicates a network element range in which the peer network element needs to discover the MIH capability ;
  • the MIH capability information of the network element corresponding to the request type is obtained and sent to the peer network element.
  • Another method for implementing MIH capability discovery includes: Sending a capability discovery request carrying a request type to the peer network element, where the request type indicates a network element range in which the network element needs to discover the MIH capability;
  • the MIH capability information of the network element corresponding to the request type is received from the peer network element.
  • An embodiment of the present invention provides an apparatus for implementing MIH capability discovery, including:
  • a request receiving unit configured to receive a capability discovery request of the peer network element, where the capability discovery request includes a request type, and indicates a network element range in which the peer network element needs to discover the MIH capability;
  • the MIH capability information unit is configured to obtain MIH capability information of the corresponding network element according to the request type
  • the request response unit is configured to send the MIH capability information obtained by the MIH capability information unit to the network element.
  • An embodiment of the present invention provides another apparatus for implementing MIH capability discovery, including:
  • a request sending unit configured to send a capability discovery request to the peer network element; the capability sending request carrying the request type, indicating that the network element needs to discover the network element range of the MIH capability;
  • the response receiving unit is configured to receive MIH capability information of the network element corresponding to the request type from the peer network element.
  • the embodiment of the invention further provides a system for implementing MIH capability discovery, including:
  • a first network element configured to send a capability discovery request carrying a request type to the second network element, where the request type indicates a network element range in which the network element needs to discover the MIH capability, and receives the request type from the second network element.
  • MIH capability information of the corresponding network element
  • the second network element is configured to receive the capability discovery request sent by the first network element, obtain MIH capability information of the network element corresponding to the request type, and send the MIH capability information to the first network element.
  • the embodiment of the present invention notifies the receiver network element of the network element range in which the network element of the capability discovery request is required to obtain the MIH capability information by carrying the request type in the capability discovery request, so that the receiver network element performing the capability discovery request can be configured according to
  • the request type performs message processing, so that on one hand, the capability discovery request message of the initiator due to the receiver not broadcasting the terminal such as the service PoA can be solved, so that the information returned to the initiator is insufficient, that is, insufficient
  • the information is used by the initiator for the selection of the handover policy; on the other hand, it can also avoid the potential threat of network storm caused by the inappropriate broadcast and forwarding of the capability discovery request message by the network element such as other non-service PoA.
  • FIG. 1 is a schematic diagram of a positional relationship of a MIHF and its key services in a protocol stack in the prior art
  • FIG. 2 is a diagram showing an example of a message flow sequence of a capability discovery request in the prior art
  • FIG. 3 is a flowchart of an embodiment of a capability discovery method according to the present invention.
  • FIG. 5 is a message flow sequence diagram of an example 2 of the capability discovery method according to the present invention.
  • Example 3 is a message flow timing diagram of Example 3 of the capability discovery method according to the present invention.
  • FIG. 7 is a schematic structural diagram of an embodiment of a system for implementing MIH capability discovery according to the present invention. detailed description
  • the sender network element of the capability discovery request message carries the request type in the message, which is used to notify the receiver of the message, which MIH capability information of the network element is desired, or to notify the receiver of what needs to be performed.
  • the MIH capability discovery of the network element the receiver obtains the MIH capability information of the corresponding network element according to the request type and returns it to the sender.
  • a request type field may be added to the currently existing MIH-Capability-Examine request message, and the field may be configured with multiple identifiers according to requirements, and each identifier corresponds to a request type.
  • Each request type represents a message processing scheme of the recipient.
  • One possible implementation is to add an optional field named ActionCode to Table 1 above.
  • the message format after adding this field can be as shown in Table 2.
  • the specific definition of this field can be as shown in Table 3.
  • the capability discovery request message is a unicast message, and the sender only needs to obtain the MIH capability information of the receiver; when the ActionCode is 1, the sender hopes.
  • the receiver broadcasts the message to other network entities to obtain MIH capability information of other network entities.
  • FIG. 3 corresponds to the following steps:
  • Step 301 The network element (ie, the sender) that initiates the capability discovery request sets the corresponding identifier of the current required request type in the request type field when sending the capability discovery request message to other network elements.
  • Step 302 The network element (ie, the receiving MIHF network element) that receives the capability discovery request message and has MIHF performs a corresponding MIH capability discovery processing procedure according to the identifier in the request type field of the message.
  • Step 303 The network element that initiates the capability discovery request obtains the MIH capability information of the related network element according to the processing result in step 302.
  • the network element in the communication system can send the MIH_Capability_Discovei' request with the ActionCode field 0 when the receiver that only needs the capability discovery request message returns its own MIH capability information.
  • the message, the network element that received the request message directly returns its MIH capability information.
  • Figure 4 shows the message flow timing diagram of Example 1, which corresponds to the following steps:
  • Step 401 The network element 1 sends an MIH_Capability_Discover request message to the network element 2, and only needs to obtain the MIH capability information of the other party, and the ActionCode field in the message is 0.
  • the MIH capability information usually includes information on whether or not to support MIHF, and information on the degree of support of the MIHF.
  • Step 402 The network element 2 finds that the ActionCode field in the MIH-Capability-Discovering Request message is 0, and directly returns an MIH-Capability-Reference response message, and the message carries its own MIH capability information.
  • the message flow timing shown in Figure 4 is typically used for the MIHF capability discovery process between two peer network elements.
  • the terminal and service PoA only need to know the MIH capability information of the peer.
  • the PoA in the two heterogeneous networks only need to know the MIH capability of the other party.
  • the service network PoA needs to obtain the MIH capability information of other network PoAs.
  • the process shown in FIG. 5 may be used, and the terminal initiates the capability discovery request.
  • PoA 1, PoA 2, and PoA 3 are PoS, PoA 4 does not have PoS function.
  • the process corresponds to the following steps:
  • Step 501 The terminal sends an MIH_Capability_Discover request message to the service PoA, that is, PoAl.
  • the ActionCode field in the message is set to 1.
  • Step 502 After determining that the ActionCode field in the received MIH_Capability_Examine Request message is 1, the PoAl broadcasts the message to a heterogeneous network around it, and sets the ActionCode field in the message to 0.
  • Step 503 The PoA with the MIHF in the surrounding heterogeneous network, that is, the PoA2 and the PoA3, after receiving the MIH_Capability_Experiment request message, determine that the ActionCode field in the message is 0, and directly return the MIH_Capability to the PoAl. Discover response message, and carry its own MIH capability information in the message. Since PoA4 does not have MIHF, it cannot respond, so it is not processed.
  • Step 504 The PoAl forwards the received MIH_Capability-Discover response message, including the MIH_Capability-Discover response message from the PoA2 and the PoA3, to the terminal.
  • the terminal can obtain the MIH capability information of the PoA in all other heterogeneous networks in the location area.
  • the terminal initiates a capability discovery request.
  • the terminal needs the service PoA to forward the MIH-Capability-Discover request message sent by the terminal. Therefore, the ActionCode field of the MIH-Capability-Exam request message is set to 1. If the PoA initiates the capability discovery request in the communication system, the message may not be forwarded by the receiver, so the ActionCode field of the MIH-Capability-Exam request message may be set to 0, where the network receiving the request message is received.
  • the element can be another PoA or a terminal.
  • multiple identities can be set for the added ActionCode to identify different request types and recipient processing schemes.
  • other identifiers may be set by the manager of the communication system according to specific operational needs. For example, if the sender needs to obtain the MIH capability information of the network element in all heterogeneous networks, an identifier may be added to the ActionCode, for example, the identifier 2 is added to indicate that the sender wants the receiver to return its MIH capability information, and the MIH_Capability—The Discover request message is broadcast.
  • the network element that receives the message After receiving the MIH_Capability_Discover request message with the ActionCode field of 2, the network element that receives the message returns an MIH__Capability_Discover response message carrying its own MIH capability information, and forwards the request message to other network elements, and The MIH-Capability-Review response messages returned by these network elements are forwarded to the sender.
  • the terminal initiates the request as an example.
  • 6 is a message flow timing diagram of Example 3 of the method embodiment of the present invention.
  • ⁇ 1, PoA 2, and PoA 3 are PoS, and PoA 4 does not have a PoS function.
  • PoAl sends its MIH capability information to the terminal through the MIH-Capability-Exposure response message.
  • identifiers may be set for the ActionCode as needed to indicate other request types and corresponding receiver processing schemes, and the MIH_Capability_Experiment request message is received.
  • the network element performs corresponding processing according to the identifier.
  • the action code field is set in the MIH-Capability-Execution request message. To ensure that the processing of the message is not caused by each network element, the following solution can be adopted:
  • each network element After receiving the MIH_Capability-Exam request message, each network element determines whether the ActionCode field in the message has a request type identifier. If yes and identifiable, the corresponding processing is performed according to the identifier; if not, or not, the identifier is unrecognizable. Then, according to the role of the network element and the sender network element, whether to forward the message is determined.
  • the processing of the message by the network element of the role may be determined by the administrator of the communication system. For example, if the network element is a service PoA, and the received request message is a capability discovery request message sent by the terminal, then The network element sends the request message to other surrounding network elements by broadcast. If it is not the former case, for example, the service PoA network element receives the request message sent by other network elements, and does not perform forwarding processing, but directly returns its MIH capability information to the sender through the response message.
  • the storage medium shield may be a read only memory, a random access memory, a magnetic disk, an optical disk, or the like.
  • FIG. 7 is a schematic structural diagram of a system for implementing MIH capability discovery according to the present invention.
  • the system includes a network element 700 and a network element 800.
  • the network element 700 is a sender network element of a capability discovery request, and the network element 800 The recipient network element for the capability discovery request.
  • the network element 700 includes a request transmitting unit 710 and a response receiving unit 720.
  • the network element 800 includes a request receiving unit 810, a request response unit 830, and an MIH information capability unit 820.
  • the request sending unit 710 of the network element 700 sends a capability discovery request to the network element 800.
  • the capability discovery request includes a request type, and indicates a network element range in which the network element 700 needs to discover the MIH capability, that is, the MIH of the network element that the network element 700 wants to obtain. Capability information.
  • the request receiving unit 810 of the network element 800 receives the capability discovery request sent by the network element 700, and outputs the request type in the request to the MIH capability information unit 820.
  • the MIH capability information unit 820 obtains the MIH capability information of the corresponding network element according to the request type in the capability discovery request sent by the network element 700, and outputs the acquired MIH capability information to the request response unit 830.
  • the request type may be the first type, indicating that the network element 700 wishes to obtain the network element 800.
  • the MIH capability information may be a second type, indicating that the network element 700 wishes to obtain the MIH capability information of the other network element, and may be the third type, indicating that the network element 700 wishes to obtain the MIH capability information of the network element 800 and other network elements;
  • the network element is a network element other than the network element that sends and receives the capability discovery request.
  • the MIH capability information unit 820 may include the local network element information sub-unit 821 and other network element information sub-units 822.
  • the local network element information sub-unit 821 acquires the MIH capability of the network element 800.
  • the information is output to the request response unit 830; when the request type is the second type and the third type, the other network element information sub-unit 822 acquires the MIH capability information of the other network elements and outputs the same to the request response unit 830.
  • the request response unit 830 of the network element 800 transmits the MIH capability information of the local network element and/or other network elements output by the MIH capability information unit 820 to the response receiving unit of the network element 700.
  • the network element 700 which is the sender of the capability request, may be a terminal or a PoS
  • the network element 800 which is the recipient of the capability discovery request, is generally PoS.
  • the PoS network element in the communication system can be used not only as the receiver network element of the capability discovery request, but also as the sender network element.
  • the PoS network element in the communication system can include each of the network element 700 and the network element 800.
  • the sender of the capability discovery request carries the request type in the capability discovery request, and the network element range of the network element that the sender network element of the capability discovery request wishes to obtain the MIH capability information is notified to the receiver network element, so that the receiver network element can
  • the message processing according to the request type can solve the capability discovery request message of the initiator due to the receiver not broadcasting the terminal such as the service PoA, so that the information returned to the initiator is insufficient;
  • a potential threat of network storms is caused by improperly broadcasting and forwarding of capability discovery request messages by network elements such as other non-serving PoAs.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé de mise en oeuvre de découverte de capacité de transfert intercellulaire indépendant du support (MIH). Le procédé consiste: à recevoir la demande de découverte de capacité de MIH qui est transmise par un élément réseau. La demande de découverte de capacité de MIH comprend un type de demande qui représente l'objet de l'élément réseau signifiant que l'émetteur souhaite découvrir la capacité de MIH; à obtenir les informations de capacité de MIH qui correspondent au type de demande et à les transmettre à l'élément réseau. Alors, le problème représenté par le fait que l'élément réseau de l'état antérieur de la technique ne peut pas déterminer le mode de transmission du message de découverte de capacité selon les besoins est résolu, et l'élément réseau peut notifier à un autre élément réseau comment traiter le message au moyen du message de demande de découverte de capacité.
PCT/CN2007/001327 2006-04-21 2007-04-23 Procédé, dispositif et système de mise en oeuvre de découverte de capacité de mih WO2007121675A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610077644.6 2006-04-21
CNA2006100776446A CN101052036A (zh) 2006-04-21 2006-04-21 在异质网络切换中实现媒体无关的切换能力发现的方法

Publications (1)

Publication Number Publication Date
WO2007121675A1 true WO2007121675A1 (fr) 2007-11-01

Family

ID=38624556

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/001327 WO2007121675A1 (fr) 2006-04-21 2007-04-23 Procédé, dispositif et système de mise en oeuvre de découverte de capacité de mih

Country Status (2)

Country Link
CN (1) CN101052036A (fr)
WO (1) WO2007121675A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005062580A1 (fr) * 2003-12-23 2005-07-07 Telefonaktiebolaget Lm Ericsson (Publ) Procede d'exploration des capacites d'un routeur d'acces candidat
US20050163080A1 (en) * 2003-10-18 2005-07-28 Samsung Electronics Co., Ltd. System and method for providing handover of a mobile IP terminal in a wireless network
CN1650663A (zh) * 2002-04-26 2005-08-03 诺基亚公司 与移动通信系统中ip会话的重新定位相关的优化信息传送
CN1711781A (zh) * 2002-11-12 2005-12-21 诺基亚公司 用于发现网络接口能力的系统和方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1650663A (zh) * 2002-04-26 2005-08-03 诺基亚公司 与移动通信系统中ip会话的重新定位相关的优化信息传送
CN1711781A (zh) * 2002-11-12 2005-12-21 诺基亚公司 用于发现网络接口能力的系统和方法
US20050163080A1 (en) * 2003-10-18 2005-07-28 Samsung Electronics Co., Ltd. System and method for providing handover of a mobile IP terminal in a wireless network
WO2005062580A1 (fr) * 2003-12-23 2005-07-07 Telefonaktiebolaget Lm Ericsson (Publ) Procede d'exploration des capacites d'un routeur d'acces candidat

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"MIH Capability discovery Amendent", IEEE 802.21 MEDIA INDEPENDENT HANDOVER, May 2006 (2006-05-01) *
"Proposal for Handover Procedures of 802.21", IEEE 802.21 MEDIA INDEPENDENT HANDOVER, March 2006 (2006-03-01) *

Also Published As

Publication number Publication date
CN101052036A (zh) 2007-10-10

Similar Documents

Publication Publication Date Title
US7272122B2 (en) Relocation of application-specific functionality during seamless network layer-level handoffs
Siddiqui et al. Mobility management across hybrid wireless networks: Trends and challenges
RU2459382C2 (ru) Механизм поддержки эстафетной передачи обслуживания гетерогенной сети с использованием функций независимой от среды передачи эстафетной передачи обслуживания (mih)
KR101221610B1 (ko) 무선 통신 시스템에서 링크 ｉｄ 프리픽스와 함께 고속이동성 ｉｐ를 지원하기 위한 방법 및 장치
US20080304454A1 (en) Heterogeneous network and method for handover between heterogeneous networks
US8711701B2 (en) Method and system and policy server for guaranteeing data not to be interrupted
US20240022541A1 (en) Method and device for edge application server discovery
JP2021504991A (ja) アプリケーションのためのトラフィックをハンドリングするための方法および機能
WO2020200242A1 (fr) Procédé de traitement de session, dispositif de communication et système de communication
JP2005500763A (ja) 無線データ・ネットワーク内でソフト・ハンドオフを実行するためのシステム並びに方法
IL186480A (en) Wireless system for communicating heterogeneous network information for performing handover to a network
EP1643723A2 (fr) Méthodes et systèmes de gestion de trafic de communication
TW202021411A (zh) 無效協定資料單元會話之處理方法及其使用者設備
CN113767672A (zh) 用于在插入中间会话管理功能之后管理无线通信的移动通信核心网络装置及方法
EP2673970A1 (fr) Systèmes et procédés pour un comportement étendu / enrichi d'interface logique
WO2021051420A1 (fr) Procédé et appareil de détermination d'un enregistrement de cache dns
AU2007297676B2 (en) Switching multiple link layer resources for media independent handover
US20110075632A1 (en) Heterogeneous communication system and method for circuit switched handover
WO2011143997A1 (fr) Procédé et dispositif de routage
TW201019754A (en) Method and apparatus for fast break-before-make media independent handover
WO2014059647A1 (fr) Procédé, appareil et système de traitement de service du domaine des données
WO2009043284A1 (fr) Procédé, entité de réseau et terminal pour le transfert entre réseaux sans fil hétérogènes
WO2007121675A1 (fr) Procédé, dispositif et système de mise en oeuvre de découverte de capacité de mih
WO2008106877A1 (fr) Procédé et dispositif de manipulation de liaison lors d'un transfert réseau hétérogène
WO2013000289A1 (fr) Procédé de gestion de mobilité pour un tunnel direct, élément de réseau et système

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07720900

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07720900

Country of ref document: EP

Kind code of ref document: A1