WO2010083739A1 - Ip会话存活监控方法及系统、家庭网关和网络设备 - Google Patents

Ip会话存活监控方法及系统、家庭网关和网络设备 Download PDF

Info

Publication number
WO2010083739A1
WO2010083739A1 PCT/CN2010/070161 CN2010070161W WO2010083739A1 WO 2010083739 A1 WO2010083739 A1 WO 2010083739A1 CN 2010070161 W CN2010070161 W CN 2010070161W WO 2010083739 A1 WO2010083739 A1 WO 2010083739A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
detection message
bidirectional forwarding
home gateway
edge node
Prior art date
Application number
PCT/CN2010/070161
Other languages
English (en)
French (fr)
Inventor
郑若滨
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to AT10733212T priority Critical patent/ATE557497T1/de
Priority to KR1020117018476A priority patent/KR101245786B1/ko
Priority to JP2011546574A priority patent/JP5118257B2/ja
Priority to ES10733212T priority patent/ES2384162T3/es
Priority to EP10733212A priority patent/EP2383934B1/en
Publication of WO2010083739A1 publication Critical patent/WO2010083739A1/zh
Priority to US13/187,972 priority patent/US8331245B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/026—Details of "hello" or keep-alive messages
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/045—Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B

Definitions

  • IP session survival monitoring method and system home gateway and network device
  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to an IP session survival monitoring method and system, a home gateway, and a network device. Background technique
  • an IP session represents a network access connection session associated with a user's IP address, "IP Session” and a point-to-point protocol (Point-to-Point Protocol; PPP) Session is peer-to-peer.
  • IP Session IP Session
  • PPP Session Point-to-Point Protocol
  • Subscriber Session is a general term for "IP Session” and "PPP Session”.
  • the PPP session uses a unique PPP survival detection mechanism
  • the IPv4 session uses a unique bidirectional forwarding detection (BFD) or Address Resolution Protocol (ARP) survival detection mechanism.
  • BFD bidirectional forwarding detection
  • ARP Address Resolution Protocol
  • IP Session is usually terminated on an IP Edge Node, such as a Broadband Network Gateway (BNG) or Broadband Remote Access Server (BRAS), on the other side of the “IP Session”.
  • BNG Broadband Network Gateway
  • BRAS Broadband Remote Access Server
  • IP Session is a session connection established between the user equipment and the IP edge node, which is a single hop session.
  • IP Session is used for network management of user access networks, such as billing and status.
  • IP Session uses the IP address or IP address prefix as the identifier of "IP Session”.
  • the HGW supports Network Address Translation (NAT) under IPv4, and the "IPv4 Session" is "Single IPv4 hop”;
  • the HGW is a router (IPv2) under IPv6.
  • IPv2 IPv2
  • NAT Network Address Translation
  • the user equipment at the end of the IP Session is not necessarily the HGW.
  • the user equipment (UE) after the HGW can be extended to "Multiple IPv6 hop", but how the UE behind the HGW traverses the HGW to implement the "Multiple hop IPv6 Session" survival monitoring ( Keepalive), there is no solution in the prior art. Summary of the invention
  • the embodiment of the invention provides a method and system for monitoring the survival of an IP session, a home gateway and a network device, and implements the monitoring of the survival of the "Multiple hop IPv6 Session".
  • the embodiment of the invention provides an IP session survival monitoring method, which includes:
  • the user terminal or the IP edge node receives the bidirectional forwarding detection message sent by the home gateway, where the first authentication domain value included in the bidirectional forwarding detection message is a difference between the user terminal IP address prefix and the home gateway IP address prefix;
  • the user terminal or the IP edge node monitors whether the IP session between the IP edge node and the user terminal is alive according to the first authentication domain value in the bidirectional forwarding detection message.
  • the embodiment of the invention provides a home gateway, including:
  • a first receiving module configured to receive a bidirectional forwarding detection message sent by the user terminal or the IP edge node
  • a first forwarding module configured to send, according to the bidirectional forwarding detection message received by the first receiving module, a bidirectional forwarding detection message including a first authentication domain value to the IP edge node or the user terminal, where the first The authentication field value is the difference between the user terminal IP address prefix and the home gateway IP address prefix.
  • the embodiment of the invention provides a network device, including:
  • a second receiving module configured to receive a bidirectional forwarding detection message sent by the home gateway, where the first authentication domain value included in the bidirectional forwarding detection message is a difference between a user terminal IP address prefix and a home gateway IP address prefix;
  • a processing module configured to monitor, according to the first authentication domain value in the bidirectional forwarding detection message, Whether the IP session between the IP edge node and the user terminal is alive.
  • An embodiment of the present invention provides an IP session survival monitoring system, including:
  • a home gateway configured to send a bidirectional forwarding detection message to the network device, where the first authentication domain value in the bidirectional forwarding detection message is a difference between the user terminal IP address prefix and the home gateway IP address prefix;
  • a network device configured to receive a bidirectional forwarding detection message sent by the home gateway, and monitor, according to the first authentication domain value in the bidirectional forwarding detection message, whether an IP session between the IP edge node and the user terminal is alive .
  • the IP session surviving monitoring method and system, the home gateway and the network device provided by the embodiments of the present invention use "Multihop BFD” as the survival monitoring mechanism of the "Multihop IPv6 Session", and can establish the "IPv6 Session" in the UE after the HGW and
  • the "Single hop IP Session” is extended to "Multihop IP Session" between IP edge nodes to implement the "Multiple hop IPv6 Session" survival monitoring.
  • IPv6 Session is a schematic structural diagram of an "IPv6 Session" system of the present invention
  • FIG. 2 is a schematic diagram of a data plane of a "Multihop IPv6 Session" according to the present invention
  • IPv6 Session survivability monitoring agent of the present invention
  • Embodiment 1 of an IP session survival monitoring method according to the present invention
  • Embodiment 2 is a schematic diagram of Embodiment 2 of an IP session survival monitoring method according to the present invention.
  • Embodiment 3 of an IP session survival monitoring method according to the present invention.
  • FIG. 7 is a schematic structural diagram of an embodiment of a home gateway according to the present invention.
  • FIG. 8 is a schematic structural diagram of an embodiment of a network device according to the present invention.
  • FIG. 9 is a schematic structural diagram of an embodiment of an IP session survival monitoring system according to the present invention. detailed description The technical solutions of the embodiments of the present invention are further described below with reference to the accompanying drawings and specific embodiments.
  • FIG. 1 is a schematic structural diagram of an "IPv6 Session” system according to the present invention.
  • the HGW is a Layer 3 router, and implements an "IPv6 Session Keepalive” (Proxy) function.
  • IPv6 Session Keepalive Proxy
  • Multiple UEs or multiple "IPv6 Sessions” can be bundled into a UE group or an "IPv6 Session” group by management domain, region, or service classification.
  • IP Session 0 is a single-hop “IPv6 Session” established between HGW and BNG by HGW as user (Subscriber);
  • IP Session n is user terminal (especially nomadic user) as user (Subscriber) in UE and
  • IPv6 Session established between BNG,
  • IP Session n is Multihop "Session", UE to HGW is the first hop, HGW goes to "IP Edge Node” as the second hop;
  • HGW is configured by dynamic host
  • DHCP Dynamic Host Configuration Protocol
  • PD Prefix Delegation
  • an address prefix such as the 56-bit address prefix "Prefix Z”.
  • the HGW uses the "Prefix Z" to extend different sub-prefixes for subsequent UEs. For example, different users have different 64-bit sub-prefixes, or fixed users and nomadic users have different 64-bit sub-prefixes.
  • FIG. 2 is a schematic diagram of the data plane of the "Multihop IPv6 Session” of the present invention.
  • the "Multihop IP Session” between the BNG and the UE is carried in a single hop “IP Session” between the BNG and the HGW.
  • IP Session the single hop between the BNG and the HGW.
  • FIG. 3 is a schematic diagram of the principle of the "IPv6 Session” survivability monitoring agent of the present invention.
  • the block “P” represents the peer end (Peer), and the present invention mainly has two schemes:
  • Solution 1 Use "Multihop BFD” as the Keepalive mechanism of the "Multihop IPv6 Session”. Set the IPv6 Session Keepalive Proxy on the HGW to transparently transmit the "Multihop BFD” protocol message or modify the BFD protocol message. Discriminator domain;
  • IPv6 Session Keepalive Proxy on the HGW, "Legacy UE” Use “Single Keep Unive” for the first hop of "Single ho Neighbor Unreachable Detection (NUD) / "BFD”, and “Session Keepalive” for "Second Mega” with “Single hop BFD” for BNG ⁇ , " The IPv6 Session Keepalive Proxy implements the surviving relay of the first hop NUD/BFD to the second hop BFD.
  • Multiple UEs or multiple "IPv6 Sessions” can be bundled into UE groups or IPv6 Session groups according to the management domain, region, or service classification.
  • the proxy can use different wide area network (WAN) ports to correspond to different UE groups or "IPv6 Session” groups. Specifically, when the UE group or "IPv6 Session" group contains only one UE or "IPv6 Session” , the proxy can use different WAN ports to correspond to different UEs or "IPv6 Sessions”.
  • WAN wide area network
  • FIG. 4 is a schematic diagram of Embodiment 1 of an IP session survival monitoring method according to the present invention.
  • the "IPv6 Session Keepalive Proxy" set on the HGW implements the "Multiple hop IPv6 Session" survivability monitoring in a transparent manner.
  • the IP edge node may include a BNG or a BRAS, and the like. Be explained.
  • the monitoring of the "IP Session" between the UE and the BNG includes the HGW forwarding the BFD message sent between the UE and the BNG.
  • the first authentication domain (Discrinum field) in the BFD message is the user terminal IP.
  • the corresponding "BFD Session” is alive, because "BFD Session” and "IP Session” are Associated, so you can judge whether the "IP Session" is alive.
  • the BNG receives the BFD message and monitors whether the IP session between the BNG and the UE is alive according to the first authentication domain value of the BFD message. For the uplink direction, the UE sends a BFD message to the BNG. After receiving the message, the BNG can determine the corresponding "based on the value of the "Discriminator” field in the message and the pre-defined "BFD Session" identifier. Whether IPv6 Session" is alive.
  • IPv6 Session survival monitoring between HGW and BNG includes HGW receiving BNG Sending a BFD message, and monitoring whether the IP session between the HGW and the BNG point is alive according to the second discriminator field value in the BFD message, and the second discriminating field value is set to a special value, such as "0" or "OxFFFF".
  • the BNG sends a BFD message to the HGW.
  • the HGW can determine the corresponding "BFD Session" according to the value of the "Discriminator" field in the BFD message, and monitor the survival status of the associated "IP Session" accordingly.
  • the BNG receives the BFD message sent by the HGW, and monitors whether the IP session between the BNG and the HGW is alive according to the source IP address related information and/or the second authentication domain value of the BFD message, and the source IP address related information includes the source IP address or the source. IP address prefix.
  • the HGW can determine the corresponding "BFD Session" according to the source IP address of the message, that is, the source IP address/prefix of the BNG, and/or the value of the "Discriminator" field in the BFD message. Based on this, the associated "IP Session" is monitored for survival.
  • the "BFD Session” used by the "Keepalive” of the “IPv6 Session” is "Keepalive” with the HGW address or BNG address.
  • the "Discriminator” of the BFD message is set to "0" or "OxFFFF".
  • the "BFD Session” used by the "IPv6 Session Keepalive” of the “IPv6 Session” is "Keepalive” interaction with the address or BNG address of the UE.
  • the BNG/UE associates the "BFD Session” with the corresponding "IPv6 Session” I "IPv6 Session” group according to the value of the "Discriminator” field of the BFD message.
  • the "Discriminator” field can include the “My Discriminator” or "Your Discriminator” field.
  • the user may have multiple IP addresses and multiple "IP Sessions” under the same “Prefix Yn”. These multiple "IP Sessions” can be used as an "IP Session” group, and "Discriminator” with BFD messages.
  • the value of the "Discriminator" field of the BFD message can represent the "IP Session" group under the same "Prefix Yn", so the first authentication field value is used to identify an IP session or IP address prefix of the same user terminal. Multiple IP sessions.
  • the source IP address prefix is used to identify an IP session
  • the single-hop "BFD Session” is identified by "Prefix Z” as the “Session”
  • the multi-hop “BFD Session” is preceded by "Prefix Z,, or "Prefix Yn” As the identifier of "Session”.
  • IP Session 0 can be marked with "Prefix Z”
  • BFD Session 0 is used to support "Keepalive”
  • the "Discriminator” field of BFD messages is set to "0" or "OxFFFF”
  • BNG /UE associates "BFD Session 0" with the corresponding "IPv6 Session 0" according to the value of the source IP address prefix "Prefix Z” and "Discriminator” field of the BFD message (0 or OxFFFF).
  • IP Session 1 For "IP Session 1", you can use the "Prefix ⁇ flag, use "BFD Session 1" to support "Keepalive", the "Discriminator” field of the BFD message is set to (Y1-Z); BNG/UE according to the Discriminator of the BFD message” The value of the field (Y1-Z) associates "BFD Session 1" with the corresponding "IPv6 Session ⁇ ".
  • IP Session n For "IP Session n", you can use "Prefix Yn” to identify "BFD Session n” to support "Keepalive”, and the "Discriminator” field of BFD messages is set to (Yn-Z); BNG/UE according to BFD messages" The value of the Discriminator field (Yn-Z) associates "BFD Session n" with the corresponding "IPv6 Session n".
  • the "IPv6 Session Keepalive Proxy" set on the HGW is used to implement the "Multiple hop IPv6 Session" survival monitoring, and the proxy mode is the HGW receiving the detection of the mutual transmission between the UE or the BNG.
  • the proxy mode is the HGW receiving the detection of the mutual transmission between the UE or the BNG.
  • the modified detection message is forwarded to the BNG or the UE; the UE or the BNG monitors whether the IP session between the BNG and the UE is alive according to the first authentication domain value of the detection message.
  • the proxy mode according to the port settings of the HGW, they are introduced separately:
  • a case of the proxy mode is as shown in FIG. 4, for the monitoring of the survival of the "IP Session" between the UE and the BNG, after modifying the first authentication domain value in the detection message, forwarding the modified to the BNG or the UE
  • the detecting message specifically includes: receiving, by the HGW, the BFD message sent by the UE, and modifying the first authentication domain value in the BFD message to the difference between the IP address prefix of the user terminal and the IP address prefix of the home gateway, and then sending the modified BFD message to the BNG
  • the HGW receives the BFD message sent by the BNG.
  • the first authentication field value in the BFD message is the difference between the user terminal IP address prefix and the home gateway IP address prefix, and the first authentication domain value is modified to a value recognizable by the UE, and The modified BFD message is sent to the UE.
  • the "BFD Session” used by the "IPv6 Session Keepalive” of the "IPv6 Session” is "Keepalive” interaction with the user's address or BNG address.
  • "IPv6 Session Keepalive Proxy” will be the "Discriminator" field of the first hop BFD message.
  • the value of the value is changed to (Yn-Z), that is, the difference between "Prefix Yn” and “Prefix Z", and then forwarded on the second hop; or "IPv6 Session Keepalive Proxy" will be the "Discriminator” of the second hop BFD message.
  • the value of the field "(Yn-Z) is changed to the value that can be recognized by the UE/BNG, and then forwarded on the first hop.
  • the BNG/UE associates the "BFD Session” with the value of the "Discriminator” field of the BFD message.
  • the corresponding "IPv6 Session” is associated.
  • the "Discriminator” field can include the "My Discriminator” or "Your Discriminator” field.
  • the user may have multiple IP addresses under the same "Prefix Yn", multiple" IP Session", these multiple "IP Sessions” can be associated with the value of "Discriminator” i of the BFD message as an "IP Session” group, ie the "Discriminator” field of the BFD message can represent the same "Prefix Yn” "Under the IP Sessio n” group.
  • the single-hop "BFD Session" uses "Prefix Z" as the identifier of "Session”; the multi-hop “BFD Session” uses "Prefix Z,, or "Prefix Yn” as the identifier of "Session”.
  • FIG. 5 is a schematic diagram of Embodiment 2 of the IP session survival monitoring method according to the present invention.
  • the present embodiment provides an 'IPv6 Session Keepalive Proxy' proxy set set on the HGW.
  • the method implements the survival monitoring of the "Multiple hop IPv6 Session".
  • the "Proxy" uses different WAN ports to correspond to different UE groups or IPv6 Session groups. For example, in Figure 5, a WAN port 0 corresponds to the user 1 to the user n. .
  • the HGW receives the BFD or NUD message sent by the UE through the corresponding LAN port.
  • the next hop survival monitoring message that is, the next hop monitoring message
  • the source address and the destination address are both changed.
  • the destination address is changed to the address of the BNG in the uplink direction
  • the source address is changed to the address of the HGW.
  • the first authentication domain value in the BFD message is modified to be the user terminal.
  • the reconstructed BFD message including the modified first authentication domain value is sent to the BNG through a WAN port corresponding to the different local area network port;
  • the HGW receives the NUD message sent by the UE, reconstructs the BFD message of the next hop, and sends the reconstructed BFD message to the BNG.
  • the HGW receives the BFD message sent by the BNG through a WAN port.
  • the first authentication field in the BFD message is the difference between the IP address prefix of the user terminal and the IP address prefix of the home gateway, and the first authentication domain value is modified to be the user.
  • the corresponding value of the terminal IP address prefix is used to reconstruct the BFD message, and the BFD message including the modified first authentication domain value is sent to the UE through the corresponding local area network port.
  • the "IPv6 Session" surviving monitoring between the HGW and the BNG includes the HGW receiving the BFD message sent by the BNG, and monitoring whether the IP session between the HGW receiving the BNG point is alive according to the second discriminator field value in the BFD message.
  • the second discrimination field value is set to a special value such as "0" or "OxFFFF".
  • the BNG sends a BFD message to the HGW.
  • the HGW can determine the corresponding "BFD Session” according to the value of the "Discriminator" field in the BFD message, and monitor the survival status of the associated "IP Session" accordingly.
  • the BNG receives the BFD message sent by the HGW, and monitors the IP session between the BNG and the HGW according to the second authentication domain value of the BFD message. Whether it is alive.
  • the HGW can determine the corresponding "BFD Session” according to the value of the "Discriminator” field in the BFD message, and monitor the survival status of the associated "IP Session" accordingly.
  • the "BFD Session" used by the single-hop “Keepalive of IPv6 Session” performs "Keepalive” interaction with the HGW address or BNG address, and the BFD message "Discriminator” field setting is set to a special value, such as "0" or " OxFFFF".
  • IPv6 Session Keepalive of the multi-hop “IPv6 Session” is completed with two single hops.
  • the "Proxy” relays the “Keepalive” process of the first hop and the second hop, and is responsible for maintaining the first hop and the second hop.”
  • the state of Keepalive is synchronized, and the "Discriminator” i of "BDF Session” can also be set or falsified by "Proxy".
  • the first flea uses the "NUD/BFD Session" of the single hop to perform "keepalive”
  • the second hop uses the "BFD Session” of the single hop to perform "keepalive”.
  • the "NUD/BFD Session" of the single hop for the first hop uses the user's address or "Proxy” address, which can be the "Keepalive” interaction of the HGW's LAN port address.
  • the UE/HGW associates the "BFD Session" with the corresponding "IPv6 Session” according to the value of the "Discriminator" field of the BFD message.
  • IPv6 Session Keepalive Proxy changes the value of the "Discriminator” field of the first megabit BFD message to (Yn-Z) and then forwards it on the second hop; or "IPv6 Session Keepalive Proxy” hops the second hop BFD message.
  • the value of the "Discriminator” field (Yn-Z) is changed to the value corresponding to "Prefix Yn” and then forwarded on the first hop.
  • the second hop, the BNG/HGW associates the "BFD Session” with the corresponding "IPv6 Session" according to the source IP address/prefix of the BFD message and/or the value of the "Discriminator” field.
  • the single-hop "BFD Session” uses “Prefix Z” as the identifier of "Session”; the multi-hop “BFD Session” uses "Prefix Z,” or "Prefix Yn” as the identifier of "Session”.
  • the BNG/HGW associates "BFD Session 0" with the corresponding "IPv6 Session n" according to the source IP address prefix "Prefix Z" and "Discriminator” i of the BFD message (Yn-Z); HGW/UE according to BFD
  • the source IP address prefix "Prefix Yn" of the message associates "BFD Session In” with the corresponding "IPv6 Session n".
  • the HGW also performs the state synchronization operation of the session peer, including "Proxy” to collect the "IP Session".
  • the BFD diagnostic code or NUD status is expressed on the other hop by the BFD diagnostic code or NUD status.
  • the "Proxy” is responsible for the BFD message of the second hop.
  • the "diagnostic code” value is copied to the "diagnostic code” field of the first hop BFD message of all "IP Sessions", or "Proxy” is responsible for diagnosing the survival state of session 2 (Peer2) of the second hop, and then the session pair
  • the survival state of the end 2 ( Peer 2 ) generates a corresponding diagnostic code ( BFD diagnostic code ), and the first hop of all the "IP Sessions” is notified to the peer end 1 ( Peerl ) through the BFD message.
  • the upstream direction "Proxy” is responsible for diagnosing the survival state of the first hop session peer 1 (PEerl) through the NUD mechanism, and then the first hop survival state.
  • the corresponding diagnostic code (BFD diagnostic code) is generated, and the peer end 2 (PEer2) is notified by the BFD message.
  • BFD diagnostic code diagnostic code
  • Neighbor Solicitation (NS) message may not reply to the Peer 1 Neighbor Advertisement (NA) message, or the "Proxy” may stop the Neighbor Solicitation (NS) message to the Peer 1 initiative.
  • NA Neighbor Advertisement
  • FIG. 6 is a schematic diagram of Embodiment 3 of the IP session survival monitoring method according to the present invention.
  • the present embodiment provides an 'IPv6 Session Keepalive Proxy' proxy set on the HGW.
  • the method implements the survival monitoring of the "Multiple hop IPv6 Session".
  • the Proxy uses different WAN ports to correspond to different UEs or IPv6 sessions. For example, in FIG. 6, WAN port 1 corresponds to user 1, and WAN port n corresponds to user n.
  • the HGW receives the BFD or NUD message sent by the UE through a LAN port, and reconstructs the next hop survival monitoring message, that is, the next hop monitoring message for the BFD message.
  • the source address and the destination address are both changed.
  • the destination address is changed to the address of the BNG in the uplink direction
  • the source address is changed to the address of the HGW.
  • the first authentication domain value in the BFD message is modified to be the user terminal.
  • the reconstructed BFD message including the modified first authentication domain value is sent to the BNG through a WAN port corresponding to the local area network port; for the NUD message, the HGW receives the NUD sent by the UE.
  • the message reconstructs the BFD message of the next hop and sends the reconstructed BFD message to the BNG.
  • the HGW receives the BFD message sent by the BNG through a WAN port.
  • the first authentication field in the BFD message is a value corresponding to the IP address prefix of the user terminal, and the BFD or NUD message is reconstructed, and the NUD message or the first authentication is included.
  • the BFD message of the domain value is sent to the UE through a local area network port corresponding to the WAN port.
  • IPv6 Session survival monitoring between HGW and BNG includes HGW receiving BNG
  • the BFD message is sent, and according to the second discriminator field value in the BFD message, it is monitored whether the IP session between the HGW receiving the BNG point is alive, and the second discriminating field value is set to a special value, such as "0" or "OxFFFF".
  • the BNG sends a BFD message to the HGW.
  • the HGW can determine the corresponding "BFD Session” according to the value of the "Discriminator" field in the BFD message, and monitor the survival status of the associated "IP Session" accordingly.
  • the BNG receives the BFD message sent by the HGW, and monitors whether the IP session between the BNG and the HGW is alive according to the second authentication domain value of the BFD message.
  • the HGW can determine the corresponding "BFD Session” according to the value of the "Discriminator” field in the BFD message, and monitor the survival status of the associated "IP Session" accordingly.
  • the "BFD Session" used by the "Keepalive” of the single-hop “IPv6 Session” performs a "Keepalive” interaction with an HGW address or a BNG address, and the "Discriminator” field of the BFD message is set to "0" or "OxFFFF".
  • IPv6 Session Keepalive of the multi-hop “IPv6 Session” is completed with two single hops.
  • the "Proxy” relays the “Keepalive” process of the first hop and the second hop, and is responsible for maintaining the first hop and the second hop.” Keepalive” state synchronization.
  • the first flea uses the "NUD/BFD Session" of the single hop to perform "keepalive”
  • the second hop uses the "BFD Session” of the single hop to perform "keepalive”.
  • the "NUD/BFD Session" for the first hop of the first hop uses the user's address or "Proxy” address, which can be the "Keepalive” interaction of the HGW's LAN port address.
  • the UE/HGW associates the "BFD Session" with the corresponding "IPv6 Session” according to the value of the "Discriminator" field of the BFD message.
  • the second hop, the BNG/HGW associates the "BFD Session" with the corresponding "IPv6 Session" according to the source IP address/prefix of the BFD message and/or the value of "Discriminator”i or.
  • "Proxy” uses different WAN ports to correspond to different UEs or "IPv6 Sessions”.
  • the BNG/HGW distinguishes the "IPv6 Sessions” of different users according to the value of the "Discriminator" field of the BFD message.
  • the single-hop "BFD Session” uses “Prefix Z” as the identifier of "Session”; the multi-hop “BFD Session” uses "Prefix Z” or "Prefix Yn” as the identifier of "Session”.
  • IP Session 0 For "IP Session 0", you can use the Prefix Z logo and use "BFD Session”.
  • the "Discriminator” field of the BFD message is set to "0" or "OxFFFF"; BNG/UE will "BFD Session 0" according to the source IP address prefix of the BFD message "Prefix Z" with the corresponding " IPv6 Session 0" is associated.
  • IP Session 1 For "IP Session 1", you can use the Prefix Yl logo, use “BFD Session 11" and “BFD Session 21” to support " Keepalive", and the "Discriminator” field of the "BFD Session 21" message is set to (Yl-Z);
  • the BNG/HGW associates the "BFD Session 21" with the corresponding "IPv6 Session 1" according to the source IP address prefix "Prefix Y1" of the BFD message; the HGW/UE will "BFD” according to the source IP address prefix "Prefix Yl” of the BFD message.
  • Session 11 " is associated with the corresponding "IPv6 Session ⁇ ".
  • IP Session ⁇ For "IP Session ⁇ ,, , you can use the Prefix Yn flag, use "BFD Session In” and
  • BFD Session 2n to support "Keepalive", "BFD Session 2n” BFD message “Discriminator” i or set to (Yn-Z); "BFD Session In” BFD message “Discriminator” field set to "Prefix Yn” The last 32 bits.
  • the BNG/HGW associates the "BFD Session 2n” with the corresponding "IPv6 Session n” according to the source IP address prefix "Prefix Yn" of the BFD message; the HGW/UE will “BFD” according to the source IP address prefix "Prefix Yn” of the BFD message.
  • Session In is associated with the corresponding "IPv6 Session n".
  • the HGW also performs the state synchronization operation of the session peer, and may include "Proxy” to collect the "IP Session" one-hop diagnostic code (BFD diagnostic code) or NUD.
  • BFD diagnostic code one-hop diagnostic code
  • NUD one-hop diagnostic code
  • the status is, for example, the neighbor is unreachable, and is expressed on another hop by a diagnostic code (BFD diagnostic code) or NUD.
  • "Proxy” is responsible for diagnosing the survival state of the first hop session peer 1 (PEerl) through the NUD mechanism, and then the first hop survival state. Generate a corresponding diagnostic code (BFD diagnostic code), and notify the peer 2 (PEer2) through the BFD message; for example, when the "Proxy” sends a Neighbor Solicitation (NS) message to Peer 1, it is not within the specified time.
  • BFD diagnostic code corresponding diagnostic code
  • NS Neighbor Solicitation
  • the IP session survival monitoring method provided by the embodiment of the present invention uses "Multihop BFD” as the survival monitoring mechanism of the "Multihop IPv6 Session” or “IPv6 Session Keepalive Proxy” on the HGW, so that the "IPv6 Session” can be established in the HGW.
  • the subsequent "Single hop IP Session” is extended to "Multihop IP Session” between the UE and the IP edge node to implement the "Multiple hop IPv6 Session" survival monitoring.
  • FIG. 7 is a schematic structural diagram of a home gateway embodiment of the present invention, as shown in FIG.
  • the home gateway includes a first receiving module 11 and a first forwarding module 12, where the first receiving module 11 is configured to receive a bidirectional forwarding detection message sent by the user terminal or the IP edge node; the first forwarding module 12 is configured to use the first And receiving, by the receiving module, a bidirectional forwarding detection message, and sending, by the IP edge node or the user terminal, a bidirectional forwarding detection message including a first authentication domain value, where the first authentication domain value is a user terminal IP address prefix and a home gateway The difference between the IP address prefixes. Specifically, the first receiving module 11 receives the BFD message sent by the UE or the BNG.
  • the first discriminator value in the BFD message is the difference between the IP address prefix of the user terminal and the IP address prefix of the home gateway. If the first authentication domain value in the BFD message is not the difference between the user terminal IP address prefix and the home gateway IP address prefix, then the user's IP address prefix and the home gateway IP address are changed. After the difference of the address prefix, it is forwarded to the UE or BNG.
  • the home gateway provided in this embodiment further includes a proxy module 13 for modifying the first authentication domain value in the bidirectional forwarding detection message received by the first receiving module 11.
  • a proxy module 13 for modifying the first authentication domain value in the bidirectional forwarding detection message received by the first receiving module 11.
  • the home gateway in order to realize the survival monitoring of the "IP Session" between the UE connected to the IP edge node and the IP edge node, such as the BNG, adding a proxy function in the home gateway, and implementing the first hop to the second hop through the proxy
  • the first receiving module 11 receives the BFD detection message sent by the UE or the BNG, and the proxy module 13 modifies the authentication domain value in the detection message according to the actual situation, so that it is suitable for transmission in the next hop to achieve survival monitoring. purpose.
  • the first forwarding module 12 sends a detection message including the modified home domain value to the destination of the next hop, which may be the UE or the BNG.
  • the home gateway provided in this embodiment further includes a sending module 14 configured to send a detection message including a second authentication domain value to the BNG, where the second authentication domain value is "0" or "OxFFFF", and the home gateway passes the sending module 14 Implement session monitoring monitoring with BNG.
  • the "IPv6 Session Keepalive Proxy" is set on the HGW, so that the "IPv6 Session” can be established between the UE behind the HGW and the IP edge node, and the "Single hop IP Session" is expanded to "Multihop”.
  • the IP Session "implements the survival monitoring of the "Multiple hop IPv6 Session”.
  • FIG. 8 is a schematic structural diagram of an embodiment of a network device according to the present invention.
  • the network device includes a second receiving module 21 and a processing module 22, and the network device receives a BFD message sent by the home gateway through the second receiving module 21, where The first authentication domain value included in the BFD message is a difference between the user terminal IP address prefix and the home gateway IP address prefix.
  • the processing module 22 monitors the IP edge node according to the first authentication domain value in the BFD message. Whether the IP session with the user terminal is alive.
  • the processing module is further configured to determine, according to the first authentication domain value in the bidirectional forwarding detection message, whether a bidirectional forwarding detection session corresponding to the first authentication domain value is alive, and detect whether the session is alive according to the bidirectional forwarding And determining whether the IP session associated with the two-way forwarding detection session is alive.
  • the network device provided in this embodiment may be a UE or a BNG, and the BFD message sent by the home gateway monitors the survival of the "IPv6 Session" between the UE and the BNG.
  • FIG. 9 is a schematic structural diagram of an embodiment of an IP session survival monitoring system according to the present invention, as shown in FIG.
  • the IP session surviving monitoring system includes a home gateway 1 and a network device 2, wherein the home gateway 1 is configured to send a bidirectional forwarding detection message to the network device, where the first authentication domain value in the bidirectional forwarding detection message is a user terminal IP address prefix and The difference between the home gateway IP address prefix and the network device 2 is configured to receive the bidirectional forwarding detection message sent by the home gateway, and monitor the IP edge node and the user terminal according to the first authentication domain value in the bidirectional forwarding detection message. Whether the IP session between the two is alive.
  • the home gateway and the network device involved in the IP session surviving monitoring system provided in this embodiment may use the home gateway and the network device provided in the foregoing embodiments, and details are not described herein again.
  • IPv6 Session In the IP session surviving monitoring system provided in this embodiment, by setting an "IPv6 Session Keepalive Proxy" on the HGW, an “IPv6 Session” can be established between the UE behind the HGW and the IP edge node, and “Single hop IP Session” "Expanded to "Multihop IP Session” implements the survival monitoring of "Multiple hop IPv6 Session”.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Computer Security & Cryptography (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Alarm Systems (AREA)
  • Computer And Data Communications (AREA)

