WO2016091009A1 - 一种地址分配、获取方法及装置 - Google Patents

一种地址分配、获取方法及装置 Download PDF

Info

Publication number
WO2016091009A1
WO2016091009A1 PCT/CN2015/092106 CN2015092106W WO2016091009A1 WO 2016091009 A1 WO2016091009 A1 WO 2016091009A1 CN 2015092106 W CN2015092106 W CN 2015092106W WO 2016091009 A1 WO2016091009 A1 WO 2016091009A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
host
address
identity
location identifier
Prior art date
Application number
PCT/CN2015/092106
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 电信科学技术研究院
Publication of WO2016091009A1 publication Critical patent/WO2016091009A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/45Network directories; Name-to-address mapping
    • H04L61/4505Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • H04L61/5007Internet protocol [IP] addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • H04L61/5046Resolving address allocation conflicts; Testing of addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/16Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/26Resource reservation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/11Allocation or use of connection identifiers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08Mobility data transfer
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00Indexing scheme associated with group H04L61/00
    • H04L2101/60Types of network addresses
    • H04L2101/618Details of network addresses
    • H04L2101/659Internet protocol version 6 [IPv6] addresses

Definitions

  • the present invention relates to the field of network communication technologies, and in particular, to an address allocation and acquisition method and apparatus.
  • IP Internet Protocol
  • the routing and forwarding of packets has dual semantics. This dual semantics has significant limitations in supporting host mobility.
  • MIP Mobile IP Protocol
  • the global IPv4 address is about to run out, and the IPv6 address will be the core address resource of the future Internet. Therefore, there is a need for a technology that can separate the identity attribute and the location attribute of the IPv6 address, and solve the problem of IPv6 address support for mobility.
  • An embodiment of the present invention provides an address allocation and acquisition method, and an apparatus for determining an identity identifier and a location identifier by setting an address type flag bit in an IPv6 address to distinguish whether the IPv6 address is a host identity identifier or a host location identifier. Separation, supporting the continuity of host communication during the move.
  • An embodiment of the present invention provides an address allocation method, including:
  • the receiving network access request includes:
  • the mobile anchor receiving node sends a host identity assignment request, and the node belongs to the mobility anchor point;
  • the assigning the host identity to the node according to the network access request includes:
  • the mobility anchor assigns a host identity to the node according to the identity identifier allocation request, and the host identity of the node is carried in a response message to the node, and the host identity of the node is simultaneously The host location identifier of the node is used;
  • the host identity identifier that is to be allocated to the node, including:
  • the mobility anchor sends the host identity assigned to the node to the home domain mapping server of the node, and indicates that the home domain mapping server of the node stores the host identity and the host location identifier of the node, where The host location identifier of the node is the same as the host identity of the node.
  • the receiving network access request includes:
  • the mobile anchor receives an access request sent by the node, and the node is not attributed to the mobility anchor point;
  • the assigning a host location identifier to the node according to the network access request includes:
  • the mobility anchor assigns a host location identifier to the node according to the access request
  • the mobility anchor sends the host location identifier assigned to the node to the home domain mapping server of the node, and indicates that the home domain mapping server of the node specifies the host location identifier corresponding to the host identity of the node. Updated to the currently assigned host location ID.
  • the method further includes:
  • the query response carries an Internet Protocol IP address of the home domain mapping server of the node that is queried by the DNS according to the domain name of the management domain in the global host name of the node.
  • the assigning the host identity to the node according to the network access request includes:
  • the assigning a host location identifier to the node according to the network access request includes:
  • the number of the first address type identifiers pre-allocated in the address pool of the host identity identifier and the number of the second address type identifiers pre-allocated in the address pool of the host location identifier are set according to a set ratio.
  • a reserved address pool is further configured, where the reserved address pool includes a host identity identifier and a host location identifier, where the number of pre-allocated first address type flags and the second address type flag in the reserved address pool The number is set according to the set ratio;
  • the method also includes:
  • the first address type flag or the second address type flag is carried in an address type field of the IPv6 address.
  • An address obtaining method is provided in the embodiment of the present invention, where the method includes:
  • the obtaining, by the global host name of the node, the host identity and the host location identifier of the node including:
  • the DNS Receiving a first query response returned by the DNS, where the first query response carries an Internet Protocol IP address of the domain mapping server that is queried by the DNS according to the domain name of the management domain in the global host name of the node;
  • the global host name of the acquiring node includes:
  • the method further includes:
  • An embodiment of the present invention provides an address allocation apparatus, including:
  • a receiving unit configured to receive a network access request
  • An allocating unit configured to allocate a host identity or a host location identifier to the node that requests the access according to the network access request; wherein the host identity and the host location identifier are both IPv6 addresses, and serve as a host identity
  • the IPv6 address contains the first address type flag, and the IPv6 address that is the host location identifier contains the second address.
  • Type flag
  • a maintenance unit configured to send a host identity or a host location identifier allocated to the node to a home domain mapping server of the node, so that the home domain mapping server of the node maintains a host identity and a host of the node The correspondence between location identifiers.
  • the receiving unit is specifically configured to: receive a host identity assignment request sent by the node, where the node belongs to the mobility anchor point;
  • the allocating unit is configured to: allocate a host identity to the node according to the identity identifier allocation request, and use the host identity of the node as a host location identifier of the node;
  • the identity identifier is carried in the response message and sent to the node;
  • the maintenance unit is specifically configured to: send a host identity identifier allocated to the node to a home domain mapping server of the node, and instruct the home domain mapping server of the node to store a host identity identifier and a host location of the node An identifier, wherein the host location identifier of the node is the same as the host identity of the node.
  • the receiving unit is specifically configured to: receive an access request sent by the node, where the node is not attributable to the mobility anchor point;
  • the allocating unit is configured to: allocate a host location identifier to the node according to the access request;
  • the maintenance unit is specifically configured to: send a host location identifier allocated to the node to a home domain mapping server of the node, and instruct the home domain mapping server of the node to correspond to a host identity identifier of the node
  • the host location ID is updated to the currently assigned host location ID.
  • the maintenance unit is further configured to: send a query request to the domain name system DNS, where the query request carries a global host name of the node;
  • the query response carries an Internet Protocol IP address of the home domain mapping server of the node that is queried by the DNS according to the domain name of the management domain in the global host name of the node.
  • the allocating unit is configured to: select, according to the network access request, a host identity identifier from the address pool of the host identity for the node; or, according to the network access request, identify the host location Select a host location identifier for the node in the address pool;
  • the number of the first address type identifiers pre-allocated in the address pool of the host identity identifier and the number of the second address type identifiers pre-allocated in the address pool of the host location identifier are set according to a set ratio.
  • a reserved address pool is further configured, where the reserved address pool includes a host identity identifier and a host location identifier, where the number of pre-allocated first address type flags and the second address type flag in the reserved address pool The number is set according to the set ratio;
  • the adjusting unit is further configured to: add the first address type flag reserved in the reserved address pool to the address pool of the host identity, and/or reserve the reserved address pool The second address type flag is added to the address pool of the host location ID.
  • the first address type flag or the second address type flag is carried in an address type field of the IPv6 address.
  • An embodiment of the present invention provides an address obtaining apparatus, where the apparatus includes:
  • a first obtaining unit configured to acquire a global host name of the node
  • a second acquiring unit configured to acquire, according to the global host name of the node, a host identity and a host location identifier of the node; the host identity and the host location identifier are both IPv6 addresses, and are used as host identifiers.
  • the IPv6 address includes a first address type flag, and the IPv6 address that is the host location identifier includes a second address type flag, and the first address type flag and the second address type flag have different value spaces.
  • the second obtaining unit has:
  • the DNS Receiving a first query response returned by the DNS, where the first query response carries an Internet Protocol IP address of the domain mapping server that is queried by the DNS according to the domain name of the management domain in the global host name of the node;
  • the first acquiring unit is specifically configured to: receive a communication establishment request sent by the calling node, and acquire a global host name of the called node carried in the communication establishment request;
  • a sending unit configured to send, after the second obtaining unit acquires the host identity and the host location identifier of the called node according to the global host name of the called node, send the host identity of the calling node to The called node sends the host identity of the called node to the calling node, so as to establish a communication connection between the called node and the calling node.
  • the host identity and the host location identifier of the node are both IPv6 addresses, and the IPv6 address that is the host identity identifier includes the first address type identifier, and the IPv6 address that is the host location identifier includes the second address type identifier. Therefore, the IPv6 address grammatically supports mobility from its own, and also solves the problem of dual semantics of IP addresses.
  • FIG. 1 is a schematic diagram of a global unicast address format in the prior art
  • FIG. 2 is a schematic diagram of an IPv6 address allocation method according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of an address allocation method according to an embodiment of the present disclosure.
  • FIG. 4 is a flowchart of a mapping analysis method in an address allocation method according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a method for a node to access a home domain mobile anchor point according to an embodiment of the present invention
  • FIG. 6 is a schematic flowchart of a method for a node to access a mobile domain anchor point according to an embodiment of the present invention
  • FIG. 7 is a schematic diagram of a method for parsing two mappings according to an embodiment of the present invention.
  • FIG. 8 is a schematic flowchart of a method for parsing two mappings according to an embodiment of the present invention.
  • FIG. 9 is a schematic flowchart of a method for establishing a communication connection between a node 1 and a node 2 according to an embodiment of the present invention.
  • FIG. 10 is a schematic flowchart of a method for a node 1 to initiate communication to a node 2 according to an embodiment of the present invention
  • FIG. 11 is a schematic flowchart of a method for changing a host location identifier of a node 1 during a communication process between a node 1 and a node 2 according to an embodiment of the present invention
  • FIG. 12 is a schematic diagram of an address allocation apparatus according to an embodiment of the present invention.
  • FIG. 13 is a schematic diagram of an address obtaining apparatus according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic diagram of another address allocation apparatus according to an embodiment of the present invention.
  • FIG. 15 is a schematic diagram of another address obtaining apparatus according to an embodiment of the present invention.
  • the operator After obtaining the N/IPv6 prefix address block from the upper-level RIR/ISP (Regional Internet Register/Internet Service Provider), the operator can follow the deployment plan, load status, etc. in the IPv6 address.
  • the prefix address block is reasonably encoded before allocation, where N is the prefix length.
  • the global route prefix refers to the prefix value assigned to a site, which is a subnet or a cluster of links; the intranet subnet refers to an identifier that identifies a subnet or link in the site.
  • T bits are taken out from the IPv6 address, and the T-bit is used to set the address type flag, which is used to identify whether the IPv6 address is used as the host identity identifier for allocation. Assigned as a host location identifier.
  • the address type flag can be set by fetching consecutive T bits from the prefix address block in the IPv6 address.
  • the host identity identifier is used to uniquely identify a host, and together with the port number, constitutes an access point of the host transport layer; the host home domain access router is allocated, globally unique, and is fixed during the lifetime of the host; in the home network The host identity can be globally routed.
  • the host location identifier is used as the basis for determining the link where a host is located. It is also the basis for the router to determine where the packet is forwarded.
  • the network access router is dynamically allocated by the visited network and changes according to the network access point where the host is located. The host location identifier can be changed. Global routing.
  • FIG. 2 shows a specific division format of an IPv6 address according to an embodiment of the present invention.
  • IPv6 address is divided into n ratio A special "global route prefix” field, an "intra-subnet” field of (64 minus n) bits, and a 64-bit "interface identifier” field.
  • the "in-site subnet” field is used to carry an identifier that identifies a subnet or link in the site, occupying C bits; the "interface identifier” field is used to carry the interface identifier, and the interface identifier remains in the standard global The format of the interface identifier in the unicast address, occupying 64 bits.
  • the "Global Routing Prefix” field is divided into three parts: the "Access Address” field, the "Address Type” field, and the "Site Code” field.
  • the access address field carries the access address, and the length of the domain is the length N of the prefix address block allocated by the RIR/ISP.
  • the access address refers to the N/prefix address block that the operating entity has obtained and filed from the upper-level RIR/ISP. For example, the address blocks of the three major operators, education network, and technology network are recorded.
  • Site Encoding field carries the site code, which is S bits long, S ⁇ 1.
  • Site coding is a site-level coding, that is, an identifier used to identify each site under an operating entity.
  • the address type field carries the address type flag.
  • the length of the field is T bits.
  • the value of T is related to the access address, site code, intranet subnet, and length of the interface identifier. It can be determined by the carrier according to its own load.
  • the address type flag includes a first address type flag and a second address type flag, wherein when the host identity is assigned to the node, the assigned host identity includes the first address type flag; when the node is assigned the host location identifier, The allocated host location identifier includes a second address type flag; the first address type flag and the second address type flag have different values, so that the IPv6 address space vertical block decoupling can be implemented.
  • the first address type flag may have a value of 1000
  • the second address type flag may have a value of 1100.
  • the embodiment of the present invention may configure the number of first address type flags for the site according to the ratio of the number of mobile nodes and fixed nodes included in the site. Or a range of values, and a number or range of values for configuring the second address type flag, thereby setting a ratio of the number of assignable host identities to the number of assignable host location identities.
  • an operating entity has a 32/IPv6 prefix block with two sites: site A and site B.
  • Site A's default load is 1.5 times that of site B. It is assumed that the fixed node of site A has more mobile nodes than non-hotspots; there are more mobile nodes in site B than fixed nodes, and the inflow and outflow of mobile nodes are relatively equal.
  • the length of the "access address” is the length of the prefix block allocated by the operating entity, so it is 32 bits, and its specific value is represented by N; the "address type flag” is set to After the address is entered, it is set to 4 bits (that is, the 32th to 35th bits of the IPv6 address are set to the address type flag), and the 4-bit address type flag has 16 values.
  • the "Site Encoding” is S bits in length
  • the 64-bit IPv6 address is "Interface Identifier", which is represented by LID.
  • the value of the first address type flag is 0000 to 0111 (0000, 0001, 0010, 0011, 0100, 0101, 0110, 0111). There are 8 values.
  • Configure the second address type flag to be in the range of 1000 to 1011 (1000, 1001, 1010, and 1011). 4 values.
  • the ratio of the number of pre-allocated first address type flags in this operator to the number of pre-allocated second address type flags is 2:1. From this it can be concluded that the ratio of the number of assignable host identities to the number of assignable host location identities is 2:1.
  • a reserved address pool is set, and an address in the reserved address pool can serve as a host, in order to dynamically adjust the proportion of the assignable host identity and/or the host location identifier according to the change of the node in the site.
  • the identity can also be used as the host location identifier.
  • the assignable host identity needs to be adjusted, the first address type flag reserved in the reserved address pool is added to the address pool of the host identity; when the assignable host location identifier needs to be adjusted, the reserved address is reserved.
  • the second address type reserved in the pool is added to the address pool identified by the host location.
  • the part of the IPv6 address reserved in the reserved address pool may be used as the first address type flag, and another reserved part of the IPv6 address may be used as the second address type flag.
  • the reserved first address type flag in the reserved address pool may be added to the address pool of the host identity, and when the assignable host location identifier needs to be adjusted, the The reserved second address type flag in the reserved address pool is added to the address pool of the host location identifier.
  • the number of assignable IPv6 addresses in the address pool of the host identity may be adjusted, or the number of assignable IPv6 addresses in the address pool of the host location identifier may be adjusted.
  • the ratio of the number of IPv6 addresses corresponding to the first address type flag in the reserved address pool and the number of IPv6 addresses corresponding to the second address type flag may also be adjusted.
  • the number of pre-assigned host identifiers in the address pool of the host identity identifier and the pre-allocated host location identifier in the address pool of the host location identifier are set according to the ratio m: 1, the first address in the address pool is reserved.
  • the type flag corresponds to the number of IPv6 addresses and the number of IPv6 addresses corresponding to the second address type flag. It can also be set according to m:1. In this way, the new host identity and host location identity of the site extension can be aggregated as much as possible.
  • some values in the value range of the address type flag may also be used as the reserved value in the embodiment of the present invention, and the reserved values are not used as the first address type flag or its reserved value.
  • the reserved value is not obtained as the second address type flag, but is reserved for use in future function extensions.
  • Table 1 shows the address type identifiers configured for site A and site B, as well as the host identity address pool and host location identifier address pool.
  • the number of fixed nodes in the site A is relatively large. Therefore, the total number of host IDs in the host identity pool allocated for site A is about the host location ID in the host location ID pool. Three times the total amount.
  • the first address type flag assigned to site A includes: 0000, 0001, 0010; the address that can be allocated in the address pool of the host identity is represented as: N 0000 S C LID, N 0001 S C LID, N 0010 S C LID .
  • the second address type flag assigned to site A includes: 1000; the address that can be allocated in the address pool of the host location identifier is represented as: N 1000 S C LID.
  • the ratio of the host identity and the pre-allocated host location identifier pre-assigned to the site A in the reserved address pool is the aggregation of the new host identity and the host location identifier collected by the siteA in the future.
  • the pre-assigned host ID in the address pool is the same as the pre-allocated host location ID in the address pool of the host location ID.
  • the address types reserved for site A include: 0011, 0100, 0101, 1001.
  • the first address type flag in the reserved pool corresponds to an IPv6 address including N 0011 S C LID, N 0100 S C LID, N 0101 S C LID; the IPv6 address corresponding to the second address type flag in the reserved pool is: N 1001 S C LID.
  • the host identity and host location identifier can be assigned to site B by 1:1.
  • the first address type identifier assigned to the site B includes: 0110; the address that can be allocated in the address pool of the host identity identifier is represented as: N 0110 S C LID.
  • the second address type flag assigned to site B includes: 1010; the address assignable in the address pool of the host location identifier is represented as: N 1010 S C LID.
  • the ratio of the host identity and the pre-allocated host location identifier pre-allocated for the site B in the reserved address pool to the host identity and the host location identifier are aggregated as much as possible for the siteB extension.
  • the pre-assigned host ID in the address pool is the same as the pre-allocated host location ID in the address pool of the host location ID.
  • the address type reserved for the site B is: 0111, 1011.
  • the IPv6 address corresponding to the first address type flag in the reserved pool is: N 0111 S C LID; the IPv6 address corresponding to the second address type flag in the reserved pool is :N 1011 S C LID.
  • the operator also retains a part of the address type flag, and does not make a specific host identity and the main
  • the setting of the machine location identifier can use the reserved value as the state extension code of the host identity or the host location, and adjust or extend the allocation ratio of the host identity and the host location identifier of the operator as a whole.
  • 1100 to 1111 are reserved values, where N 1100 S C LID, N1101 S C LID, N 1110 S C LID, and N 1111 S C LID can be used for the host location.
  • Identity assignments can also be used for host identity assignments.
  • the embodiment of the present invention sets an IPv6 address type flag in a range allowed by the IPv6 division standard, where the address type flag includes a first address type flag and a second address type flag; the first address type flag indicates The IPv6 address can be assigned as a host identity flag, and the second address type flag indicates that the IPv6 address can be assigned as a host location identifier.
  • the determining of the value space of the first address type flag and the second address type flag, and the ratio of the first address type flag and the second address type flag may be flexibly set and dynamically adjusted according to the site situation, and the first address
  • the ratio of the type flag and the second address type flag can also be flexibly adjusted according to the ratio of the mobile node to the fixed node, so that the IPv6 address grammatically supports mobility from the self-division, and also solves the problem of dual semantics of the IP address.
  • an embodiment of the present invention further provides an address allocation method.
  • FIG. 3 is a schematic flowchart diagram of an address allocation method according to an embodiment of the present invention. This process can be performed by a mobile anchor.
  • the mobility anchor is deployed at the edge router level in the access network.
  • the process can include:
  • Step 101 Receive a network access request.
  • Step 102 Assign a host identity identifier or a host location identifier to the node requesting access according to the network access request.
  • the host identity identifier and the host location identifier are both IPv6 addresses, and the IPv6 address that is the host identity identifier includes the first address type identifier, and is the IPv6 of the host location identifier.
  • the address contains the second address type flag.
  • Step 103 Send a host identity or a host location identifier assigned to the node to the home domain mapping server of the node, so that the home domain mapping server of the node maintains a host identity and a host location identifier of the node. Correspondence between them.
  • the nodes in the above process may be mobile nodes or fixed nodes.
  • the IP address of the domain mapping server of the home domain of the node may be first queried. That is, the domain name of the domain name of the management domain in the GH (Global-Hostname) is queried by the DNS to obtain the IP address of the DMS (Domain Mapping Server) of the node's home domain.
  • the domain name of the domain name of the management domain in the GH Global-Hostname
  • the DNS Domain Mapping Server
  • step 102 is as shown in FIG. 4, and may include:
  • Step 1021 Send a query request to a DNS (Domian Name System), where the query request carries the domain name of the management domain of the node, and further, the domain name of the management domain and the local host name form a global host name.
  • DNS Domain Name System
  • the global host name is used to uniquely identify a user (individual or organization), and the user applies to the authority for obtaining, and can be bound to the real identity information of the user, and the form conforms to the definition of Fully Qualified Domain Name (FQDN), and the present invention
  • the abbreviated form is the domain name DN (Domain Name) @ local host name LH (Local Hostname) (ie LH@DN).
  • LH can reflect the user's real identity information
  • GH is the domain name of the home domain where the host is located.
  • Step 1022 Receive a query response returned by the DNS, where the query response carries an IP address of the home domain mapping server of the node that is queried by the DNS according to the domain name of the management domain in the GH of the node.
  • the DNS (but not limited to the DNS) is used to perform a parsing and query service for different administrative domains, and the mapping of the DMS Internet IP address is implemented.
  • each management domain In order to be compatible with the existing domain name resolution system, each management domain only needs to register the mapping entry ⁇ admin domain domain name, DMS IP> to the DNS, and no longer registers with the host as the domain name, host IP address. Map entry. According to the domain name information of the management domain in the GH, the IP address of the primary service DMS in the management domain can be obtained and returned.
  • the embodiment of the present invention can greatly reduce the size of DNS mapping entries.
  • the types of network access requests sent by the nodes are different because the locations of the nodes are different. That is to say, the network access request received by the mobility anchor may be a network access request sent by a node of the home domain, or may be a network access request sent by a node of the visited domain.
  • the process may include:
  • Step 201 The node sends a request to the home domain mobility anchor to send a host identity. Since the node is the first time to access the home domain mobility anchor, it needs to first send a request to the home domain mobility anchor to allocate the host identity.
  • a host identity address pool and a host location identifier address pool are set in each home domain.
  • the address pool may be set on the mobility anchor point in the home domain, or may be set on the server in the home domain.
  • the embodiment of the present invention does not limit the specific setting of the address pool in the home domain.
  • Step 202 The home domain mobility anchor assigns a host identity to the node.
  • the home domain mobility anchor After the home domain mobility anchor receives the request for the node to send the host identity, the home domain mobility anchor requests a host identity from the host identity address pool for the node, and the host that is requested by the node The identity is returned to the node. Because the node is in the home domain network, the home domain mobility anchor can be globally routed to the host identity assigned by the node, and the home domain mobility anchor can be used as the node identity. Host location ID. At this point, the node's host ID and host location ID are the same.
  • Step 203 The home domain mobility anchor first sends a query request to the DNS.
  • the query request carries the domain name of the management domain of the node. Further, the domain name of the management domain and the local host name form a global host name.
  • Step 204 The query response returned by the DNS.
  • the DNS receives the query request sent by the home domain mobility anchor of the node, since the DNS stores the mapping between the ⁇ admin domain domain name and the home domain mapping server IP address>, the DNS is based on the management domain domain name of the node.
  • the IP address of the home domain mapping server of the node may be queried, and the IP address of the home domain mapping server that queries the node is returned to the home domain mobility anchor point of the node.
  • Step 205 The home domain mobility anchor of the node determines the binding relationship between the host identity of the node and the host location identifier, and stores the binding relationship to the home domain mapping server of the node.
  • the mapping server issues a change content synchronization message.
  • the mobile node After the mobility anchor allocates the host identity to the node of the network access request, the mobile node performs an address allocation response to the node of the network access request, where the address allocation response carries the network The host identity assigned by the node accessing the request.
  • the mobility anchor returns an address allocation response to the node of the network access request, and the host identity identifier that the mobility anchor assigns to the node is sent to the home domain mapping server of the node, and indicates the node
  • the home domain mapping server stores the host identity and the host location identifier of the node, which may be completed at the same time; or the mobility anchor first returns an address allocation response to the node of the network access request, and then the node is
  • the assigned host identity is sent to the home domain mapping server of the node, and indicates that the home domain mapping server of the node stores the host identity and the host location identifier of the node;
  • the host identity assigned by the node is sent to the home domain mapping server of the node, and the home domain mapping server of the node is instructed to store the host identity and the host location identifier of the node, and then the node that requests the network access Returning the address allocation response; the sequence of performing the two steps for the embodiment of the present invention Do limited.
  • the host identity identifier address pool and the host location identifier address pool are set in the home domain, and the reserved address pool is also set in the operator, wherein the address in the reserved address pool can be used as the host identity identifier. It can also be used as a host location identifier, where the ratio of the number of pre-allocated first address type flags in the reserved address pool to the number of second address type flags, and the pre-allocated first address type in the address pool of the host identity The number of flags is equal to the number of pre-allocated second address type flags in the address pool of the host location identifier.
  • the first address type flag reserved in the reserved address pool of the operator may be added to the address pool of the host identity; when the host location identifier needs to be adjusted, the operation may be performed.
  • the second address type flag reserved in the reserved address pool of the merchant is added to the address pool of the host location identifier.
  • the process may include:
  • step 301 the node sends an access request to the visited domain mobility anchor.
  • the node home domain mobility anchor node loses the ability to route the host identity assigned by the node. After the node moves to the visited domain mobility anchor point, it needs to send the access point to the visited domain mobility anchor point. Into the request.
  • the visited domain mobility anchor assigns a host location identifier to the node.
  • the visited domain mobility anchor After the access domain access anchor receives the access request sent by the node, the visited domain mobility anchor requests a host location identifier for the node from the host location identifier address pool, and returns the host location identifier requested by the node to the node. Since the node has moved to the visited domain mobility anchor, and the node home domain mobility anchor loses the ability to route the host identity assigned to the node, the host location identifier assigned to the node by the visited domain mobility anchor can be routed. At this point, the node's host ID and host location ID are not the same.
  • the host identity identifier address pool and the host location identifier address pool are set in the visited domain, and the reserved address pool is also set in the operator, wherein the address in the reserved address pool can be used as the host identity identifier. It can also be used as a host location identifier, where the ratio of the number of pre-allocated first address type flags in the reserved address pool to the number of second address type flags, and the pre-allocated first address type in the address pool of the host identity The number of flags is equal to the number of pre-allocated second address type flags in the address pool of the host location identifier.
  • the first address type flag reserved in the reserved address pool of the operator may be added to the address pool of the host identity; when the host location identifier needs to be adjusted, the operation may be performed.
  • the second address type flag reserved in the reserved address pool of the merchant is added to the address pool of the host location identifier.
  • the visited domain mobility anchor sends the host location identifier assigned by the node to the home domain mapping server of the node, and indicates that the home domain mapping server of the node corresponds to the host identity identifier of the node.
  • the host location ID is updated to the currently assigned host location ID.
  • the IP address of the node home domain mapping server needs to be obtained first.
  • the visited domain mobility anchor of the node first sends a query request to the DNS.
  • the query request carries the domain name of the management domain of the node. Further, the domain name of the management domain and the local host name form a global host name.
  • Step 304 the query response returned by the DNS.
  • the DNS After the DNS receives the query request sent by the accessing domain mobility anchor of the node, since the DNS stores the mapping between the ⁇ admin domain domain name and the DMS IP>, the DNS can query the node according to the management domain domain name of the node.
  • the home domain maps the IP address of the server, and returns the IP address of the home domain mapping server that is queried to the node to the visited domain mobility anchor of the node.
  • Step 305 The visited domain mobility anchor of the node sends the host location identifier of the node to the home domain mapping server of the node.
  • the home location mapping server of the node replaces the host location identifier corresponding to the host location identifier corresponding to the host identity of the node.
  • the backup mapping server issues a change content synchronization message.
  • an embodiment of the present invention in order to increase reliability or implement load sharing, multiple DMSs may be set in one management domain.
  • the data is synchronized to other DMSs in the management domain to keep the data of all DMSs in one management domain synchronized.
  • an embodiment of the present invention further provides an address obtaining method.
  • FIG. 7 is a schematic diagram of an address obtaining process according to an embodiment of the present invention. This process can be performed by a mobile anchor.
  • the mobility anchor is deployed at the edge router level of the access network.
  • the process can include:
  • Step 401 Obtain a global host name of the node.
  • Step 402 Obtain a host identity and a host location identifier of the node according to the global host name of the node.
  • the host identity and the host location identifier are both IPv6 addresses, and are included in the IPv6 address of the host identity.
  • the first address type flag, the IPv6 address identified as the host location identifier, includes the second address type flag.
  • the step 402 can be implemented by two parsing processes. As shown in FIG. 8 , the two parsing processes may include:
  • Step 4021 Send a first query request to the DNS, where the first query request carries the domain name of the management domain of the node, where the domain name and the local host name form a global host name.
  • Step 4022 Receive a first query response returned by the DNS, where the first query response carries an IP address of the DMS queried by the DNS according to the domain name part of the management domain of the node.
  • the DNS (but not limited to the DNS) is used to perform a parsing and query service for different administrative domains, and the mapping of the DMS Internet IP address is implemented.
  • each management domain In order to be compatible with the existing domain name resolution system, each management domain only needs to register the mapping entry ⁇ admin domain domain name, DMS IP> to the DNS, and no longer registers with the host as the domain name, host IP address. Map entry. According to the domain name information of the management domain in the GH, the IP address of the primary service DMS in the management domain can be obtained and returned.
  • the embodiment of the present invention can greatly reduce the size of DNS mapping entries.
  • Step 4023 Send a second query request to the home domain DMS of the node according to the IP address of the queried DMS, where the second query request carries the global host name of the node.
  • the mobility anchor After the mobile anchor receives the IP address of the DMS returned by the DNS, in order to further obtain the host identity and the host location identifier of the node, the mobility anchor initiates a second query request to the home domain DMS of the node according to the DMS IP address.
  • the DMS queries the local host name of the node as the keyword according to the local host name in the global host name of the node.
  • the DMS maintains the mapping between the host ID and the host location identifier of the node. Therefore, the DMS can obtain the host identity and host location identifier of the node.
  • the mapping entry of the host identity and the host location identifier, the local host name, the host identity, and the host location identifier are stored in the DMS, and are mainly used for registering and storing the host identity and the host location identifier. Mapping resolution, handling binding updates for host location IDs and host identities, and more.
  • Step 4024 Receive a second query response returned by the home domain DMS of the node, where the home domain DMS carrying the node in the second query response is queried according to the local host name part in the global host name of the node. Host identity and host location ID.
  • the mobility anchor After receiving the host identity and host location identifier of the node returned by the DMS, the mobility anchor caches the mapping relationship between the host identity and the host location identifier of the node.
  • the home domain DMS of the node needs to maintain the mapping entry ⁇ host identity, host location identifier> in its jurisdiction, so the home domain DMS implements dynamic resolution.
  • the resolution process of the home domain DMS relies on the idea of DNS, and uses the domain name mapping to resolve the changed IP address, which is suitable for fast dynamic update.
  • the mapping storage of the mapping entry to the global DMS is related to the geographic location, and the solution of determining the local identification of the local identity identifier of the node to the domain mapping server is determined by the mapping algorithm, and the embodiment of the present invention facilitates direct query. Can reduce query latency.
  • the above address acquisition process usually occurs during the establishment of a communication connection.
  • the communication connection establishment process will be described in detail below with reference to FIGS. 9 to 11.
  • the process may include:
  • Step 501 Node 1 sends a communication connection establishment request to the home domain mobility anchor of the node.
  • the request carries the global host name of the node 2, and the node 2 is the opposite node that the node 1 requests to communicate with.
  • Step 502 The home domain mobility anchor of the node 1 sends a query request to the DNS, where the query request carries the domain name of the management domain of the node 2. Further, the administrative domain domain name and the local host name constitute a global host name.
  • Step 503 The query response returned by the DNS, wherein the DNS obtains the IP address of the DMS of the home domain of the node 2 according to the domain name of the management domain of the node 2, and the DMS IP address is carried in the query response message and returned to the home domain mobile anchor point. .
  • the specific implementation process of this step can be referred to the foregoing embodiment.
  • Step 504 The home domain mobility anchor of the node 1 initiates a query request to the home domain mobility anchor node of the node 2 according to the DMS IP address carried in the query response returned by the DNS.
  • the query request carries the global host name of the node 2.
  • Step 505 The query response returned by the home domain mapping server of the node 2.
  • the home domain mobility anchor of the node 2 queries the host identity and the host location identifier of the node 2 according to the local host part of the global host name of the node 2, and queries the host identity and host location identifier of the node 2 that is queried.
  • the bearer and the query response are returned to the home domain mobility anchor of node 1.
  • the specific implementation process of this step can be referred to the foregoing embodiment.
  • Step 506 The home domain mobility anchor of the node 1 slows down the host identity and the host location identifier of the node 2 Save and return the host ID of node 2 to node 1.
  • Step 507 The home domain mobility anchor of the node 1 initiates a communication connection establishment request to the home domain mobility anchor node of the node 2, where the host identity identifier and the host location identifier of the node 1 are carried.
  • Step 508 After the home domain mobility anchor of the node 2 receives the host identity and the host location identifier of the node 1 sent by the home domain mobility anchor of the node 1, the host identity and the host location identifier of the node 1 are cached, and Send the host ID of node 1 to node 2.
  • Step 509 Node 2 caches the host identity of Node 1, and establishes a communication connection between Node 2 and Node 1.
  • FIG. 10 shows the communication process between two nodes.
  • the process may include:
  • Step 601 The home domain mobility anchor of the node 1 receives the first communication message sent by the node 1.
  • the first communication message sent by the node 1 carries the host identity of the node 1 and the host identity of the node 2.
  • Step 602 The home domain mobility anchor of the node 1 is based on the mapping relationship between the host identity of the locally cached node 1 and the node 2 and the host location identifier, and if necessary, the host identity of the node 1 in the first communication message is converted to the node 1
  • the host location identifier is used to convert the host identity of the node 2 in the first communication message to the host location identifier of the node 2, and then send the first message after the address translation to the home domain mobility anchor node of the node 2.
  • Step 603 The home domain mobility anchor of the node 2 is mapped according to the mapping between the host identity of the locally cached node 1 and the node 2 and the host location identifier, and if necessary, the host location identifier of the node 1 in the first communication message is converted to the node 1
  • the host identity identifier converts the host location identifier of the node 2 in the first communication message to the host identity of the node 2, and then sends the first message after the address translation to the node 2.
  • Step 701 In the process of communication between the node 1 and the node 2, the node 1 moves from the home domain mobility anchor point to the visited domain mobility anchor point, the host identity of the node 1 loses the routing role, and the node 1 needs to move the anchor to the visited domain. Point to issue an access request, referring to FIG. 6 and the method in which node 1 accesses the visited domain mobility anchor point.
  • the visited domain mobility anchor node 1 assigns the host location identifier to the node 1, and stores the host location identifier of the node 1 to the home domain mapping server of the node 1, the following steps are also included:
  • the visited domain mobility anchor of the node 1 receives the communication message sent by the node 1 to the node 2, wherein the communication message carries the host identity of the node 1 and the node 2, and the visited domain of the node 1 moves the anchor point.
  • the host of the node 1 The identity identifier of the identity conversion node 1 is converted, if necessary, the host identity of the node 2 is converted to the host location identifier of the node 2, and then the address-converted communication message is sent to the home domain mobility anchor of the node 2.
  • the home domain mobility anchor of the node 2 When the home domain mobility anchor of the node 2 receives the converted communication message sent by the visited domain mobility anchor of the node 1, the host identity of the node 1 and the new host location identifier are re-established, and then the home domain of the node 2 moves the anchor point. According to the mapping relationship between the host ID of the locally cached node 1 and the host 2 and the host location identifier, the host location identifier of the node 1 in the communication message is converted into the host identity of the node 1 and, if necessary, the host location of the node 2 in the communication message. The host identity of the conversion node 2 is identified, and then the address-converted communication message is sent to the node 2.
  • step 703 a communication signaling interaction is performed between the visited domain mobility anchor of the node 1 and the home domain mobility anchor of the node 1. It is ensured that the visited domain mobility anchor of the node 1 can receive the communication message sent by the node 2 forwarded by the home domain mobility anchor of the node 2 of the node 1 to the node 1 to the node 1.
  • the steps 702 and 703 are not in the order, and the step 702 may be performed first, and then the step 703 may be performed; or the step 703 may be performed first; and the step sequence is not limited in the present invention.
  • the host identity and the host location identifier are both IPv6 addresses, and the IPv6 address that is the host identity identifier includes the first address type identifier, and the IPv6 address that is the host location identifier includes the second address.
  • a type flag, the first address type flag and the second address type flag have different value spaces; the first address type flag and the second address type flag value space are determined and the first address type flag and the second
  • the proportion of the address type flag can be flexibly set and dynamically adjusted according to the carrier's own load status, and the ratio of the first address type flag and the second address type flag can also be flexibly adjusted according to the ratio of the mobile node to the fixed node.
  • the IPv6 address supports the mobility from its own grammar, and also solves the problem of dual semantics of the IP address. Sending, to the home domain mapping server of the node, a host identity or a host location identifier assigned to the node, so that the home domain mapping server of the node maintains a relationship between the host identity and the host location identifier of the node Correspondence relationship. Reduce the number of queries and improve query efficiency.
  • the embodiment of the present invention further provides an address allocation device and a communication device.
  • the specific content of the device may be implemented by referring to the foregoing method, and details are not described herein again.
  • an embodiment of the present invention provides an address allocation apparatus, including: a receiving unit 21, an allocating unit 22, a maintenance unit 23, and an adjusting unit 24.
  • the receiving unit 21 is configured to receive a network access request.
  • the allocating unit 22 is configured to allocate a host identity or a host location identifier to the node that requests access according to the network access request, where the host identity and the host location identifier are both IPv6 addresses, and serve as a host identity.
  • the identified IPv6 address contains the first address type flag, and the IPv6 address that is the host location identifier contains the second Address type flag;
  • the maintenance unit 23 is configured to send a host identity or a host location identifier allocated to the node to the home domain mapping server of the node, so that the home domain mapping server of the node maintains the host identity of the node and The correspondence between host location identifiers.
  • the receiving unit 21 is specifically configured to: receive a host identity assignment request sent by the node, where the node belongs to the mobility anchor point;
  • the allocating unit 22 is specifically configured to: allocate a host identity identifier to the node according to the identity identifier allocation request, and use the host identity identifier of the node as a host location identifier of the node at the same time;
  • the host identity identifier is carried in the response message and sent to the node;
  • the maintenance unit 23 is specifically configured to: send a host identity identifier allocated to the node to the home domain mapping server of the node, and instruct the home domain mapping server of the node to store the host identity identifier and the host of the node a location identifier, wherein the host location identifier of the node is the same as the host identity of the node.
  • the receiving unit 21 is specifically configured to: receive an access request sent by the node, where the node is not attributable to the mobility anchor point;
  • the allocating unit 22 is specifically configured to: allocate a host location identifier to the node according to the access request;
  • the maintenance unit 23 is specifically configured to: send a host location identifier allocated to the node to the home domain mapping server of the node, and instruct the home domain mapping server of the node to correspond to the host identity identifier of the node
  • the host location ID is updated to the currently assigned host location ID.
  • the maintenance unit 23 is further configured to: send a query request to the domain name system DNS, where the query request carries a global host name of the node;
  • the query response carries an Internet Protocol IP address of the home domain mapping server of the node that is queried by the DNS according to the domain name of the management domain in the global host name of the node.
  • the allocating unit 22 is specifically configured to: select, according to the network access request, a host identity identifier from the address pool of the host identity for the node; or, according to the network access request, from the host location Selecting a host location identifier for the node in the identified address pool;
  • the number of the first address type identifiers pre-allocated in the address pool of the host identity identifier and the number of the second address type identifiers pre-allocated in the address pool of the host location identifier are set according to a set ratio.
  • a reserved address pool is further configured, where the reserved address pool includes a host identity identifier and a host location identifier, where the number of pre-allocated first address type flags and the second address type flag in the reserved address pool The number is set according to the set ratio;
  • the adjusting unit 24 is further configured to: add the first address type flag reserved in the reserved address pool to the address pool of the host identity, and/or reserve the reserved address pool The second address type flag is added to the address pool of the host location ID.
  • the first address type flag or the second address type flag is carried in an address type field of the IPv6 address.
  • an embodiment of the present invention provides an address obtaining apparatus, where the apparatus includes: a first acquiring unit 31, a second acquiring unit 32, and a sending unit 33.
  • a first obtaining unit 31 configured to acquire a global host name of the node
  • the second obtaining unit 32 is configured to obtain, according to the global host name of the node, a host identity and a host location identifier of the node; the host identity and the host location identifier are both IPv6 addresses, and serve as a host identity.
  • the IPv6 address includes a first address type flag, and the IPv6 address that is the host location identifier includes a second address type flag, where the first address type flag and the second address type flag have different value spaces.
  • the second obtaining unit 32 has:
  • the DNS Receiving a first query response returned by the DNS, where the first query response carries an Internet Protocol IP address of the domain mapping server that is queried by the DNS according to the domain name of the management domain in the global host name of the node;
  • the first acquiring unit 31 is specifically configured to: receive a communication establishment request sent by the calling node, and acquire a global host name of the called node carried in the communication establishment request;
  • the sending unit 33 is configured to send, after the second obtaining unit acquires the host identity and the host location identifier of the called node according to the global host name of the called node, send the host identity of the calling node Sending, to the called node, a host identity of the called node to the calling node, so as to establish a communication connection between the called node and the calling node.
  • An address distribution apparatus of the present embodiment includes a reception communication unit, a transmission communication unit, and a communication establishment unit.
  • the above-mentioned unit may be disposed in the same physical device, or may be a plurality of independently configured physical devices, which are not specifically limited in the embodiment of the present invention.
  • an embodiment of the present invention provides another address allocation apparatus, including: a processor 500, configured to read a program in the memory 520, and perform the following process:
  • the host identity and the host location identifier are both IPv6 addresses, and the IPv6 address that is the host identity identifier includes the first address type identifier, and the IPv6 address that is the host location identifier includes the second address type identifier.
  • the processor 500 receives, by the transceiver 510, a host identity assignment request sent by the node, where the node belongs to the mobility anchor point;
  • the processor 500 allocates a host identity to the node according to the identity identifier allocation request, and uses the host identity of the node as the host location identifier of the node; the node is used by the transceiver 510.
  • the host identity identifier is carried in the response message and sent to the node;
  • the processor 500 sends the host identity assigned to the node to the home domain mapping server of the node through the transceiver 510, and instructs the home domain mapping server of the node to store the host identity of the node and A host location identifier, wherein the host location identifier of the node is the same as the host identity of the node.
  • the processor 500 receives an access request sent by the node through the transceiver 510, and the node is not attributable to the mobility anchor point;
  • the processor 500 allocates a host location identifier to the node according to the access request
  • the processor 500 sends a host location identifier assigned to the node to the home domain mapping server of the node by using the transceiver 510, and indicates that the home domain mapping server of the node corresponds to the host identity of the node.
  • the host location ID is updated to the currently assigned host location ID.
  • the processor 500 sends a query request to the domain name system DNS through the transceiver 510, where the query request carries the global host name of the node;
  • the query response carries an Internet Protocol IP address of the home domain mapping server of the node that is queried by the DNS according to the domain name of the management domain in the global host name of the node.
  • the processor 500 selects, according to the network access request, a host identity identifier from the address pool of the host identity for the node; or, according to the network access request, the address pool identified from the host location Selecting a host location identifier for the node;
  • the number of the first address type identifiers pre-allocated in the address pool of the host identity identifier and the number of the second address type identifiers pre-allocated in the address pool of the host location identifier are set according to a set ratio.
  • a reserved address pool is further configured, where the reserved address pool includes a host identity identifier and a host location identifier, where the number of pre-allocated first address type flags and the second address type flag in the reserved address pool The number is set according to the set ratio;
  • the processor 500 is further configured to: add a first address type identifier reserved in the reserved address pool to the address pool of the host identifier, and/or a second address type reserved in the reserved address pool. Flag added to the location of the host location identifier In the address pool.
  • the first address type flag or the second address type flag is carried in an address type field of the IPv6 address.
  • the transceiver 510 is configured to receive and transmit data under the control of the processor 500.
  • the bus architecture can include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 500 and various circuits of memory represented by memory 520.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • Transceiver 510 can be a plurality of components, including a transmitter and a transceiver, providing means for communicating with various other devices on a transmission medium.
  • the processor 500 is responsible for managing the bus architecture and general processing, and the memory 520 can store data used by the processor 500 when performing operations.
  • the embodiment of the present invention provides another address obtaining apparatus, and the structure of the apparatus may be the structure shown in FIG. 14 or other structures.
  • the embodiment of the present invention provides another address obtaining apparatus.
  • the processor 600 is configured to read a program in the memory 620 and perform the following process:
  • the processor 600 sends a first query request to the domain name system DNS through the transceiver 610, where the first query request carries the global host name of the node;
  • the processor 600 receives the first query response returned by the DNS by using the transceiver 610, where the first query response carries the domain queried by the DNS according to the domain name of the management domain in the global host name of the node. Mapping the server's Internet Protocol IP address;
  • the processor 600 sends a query request to the home domain mapping server of the node according to the IP address of the queried domain mapping server, where the query request carries the global host name of the node;
  • the processor 600 receives, by the transceiver 610, a second query response returned by the home domain mapping server of the node, where the second query response carries the home domain mapping server of the node according to the global host name of the node.
  • the host ID and host location ID queried by the local hostname part in .
  • the processor 600 receives, by the transceiver 610, a communication establishment request sent by the calling node, and acquires a global host name of the called node carried in the communication establishment request;
  • the processor 600 is further configured to send the host identity of the calling node by using the transceiver 610 after acquiring the host identity and the host location identifier of the called node according to the global host name of the called node. To the stated The called node sends the host identity of the called node to the calling node, so as to establish a communication connection between the called node and the calling node.
  • the transceiver 610 is configured to receive and transmit data under the control of the processor 600.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 600 and various circuits of memory represented by memory 620.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • Transceiver 610 can be a plurality of components, including a transmitter and a receiver, providing means for communicating with various other devices on a transmission medium.
  • the user interface 630 may also be an interface capable of externally connecting the required devices, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 600 is responsible for managing the bus architecture and general processing, and the memory 620 can store data used by the processor 600 in performing operations.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Databases & Information Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Small-Scale Networks (AREA)

Abstract

本发明公开了一种地址分配、获取方法及装置,该方法包括:接收网络接入请求;根据所述网络接入请求为请求接入的节点分配主机身份标识或主机位置标识;其中,所述主机身份标识和所述主机位置标识均为IPv6地址,且作为主机身份标识的IPv6地址中包含第一地址类型标志,作为主机位置标识的IPv6地址中包含第二地址类型标志,所述第一地址类型标志和第二地址类型标志具有不同的取值空间;将为所述节点分配的主机身份标识或主机位置标识发送给所述节点的归属域映射服务器,以使所述节点的归属域映射服务器维护所述节点的主机身份标识和主机位置标识之间的对应关系。

Description

一种地址分配、获取方法及装置
本申请要求在2014年12月11日提交中国专利局、申请号为201410766245.5、发明名称为“一种地址分配、获取方法及装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本发明涉及网络通信技术领域,更具体的涉及一种地址分配、获取方法及装置。
背景技术
随着移动互联网的发展,现有移动网络的通信过程中仍存在传统互联网的特性,即IP(Internet Protocol,网络协议)地址既作为终端身份标识与高层会话绑定,又作为终端位置标识进行数据包的路由和转发,具有双重语义。这种双重语义对支持主机移动性具有很大局限性。
针对移动性问题,IETF(Internet Engineering Task Force,Internet工程任务组)提出了移动IP协议(MIP,Mobile IP Protocol)及其改进方法。但是,无论移动IPv4协议,还是移动IPv6协议,均没有改变IP地址双重语义的本质特性,这意味着移动IP协议及其改进方法不能彻底解决互联网的移动性管理中身份标识与位置标识定义的问题。
目前,全球IPv4地址即将耗尽,IPv6地址将是未来互联网的核心地址资源。因此,亟需一种能够实现IPv6地址的身份属性和位置属性分离的技术,解决IPv6地址对移动性支持的问题。
发明内容
本发明实施例提供一种地址分配、获取方法及装置,通过在IPv6地址中设置地址类型标志位,用以区分该IPv6地址是主机身份标识,还是主机位置标识,从而实现身份标识和位置标识的分离,支持移动过程中主机通信的连续性。
本发明实施例提供一种地址分配方法,包括:
接收网络接入请求;
根据所述网络接入请求为请求接入的节点分配主机身份标识或主机位置标识;其中,所述主机身份标识和所述主机位置标识均为IPv6地址,且作为主机身份标识的IPv6地址中包含第一地址类型标志,作为主机位置标识的IPv6地址中包含第二地址类型标志;
将为所述节点分配的主机身份标识或主机位置标识发送给所述节点的归属域映射服务器,以使所述节点的归属域映射服务器维护所述节点的主机身份标识和主机位置标识之间的对应关系。
进一步地,所述接收网络接入请求,包括:
移动锚点接收节点发送的主机身份标识分配请求,所述节点归属于所述移动锚点;
所述根据所述网络接入请求为所述节点分配主机身份标识,包括:
所述移动锚点根据所述身份标识分配请求为所述节点分配主机身份标识,将所述节点的主机身份标识携带于响应消息发送给所述节点,并将所述节点的主机身份标识同时作为所述节点的主机位置标识使用;
所述将为所述节点分配的主机身份标识发送给所述节点的归属域映射服务器,包括:
所述移动锚点将为所述节点分配的主机身份标识发送给所述节点的归属域映射服务器,并指示所述节点的归属域映射服务器存储所述节点的主机身份标识和主机位置标识,其中,所述节点的主机位置标识与所述节点的主机身份标识相同。
进一步地,所述接收网络接入请求,包括:
移动锚点接收节点发送的接入请求,所述节点不归属于所述移动锚点;
所述根据所述网络接入请求为所述节点分配主机位置标识,包括:
所述移动锚点根据所述接入请求为所述节点分配主机位置标识;
所述将为所述节点分配的主机位置标识发送给所述节点的归属域映射服务器,包括:
所述移动锚点将为所述节点分配的主机位置标识发送给所述节点的归属域映射服务器,并指示所述节点的归属域映射服务器将所述节点的主机身份标识所对应的主机位置标识更新为当前所分配的主机位置标识。
进一步地,所述将为所述节点分配的主机身份标识或主机位置标识发送给所述节点的归属域映射服务器之前,还包括:
向域名系统DNS发送查询请求,所述查询请求中携带所述节点的全球主机名;
接收所述DNS返回的查询响应,所述查询响应中携带有所述DNS根据所述节点的全球主机名中的管理域域名部分查询到的所述节点的归属域映射服务器的网际协议IP地址。
进一步地,所述根据所述网络接入请求为所述节点分配主机身份标识,包括:
根据所述网络接入请求,从主机身份标识的地址池中为所述节点选取主机身份标识;
所述根据所述网络接入请求为所述节点分配主机位置标识,包括:
根据所述网络接入请求,从主机位置标识的地址池中为所述节点选取主机位置标识;
其中,主机身份标识的地址池中预分配的第一地址类型标志的数量与主机位置标识的地址池中预分配的第二地址类型标志的数量,按照设定比例设置。
进一步地,还设置有预留地址池,所述预留地址池中包括主机身份标识和主机位置标识,其中,预留地址池中预分配的第一地址类型标志的数量与第二地址类型标志的数量,按照所述设定比例设置;
该方法还包括:
将预留地址池中预留的第一地址类型标志添加到主机身份标识的地址池中,和/或,将预留地址池中预留的第二地址类型标志添加到主机位置标识的地址池中。
进一步地,所述第一地址类型标志或所述第二地址类型标志承载在所述IPv6地址的地址类型域中。
本发明实施例一种地址获取方法,该方法包括:
获取节点的全球主机名;
根据所述节点的全球主机名获取所述节点的主机身份标识和主机位置标识;所述主机身份标识和所述主机位置标识均为IPv6地址,且作为主机身份标识的IPv6地址中包含第一地址类型标志,作为主机位置标识的IPv6地址中包含第二地址类型标志,所述第一地址类型标志和第二地址类型标志具有不同的取值空间。
进一步地,所述根据所述节点的全球主机名获取所述节点的主机身份标识和主机位置标识,包括:
向域名系统DNS发送第一查询请求,所述第一查询请求中携带所述节点的全球主机名;
接收所述DNS返回的第一查询响应,所述第一查询响应中携带有所述DNS根据所述节点的全球主机名中的管理域域名部分查询到的域映射服务器的网际协议IP地址;
根据查询到的域映射服务器的的IP地址,向所述节点的归属域映射服务器发送第二查询请求,所述第二查询请求中携带所述节点的全球主机名;
接收所述节点的归属域映射服务器返回的第二查询响应,所述第二查询响应中携带有所述节点的归属域映射服务器根据所述节点的全球主机名中的本地主机名部分查询到的主机身份标识和主机位置标识。
进一步地,所述获取节点的全球主机名,包括:
接收主叫节点发送的通信建立请求,获取所述通信建立请求中携带的被叫节点的全球主机名;
根据所述被叫节点的全球主机名获取所述被叫节点的主机身份标识和主机位置标识之后,所述方法还包括:
将所述主叫节点的主机身份标识发送至所述被叫节点,将所述被叫节点的主机身份标识发送至所述主叫节点,以使所述被叫节点与所述主叫节点之间建立通信连接。
本发明实施例提供一种地址分配装置,包括:
接收单元,用于接收网络接入请求;
分配单元,用于根据所述网络接入请求为请求接入的节点分配主机身份标识或主机位置标识;其中,所述主机身份标识和所述主机位置标识均为IPv6地址,且作为主机身份标识的IPv6地址中包含第一地址类型标志,作为主机位置标识的IPv6地址中包含第二地址 类型标志;
维护单元,用于将为所述节点分配的主机身份标识或主机位置标识发送给所述节点的归属域映射服务器,以使所述节点的归属域映射服务器维护所述节点的主机身份标识和主机位置标识之间的对应关系。
进一步地,所述接收单元具体用于:接收节点发送的主机身份标识分配请求,所述节点归属于所述移动锚点;
所述分配单元具体用于:根据所述身份标识分配请求为所述节点分配主机身份标识,并将所述节点的主机身份标识同时作为所述节点的主机位置标识使用;将所述节点的主机身份标识携带于响应消息发送给所述节点;
所述维护单元具体用于:将为所述节点分配的主机身份标识发送给所述节点的归属域映射服务器,并指示所述节点的归属域映射服务器存储所述节点的主机身份标识和主机位置标识,其中,所述节点的主机位置标识与所述节点的主机身份标识相同。
进一步地,所述接收单元具体用于:接收节点发送的接入请求,所述节点不归属于所述移动锚点;
所述分配单元具体用于:根据所述接入请求为所述节点分配主机位置标识;
所述维护单元具体用于:将为所述节点分配的主机位置标识发送给所述节点的归属域映射服务器,并指示所述节点的归属域映射服务器将所述节点的主机身份标识所对应的主机位置标识更新为当前所分配的主机位置标识。
进一步地,所述维护单元还用于:向域名系统DNS发送查询请求,所述查询请求中携带所述节点的全球主机名;
接收所述DNS返回的查询响应,所述查询响应中携带有所述DNS根据所述节点的全球主机名中的管理域域名部分查询到的所述节点的归属域映射服务器的网际协议IP地址。
进一步地,所述分配单元具体用于:根据所述网络接入请求,从主机身份标识的地址池中为所述节点选取主机身份标识;或者,根据所述网络接入请求,从主机位置标识的地址池中为所述节点选取主机位置标识;
其中,主机身份标识的地址池中预分配的第一地址类型标志的数量与主机位置标识的地址池中预分配的第二地址类型标志的数量,按照设定比例设置。
进一步地,还设置有预留地址池,所述预留地址池中包括主机身份标识和主机位置标识,其中,预留地址池中预分配的第一地址类型标志的数量与第二地址类型标志的数量,按照所述设定比例设置;
还包括调整单元,所述调整单元用于:将预留地址池中预留的第一地址类型标志添加到主机身份标识的地址池中,和/或,将预留地址池中预留的第二地址类型标志添加到主机位置标识的地址池中。
进一步地,所述第一地址类型标志或所述第二地址类型标志承载在所述IPv6地址的地址类型域中。
本发明实施例提供一种地址获取装置,该装置包括:
第一获取单元,用于获取节点的全球主机名;
第二获取单元,用于根据所述节点的全球主机名获取所述节点的主机身份标识和主机位置标识;所述主机身份标识和所述主机位置标识均为IPv6地址,且作为主机身份标识的IPv6地址中包含第一地址类型标志,作为主机位置标识的IPv6地址中包含第二地址类型标志,所述第一地址类型标志和第二地址类型标志具有不同的取值空间。
进一步地,所述第二获取单元具有用于:
向域名系统DNS发送第一查询请求,所述第一查询请求中携带所述节点的全球主机名;
接收所述DNS返回的第一查询响应,所述第一查询响应中携带有所述DNS根据所述节点的全球主机名中的管理域域名部分查询到的域映射服务器的网际协议IP地址;
根据查询到的域映射服务器的的IP地址,向所述节点的归属域映射服务器发送查询请求,所述查询请求中携带所述节点的全球主机名;
接收所述节点的归属域映射服务器返回的第二查询响应,所述第二查询响应中携带有所述节点的归属域映射服务器根据所述节点的全球主机名中的本地主机名部分查询到的主机身份标识和主机位置标识。
进一步地,所述第一获取单元具体用于:接收主叫节点发送的通信建立请求,获取所述通信建立请求中携带的被叫节点的全球主机名;
还包括:
发送单元,用于在所述第二获取单元根据所述被叫节点的全球主机名获取所述被叫节点的主机身份标识和主机位置标识之后,将所述主叫节点的主机身份标识发送至所述被叫节点,将所述被叫节点的主机身份标识发送至所述主叫节点,以使所述被叫节点与所述主叫节点之间建立通信连接。
本发明实施例中,节点的主机身份标识和主机位置标识均为IPv6地址,且作为主机身份标识的IPv6地址中包含第一地址类型标志,作为主机位置标识的IPv6地址中包含第二地址类型标志,从而使得IPv6地址从自身划分语法上支持移动性的同时,也解决了IP地址双重语义的问题。
附图说明
图1为现有技术中全球单播地址格式示意图;
图2为本发明实施例中的IPv6地址分配方法示意图;
图3为本发明实施例提供的一种地址分配方法示意图;
图4为本发明实施例提供的一种地址分配方法中映射解析方法流程图;
图5为本发明实施例提供一种节点接入归属域移动锚点的方法流程示意图;
图6为本发明实施例提供一种节点接入拜访域移动锚点的方法流程示意图;
图7为本发明实施例中两次映射解析方法示意图;
图8为本发明实施例中两次映射解析方法流程示意图;
图9为本发明实施例提供一种节点1与节点2建立通信连接的方法流程示意图;
图10为本发明实施例提供一种节点1向节点2发起通信的方法流程示意图;
图11为本发明实施例提供一种节点1与节点2通信过程中,节点1的主机位置标识发生变化的方法流程示意图;
图12为本发明实施例提供的一种地址分配装置示意图;
图13为本发明实施例提供的一种地址获取装置示意图;
图14为本发明实施例提供的另一种地址分配装置示意图;
图15为本发明实施例提供的另一种地址获取装置示意图。
具体实施方式
运营商从上级RIR/ISP(Regional Internet Register/Internet Service Provider,区域互联网注册管理机构/互联网服务提供商)获得N/的IPv6前缀地址块后,可依照自身部署规划、负载状况等,在IPv6地址分配之前对前缀地址块进行合理的编码,其中,N表示前缀长度。
图1示出了RFC 4291对IPv6地址进行划分所得到的全球单播地址一般格式,其中,全球路由选择前缀占用n个比特;站内子网占用64-n(即64减n)个比特;接口标识符占用64个比特。其中,全球路由前缀是指分配给某个站点的前缀值,所述站点为子网或者链路的集群;站内子网是指标识此站点中某一子网或链路的标识符。
为使IPv6地址从划分伊始就支持移动性,本发明实施例中,从IPv6地址中取出T个比特,用这T个比特设置地址类型标志,用于标识该IPv6地址作为主机身份标识进行分配还是作为主机位置标识进行分配。优选地,可从IPv6地址中的前缀地址块中取出连续T个比特来设置地址类型标志。
其中,主机身份标识用于唯一标识一台主机,与端口号一起组成主机传输层的访问点;由主机归属域接入路由器分配,全局唯一,在主机生命周期内固定不变;在归属网络中,主机身份标识可全局路由。主机位置标识作为确定某主机所在链路的依据,同时也是路由器决定分组向何处转发的依据;由拜访网络接入路由器动态分配,随主机所在网络接入点的改变而变化;主机位置标识可全局路由。
图2示出了一种本发明实施例对于IPv6地址的具体划分格式。IPv6地址划分为n比 特的“全球路由前缀”域、(64减n)比特的“站内子网”域和64比特的“接口标识符”域。其中,“站内子网”域用于承载标识此站点中某一子网或链路的标识符,占用C比特;“接口标识符”域用于承载接口标识符,接口标识符依然保留标准全球单播地址中接口标识符的格式,占用64个比特。“全球路由前缀”域划分为“接入地址”域、“地址类型”域和“站点编码”域三部分。
“接入地址”域中承载接入地址,该域的长度为RIR/ISP分配的前缀地址块的长度N。接入地址是指运营主体从上级RIR/ISP分得并备案的N/前缀地址块,例如:三大运营商、教育网、科技网等备案的地址块。
“站点编码”域中承载站点编码,该域的长度为S比特,S≥1。站点编码是各站点层次编码,即用于标识某运营主体下各站点的标识符。
“地址类型”域中承载地址类型标志,该域的长度为T比特,T的取值与接入地址、站点编码、站内子网以及接口标识符的长度有关,可由运营商根据自身负载情况确定,T的取值最小是1,N+S+T+C=64比特。
地址类型标志包括第一地址类型标志、第二地址类型标志,其中,当为节点分配主机身份标识时,所分配的主机身份标识中包含第一地址类型标志;当为节点分配主机位置标识时,所分配的主机位置标识中包含第二地址类型标志;所述第一地址类型标志和第二地址类型标志具有不同的取值,从而可实现IPv6地址空间垂直分块解耦。比如,第一地址类型标志可取值为1000,第二地址类型标志可取值为1100。
进一步地,考虑到不同站点负载(比如节点数量)和移动性要求的不同,本发明实施例可根据站点内包含的移动节点和固定节点的数量比例来为该站点配置第一地址类型标志的数量或取值范围,以及配置第二地址类型标志的数量或取值范围,从而设定可分配的主机身份标识的数量与可分配的主机位置标识的数量的比例。
比如,某运营主体拥有32/的IPv6前缀块,其下设有两个站点:site A与site B。site A的预设负载量为site B的1.5倍。设site A固定节点相对移动节点较多,且为非热点区域;设site B中移动节点相对固定节点较多,且移动节点流入量与流出量相对平等。
基于图2所示的IPv6地址的格式,“接入地址”长度即为运营主体分得的前缀块的长度,故为32比特,其具体值用N表示;“地址类型标志”设在“接入地址”后,设为4比特(即IPv6地址的第32bit~35bit设置为地址类型标志),其中,4比特的地址类型标志共有16个值。“站点编码”长度为S比特,“站内子网”长度为C比特,S+C=28;IPv6地址后64位为“接口标识符”,用LID表示。
配置第一地址类型标志的取值范围为:0000~0111(0000、0001、0010、0011、0100、0101、0110、0111),共有8个值。
配置第二地址类型标志的取值范围为:1000~1011(1000、1001、1010、1011),共有 4个值。
这样,此运营商中预分配的第一地址类型标志的数量与预分配的第二地址类型标志的数量的比例为2:1。由此可以得出:可分配的主机身份标识的数量与可分配的主机位置标识的数量的比例为2:1。
为了能够根据站点内的节点的变化动态调整可分配的主机身份标识和/或主机位置标识的比例,本发明实施例中设置有预留地址池,该预留地址池中的地址既可以作为主机身份标识,也可以作为主机位置标识。当需要调整可分配的主机身份标识时,将预留地址池中预留的第一地址类型标志添加到主机身份标识的地址池中;当需要调整可分配的主机位置标识时,将预留地址池中预留的第二地址类型添加到主机位置标识的地址池中。
例如,可设置预留地址池。其中,预留地址池中预留的部分IPv6地址可以当第一地址类型标志使用,预留的另外一部分IPv6地址可以当第二地址类型标志使用。当需要调整可分配的主机身份标识时,可将预留地址池中的预留的第一地址类型标志添加到主机身份标识的地址池中,当需要调整可分配的主机位置标识时,可将预留地址池中的预留的第二地址类型标志添加到主机位置标识的地址池中。当需要调整主机身份标识和主机位置标识的分配比例时,即可以调整主机身份标识的地址池中的可分配IPv6地址的数量,或者调整主机位置标识的地址池中的可分配IPv6地址的数量,还可调整预留地址池中的第一地址类型标志对应IPv6地址的数量和第二地址类型标志对应IPv6地址的数量的比例。
优选地,如果主机身份标识的地址池中预分配的主机身份标识与主机位置标识的地址池中预分配的主机位置标识的数量,按照比例m:1设置,则预留地址池中第一地址类型标志对应IPv6地址的数量和第二地址类型标志对应IPv6地址的数量,也可按照m:1设置。这样,可以使站点日后扩展所分得的新的主机身份标识与主机位置标识尽可能聚合。
进一步地,为了提高可扩展性,本发明实施例中还可将地址类型标志的取值范围内的一些值作为保留值,这些保留值既不用作第一地址类型标志或其预留值,也不作为第二地址类型标志获取预留值,而是保留用作以后功能扩展使用。
根据以上site A与site B的负载量和移动性要求,表1示出了为site A与site B配置的地址类型标识以及主机身份标识地址池与主机位置标识地址池。
表1.site A与site B主机身份标识地址池与主机位置标识地址池分配详情
Figure PCTCN2015092106-appb-000001
Figure PCTCN2015092106-appb-000002
由于site A中固定节点相对较多,所以消耗的主机身份标识相对主机位置标识较多,故为site A分配的主机身份标识池中主机身份标识的总量约为主机位置标识池中主机位置标识总量的三倍。其中,为site A分配的第一地址类型标志包括:0000,0001,0010;主机身份标识的地址池内可分配的地址表示为:N 0000 S C LID,N 0001 S C LID,N 0010 S C LID。为site A分配的第二地址类型标志包括:1000;主机位置标识的地址池内可分配的地址表示为:N 1000 S C LID。
为了siteA日后扩展所分得的新主机身份标识与主机位置标识尽可能聚合,在预留地址池中为站点A预分配的主机身份标识与预分配的主机位置标识的比例,与主机身份标识的地址池中预分配的主机身份标识与主机位置标识的地址池中预分配的主机位置标识的比例相同。比如,为site A预留的地址类型包括:0011,0100,0101,1001;其中,预留池中第一地址类型标志对应IPv6地址包括N 0011 S C LID,N 0100 S C LID,N 0101 S C LID;预留池中第二地址类型标志对应IPv6地址为:N 1001 S C LID。
由于site B中移动节点相对较多,且移动节点的流入量与流出量相对持平,需考虑为拜访移动节点多预留一些临时主机位置标识。故可为site B按1:1分配主机身份标识与主机位置标识。其中,为site B分配的第一地址类型标志包括:0110;主机身份标识的地址池内可分配的地址表示为:N 0110 S C LID。为site B分配的第二地址类型标志包括:1010;主机位置标识的地址池内可分配的地址表示为:N 1010 S C LID。
为了siteB日后扩展所分得的新主机身份标识与主机位置标识尽可能聚合,在预留地址池中为站点B预分配的主机身份标识与预分配的主机位置标识的比例,与主机身份标识的地址池中预分配的主机身份标识与主机位置标识的地址池中预分配的主机位置标识的比例相同。比如,为siteB预留的地址类型包括:0111,1011;其中,预留池中第一地址类型标志对应IPv6地址为:N 0111 S C LID;预留池中第二地址类型标志对应IPv6地址为:N 1011 S C LID。
本发明实施例中运营商还保留了一部分地址类型标志,不作具体的主机身份标识与主 机位置标识的设定,以后根据部署情况的实际需求,可使用该保留值作为主机身份或主机位置的状态扩展编码,进行运营商整体的主机身份标识与主机位置标识比例的调整或进行扩展分配。比如,IPv6地址中的“地址类型”域中,1100~1111为保留值,其中,N 1100 S C LID、N1101 S C LID、N 1110 S C LID、N 1111 S C LID即可以用于主机位置标识分配,也可以用于主机身份标识分配。
通过以上描述可以看出,本发明实施例基于IPv6划分标准允许的范围内,设置IPv6地址类型标志,其中,地址类型标志包括第一地址类型标志、第二地址类型标志;第一地址类型标志指示IPv6地址可作为主机身份标志进行分配,第二地址类型标志指示IPv6地址可作为主机位置标识进行分配。所述第一地址类型标志和第二地址类型标志取值空间的确定,以及第一地址类型标志和第二地址类型标志的比例,均可以根据站点情况进行灵活设置与动态调整,而且第一地址类型标志和第二地址类型标志的比例也可根据移动节点与固定节点的比例进行灵活调整,从而使得IPv6地址从自身划分语法上支持移动性的同时,也解决了IP地址双重语义的问题。
基于上述IPv6地址规划方法,本发明实施例还提供了一种地址分配方法。
参见图3,为本发明实施例提供一种地址分配方法的流程示意图。该流程可由移动锚点执行。所述移动锚点部署在接入网络中的边缘路由器水平。
如图所示,该流程可包括:
步骤101,接收网络接入请求。
步骤102,根据所述网络接入请求为请求接入的节点分配主机身份标识或主机位置标识。其中,根据上述IPv6地址规划方法可以得出:所述主机身份标识和所述主机位置标识均为IPv6地址,且作为主机身份标识的IPv6地址中包含第一地址类型标志,作为主机位置标识的IPv6地址中包含第二地址类型标志。
步骤103,将为所述节点分配的主机身份标识或主机位置标识发送给所述节点的归属域映射服务器,以使所述节点的归属域映射服务器维护所述节点的主机身份标识和主机位置标识之间的对应关系。
上述流程中的节点,可以是移动节点,也可以是固定节点。
优选地,步骤102中可首先查询节点的归属域的域映射服务器的IP地址。即,通过DNS针对GH(Global-Hostname,全球主机名)中的管理域域名部分进行解析查询,以获得节点归属域的DMS(Domain Mapping Server,域映射服务器)的IP地址。
具体来说,步骤102的执行过程如图4所示,可包括:
步骤1021:向DNS(Domian Name System,域名系统)发送查询请求,其中,查询请求中携带有所述节点的管理域域名,进一步地,所述管理域域名和本地主机名组成全球主机名。
其中,全球主机名用于唯一标识一个用户(个人或组织),由用户向权威机构申请获得,可与用户的真实身份信息绑定,其形式符合Fully Qualified Domain Name(FQDN)的定义,本发明中简写为管理域域名DN(Domain Name)@本地主机名LH(Local Hostname)的形式(即LH@DN)。其中,LH可反应用户真实身份信息,GH为主机所在归属域的域名。
步骤1022:接收所述DNS返回的查询响应,所述查询响应中携带有所述DNS根据所述节点的GH中的管理域域名部分查询到的所述节点的归属域映射服务器的IP地址。
本发明实施例中借助DNS(但不仅局限于DNS)为不同的管理域进行解析查询服务,实现DMS网际IP地址的映射解析。
为了兼容现有的域名解析系统,每个管理域中只需将映射条目<管理域域名,DMS IP>注册到DNS中,而不再以主机为单位,向DNS中注册<域名,主机IP>的映射条目。根据GH中的管理域域名信息进行解析,即可获得本管理域中的主服务DMS的IP地址并将其返回。
因为DMS的IP地址几乎不变,这就维持了原有DNS保存静态结果且进行静态解析的特性。同时,由于同一管理域中,DMS的数量远远少于节点的数量,针对目前多数采用DNS存储<域名,主机身份标识>的方案来说,本发明实施例能大大降低DNS映射条目的规模。
步骤101中,由于节点所处的位置不同,所以节点发出的网络接入请求的类型也会不同。也就是说,移动锚点所接收到的网络接入请求可能是归属域的节点发送的网络接入请求,也可能是拜访域的节点发送的网络接入请求。
下面结合图5和图6,对不同情况下的网络接入过程中的地址分配流程进行详细描述。
参见图5,当节点初次接入归属域时,该流程可包括:
步骤201:节点向其归属域移动锚点发送请求分配主机身份标识。由于节点是初次接入到归属域移动锚点,所以需要先向其归属域移动锚点发送请求分配主机身份标识。
进一步地,每个归属域内设置有一个主机身份标识地址池和主机位置标识地址池。本发明实施例中,地址池可以设置在归属域内的移动锚点上,也可以设置在归属域内负责地址池的服务器上,本发明实施例对地址池在归属域内具体的设置不做限定。
步骤202:归属域移动锚点为节点分配一个主机身份标识。
该步骤中,当归属域移动锚点收到节点发送分配主机身份标识的请求后,归属域移动锚点从主机身份标识地址池中为节点请求一个主机身份标识,并且将为节点请求到的主机身份标识返回给节点,由于节点在归属域网络内,可以将归属域移动锚点为节点分配的主机身份标识进行全局路由,同时可以将归属域移动锚点为节点分配的主机身份标识作为节点的主机位置标识。此时,节点的主机身份标识和主机位置标识是相同的。
步骤203:归属域移动锚点先向DNS发送查询请求。其中,查询请求中携带有所述节点的管理域域名,进一步地,所述管理域域名和本地主机名组成全球主机名。
步骤204:DNS返回的查询响应。其中,DNS接收到节点的归属域移动锚点发送的查询请求后,由于DNS中存储有<管理域域名,归属域映射服务器IP地址>之间的映射,所以DNS根据所述节点的管理域域名可以查询到节点的归属域映射服务器的IP地址,将查询到节点的归属域映射服务器的IP地址返回给节点的归属域移动锚点。
步骤205:节点的归属域移动锚点将节点的主机身份标识和主机位置标识确定绑定关系,存储到节点的归属域映射服务器。
在本发明实施例中,为了保持节点的归属域备份映射服务器和节点的归属域映射服务器之间数据的同步,当节点的归属域主映射服务器中数据有变化时,会向节点的归属域备份映射服务器发出变化内容同步消息。
进一步地,移动锚点为所述网络接入请求的节点分配主机身份标识后,会向所述网络接入请求的节点返回地址分配响应,其中,所述地址分配响应中携带有为所述网络接入请求的节点分配的主机身份标识。
其中,移动锚点向所述网络接入请求的节点返回地址分配响应,和移动锚点将为所述节点分配的主机身份标识发送给所述节点的归属域映射服务器,并指示所述节点的归属域映射服务器存储所述节点的主机身份标识和主机位置标识,可以是同时完成的;也可以是移动锚点先向所述网络接入请求的节点返回地址分配响应,然后将为所述节点分配的主机身份标识发送给所述节点的归属域映射服务器,并指示所述节点的归属域映射服务器存储所述节点的主机身份标识和主机位置标识;还可以是移动锚点先将为所述节点分配的主机身份标识发送给所述节点的归属域映射服务器,并指示所述节点的归属域映射服务器存储所述节点的主机身份标识和主机位置标识,然后向所述网络接入请求的节点返回地址分配响应;本发明实施例对这执行这两个步骤的先后顺序不做限定。
在本发明实施例中,归属域内设置有主机身份标识地址池和主机位置标识地址池,在运营商处还设置有预留地址池,其中预留地址池中的地址既可以作为主机身份标识,也可以作为主机位置标识,其中,预留地址池中预分配的第一地址类型标志的数量与第二地址类型标志的数量的比例,与主机身份标识的地址池中预分配的第一地址类型标志的数量与主机位置标识的地址池中预分配的第二地址类型标志的数量比例相等。进一步地,当需要调整主机身份标识时,可以将运营商处预留地址池中预留的第一地址类型标志添加到主机身份标识的地址池中;当需要调整主机位置标识时,可以将运营商处预留地址池中预留的第二地址类型标志添加到主机位置标识的地址池中。
参见图6,当节点初次接入拜访域时,该流程可包括:
步骤301,节点向拜访域移动锚点发送接入请求。
由于节点移动到拜访域移动锚点,所以节点归属域移动锚点为节点分配的主机身份标识失去了路由的能力,当节点移动到拜访域移动锚点后,需要向拜访域移动锚点发送接入请求。
步骤302,拜访域移动锚点为节点分配一个主机位置标识。
拜访域移动锚点接收到节点发送的接入请求后,拜访域移动锚点从主机位置标识地址池中为节点请求一个主机位置标识,并且将为节点请求到的主机位置标识返回给节点。由于节点已经移动到拜访域移动锚点,而节点归属域移动锚点为节点分配的主机身份标识失去了路由的能力,所以拜访域移动锚点为节点分配的主机位置标识可以进行路由。此时,节点的主机身份标识和主机位置标识是不相同的。
在本发明实施例中,拜访域内设置有主机身份标识地址池和主机位置标识地址池,在运营商处还设置有预留地址池,其中预留地址池中的地址既可以作为主机身份标识,也可以作为主机位置标识,其中,预留地址池中预分配的第一地址类型标志的数量与第二地址类型标志的数量的比例,与主机身份标识的地址池中预分配的第一地址类型标志的数量与主机位置标识的地址池中预分配的第二地址类型标志的数量比例相等。进一步地,当需要调整主机身份标识时,可以将运营商处预留地址池中预留的第一地址类型标志添加到主机身份标识的地址池中;当需要调整主机位置标识时,可以将运营商处预留地址池中预留的第二地址类型标志添加到主机位置标识的地址池中。
在本发明实施例中,拜访域移动锚点将节点分配的主机位置标识发送给所述节点的归属域映射服务器,并指示所述节点的归属域映射服务器将所述节点的主机身份标识所对应的主机位置标识更新为当前所分配的主机位置标识。
进一步地,在将节点主机位置标识发送给节点归属域映射服务器之前,需要先获得节点归属域映射服务器的IP地址。
步骤303,节点的拜访域移动锚点先向DNS发送查询请求。其中,查询请求中携带有节点的管理域域名,进一步地,所述管理域域名和本地主机名组成全球主机名。
步骤304,DNS返回的查询响应。其中,DNS接收到节点的拜访域移动锚点发送的查询请求后,由于DNS中存储有<管理域域名,DMS IP>之间的映射,所以DNS根据所述节点的管理域域名可以查询到节点的归属域映射服务器的IP地址,将查询到节点的归属域映射服务器的IP地址返回给节点的拜访域移动锚点。
步骤305,节点的拜访域移动锚点将节点的主机位置标识发送给所述节点的归属域映射服务器。所述节点的归属域映射服务器将接收到的主机位置标识替代所述节点的主机身份标识对应的主机位置标识。
在本发明实施例中,为了保持节点的归属域备份映射服务器和节点的归属域主映射服务器之间数据的同步,当节点的归属域主映射服务器中数据有变化时,会向节点的归属域 备份映射服务器发出变化内容同步消息。
本发明实施例中,为了增加可靠性或者实现负载分担,一个管理域中可设置多个DMS。当管理域中的一个DMS中的数据有变化后,会将数据同步给该管理域中的其他DMS,以使一个管理域中的所有DMS的数据保持同步。基于上述IPv6地址规划方法,本发明实施例还提供了一种地址获取方法。
参见图7,为本发明实施例提供的地址获取流程示意图。该流程可由移动锚点执行。所述移动锚点部署在接入网络的边缘路由器水平。该流程可包括:
步骤401,获取节点的全球主机名;
步骤402,根据所述节点的全球主机名获取所述节点的主机身份标识和主机位置标识;所述主机身份标识和所述主机位置标识均为IPv6地址,且作为主机身份标识的IPv6地址中包含第一地址类型标志,作为主机位置标识的IPv6地址中包含第二地址类型标志。
其中,步骤402可通过两次解析过程实现,具体的如图8所示,该两次解析过程可包括:
步骤4021,向DNS发送第一查询请求,所述第一查询请求中携带所述节点的管理域域名,其中,所述管理域域名和本地主机名组成全球主机名。
步骤4022,接收所述DNS返回的第一查询响应,所述第一查询响应中携带有所述DNS根据所述节点的管理域域名部分查询到的DMS的IP地址。
本发明实施例中借助DNS(但不仅局限于DNS)为不同的管理域进行解析查询服务,实现DMS网际IP地址的映射解析。
为了兼容现有的域名解析系统,每个管理域中只需将映射条目<管理域域名,DMS IP>注册到DNS中,而不再以主机为单位,向DNS中注册<域名,主机IP>的映射条目。根据GH中的管理域域名信息进行解析,即可获得本管理域中的主服务DMS的IP地址并将其返回。
因为DMS的IP地址几乎不变,这就维持了原有DNS保存静态结果且进行静态解析的特性。同时,由于同一管理域中,DMS的数量远远少于节点的数量,针对目前多数采用DNS存储<域名,主机身份标识>的方案来说,本发明实施例能大大降低DNS映射条目的规模。
步骤4023,根据查询到的DMS的IP地址,向所述节点的归属域DMS发送第二查询请求,所述第二查询请求中携带所述节点的全球主机名。
移动锚点收到DNS返回的DMS的IP地址后,为了进一步获得节点的主机身份标识和主机位置标识,该移动锚点根据该DMS IP地址向节点的归属域DMS发起第二次查询请求。DMS根据查询消息中携带的节点全球主机名中的本地主机名,将节点的本地主机名作为关键字进行查询,由于DMS维护该节点的主机身份标识和主机位置标识的映射关系, 因此DMS可以获取到该节点的主机身份标识和主机位置标识。
在本发明实施例中,DMS中存储了主机身份标识与主机位置标识的映射条目<本地主机名,主机身份标识,主机位置标识>,主要用于进行主机身份标识与主机位置标识的注册存储与映射解析,处理主机位置标识和主机身份标识的绑定更新等。
步骤4024,接收所述节点的归属域DMS返回的第二查询响应,所述第二查询响应中携带有所述节点的归属域DMS根据所述节点的全球主机名中的本地主机名部分查询到的主机身份标识和主机位置标识。
移动锚点接收到DMS返回的该节点的主机身份标识和主机位置标识后,缓存该节点的主机身份标识和主机位置标识的映射关系。
由于节点的移动性或多归属等特征,其主机位置标识可能会时常变化。为了维持节点间网络层通信的连续性,节点的归属域DMS需要维持其管辖域内的映射条目<主机身份标识,主机位置标识>,所以归属域DMS实现的是动态解析。归属域DMS的解析过程借助了DNS的思想,利用域名映射解析变化的IP地址,适合快速动态更新。且映射条目到全局DMS的映射存储与地理位置相关,相对于映射算法来决定某节点的<本地身份标识,本地位置标识>存储到哪个域映射服务器的方案,本发明实施例便于进行直接查询,可降低查询时延。
上述地址获取过程通常发生在通信连接建立过程中。下面结合图9至图11,对通信连接建立过程进行详细描述。
参见图9,当节点1向节点2发起通信连接建立过程时,该流程可包括:
步骤501:节点1向该节点的归属域移动锚点发送通信连接建立请求。其中,该请求中携带有节点2的全球主机名,节点2是节点1请求通信的对端节点。
步骤502:节点1的归属域移动锚点向DNS发送查询请求,其中,所述查询请求中携带节点2的管理域域名。进一步地,所述管理域域名和本地主机名组成全球主机名。
步骤503:DNS返回的查询响应,其中,DNS根据节点2的管理域域名查询得到节点2的归属域的DMS的IP地址,并将该DMS IP地址携带于查询响应消息返回给归属域移动锚点。该步骤的具体实现过程可参见前述实施例。
步骤504:节点1的归属域移动锚点根据DNS返回的查询响应中携带的DMS IP地址,向节点2的归属域移动锚点发起查询请求,查询请求中携带有节点2的全球主机名。
步骤505:节点2的归属域映射服务器返回的查询响应。其中,节点2的归属域移动锚点根据节点2的全球主机名中的本地主机部分查询到节点2的主机身份标识和主机位置标识,并将查询到的节点2的主机身份标识和主机位置标识携带与查询响应返回给节点1的归属域移动锚点。该步骤的具体实现过程可参见前述实施例。
步骤506:节点1的归属域移动锚点将节点2的主机身份标识与主机位置标识进行缓 存,并将节点2的主机身份标识返回给节点1。
步骤507:节点1的归属域移动锚点向节点2的归属域移动锚点发起通信连接建立请求,其中携带有节点1的主机身份标识与主机位置标识。
步骤508:节点2的归属域移动锚点收到节点1的归属域移动锚点发送的节点1的主机身份标识与主机位置标识后,将节点1的主机身份标识与主机位置标识进行缓存,并将节点1的主机身份标识发送给节点2。
步骤509:节点2将节点1的主机身份标识进行缓存,节点2与节点1之间建立通信连接。
当节点1与节点2之间建立通信连接之后,节点1和节点2之间可以进行通信。图10示出了两个节点间的通信过程。
如图10所示,该流程可包括:
步骤601:节点1的归属域移动锚点接收节点1发送的第一通信消息。节点1发送的第一通信消息中携带有节点1的主机身份标识和节点2的主机身份标识。
步骤602:节点1的归属域移动锚点根据本地缓存的节点1和节点2的主机身份标识与主机位置标识的映射关系,必要时将第一通信消息中节点1的主机身份标识转换节点1的主机位置标识,将第一通信消息中节点2的主机身份标识转换节点2的主机位置标识,然后将进行地址转换后的第一消息发送给节点2的归属域移动锚点。
步骤603:节点2的归属域移动锚点根据本地缓存的节点1和节点2的主机身份标识与主机位置标识的映射关系,必要时将第一通信消息中节点1的主机位置标识转换节点1的主机身份标识,将第一通信消息中节点2的主机位置标识转换节点2的主机身份标识,然后将进行地址转换后的第一消息发送给节点2。
若节点1与节点2通信过程中发生移动切换,节点1的主机位置标识则会发生变化。为维持节点1与节点2原有通信的连续性,需要进行相应的映射更新操作及切换控制过程,使得节点2或其他即将向节点1发起通信的节点可以找到节点1最新位置。具体场景及信令交互过程如图11所示:
步骤701:当节点1和节点2之间通信的过程中,节点1从归属域移动锚点移动到拜访域移动锚点,节点1的主机身份标识失去路由作用,节点1需要向拜访域移动锚点发出接入请求,参考图6和实施例节点1接入拜访域移动锚点的方法。
当节点1的拜访域移动锚点为节点1分配主机位置标识后,并将节点1的主机位置标识存储到节点1的归属域映射服务器之后,还包括以下步骤:
在步骤702中,节点1的拜访域移动锚点接收到节点1发送给节点2的通信消息,其中,通信消息中携带有节点1和节点2的主机身份标识,节点1的拜访域移动锚点,根据本地缓存的节点1和节点2的主机身份标识与主机位置标识的映射关系,将节点1的主机 身份标识转换节点1的主机位置标识,必要时将节点2的主机身份标识转换为节点2的主机位置标识,然后将进行地址转换后的通信消息发送给节点2的归属域移动锚点。
当节点2的归属域移动锚点接收到节点1的拜访域移动锚点发送的转换后的通信消息,将节点1的主机身份标识和新主机位置标识重新,然后节点2的归属域移动锚点根据本地缓存的节点1和节点2的主机身份标识与主机位置标识的映射关系,将通信消息中节点1的主机位置标识转换节点1的主机身份标识,必要时将通信消息中节点2的主机位置标识转换节点2的主机身份标识,然后将进行地址转换后的通信消息发送给节点2。
在步骤703中,节点1的拜访域移动锚点与节点1的归属域移动锚点之间进行通信信令交互。保证节点1的拜访域移动锚点能够收到节点1的归属域移动锚点转发的节点2的归属域移动锚点转发的节点2发送给节点1的通信消息。
当节点1的拜访域移动锚点与节点2的归属域移动锚点之间建立通信后,则将节点1的拜访域移动锚点与节点1的归属域移动锚点之间进行通信信令取消,并且释放节点1的归属域移动锚点。
本发明实施例中步骤702和步骤703没有先后顺序,可以先执行步骤702,再执行步骤703;也可以先执行步骤703,再执行步骤702;本发明对步骤的先后顺序不做限定。
本发明实施例中,所述主机身份标识和所述主机位置标识均为IPv6地址,且作为主机身份标识的IPv6地址中包含第一地址类型标志,作为主机位置标识的IPv6地址中包含第二地址类型标志,所述第一地址类型标志和第二地址类型标志具有不同的取值空间;所述第一地址类型标志和第二地址类型标志取值空间的确定与第一地址类型标志和第二地址类型标志的比例均可以根据运营商主体自身负载状况进行灵活设定与动态调整,而且第一地址类型标志和第二地址类型标志的比例也可根据移动节点与固定节点的比例进行灵活调整,从而使得IPv6地址从自身划分语法上支持移动性的同时,也解决了IP地址双重语义的问题。将为所述节点分配的主机身份标识或主机位置标识发送给所述节点的归属域映射服务器,以使所述节点的归属域映射服务器维护所述节点的主机身份标识和主机位置标识之间的对应关系。减少查询次数,提高查询效率。
针对上述方法流程,本发明实施例还提供一种地址分配装置和一种通信装置,这些设备的具体内容可以参照上述方法实施,在此不再赘述。
如图12所示,本发明实施例提供一种地址分配装置,包括:接收单元21、分配单元22、维护单元23和调整单元24。
接收单元21,用于接收网络接入请求;
分配单元22,用于根据所述网络接入请求为请求接入的节点分配主机身份标识或主机位置标识;其中,所述主机身份标识和所述主机位置标识均为IPv6地址,且作为主机身份标识的IPv6地址中包含第一地址类型标志,作为主机位置标识的IPv6地址中包含第二 地址类型标志;
维护单元23,用于将为所述节点分配的主机身份标识或主机位置标识发送给所述节点的归属域映射服务器,以使所述节点的归属域映射服务器维护所述节点的主机身份标识和主机位置标识之间的对应关系。
进一步地,所述接收单元21具体用于:接收节点发送的主机身份标识分配请求,所述节点归属于所述移动锚点;
所述分配单元22具体用于:根据所述身份标识分配请求为所述节点分配主机身份标识,并将所述节点的主机身份标识同时作为所述节点的主机位置标识使用;将所述节点的主机身份标识携带于响应消息发送给所述节点;
所述维护单元23具体用于:将为所述节点分配的主机身份标识发送给所述节点的归属域映射服务器,并指示所述节点的归属域映射服务器存储所述节点的主机身份标识和主机位置标识,其中,所述节点的主机位置标识与所述节点的主机身份标识相同。
进一步地,所述接收单元21具体用于:接收节点发送的接入请求,所述节点不归属于所述移动锚点;
所述分配单元22具体用于:根据所述接入请求为所述节点分配主机位置标识;
所述维护单元23具体用于:将为所述节点分配的主机位置标识发送给所述节点的归属域映射服务器,并指示所述节点的归属域映射服务器将所述节点的主机身份标识所对应的主机位置标识更新为当前所分配的主机位置标识。
进一步地,所述维护单元23还用于:向域名系统DNS发送查询请求,所述查询请求中携带所述节点的全球主机名;
接收所述DNS返回的查询响应,所述查询响应中携带有所述DNS根据所述节点的全球主机名中的管理域域名部分查询到的所述节点的归属域映射服务器的网际协议IP地址。
进一步地,所述分配单元22具体用于:根据所述网络接入请求,从主机身份标识的地址池中为所述节点选取主机身份标识;或者,根据所述网络接入请求,从主机位置标识的地址池中为所述节点选取主机位置标识;
其中,主机身份标识的地址池中预分配的第一地址类型标志的数量与主机位置标识的地址池中预分配的第二地址类型标志的数量,按照设定比例设置。
进一步地,还设置有预留地址池,所述预留地址池中包括主机身份标识和主机位置标识,其中,预留地址池中预分配的第一地址类型标志的数量与第二地址类型标志的数量,按照所述设定比例设置;
还包括调整单元24,所述调整单元24用于:将预留地址池中预留的第一地址类型标志添加到主机身份标识的地址池中,和/或,将预留地址池中预留的第二地址类型标志添加到主机位置标识的地址池中。
进一步地,所述第一地址类型标志或所述第二地址类型标志承载在所述IPv6地址的地址类型域中。
如图13所示,本发明实施例提供一种地址获取装置,该装置包括:第一获取单元31、第二获取单元32和发送单元33。
第一获取单元31,用于获取节点的全球主机名;
第二获取单元32,用于根据所述节点的全球主机名获取所述节点的主机身份标识和主机位置标识;所述主机身份标识和所述主机位置标识均为IPv6地址,且作为主机身份标识的IPv6地址中包含第一地址类型标志,作为主机位置标识的IPv6地址中包含第二地址类型标志,所述第一地址类型标志和第二地址类型标志具有不同的取值空间。
进一步地,所述第二获取单元32具有用于:
向域名系统DNS发送第一查询请求,所述第一查询请求中携带所述节点的全球主机名;
接收所述DNS返回的第一查询响应,所述第一查询响应中携带有所述DNS根据所述节点的全球主机名中的管理域域名部分查询到的域映射服务器的网际协议IP地址;
根据查询到的域映射服务器的的IP地址,向所述节点的归属域映射服务器发送查询请求,所述查询请求中携带所述节点的全球主机名;
接收所述节点的归属域映射服务器返回的第二查询响应,所述第二查询响应中携带有所述节点的归属域映射服务器根据所述节点的全球主机名中的本地主机名部分查询到的主机身份标识和主机位置标识。
进一步地,所述第一获取单元31具体用于:接收主叫节点发送的通信建立请求,获取所述通信建立请求中携带的被叫节点的全球主机名;
还包括:
发送单元33,用于在所述第二获取单元根据所述被叫节点的全球主机名获取所述被叫节点的主机身份标识和主机位置标识之后,将所述主叫节点的主机身份标识发送至所述被叫节点,将所述被叫节点的主机身份标识发送至所述主叫节点,以使所述被叫节点与所述主叫节点之间建立通信连接。
对于本实施例的一种地址分配装置,包括的接收通信单元、发送通信单元和通信建立单元。其中,上述单元可以设置在同一个实体装置内,也可以是多个独立设置的实体设备,本发明实施例不做具体的限定。
如图14所示,本发明实施例提供另一种地址分配装置,包括:处理器500,用于读取存储器520中的程序,执行下列过程:
通过收发机510接收网络接入请求;
根据所述网络接入请求为请求接入的节点分配主机身份标识或主机位置标识;其中, 所述主机身份标识和所述主机位置标识均为IPv6地址,且作为主机身份标识的IPv6地址中包含第一地址类型标志,作为主机位置标识的IPv6地址中包含第二地址类型标志;
通过收发机510将为所述节点分配的主机身份标识或主机位置标识发送给所述节点的归属域映射服务器,以使所述节点的归属域映射服务器维护所述节点的主机身份标识和主机位置标识之间的对应关系。
进一步地,所述处理器500通过收发机510接收节点发送的主机身份标识分配请求,所述节点归属于所述移动锚点;
所述处理器500根据所述身份标识分配请求为所述节点分配主机身份标识,并将所述节点的主机身份标识同时作为所述节点的主机位置标识使用;通过收发机510将所述节点的主机身份标识携带于响应消息发送给所述节点;
所述处理器500将为所述节点分配的主机身份标识,通过收发机510发送给所述节点的归属域映射服务器,并指示所述节点的归属域映射服务器存储所述节点的主机身份标识和主机位置标识,其中,所述节点的主机位置标识与所述节点的主机身份标识相同。
进一步地,所述处理器500通过收发机510接收节点发送的接入请求,所述节点不归属于所述移动锚点;
所述处理器500根据所述接入请求为所述节点分配主机位置标识;
所述处理器500通过收发机510将为所述节点分配的主机位置标识发送给所述节点的归属域映射服务器,并指示所述节点的归属域映射服务器将所述节点的主机身份标识所对应的主机位置标识更新为当前所分配的主机位置标识。
进一步地,所述处理器500通过收发机510向域名系统DNS发送查询请求,所述查询请求中携带所述节点的全球主机名;
接收所述DNS返回的查询响应,所述查询响应中携带有所述DNS根据所述节点的全球主机名中的管理域域名部分查询到的所述节点的归属域映射服务器的网际协议IP地址。
进一步地,所述处理器500根据所述网络接入请求,从主机身份标识的地址池中为所述节点选取主机身份标识;或者,根据所述网络接入请求,从主机位置标识的地址池中为所述节点选取主机位置标识;
其中,主机身份标识的地址池中预分配的第一地址类型标志的数量与主机位置标识的地址池中预分配的第二地址类型标志的数量,按照设定比例设置。
进一步地,还设置有预留地址池,所述预留地址池中包括主机身份标识和主机位置标识,其中,预留地址池中预分配的第一地址类型标志的数量与第二地址类型标志的数量,按照所述设定比例设置;
所述处理器500还用于:将预留地址池中预留的第一地址类型标志添加到主机身份标识的地址池中,和/或,将预留地址池中预留的第二地址类型标志添加到主机位置标识的地 址池中。
进一步地,所述第一地址类型标志或所述第二地址类型标志承载在所述IPv6地址的地址类型域中。
收发机510,用于在处理器500的控制下接收和发送数据。
其中,在图14中,总线架构可以包括任意数量的互联的总线和桥,具体由处理器500代表的一个或多个处理器和存储器520代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起,这些都是本领域所公知的,因此,本文不再对其进行进一步描述。总线接口提供接口。收发机510可以是多个元件,即包括发送机和收发机,提供用于在传输介质上与各种其他装置通信的单元。处理器500负责管理总线架构和通常的处理,存储器520可以存储处理器500在执行操作时所使用的数据。
本发明实施例提供另一种地址获取装置,该装置的结构可以为图14所示的结构,也可以为其他结构,例如,如图15所示,本发明实施例提供另一种地址获取装置包括:
处理器600,用于读取存储器620中的程序,执行下列过程:
通过收发机610获取节点的全球主机名;
根据所述节点的全球主机名获取所述节点的主机身份标识和主机位置标识;所述主机身份标识和所述主机位置标识均为IPv6地址,且作为主机身份标识的IPv6地址中包含第一地址类型标志,作为主机位置标识的IPv6地址中包含第二地址类型标志,所述第一地址类型标志和第二地址类型标志具有不同的取值空间。
进一步地,所述处理器600通过收发机610向域名系统DNS发送第一查询请求,所述第一查询请求中携带所述节点的全球主机名;
所述处理器600通过收发机610接收所述DNS返回的第一查询响应,所述第一查询响应中携带有所述DNS根据所述节点的全球主机名中的管理域域名部分查询到的域映射服务器的网际协议IP地址;
所述处理器600根据查询到的域映射服务器的的IP地址,向所述节点的归属域映射服务器发送查询请求,所述查询请求中携带所述节点的全球主机名;
所述处理器600通过收发机610接收所述节点的归属域映射服务器返回的第二查询响应,所述第二查询响应中携带有所述节点的归属域映射服务器根据所述节点的全球主机名中的本地主机名部分查询到的主机身份标识和主机位置标识。
进一步地,所述处理器600通过收发机610接收主叫节点发送的通信建立请求,获取所述通信建立请求中携带的被叫节点的全球主机名;
所述处理器600还用于在根据所述被叫节点的全球主机名获取所述被叫节点的主机身份标识和主机位置标识之后,通过收发机610将所述主叫节点的主机身份标识发送至所述 被叫节点,将所述被叫节点的主机身份标识发送至所述主叫节点,以使所述被叫节点与所述主叫节点之间建立通信连接。
收发机610,用于在处理器600的控制下接收和发送数据。
其中,在图15中,总线架构可以包括任意数量的互联的总线和桥,具体由处理器600代表的一个或多个处理器和存储器620代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起,这些都是本领域所公知的,因此,本文不再对其进行进一步描述。总线接口提供接口。收发机610可以是多个元件,即包括发送机和接收机,提供用于在传输介质上与各种其他装置通信的单元。针对不同的用户设备,用户接口630还可以是能够外接内接需要设备的接口,连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器600负责管理总线架构和通常的处理,存储器620可以存储处理器600在执行操作时所使用的数据。
本领域内的技术人员应明白,本发明的实施例可提供为方法、系统、或计算机程序产品。因此,本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本发明的优选实施例,但本领域内的技术人员一旦得知了基本创造性概 念,则可对这些实施例作出另外的变更和修改。所以,所附权利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和修改。
显然,本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样,倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包含这些改动和变型在内。

