[go: up one dir, main page]

WO2011069448A1 - Procédé de commande, dispositif et système de communication d'un tunnel direct - Google Patents

Procédé de commande, dispositif et système de communication d'un tunnel direct Download PDF

Info

Publication number
WO2011069448A1
WO2011069448A1 PCT/CN2010/079555 CN2010079555W WO2011069448A1 WO 2011069448 A1 WO2011069448 A1 WO 2011069448A1 CN 2010079555 W CN2010079555 W CN 2010079555W WO 2011069448 A1 WO2011069448 A1 WO 2011069448A1
Authority
WO
WIPO (PCT)
Prior art keywords
ggsn
rnc
network topology
topology information
address
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2010/079555
Other languages
English (en)
Chinese (zh)
Inventor
陈靖
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2011069448A1 publication Critical patent/WO2011069448A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a direct tunnel control method, apparatus, and communication system. Background technique
  • GPRS General Packet Radio Service
  • GGSN Gateway GPRS Support Node
  • the operator also needs to reduce equipment investment and operating expenses, as well as facilitate subsequent expansion.
  • the 3rd Generation Partnership Project (3GPP) has proposed a Direct Tunnel solution, which is a two-stage tunnel between the original RNC, SGSN and GGSN: between the RNC and the SGSN.
  • Tunnel the tunnel between the SGSN and the GGSN, cuts a tunnel, that is, directly establishes a tunnel between the RNC and the GGSN, so that the user plane completely skips the SGSN, thereby reducing the majority of the SGSN user plane resources and reducing the operation for the operator.
  • Investment and operating expenses can reduce user delay and improve user experience.
  • the scalability of the solution is good, and the expansion of the user plane no longer needs to upgrade the SGSN, but the core network needs to upgrade the GGSN and other devices.
  • the solution can separate the control plane from the user plane, so that it can be upgraded to the SAE network in the future.
  • the GGSN and the SGSN belong to the same Public Land Mobile Network (PLMN).
  • PLMN Public Land Mobile Network
  • the direct tunnel is enabled when the connection status between the RNC and the GGSN is normal according to the obtained network topology information.
  • the first processing unit is configured to enable the direct tunnel when the connection state between the RNC and the GGSN is normal according to the network topology information acquired by the acquiring unit.
  • the network topology information distribution unit is configured to provide the updated network topology information to the network topology information using device.
  • a network topology information processing device configured to collect network topology information and send network topology information Use the device for network topology information.
  • the network topology information is obtained, and then the direct tunnel is determined according to the network topology information. For example, when the connection state between the RNC and the GGSN is normal, the direct tunnel is enabled, because the solution is directly established. Tunnel-related factors, such as dynamic network topology information, are used as conditions for enabling direct tunneling. Therefore, it is possible to control whether direct tunneling is enabled more flexibly and efficiently than in the prior art.
  • Embodiment 1 is a flowchart of a method provided by Embodiment 1 of the present invention.
  • FIG. 5(c) is still another schematic structural diagram of a network topology information using device according to an embodiment of the present invention.
  • Figure 6 (a) is a schematic structural diagram of a network topology information processing device according to an embodiment of the present invention
  • Figure 6 (b) is another schematic structural diagram of a network topology information processing device according to an embodiment of the present invention
  • Figure 6 (c) is a schematic structural diagram of another network topology information processing device according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a communication system according to an embodiment of the present invention. Specific lung
  • Embodiments of the present invention provide a direct tunnel control method, apparatus, and communication system. The details are described below separately.
  • Embodiment 1
  • an embodiment of the present invention provides a method for controlling a direct tunnel, including:
  • the network topology information can reflect the composition and connection status of the entire network
  • the OSS system may also receive a request for an Internet Protocol (IP) address of the GGSN to be detected, and then return a list of IP addresses of the GGSN to be detected to the OSS system according to the received request, so as to The OSS system collects connection state information between the RNC and the GGSN according to the list.
  • IP Internet Protocol
  • a domain name resolution request with a direct tunnel identifier may also include:
  • connection state information indicates that the connection state between the RNC and the GGSN is normal, the direct tunnel is enabled
  • the method may further include step 103; as follows:
  • the corresponding processing can be as follows:
  • connection state information indicates that the connection state between the RNC and the GGSN is abnormal, a tunnel to the RNC is established and a tunnel to the GGSN is established.
  • the method may further include:
  • a message indicating that the connection status between the RNC and the GGSN is abnormal is generated, and a timer is started, and a direct tunnel is not initiated between the RNC and the GGSN within a preset time of the timer.
  • the recorded information indicating the abnormal connection state between the RNC and the GGSN can also be cleared.
  • the request for detecting the IP address of the GGSN may be sent to the RNC, and the detection result returned by the RNC is received. If the detection result indicates that the connection state between the RNC and the GGSN address is normal, Then, the direct tunnel is allowed to be enabled later; if the detection result indicates that the connection state between the RNC and the GGSN address is abnormal, the timer is continuously started.
  • the network topology information is obtained, and then the direct tunnel is determined according to the network topology information, that is, when the connection state between the RNC and the GGSN is determined to be normal, the direct tunnel is enabled, and vice versa. If the connection status between the RNC and the GGSN is abnormal, a normal two-stage tunnel is established, because the solution will be related to the establishment of a direct tunnel, such as a dynamic network extension.
  • the Pu information is used as a condition for enabling direct tunneling, so that it is possible to control whether or not the direct tunnel is enabled more flexibly and efficiently than the prior art.
  • the OSS system is used as a network topology information collection unit and a network topology information distribution unit of the network topology information processing device
  • the RNC is used as a network topology information execution unit of the network topology information processing device
  • the SGSN is used as the SGSN.
  • Network topology information uses devices.
  • the OSS system sends a request for the IP address of the GGSN to be probed to the SGSN.
  • step 201 is an optional step.
  • the SGSN After receiving the request for the IP address of the GGSN to be detected by the OSS system, the SGSN reports the IP address list of the GGSN to be detected to the OSS system according to the received request.
  • step 202 is an optional step.
  • the OSS system After receiving the IP address list of the GGSN to be detected sent by the SGSN, the OSS system requests the RNC to detect the IP address of the GGSN according to the IP address list of the GGSN to be detected.
  • step 203 is an optional step.
  • the RNC sends a GTPv1 message to the IP address of each GGSN, such as an Echo Request.
  • the GGSN may return an Echo Response to the RNC. Otherwise, if the RNC does not receive the Echo Response message returned by the GGSN, the RNC determines the self (ie, RNC) and the GGSN. The connection between the two is abnormal.
  • the RNC summarizes the connection between the IP address of the GGSN and the GGSN, and obtains the detection result of the IP address of the GGSN, and reports the detection result of the IP address of the GGSN to the OSS system.
  • the OSS system updates the connection state information between the RNC and the GGSN saved by the GGSN according to the detection result of the received IP address of the GGSN, and then sends the connection state information between the updated GGSN and the RNC to the SGSN.
  • the SGSN may determine whether the direct tunnel is enabled for the user, and may determine according to the connection status information, as follows: if the received connection status information indicates the RNC and the GGSN If the connection status is normal, you can enable direct tunneling for the user. If the received connection status information indicates that the connection status between the RNC and the GGSN is abnormal, the direct tunnel is not enabled for the user, but a normal two-stage tunnel is established, that is, a tunnel to the RNC is established and a tunnel to the GGSN is established.
  • the SGSN in this embodiment receives the connection state information between the RNC and the GGSN sent by the OSS system, and then determines whether to enable the direct tunnel according to the connection state information, that is, if the connection state information indicates the RNC and the GGSN.
  • the connection state information indicates the connection status between the RNC and the GGSN.
  • an ordinary two-stage tunnel is established, because the solution will be related to the establishment of a direct tunnel. That is, the connection state between the RNC and the GGSN serves as a condition for enabling the direct tunnel, so that it is possible to control whether or not the direct tunnel is enabled more flexibly and efficiently than the prior art.
  • Embodiment 3 Embodiment 3
  • the OSS system is also used as the network topology information collection unit of the network topology information processing device, and the SGSN is used as the network topology information usage device, which is different from the implementation two.
  • the GGSN is used as a network topology information execution unit of the network topology information processing device, and the DNS system is used as a network topology information distribution unit of the network topology information processing device.
  • the prerequisite is that the domain name record with the direct tunnel identifier is configured in the DNS system.
  • the domain name includes:
  • Access Point Name (APN, Access Point Name), used to identify GGSN
  • RNC identifier ID, Identity
  • Routing Area Code used to identify the RNC
  • the IP address of the GGSN corresponding to the domain name is recorded in the domain name record.
  • the SGSN can select the GGSN for the user by sending a domain name resolution request message to the DNS.
  • the OSS system sends a request for the IP address of the RNC to be probed to the SGSN.
  • step 301 is an optional step.
  • the SGSN After receiving the request for the IP address of the RNC to be detected by the OSS system, the SGSN reports the IP address list of the RNC to be probed to the OSS system according to the received request.
  • step 302 is an optional step.
  • the OSS system After receiving the IP address list of the RNC that needs to be detected by the SGSN, the OSS system requests the GGSN to detect the IP address of the RNC according to the IP address list of the RNC to be detected.
  • step 303 is an optional step.
  • the GGSN sends a GTPv1 message, such as an Echo Request message, to the IP address of each RNC.
  • the RNC may return an Echo Response message. Otherwise, if the GGSN does not receive the Echo Response message returned by the RNC, the shell 'j GGSN determines that the connection between itself (ie, GGSN) and the RNC is abnormal.
  • the GGSN aggregates the connection between the GGSN and the RNCs, and obtains the connection status information between the GGSN and each RNC, and reports the connection status information between the GGSN and each RNC as a detection result.
  • the GGSN aggregates the connection between the GGSN and the RNCs, and obtains the connection status information between the GGSN and each RNC, and reports the connection status information between the GGSN and each RNC as a detection result.
  • the OSS system receives the connection status information between the GGSN reported by the GGSN and each RNC, and updates the domain name record on the DNS system according to the connection status information between the received GGSN and the RNC:
  • the domain name record is kept unchanged.
  • the IP address of the GGSN in the corresponding domain name record is cleared.
  • the domain name includes:
  • APN used to identify GGSN
  • RNC ID or Routing Area Code used to identify RNC
  • the DNS system queries the domain name record according to the received domain name resolution request with the direct tunnel identifier, and then returns the IP address result of the GGSN corresponding to the domain name to the SGSN, as follows:
  • step 310 If the connection status between the RNC and the GGSN is abnormal, the IP address returned by the DNS system is null, then step 310 can be performed;
  • the IP address returned by the DNS system is not empty, that is, the IP address result of the GGSN corresponding to the domain name is returned, and the SGSN receives the IP address result that is not null. After that, a direct tunnel is established according to the result of the IP address;
  • the SGSN sends a domain name resolution request without a direct tunnel identifier to the DNS system.
  • the DNS system After receiving the domain name resolution request without the direct tunnel identifier, the DNS system queries the domain name record according to the domain name resolution request without the direct tunnel identifier, and returns the IP address result of the GGSN corresponding to the domain name to the SGSN.
  • the SGSN After receiving the IP address result, the SGSN does not enable the direct tunnel, but establishes a common two-stage tunnel for the user, that is, establishes a tunnel to the RNC and establishes a tunnel to the GGSN according to the IP address result.
  • the SGSN in this embodiment sends a domain name resolution request with a direct tunnel identifier to the DNS system, and after receiving the IP address result of the GGSN corresponding to the domain name returned by the DNS system, and then determining whether to enable the IP address result according to the result of the IP address.
  • a direct tunnel that is, if the IP address result is not empty, it indicates that the direct tunnel is enabled when the connection state between the RNC and the GGSN is normal. Otherwise, if the IP address result is empty, it indicates between the RNC and the GGSN. The connection status is abnormal, so it is determined that a common two-stage tunnel needs to be established.
  • the RNC is also used as the network topology information execution unit of the network topology information processing device.
  • the SGSN integrates the network extension.
  • the SGSN sends a radio network resource allocation request to the RNC, where the radio network resource allocation request carries the IP address of the GGSN. It should be noted that before the WLAN resource allocation request is sent to the RNC, the SGSN has communicated with the GGSN, but only the SGSN has not determined whether to establish a direct tunnel. Therefore, the SGSN can know the IP address of the GGSN.
  • the RNC After receiving the RRC resource allocation request, the RNC performs a connection state determination according to the IP address of the GGSN, that is, performs GTP path detection. For example, the RNC sends a GTPv1 message, such as an Echo Request message, to the GGSN corresponding to the IP address of the GGSN.
  • a GTPv1 message such as an Echo Request message
  • the GGSN If the connection status between the RNC and the GGSN IP address is normal, the GGSN returns an Echo Response message after receiving the Echo Request message sent by the RNC; otherwise, if the connection status between the RNC and the GGSN IP address is abnormal, the GGSN The Echo Request message sent by the RNC cannot be received, so that the GGSN does not return the Echo Response message to the RNC. Therefore, if the RNC does not receive the Echo Response message from the GGSN, the RNC can determine itself (ie, RNC) and the GGSN IP address. The connection between the two is broken. Of course, the RNC can also perform path detection on each GGSN connected to itself, and save the connection status as a detection result. After receiving the wireless network resource allocation request, the RNC can directly query the corresponding according to the wireless network resource allocation request. The detection result is recorded without path detection based on the radio network resource allocation request, and therefore steps 402 and 403 are optional steps.
  • step 405 If the RNC determines that the connection state between the self (ie, the RNC) and the IP address of the GGSN is normal, the RNC returns a successful wireless network resource allocation response to the SGSN, and after the SGSN receives the wireless network resource allocation response, the RNC and the RNC The direct tunnel between the GGSNs is successfully established. The process ends. Otherwise, if the RNC determines that the connection status between itself (ie, RNC) and the IP address of the GGSN is abnormal, the RNC returns a failure indicating a radio network resource allocation response message to the SGSN, indicating a path between the SGSN RNC and the IP address of the GGSN. If not, step 405 can be performed.
  • the SGSN may resend the radio network resource allocation request to the RNC, where the radio network resource allocation request carries the IP address of the SGSN.
  • the RNC After receiving the radio network resource allocation request that carries the IP address of the SGSN, the RNC returns a radio network resource allocation response to the SGSN according to the IP address of the SGSN. After receiving the radio network resource allocation response, the SGSN establishes between the RNC and the SGSN. And a common two-stage tunnel between the SGSN and the GGSN. At this time, the SGSN may also record information indicating that the connection status between the RNC and the GGSN is abnormal, and start a timer. The direct tunnel is not started between the RNC and the GGSN within a preset time of the timer. Of course, the premise is that a timer needs to be set inside the SGSN. Of course, in order to release the storage space, after the time preset by the timer expires, the SGSN can directly clear the recorded information indicating that the connection status between the RNC and the GGSN is abnormal.
  • the SGSN may further request the RNC to detect the IP address of the GGSN, that is, the SGSN may also send a request for detecting the IP address of the GGSN to the RNC.
  • the RNC After receiving the request for detecting the IP address of the GGSN, the RNC performs GTP path detection according to the IP address of the GGSN. For example, the RNC sends a GTPv1 message, such as an Echo Request message, to the GGSN corresponding to the IP address of the GGSN.
  • a GTPv1 message such as an Echo Request message
  • the GGSN may return an Echo Response to the RNC; otherwise, the GGSN does not return an Echo Response to the RNC; therefore, if the RNC receives the Echo Response returned by the GGSN, the RNC determines The connection state between the self (ie, RNC) and the GGSN IP address is normal. If the RNC does not receive the Echo Response returned by the GGSN, the RNC determines that the connection between itself (ie, the RNC) and the IP address of the GGSN is abnormal.
  • the 4ia RNC reports the detection result, that is, the connection status information between the RNC and the GGSN to the SGSN.
  • the SGSN may determine whether the direct tunnel is enabled for the user, and may determine according to the connection status information, as follows:
  • the received connection status information indicates between the RNC and the GGSN.
  • the connection status is normal, allowing subsequent direct tunnels to be enabled. In subsequent processes, the SGSN can enable direct tunneling for users if direct tunneling is required for the user.
  • the received connection status information indicates that the connection status between the RNC and the GGSN is abnormal, and the timer is continued to be started.
  • the SGSN does not enable the direct tunnel for the user. Instead, two ordinary tunnels are established, that is, two tunnels arriving at the RNC and the GGSN are respectively established.
  • the SGSN in this embodiment sends a radio network resource allocation request that carries the IP address of the GGSN to the RNC, and then receives the radio network resource allocation response returned by the RNC according to the IP address of the GGSN, according to the wireless network resource allocation response.
  • the network resource allocation response determines whether to enable the direct tunnel, that is, if the wireless network resource allocation response indicating success is received, the direct tunnel is enabled, and if the wireless network resource allocation response indicating the failure is received, the ordinary two-stage tunnel is established.
  • the embodiment of the present invention further provides a network extension information using device 500, as shown in FIG. 5 (a), FIG. 5 (b) and FIG. 5 (c), the network
  • the topology information using device 500 includes an obtaining unit 501 and a first processing unit 502;
  • the obtaining unit 501 is configured to acquire network topology information.
  • the first processing unit 502 is configured to determine, according to the network topology information acquired by the obtaining unit 501, that the connection state between the wireless network controller RNC and the gateway general packet radio service support node GGSN is normal, and enable the direct tunnel;
  • the network topology information using device 500 may further include a second processing unit 503;
  • the second processing unit 503 is configured to determine, according to the network topology information acquired by the obtaining unit 501, that the connection state between the RNC and the GGSN is abnormal, establish a tunnel that reaches the RNC, and establish a tunnel that reaches the GGSN.
  • the network topology information using device 500 may specifically be an SGSN.
  • the network topology information collection unit and the network topology information distribution unit of the network topology information processing device may be specifically the OSS system A900, and the network topology information execution unit of the network topology information processing device. Specifically, it may be an RNC, and the network topology information using device 500 may specifically be an SGSN, and the respective units in the network topology information using device 500 may specifically be as follows:
  • the obtaining unit 501 is specifically configured to receive connection state information between the RNC and the GGSN sent by the OSS system A900.
  • the first processing unit 502 is specifically configured to determine that the connection status information received by the obtaining unit 501 indicates that the direct connection is enabled when the connection status between the RNC and the GGSN is normal.
  • the second processing unit 503 is specifically configured to determine that the connection status information received by the obtaining unit 501 indicates that the connection status between the RNC and the GGSN is abnormal, establish a tunnel to the RNC, and establish a tunnel to reach the GGSN.
  • the network topology information using device 500 may further include a first receiving unit A504 and a first sending unit A505.
  • the first receiving unit A504 is configured to receive, by the OSS system A900, a request for an Internet Protocol IP address of the GGSN to be detected;
  • the first sending unit A505 is configured to return, according to the request received by the first receiving unit A504, the IP address list of the GGSN to be detected to the OSS system A900, so that the OSS system A900 collects connection state information between the RNC and the GGSN according to the list.
  • the network topology information collection unit of the network topology information processing device may be an OSS system, and the network topology information execution unit of the network topology information processing device may be a GGSN, a network topology.
  • the network topology information distribution unit of the information processing device may be specifically a DNS system B900, and the network topology information usage device 500 may be an SGSN.
  • the specific units in the network topology information usage device 500 may be specifically as follows:
  • the DNS system B900 is also shown in Figure 5 (b).
  • the obtaining unit 501 may include a domain name resolution request subunit B5011 and an address result receiving subunit B5012;
  • the domain name resolution request sub-unit B5011 is configured to send a direct tunnel identifier to the DNS system B900.
  • the address result receiving sub-unit B5012 is configured to receive an IP address result of the GGSN corresponding to the domain name returned by the DNS system B900 according to the domain name resolution request received by the domain name resolution request sub-unit B5011 after querying the domain name record;
  • the first processing unit 502 is specifically configured to enable a direct tunnel according to the IP address result when the IP address result received by the address result receiving subunit B5012 is not empty;
  • the second processing unit 503 is specifically configured to: when the IP address result received by the address result receiving subunit B5012 is null, send a domain name resolution request without a direct tunnel identifier, and receive an IP of the GGSN corresponding to the domain name returned by the DNS system. The result of the address is then established based on the result of the IP address to establish a tunnel to the RNC and establish a tunnel to the GGSN.
  • the network topology information using device 500 may further include a second receiving unit B504 and a second sending unit B505;
  • a second receiving unit B504 configured to receive, by the OSS system, a request for an IP address of the RNC to be detected
  • the second sending unit B505 is configured to return, according to the request received by the second receiving unit B504, the IP address list of the RNC to be detected to the OSS system, so that the OSS system collects the connection status information between the RNC and the GGSN according to the list, and then updates Domain name record in DNS system B900.
  • the network topology information execution unit of the network topology information processing device may specifically be an RNC, and the network topology information using device 500 and the network topology information collecting unit of the network topology information processing device And the network topology information distribution unit may be specifically integrated in the SGSN.
  • each unit in the network topology information using device 500 may specifically be as follows:
  • the obtaining unit 501 may include a resource allocation request subunit C5011 and an allocation response receiving subunit C5012;
  • a resource allocation request sub-unit C5011 configured to send a radio network resource allocation request to the RNC, where the radio network resource allocation request carries an IP address of the GGSN;
  • the allocation response receiving subunit C5012 is configured to receive the wireless network resource returned by the RNC according to the IP address of the GGSN received by the resource allocation request subunit C5011.
  • the first processing unit 502 is specifically configured to enable the direct tunnel when the allocation response receiving subunit C5012 receives the wireless network resource allocation response indicating success;
  • the second processing unit 503 is specifically configured to receive the indication loss in the allocation response receiving subunit C5012. When the failed wireless network resource allocation response, a tunnel to the RNC is established and a tunnel to the GGSN is established.
  • the network topology information using device 500 may further include a third processing unit C504;
  • the third processing unit C504 is configured to: when the allocation response receiving subunit C5012 receives the wireless network resource allocation response indicating the failure, record the abnormal connection status between the RNC and the GGSN, and start a timer, which is preset by the timer. During the set time, no direct tunnel is initiated between the RNC and the GGSN. Of course, in order to release the storage space, after the time preset by the timer expires, the SGSN can also directly clear the recorded information indicating that the connection status between the RNC and the GGSN is abnormal.
  • the network topology information using device 500 further includes a fourth processing unit C505;
  • the network topology information collecting unit 602 is configured to receive the report reported by the network topology information execution unit 601.
  • the network topology information detection result is updated, and the network topology information saved by the network topology information distribution unit 603 is updated according to the received network topology information detection result;
  • the network topology information execution unit 601 is specifically a radio network controller RNC. At this time, the network topology information execution unit 601 may include a first probe subunit A6011 and a first summary subunit A6013. And the first reporting subunit A6013;
  • the first summary sub-unit A6012 is configured to perform a summary according to the connection between the RNC and each GGSN determined by the first detecting sub-unit A6011, to obtain a detection result of the IP address of the GGSN;
  • the first reporting sub-unit A6013 is configured to report the detection result of the IP address of the GGSN obtained by the first summary sub-unit A6012 to the network topology information collecting unit 602.
  • the first receiving sub-unit A6021 is configured to receive the network topology information executing unit 601, for example, the first first update sub-unit A6022, configured to update the network topology information according to the IP address result of the GGSN received by the first receiving sub-unit A6021. Connection status information between the RNC and the GGSN held by the distribution unit 603
  • the second reporting sub-unit B6013 is specifically configured to report the connection status information between the GGSN obtained by the second summary sub-unit B6012 and each RNC to the network topology information collecting unit 602.
  • the network topology information collecting unit 602 may include a second receiving subunit B6021 and a second updating subunit B6022;
  • the second receiving sub-unit B6021 is configured to receive the network topology information executing unit 601, and specifically, the second update sub-unit B6022, configured to update the connection status information between the GGSN and each RNC received by the second receiving sub-unit B6021.
  • the network topology information distribution unit 603 is configured to: when receiving the domain name resolution request with the direct tunnel identifier sent by the network topology information using device, send the IP address result of the GGSN corresponding to the domain name to the network topology according to the updated domain name record Information is used by the device.
  • the network topology information execution unit 601 may specifically be an RNC, and the network topology information receiving unit 602 and the network topology information distribution unit 603 may be integrated into the network topology information using device 500.
  • the network topology information execution unit 601 may include a receiving subunit C6011, a third detecting subunit C6012, and a third reporting subunit C6013;
  • the third detecting sub-unit C6012 is configured to send a response request to the GGSN according to the IP address of the GGSN received by the receiving sub-unit C6011. If the response response returned by the GGSN is received, it is determined that the connection between the RNC and the GGSN is normal, if not received. Responding to the response returned by the GGSN, determining that the connection between the RNC and the GGSN is abnormal;
  • the 601 can detect the network topology information, and report the network topology information detection result to the network topology information collection unit 602.
  • the network topology information collection unit 602 saves the network topology saved by the network topology information distribution unit 603.
  • the information is updated, and when the network topology information usage device needs to determine whether to enable the direct tunnel, the network topology information distribution unit 603 sends the network topology information to the network topology information using device, so that the network topology information using device Determining whether to enable the direct tunnel according to the network topology information. Since the solution will be related to establishing a direct tunnel, for example, the dynamic network topology information is used as a condition for enabling direct tunneling, therefore, compared with the prior art, It is more flexible and efficient to control whether direct tunneling is enabled.
  • Example VII Example VII.
  • the embodiment of the present invention further provides a communication system.
  • the communication system includes a network topology information using device 500 and a network topology information processing device 600;
  • the network topology information using device 500 is configured to obtain the network topology information from the network topology information processing device 600, and determine that the connection state between the RNC and the GGSN is normal according to the obtained network topology information, and enable the direct tunnel;
  • the network topology information processing device 600 is configured to collect network topology information, and send network topology information to the network topology information using device 500.
  • the network topology information using device 500 is further configured to determine, when the connection state between the RNC and the GGSN is abnormal according to the obtained network topology information, establish a tunnel to the RNC and establish a tunnel to reach the GGSN.
  • the information using device 50 may be as follows: Step A1, the OSS system sends a request for the IP address of the GGSN to be probed to the SGSN. Step A2: The SGSN reports the IP address list of the GGSN to be probed to the OSS system according to the received request. Step A3: The OSS system requests the RNC to detect the IP address of the GGSN according to the IP address list of the GGSN that needs to be detected.
  • Step A4 The RNC sends a GTPv1 to the IP address of each GGSN. For example, Echo Request Step A5. If the connection between the GGSN and the RNC is normal, the GGSN may return an Echo Response to the RNC. Otherwise, if the RNC does not receive the Echo Response message returned by the GGSN. Then, the RNC determines that the connection between the self (ie, RNC) and the GGSN is abnormal.
  • Step A6 The RNC summarizes the connection between itself (ie, RNC) and the IP address of each GGSN, and reports it to the OSS system to update the connection status information between the RNC and the GGSN saved by the OSS system.
  • the direct tunnel can be enabled for the user. If the received connection status information indicates that the connection status between the RNC and the GGSN is abnormal, the direct tunnel is not enabled for the user, but the tunnel to the RNC is established and the tunnel to the GGSN is established.
  • Step B1 The OSS system sends a request for the IP address of the RNC to be probed to the SGSN.
  • Step B2 The SGSN reports the IP address of the RNC to be probed to the OSS system according to the received request. A list of addresses.
  • Step B3 The OSS system requests the GGSN to detect the IP address of the RNC according to the IP address list of the RNC that needs to be detected.
  • Step B4 The GGSN sends a GTPv1 message, such as an Echo Request message, to the IP address of each RNC. Step If the connection between the GGSN and the RNC is normal, the RNC may return an Echo Response message.
  • Step B6 The GGSN aggregates the connection status between itself (ie, GGSN) and the IP address of each RNC, and reports it to the OSS system.
  • Step B7 The OSS system updates the domain name record on the DNS system according to the received connection status information between the GGSN and the RNC, as follows: If the received connection status information indicates that the connection status between the RNC and the GGSN is normal, the domain name record is maintained. constant.
  • step B8 when the SGSN selects the GGSN for the user, the SGSN sends a domain name resolution request with a direct tunnel identifier to the DNS system.
  • Step B9 The DNS system receives the domain name resolution request with the direct tunnel identifier.
  • Step B 10 SGSN sends without The domain name resolution request of the direct tunnel identifier is given to the DNS system.
  • Step B11 The DNS system queries the domain name according to the domain name resolution request without the direct tunnel identifier. Record, return the IP address result of the GGSN corresponding to the domain name to the SGSN;
  • the SGSN After receiving the IP address result, the SGSN does not enable the direct tunnel, but establishes a tunnel to the RNC and establishes a tunnel to the GGSN based on the IP address result.
  • the RNC is used as the network topology information execution unit of the network topology information processing device 600
  • the SGSN is used as the network topology information using device 500, the network topology information collecting unit of the network topology information processing device 600, and the network topology information distribution.
  • the specific process can be as follows:
  • Step C4 If the RNC receives the Echo Response message returned by the GGSN, the RNC returns a successful wireless network resource allocation response to the SGSN. After the SGSN receives the wireless network resource allocation response, the direct tunnel between the RNC and the GGSN is successfully established. The process ends. Otherwise, if the RNC does not receive the Echo Response message returned by the GGSN, the RNC returns a failed wireless network resource allocation response message to the SGSN, indicating that the path between the SGSN RNC and the IP address of the GGSN is unreachable, and step C5 may be performed. . Step C5: The SGSN may resend the wireless network resource allocation request to the RNC, where the wireless network resource allocation request carries the IP address of the SGSN.
  • the RNC returns a radio network resource allocation response to the SGSN according to the IP address of the SGSN.
  • the SGSN After receiving the radio network resource allocation response, the SGSN establishes a common two-stage tunnel between the RNC and the SGSN and between the SGSN and the GGSN.
  • the SGSN may also record information indicating that the connection state between the RNC and the GGSN is abnormal, and start a timer.
  • the direct tunnel is not started between the RNC and the GGSN within a preset time of the timer.
  • the premise is that a timer needs to be set inside the SGSN.
  • the SGSN may determine whether the direct tunnel is enabled for the user, and may determine according to the connection status information, as follows:
  • the received connection status information indicates between the RNC and the GGSN. If the connection status is normal, it means that when it is necessary to determine whether the direct tunnel is enabled for the user, the SGSN can enable direct tunneling for the user.
  • the received connection status information indicates that the connection status between the RNC and the GGSN is abnormal, and the timer is continuously enabled, indicating that when it is required to determine whether the direct tunnel is enabled for the user, the SGSN does not enable the direct tunnel for the user, but establishes a tunnel to the RNC. And establish a tunnel to the GGSN.
  • the network topology information processing device 600 of the communication system of the present embodiment can collect dynamic network topology information, and the network topology information using device 500 needs to determine whether to enable the direct tunnel when the network is used. 500, the network topology information using device 500 can determine whether to enable the direct tunnel according to the network topology information, that is, when determining that the connection state between the RNC and the GGSN is normal, the direct tunnel is enabled, and if not, the RNC and the GGSN are determined. If the connection status is abnormal, a normal two-segment tunnel is established. Since the solution will be related to the establishment of a direct tunnel, such as dynamic network topology information as a condition for enabling direct tunneling, it is relative to the prior art.