Description

IP会话存活监控方法及系统、 家庭网关和网絡设备 技术领域
本发明实施例涉及通信技术领域，尤其涉及一种 IP会话存活监控方法及 系统、 家庭网关和网络设备。 背景技术
在接入网中， IP会话 ( session )代表了与一个用户的 IP地址关联的网 络接入连接会话， "IP Session" 与点到点的链路层协议 ( Point-to-Point Protocol; 简称： PPP )会话 ( session )是对等的，用户会话（ Subscriber Session ) 是 "IP Session" 和 "PPP Session" 的统称。 PPP会话釆用特有的 PPP存活检 测机制， IPv4 会话釆用特有的双向转发检测 （Bidirectional Forwarding Detection; 以下简称： BFD )或地址解析协议 (Address Resolution Protocol; 简称： ARP)存活检测机制。
"IP Session" 通常在 IP边缘节点 （IP Edge Node ) , 例如宽带网络网关 ( Broadband Network Gateway, BNG )或宽带接入服务器（ Broadband Remote Access Server, BRAS )上终结， "IP Session" 的另一侧通常在用户设备， 例 如家庭网关 （Home Gateway, HGW )上终结， 即 "IP Session" 是在用户设 备与 IP边缘节点建立的一条会话连接，为单跳（ single hop )会话。 "IP Session" 用于网络对用户接入网络的管理， 如计费和状态等。 "IP Session" 以 IP地址 或 IP地址前缀作为 "IP Session" 的标识。
在实现本发明过程中， 发明人发现现有技术中至少存在如下问题： 现有 技术 IPv4下 HGW支持网络地址转换 (Network Address Translation, NAT), "IPv4 Session"为 "Single IPv4 hop"；而在 IPv6下 HGW为路由器（ Router ) , 通常不支持 NAT, 此时 "IP Session" 终结处的用户设备不一定是 HGW, 可 能是 HGW之后的用户终端 （ User Equipment, UE ) , 此时 "IPv6 Session" 将需要扩展到 "Multiple IPv6 hop" , 但 HGW后面的 UE如何穿越 HGW以 实现 "Multiple hop IPv6 Session" 的存活监控 ( Keepalive ) , 现有技术尚无 解决方案。 发明内容
本发明实施例提供一种 IP会话存活监控方法及系统、 家庭网关和网络设 备， 实现了 "Multiple hop IPv6 Session" 的存活监控。
本发明实施例提供一种 IP会话存活监控方法， 包括：
用户终端或 IP边缘节点接收家庭网关发送的双向转发检测消息， 所述双 向转发检测消息中包括的第一鉴别域值为用户终端 IP地址前缀与家庭网关 IP 地址前缀的差值；
用户终端或 IP边缘节点根据所述双向转发检测消息中的第一鉴别域值， 监控所述 IP边缘节点与所述用户终端之间的 IP会话是否存活。
本发明实施例提供一种家庭网关， 包括：
第一接收模块， 用于接收用户终端或 IP边缘节点发送的双向转发检测消 息；
第一转发模块，用于根据所述第一接收模块接收到的双向转发检测消息， 向所述 IP边缘节点或所述用户终端发送包括第一鉴别域值的双向转发检测消 息， 所述第一鉴别域值为用户终端 IP地址前缀与家庭网关 IP地址前缀的差 值。
本发明实施例提供一种网络设备， 包括：
第二接收模块， 用于接收家庭网关发送的双向转发检测消息， 所述双向 转发检测消息中包括的第一鉴别域值为用户终端 IP地址前缀与家庭网关 IP 地址前缀的差值；
处理模块， 用于根据所述双向转发检测消息中的第一鉴别域值， 监控所 述 IP边缘节点与所述用户终端之间的 IP会话是否存活。
本发明实施例提供一种 IP会话存活监控系统， 包括：
家庭网关， 用于向网络设备发送双向转发检测消息， 所述双向转发检测 消息中的第一鉴别域值为用户终端 IP地址前缀与家庭网关 IP地址前缀的差 值；
网络设备， 用于接收所述家庭网关发送的双向转发检测消息， 根据所述 双向转发检测消息中的第一鉴别域值， 监控所述 IP边缘节点与所述用户终端 之间的 IP会话是否存活。
本发明实施例提供的 IP会话存活监控方法及系统、家庭网关和网络设备， 用 "Multihop BFD" 作为 "Multihop IPv6 Session" 的存活监控机制， 而能将 "IPv6 Session"建立于 HGW之后的 UE与 IP边缘节点之间， 将 "Single hop IP Session" 扩展为 "Multihop IP Session" 实现了 "Multiple hop IPv6 Session" 的存活监控。 附图说明
图 1为本发明 "IPv6 Session" 系统结构示意图；
图 2为本发明 "Multihop IPv6 Session" 数据面示意图；
图 3为本发明 "IPv6 Session" 存活监控代理原理示意图；
图 4为本发明 IP会话存活监控方法实施例一示意图；
图 5为本发明 IP会话存活监控方法实施例二示意图；
图 6为本发明 IP会话存活监控方法实施例三示意图；
图 7为本发明家庭网关实施例结构示意图；
图 8为本发明网络设备实施例结构示意图；
图 9为本发明 IP会话存活监控系统实施例结构示意图。 具体实施方式 下面结合附图和具体实施例进一步说明本发明实施例的技术方案。
图 1为本发明 "IPv6 Session" 系统结构示意图， 如图 1所示， HGW为 三层路由器， 实现 "IPv6 Session Keepalive" (存活监控） "Proxy" (代理） 功能。 多个 UE或多个 "IPv6 Session" 可以按管理域、 地域或业务的分类捆 绑形成 UE组或 "IPv6 Session" 组。 其中， "IP Session 0" 为 HGW作为用 户（ Subscriber )在 HGW和 BNG间建立的单跳 "IPv6 Session"； "IP Session n" 为用户终端 （特别是游牧用户）作为用户 （Subscriber )在 UE和 BNG间 建立的 "IPv6 Session" , "IP Session n" 为多跳 (Multihop) "Session" , UE到 HGW为第一跳， HGW再到 "IP Edge节点" 为第二跳； HGW通过动 态主机配置协议 ( Dynamic Host Configuration Protocol, DHCP ) 前缀委派 ( Prefix Delegation, PD )申请地址前缀， 例如 56位的地址前缀 "Prefix Z" 。 HGW通过 "Prefix Z" 为其后的 UE扩展不同的子前缀， 例如不同的用户有 不同的 64位子前缀， 或者固定用户和游牧用户有不同的 64位子前缀。 "IP Session" 以 IP地址 /前缀作为 "IP Session" 标识， 例如 "IP Session 0" 以 56 位的 "Prefix Z" 作为标识， "IP Session n" 以 64位的 "Prefix Yn，， 作为标 识， 其中， η=1、 2、 3... ...。
图 2为本发明 "Multihop IPv6 Session" 数据面示意图， 如图 2所示， 在 数据面上，在 BNG到 UE间的 "Multihop IP Session"承载于在 BNG到 HGW 间的单跳 "IP Session" 之上。 图 3为本发明 "IPv6 Session" 存活监控代理 原理示意图， 如图 3所示， 其中方块 "P" 代表会话对端 （Peer ) , 本发明主 要有两种方案：
方案 1、 釆用 "Multihop BFD" 作为 "Multihop IPv6 Session" 的存活监 控（ Keepalive )机制， 在 HGW上设置存活监控代理（ IPv6 Session Keepalive Proxy ) , 透传 "Multihop BFD" 协议消息或修改 BFD 协议消息的鉴别 ( Discriminator )域；
方案 2、在 HGW上设置 "IPv6 Session Keepalive Proxy" , "Legacy UE" 釆用 "Single ho 邻机不能到达检测（ Neighbor Unreachable Detection, NUD ) / "BFD" 进行第一跳的 "Session keepalive" , BNG釆用 "Single hop BFD" 进行第二兆的 "Session keepalive" , "IPv6 Session Keepalive Proxy" 实现第 一跳 NUD/BFD到第二跳 BFD的存活中继。 多个 UE或多个 "IPv6 Session" 可以按管理域、 地域或业务的分类捆绑形成 UE组或 IPv6 Session组， 代理 ( Proxy )可釆用不同的广域网 （ WAN ) 口与不同的 UE组或 "IPv6 Session" 组相对应， 特殊地， 当 UE组或 "IPv6 Session" 组只包含一个 UE或 "IPv6 Session" , 则代理可釆用不同的 WAN口与不同的 UE或 "IPv6 Session" 相 对应。
图 4为本发明 IP会话存活监控方法实施例一示意图， 本实施例提供的是
HGW上设置的 "IPv6 Session Keepalive Proxy"釆用透传的方式实现 "Multiple hop IPv6 Session" 的存活监控， IP边缘节点可以包括 BNG或 BRAS等， 本 发明各实施例以 IP边缘节点以 BNG为例进行说明。 如图 4所示， 对于 UE 与 BNG之间的 "IP Session" 存活监控包括 HGW转发 UE和 BNG之间相互 发送的 BFD消息， BFD消息中的第一鉴别域（ Discriminator域）值为用户终 端 IP地址前缀与家庭网关 IP地址前缀的差值； UE接收 BFD消息 , 并根据 第一鉴别域值监控 UE与 BNG之间的 IP会话是否存活；对于下行方向， BNG 发送 BFD消息给 UE, UE接收到该消息后， 可以根据其中的 "Discriminator" 域的值，并结合预先规定好的 "BFD Session"标识，得出对应的 "BFD Session" 是存活的， 由于 "BFD Session" 与 "IP Session" 是相关联的， 因此可以据此 判断出 "IP Session" 是否存活。 BNG接收 BFD消息， 并根据 BFD消息的第 一鉴别域值， 监控 BNG与 UE之间的 IP会话是否存活。 对于上行方向， UE 发送 BFD 消息给 BNG , BNG 接收到该消息后可以根据该消息中的 "Discriminator" 域的值， 并结合预先规定好的 "BFD Session" 标识， 可以 据此判断出对应的 "IPv6 Session" 是否存活。
对于 HGW与 BNG之间的 "IPv6 Session"存活监控包括 HGW接收 BNG 发送的 BFD消息 , 并根据 BFD消息中的第二鉴别域（ Discriminator域）值， 监控 HGW与 BNG点之间的 IP会话是否存活， 第二鉴别域值设置为特殊值， 如为 "0" 或 "OxFFFF" 。 下行方向， BNG向 HGW发送 BFD消息， HGW 可以根据 BFD消息中的 "Discriminator"域的值判断出对应的 "BFD Session" , 便据此监控相关联的 "IP Session" 的存活状态。 BNG接收 HGW发送的 BFD 消息， 并根据 BFD消息的源 IP地址相关信息和 /或第二鉴别域值， 监控 BNG 与 HGW之间的 IP会话是否存活， 源 IP地址相关信息包括源 IP地址或源 IP 地址前缀。 上行方向， HGW接收 BNG发送的 BFD消息后， 可以根据该消息 的源 IP地址即 BNG的源 IP地址 /前缀， 和 /或 BFD消息中的 "Discriminator" 域的值判断出对应的 "BFD Session" , 便据此监控相关联的 "IP Session" 的 存活状态。
具体地， 在 HGW的透传模式下：
单跳 "IPv6 Session" 的 "Keepalive" 所釆用的 "BFD Session" 以 HGW 地址或 BNG地址进行 "Keepalive" 交互， BFD消息的 "Discriminator" i或设 置为 "0" 或 "OxFFFF" 。
多跳 "IPv6 Session"的 "IPv6 Session Keepalive"所釆用的 "BFD Session" 以 UE的地址或 BNG地址进行" Keepalive"交互， BFD消息的 "Discriminator" 域值设置为 （Υη-Ζ ) , η=1 , 2, 3 , 即 "Prefix Υη" 与 "Prefix Ζ" 的 差值， 例如， " Prefix Yn = 2002: db8 :200 :122: :/64 " , " Prefix Z = 2002:db8:200:100::/56" , 则 Yn-Z = 0x22, 如表 1所示。
表 1
Figure imgf000008_0001
BNG/UE根据 BFD消息的 "Discriminator" 域的值将 "BFD Session" 与 相应的 "IPv6 Session" I "IPv6 Session" 组关联起来。 其中， "Discriminator" 域可以包括 "My Discriminator" 或 "Your Discriminator" 域。 另夕卜, 用户在 同一个 "Prefix Yn"下， 可能有多个 IP地址， 多个 "IP Session" , 这多个 "IP Session" 可以作为一个 "IP Session" 组， 与 BFD消息的 "Discriminator"
Figure imgf000009_0001
的值相关联，即 BFD消息的 "Discriminator"域可代表一个同一个 "Prefix Yn" 下的 "IP Session"组， 因此第一鉴别域值用于标识一路 IP会话或同一用户终 端 IP地址前缀下的多路 IP会话。
可选地， 源 IP地址前缀用于标识一路 IP会话， 单跳 "BFD Session" 以 "Prefix Z" 作为 "Session" 的标识； 多跳 "BFD Session" 以 "Prefix Z，， 或 "Prefix Yn" 作为 "Session" 的标识。
以图 4为例，对于 "IP Session 0 "可以 "Prefix Z"标识，釆用 "BFD Session 0"以支持 "Keepalive" , BFD消息的 "Discriminator"域设置为 "0"或 "OxFFFF"； BNG/UE根据 BFD消息的源 IP地址前缀 "Prefix Z"和 "Discriminator"域的 值（ 0或 OxFFFF )将 "BFD Session 0" 与相应的 "IPv6 Session 0" 关联起来。
对于 "IP Session 1" , 可以 "Prefix ΥΓ 标识， 釆用 "BFD Session 1 " 以支持 "Keepalive" , BFD消息的 "Discriminator"域设置为（ Y1-Z )； BNG/UE 根据 BFD消息的 Discriminator" 域的值（Y1-Z )将 "BFD Session 1" 与相应 的 "IPv6 Session Γ 关联起来。
对于 "IP Session n" , 可以 "Prefix Yn" 标识， 釆用 "BFD Session n" 以支持 "Keepalive" , BFD消息的 "Discriminator"域设置为（ Yn-Z )； BNG/UE 根据 BFD消息的 "Discriminator" 域的值（Yn-Z )将 "BFD Session n" 与相 应的 "IPv6 Session n" 关联起来。
本发明的再一个实施例提供的是在 HGW 上设置的 "IPv6 Session Keepalive Proxy"釆用代理模式实现 "Multiple hop IPv6 Session"的存活监控， 代理模式为 HGW接收 UE或 BNG之间相互发送的检测消息， 修改检测消息 中的第一鉴别域值后， 向 BNG或 UE转发修改后的检测消息； UE或 BNG根 据检测消息的第一鉴别域值， 监控 BNG与 UE之间的 IP会话是否存活。 对 于代理模式根据 HGW的的端口设置不同， 分别进行介绍：
代理模式的一种情况是如图 4所示，对于 UE与 BNG之间的 "IP Session" 的存活监控， 所述修改检测消息中的第一鉴别域值后， 向 BNG或 UE转发修 改后的检测消息具体包括 , HGW接收 UE发送的 BFD消息 , 将 BFD消息中 的第一鉴别域值修改为用户终端 IP地址前缀与家庭网关 IP地址前缀的差值 后 , 将修改后的 BFD消息发送给 BNG; HGW接收 BNG发送的 BFD消息 , BFD消息中的第一鉴别域值为用户终端 IP地址前缀与家庭网关 IP地址前缀 的差值， 将第一鉴别域值修改为 UE可识别的值， 并将修改后的 BFD消息发 送给 UE。 多跳 "IPv6 Session" 的 "IPv6 Session Keepalive" 所釆用的 "BFD Session" 以用户的地址或 BNG地址进行 "Keepalive" 交互， "IPv6 Session Keepalive Proxy"将第一跳 BFD消息的 "Discriminator"域的值修改为 （Yn-Z), 即 "Prefix Yn"与 "Prefix Z"的差值，再在第二跳上进行转发；或者 "IPv6 Session Keepalive Proxy" 将第二跳 BFD消息的 "Discriminator" 域的值 "（Yn-Z )改 为 UE/BNG所能识别的值，再在第一跳上进行转发。同样， BNG/UE根据 BFD 消息的 "Discriminator" 域的值将 "BFD Session" 与相应的 "IPv6 Session" 关联起来。 其中, "Discriminator" 域可以包括 "My Discriminator" 或 "Your Discriminator"域。 另外， 用户在同一个 "Prefix Yn" 下， 可能有多个 IP地址， 多个 "IP Session" , 这多个 "IP Session" 可以作为一个 "IP Session" 组， 与 BFD消息的 "Discriminator" i或的值相关联， 即 BFD消息的 "Discriminator" 域可代表一个同一个 "Prefix Yn" 下的 "IP Session"组。 可选地， 单跳 "BFD Session"以 "Prefix Z"作为 "Session"的标识； 多跳 "BFD Session"以 "Prefix Z ，， 或 "Prefix Yn" 作为 "Session" 的标识。
对于 HGW与 BNG之间的 "IPv6 Session" 的存活监控， 与在 HGW上设 置的 "IPv6 Session Keepalive Proxy" 釆用透传的方式实现 "Multiple hop IPv6 Session" 的存活监控实现方法相同， 此处不再赘述。
代理模式的另一种情况是如图 5所示， 图 5为本发明 IP会话存活监控方 法实施例二示意图，本实施例提供的是 HGW上设置的' 'IPv6 Session Keepalive Proxy"釆用代理的方式实现 "Multiple hop IPv6 Session"的存活监控， "Proxy" 釆用不同的 WAN口与不同的 UE组或 IPv6 Session组相对应， 例如图 5中， 釆用一个 WAN口 0对应用户 1〜用户 n。
对于 UE与 BNG之间的 "IPv6 Session" 的存活监控， HGW通过对应的 局域网端口接收 UE发送的 BFD或 NUD消息 , 对于 BFD消息 , 要重构下一 跳的存活监控消息即下一跳监控消息的源地址和目的地址均发生改变， 例如 该上行方向上是将目的地址改为 BNG的地址， 将源地址改为 HGW的地址， 具体为将 BFD消息中的第一鉴别域值修改为用户终端 IP地址前缀与家庭网 关 IP地址前缀的差值后， 通过与所述不同的局域网端口对应的一广域网端口 将重构的包括经过修改的第一鉴别域值的 BFD消息发送给 BNG;对 NUD消 息 , HGW接收 UE发送的 NUD消息 , 重构下一跳的 BFD消息 , 并向 BNG 发送重构的 BFD消息 。 下行方向 , HGW通过一广域网端口接收 BNG发送 的 BFD消息， BFD消息中的第一鉴别域值为用户终端 IP地址前缀与家庭网 关 IP地址前缀的差值， 将第一鉴别域值修改为与用户终端 IP地址前缀的对 应值， 重构 BFD消息， 并将包括经过修改的第一鉴别域值的 BFD消息通过 对应的局域网端口发送给 UE。
对于 HGW与 BNG之间的 "IPv6 Session"存活监控包括 HGW接收 BNG 发送的 BFD消息， 并根据 BFD消息中的第二鉴别域（ Discriminator域）值， 监控 HGW接收 BNG点之间的 IP会话是否存活， 第二鉴别域值设置为特殊 值，如为 "0"或 "OxFFFF"。 下行方向， BNG向 HGW发送 BFD消息， HGW 可以根据 BFD消息中的 "Discriminator"域的值判断出对应的 "BFD Session" , 便据此监控相关联的 "IP Session" 的存活状态。 BNG接收 HGW发送的 BFD 消息， 并根据 BFD消息的第二鉴别域值， 监控 BNG与 HGW之间的 IP会话 是否存活。 上行方向， HGW接收 BNG发送的 BFD消息后， 可以根据 BFD 消息中的 "Discriminator" 域的值判断出对应的 "BFD Session" , 便据此监 控相关联的 "IP Session" 的存活状态。
具体地， 单跳 "IPv6 Session的 Keepalive" 所釆用的 "BFD Session" 以 HGW地址或 BNG地址进行 "Keepalive" 交互， BFD消息 "Discriminator" 域设置设置为特殊值， 如为 "0" 或 "OxFFFF" 。
多跳 "IPv6 Session" 的 "IPv6 Session Keepalive"釆用两个单跳完成， 通 过 "Proxy" 中继第一跳和第二跳的 "Keepalive" 过程， 负责保持第一跳和第 二跳的 "Keepalive" 的状态同步， 还可以通过 "Proxy" 进行 "BDF Session" 的 "Discriminator" i或的设置或爹改。
其中， 第一跳釆用单跳的 "NUD/BFD Session" 进行 "keepalive" , 第二 跳釆用单跳的 "BFD Session" 进行 "keepalive" 。
第一跳釆用的单跳的 "NUD/BFD Session" 以用户的地址或 "Proxy" 地 址， 可以是 HGW 的 LAN 口地址进行 "Keepalive" 交互， BFD 消息的 "Discriminator" 域设置为与 "Prefix Yn " ( η=1,2,3 )相对应的值， 例 如推荐取 "Prefix Yn" 的最后 32位作为 "Discriminator" 域的值， 还可取值
( Yn-Z ) η=1,2,3 。
其中，第一跳， UE/HGW根据 BFD消息的 "Discriminator"域的值将 "BFD Session" 与相应的 "IPv6 Session" 关联起来。
第二跳釆用的单跳的 "BFD Session" 以 BNG的地址或 Proxy地址可以 是 HGW的 WAN口地址进行 "Keepalive"交互， BFD消息的 "Discriminator" 域设置为 （ Yn-Z ) n=l, 2,3 , 即 "Prefix Yn" 与 "Prefix Z" 的差值。
"IPv6 Session Keepalive Proxy" 将第一兆 BFD消息的 "Discriminator" 域的值修改为 （ Yn-Z ) ,再在第二跳上进行转发；或者 "IPv6 Session Keepalive Proxy"将第二跳 BFD消息的 "Discriminator"域的值（ Yn-Z )修改为与 "Prefix Yn" 相对应的值， 再在第一跳上进行转发。 其中， 第二跳， BNG/HGW 根据 BFD 消息的源 IP 地址 /前缀和 /或 "Discriminator" 域的值将 "BFD Session" 与相应的 "IPv6 Session" 关联起 来。 "Proxy" 釆用不同的 WAN口与不同的 UE组或 IPv6 Session组相对应， 在同一个 WAN口下， BNG/HGW根据 BFD消息的 "Discriminator" 域的值 来区分不同用户的 "IPv6 Session" 或 "IPv6 Session" 组。
可选地， 单跳 "BFD Session" 以 "Prefix Z " 作为 "Session" 的标识； 多跳 "BFD Session" 以 "Prefix Z ，，或 "Prefix Yn ，，作为 "Session" 的标识。
以图 5为例，对于 "IP Session 0" ,可以 Prefix Ζ标识，釆用 "BFD Session 0"以支持 "Keepalive" , BFD消息的 "Discriminator"域设置为 "0"或 "OxFFFF"； BNG/UE根据 BFD消息的源 IP地址前缀 "Prefix Z"和 "Discriminator"域的 值（ 0或 OxFFFF )将 "BFD Session 0" 与相应的 "IPv6 Session 0" 关联起来。
对于 "IP Session 1" , 可以 "Prefix ΥΓ 标识， 釆用 "BFD Session 11 ，， 和 "BFD Session 0 " 以支持 "Keepalive" , "BFD Session 0 " 消息的 "Discriminator" 域设置为（Yl-Z ) ; BNG/HGW根据 BFD消息的源 IP地址 前缀 "Prefix Z" 和 "Discriminator" 域的值 ( Yl-Z )将 "BFD Session 0" 与 相应的 "IPv6 Session 1" 关联起来； HGW/UE根据 BFD消息的源 IP地址前 缀 "Prefix Y1" 将 "BFD Session 1 Γ 与相应的 "IPv6 Session 1" 关联起来。
对于 IP Session n,可以 "Prefix Yn"标识，釆用 "BFD Session In"和 "BFD Session 0" 以支持 "Keepalive" , "BFD Session 0" 消息的 "Discriminator" i或设置为（ Yn-Z )； "BFD Session In"消息的 "Discriminator" i或设置为 "Prefix Yn" 的最后 32位。 BNG/HGW根据 BFD消息的源 IP地址前缀 "Prefix Z" 和 "Discriminator" i或的值 ( Yn-Z )将 "BFD Session 0 "与相应的 "IPv6 Session n"关联起来； HGW/UE根据 BFD消息的源 IP地址前缀 "Prefix Yn"将 "BFD Session In" 与相应的 "IPv6 Session n" 关联起来。
HGW在进行检测消息转发监控 "IPv6 Session" 存活的过程中， 还要进 行会话对端的状态同步的操作， 包括 "Proxy" 收集 "IP Session" 其中一跳的 诊断码（ BFD diagnostic code) 或 NUD状态， 在另一跳上通过诊断码 ( BFD diagnostic code )或 NUD 态进行表达。
以图 5 为例， 当第一跳和第二跳皆为 "BFD Session" , 则上行方向， "Proxy"负责将第一跳的 BFD消息 "diagnostic code"值复制到第二跳的 BFD 消息的 "diagnostic code"域，或者" Proxy"负责诊断第一跳的会话对端 1( Peerl ) 的存活状态， 然后将会话对端 1 ( Peerl )的存活状态生成相应的诊断码（ BFD diagnostic code ) , 通过 BFD消息通知会话对端 2 ( Peer2 ) , BNG根据 BFD 消息的 "Discriminator" 域的值来区分不同用户的 "IPv6 Session" 的存活状 态； 下行方向， "Proxy" 负责将第二跳的 BFD消息 "diagnostic code" 值复 制到所有 "IP Session"的第一跳 BFD消息的 "diagnostic code"域，或者 "Proxy" 负责诊断第二跳的会话对端 2 ( Peer2 )的存活状态，然后将会话对端 2 ( Peer2 ) 的存活状态生成相应的诊断码 ( BFD diagnostic code ) , 向所有 "IP Session" 的第一跳通过 BFD消息通知会话对端 1 ( Peerl ) 。
当其中一跳为 NUD而另一跳为 "BFD Session" , 则上行方向， "Proxy" 负责通过 NUD机制诊断第一跳会话对端 1 ( Peerl )的存活状态， 然后将第一 跳的存活状态生成相应的诊断码 ( BFD diagnostic code ) , 通过 BFD消息通 知会话对端 2 ( Peer2 ) , BNG根据 BFD消息的 "Discriminator" 域的值来区 分不同用户的 "IPv6 Session" 的存活状态； 例如， 当 "Proxy" 向 Peer l发出 邻居请求（ Neighbor Solicitation, NS )消息后， 没有在规定的时间内收到 Peer 1 回复的邻居广告（Neighbor Advertisement, NA ) 消息， 则 "Proxy"生成相 应的诊断码 (BFD diagnostic code), 比如 "diagnostic code =1"表明控制检测超 时 ( Control Detection Time Expired ) 、 "diagnostic code = 2" 表明功能故障 ( Echo Function Failed )或 "diagnostic code = 3" 表明 Peer 1下线 ( Neighbor Signaled Session Down ) , 然后通过 BFD消息通知 Peer2。
或者当其中一跳为 NUD而另一跳为 "BFD Session" ,下行方向， "Proxy" 负责根据第二跳的 BFD消息 "diagnostic code" 值， 在所有 "IP Session" 的 第一跳产生相应的 NUD动作。例如， 当第二跳的 BFD消息 "diagnostic code" 表明 Peer 2下线（ Neighbor Signaled Session Down )、路径下线（ Path Down )、 控制检测超时（ Control Detection Time Expired ) 、 功能故障 （ Echo Function Failed )、 转发面重启 ( Forwarding Plane Reset )或强制下线 ( Administratively Down ) , 则 "Proxy" 将通过 NUD向所有 "IP Session" 的 Peer表明邻居不 可达， 比如， "Proxy"在收到 Peer 1的邻居请求（Neighbor Solicitation; NS ) 消息后可不向 Peer 1 回复邻居广告（ Neighbor Advertisement; NA )消息， 或 "Proxy"停止向 Peer 1主动发起邻居请求 ( Neighbor Solicitation; NS )消息。
代理模式的再一种情况是如图 6所示， 图 6为本发明 IP会话存活监控方 法实施例三示意图，本实施例提供的是 HGW上设置的' 'IPv6 Session Keepalive Proxy" 釆用代理的方式实现 "Multiple hop IPv6 Session" 的存活监控， Proxy 釆用不同的 WAN口与不同的 UE或 IPv6 Session相对应；例如图 6中， WAN 口 1与用户 1对应， WAN口 n与用户 n对应。
对于 UE与 BNG之间的 "IPv6 Session" 的存活监控， HGW通过一局域 网端口接收 UE发送的 BFD或 NUD消息 , 对于 BFD消息 , 要重构下一跳的 存活监控消息， 即下一跳监控消息的源地址和目的地址均发生改变， 例如该 上行方向上是将目的地址改为 BNG的地址， 将源地址改为 HGW的地址， 具 体为将 BFD消息中的第一鉴别域值修改为用户终端 IP地址前缀相对应的值 后， 通过与所述局域网端口对应的一广域网端口将重构的包括经过修改的第 一鉴别域值的 BFD消息发送给 BNG; 对 NUD消息 , HGW接收 UE发送的 NUD消息， 重构下一跳的 BFD消息， 并向 BNG发送重构的 BFD消息。 下 行方向 , HGW通过一广域网端口接收 BNG发送的 BFD消息 , BFD消息中 的第一鉴别域值为用户终端 IP地址前缀相对应的值，重构 BFD或 NUD消息， 将 NUD消息或包括第一鉴别域值的 BFD消息通过与广域网端口对应的一局 域网端口发送给 UE。
对于 HGW与 BNG之间的 "IPv6 Session"存活监控包括 HGW接收 BNG 发送的 BFD消息 , 并根据 BFD消息中的第二鉴别域（ Discriminator域）值， 监控 HGW接收 BNG点之间的 IP会话是否存活， 第二鉴别域值设置为特殊 值，如为 "0"或 "OxFFFF"。 下行方向， BNG向 HGW发送 BFD消息， HGW 可以根据 BFD消息中的 "Discriminator"域的值判断出对应的 "BFD Session" , 便据此监控相关联的 "IP Session" 的存活状态。 BNG接收 HGW发送的 BFD 消息， 并根据 BFD消息第二鉴别域值， 监控 BNG与 HGW之间的 IP会话是 否存活。 上行方向， HGW接收 BNG发送的 BFD消息后， 可以根据 BFD消 息中的 "Discriminator" 域的值判断出对应的 "BFD Session" , 便据此监控 相关联的 "IP Session" 的存活状态。
具体地， 单跳 "IPv6 Session" 的 "Keepalive"所釆用的 "BFD Session" 以 HGW地址或 BNG地址进行" Keepalive"交互， BFD消息的 "Discriminator" 域设置为 "0" 或 "OxFFFF" 。
多跳 "IPv6 Session" 的 "IPv6 Session Keepalive"釆用两个单跳完成， 通 过 "Proxy" 中继第一跳和第二跳的 "Keepalive" 过程， 负责保持第一跳和第 二跳的 "Keepalive" 的状态同步。
其中， 第一跳釆用单跳的 "NUD/BFD Session" 进行 "keepalive" , 第二 跳釆用单跳的 "BFD Session" 进行 "keepalive" 。
第一跳釆用的单跳的 "NUD/BFD Session" 以用户的地址或 "Proxy" 地 址， 可以是 HGW 的 LAN 口地址进行 "Keepalive" 交互， BFD 消息的 "Discriminator"域设置为与 "Prefix Yn" (η=1,2,3 )相对应的值， 例如取
"Prefix Yn"的最后 32位作为 "Discriminator"域的值或取 (Yn-Z) η=1,2,3 。
其中， 第一跳， UE/HGW根据 BFD消息的 "Discriminator" 域的值将 "BFD Session" 与相应的 "IPv6 Session" 关联起来。
第二跳釆用的单跳的 "BFD Session" 以 BNG的地址或 "Proxy" 地址， 可以是 HGW 的 WAN 口地址进行 " Keepalive " 交互， BFD 消息的 "Discriminator" i或设置为与 "Prefix Yn" (n=l,2,3 )相对应的值， 例如取 "Prefix Yn "的最后 32 位作为 "Discriminator "域的值或取 ( Yn-Z ) η=1,2,3... ...。
其中， 第二跳， BNG/HGW 根据 BFD 消息的源 IP 地址 /前缀和 /或 "Discriminator "i或的值将 "BFD Session" 与相应的 "IPv6 Session" 关联起 来。 "Proxy" 釆用不同的 WAN口与不同的 UE或 "IPv6 Session" 相对应， BNG/HGW根据 BFD消息的 "Discriminator"域的值来区分不同用户的 "IPv6 Session" 。
可选地， 单跳 "BFD Session" 以 "Prefix Z" 作为 "Session" 的标识； 多跳 "BFD Session" 以 "Prefix Z" 或 "Prefix Yn" 作为 "Session" 的标识。
以图 6为例，对于 "IP Session 0 "，可以 Prefix Z标识，釆用 "BFD Session
0"以支持 "Keepalive" , BFD消息的 "Discriminator"域设置为 "0"或 "OxFFFF"； BNG/UE根据 BFD消息的源 IP地址前缀 "Prefix Z" 将 "BFD Session 0" 与 相应的 "IPv6 Session 0" 关联起来。
对于 "IP Session 1" , 可以 Prefix Yl标识， 釆用 "BFD Session 11" 和 "BFD Session 21 " 以支持 " Keepalive " , "BFD Session 21 " 消息的 "Discriminator" 域设置为（Yl-Z); BNG/HGW根据 BFD消息的源 IP地址前 缀 "Prefix Y1" 将 "BFD Session 21 " 与相应的 "IPv6 Session 1" 关联起来； HGW/UE根据 BFD消息的源 IP地址前缀 "Prefix Yl" 将 "BFD Session 11 " 与相应的 "IPv6 Session Γ 关联起来。
对于 "IP Session η，， ， 可以 Prefix Yn标识， 釆用 "BFD Session In" 和
"BFD Session 2n" 以支持 "Keepalive" , "BFD Session 2n" BFD消息的 " Discriminator " i或设置为（Yn-Z) ; " BFD Session In " BFD 消息的 "Discriminator" 域设置为 "Prefix Yn" 的最后 32位。 BNG/HGW根据 BFD 消息的源 IP地址前缀 "Prefix Yn"将 "BFD Session 2n"与相应的 "IPv6 Session n"关联起来； HGW/UE根据 BFD消息的源 IP地址前缀 "Prefix Yn"将 "BFD Session In" 与相应的 "IPv6 Session n" 关联起来。 HGW在进行检测消息转发监控 "IPv6 Session" 存活的过程中， 还要进 行会话对端的状态同步的操作， 可以包括 "Proxy" 收集 "IP Session" 其中一 跳的诊断码（ BFD diagnostic code )或 NUD状态例如邻居不可达， 在另一跳 上通过诊断码 ( BFD diagnostic code )或 NUD进行表达。
例如， 当第一跳和第二跳皆为 "BFD Session" , 则 "Proxy" 负责将其中 一跳的 BFD消息 "diagnostic code"值复制到另一跳的 BFD消息的 "diagnostic code" 域， 或者 "Proxy" 负责诊断其中一跳的会话对端 1 ( Peerl ) 的存活状 code ) , 通过 BFD消息通知会话对端 2 ( Peer2 ) 。
当其中一跳为 NUD而另一跳为 " BFD Session" , 则上行方向， "Proxy" 负责通过 NUD机制诊断第一跳会话对端 1 ( Peerl )的存活状态， 然后将第一 跳的存活状态生成相应的诊断码 ( BFD diagnostic code ) , 通过 BFD消息通 知会话对端 2 ( Peer2 )； 例如， 当 "Proxy"向 Peer 1发出邻居请求（Neighbor Solicitation, NS ) 消息后， 没有在规定的时间内收到 Peer 1 回复的邻居广告 ( Neighbor Advertisement, NA )消息， 则 "Proxy "生成相应的诊断码（BFD diagnostic code ) , 比 ^口 "diagnostic code =1 " 表明控 ll检;则超时 ( Control Detection Time Expired )、 "diagnostic code = 2"表明功能故障 ( Echo Function Failed )或 "diagnostic code = 3" 表明 Peer 1下线 ( Neighbor Signaled Session Down ) , 然后通过 BFD消息通知 Peer2。
或者当其中一跳为 NUD而另一跳为 "BFD Session" ,下行方向， "Proxy" 负责根据第二跳的 BFD消息 "diagnostic code"值，在第一跳产生相应的 NUD 动作。例如，当第二跳的 BFD消息" diagnostic code"表明 Peer 2下线（Neighbor Signaled Session Down ) 、 路径下线（Path Down ) 、 控制检测超时（Control Detection Time Expired ) 、 功能故障 ( Echo Function Failed ) 、 转发面重启 ( Forwarding Plane Reset )或强帝 J下线 ( Administratively Down ) , U'J "Proxy" 将通过 NUD向 Peer 1表明邻居不可达， 比如， "Proxy" 在收到 Peer 1的邻 居请求 （Neighbor Solicitation, NS ) 消息后可不向 Peer 1 回复邻居广告 ( Neighbor Advertisement, NA ) 消息, 或 "Proxy" 停止向 Peer 1主动发起 邻居请求 ( Neighbor Solicitation, NS ) 消息。
本发明实施例提供的 IP会话存活监控方法， 用 "Multihop BFD" 作为 "Multihop IPv6 Session"的存活监控机制，或者在 HGW上设置 "IPv6 Session Keepalive Proxy" , 从而能将 "IPv6 Session" 建立于 HGW之后的 UE与 IP 边缘节点之间， 将 "Single hop IP Session" 扩展为 "Multihop IP Session" 实 现了 "Multiple hop IPv6 Session" 的存活监控。
本领域普通技术人员可以理解： 实现上述方法实施例的全部或部分步骤 可以通过程序指令相关的硬件来完成， 前述的程序可以存储于一计算机可读 取存储介质中， 该程序在执行时， 执行包括上述方法实施例的步骤； 而前述 的存储介质包括： ROM, RAM, 磁碟或者光盘等各种可以存储程序代码的介 图 7为本发明家庭网关实施例结构示意图， 如图 7所示， 该家庭网关包 括第一接收模块 11和第一转发模块 12 , 其中第一接收模块 11用于接收用户 终端或 IP边缘节点发送的双向转发检测消息； 第一转发模块 12用于根据所 述第一接收模块接收到的双向转发检测消息， 向所述 IP边缘节点或所述用户 终端发送包括第一鉴别域值的双向转发检测消息， 所述第一鉴别域值为用户 终端 IP地址前缀与家庭网关 IP地址前缀的差值。 具体地， 第一接收模块 11 接收到 UE 或 BNG 发送的 BFD 消息， 若 BFD 消息中的第一鉴别域 ( Discriminator )值为用户终端 IP地址前缀与家庭网关 IP地址前缀的差值， 则直接向 UE或 BNG转发； 若 BFD消息中的第一鉴别域值不为用户终端 IP 地址前缀与家庭网关 IP地址前缀的差值， 则将其 ^ί'爹改为用户终端 IP地址前 缀与家庭网关 IP地址前缀的差值后， 向 UE或 BNG转发。
本实施例提供的家庭网关还包括用于修改第一接收模块 11 接收到的双 向转发检测消息中的第一鉴别域值的代理模块 13。 具体为， 作为 "Router" 的家庭网关， 为实现接入到其上的 UE与 IP边缘节点例如 BNG之间的 "IP Session" 的存活监控， 在家庭网关中增加代理功能， 通过代理实现第一跳到 第二跳的中继， 其中第一接收模块 11接收 UE或 BNG发送来的 BFD检测消 息， 代理模块 13根据实际情况将检测消息中的鉴别域值进行修改， 使其适于 在下一跳中传送， 达到存活监控的目的。 代理模块 13修改完鉴别域值后， 通 过第一转发模块 12 将包含有经过修改的家别域值的检测消息发送给下一跳 的目的端， 可以是 UE或 BNG。
本实施例提供的家庭网关还包括发送模块 14, 用于向 BNG发送包括第 二鉴别域值的检测消息， 所述第二鉴别域值为 "0" 或 "OxFFFF" , 家庭网关 通过发送模块 14实现与 BNG之间的会话存活监控。
本实施例提供的家庭网关中在 HGW 上设置 "IPv6 Session Keepalive Proxy" , 从而能将 "IPv6 Session"建立于 HGW之后的 UE与 IP边缘节点之 间，将 "Single hop IP Session"扩展为 "Multihop IP Session"实现了 "Multiple hop IPv6 Session" 的存活监控。
图 8为本发明网络设备实施例结构示意图， 如图 8所示， 该网络设备包 括第二接收模块 21和处理模块 22, 网络设备通过第二接收模块 21接收家庭 网关发送的 BFD消息， 所述 BFD消息中包括的第一鉴别域值为用户终端 IP 地址前缀与家庭网关 IP地址前缀的差值； 然后， 再通过处理模块 22根据所 述 BFD消息中的第一鉴别域值， 监控 IP边缘节点与用户终端之间的 IP会话 是否存活。 处理模块还用于根据所述双向转发检测消息中的所述第一鉴别域 值， 判断与所述第一鉴别域值对应的双向转发检测会话是否存活， 并根据所 述双向转发检测会话是否存活， 判断与所述双向转发检测会话关联的 IP会话 是否存活。
本实施例提供的网络设备可以为 UE或 BNG, 通过家庭网关发送的 BFD 消息对 UE与 BNG之间的 "IPv6 Session" 进行存活监控。
图 9为本发明 IP会话存活监控系统实施例结构示意图， 如图 9所示， 该 IP会话存活监控系统包括家庭网关 1和网络设备 2, 其中， 家庭网关 1用于 向网络设备发送双向转发检测消息， 所述双向转发检测消息中的第一鉴别域 值为用户终端 IP地址前缀与家庭网关 IP地址前缀的差值； 网络设备 2, 用于 接收所述家庭网关发送的双向转发检测消息， 根据所述双向转发检测消息中 的第一鉴别域值， 监控 IP边缘节点与用户终端之间的 IP会话是否存活。
本实施例提供的 IP会话存活监控系统中涉及的家庭网关和网络设备， 可 以釆用上述实施例中提供的家庭网关和网络设备， 此处不再赘述。
本实施例提供的 IP会话存活监控系统中， 通过在 HGW上设置 "IPv6 Session Keepalive Proxy" , 从而能将 "IPv6 Session"建立于 HGW之后的 UE 与 IP边缘节点之间， 将 "Single hop IP Session"扩展为 "Multihop IP Session" 实现了 "Multiple hop IPv6 Session" 的存活监控。
最后应说明的是： 以上实施例仅用以说明本发明的技术方案， 而非对其 限制； 尽管参照前述实施例对本发明进行了详细的说明， 本领域的普通技术 人员应当理解： 其依然可以对前述各实施例所记载的技术方案进行修改， 或 者对其中部分技术特征进行等同替换； 而这些修改或者替换， 并不使相应技 术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims

权 利 要 求 书
1、 一种 IP会话存活监控方法， 其特征在于， 包括：
用户终端或 IP边缘节点接收家庭网关发送的双向转发检测消息， 所述双 向转发检测消息中包括的第一鉴别域值为用户终端 IP地址前缀与家庭网关 IP 地址前缀的差值；
用户终端或 IP边缘节点根据所述双向转发检测消息中的第一鉴别域值， 监控所述 IP边缘节点与所述用户终端之间的 IP会话是否存活。
2、 根据权利要求 1所述的 IP会话存活监控方法， 其特征在于， 所述监 控所述 IP边缘节点与所述用户终端之间的 IP会话是否存活包括：
根据所述双向转发检测消息中的所述第一鉴别域值， 判断与所述第一鉴 别域值对应的双向转发检测会话是否存活， 并根据所述双向转发检测会话是
3、 根据权利要求 1或 2所述的 IP会话存活监控方法， 其特征在于， 所 述双向转发检测消息还包括第二鉴别域值， 所述第二鉴别域值为 "0" 或 "OxFFFF"。
4、 根据权利要求 3所述的 IP会话存活监控方法， 其特征在于， 所述方 法还包括：
所述家庭网关或所述 IP边缘节点根据所述双向转发检测消息的所述第二 鉴别域值， 监控所述 IP边缘节点与所述家庭网关之间的 IP会话是否存活。
5、 根据权利要求 1或 2所述的 IP会话存活监控方法， 其特征在于， 所 述用户终端或 IP边缘节点接收家庭网关发送的双向转发检测消息具体为： 所 述用户终端或 IP边缘节点接收所述家庭网关通过对应的广域网端口发送的双 向检测消息。
6、 根据权利要求 1或 2所述的 IP会话存活监控方法， 其特征在于， 所 述用户终端或 IP边缘节点接收家庭网关发送的双向转发检测消息之前， 所述 方法还包括： 所述家庭网关将双向转发检测消息中包括的第一鉴别域值修改为用户终 端 IP地址前缀与家庭网关 IP地址前缀的差值后， 向所述用户终端或 IP边缘 节点进行转发经过修改的所述双向转发检测消息。
7、 根据权利要求 1或 2所述的 IP会话存活监控方法， 其特征在于， 所 述方法还包括：
所述 IP边缘节点或所述用户终端接收所述家庭网关发送的携带有诊断码 的双向转发检测消息。
8、 根据权利要求 1所述的 IP会话存活监控方法， 其特征在于， 所述方 法还包括：
家庭网关接收用户终端发送的邻机不能到达检测消息， 向 IP边缘节点发 送重构的双向转发检测消息， 所述 IP边缘节点根据所述双向转发检测消息， 监控所述 IP边缘节点与所述用户终端之间的 IP会话是否存活， 所述源 IP地 址相关信息包括源 IP地址或源 IP地址前缀;或
所述家庭网关接收所述 IP边缘节点发送的双向转发检测消息， 向所述终 端发送重构的邻机不能到达检测消息,所述用户终端根据所述邻机不能到达 检测消息的源 IP地址相关信息， 监控所述 IP边缘节点与所述用户终端之间 的 IP会话是否存活，所述源 IP地址相关信息包括源 IP地址或源 IP地址前缀。
9、 根据权利要求 8所述的 IP会话存活监控方法， 其特征在于， 所述家 庭网关接收用户终端发送的邻机不能到达检测消息， 向 IP边缘节点发送重构 的双向转发检测消息， 包括：
所述家庭网关通过对应的局域网端口接收所述用户终端发送的邻机不能 到达检测消息， 通过与所述不同的局域网端口对应的一广域网端口将重构的 双向转发检测消息发送给 IP边缘节点； 或
所述家庭网关通过一局域网端口接收所述用户终端发送的邻机不能到达 检测消息， 通过与所述局域网端口对应的一广域网端口将重构的双向转发检 测消息发送给 IP边缘节点。
10、 根据权利要求 8所述的 IP会话存活监控方法， 其特征在于， 所述家 庭网关接收所述 IP边缘节点发送的双向转发检测消息， 向所述终端发送重构 的邻机不能到达检测消息， 包括：
所述家庭网关通过一广域网端口接收所述 IP边缘节点发送的双向转发检 测消息， 将重构的邻机不能到达检测消息通过与所述广域网端口对应的一局 域网端口发送给所述用户终端。
11、 根据权利要求 8或 9或 10所述的 IP会话存活监控方法， 其特征在 于， 所述方法还包括：
所述家庭网关接收所述 IP边缘节点发送的双向转发检测消息， 并根据所 述双向转发检测消息中的第二鉴别域值，监控所述家庭网关与所述 IP边缘节 点之间的 IP会话是否存活， 所述第二鉴别域值为 "0" 或 "OxFFFF" ; 或
所述 IP边缘节点接收所述家庭网关发送的双向转发检测消息， 并根据所 述双向转发检测消息的源 IP地址相关信息和 /或所述第二鉴别域值，监控所述 IP边缘节点与所述家庭网关之间的 IP会话是否存活， 所述源 IP地址相关信 息包括源 IP地址或源 IP地址前缀。
12、 根据权利要求 8或 9或 10所述的 IP会话存活监控方法， 其特征在 于， 所述方法还包括：
所述家庭网关检测所述用户终端的存活状态， 并生成诊断码， 向所述 IP 边缘节点发送包括所述诊断码的双向转发检测消息； 或
若所述家庭网关接收到所述用户终端发送的检测消息为邻机不能到达检 测消息， 则所述家庭网关根据所述 IP边缘节点发送的双向转发检测消息中的 诊断码， 执行相应的邻机不能到达检测的操作。
13、 一种家庭网关， 其特征在于， 包括：
第一接收模块， 用于接收用户终端或 IP边缘节点发送的双向转发检测消 息；
第一转发模块，用于根据所述第一接收模块接收到的双向转发检测消息， 向所述 IP边缘节点或所述用户终端发送包括第一鉴别域值的双向转发检测消 息， 所述第一鉴别域值为用户终端 IP地址前缀与家庭网关 IP地址前缀的差 值。
14、 根据权利要求 13所述的家庭网关， 其特征在于， 还包括：
代理模块， 用于将所述第一接收模块接收到的双向转发检测消息修改为 包括所述第一鉴别域值的双向转发检测消息。
15、 根据权利要求 13所述的家庭网关， 其特征在于， 还包括发送模块， 用于向所述 IP边缘节点发送包括第二鉴别域值的检测消息，所述第二鉴别域 值为 "0" 或 "0xFFFF"。
16、 根据权利要求 14所述的家庭网关， 其特征在于，
所述代理模块，还用于收集 IP会话其中一跳的的诊断码或邻机不能到达 检测状态，在所述 IP会话的另一跳中通过双向转发检测消息发送给会话对端。
17、 一种网络设备， 其特征在于， 包括：
第二接收模块， 用于接收家庭网关发送的双向转发检测消息， 所述双向 转发检测消息中包括的第一鉴别域值为用户终端 IP地址前缀与家庭网关 IP 地址前缀的差值；
处理模块， 用于根据所述双向转发检测消息中的第一鉴别域值， 监控所 述 IP边缘节点与所述用户终端之间的 IP会话是否存活。
18、 根据权利要求 17所述的网络设备， 其特征在于， 所述处理模块还用 于根据所述双向转发检测消息中的所述第一鉴别域值， 判断与所述第一鉴别 域值对应的双向转发检测会话是否存活， 并根据所述双向转发检测会话是否
19、 一种 IP会话存活监控系统， 其特征在于， 包括：
家庭网关， 用于向网络设备发送双向转发检测消息， 所述双向转发检测 消息中的第一鉴别域值为用户终端 IP地址前缀与家庭网关 IP地址前缀的差 值；
网络设备， 用于接收所述家庭网关发送的双向转发检测消息， 根据所述 双向转发检测消息中的第一鉴别域值， 监控所述 IP边缘节点与所述用户终端 之间的 IP会话是否存活。
20、 根据权利要求 19所述的 IP会话存活监控系统， 其特征在于， 所述 网络设备还用于根据所述双向转发检测消息中的所述第一鉴别域值， 判断与 所述第一鉴别域值对应的双向转发检测会话是否存活， 并根据所述双向转发
PCT/CN2010/070161 2009-01-21 2010-01-13 Ip会话存活监控方法及系统、家庭网关和网络设备 WO2010083739A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
AT10733212T ATE557497T1 (de) 2009-01-21 2010-01-13 Verfahren und system zur überwachung der stabilität von ip-sitzungen sowie heim-gateway und netzwerkausrüstung dafür
KR1020117018476A KR101245786B1 (ko) 2009-01-21 2010-01-13 Ｉｐ 세션 킵얼라이브 모니터링을 위한 방법 및 시스템, 홈 게이트웨이, 및 네트워크 장치
JP2011546574A JP5118257B2 (ja) 2009-01-21 2010-01-13 Ｉｐセッションキープアライブ監視方法およびシステム、ホームゲートウェイ、ならびにネットワーク装置
ES10733212T ES2384162T3 (es) 2009-01-21 2010-01-13 Método y sistema de vigilancia de la vivacidad de sesiones IP, pasarela doméstica y equipo de red
EP10733212A EP2383934B1 (en) 2009-01-21 2010-01-13 Ip session liveness monitoring method and system, home gateway and network equipment
US13/187,972 US8331245B2 (en) 2009-01-21 2011-07-21 Method and system for IP session keepalive monitoring, home gateway and network device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2009100019971A CN101783773B (zh) 2009-01-21 2009-01-21 Ip会话存活监控方法及系统、家庭网关和网络设备
CN200910001997.1 2009-01-21

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/187,972 Continuation US8331245B2 (en) 2009-01-21 2011-07-21 Method and system for IP session keepalive monitoring, home gateway and network device