Claims (20)

  1. 一种地址分配方法,其特征在于,包括:
    接收网络接入请求;
    根据所述网络接入请求为请求接入的节点分配主机身份标识或主机位置标识;其中,所述主机身份标识和所述主机位置标识均为IPv6地址,且作为主机身份标识的IPv6地址中包含第一地址类型标志,作为主机位置标识的IPv6地址中包含第二地址类型标志;
    将为所述节点分配的主机身份标识或主机位置标识发送给所述节点的归属域映射服务器,以使所述节点的归属域映射服务器维护所述节点的主机身份标识和主机位置标识之间的对应关系。
  2. 如权利要求1所述的方法,其特征在于,所述接收网络接入请求,包括:
    移动锚点接收节点发送的主机身份标识分配请求,所述节点归属于所述移动锚点;
    所述根据所述网络接入请求为所述节点分配主机身份标识,包括:
    所述移动锚点根据所述身份标识分配请求为所述节点分配主机身份标识,将所述节点的主机身份标识携带于响应消息发送给所述节点,并将所述节点的主机身份标识同时作为所述节点的主机位置标识使用;
    所述将为所述节点分配的主机身份标识发送给所述节点的归属域映射服务器,包括:
    所述移动锚点将为所述节点分配的主机身份标识发送给所述节点的归属域映射服务器,并指示所述节点的归属域映射服务器存储所述节点的主机身份标识和主机位置标识,其中,所述节点的主机位置标识与所述节点的主机身份标识相同。
  3. 如权利要求1所述的方法,其特征在于,所述接收网络接入请求,包括:
    移动锚点接收节点发送的接入请求,所述节点不归属于所述移动锚点;
    所述根据所述网络接入请求为所述节点分配主机位置标识,包括:
    所述移动锚点根据所述接入请求为所述节点分配主机位置标识;
    所述将为所述节点分配的主机位置标识发送给所述节点的归属域映射服务器,包括:
    所述移动锚点将为所述节点分配的主机位置标识发送给所述节点的归属域映射服务器,并指示所述节点的归属域映射服务器将所述节点的主机身份标识所对应的主机位置标识更新为当前所分配的主机位置标识。
  4. 如权利要求1至3中任一项所述的方法,其特征在于,所述将为所述节点分配的主机身份标识或主机位置标识发送给所述节点的归属域映射服务器之前,还包括:
    向域名系统DNS发送查询请求,所述查询请求中携带所述节点的全球主机名;
    接收所述DNS返回的查询响应,所述查询响应中携带有所述DNS根据所述节点的全球主机名中的管理域域名部分查询到的所述节点的归属域映射服务器的网际协议IP地址。
  5. 如权利要求1至3中任一项所述的方法,其特征在于,所述根据所述网络接入请求为所述节点分配主机身份标识,包括:
    根据所述网络接入请求,从主机身份标识的地址池中为所述节点选取主机身份标识;
    所述根据所述网络接入请求为所述节点分配主机位置标识,包括:
    根据所述网络接入请求,从主机位置标识的地址池中为所述节点选取主机位置标识;
    其中,主机身份标识的地址池中预分配的第一地址类型标志数量与主机位置标识的地址池中预分配的第二地址类型标志数量,按照设定比例设置。
  6. 如权利要求5所述的方法,其特征在于,还设置有预留地址池,所述预留地址池中包括主机身份标识和主机位置标识,其中,预留地址池中预分配的第一地址类型标志的数量与第二地址类型标志的数量,按照所述设定比例设置;
    该方法还包括:
    将预留地址池中预留的第一地址类型标志添加到主机身份标识的地址池中,和/或,将预留地址池中预留的第二地址类型标志添加到主机位置标识的地址池中。
  7. 如权利要求1所述的方法,其特征在于,所述第一地址类型标志或所述第二地址类型标志承载在所述IPv6地址的地址类型域中。
  8. 一种地址获取方法,其特征在于,该方法包括:
    获取节点的全球主机名;
    根据所述节点的全球主机名获取所述节点的主机身份标识和主机位置标识;所述主机身份标识和所述主机位置标识均为IPv6地址,且作为主机身份标识的IPv6地址中包含第一地址类型标志,作为主机位置标识的IPv6地址中包含第二地址类型标志,所述第一地址类型标志和第二地址类型标志具有不同的取值空间。
  9. 如权利要求8所述的方法,其特征在于,所述根据所述节点的全球主机名获取所述节点的主机身份标识和主机位置标识,包括:
    向域名系统DNS发送第一查询请求,所述第一查询请求中携带所述节点的全球主机名;
    接收所述DNS返回的第一查询响应,所述第一查询响应中携带有所述DNS根据所述节点的全球主机名中的管理域域名部分查询到的域映射服务器的网际协议IP地址;
    根据查询到的域映射服务器的的IP地址,向所述节点的归属域映射服务器发送第二查询请求,所述第二查询请求中携带所述节点的全球主机名;
    接收所述节点的归属域映射服务器返回的第二查询响应,所述第二查询响应中携带有所述节点的归属域映射服务器根据所述节点的全球主机名中的本地主机名部分查询到的主机身份标识和主机位置标识。
  10. 如权利要求8或9所述的方法,其特征在于,所述获取节点的全球主机名,包括:
    接收主叫节点发送的通信建立请求,获取所述通信建立请求中携带的被叫节点的全球主机名;
    根据所述被叫节点的全球主机名获取所述被叫节点的主机身份标识和主机位置标识之后,所述方法还包括:
    将所述主叫节点的主机身份标识发送至所述被叫节点,将所述被叫节点的主机身份标识发送至所述主叫节点,以使所述被叫节点与所述主叫节点之间建立通信连接。
  11. 一种地址分配装置,其特征在于,包括:
    接收单元,用于接收网络接入请求;
    分配单元,用于根据所述网络接入请求为请求接入的节点分配主机身份标识或主机位置标识;其中,所述主机身份标识和所述主机位置标识均为IPv6地址,且作为主机身份标识的IPv6地址中包含第一地址类型标志,作为主机位置标识的IPv6地址中包含第二地址类型标志;
    维护单元,用于将为所述节点分配的主机身份标识或主机位置标识发送给所述节点的归属域映射服务器,以使所述节点的归属域映射服务器维护所述节点的主机身份标识和主机位置标识之间的对应关系。
  12. 如权利要求11所述的装置,其特征在于,所述接收单元具体用于:接收节点发送的主机身份标识分配请求,所述节点归属于所述移动锚点;
    所述分配单元具体用于:根据所述身份标识分配请求为所述节点分配主机身份标识,并将所述节点的主机身份标识同时作为所述节点的主机位置标识使用;将所述节点的主机身份标识携带于响应消息发送给所述节点;
    所述维护单元具体用于:将为所述节点分配的主机身份标识发送给所述节点的归属域映射服务器,并指示所述节点的归属域映射服务器存储所述节点的主机身份标识和主机位置标识,其中,所述节点的主机位置标识与所述节点的主机身份标识相同。
  13. 如权利要求11所述的装置,其特征在于,所述接收单元具体用于:接收节点发送的接入请求,所述节点不归属于所述移动锚点;
    所述分配单元具体用于:根据所述接入请求为所述节点分配主机位置标识;
    所述维护单元具体用于:将为所述节点分配的主机位置标识发送给所述节点的归属域映射服务器,并指示所述节点的归属域映射服务器将所述节点的主机身份标识所对应的主机位置标识更新为当前所分配的主机位置标识。
  14. 如权利要求11至13中任一项所述的装置,其特征在于,所述维护单元还用于:向域名系统DNS发送查询请求,所述查询请求中携带所述节点的全球主机名;
    接收所述DNS返回的查询响应,所述查询响应中携带有所述DNS根据所述节点的全球主机名中的管理域域名部分查询到的所述节点的归属域映射服务器的网际协议IP地址。
  15. 如权利要求11至13中任一项所述的装置,其特征在于,所述分配单元具体用于:根据所述网络接入请求,从主机身份标识的地址池中为所述节点选取主机身份标识;或者,根据所述网络接入请求,从主机位置标识的地址池中为所述节点选取主机位置标识;
    其中,主机身份标识的地址池中预分配的第一地址类型标志的数量与主机位置标识的地址池中预分配的第二地址类型标志的数量,按照设定比例设置。
  16. 如权利要求15所述的装置,其特征在于,还设置有预留地址池,所述预留地址池中包括主机身份标识和主机位置标识,其中,预留地址池中预分配的第一地址类型标志的数量与第二地址类型标志的数量,按照所述设定比例设置;
    还包括调整单元,所述调整单元用于:将预留地址池中预留的第一地址类型标志添加到主机身份标识的地址池中,和/或,将预留地址池中预留的第二地址类型标志添加到主机位置标识的地址池中。
  17. 如权利要求11所述的装置,其特征在于,所述第一地址类型标志或所述第二地址类型标志承载在所述IPv6地址的地址类型域中。
  18. 一种地址获取装置,其特征在于,该装置包括:
    第一获取单元,用于获取节点的全球主机名;
    第二获取单元,用于根据所述节点的全球主机名获取所述节点的主机身份标识和主机位置标识;所述主机身份标识和所述主机位置标识均为IPv6地址,且作为主机身份标识的IPv6地址中包含第一地址类型标志,作为主机位置标识的IPv6地址中包含第二地址类型标志,所述第一地址类型标志和第二地址类型标志具有不同的取值空间。
  19. 如权利要求18所述的装置,其特征在于,所述第二获取单元具有用于:
    向域名系统DNS发送第一查询请求,所述第一查询请求中携带所述节点的全球主机名;
    接收所述DNS返回的第一查询响应,所述第一查询响应中携带有所述DNS根据所述节点的全球主机名中的管理域域名部分查询到的域映射服务器的网际协议IP地址;
    根据查询到的域映射服务器的IP地址,向所述节点的归属域映射服务器发送第二查询请求,所述查询请求中携带所述节点的全球主机名;
    接收所述节点的归属域映射服务器返回的第二查询响应,所述第二查询响应中携带有所述节点的归属域映射服务器根据所述节点的全球主机名中的本地主机名部分查询到的主机身份标识和主机位置标识。
  20. 如权利要求18或19所述的装置,其特征在于,所述第一获取单元具体用于:接收主叫节点发送的通信建立请求,获取所述通信建立请求中携带的被叫节点的全球主机名;
    还包括:
    发送单元,用于在所述第二获取单元根据所述被叫节点的全球主机名获取所述被叫节点的主机身份标识和主机位置标识之后,将所述主叫节点的主机身份标识发送至所述被叫节点,将所述被叫节点的主机身份标识发送至所述主叫节点,以使所述被叫节点与所述主叫节点之间建立通信连接。