Landscapes

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

Abstract

La présente invention se rapporte, dans les modes de réalisation, à un procédé de commande, à un dispositif et à un système de communication d'un tunnel direct. Les modes de réalisation de l'invention déterminent s'il faut permettre un tunnel direct selon des informations de topologie de réseau en obtenant en premier lieu les informations de topologie de réseau. Par exemple, lorsque l'état de connexion entre un dispositif de commande de réseau radio (RNC) et un nœud de support GPRS de transit (GGSN) est normal, on permet le tunnel direct. Par comparaison avec l'état de la technique, puisque le schéma utilise des facteurs se rapportant à l'établissement d'un tunnel direct, tel que les informations de topologie de réseau dynamiques, en tant que conditions pour permettre un tunnel direct, le schéma peut commander l'obtention, ou non, d'un tunnel direct de manière plus flexible et plus efficace.
PCT/CN2010/079555 2009-12-08 2010-12-08 Procédé de commande, dispositif et système de communication d'un tunnel direct Ceased WO2011069448A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2009102520828A CN101753638B (zh) 2009-12-08 2009-12-08 一种直接隧道的控制方法、装置和通信系统
CN200910252082.8 2009-12-08

Publications (1)

Publication Number Publication Date
WO2011069448A1 true WO2011069448A1 (fr) 2011-06-16

Family

ID=42480025

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/079555 Ceased WO2011069448A1 (fr) 2009-12-08 2010-12-08 Procédé de commande, dispositif et système de communication d'un tunnel direct

Country Status (2)

Country Link
CN (1) CN101753638B (fr)
WO (1) WO2011069448A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101753638B (zh) * 2009-12-08 2013-08-14 华为技术有限公司 一种直接隧道的控制方法、装置和通信系统
JP5986287B2 (ja) 2012-03-28 2016-09-06 ▲ホア▼▲ウェイ▼技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． ダイレクトトンネルを確立するための方法および装置
WO2015018038A1 (fr) * 2013-08-08 2015-02-12 华为技术有限公司 Procédé et dispositif d'établissement de tunnels
WO2018082098A1 (fr) * 2016-11-07 2018-05-11 华为技术有限公司 Procédé de gestion d'état de réseau et dispositif pertinent

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1454433A (zh) * 2000-07-04 2003-11-05 诺基亚公司 用于附加用户设备至电信网络的方法与设备
US20060262778A1 (en) * 2005-05-19 2006-11-23 Nokia Corporation Unlicensed mobile access optimization
CN101013967A (zh) * 2005-12-23 2007-08-08 上海大学 无线自组网络拓扑结构可视化监测方法
CN101753638A (zh) * 2009-12-08 2010-06-23 华为技术有限公司 一种直接隧道的控制方法、装置和通信系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101197817A (zh) * 2006-12-05 2008-06-11 华为技术有限公司 一种更新分组数据协议上下文的方法
EP2127459A4 (fr) * 2006-12-21 2013-06-12 Ericsson Telefon Ab L M Dispositif et procédé de tunnelisation directe associée à un transfert dans un réseau de communication
WO2008080717A1 (fr) * 2006-12-29 2008-07-10 Nokia Corporation Traitement d'erreur de tunnel direct

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1454433A (zh) * 2000-07-04 2003-11-05 诺基亚公司 用于附加用户设备至电信网络的方法与设备
US20060262778A1 (en) * 2005-05-19 2006-11-23 Nokia Corporation Unlicensed mobile access optimization
CN101013967A (zh) * 2005-12-23 2007-08-08 上海大学 无线自组网络拓扑结构可视化监测方法
CN101753638A (zh) * 2009-12-08 2010-06-23 华为技术有限公司 一种直接隧道的控制方法、装置和通信系统

Also Published As

Publication number Publication date
CN101753638A (zh) 2010-06-23
CN101753638B (zh) 2013-08-14

Similar Documents

Publication Publication Date Title
US12207344B2 (en) Communications method and apparatus
CN100592696C (zh) 在移动通信系统和无线局域网之间进行耦合的系统和方法
CN101378596B (zh) 单用户跟踪方法、系统和设备
WO2014000304A1 (fr) Procédé de gestion de ressources de tunnel de plan d'envoi sous commande et architecture de découplage d'envoi
WO2014146474A1 (fr) Procédé d'enregistrement de terminal, procédé de découverte de terminal, terminal et dispositif
WO2008151544A1 (fr) Procédé, appareil et système pour établir une connexion de support
WO2009135431A1 (fr) Procédé, système et équipement pour notifier des données d'utilisateur
WO2010012176A1 (fr) Procédé, dispositif et système d'obtention dune information relative à la capacité de transfert intercellulaire entre systèmes et d'accès à un système
WO2012136097A1 (fr) Passerelle de réseau de commutation par paquets et système de gestion de mobilité de terminal
WO2011098040A1 (fr) Procédé de reprise de réseau 2g/3g, appareils associés et système de communication
WO2012071695A1 (fr) Procédé, système et dispositif associé de traitement de panne de nœud
CN110493890A (zh) 一种连接恢复方法、接入和移动性管理功能实体及用户设备
WO2009111983A1 (fr) Procédé, équipement d'accès radio et terminal de recherche d’utilisateurs
WO2010108352A1 (fr) Procédé d'envoi de politiques de réseau d'accès et unité à fonctions de découverte et de prise en charge de réseau d'accès nominal
WO2012126362A1 (fr) Procédé, dispositif et système de suivi de signalisation
WO2007109955A1 (fr) Procédé d'utilisation de l'adresse ip d'un utilisateur itinérant et terminal utilisateur destiné à cet effet
CN101631344A (zh) 隧道管理方法、装置及通信系统
WO2010124551A1 (fr) Procédé et système pour préserver un identifiant de passerelle de réseau par paquets dans un scénario d'accès multiples
WO2009046666A1 (fr) Procédé d'adressage d'entité à fonction de décision de politique, élément de réseau et système de réseau
WO2009105956A1 (fr) Procédé et système de commande permettant d'établir plusieurs tunnels dans un réseau de communication sans fil
CN105359591A (zh) 一种网络故障的处理方法和设备
CN109429366B (zh) 一种pdu会话处理方法及设备
CN102209365B (zh) 网络选择方法、设备及系统
WO2013170449A1 (fr) Procédé, dispositif et système pour la gestion d'un partage de réseau
WO2011069448A1 (fr) Procédé de commande, dispositif et système de communication d'un tunnel direct

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

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

Country of ref document: EP

Kind code of ref document: A1