Publications (1)

Publication Number Publication Date
WO2010083739A1 true WO2010083739A1 (zh) 2010-07-29

Family

ID=42355536

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/070161 WO2010083739A1 (zh) 2009-01-21 2010-01-13 Ip会话存活监控方法及系统、家庭网关和网络设备

Country Status (8)

Country Link
US (1) US8331245B2 (zh)
EP (1) EP2383934B1 (zh)
JP (1) JP5118257B2 (zh)
KR (1) KR101245786B1 (zh)
CN (1) CN101783773B (zh)
AT (1) ATE557497T1 (zh)
ES (1) ES2384162T3 (zh)
WO (1) WO2010083739A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013500653A (ja) * 2010-10-08 2013-01-07 ▲ホア▼▲ウェイ▼技術有限公司 情報を提供するための方法、ホームゲートウェイおよびホームネットワークシステム
CN111355764A (zh) * 2018-12-24 2020-06-30 迈普通信技术股份有限公司 保活报文发送方法、装置、电子设备及可读存储介质

Families Citing this family (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101945020A (zh) * 2010-09-14 2011-01-12 中兴通讯股份有限公司 会话监控处理方法和监控设备
EP3282733A1 (en) * 2012-03-01 2018-02-14 Interdigital Patent Holdings, Inc. Method and apparatus for supporting dynamic and distributed mobility management
US9083650B2 (en) 2012-10-16 2015-07-14 Cable Television Laboratories, Inc. Overlay network
WO2014075213A1 (zh) * 2012-11-13 2014-05-22 华为技术有限公司 双向转发检测bfd会话协商方法、设备及系统
CN103067220B (zh) * 2012-12-19 2016-02-10 中兴通讯股份有限公司 参数更新情况下双向链路转发检测方法及装置
US9185170B1 (en) 2012-12-31 2015-11-10 Juniper Networks, Inc. Connectivity protocol delegation
US9602367B2 (en) * 2013-03-15 2017-03-21 Teoco Corporation System, method, and computer program product for creating a header detail record
WO2014179508A1 (en) * 2013-04-30 2014-11-06 Seven Networks, Inc. Detection and reporting of keepalive messages for optimization of keepalive traffic in a mobile network
WO2014194333A1 (en) 2013-05-31 2014-12-04 Seven Networks, Inc. Optimizing traffic by controlling keep-alives
US9497107B1 (en) * 2013-06-06 2016-11-15 Cisco Technology, Inc. Seamless path monitoring and rapid fault isolation using bidirectional forwarding detection in a network environment
WO2017210208A1 (en) * 2016-05-31 2017-12-07 Brocade Communications Systems, Inc. Keepalive technique in a network device
US10476774B2 (en) * 2016-08-31 2019-11-12 Juniper Networks, Inc. Selective transmission of bidirectional forwarding detection (BFD) messages for verifying multicast connectivity
US10541904B2 (en) 2016-12-14 2020-01-21 Hewlett Packard Enterprise Development Lp Establishing a network fault detection session
CN107733931B (zh) * 2017-11-30 2021-03-09 新华三技术有限公司 入口认证方法、装置及入口服务器
CN111614505B (zh) * 2019-02-25 2022-02-25 华为技术有限公司 报文处理的方法和网关设备
US10855813B1 (en) * 2019-07-01 2020-12-01 EMC IP Holding Company LLC Controlled activation of performance monitoring component of network protocol
US10958769B2 (en) * 2019-07-01 2021-03-23 EMC IP Holding Company LLC Activation of performance monitoring component of network protocol based on network metrics
CN110753002B (zh) * 2019-09-29 2023-04-07 北京浪潮数据技术有限公司 流量调度方法及装置
CN112995353B (zh) * 2019-12-17 2022-10-21 北京白帽汇科技有限公司 基于流量分析的IPv6地址存活性扫描系统及扫描方法
CN111654407B (zh) * 2020-04-14 2022-05-27 新华三信息安全技术有限公司 一种堆叠系统及其双向转发检测方法
US11700178B2 (en) 2020-10-30 2023-07-11 Nutanix, Inc. System and method for managing clusters in an edge network
US11374807B2 (en) 2020-10-30 2022-06-28 Nutanix, Inc. Handling dynamic command execution in hybrid cloud environments
US11290330B1 (en) 2020-10-30 2022-03-29 Nutanix, Inc. Reconciliation of the edge state in a telemetry platform
CN113595599B (zh) * 2021-09-30 2021-12-10 华东交通大学 面向5g的群簇协作通信异构系统和干扰抑制的方法
US11765065B1 (en) 2022-03-23 2023-09-19 Nutanix, Inc. System and method for scalable telemetry

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070073891A1 (en) * 2005-09-29 2007-03-29 Cisco Technology, Inc. MGCP fallback mechanism enhancement
WO2008067760A1 (en) * 2006-12-05 2008-06-12 Huawei Technologies Co., Ltd. Method and system for distributed architecture for monitoring session liveness
CN101304367A (zh) * 2007-05-11 2008-11-12 华为技术有限公司 订户会话的存活监控方法、系统及装置
CN101312456A (zh) * 2007-05-21 2008-11-26 华为技术有限公司 对订户会话进行存活监控的方法及系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6628671B1 (en) * 1999-01-19 2003-09-30 Vtstarcom, Inc. Instant activation of point-to point protocol (PPP) connection using existing PPP state
US7277453B2 (en) * 2003-05-30 2007-10-02 Motorola, Inc. Inter private network communications between IPv4 hosts using IPv6
US7526556B2 (en) * 2003-06-26 2009-04-28 International Business Machines Corporation Method and apparatus for managing keepalive transmissions
JP4681049B2 (ja) * 2005-06-14 2011-05-11 テレフオンアクチーボラゲット エル エム エリクソン（パブル） ネットワークにおける障害処理のための方法および装置
US7860981B1 (en) * 2006-09-29 2010-12-28 Juniper Networks, Inc. Systems and methods for IP session keepalive using BFD protocols
US8374164B2 (en) * 2007-04-06 2013-02-12 Cisco Technology, Inc. Detection of specific BFD path failures
JP2009016905A (ja) * 2007-06-29 2009-01-22 Fujitsu Ltd パケットネットワークシステム

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070073891A1 (en) * 2005-09-29 2007-03-29 Cisco Technology, Inc. MGCP fallback mechanism enhancement
WO2008067760A1 (en) * 2006-12-05 2008-06-12 Huawei Technologies Co., Ltd. Method and system for distributed architecture for monitoring session liveness
CN101304367A (zh) * 2007-05-11 2008-11-12 华为技术有限公司 订户会话的存活监控方法、系统及装置
CN101312456A (zh) * 2007-05-21 2008-11-26 华为技术有限公司 对订户会话进行存活监控的方法及系统

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013500653A (ja) * 2010-10-08 2013-01-07 ▲ホア▼▲ウェイ▼技術有限公司 情報を提供するための方法、ホームゲートウェイおよびホームネットワークシステム
US8606937B2 (en) 2010-10-08 2013-12-10 Huawei Technologies Co., Ltd. Information providing method, home gateway, and home network system
CN111355764A (zh) * 2018-12-24 2020-06-30 迈普通信技术股份有限公司 保活报文发送方法、装置、电子设备及可读存储介质
CN111355764B (zh) * 2018-12-24 2023-10-24 迈普通信技术股份有限公司 保活报文发送方法、装置、电子设备及可读存储介质

Also Published As

Publication number Publication date
JP2012516084A (ja) 2012-07-12
ES2384162T3 (es) 2012-07-02
EP2383934B1 (en) 2012-05-09
US8331245B2 (en) 2012-12-11
KR20110104551A (ko) 2011-09-22
EP2383934A4 (en) 2011-11-02
US20110280134A1 (en) 2011-11-17
CN101783773B (zh) 2013-01-09
EP2383934A1 (en) 2011-11-02
CN101783773A (zh) 2010-07-21
ATE557497T1 (de) 2012-05-15
JP5118257B2 (ja) 2013-01-16
KR101245786B1 (ko) 2013-03-20

Similar Documents

Publication Publication Date Title
WO2010083739A1 (zh) Ip会话存活监控方法及系统、家庭网关和网络设备
US9832168B2 (en) Service discovery within multi-link networks
KR101313831B1 (ko) 모바일 가상 사설망 통신을 위한 방법, 장치 및 시스템
JP5421392B2 (ja) 宅内ネットワーク内におけるプロキシモバイルＩＰｖ６のサポート
JP4487948B2 (ja) パケット送信方法、中継ノード、および受信ノード
EP2401873B1 (en) Ipv6 anycast-based load balancing and redirection functionality for pmipv6
US11153207B2 (en) Data link layer-based communication method, device, and system
WO2006058206A2 (en) A method of subnet roaming within a network
JP5519710B2 (ja) データリンク層のための最大送信単位（ｍｔｕ）サイズ検出メカニズムおよび方法
WO2011137842A1 (zh) 一种基于cgn实体的数据传输方法、cgn实体、网关及系统
WO2014116148A1 (en) Methods and arrangements for checking connectivity and detecting connectivity failure
WO2009071030A1 (fr) Procédé pour rapporter des informations de dispositif, système et dispositif pour obtenir des informations de dispositif
EP3337121B1 (en) Networking bonding by a mobile communication device
Kärkkäinen et al. Enabling ad-hoc-style communication in public wlan hot-spots
JP5857222B2 (ja) 無線ネットワークシステム、無線通信装置、及び、無線通信装置のプログラム
US10367732B2 (en) Route control for internet exchange point
WO2014090194A1 (zh) 终端设备的拨号方法和接入设备
JP5889122B2 (ja) 制御ノード及び通信制御方法
JP3613207B2 (ja) Ａｒｐテーブル形成方法及びこれを用いた経路制御方法
CN106452992A (zh) 一种远端多归属组网的实现方法及装置
Chen et al. OSPFv3 over IPv4 for IPv6 Transition
Chen et al. RFC 7949: OSPFv3 over IPv4 for IPv6 Transition
Proto et al. The olsr mdns extension for service discovery
Shah et al. Address Resolution Protocol (ARP) Mediation for IP Interworking of Layer 2 VPNs
Kompella Internet Engineering Task Force (IETF) H. Shah, Ed. Request for Comments: 6575 Ciena Category: Standards Track E. Rosen, Ed.

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: 10733212

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2011546574

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2010733212

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 3191/KOLNP/2011

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 20117018476

Country of ref document: KR

Kind code of ref document: A