PCT/CN2015/092106 2014-12-11 2015-10-16 一种地址分配、获取方法及装置 WO2016091009A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410766245.5A CN104486457B (zh) 2014-12-11 2014-12-11 一种地址分配、获取方法及装置
CN201410766245.5 2014-12-11

Publications (1)

Publication Number Publication Date
WO2016091009A1 true WO2016091009A1 (zh) 2016-06-16

Family

ID=52760961

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/092106 WO2016091009A1 (zh) 2014-12-11 2015-10-16 一种地址分配、获取方法及装置

Country Status (2)

Country Link
CN (1) CN104486457B (zh)
WO (1) WO2016091009A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112468334A (zh) * 2020-11-13 2021-03-09 苏州浪潮智能科技有限公司 一种服务器配置方法、装置、设备及计算机可读存储介质

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106406793B (zh) * 2016-09-13 2019-09-17 广东威创视讯科技股份有限公司 节点机的标识配置方法和系统与ip地址分配方法和系统
CN106878973B (zh) * 2017-01-03 2019-08-30 电信科学技术研究院 一种网络标识映射方法及装置
CN106792657B (zh) * 2017-01-03 2019-09-17 电信科学技术研究院 一种支持身份与位置解耦的网络标识方法及装置
EP3451633B1 (en) 2017-08-30 2021-04-28 Canon Kabushiki Kaisha Image capturing apparatus, client apparatus, and method
CN108259218B (zh) * 2017-10-30 2021-04-27 新华三技术有限公司 一种ip地址分配方法和装置
CN109547535B (zh) * 2018-10-31 2021-11-02 创新先进技术有限公司 设备绑定方法、装置和系统
CN111416884B (zh) 2020-03-12 2021-08-31 苏州浪潮智能科技有限公司 Ctdb虚拟ip的分配方法、装置及分布式存储设备
CN114553819B (zh) * 2020-11-23 2023-07-25 中盈优创资讯科技有限公司 一种IPv6地址识别方法及装置
CN114710469B (zh) * 2020-12-16 2023-08-01 中盈优创资讯科技有限公司 一种ipv4地址合理化管理方法及装置
CN113452698A (zh) * 2021-06-25 2021-09-28 佛山市顺德区美的电子科技有限公司 一种终端身份分配方法、控制终端和受控设备
CN114338419B (zh) * 2021-12-15 2024-04-16 中电信数智科技有限公司 一种IPv6全球组网边缘节点监测及预警方法及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101483675A (zh) * 2008-01-11 2009-07-15 华为技术有限公司 一种网络设备查找方法和网络设备
CN102025791A (zh) * 2009-09-17 2011-04-20 中兴通讯股份有限公司 一种分配位置标识和报文发送的方法及系统
CN102123182A (zh) * 2011-04-09 2011-07-13 山东师范大学 一种基于ipv6地址的主机身份标识与位置标识分离的方法
CN102957621A (zh) * 2011-08-31 2013-03-06 上海贝尔股份有限公司 一种基于位置和身份标识分离的通信网络系统及其设备

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102056166B (zh) * 2009-10-27 2014-04-09 中兴通讯股份有限公司 一种基于ipsplit网络中多穴性的实现方法和系统
CN102238059B (zh) * 2010-04-20 2015-05-13 中兴通讯股份有限公司 数据报文处理方法、系统及接入服务节点

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101483675A (zh) * 2008-01-11 2009-07-15 华为技术有限公司 一种网络设备查找方法和网络设备
CN102025791A (zh) * 2009-09-17 2011-04-20 中兴通讯股份有限公司 一种分配位置标识和报文发送的方法及系统
CN102123182A (zh) * 2011-04-09 2011-07-13 山东师范大学 一种基于ipv6地址的主机身份标识与位置标识分离的方法
CN102957621A (zh) * 2011-08-31 2013-03-06 上海贝尔股份有限公司 一种基于位置和身份标识分离的通信网络系统及其设备

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112468334A (zh) * 2020-11-13 2021-03-09 苏州浪潮智能科技有限公司 一种服务器配置方法、装置、设备及计算机可读存储介质
CN112468334B (zh) * 2020-11-13 2022-05-24 苏州浪潮智能科技有限公司 一种服务器配置方法、装置、设备及计算机可读存储介质

