WO2016161765A1 - 发送、传递和获取能力的方法及装置 - Google Patents

发送、传递和获取能力的方法及装置 Download PDF

Info

Publication number
WO2016161765A1
WO2016161765A1 PCT/CN2015/089662 CN2015089662W WO2016161765A1 WO 2016161765 A1 WO2016161765 A1 WO 2016161765A1 CN 2015089662 W CN2015089662 W CN 2015089662W WO 2016161765 A1 WO2016161765 A1 WO 2016161765A1
Authority
WO
WIPO (PCT)
Prior art keywords
pcp
server
capability
bearer protocol
servers
Prior art date
Application number
PCT/CN2015/089662
Other languages
English (en)
French (fr)
Inventor
孟伟
王翠
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US15/561,070 priority Critical patent/US20180063254A1/en
Priority to EP15888318.1A priority patent/EP3264724B1/en
Publication of WO2016161765A1 publication Critical patent/WO2016161765A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • H04L43/0882—Utilisation of link capacity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/256—NAT traversal
    • H04L61/2564—NAT traversal for a higher-layer protocol, e.g. for session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Definitions

  • This application relates to, but is not limited to, the field of communications.
  • NAT Network Address Translation
  • WAN Access Wide Area Network
  • IP Internet Protocol
  • NAT peer-to-peer
  • Port Control Protocol is a key protocol in the NAT technology scenario. Its purpose is to provide a mechanism for dynamically creating mapping entries on NATs and firewalls to forward external networks to actively access intranet traffic.
  • PCP Port Control Protocol
  • a node of the NAT internal network receives traffic of the external network, if the internal node does not connect with the source of the traffic, the traffic is discarded on the NAT device.
  • the PCP technology is used to establish a NAT mapping entry on the NAT device, and when the traffic arrives, it can pass through the NAT device to reach the internal receiving node.
  • the PCP client can obtain the IP address of one or more PCP servers through the DHCP (Dynamic Host Configuration Protocol, including the DHCPv4 and DHCPv6) protocol or other bearer protocol options, and the PCP client is in these PCPs. Pick one of the servers as the server side that matches itself.
  • the related technology can only obtain the IP address of one or more PCP server terminals, and the PCP client cannot select a PCP server that is more suitable for itself according to the information.
  • This paper provides a method and device for transmitting, transmitting, and acquiring capabilities, which can provide a basis for the PCP client to select a server.
  • a method of transmitting capabilities including:
  • the port control protocol PCP server monitors its own PCP server capability indicator
  • the PCP server sends its own PCP server capability indicator to the bearer protocol server;
  • the PCP server capability indicator includes a PCP resource quantity and/or a PCP resource utilization rate.
  • a method of delivering capabilities including:
  • the bearer protocol server receives a PCP server capability indicator sent by one or more PCP servers, where the PCP server capability indicator includes a PCP resource quantity and/or a PCP resource utilization rate;
  • the PCP server capability information includes a capability value
  • the bearer protocol server After the bearer protocol server receives the PCP server capability indicator sent by one or more PCP servers,
  • the bearer protocol server sets a corresponding capability value according to the strength of the capability according to the received one or more PCP server capability indicators.
  • the PCP server capability information includes a capability value
  • the bearer protocol server After the bearer protocol server receives the PCP server capability indicator sent by one or more PCP servers,
  • the bearer protocol server uses the PCP server capability indicator as a capability value.
  • the method further includes:
  • the PCP server capability information should be selected according to the PCP server capability information, and one PCP server is selected to establish a PCP session.
  • a method of acquiring capabilities including:
  • the PCP client sends a bearer protocol request to the bearer protocol server;
  • one of the PCP servers is selected to establish a PCP session.
  • a transmitting capability device for a PCP server including:
  • the monitoring module is set to: monitor its own PCP server capability indicator;
  • the capability indicator sending module is configured to: send its own PCP server capability indicator to the bearer protocol server;
  • the PCP server capability indicator includes a PCP resource quantity and/or a PCP resource utilization rate.
  • a delivery capability device for a bearer protocol server including:
  • the first receiving module is configured to: receive a PCP server capability indicator sent by one or more PCP servers; the PCP server capability indicator includes a PCP resource quantity and/or a PCP resource utilization rate;
  • the second receiving module is configured to: receive a bearer protocol request sent by the PCP client, and notify the bearer protocol response sending module;
  • the bearer protocol response sending module is configured to: send, according to the notification of the second receiving module, the IP address of the one or more PCP servers and the PCP server capability information corresponding to the PCP server capability indicator to the PCP client.
  • the device further includes:
  • the capability value setting module is configured to: set a corresponding capability value according to the received one or more PCP server capability indicators, and send the response to the bearer protocol response sending module;
  • the PCP server capability information includes the capability value.
  • a device for acquiring capabilities, applied to a PCP client including:
  • the bearer protocol request sending module is configured to: send a bearer protocol request to the bearer protocol server;
  • the bearer protocol response receiving module is configured to: receive an IP address of one or more PCP servers returned by the bearer protocol server, and corresponding PCP server capability information;
  • the establishing module is configured to: according to the PCP server capability information, select one of the PCP servers to establish a PCP session.
  • a computer readable storage medium storing computer executable instructions for performing the method of any of the above.
  • the embodiment of the present invention solves the defect that the PCP client cannot know the PCP server capability in the related art by transmitting the related PCP server capability to the PCP client, thereby causing the PCP client to fail to select the PCP server, and selecting the server end for the PCP client. Provide a valid basis.
  • FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present invention.
  • FIG. 2 is a flowchart of a PCP server end according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a bearer protocol server end according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of a PCP client according to an embodiment of the present invention.
  • FIG. 5 is a diagram of interaction between a PCP client and a bearer protocol server according to an embodiment of the present invention
  • FIG. 6 is a schematic diagram of a location of a PCP server capability value in a bearer protocol packet according to an embodiment of the present invention
  • Figure 7 is a schematic view of a first embodiment of the present invention.
  • Figure 8 is a schematic view of the second embodiment of the present invention.
  • Figure 9 is a schematic view of the third embodiment of the present invention.
  • Figure 10 is a schematic view of the fourth embodiment of the present invention.
  • FIG. 11 is a schematic diagram of an apparatus for transmitting capability according to an embodiment of the present invention.
  • FIG. 12 is a schematic diagram of an apparatus for transmitting capability according to an embodiment of the present invention.
  • FIG. 13 is a schematic diagram of an apparatus for acquiring capability according to an embodiment of the present invention.
  • the PCP client can obtain the IP address of one or more PCP server terminals through the DHCP protocol or other bearer protocol options, and the PCP client selects one of the PCP servers as the server end that matches itself.
  • related technologies can only obtain the IP addresses of one or more PCP servers, but the capabilities and priorities of these PCP servers to support NAT cannot be obtained. In this case, the PCP client cannot correctly select the server based on the NAT capability.
  • a client application needs to apply for 10 NAT sessions.
  • the first public network resource utilization rate is 98%
  • the second public network resource utilization rate is only 10%.
  • the client should prefer to select a second PCP server for peer-to-peer communication.
  • the IP addresses of two PCP servers are sent to the client, but the client cannot make a correct choice.
  • an option for increasing the capability of the PCP server in the extended option of the bearer protocol is provided, which solves the defect that the PCP client cannot correctly select the server end in the related art.
  • the bearer protocol is a protocol other than the PCP, and the PCP client simultaneously functions as a client of the bearer protocol to perform the function performed by the bearer protocol.
  • DHCPv4 protocol a protocol other than the PCP
  • DHCPv6 protocol a protocol other than the PCP
  • neighbor discovery protocol a protocol other than the PCP
  • routing protocol a protocol other than the PCP
  • FIG. 1 it is a schematic diagram of an application scenario of an embodiment of the present invention, where one or more PCP servers (only two are shown in the figure, PCP server A and PCP server B may also be one or more in actual applications).
  • the capability is reported to the bearer protocol server, and the bearer protocol server sends the capability information to the PCP client through the bearer protocol message.
  • the PCP client selects a suitable PCP server to connect according to the information, such as the PCP client in the figure.
  • the PCP server B is selected.
  • Step 21 The PCP server monitors its own PCP server capability indicator.
  • Step 22 The PCP server sends its own PCP server capability indicator to the bearer protocol server.
  • the PCP server capability indicator includes a PCP resource quantity and/or a PCP resource utilization rate. That is, the PCP server sends at least one of its own PCP resource quantity and PCP resource utilization rate to the bearer protocol server.
  • the number of the PCP resources refers to the number of protocol ports owned by the PCP server
  • the PCP resource utilization refers to the percentage of the number of protocol ports used by the PCP server divided by the number of the above PCP resources.
  • the embodiment of the present invention may further include step 23, the PCP server determines whether the interval is up to time, and if so, performs steps 21 and 22; that is, the PCP server monitors its own PCP server capability indicator at a certain time interval. It is reported to the bearer protocol server periodically.
  • Step 31 The bearer protocol server receives the PCP server capability indicator sent by one or more PCP servers.
  • Step 32 When the bearer protocol server receives the bearer protocol request sent by the PCP client, the IP address of the one or more PCP servers and the corresponding PCP server capability information are sent to the PCP client.
  • the PCP server capability information corresponds to the PCP server capability indicator, and includes a capability value.
  • the principle of setting the capability value can be:
  • the bearer protocol server sets a corresponding capability value according to the strength of the capability according to the received one or more PCP server capability indicators; or the bearer protocol server directly uses the PCP server capability indicator as the capability value.
  • the bearer protocol server sorts according to the received one or more PCP server capability indicators according to the capability strength, and sets the corresponding PCP server capability value according to the sorted result.
  • the PCP server capability index is divided into different sections according to the strength of the capability, and the PCP server capability indicators located in different sections correspond to different capability values, and the like.
  • the bearer protocol server may be a network device such as a DHCP server, a router, a switch, or a firewall.
  • the bearer protocol server can also be a PCP server at the same time.
  • Step 41 The PCP client sends a bearer protocol request to the bearer protocol server.
  • Step 42 Receive an IP address of one or more PCP servers returned by the bearer protocol server and corresponding PCP server capability information.
  • Step 43 Select one of the PCP servers according to the PCP server capability information, and establish a PCP session.
  • the PCP client selects the PCP server according to the selection policy.
  • the selection policy may be the PCP server with the strongest selection capability, or the PCP server corresponding to the capability level according to the user level and the like.
  • the PCP client may be a network device such as a router, a switch, or a firewall; or may be a terminal such as a personal computer or a mobile phone.
  • the interaction between the PCP client and the bearer protocol server includes:
  • Step 1 The PCP client sends a bearer protocol request message to the bearer protocol server.
  • Step 2 The bearer protocol server encapsulates the IP address of the PCP server and the corresponding PCP server capability value into a bearer protocol response message.
  • Step 3 The bearer protocol server sends the bearer protocol response packet to the PCP client.
  • FIG. 7 is a schematic view of an embodiment of the present invention. As shown in Figure 7, the intranet users access the Internet users through NAT-A or NAT-B.
  • the home gateway acts as the PCP client
  • NAT-A and NAT-B act as the PCP server
  • the DHCP server acts as the server for the bearer protocol. Proceed as follows:
  • Step S101 The Internet user needs to access the intranet user through the firewall, and the intranet user needs to create a session on the NAT-A or the NAT-B.
  • Step S102 NAT-A has 10 public IP addresses, and 80% of them have already been used; NAT-B has 80 public IP addresses, and 1% has been used; NAT-A and NAT-B respectively Ability to send to the DHCP server;
  • Step S103 The DHCP server calculates NAT-A and NAT-B, and finds that NAT-B has the most remaining resources and the strongest capability. Therefore, DHCP sets the capability value of NAT-A to 1 according to the policy, and sets the capability value of NAT-B to 2;
  • Step S104 The home gateway obtains its own IP address through the DHCP protocol, and sends a DHCP request message.
  • Step S105 The DHCP server receives the packet sent by the home gateway, and encapsulates the IP address and the capability value of the NAT-A device, the IP address and the capability value of the NAT-B device in the DHCP response message option, and sends the message to the home gateway. ;
  • Step S106 The home gateway receives the DHCP response message, parses the IP address and capability value of the NAT-A and the NAT-B, selects the NAT-B as the PCP server according to the user policy, and creates a new session;
  • Step S107 After the session is established, the Internet user successfully accesses the intranet user actively through the established session;
  • FIG. 8 is a schematic diagram of Embodiment 2 of the present invention.
  • the intranet user is an IPv6 user. It communicates with Internet IPv4 users through NAT64-A or NAT64-B.
  • the intranet users act as PCP clients, and NAT64-A and NAT64-B act as PCP servers respectively.
  • the server acts as a server hosting the protocol. Proceed as follows:
  • Step S201 The Internet user needs to access the intranet user through the firewall, and the intranet user needs to Create a session on NAT64-A or NAT64-B;
  • Step S202 NAT64-A has 15 public IP addresses, and 60% of them have already been used; NAT64-B has 15 public IP addresses, and 50% have been used; NAT64-A and NAT-B respectively Ability to send to the access server;
  • Step S203 The access server calculates NAT64-A and NAT64-B, and finds that NAT64-B has the most remaining resources and the strongest capability. Therefore, DHCP sets the capability value of NAT64-A to 1 according to the policy, and sets the capability value of NAT64-B to 2;
  • Step S204 The intranet user performs Neighbor Discovery (Neighbor Discovery, ND) protocol to perform neighbor discovery and sends an ND packet.
  • Neighbor Discovery Neighbor Discovery, ND
  • Step S205 The access server receives the packet sent by the intranet user, and encapsulates the IP address and the capability value of the NAT64-A device, the IP address and the capability value of the NAT64-B device in the ND response packet option, and sends the packet to the ND response packet option.
  • Intranet user receives the packet sent by the intranet user, and encapsulates the IP address and the capability value of the NAT64-A device, the IP address and the capability value of the NAT64-B device in the ND response packet option, and sends the packet to the ND response packet option.
  • Step S206 The internal network user receives the ND response message, parses the IP address and capability value of the NAT64-A and the NAT64-B, selects the NAT64-B as the PCP server according to the user policy, and creates a new session;
  • Step S207 After the session is established, the Internet IPv4 user successfully accesses the intranet IPv6 user actively through the established session.
  • FIG. 9 is a schematic view of a third embodiment of the present invention.
  • the intranet user is an IPv4 user, and accesses the Internet user through the access router or the NAT-B.
  • the access router integrates the functions of the NAT-A (PCP server) and the bearer protocol server.
  • the intranet user acts as a PCP client, and NAT-B also acts as a PCP server. Proceed as follows:
  • Step S301 The Internet user needs to access the intranet user through the firewall, and the intranet user needs to create a session on the access router or NAT-B;
  • Step S302 The access router has 105 public IP addresses, and 60% of them have already been used; NAT-B has 150 public IP addresses, and 50% of them have been used; NAT-B sends its own capabilities to pick up Into the router;
  • Step S303 The access router acquires its own NAT-A and acquires the number of resources and resource utilization of the NAT-B. Therefore, the DHCP server of the access router will have the NAT-A capability value 0x693C, which The hexadecimal 0x69 indicates decimal 105, 0x3C indicates decimal 60, 0x693C indicates 105 public IP addresses and 60% usage; the NAT-B capability value is set to 0x9632, where hexadecimal 0x96 indicates decimal 150, 0x32 means decimal 50, 0x9632 means 150 public IP addresses and 50% usage.
  • Step S304 The mobile phone user of the intranet obtains its own IP address through the DHCP protocol, and sends a DHCP request message.
  • Step S305 The access router receives the packet sent by the intranet user, and encapsulates the IP address and the capability value of the access router, the IP address and the capability value of the NAT-B device in the DHCP response message option, and sends the packet to the internal device.
  • Network user
  • Step S306 The mobile phone user of the internal network receives the DHCP response message and parses the IP address and capability value of the access router and the NAT-B.
  • the intranet mobile phone user resolves its own user policy and finds that the mobile phone user belongs to a low-level mobile phone user. Therefore, the NAT-A with weak automatic selection capability is the access router as the PCP server end, and establishes a NAT session with the access router.
  • Step S307 After the session is established, the Internet user successfully accesses the intranet mobile phone user through the established session.
  • FIG. 10 is a schematic view of the fourth embodiment of the present invention.
  • intranet users can exchange Internet users with NAT-A, NAT-B, NAT-C, or NAT-D.
  • the home gateway acts as a PCP client, NAT-A, NAT-B, and NAT-C.
  • NAT-D as the PCP server, and the DHCP server as the server of the bearer protocol.
  • Step S401 The Internet user needs to access the intranet user through the firewall, and the intranet user needs to create a session on the NAT-A or the NAT-B.
  • Step S402 NAT-A has 10 public IP addresses, and 80% of them have already been used, and the remaining 2 resources; NAT-B has 20 public IP addresses, and 70% have been used, and the remaining 6 resources; NAT-C has 50 public IP addresses, and 20% have been used, leaving 40 resources; NAT-D has 40 public IP addresses, and 60% have been used, and the remaining 16 resources; NAT-A, NAT-B, NAT-C, and NAT-B send their capabilities to the DHCP server respectively;
  • Step S403 The DHCP server calculates NAT-A, NAT-B, NAT-C, and NAT-B, and divides the remaining resources into four grades.
  • the capability value is 1, and the remaining resources are 10 to 20.
  • the capacity value is 2, the remaining resources are between 20 and 30, the capability value is 3, the remaining resources are above 30, and the capability value is 4. Therefore, DHCP sets the NAT-A and NAT-B capability values to 1 according to the policy; the NAT-C capability value is set to 2; and the NAT-D capability value is set to 4.
  • Step S404 The home gateway obtains its own IP address through the DHCP protocol, and sends a DHCP request message.
  • Step S405 The DHCP server receives the packet sent by the home gateway, and sets the IP address and capability value of the NAT-A device, the IP address and capability value of the NAT-B device, the IP address and capability value of the NAT-C device, and NAT.
  • the IP address and capability value of the -D device are encapsulated in the DHCP response message option and sent to the home gateway.
  • Step S406 The home gateway receives the DHCP response message, and resolves the IP address and the capability value of the NAT-A, the NAT-B, the NAT-C, and the NAT-B, and selects the NAT-B as the PCP server according to the user policy, and creates a new one.
  • Step S407 After the session is established, the Internet user successfully accesses the intranet user actively through the established session;
  • the embodiment of the present invention further provides a device for transmitting, transmitting, and acquiring capabilities, where:
  • the transmitting capability device is applied to a PCP server, including:
  • the monitoring module 111 is configured to: monitor its own PCP server capability indicator;
  • the capability indicator sending module 112 is configured to: send its own PCP server capability indicator to the bearer protocol server;
  • the PCP server capability indicator includes a PCP resource quantity and/or a PCP resource utilization rate.
  • the device capable of transmitting capability is applied to a bearer protocol server, including:
  • the first receiving module 121 is configured to: receive a PCP server capability indicator sent by one or more PCP servers; the PCP server capability indicator includes a PCP resource quantity and/or a PCP resource utilization rate;
  • the second receiving module 122 is configured to: receive a bearer protocol request sent by the PCP client, and Notifying the bearer protocol response sending module;
  • the bearer protocol response sending module 123 is configured to: send, according to the notification of the second receiving module 122, the IP address of the one or more PCP servers and the PCP server capability information corresponding to the PCP server capability indicator to The PCP client.
  • the means for transferring the capability may further include:
  • the capability value setting module is configured to: set a corresponding capability value according to the received one or more PCP server capability indicators, and send the corresponding capability value to the bearer protocol response sending module 123; the PCP server capability information includes the capability value.
  • the capability value setting module may set a corresponding capability value according to the strength of the capability according to the received one or more PCP server capability indicators; or directly use the PCP server capability indicator as the capability value.
  • the device for acquiring capability is applied to a PCP client, including:
  • the bearer protocol request sending module 131 is configured to: send a bearer protocol request to the bearer protocol server;
  • the bearer protocol response receiving module 132 is configured to: receive an IP address of one or more PCP servers returned by the bearer protocol server, and corresponding PCP server capability information;
  • the selection establishing module 133 is configured to: according to the PCP server capability information, select one of the PCP servers to establish a PCP session.
  • the selection establishing module 133 may select a PCP server according to the selection policy.
  • the selection policy may be a PCP server with the strongest selection capability, or may select a PCP server corresponding to the capability level according to the user level or the like.
  • all or part of the steps of the foregoing embodiments may also be implemented by using an integrated circuit, and the steps may be separately fabricated into integrated circuit modules, or multiple modules thereof or The steps are made into a single integrated circuit module.
  • the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • the device/function module/functional unit in the above embodiment When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the embodiment of the present invention solves the defect that the PCP client cannot know the PCP server capability in the related art by transmitting the related PCP server capability to the PCP client, thereby causing the PCP client to fail to select the PCP server, and selecting the server end for the PCP client. Provide a valid basis.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Environmental & Geological Engineering (AREA)
  • Computer Security & Cryptography (AREA)
  • Multimedia (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本文公布一种发送、传递和获取能力的方法及装置，其中，一个或多个PCP服务器将自身的PCP服务器能力指标发送至承载协议服务器，承载协议服务器将相应的能力信息发送至PCP客户端，PCP客户端根据该能力信息选择合适的PCP服务器进行连接。

Description

发送、传递和获取能力的方法及装置 技术领域
本申请涉及但不限于通信领域。
背景技术
目前，相关技术中的网络地址转换(Network Address Translation，NAT)属于接入广域网(Wide Area Network，WAN)技术，是一种将私有(保留)地址转化为合法互联网协议(IP)地址的转换技术，其被广泛应用于各种类型的因特网接入方式和各种类型的网络中。NAT能够解决IP地址匮乏的问题。
但是NAT的应用带来了很多的问题，例如很多应用无法穿越NAT，外网的主机无法主动针对内网的主机进行访问，使得很多点对点(P2P)的应用受到限制。
端口控制协议(Port Control Protocol，PCP)是在NAT技术场景下的关键性协议，其目的在于提供一种在NATs和防火墙上动态创建映射条目从而转发外网主动访问内网流量的机制。当NAT内部网络的节点接收外部网络的流量时，如果内部节点没有和该流量的源端进行过连接，那么该流量在NAT设备上被丢弃。当流量经过NAT设备之前，使用PCP技术在NAT设备上建立关于该流量的NAT映射条目，当流量到来时，能够穿过NAT设备而到达到内部接收节点。
相关技术中，PCP客户端可以通过DHCP(Dynamic Host Configuration Protocol，动态主机配置协议，包括DHCPv4和DHCPv6)协议或者其他承载协议的选项获取一个或者多个PCP服务器端的IP地址，PCP客户端在这些PCP服务器中挑选一个作为与自身匹配的服务器端。在实际应用中，相关技术只能获取一个或者多个PCP服务器端的IP地址，PCP客户端无法依据该信息选择更适合自己的PCP服务器。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本文提供了一种发送、传递和获取能力的方法及装置，能够为PCP客户端选择服务器端提供依据。
一种发送能力的方法，包括：
端口控制协议PCP服务器监听自身的PCP服务器能力指标；
PCP服务器将自身的PCP服务器能力指标发送至承载协议服务器；
其中，所述PCP服务器能力指标包括PCP资源数量和/或PCP资源利用率。
一种传递能力的方法，包括：
承载协议服务器接收一个或多个PCP服务器发送的PCP服务器能力指标，所述PCP服务器能力指标包括PCP资源数量和/或PCP资源利用率；
当承载协议服务器接收到PCP客户端发来的承载协议请求，则将所述一个或者多个PCP服务器的IP地址以及与所述PCP服务器能力指标对应的PCP服务器能力信息，发送至所述PCP客户端。
可选地，所述PCP服务器能力信息包含能力值；
承载协议服务器接收一个或多个PCP服务器发送的PCP服务器能力指标之后，
所述承载协议服务器根据接收到的一个或多个PCP服务器能力指标，按照能力的强弱设置相应的能力值。
可选地，所述PCP服务器能力信息包含能力值；
承载协议服务器接收一个或多个PCP服务器发送的PCP服务器能力指标之后，
承载协议服务器将所述PCP服务器能力指标作为能力值。
可选地，所述方法还包括：
所述PCP客户端接收到所述一个或者多个PCP服务器的IP地址以及相 应的PCP服务器能力信息，根据所述PCP服务器能力信息，选择其中一个PCP服务器，建立PCP会话。
一种获取能力的方法，包括：
PCP客户端向承载协议服务器发送承载协议请求；
接收承载协议服务器返回的一个或者多个PCP服务器的IP地址以及相应的PCP服务器能力信息；
根据所述PCP服务器能力信息，选择其中一个PCP服务器，建立PCP会话。
一种发送能力的装置，应用于PCP服务器，包括：
监听模块，设置为：监听自身的PCP服务器能力指标；
能力指标发送模块，设置为：将自身的PCP服务器能力指标发送至承载协议服务器；
其中，所述PCP服务器能力指标包括PCP资源数量和/或PCP资源利用率。
一种传递能力的装置，应用于承载协议服务器，包括：
第一接收模块，设置为：接收一个或多个PCP服务器发送的PCP服务器能力指标；所述PCP服务器能力指标包括PCP资源数量和/或PCP资源利用率；
第二接收模块，设置为：接收PCP客户端发来的承载协议请求，并通知承载协议响应发送模块；
承载协议响应发送模块，设置为：根据所述第二接收模块的通知，将所述一个或者多个PCP服务器的IP地址以及与所述PCP服务器能力指标对应的PCP服务器能力信息，发送至所述PCP客户端。
可选地，所述装置还包括：
能力值设置模块，设置为：根据接收到的一个或多个PCP服务器能力指标，设置相应的能力值，发送至承载协议响应发送模块；
所述PCP服务器能力信息包含所述能力值。
一种获取能力的装置，应用于PCP客户端，包括：
承载协议请求发送模块，设置为：向承载协议服务器发送承载协议请求；
承载协议响应接收模块，设置为：接收承载协议服务器返回的一个或者多个PCP服务器的IP地址以及相应的PCP服务器能力信息；
选择建立模块，设置为：根据所述PCP服务器能力信息，选择其中一个PCP服务器，建立PCP会话。
一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述任一项的方法。
本发明实施例通过向PCP客户端传递相关的PCP服务器的能力，解决了相关技术中PCP客户端无法获知PCP服务器能力，从而导致PCP客户端无法选择PCP服务器的缺陷，为PCP客户端选择服务器端提供了有效的依据。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1是本发明实施例应用场景示意图；
图2是本发明实施例PCP服务器端的流程图；
图3是本发明实施例承载协议服务器端的流程图；
图4是本发明实施例PCP客户端的流程图；
图5是本发明实施例PCP客户端与承载协议服务器报文交互图；
图6是本发明实施例PCP服务器能力值在承载协议报文中的位置示意图；
图7是本发明实施例一示意图；
图8是本发明实施例二示意图；
图9是本发明实施例三示意图；
图10是本发明实施例四示意图；
图11是本发明实施例的发送能力的装置示意图；
图12是本发明实施例的传递能力的装置示意图；
图13是本发明实施例的获取能力的装置示意图。
本发明的实施方式
下文中将结合附图对本发明的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
相关技术中，PCP客户端可以通过DHCP协议或者其他承载协议的选项获取一个或者多个PCP服务器端的IP地址，PCP客户端在这些PCP服务器中挑选一个作为与自身匹配的服务器端。在实际应用中，相关技术只能获取一个或者多个PCP服务器端的IP地址，但是，无法获取这些PCP服务器端支持NAT的能力和优先级。在这种情况下，PCP客户端无法正确根据NAT能力对服务器进行选择。
例如，某个客户端应用需要申请10个NAT会话，此时，供选择的PCP服务器有2个，第一个公网资源利用率98％，第二个公网资源利用率只有10％。在这种情况下客户端应该优选选择第二个PCP服务器进行对等通信。但是相关技术中会将两个PCP服务器的IP地址都发送给客户端，客户端却无法做出正确选择。
在本发明实施例中，提供了一种在承载协议的扩展选项中，增加PCP服务器能力的选项，解决相关技术中PCP客户端无法正确选择服务器端的缺陷。
所述的承载协议为除PCP以外的一种协议，PCP客户端同时作为所述承载协议的客户端，完成所述承载协议执行的功能。例如DHCPv4协议、DHCPv6协议、邻居发现协议、路由协议等等。
如图1所示，为本发明实施例应用场景示意图，其中，一个或多个PCP服务器(图中仅示出两个，PCP服务器A和PCP服务器B，在实际应用中也可以为一个或多个)将自身的能力上报至承载协议服务器，承载协议服务器将该能力信息通过承载协议报文发送至PCP客户端，PCP客户端根据该信息选择合适的PCP服务器进行连接，比如本图中PCP客户端选择了PCP服务器B。
在本发明实施例中，针对PCP服务器端，如图2所示：
步骤21，PCP服务器监听自身的PCP服务器能力指标；
步骤22，PCP服务器将自身的PCP服务器能力指标发送至承载协议服务器；
其中，所述PCP服务器能力指标包括PCP资源数量和/或PCP资源利用率。即：PCP服务器将自身的PCP资源数量和PCP资源利用率至少之一发送给承载协议服务器。
所述PCP资源数量，是指PCP服务器所拥有的协议端口个数；
所述PCP资源利用率，是指PCP服务器已使用的协议端口数目除以上述PCP资源数量的百分比。
从图2可以看出，本发明实施例还可以包括步骤23，PCP服务器判断是否到间隔时间，如果到，则执行步骤21和22；也即PCP服务器以一定时间间隔监听自身的PCP服务器能力指标，定时上报至承载协议服务器。
如图3所示，在本发明实施例中，针对承载协议服务器端：
步骤31，承载协议服务器接收一个或多个PCP服务器发送的PCP服务器能力指标；
步骤32，当承载协议服务器接收到PCP客户端发来的承载协议请求，则将所述一个或者多个PCP服务器的IP地址以及相应的PCP服务器能力信息，发送至所述PCP客户端。
其中，PCP服务器能力信息与所述PCP服务器能力指标相对应，包含能力值。
该能力值的设置原则可以是：
所述承载协议服务器根据接收到的一个或多个PCP服务器能力指标，按照能力的强弱设置相应的能力值；或者，承载协议服务器直接将所述PCP服务器能力指标作为能力值。
当按照能力的强弱设置能力值时，可以采用如下方式：承载协议服务器根据接收到的一个或多个PCP服务器能力指标，按照能力强弱排序，并根据排序的结果设置相应的PCP服务器能力值；或者，将PCP服务器能力指标按照能力强弱划分不同的区间，位于不同区间的PCP服务器能力指标对应不同的能力值，等等。
所述承载协议服务器可以是DHCP服务器、路由器、交换机、防火墙等网络设备。
所述承载协议服务器也可以同时是PCP服务器。
如图4所示，在本发明实施例中，针对PCP客户端：
步骤41，PCP客户端向承载协议服务器发送承载协议请求；
步骤42，接收承载协议服务器返回的一个或者多个PCP服务器的IP地址以及相应的PCP服务器能力信息；
步骤43，根据所述PCP服务器能力信息，选择其中一个PCP服务器，建立PCP会话。
其中，PCP客户端根据选择策略选择PCP服务器，该选择策略可以是选择能力最强的PCP服务器，也可以是根据用户等级等原则，选择对应能力等级的PCP服务器。
所述PCP客户端可以是路由器、交换机、防火墙等网络设备；也可以是个人电脑、手机等终端。
如图5所示，PCP客户端与承载协议服务器之间交互包括：
步骤1，PCP客户端向承载协议服务器发送承载协议请求报文；
步骤2，承载协议服务器将PCP服务器的IP地址以及相应的PCP服务器能力值封装到承载协议响应报文；
步骤3，承载协议服务器将该承载协议响应报文发送至PCP客户端。
如图6所示，为PCP服务器能力值在承载协议报文中的位置示意图。
图7是本发明实施例一示意图。如图7所示，内网用户通过NAT-A或NAT-B与互联网用户互访，家庭网关作为PCP客户端，NAT-A和NAT-B分别作为PCP服务器，DHCP服务器作为承载协议的服务器。步骤如下：
步骤S101：互联网用户需要穿越防火墙访问内网用户，内网用户需要在NAT-A或者NAT-B上创建一个会话；
步骤S102：NAT-A拥有10个公网IP地址，并且已经有80％已经使用；NAT-B拥有80个公网IP地址，并且有1％已经使用；NAT-A和NAT-B分别把自身的能力发送到DHCP服务器；
步骤S103：DHCP服务器计算NAT-A和NAT-B，发现NAT-B剩余资源最多，能力最强。因此DHCP根据策略将NAT-A的能力值设置为1，NAT-B的能力值设置为2；
步骤S104：家庭网关通过DHCP协议获取自身的IP地址，发送DHCP请求报文；
步骤S105：DHCP服务器收到家庭网关发来的报文，把NAT-A设备的IP地址和能力值、NAT-B设备的IP地址和能力值封装在DHCP应答报文选项中，发送给家庭网关；
步骤S106：家庭网关收到DHCP应答报文，解析到NAT-A和NAT-B的IP地址和能力值，根据用户策略，选择NAT-B作为PCP服务器，并新建会话；
步骤S107：会话建立后，互联网用户通过建立的会话，成功主动访问内网用户；
图8是本发明实施例二的示意图。如图8所示，内网用户是IPv6用户，通过NAT64-A或NAT64-B与互联网IPv4用户互访，内网用户作为PCP客户端，NAT64-A和NAT64-B分别作为PCP服务器，接入服务器作为承载协议的服务器。步骤如下：
步骤S201：互联网用户需要穿越防火墙访问内网用户，内网用户需要在 NAT64-A或者NAT64-B上创建一个会话；
步骤S202：NAT64-A拥有15个公网IP地址，并且已经有60％已经使用；NAT64-B拥有15个公网IP地址，并且有50％已经使用；NAT64-A和NAT-B分别把自身的能力发送到接入服务器；
步骤S203：接入服务器计算NAT64-A和NAT64-B，发现NAT64-B剩余资源最多，能力最强。因此DHCP根据策略将NAT64-A的能力值设置为1，NAT64-B的能力值设置为2；
步骤S204：内网用户通过邻居发现(Neighbor Discovery，ND)协议进行邻居发现，发送ND报文；
步骤S205：接入服务器收到内网用户发来的报文，把NAT64-A设备的IP地址和能力值、NAT64-B设备的IP地址和能力值封装在ND应答报文选项中，发送给内网用户；
步骤S206：内网用户收到ND应答报文，解析到NAT64-A和NAT64-B的IP地址和能力值，根据用户策略，选择NAT64-B作为PCP服务器，并新建会话；
步骤S207：会话建立后，互联网IPv4用户通过建立的会话，成功主动访问内网IPv6用户。
图9是本发明实施例三的示意图。如图9所示，内网用户是IPv4用户，通过接入路由器或NAT-B与互联网用户互访，其中，接入路由器集成了NAT-A(PCP服务器)和承载协议服务器的功能。内网用户作为PCP客户端，NAT-B也作为PCP服务器。步骤如下：
步骤S301：互联网用户需要穿越防火墙访问内网用户，内网用户需要在接入路由器或者NAT-B上创建一个会话；
步骤S302：接入路由器拥有105个公网IP地址，并且已经有60％已经使用；NAT-B拥有150个公网IP地址，并且有50％已经使用；NAT-B把自身的能力发送到接入路由器；
步骤S303：接入路由器获取自身NAT-A及获取NAT-B的资源数目和资源利用率。因此接入路由器的DHCP服务端将NAT-A的能力值0x693C，其 中十六进制0x69表示十进制的105，0x3C表示十进制的60，0x693C表示105个公网IP地址和60％的使用率；NAT-B的能力值设置为0x9632，其中十六进制0x96表示十进制的150，0x32表示十进制的50，0x9632表示150个公网IP地址和50％的使用率。
步骤S304：内网手机用户通过DHCP协议获取自身的IP地址，发送DHCP请求报文；
步骤S305：接入路由器收到内网用户发来的报文，把接入路由器的IP地址和能力值、NAT-B设备的IP地址和能力值封装在DHCP应答报文选项中，发送给内网用户；
步骤S306：内网手机用户收到DHCP应答报文，解析到接入路由器和NAT-B的IP地址和能力值。内网手机用户解析自身的用户策略，发现该手机用户属于低等级手机用户，因此自动选择能力较弱的NAT-A也就是接入路由器作为PCP服务器端，并和接入路由器建立NAT会话。
步骤S307：会话建立后，互联网用户通过建立的会话，成功主动访问内网手机用户。
图10是本发明实施例四示意图。如图10所示，内网用户可以通过NAT-A、NAT-B、NAT-C或NAT-D与互联网用户互访，家庭网关作为PCP客户端，NAT-A、NAT-B、NAT-C和NAT-D分别作为PCP服务器，DHCP服务器作为承载协议的服务器。步骤如下：
步骤S401：互联网用户需要穿越防火墙访问内网用户，内网用户需要在NAT-A或者NAT-B上创建一个会话；
步骤S402：NAT-A拥有10个公网IP地址，并且已经有80％已经使用，剩余2个资源；NAT-B拥有20个公网IP地址，并且有70％已经使用，剩余6个资源；NAT-C拥有50个公网IP地址，并且有20％已经使用，剩余40个资源；NAT-D拥有40个公网IP地址，并且有60％已经使用，剩余16个资源；NAT-A、NAT-B、NAT-C和NAT-B分别把自身的能力发送到DHCP服务器；
步骤S403：DHCP服务器计算NAT-A、NAT-B、NAT-C和NAT-B，并将剩余资源分为四个档次，剩余资源少于10时能力值为1，剩余资源在10到20之间，能力值为2，剩余资源在20到30之间，能力值为3，剩余资源在30以上，能力值为4。因此，DHCP根据策略将NAT-A、NAT-B能力值设为1；NAT-C能力值设为2；NAT-D能力值设为4。
步骤S404：家庭网关通过DHCP协议获取自身的IP地址，发送DHCP请求报文；
步骤S405：DHCP服务器收到家庭网关发来的报文，把NAT-A设备的IP地址和能力值、NAT-B设备的IP地址和能力值、NAT-C设备的IP地址和能力值以及NAT-D设备的IP地址和能力值封装在DHCP应答报文选项中，发送给家庭网关；
步骤S406：家庭网关收到DHCP应答报文，解析到NAT-A、NAT-B、NAT-C和NAT-B的IP地址和能力值，根据用户策略，选择NAT-B作为PCP服务器，并新建会话；
步骤S407：会话建立后，互联网用户通过建立的会话，成功主动访问内网用户；
相应地，本发明实施例还提出了发送、传递、获取能力的装置，其中：
如图11所示，发送能力的装置，应用于PCP服务器，包括：
监听模块111，设置为：监听自身的PCP服务器能力指标；
能力指标发送模块112，设置为：将自身的PCP服务器能力指标发送至承载协议服务器；
其中，所述PCP服务器能力指标包括PCP资源数量和/或PCP资源利用率。
如图12所示，传递能力的装置，应用于承载协议服务器，包括：
第一接收模块121，设置为：接收一个或多个PCP服务器发送的PCP服务器能力指标；所述PCP服务器能力指标包括PCP资源数量和/或PCP资源利用率；
第二接收模块122，设置为：接收PCP客户端发来的承载协议请求，并 通知承载协议响应发送模块；
承载协议响应发送模块123，设置为：根据所述第二接收模块122的通知，将所述一个或者多个PCP服务器的IP地址以及与所述PCP服务器能力指标对应的PCP服务器能力信息，发送至所述PCP客户端。
所述传递能力的装置还可包括：
能力值设置模块，设置为：根据接收到的一个或多个PCP服务器能力指标，设置相应的能力值，发送至承载协议响应发送模块123；所述PCP服务器能力信息包含所述能力值。
该能力值设置模块可以根据接收到的一个或多个PCP服务器能力指标，按照能力的强弱设置相应的能力值；或者，直接将所述PCP服务器能力指标作为能力值。
如图13所示，获取能力的装置，应用于PCP客户端，包括：
承载协议请求发送模块131，设置为：向承载协议服务器发送承载协议请求；
承载协议响应接收模块132，设置为：接收承载协议服务器返回的一个或者多个PCP服务器的IP地址以及相应的PCP服务器能力信息；
选择建立模块133，设置为：根据所述PCP服务器能力信息，选择其中一个PCP服务器，建立PCP会话。
选择建立模块133可以根据选择策略选择PCP服务器，该选择策略可以是选择能力最强的PCP服务器，也可以是根据用户等级等原则，选择对应能力等级的PCP服务器。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计算机程序流程来实现，所述计算机程序可以存储于一计算机可读存储介质中，所述计算机程序在相应的硬件平台上(如系统、设备、装置、器件等)执行，在执行时，包括方法实施例的步骤之一或其组合。
可选地，上述实施例的全部或部分步骤也可以使用集成电路来实现，这些步骤可以被分别制作成一个个集成电路模块，或者将它们中的多个模块或 步骤制作成单个集成电路模块来实现。
上述实施例中的装置/功能模块/功能单元可以采用通用的计算装置来实现，它们可以集中在单个的计算装置上，也可以分布在多个计算装置所组成的网络上。
上述实施例中的装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。上述提到的计算机可读取存储介质可以是只读存储器，磁盘或光盘等。
工业实用性
本发明实施例通过向PCP客户端传递相关的PCP服务器的能力，解决了相关技术中PCP客户端无法获知PCP服务器能力，从而导致PCP客户端无法选择PCP服务器的缺陷，为PCP客户端选择服务器端提供了有效的依据。

Claims (11)

  1. 一种发送能力的方法，包括：
    端口控制协议PCP服务器监听自身的PCP服务器能力指标；
    PCP服务器将自身的PCP服务器能力指标发送至承载协议服务器；
    其中，所述PCP服务器能力指标包括PCP资源数量和/或PCP资源利用率。
  2. 一种传递能力的方法，包括：
    承载协议服务器接收一个或多个PCP服务器发送的PCP服务器能力指标，所述PCP服务器能力指标包括PCP资源数量和/或PCP资源利用率；
    当承载协议服务器接收到PCP客户端发来的承载协议请求，则将所述一个或者多个PCP服务器的IP地址以及与所述PCP服务器能力指标对应的PCP服务器能力信息，发送至所述PCP客户端。
  3. 如权利要求2所述的方法，其中，
    所述PCP服务器能力信息包含能力值；
    承载协议服务器接收一个或多个PCP服务器发送的PCP服务器能力指标之后，
    所述承载协议服务器根据接收到的一个或多个PCP服务器能力指标，按照能力的强弱设置相应的能力值。
  4. 如权利要求2所述的方法，其中，
    所述PCP服务器能力信息包含能力值；
    承载协议服务器接收一个或多个PCP服务器发送的PCP服务器能力指标之后，
    承载协议服务器将所述PCP服务器能力指标作为能力值。
  5. 如权利要求2～4中任意一项所述的方法，还包括：
    所述PCP客户端接收到所述一个或者多个PCP服务器的IP地址以及相应的PCP服务器能力信息，根据所述PCP服务器能力信息，选择其中一个 PCP服务器，建立PCP会话。
  6. 一种获取能力的方法，包括：
    PCP客户端向承载协议服务器发送承载协议请求；
    接收承载协议服务器返回的一个或者多个PCP服务器的IP地址以及相应的PCP服务器能力信息；
    根据所述PCP服务器能力信息，选择其中一个PCP服务器，建立PCP会话。
  7. 一种发送能力的装置，应用于PCP服务器，包括：
    监听模块，设置为：监听自身的PCP服务器能力指标；
    能力指标发送模块，设置为：将自身的PCP服务器能力指标发送至承载协议服务器；
    其中，所述PCP服务器能力指标包括PCP资源数量和/或PCP资源利用率。
  8. 一种传递能力的装置，应用于承载协议服务器，包括：
    第一接收模块，设置为：接收一个或多个PCP服务器发送的PCP服务器能力指标；所述PCP服务器能力指标包括PCP资源数量和/或PCP资源利用率；
    第二接收模块，设置为：接收PCP客户端发来的承载协议请求，并通知承载协议响应发送模块；
    承载协议响应发送模块，设置为：根据所述第二接收模块的通知，将所述一个或者多个PCP服务器的IP地址以及与所述PCP服务器能力指标对应的PCP服务器能力信息，发送至所述PCP客户端。
  9. 如权利要求8所述的装置，还包括：
    能力值设置模块，设置为：根据接收到的一个或多个PCP服务器能力指标，设置相应的能力值，发送至承载协议响应发送模块；
    所述PCP服务器能力信息包含所述能力值。
  10. 一种获取能力的装置，应用于PCP客户端，包括：
    承载协议请求发送模块，设置为：向承载协议服务器发送承载协议请求；
    承载协议响应接收模块，设置为：接收承载协议服务器返回的一个或者多个PCP服务器的IP地址以及相应的PCP服务器能力信息；
    选择建立模块，设置为：根据所述PCP服务器能力信息，选择其中一个PCP服务器，建立PCP会话。
  11. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1-6任一项的方法。
PCT/CN2015/089662 2015-04-09 2015-09-15 发送、传递和获取能力的方法及装置 WO2016161765A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/561,070 US20180063254A1 (en) 2015-04-09 2015-09-15 Method and Apparatus for Sending, Transferring and Acquiring Capability
EP15888318.1A EP3264724B1 (en) 2015-04-09 2015-09-15 Method and apparatus for sending, transferring and acquiring capability

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510166145.3A CN106161534B (zh) 2015-04-09 2015-04-09 发送、传递和获取能力的方法及装置
CN201510166145.3 2015-04-09

Publications (1)

Publication Number Publication Date
WO2016161765A1 true WO2016161765A1 (zh) 2016-10-13

Family

ID=57071731

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/089662 WO2016161765A1 (zh) 2015-04-09 2015-09-15 发送、传递和获取能力的方法及装置

Country Status (4)

Country Link
US (1) US20180063254A1 (zh)
EP (1) EP3264724B1 (zh)
CN (1) CN106161534B (zh)
WO (1) WO2016161765A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI776454B (zh) * 2021-04-08 2022-09-01 立新 陳 動態分配服務伺服器的方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102148767A (zh) * 2011-05-12 2011-08-10 杭州华三通信技术有限公司 一种基于nat的数据路由方法及其装置
CN102447630A (zh) * 2011-12-28 2012-05-09 中兴通讯股份有限公司 协议报文的传输方法、家庭网关及运营商级网络转换设备
WO2014047548A1 (en) * 2012-09-21 2014-03-27 Ixia Methods, systems, and computer readable media for providing mapping information associated with port control protocol (pcp) in a test environment
CN103906037A (zh) * 2012-12-25 2014-07-02 中兴通讯股份有限公司 采用端口控制协议完成网络地址转换保活的方法及设备

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6335927B1 (en) * 1996-11-18 2002-01-01 Mci Communications Corporation System and method for providing requested quality of service in a hybrid network
CN1852094B (zh) * 2005-12-13 2010-09-29 华为技术有限公司 网络业务应用账户的保护方法和系统
CN102664971B (zh) * 2012-04-11 2016-02-10 中兴通讯股份有限公司 网络地址资源管理方法、系统及外部地址资源服务器
CN103179639B (zh) * 2013-03-15 2015-12-02 华为技术有限公司 选择网络控制器的方法和站设备
CN103535015B (zh) * 2013-05-24 2016-11-23 华为技术有限公司 公网地址资源的管理方法、端口控制协议服务器及客户端
US10320676B2 (en) * 2014-02-28 2019-06-11 Cisco Technology, Inc. Smarter policy decisions based on metadata in data flows

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102148767A (zh) * 2011-05-12 2011-08-10 杭州华三通信技术有限公司 一种基于nat的数据路由方法及其装置
CN102447630A (zh) * 2011-12-28 2012-05-09 中兴通讯股份有限公司 协议报文的传输方法、家庭网关及运营商级网络转换设备
WO2014047548A1 (en) * 2012-09-21 2014-03-27 Ixia Methods, systems, and computer readable media for providing mapping information associated with port control protocol (pcp) in a test environment
CN103906037A (zh) * 2012-12-25 2014-07-02 中兴通讯股份有限公司 采用端口控制协议完成网络地址转换保活的方法及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3264724A4 *

Also Published As

Publication number Publication date
EP3264724B1 (en) 2019-06-26
US20180063254A1 (en) 2018-03-01
EP3264724A4 (en) 2018-04-11
EP3264724A1 (en) 2018-01-03
CN106161534A (zh) 2016-11-23
CN106161534B (zh) 2021-05-11

Similar Documents

Publication Publication Date Title
EP2608491B1 (en) Method, apparatus and system for allocating public IP address
Mortier et al. Control and understanding: Owning your home network
US8751614B2 (en) Providing virtualized visibility through routers
WO2016210196A1 (en) Media relay server
EP3298759A1 (en) Media session
CN105376299B (zh) 一种网络通信方法、设备及网络附属存储设备
EP2680491B1 (en) Method for establishing channel for managing an IPv4 terminal
JP5711392B2 (ja) Ｐｄｎ−ｇｗ内のｎａｔ／ｎａｐｔを伴うシナリオについてのｐｃｃサポートのための方法及び装置
JP5753172B2 (ja) ネットワークアドレス変換のための管理方法および管理デバイス
WO2016210202A1 (en) Media relay server
EP2896160B1 (en) Bandwidth probing messages
US20120136976A1 (en) Identification of a private device in a public network
KR20130052240A (ko) 네트워크 주소 변환기 통과 기법을 프로비저닝하기 위한 방법 및 장치
JP5948442B2 (ja) ネットワーク構造内のアプリケーション機能によって提供されるサービスへのユーザ側デバイスのアクセスを提供するための方法、及びネットワーク構造
US20140359163A1 (en) Methods and Systems for Enabling NAT Traversal
US20140372499A1 (en) Methods and Systems for Enabling NAT Traversal
Srirama et al. Tcp hole punching approach to address devices in mobile networks
WO2016161765A1 (zh) 发送、传递和获取能力的方法及装置
US20080046571A1 (en) Pervasive inter-domain dynamic host configuration
US20150098471A1 (en) Methods and Systems for Enabling NAT Traversal
WO2014169590A1 (zh) 一种数据业务通信方法、设备及系统
EP3044929B1 (en) A mobile-device based proxy for browser-originated procedures
US20140351453A1 (en) Node in a Network
US20140379785A1 (en) Server Communication
Ata et al. Architectural design of unified multiplex communications for one-time use of IP addresses

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15561070

Country of ref document: US

REEP Request for entry into the european phase

Ref document number: 2015888318

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE