[go: up one dir, main page]

WO2011157124A2 - Procédé et dispositif de traitement de routage local et système de communication - Google Patents

Procédé et dispositif de traitement de routage local et système de communication Download PDF

Info

Publication number
WO2011157124A2
WO2011157124A2 PCT/CN2011/074972 CN2011074972W WO2011157124A2 WO 2011157124 A2 WO2011157124 A2 WO 2011157124A2 CN 2011074972 W CN2011074972 W CN 2011074972W WO 2011157124 A2 WO2011157124 A2 WO 2011157124A2
Authority
WO
WIPO (PCT)
Prior art keywords
local routing
sgw
local
routing processing
enodeb
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/CN2011/074972
Other languages
English (en)
Chinese (zh)
Other versions
WO2011157124A3 (fr
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
Priority to PCT/CN2011/074972 priority Critical patent/WO2011157124A2/fr
Priority to CN201180000644.5A priority patent/CN103109553B/zh
Publication of WO2011157124A2 publication Critical patent/WO2011157124A2/fr
Publication of WO2011157124A3 publication Critical patent/WO2011157124A3/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route

Definitions

  • the embodiments of the present invention relate to the field of communications, and in particular, to a local routing processing method, apparatus, and communication system. Background technique
  • the third-generation partner the 3rd Generation Partnership Project (hereinafter referred to as 3GPP) is conducting research on the packet-domain mobile core network, namely the Evolved Packet System (hereinafter referred to as EPS).
  • 3GPP 3rd Generation Partnership Project
  • EPS Evolved Packet System
  • the packet data is anchored to the anchor via the Evolved NodeB (eNodeB) and the Serving Gateway (hereinafter referred to as SGW).
  • eNodeB Evolved NodeB
  • SGW Serving Gateway
  • PGW Packet Data Network Gateway
  • IMS Multimedia Subsystem
  • IMS can use EPS to provide IP-based interactive multimedia services, such as real-time, end-to-end mobile services such as Voice over Internet Protocol (VoIP), video conferencing, or such as file sharing, multimedia chat, and dynamic push.
  • IP-based interactive multimedia services such as real-time, end-to-end mobile services such as Voice over Internet Protocol (VoIP), video conferencing, or such as file sharing, multimedia chat, and dynamic push.
  • VoIP Voice over Internet Protocol
  • Non-real-time end-to-end services Non-real-time end-to-end services.
  • the inventor has found that in the EPS of the IMS, when the UE establishes end-to-end multimedia communication through the IMS system, even if the UEs of the two communication parties are in the same base station (such as eNodeB) or the service gateway (such as Under SGW), the service flow also needs to implement the final data exchange and transmission in the IMS domain through the PGW, thus causing triangular routing, which ultimately increases the transmission burden of the backhaul network and the transmission network and the processing load of the PGW, and also increases The transmission delay is added, which reduces the quality of network services. Summary of the invention
  • the embodiment of the invention provides a local routing processing method, device and communication system, which solves the problem of large transmission resource occupation, long transmission delay and low network service quality caused by end-to-end service triangle routing in the prior art. .
  • the embodiment of the invention provides a local routing processing method, including:
  • the local routing processing device detects that the bearer contexts of the two user equipment UEs include the same session identifier
  • the local routing processing device performs local routing processing on the service flow corresponding to the session identifier, and the session identifier is allocated by the application function entity.
  • the embodiment of the invention provides a local routing processing device, including:
  • a detecting module configured to detect that the bearer context of the two user equipment UEs includes the same session identifier, where the session identifier is allocated by the application function entity;
  • the local routing processing module is configured to perform local routing processing on the service flow corresponding to the session identifier.
  • the embodiment of the present invention further provides a communication system, including: a multimedia subsystem IMS including an application function entity and an evolved packet system EPS, where the EPS includes a policy and charging rule function PCRF entity and a local route processing device;
  • a multimedia subsystem IMS including an application function entity and an evolved packet system EPS, where the EPS includes a policy and charging rule function PCRF entity and a local route processing device;
  • the multimedia subsystem is configured to allocate, by using the application function entity, a session identifier for a service flow between two UEs in a session negotiation process, and perform the session in a process of performing session information interaction with the PCRF entity.
  • the identifier is sent to the PCRF entity;
  • the PCRF entity is configured to interact with the local routing processing device to establish a dedicated bearer for the service flow between the two UEs, and the signaling message for establishing the dedicated bearer includes local routing authorization information and the a session identifier, where the local route authorization information includes the local route authorization indication information or used by the local route processing device to obtain the local route authorization indication Local routing policy information required for the information;
  • the local routing processing device is configured to detect that the bearer contexts of the two user equipment UEs include the same session identifier, and perform local routing processing on the service flow corresponding to the session identifier.
  • the local routing processing device may detect whether the session identifiers in the bearer contexts of the two UEs are the same. If they are the same, the local service flow may be determined between the two UEs, thereby implementing local route processing of the service flow. .
  • the embodiments of the present invention can enable two UEs in the same base station or serving gateway, or the local service flows of two UEs that are in the same anchoring gateway but between different serving gateways to directly loop back locally without Passing to the anchor gateway to route loopback through the IMS network not only reduces the network backhaul network pressure, but also reduces the service stream transmission delay and improves the network service quality.
  • FIG. 1 is a schematic diagram of a network architecture of an EPS in which an IMS is introduced in the prior art
  • FIG. 3 is a flowchart of another local routing user plane model according to an embodiment of the present invention
  • FIG. 4 is a flowchart of Embodiment 1 of a local routing processing method according to the present invention
  • FIG. 5 is a signaling flowchart of interaction between an AF and a PCRF in Embodiment 2 of a local route processing method according to the present invention
  • Embodiment 6 is a signaling flowchart of Embodiment 3 of a local route processing method according to the present invention.
  • Embodiment 7 is a signaling flowchart of Embodiment 4 of a local route processing method according to the present invention.
  • FIG. 8 is a signaling flowchart of Embodiment 5 of a local route processing method according to the present invention
  • FIG. 9 is a schematic flowchart of a sixth embodiment of a local routing processing method according to the present invention
  • FIG. 10 is a schematic structural diagram of Embodiment 1 of a local routing processing apparatus according to the present invention
  • FIG. 1 is a schematic structural diagram of Embodiment 2 of a local routing processing apparatus according to the present invention
  • Embodiment 3 of a local route processing apparatus according to the present invention.
  • Embodiment 4 of a local route processing apparatus is a schematic structural diagram of Embodiment 4 of a local route processing apparatus according to the present invention.
  • Embodiment 5 of a local route processing apparatus according to the present invention.
  • Embodiment 6 of a local route processing apparatus according to the present invention.
  • FIG. 16 is a schematic structural diagram of an embodiment of a communication system according to the present invention.
  • FIG. 1 is a schematic diagram of a network architecture of an EPS that is introduced into the IMS in the prior art.
  • an end-to-end multimedia is established through an IMS between a source-side UE (hereinafter referred to as oUE) and a destination-side UE (hereinafter referred to as tUE).
  • oUE source-side UE
  • tUE destination-side UE
  • the traffic between the oUE and the tUE needs to implement the final data exchange and transmission in the IMS network. Therefore, in the EPS of the IMS, the end-to-end service is implemented. It is easy to generate triangular routing, which occupies more transmission resources, increases transmission delay, and reduces network service quality and user experience quality.
  • the embodiment of the present invention proposes a technical solution for implementing local routing based on cross-layer joint in an EPS network.
  • the so-called local routing user plane model is the EPS network to complete in the local routing process to implement the service flow.
  • the logical implementation of the business flow control function According to the local route execution location of the EPS network, it can be divided into a local route in the base station or the serving gateway and a local route between the base station or the serving gateway.
  • oUE-1 and tUE-1 are attached to the same eNodeB or SGW, and therefore, oUE-1 and tUE-1 are The local route is the local route in the eNodeB or the SGW.
  • the bearer context in the eNodeB or the SGW binds the uplink bearer port of the oUE-1 to the downlink bearer port of the tUE-1, and also the source side eNodeB (hereinafter referred to as: o-
  • the address and the bearer ID of the eNodeB or the source SGW (hereinafter referred to as oSGW) are bound to the address and bearer ID of the destination side eNodeB (hereinafter referred to as t-eNodeB) or the destination side SGW (hereinafter referred to as tSGW).
  • the eNodeB or the SGW decapsulates the service flow data packet in the uplink bearer, and finds the tUE-1 corresponding to the local route in the bearer context according to the bearer port.
  • the downlink bearer port is then encapsulated and forwarded to the tUE-1 by the downlink bearer port of the tUE-1, so as to implement the local route of the service flow in the eNodeB or the SGW.
  • the local route between oUE-2 and tUE-2 is a local route between the eNodeB or the SGW.
  • a local route forwarding tunnel needs to be established between the o-eNodeB and the t-eNodeB, or between the oSGW and the tSGW, and the bearer context in the o-eNodeB or the oSGW binds the uplink bearer port of the oUE-2 to the port of the forwarding tunnel, t-
  • the bearer context in the eNodeB or tSGW binds the port of the forwarding tunnel to the downlink bearer port of tUE-2.
  • the eNodeB or the SGW decapsulates the service flow data packet in the uplink bearer, and finds the forwarding tunnel port corresponding to the local route in the bearer context according to the bearer port. Then, the service flow data packet is encapsulated and forwarded to the tUE-2 according to the forwarding tunnel port, thereby implementing local routing of the service flow between the eNodeB or the SGW.
  • FIG. 3 is another local routing user plane model applied according to an embodiment of the present invention.
  • the user plane model is similar to the user plane model shown in FIG. 2, and includes local routes and eNodeBs in an eNodeB or SGW. Or local route between SGWs, the difference is that Before the eNodeB or SGW performs local routing, it also includes Network Address Transfer (NAT). Specifically, if there is a NAT device between the EPS network and the IMS network, the traffic between the oUE and the tUE needs to be NAT-transformed before performing the local route.
  • NAT Network Address Transfer
  • the oUE when the local route is implemented, the eNodeB or the SGW, the oUE sends out The service flow needs to complete the NAT conversion before entering the downlink bearer of the tUE, that is, converting the destination public network transmission address of the service flow into the destination private network transmission address according to the NAT mapping information, and converting the source private network transmission address into the source public network transmission address.
  • Embodiment 1 of a local route processing method according to the present invention. As shown in FIG. 4, the method in this embodiment may include:
  • Step 401 The local route processing apparatus detects that the bearer contexts of the two UEs include the same session identifier.
  • Step 402 The local routing processing device performs local routing processing on the service flow corresponding to the session identifier.
  • the oUE and the tUE may be used by the AF entity to allocate a unified service flow between the oUE and the tUE in the process of establishing a session negotiation in the process of establishing a session negotiation by using an application function (hereinafter referred to as an AF) entity in the IMS network.
  • the session identifier, and in the process of establishing a dedicated bearer for the service flow between the oUE and the tUE, the policy and the charging policy function entity (PCRF) entity in the EPS network may perform the process of establishing a dedicated bearer for the service flow between the oUE and the tUE.
  • the session identifier is sent to the PRCF such that the local routing processing device in the EPS network can obtain the session identifier from the respective bearer contexts of the oUE and the tUE.
  • the local routing processing device in the EPS network can detect whether the bearer context of the oUE and the tUE includes the same session identifier. If the same session identifier is detected, it indicates that there is a service flow between the oUE and the tUE.
  • the session identifier may be, for example, a Global Call ID (hereinafter referred to as: GCID). Therefore, the local routing processing device can perform local routing processing on the service flow corresponding to the session identifier.
  • the local routing processing may include the local routing processing in the eNodeB or the SGW, or the local routing processing between the eNodeB or the SGW.
  • the implementation principle is similar to the implementation principle shown in FIG. 2 or FIG. 3 above. Let me repeat.
  • the local routing processing device in this embodiment may be a new deployment in the EPS network, or may be an existing deployment in the EPS network, for example, using an eNodeB, an SGW, or a PGW. limit.
  • the local routing processing device can detect whether the session identifiers in the bearer contexts of the two UEs are the same. If they are the same, the service flow between the two UEs can be determined, and the local route processing of the service flow is implemented.
  • the service flows of two UEs in the same base station or the monthly service gateway, or two UEs in the same anchor gateway but between different service gateways can be directly looped back locally without backhauling. By routing the loopback to the anchor gateway via the IMS network, the network backhaul network pressure is relieved, the service flow delay is also reduced, and the network service quality is improved.
  • the PCRF entity may also allocate local routing authorization indication information for the service flow between the oUE and the tUE in the process of establishing a dedicated bearer for the oUE and the tUE respectively, thereby making the EPS network
  • the local routing processing device may obtain the local routing authorization indication information from the respective bearer contexts of the oUE and the tUE, and determine whether to allow the local routing processing of the service flow between the oUE and the tUE according to the two local routing authorization indication information, when When the local routing authorization indication information indicates that the local routing of the service flow is allowed, the local routing processing device can perform local routing processing on the service flow between the oUE and the tUE.
  • the application control layer entity in the IMS network allocates the unified session identifier and the policy and charging rule function entity PCRF in the EPS network allocates the local route authorization indication information, which can simplify the local route of the EPS network. Policy control process.
  • the session initiated by the oUE may include: multiple service flows pointing to one tUE, or pointing to multiple Multiple service flows of tUE. Therefore, the process of assigning the same session identifier to a session between oUE and tUE may include:
  • the AF may allocate the same session identifier for each service flow between each pair of oUE and tUE, if the session initiated by the UE includes multiple service flows that are different from the tUE.
  • the AF may have different Quality of Service (QoS) requirements for multiple service flows, if the OUE-initiated session includes multiple service flows that are directed to one tUE.
  • QoS Quality of Service
  • the service flows are assigned different session identifiers, so that traffic flows with different QoS requirements between oUE and tUE can be distinguished.
  • the AF and the PCRF can perform session information interaction before the establishment of the dedicated bearer, and in the process of the session information interaction, the AF can include the session information including the session identifier.
  • the session information includes session information of the oUE and session information of the tUE.
  • the PCRF can assign local routing authorization information to the oUE and the tUE according to the session information and the local routing policy.
  • the PCRF triggers the PGW to establish a dedicated bearer for each service identifier corresponding to each session identifier.
  • the session identifier and local routing authorization information can be included in the signaling message for establishing a dedicated bearer.
  • the PCRF can allocate local routing grant information for the oUE and tUE in two ways.
  • the PCRF can set the local routing authorization information of the oUE and the tUE according to the local routing policy.
  • the local routing authorization information is the local routing authorization indication information to indicate whether the service flow to the oUE or the tUE is allowed.
  • the local route processing is performed, and then the PCRF can notify the local routing processing device in the EPS network whether the local routing processing device in the EPS network can perform local routing processing on the service flow between the oUE and the tUE.
  • the PCRF itself does not decide whether The local routing policy information is sent to the local routing processing device in the EPS network according to the local routing policy, and the local routing processing device further makes local routing according to the local routing policy information. decision making.
  • the local routing policy includes but is not limited to the IP flow service type. Restrictions, billing restrictions, lawful interception restrictions, user subscription restrictions, etc.
  • the PCRF can also send the local routing indication message to the local routing processing device by setting the local routing indication to be disabled, so that the local road processing device can The indication message de-localizes the route, thereby causing the local route communication between the oUE and the tUE to fall back to the regular route communication.
  • the PCRF can obtain the NAT mapping information directly from the AF before the local route is forwarded.
  • the AF mapping information is transmitted to the PCRF along with the session information by the AF during the session information exchange between the AF and the PRCF.
  • the signaling message may further include the NAT mapping information.
  • the local routing processing device can receive the uplink data packet of the oUE, complete the conversion of the data source and the destination IP address and the port number according to the NAT mapping information, and then forward the data to the tUE.
  • the AF and the PCRF can perform the following interaction process to complete the process of assigning the session identifier to the AF.
  • the embodiment is described by taking a GCID as an example.
  • the AF in this embodiment may be classified into a source side AF (hereinafter abbreviated as: oAF) and a destination side AF (hereinafter referred to as tAF), and the PCRF may also be classified into a source side PCRF (hereinafter referred to as oPCRF) and a destination.
  • the side PCRF hereinafter referred to as tPCRF;
  • oAF and oPCRF correspond to oUE
  • tAF and tPCRF correspond to tUE.
  • Step 501 The oUE delivers initial session information to the oAF.
  • the initial session information is used to establish a media service flow session between the oUE and the tUE.
  • the initial session information may include types of service flows that need to be negotiated with the peer tUE, such as audio, video, data, etc.; codec format; transport address, such as IP address and port number; QoS parameters, and the like.
  • Step 502 The oAF allocates a GCID to the service flow between the oUE and the tUE that is to be established, and obtains downlink service flow connection information required by the oUE from the initial session information.
  • the connection information of the downlink service flow may include an IP address, a port number, and the like of the downlink service flow.
  • Step 503 The oAF forwards the initial session information to the tAF.
  • the initial session information contains the GCID.
  • Step 504 The tAF obtains uplink service flow connection information required by the tUE from the initial session information.
  • the uplink service flow connection information may include an IP address, a port number, and the like of the uplink service flow.
  • Step 505 The tAF sends the initial session information to the tUE.
  • the tUE may select a type of service flow that can be supported from the initial session information, such as audio, video, data, etc.; codec format; transport address, such as IP address and port number; QoS parameters, etc.
  • a type of service flow that can be supported from the initial session information, such as audio, video, data, etc.; codec format; transport address, such as IP address and port number; QoS parameters, etc.
  • Step 506 The tUE returns the negotiated session information to the tAF.
  • Step 507 The tAF obtains downlink service flow connection information required by the tUE from the negotiated session information.
  • the downlink service flow connection information may include an IP address, a port number, and the like of the downlink service flow.
  • the service flow connection information may include uplink and downlink connection information, negotiated media type, codec type, bandwidth, and the like.
  • Step 509 The tPCRF saves the service flow connection information, and finds an IP Connectivity Access Network (IP-Access) network (hereinafter referred to as an IP-CAN) session corresponding to the service connection of the tUE.
  • IP-Access IP Connectivity Access Network
  • Step 510 The tPCRF returns a service flow connection information confirmation message to the tAF.
  • Step 511 The tPCRF establishes a policy and a policy of the local routing policy (Policy and Charge Control, PCC) to establish an Evolved Packet Core (EPC) proprietary bearer.
  • Policy and Charge Control, PCC Policy and Charge Control
  • EPC Evolved Packet Core
  • the PCC rules may contain GCID and local routing authorization indication information, or in order to further make local routing decisions by the local routing processing device in the EPS network, the tPCRF may also be local
  • the routing policy information is sent to the local routing processing device in the EPS network, and interacts with the PGW to trigger the EPC dedicated bearer required to establish the tUE for the current service connection.
  • step 51 1 can be performed in parallel with step 510.
  • Step 512 After receiving the service flow connection information confirmation message returned by the tPCRF, the tAF forwards the negotiated session information to the oAF.
  • Step 513 The oAF obtains the uplink service flow connection information required by the o UE.
  • Step 514 The oAF sends the service flow connection information including the GCID to the oPCRF.
  • Step 515 The oPCRF saves the service flow connection information, and finds an IP-CAN session corresponding to the service connection of the UE.
  • Step 516 The oPCRF returns a service flow connection information confirmation message to the oAF.
  • Step 517 The oAF returns the negotiated session information to the oUE.
  • Step 518 The oPCRF creates a PCC rule according to the service connection information and the local routing policy, and establishes an EPC-specific bearer.
  • the oPCRF can interact with the PGW to trigger the establishment of an EPC-specific bearer for the oUE for the current service connection.
  • step 518 can be performed in parallel with steps 516 and 517.
  • the service flow connection information transmitted by the AF to the PCRF in step 508 and step 514 may further include a NAT mapping.
  • the information, the PCC rules for establishing an EPC-specific bearer in steps 511 and 518 may also include NAT mapping information.
  • the local routing processing device may be a PGW, an SGW, or an eNodeB.
  • different local routing processing methods may be used correspondingly, specifically:
  • the PGW detects that the bearer context of the two UEs includes the same session identifier, and the PGW may request the SGW to perform local routing processing on the service flow corresponding to the session identifier. Specific For example, if two UEs are attached to different SGWs, the source side SGW is requested to establish a local route between the two SGWs.
  • the local route is established by the SGW. If the local routing processing device is SGW:
  • the SGW detects that the bearer contexts of the two user equipments contain the same session identifier, and establish a local route in the SGW for the service flow corresponding to the session identifier.
  • the local routing processing device is an SGW and an eNodeB:
  • the SGW detects that the bearer contexts of the two user equipments UEs contain the same session identifier. If two UEs are attached to different eNodeBs and both eNodeBs have local routing capabilities, the SGW requests the source side eNodeB to establish between the two eNodeBs. Local route
  • the SGW establishes a local route in the SGW
  • the eNodeB implements local routing.
  • the local routing processing device is an eNodeB:
  • the eNodeB detects that the bearer contexts of the two user equipments UEs contain the same session identifier, and establish a local route in the eNodeB for the service flow corresponding to the session identifier.
  • FIG. 6 is a signaling flowchart of a method for processing a local route in the third embodiment of the present invention.
  • the local routing processing device may be an SGW, and the tUE and the oUE are attached to the same SGW.
  • the embodiment may implement a local route in the SGW.
  • the method in this embodiment may include:
  • Step 601 Establish an EPC-specific bearer required for the session between the oUE and the tUE.
  • Step 602 The SGW identifies the local communication according to the same GCID included in the bearer context of the oUE and the tUE. It should be noted that if the PGW also identifies the local communication through the GCID and finds that the oUE and the tUE are attached to the same SGW, the PGW can be ignored and recognized and processed by the SGW.
  • Step 603 The SGW decides to perform local routing according to the local routing authorization indication information.
  • the SGW performs local routing in the SGW.
  • SGW before the execution of the judgment of the local routing within the SGW, SGW can determine oUE and tUE where the eNodeB whether to support the local routing capabilities, if they support the local routing capabilities, shellfish 1 J SGW eNodeB can trigger local routing process, local eNodeB Routing processing depends on whether oUE and tUE are attached to the same eNodeB. If the SGW determines that the eNodeB where the oUE and the tUE are located does not support the local routing function, the SGW may decide that only the local route within the SGW can be performed.
  • the SGW may obtain a local route authorization indication corresponding to the GCID in the bearer context of the respective UE and the tUE. If the two local route authorization indications indicate that the local route is allowed to be performed, the SGW may establish a local route user plane in the SGW. That is, corresponding to the upper half of FIG. 2 or FIG. 3, the uplink 7-load of the oUE is bound to the downlink 7-load of the tUE, and the uplink of the tUE is loaded with the downlink of the oUE.
  • Step 604 The SGW sends the local routing information to a Mobility Management Entity (MME).
  • MME Mobility Management Entity
  • the SGW can separately inform the MME of the local routing information of the oUE and the tUE. This step is an optional step.
  • Step 605 The service flow corresponding to the GCID between the oUE and the tUE is returned in the SGW.
  • the SGW needs to complete the NAT address translation according to the NAT mapping information before forwarding the local routing data.
  • the SGW may also periodically send the synchronization heartbeat packet to the NAT device instead of the UE to maintain the address mapping information in the NAT device not expired, so as to synchronize the NAT mapping information in the SGW.
  • the SGW can detect whether the GCIDs in the bearer context of the oUE and the tUE are the same.
  • the service flow between the oUE and the tUE can be determined, and the local route processing of the service flow in the SGW is implemented.
  • the service flows of the oUE and the tUE in the same SGW can be directly looped back in the SGW without being transmitted back to the PGW to perform loopback through the IMS network, which not only reduces the network backhaul transmission network pressure, but also simultaneously reduces the pressure of the core network backhaul network. Reduce the delay of traffic transmission and improve the quality of network services.
  • FIG. 7 is a signaling flowchart of Embodiment 4 of the local routing processing method of the present invention.
  • the local routing processing device may be a PGW and an SGW, and the PGW identifies the local communication by using the GCID and discovers the oUE and the The tUE is attached to the different SGWs. Therefore, the PGW can trigger the establishment of the local route between the SGWs.
  • the method in this embodiment may include: Step 701: Establish an EPC-specific bearer required for the inter-UE and tUE sessions.
  • Step 702 The PGW identifies the local communication according to the same GCID included in the bearer context of the oUE and the tUE.
  • Step 703 The PGW determines to perform local routing according to the local routing authorization indication information.
  • the PGW can trigger local routing between the SGWs.
  • Step 704 The PGW sends a local route establishment request to the oSGW.
  • the local route establishment request is used to implement a local route from the oUE to the tUE, and the request may include an ID of the oUE and the tUE, a bearer ID, a location of the SGW, a charging ID, and QoS information.
  • Step 705 The oSGW sends a local route establishment request to the oMME.
  • Step 706 The oMME sends a local route forwarding tunnel establishment request to the tSGW.
  • the oMME may send a local route forwarding tunnel establishment request to the tSGW according to the address of the tSGW in the local route establishment request, where the request may include the tUE ID, the tUE downlink bearer ID, and the like.
  • Step 707 The tSGW feeds back the local route forwarding tunnel establishment response to the oMME.
  • the tSGW can allocate a forwarding tunnel ID and bind it to the tUE downlink bearer ID, and then feed back the forwarding tunnel ID to the oMME through the response.
  • Step 708 The oMME sends a local route setup response to the oSGW.
  • the forwarding tunnel ID can be included in the response.
  • Step 709 The oSGW feeds back the local route establishment response to the PGW.
  • the oSGW Before performing step 709, the oSGW can bind the oUE uplink bearer to the forwarding tunnel, thereby implementing establishment of a local route user plane from oUE to tUE.
  • Step 710 The PGW sends a local route establishment request to the tSGW.
  • the request is used to implement a local route from the tUE to the oUE, and the request may include an ID of the tUE and the oUE, a bearer ID, a location of the SGW, a charging ID, and QoS information.
  • Step 711 The tSGW sends a local route establishment request to the tMME.
  • Step 712 The tMME sends a local route forwarding tunnel establishment request to the oSGW.
  • the tMME may send a local route forwarding tunnel establishment request to the oSGW according to the oSGW address in the local route establishment request, where the request may include an oUE ID and an oUE downlink bearer.
  • Step 713 The oSGW feeds back the local route forwarding tunnel establishment response to the tMME.
  • the oSGW can allocate a forwarding tunnel ID and bind it to the oUE downlink bearer ID, and then feed the forwarding tunnel ID back to the tMME through the response.
  • Step 714 The tMME sends a local route setup response to the tSGW.
  • the forwarding tunnel ID can be included in the response.
  • Step 715 The tSGW feeds back a local route setup response to the PGW.
  • the tSGW Before performing step 715, the tSGW binds the tUE uplink bearer to the forwarding tunnel, so as to implement the establishment of the local route user plane of the tUE to the oUE.
  • the oSGW and the tSGW can establish a forwarding tunnel between the SGWs, which is similar to the lower half shown in FIG. 2 or FIG. Step 716:
  • the service flow corresponding to the GCID between the oUE and the tUE is returned between the oSGW and the tSGW.
  • the SGW needs to complete the NAT address translation according to the NAT mapping information before forwarding the local routing data.
  • the SGW can also periodically send the synchronization heartbeat packet to the NAT device instead of the UE to maintain the address mapping information in the NAT device not expired, so as to facilitate the synchronization of the NAT mapping information in the SGW.
  • the PGW can detect whether the GCIDs in the bearer contexts of the oUE and the tUE are the same. If they are the same, the service flow between the oUE and the tUE can be determined, and then the local route processing between the oSGW and the tSGW is triggered. The local route of the service flow corresponding to the GCID between the SGWs.
  • the service flows of the oUE and the tUE attached to the different SGWs can be looped back between the two SGWs, and the loopback is not required to be transmitted back to the PGW via the IMS network, which not only reduces the network backhaul transmission network pressure, but also reduces the network network backhaul network pressure. At the same time, the service flow transmission delay is reduced, and the network service quality is improved.
  • FIG. 8 is a signaling flowchart of Embodiment 5 of the local routing processing method of the present invention.
  • the local routing processing apparatus may be an eNodeB, and tUE and oUE are attached to the same eNodeB, so The embodiment may implement local routing in the eNodeB.
  • the method in this embodiment may include:
  • Step 801 Establish an EPC-specific bearer required for the session between the oUE and the tUE.
  • Step 802 The eNodeB identifies the local communication according to the same GCID included in the bearer context of the oUE and the tUE.
  • the SGW also identifies the local communication through the GCID and finds that the oUE and the tUE are attached to the same eNodeB, the SGW can be ignored and identified and processed by the eNodeB.
  • Step 803 The eNodeB determines to perform local routing according to the local routing authorization indication information. Specifically, the eNodeB can acquire the respective bearer contexts of the oUE and the tUE and the GCID. Corresponding local route authorization indication, if both local route authorization indications indicate that the local route is allowed to be performed, the eNodeB can establish a local route user plane in the eNodeB, that is, corresponding to the upper part of FIG. 2 or FIG. 3, that is, the uplink of the oUE The bearer is bound to the downlink bearer of the tUE, and the uplink 7-load of the tUE is bound to the downlink 7-carrier of the oUE.
  • Step 804 The eNodeB sends the local routing information to the MME.
  • the eNodeB can inform the MME of the local routing information of the oUE and the tUE, respectively. This step is an optional step.
  • Step 805 The service flow corresponding to the GCID between the oUE and the tUE is returned in the eNodeB.
  • the eNodeB may first complete the NAT according to the NAT mapping information before the local route data is forwarded. Address translation, at the same time, the eNodeB replaces the UE to send a synchronization heartbeat packet to the NAT device periodically to maintain the address mapping information in the NAT device not expired, so as to facilitate the NAT mapping information synchronization in the eNodeB.
  • the eNodeB can detect whether the GCIDs in the bearer context of the oUE and the tUE are the same. If they are the same, it can be determined that there is a service flow between the oUE and the tUE, and then the local route processing of the service flow in the eNodeB is implemented.
  • the service flows of the oUE and the tUE in the same eNodeB can be directly looped back in the eNodeB without being transmitted back to the SGW and the PGW routing loopback through the IMS network, which not only reduces the pressure of the core network backhaul transmission network, It also reduces the delay of traffic transmission and improves the quality of network services.
  • FIG. 9 is a signaling flowchart of Embodiment 6 of the local routing processing method of the present invention.
  • the local routing processing apparatus may be an SGW and an eNodeB, and the SGW identifies the local communication by using the GCID and discovers the oUE and the The tUE is attached to different eNodeBs, so the SGW can trigger the establishment of a local route between the eNodeBs.
  • the method in this embodiment may include: Step 901: Establish an EPC-specific bearer required for the inter-UE and tUE sessions.
  • Step 902 The SGW identifies the local communication according to the same GCID included in the bearer context of the oUE and the tUE.
  • Step 903 The SGW determines to perform local routing according to the local routing authorization indication information.
  • the SGW can trigger local routing between the eNodeBs.
  • Step 904 The SGW sends a local route establishment request to the MME.
  • the local route setup request is used to implement a local route from the oUE to the tUE, and the request may include an ID of the oUE and the tUE, a bearer ID, a location of the eNodeB, a charging ID, and QoS information.
  • Step 905 The MME sends a local route forwarding tunnel establishment request to the t-eNodeB.
  • the MME may send a local routing forwarding tunnel establishment request to the t-eNodeB according to the address of the t-eNodeB in the local routing establishment request, where the request may include the tUE ID, the tUE downlink bearer ID, and the like.
  • Step 906 The t-eNodeB feeds back the local route forwarding tunnel establishment response to the MME.
  • the t-eNodeB can allocate a forwarding tunnel ID and bind it to the tUE downlink bearer ID, and then feed back the forwarding tunnel ID to the MME through the response.
  • Step 907 The MME sends a local routing request to the o-eNodeB.
  • the request may include an ID of the oUE, an oUE bearer ID, an ID of the tUE, a tUE bearer ID or a t-eNodeB address, and a t-eNodeB forwarding tunnel ID.
  • Step 908 The o-eNodeB feeds back to the MME to establish a local route response.
  • the o-eNodeB can assign a forwarding tunnel ID and bind it to the oUE uplink ID.
  • Step 909 The MME returns a local route setup response to the SGW.
  • Step 910 The SGW sends a local route establishment request to the MME.
  • the local route setup request is used to implement a local route from the tUE to the oUE, and the request may include an ID of the oUE and the tUE, a bearer ID, a location of the eNodeB, a charging ID, and QoS information.
  • Step 911 The MME sends a local route forwarding tunnel establishment request to the o-eNodeB.
  • the MME may send a local route forwarding tunnel establishment request to the o-eNodeB according to the o-eNodeB address in the local routing establishment request, where the request may include an oUE ID and an oUE bearer ID.
  • Step 912 The o-eNodeB feeds back the local route forwarding tunnel establishment response to the MME.
  • the o-eNodeB can assign a forwarding tunnel ID and bind it to the oUE downlink 7-input ID, and then return the forwarding tunnel ID to the MME.
  • Step 913 The MME sends a local route establishment request to the t-eNodeB.
  • the request may include an ID of the tUE, a tUE bearer ID, an oUE ID, an oUE bearer ID or an o-eNodeB address, and an o-eNodeB forwarding tunnel ID.
  • the t-eNodeB can bind the tUE uplink bearer to the forwarding tunnel, so as to implement the establishment of the local route user plane of the tUE to the oUE.
  • Step 914 The t-eNodeB feeds back to the MME to establish a local route response.
  • Step 915 The MME returns a local route setup response to the SGW.
  • the o-eNodeB and the t-eNodeB can establish a forwarding tunnel between the eNodeBs, which is similar to the lower half shown in FIG. 2 or FIG.
  • Step 916 The service flow corresponding to the GCID between the oUE and the tUE is returned between the o-eNodeB and the t-eNodeB.
  • the eNodeB needs to complete the NAT address translation according to the NAT mapping information before forwarding the local routing data. .
  • the eNodeB can also periodically send the synchronization heartbeat packet to the NAT device instead of the UE to maintain the address mapping information in the NAT device not expired, so as to facilitate the synchronization of the NAT mapping information in the eNodeB.
  • the SGW can detect whether the GCIDs in the bearer context of the oUE and the tUE are the same. If they are the same, it can be determined that there is a service flow between the oUE and the tUE, and then the local between the o-eNodeB and the t-eNodeB is established by triggering.
  • the routing process implements a local route between the o-eNodeB and the t-eNodeB of the service flow corresponding to the GCID.
  • This embodiment can be attached
  • the service flows of the oUE and tUE of different eNodeBs are looped back between the two eNodeBs, and no need to be transmitted back to the SGW, and the PGW routes loopback through the IMS network, which not only reduces the pressure of the core network backhaul transmission network, but also reduces the service. Streaming delays improve network service quality.
  • the apparatus in this embodiment may include: a detecting module 1 1 and a local routing processing module 12, where the detecting module 11 is configured to detect The bearer context of the two user equipments UE includes the same session identifier, and the session identifier is allocated by the application function entity.
  • the local route processing module 12 is configured to perform local routing processing on the service flow corresponding to the session identifier.
  • the device in this embodiment may be used to perform the method in the method embodiment shown in FIG. 4, and the implementation principle and the technical effect are similar, and details are not described herein again.
  • FIG. 11 is a schematic structural diagram of Embodiment 2 of a local routing processing apparatus according to the present invention.
  • the apparatus of this embodiment based on the apparatus structure shown in FIG. 10, further includes: an authorization information determining module 13 and an acquisition.
  • the module 14 is configured to: determine, according to the local routing authorization indication information included in the bearer context of the two UEs, to allow local routing processing on the service flow; the obtaining module 14 is configured to be in the UE Obtaining the local routing authorization information and the session identifier, where the local routing authorization information is generated by the policy and charging rule function PCRF entity, where the local routing authorization information includes the The local routing authorization indication information or the local routing policy information required by the local routing processing device to obtain the local routing authorization indication information.
  • the signaling message that the obtaining module 14 establishes the dedicated bearer further includes network address translation NAT mapping information, where the NAT mapping information is used by the PCRF entity to perform session information interaction with the application function entity.
  • the apparatus of the present embodiment may further include an address translation processing module 15 for using the function entity to be sent to the PCRF entity or to the application function entity by the PCRF entity.
  • the NAT mapping information performs address translation processing on the data packet between the two UEs.
  • the apparatus of this embodiment may be used to perform the method of the method embodiment shown in FIG. 5, which implements the original
  • the technical and technical effects are similar and will not be described here.
  • the local routing processing device includes: a packet data network gateway PGW and a serving gateway SGW; or a serving gateway SGW; or an SGW and an evolved base station eNodeB; or an eNodeB.
  • the local routing processing device will be further described below using several embodiments.
  • the apparatus of this embodiment is based on the apparatus structure shown in FIG. 10, and the apparatus may include a PGW and an SGW in an EPS network.
  • the detecting module 11 is deployed on the PGW, and the local routing processing module 12 is deployed on the SGW.
  • the detecting module 11 may further include: a first detecting unit 111, configured to: if the two UEs are attached to different SGWs, request the source
  • the local routing processing module on the side SGW establishes a local route between the two SGWs.
  • the second detecting unit 1 12 is configured to perform local routing processing on the SGW if the two UEs are attached to the same SGW.
  • the module establishes a local route.
  • the device in this embodiment may be used to perform the method in the embodiment of the method shown in FIG. 6 or FIG. 7.
  • the implementation principle and technical effects are similar, and details are not described herein again.
  • Embodiment 4 of a local routing processing apparatus is a schematic structural diagram of Embodiment 4 of a local routing processing apparatus according to the present invention.
  • the apparatus of this embodiment is based on the apparatus structure shown in FIG. 10, and the apparatus may be an SGW in an EPS network, and a detection module.
  • the local routing processing module 12 is configured to establish a local route in the SGW for the service flow corresponding to the session identifier.
  • the device in this embodiment may be used to perform the method in the embodiment of the method shown in FIG. 6 to FIG. 9.
  • the implementation principle and the technical effect are similar, and details are not described herein again.
  • FIG. 14 is a schematic structural diagram of Embodiment 5 of a local routing processing apparatus according to the present invention.
  • the apparatus of this embodiment is based on the apparatus structure shown in FIG. 10, and the apparatus may include an SGW and an eNodeB in an EPS network.
  • the detecting module 11 is deployed on the SGW, and the local routing processing module 12 is deployed on the eNodeB.
  • the detecting module 11 may include: a third detecting unit 1 13 For requesting the local routing processing module on the source side eNodeB to establish a local route between the two eNodeBs, if the two UEs are attached to different eNodeBs and both eNodeBs have local routing capabilities;
  • the unit 1 15 is configured to: if the two UEs are attached to the same eNodeB and the eNodeB has local routing capability, the local routing processing device on the eNodeB implements local routing.
  • the detecting module 11 may further include a fourth detecting unit (not shown), and the fourth detecting unit If the two UEs are attached to different eNodeBs and at least one of the two eNodeBs does not have the local routing capability, the local routing processing module on the SGW is requested to establish a local route in the SGW.
  • the device in this embodiment may be used to perform the method in the method embodiment shown in FIG. 9 , and the implementation principle and the technical effect are similar, and details are not described herein again.
  • Embodiment 6 is a schematic structural diagram of Embodiment 6 of a local routing processing apparatus according to the present invention.
  • the apparatus of this embodiment is based on the apparatus structure shown in FIG. 10, and the apparatus may be an eNodeB in an EPS network, and a detection module.
  • the local routing processing module 12 is configured to establish a local route in the eNodeB for the service flow corresponding to the session identifier.
  • the device in this embodiment may be used to perform the method in the method embodiment shown in FIG. 8 or FIG. 9.
  • the implementation principle and technical effects are similar, and details are not described herein again.
  • FIG. 16 is a schematic structural diagram of an embodiment of a communication system according to the present invention. As shown in FIG. 16, the system in this embodiment may include: IMS 1 and EPS2 including an application function entity 5, and the EPS2 includes
  • the IMS1 is configured to allocate a session identifier for a service flow between two UEs in the session negotiation process by the application function entity 5, and perform a session information interaction with the PCRF entity 3
  • the session identifier is sent to the PCRF entity 3;
  • the PCRF entity 3 is used to interact with the local route processing device 4 to establish a dedicated bearer for the service flow between the two UEs, and the signaling message for establishing the dedicated bearer is included in the Local routing authorization information and
  • the local routing authorization information includes the local routing authorization indication information or local routing policy information required for the local routing processing device 4 to obtain the local routing authorization indication information;
  • the bearer context for detecting the two user equipments UE includes the same session identifier, and performs local routing processing on the service flow corresponding to the session identifier.
  • the local routing processing device may be a new functional module in the EPS2, or a PGW and an SGW; or an SGW; or an SGW and an eNodeB; or an eNodeB.
  • the communication system of this embodiment can be used to perform the method shown in any of the embodiments shown in FIG. 4 to FIG. 9, and the implementation principle and technical effects are similar, and details are not described herein again.

Landscapes

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

Abstract

La présente invention se rapporte, dans ses modes de réalisation, à un procédé et à un dispositif de traitement de routage local ainsi qu'à un système de communication. Le procédé de traitement de routage local comprend : un dispositif de traitement de routage local qui détecte des contextes de support de deux équipements utilisateurs (UE) qui contiennent la même identification de session ; le dispositif de traitement de routage local met en œuvre un traitement de routage local pour des flux de trafic correspondant à l'identification de session, l'identification de session étant distribuée par une entité de fonction d'application. Avec les modes de réalisation de la présente invention, les flux de trafic des deux UE peuvent être directement renvoyés localement en boucle, les deux UE se trouvant dans la même station de base ou dans la même passerelle de desserte (SGW), ou se trouvant dans la même passerelle d'ancrage mais dans des SGW différentes tout en n'étant pas retransmis à la passerelle d'ancrage et étant renvoyés en boucle au moyen du routage du réseau de sous-système multimédia IP (IMS), ce qui permet de réduire la pression de réseau de transport terrestre du réseau fédérateur ainsi que de diminuer le retard de transmission des flux de trafic et d'améliorer la qualité de service du réseau.
PCT/CN2011/074972 2011-05-31 2011-05-31 Procédé et dispositif de traitement de routage local et système de communication Ceased WO2011157124A2 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2011/074972 WO2011157124A2 (fr) 2011-05-31 2011-05-31 Procédé et dispositif de traitement de routage local et système de communication
CN201180000644.5A CN103109553B (zh) 2011-05-31 本地路由处理方法、装置和通信系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/074972 WO2011157124A2 (fr) 2011-05-31 2011-05-31 Procédé et dispositif de traitement de routage local et système de communication

Publications (2)

Publication Number Publication Date
WO2011157124A2 true WO2011157124A2 (fr) 2011-12-22
WO2011157124A3 WO2011157124A3 (fr) 2012-05-03

Family

ID=45348615

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/074972 Ceased WO2011157124A2 (fr) 2011-05-31 2011-05-31 Procédé et dispositif de traitement de routage local et système de communication

Country Status (1)

Country Link
WO (1) WO2011157124A2 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102821435A (zh) * 2012-08-07 2012-12-12 南京邮电大学 WiMAX系统中分段建立数据路径的本地路由方法
CN104754540A (zh) * 2015-03-20 2015-07-01 中国人民解放军信息工程大学 以无线接入单元为锚点的媒体数据环回处理方法
CN107920378A (zh) * 2016-10-11 2018-04-17 中国移动通信有限公司研究院 本地路由处理方法及装置
CN111555977A (zh) * 2015-10-22 2020-08-18 华为技术有限公司 一种业务处理的方法、装置及系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101309505B (zh) * 2007-05-15 2011-12-07 华为技术有限公司 无线通信系统中语音业务路由方法及其系统
EP2250827B1 (fr) * 2008-02-04 2014-03-12 Telefonaktiebolaget L M Ericsson (publ) Procédé et appareil pour permettre l'optimisation d'un chemin
EP2117201A1 (fr) * 2008-05-07 2009-11-11 Alcatel Lucent Dispositif de réseau et procédé pour routage local de trafic de données
CN101686520A (zh) * 2008-09-24 2010-03-31 三星电子株式会社 支持家用基站上下文管理的方法

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102821435A (zh) * 2012-08-07 2012-12-12 南京邮电大学 WiMAX系统中分段建立数据路径的本地路由方法
CN104754540A (zh) * 2015-03-20 2015-07-01 中国人民解放军信息工程大学 以无线接入单元为锚点的媒体数据环回处理方法
CN104754540B (zh) * 2015-03-20 2018-06-01 中国人民解放军信息工程大学 以无线接入单元为锚点的媒体数据环回处理方法
CN111555977A (zh) * 2015-10-22 2020-08-18 华为技术有限公司 一种业务处理的方法、装置及系统
US11388095B2 (en) 2015-10-22 2022-07-12 Huawei Technologies Co., Ltd. Service processing method, apparatus, and system
CN107920378A (zh) * 2016-10-11 2018-04-17 中国移动通信有限公司研究院 本地路由处理方法及装置
CN113194517A (zh) * 2016-10-11 2021-07-30 中国移动通信有限公司研究院 本地路由处理方法、装置及存储介质

Also Published As

Publication number Publication date
WO2011157124A3 (fr) 2012-05-03
CN103109553A (zh) 2013-05-15

Similar Documents

Publication Publication Date Title
JP6535415B2 (ja) データ処理方法及びデバイス
TWI583234B (zh) 具有網際網路協定(ip)多媒體子系統(ims)能力的裝置及由其實施的方法
KR100965724B1 (ko) 이종의 무선 통신 네트워크에서 핸드오버 장치 및 방법
US9549345B2 (en) Solution to improve RAN bandwidth efficiency during VoLTE call scenarios
CN104067589B (zh) 通过虚拟专用网络来创建连接的方法和设备
WO2009043209A1 (fr) Procédé permettant d'établir une porteuse vers un terminal utilisateur en mode repos
CN101313542A (zh) 选择被叫接续网络的方法、装置及网络系统
WO2011020441A1 (fr) Procédé, système et passerelle d'accès permettant à des flux de services de partager des ressources
WO2013152472A1 (fr) Procédé et système de communication, dispositif de réseau d'accès et serveur d'application
JP2008503945A (ja) 単一ベアラサービスを介したマルチキャストサービス／ブロードキャストサービスのための適応型かつスケーラブルなＱｏＳアーキテクチャ
WO2014086280A1 (fr) Procédé, dispositif et système pour traiter un accès d'utilisateur à un réseau sans fil
WO2010015189A1 (fr) Nœud, procédé et système d'accès haut débit d'un réseau mobile à un réseau public
WO2012171172A1 (fr) Procédé de contrôle de politique, appareil associé, et système de contrôle de politique et de facturation
WO2018121384A1 (fr) Procédé, appareil et système de transmission de flux de données
KR102017167B1 (ko) 무선 통신 시스템에서 데이터 트래픽 분산을 위한 방법 및 장치
WO2013040980A1 (fr) Procédé de migration de flux, terminal et passerelle de réseau de données par paquets
WO2015120685A1 (fr) Procédé de sélection d'une passerelle de dérivation et contrôleur associé
WO2012159321A1 (fr) Procédé et dispositif de commande de qualité de service
WO2011157124A2 (fr) Procédé et dispositif de traitement de routage local et système de communication
CN102056327B (zh) 一种优化媒体路径的建立方法
WO2013104344A1 (fr) Procédé de communications à configuration en grappe, dispositif et système
WO2007147344A1 (fr) Procédé de restauration de transmission de données de plan d'utilisateur et entité de réseau évolué
CN102754460A (zh) 信息的指示方法及移动管理网元
JP5009970B2 (ja) ネットワーク接続装置による認証方法、ＱｏＳ制御方法、トラフィック制御方法およびＩＰ移動性制御方法
CN101399822B (zh) 确定媒体流路径关系的方法及呼叫控制系统

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180000644.5

Country of ref document: CN

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

Ref document number: 11795090

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11795090

Country of ref document: EP

Kind code of ref document: A2