Also Published As

Publication number Publication date
CN104486457A (zh) 2015-04-01
CN104486457B (zh) 2016-03-30

Similar Documents

Publication Publication Date Title
WO2016091009A1 (zh) 一种地址分配、获取方法及装置
CN112153098B (zh) 一种应用迁移方法及装置
US9419940B2 (en) IPv4 data center support for IPv4 and IPv6 visitors
CN109413640B (zh) 会话信息查询方法、网元及计算机存储介质
EP2756411B1 (en) Deterministic mapping
US20170155619A1 (en) Location-based domain name system service discovery
US8363663B2 (en) Methods and apparatus for routing data to nodes
US10511527B2 (en) Enhanced infrastructure routing with prefixed network addressing in content delivery networks
JP5680221B2 (ja) モバイル・ノードをネットワークに接続する方法
JP2013507801A (ja) Ipv4ネットワークと新しいネットワークとの相互通信の実現方法及びシステム
JP2013526107A (ja) データメッセージの処理方法、システム及びアクセスサービスノード
US20130176943A1 (en) System and Method for Distributed Mobility Management
US8705471B2 (en) Method and system for implementing ID/locator mapping
CN102918817B (zh) IPv6地址分配的方法及设备
JP2004242019A (ja) 移動通信制御システム、ネットワーク管理サーバ、モバイルノード、アクセスノード及びアンカーノード
CN109698868B (zh) Ip地址分配方法及装置、计算机程序及存储介质
JP4660379B2 (ja) ローミング移動ノードへの正確なアクセスのための方法、装置及びシステム
CN102958128B (zh) 为ue业务选择pdn连接的方法及装置
WO2017045197A1 (zh) 接入本地网络的方法和相关设备
CN106792657B (zh) 一种支持身份与位置解耦的网络标识方法及装置
WO2019179634A1 (en) Method and apparatus for dynamic network address translation
JP5342070B2 (ja) 次世代ネットワークでの情報インタラクションの実現方法及びシステム
WO2017147840A1 (zh) 消息路由方法、装置及直径路由实体
CN1260923C (zh) 实现建立随机隧道的方法
CN112311866A (zh) 面向服务的新型物联网体系结构

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

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

Country of ref document: EP

Kind code of ref document: A1