WO2010075729A1 - 数据传输路径的控制方法和系统、移动性管理网元和终端 - Google Patents
数据传输路径的控制方法和系统、移动性管理网元和终端 Download PDFInfo
- Publication number
- WO2010075729A1 WO2010075729A1 PCT/CN2009/075439 CN2009075439W WO2010075729A1 WO 2010075729 A1 WO2010075729 A1 WO 2010075729A1 CN 2009075439 W CN2009075439 W CN 2009075439W WO 2010075729 A1 WO2010075729 A1 WO 2010075729A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network
- terminal
- data transmission
- transmission path
- capability information
- 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
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/14—Reselecting a network or an air interface
- H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/14—Reselecting a network or an air interface
- H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
- H04W36/1446—Reselecting a network or an air interface over a different radio air interface technology wherein at least one of the networks is unlicensed
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
Definitions
- TECHNICAL FIELD Embodiments of the present invention relate to communication technologies, and in particular, to a data transmission path control method and system, a mobility management network element, and a terminal.
- the convergence of mobile communication networks and broadband wireless access technologies is the evolution of telecommunication networks.
- the network network measurement report of the terminal determines the target network for the terminal. After that, the terminal directly switches its own radio frequency to the target network.
- the network anchor completes the bearer establishment of the terminal, the network anchors switch the corresponding user plane data transmission path from the source network to the target network.
- An aspect of the present invention provides a data transmission path control method and system, a mobility management network element, and a terminal, which are used to reduce the probability of terminal data loss during an inter-network handover process.
- Another aspect of the present invention provides a method for controlling a data transmission path, including: acquiring wireless access capability information of a terminal;
- the embodiment of the invention further provides a mobility management network element, including:
- An obtaining module configured to acquire wireless access capability information of the terminal
- a control module configured to perform, according to the wireless access capability information, cross-network handover control of a data transmission path corresponding to the terminal.
- the embodiment of the invention further provides a terminal, including:
- a radio access capability information sending module configured to send, by the network side, its own radio access capability information
- a receiving module configured to receive data by using a data transmission path determined by the network side according to the wireless access capability information.
- the embodiment of the present invention further provides a control system for a data transmission path, including a terminal and a network side device, where the network side device is configured to perform a data transmission path corresponding to the terminal according to the wireless access capability information. Inter-network switching control.
- the terminal reports its own radio access capability information to the network side, which is beneficial to the network side according to the access capability of the terminal.
- the inter-network handover control of the user plane data transmission path is performed for the terminal, so that the terminal with different access capabilities adopts a control policy matching the terminal access capability in the inter-network handover process to ensure that the terminal can correctly receive the inter-network handover process.
- the network anchor sends the data, thereby reducing the probability of data loss and jitter of data transmission.
- FIG. 1 is a flowchart of a method for controlling a data transmission path according to a first embodiment of the present invention
- FIG. 2 is a signaling interaction diagram of a method for controlling a data transmission path according to a second embodiment of the present invention
- FIG. 3 is a third embodiment of the present invention
- 3b is a schematic structural diagram of a trusted non-3GPP network according to an embodiment of the present invention.
- 3c is a schematic structural diagram of a non-trusted non-3GPP network according to an embodiment of the present invention.
- 3d is a schematic structural diagram of a 3GPP network according to an embodiment of the present invention.
- FIG. 4 is a signaling interaction diagram of a data transmission path control method according to a fourth embodiment of the present invention
- FIG. 5 is a signaling interaction diagram of a data transmission path control method according to a fifth embodiment of the present invention
- FIG. 7 is a schematic structural diagram of a mobility management network element according to a seventh embodiment of the present invention
- FIG. 8 is a schematic structural diagram of a terminal according to an eighth embodiment of the present invention
- FIG. 9 is a schematic structural diagram of a control system of a data transmission path according to a ninth embodiment of the present invention.
- DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The technical solutions of the present invention will be further described in detail below with reference to the accompanying drawings and embodiments.
- the technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, those of ordinary skill in the art are not All other embodiments obtained under the premise of creative labor are within the scope of the invention.
- FIG. 1 is a flowchart of a method for controlling a data transmission path according to a first embodiment of the present invention. As shown in FIG. 1, this embodiment includes:
- Step 11 Obtain wireless access capability information of the terminal.
- the terminal radio access capability information (UE Radio Capability) is used to indicate that the terminal establishes an air interface connection with the network side base station when the terminal accesses a certain radio access technology network, for example, the universal access terminal evolves.
- the parameters in the terminal radio access capability information include: Packet Data Convergence Protocol (PDCP) parameters and physical layer parameters. Radio frequency (RF) parameters, measurement parameters, and supported Inter Radio Access Technology (Inter-RAT) parameters.
- the Inter-RAT parameters include: The wireless access capability supported by the terminal is Single Rx/Tx mode, Dual Rx/Single Tx mode, or Dual RX/Dual Rx/ Tx) mode, etc.
- the radio access capability information of the terminal may be reported to the network side device, for example, the mobility management network element, in the initial attach procedure.
- the mobility management network element may send the obtained radio access capability information of the terminal to the eNodeB (the eNB for short), so that the eNB needs to use the radio access capability information of the terminal in the process of the terminal being activated from the idle state.
- the S1-AP (S1 application layer) message can be obtained from the mobility management network element, thereby reducing the waste of the air interface resources caused by the eNB acquiring the terminal radio access capability information from the air interface, which is beneficial to saving air interface resources.
- the wireless access capability information of the terminal may also be sent to the network side device in the Handover Attach Procedure.
- the wireless access capability information of the terminal may include: a single-issue mode or a dual-issue mode.
- the single shot mode can include: Single Rx/Tx mode or Double Rx/ Single Tx) mode, etc.
- Dual-issue mode can include: Dual dual-issue (Dua l Rx/Tx) mode.
- the radio access capability information includes a dual-receiver dual-issue terminal, that is, a terminal that supports dual-receiving dual-issue, and the terminal supports RF for different access technologies, and multiple RFs can receive data and transmit data at the same time. For example: While transmitting data and receiving data via the first network, the terminal also supports transmitting data and receiving data via the second network.
- the radio access capability information includes a terminal in a dual-receive single-issue mode, that is, a terminal that supports dual-acquisition, and the terminal supports RF for different access technologies, and multiple RFs can receive data at the same time, but only one RF can be sent.
- the function of the data For example: while the terminal sends data and receives data via the first network, it also supports receiving data via the second network, but does not support sending data via the second network; in this case, the data received by the terminal via the second network is usually not A broadcast message that the terminal needs to send the feedback information to the second network, such as: a system notification message, an advertisement message, etc., for the second network user plane data that requires the terminal to send feedback, because the terminal does not support the second network at this time.
- the second network base station will not detect the uplink signal of the terminal, after a certain time, the second network base station will consider that the terminal is not in the coverage, and stop transmitting the downlink data, thereby causing the terminal The second network user plane data cannot be received correctly.
- the radio access capability information includes a terminal in a single-receive single-issue mode, that is, a terminal that supports single-acquisition-issuing, and the terminal supports RF for different access technologies, and only one RF can receive data and send data at the same time. For example: While transmitting data and receiving data via the first network, the terminal does not support transmitting data and receiving data via the second network.
- Step 1 3 Perform inter-network handover control of the data transmission path corresponding to the terminal according to the wireless access capability information.
- the terminal needs to perform inter-network handover, that is, switch from the source network to the target network
- the terminal switches its own radio frequency from the source network to the target network.
- the target network side device may perform switching control of the corresponding user plane data transmission path for the inter-network handover of the terminal according to the radio access capability information of the terminal.
- the wireless access capability information of the terminal is a single-issue mode, such as a single-receive single-issue mode or a dual-receive single-issue mode
- the user plane data transmission path corresponding to the terminal may be configured before the target network establishes a bearer for the terminal. The source network switches to the target network.
- the user plane data transmission path corresponding to the terminal may be maintained in the source network before the target network establishes the bearer for the terminal, but After the target network establishes the bearer for the terminal, the user plane data transmission path corresponding to the terminal is switched from the source network to the target network; or, if the wireless access capability information of the terminal is in the dual-issue mode, for example: dual-receive dual-issue mode
- the connection establishment process to the network anchor point may be initiated only after the target network completes the bearer establishment of the terminal, and then the network anchor point is instructed to switch the data transmission path corresponding to the terminal from the source network to the Target network.
- the terminal does not support receiving data through the source network radio and receiving data through the source network radio, such as a terminal that supports single-acquisition, then when the target network establishes a bearer for the terminal, the terminals will Unable to receive the data sent by the network anchor, causing the terminal data to be lost.
- the requirement to correctly receive the data sent by the network anchor point is: The terminal needs to support the ability to send a feedback message through the corresponding network radio that sends the data.
- the access capability of the terminal supports receiving data through the target network radio, it can also receive data through the source network radio, but does not support sending data through the target network radio, and can also send data through the source network radio, that is, the terminal supports dual
- the access mode of the incoming call then, in the process of establishing the bearer for the terminal in the target network, although the terminals can receive the data sent by the network anchor, the terminals do not support sending the feedback to the network anchor through the source network radio.
- the source network base station will not detect the uplink signal of the terminal. After a certain time, the base station will consider that the terminal is not within the coverage and stop transmitting downlink data. As a result, the terminal cannot receive data correctly.
- the terminal performs the inter-network handover of the user plane data transmission path according to the radio access capability information of the terminal, so that the terminals with different access capabilities are connected to the terminal in the inter-network handover process.
- the control strategy of matching the capability ensures that the terminal can receive the data sent by the network anchor during the inter-network handover process, thereby reducing the probability of data loss and the jitter of data transmission.
- the radio access capability information of the terminal is the single-receive single-issue mode or the dual-receive single-issue mode
- the user-side data transmission path corresponding to the terminal may be switched from the source network to the target network before the target network establishes the bearer for the terminal.
- the terminal can receive data of the network anchor point through the user plane data transmission path of the target network and send feedback to the network anchor point, thereby reducing data loss of the terminal and reducing jitteriness of data transmission.
- FIG. 2 is a signaling interaction diagram of a method for controlling a data transmission path according to a second embodiment of the present invention.
- the difference between this embodiment and the embodiment shown in FIG. 1 is that the technical solution of the embodiment of the present invention is described by taking an example of inter-network handover between heterogeneous evolution networks.
- the source network in which the terminal is located is the source network of the embodiment of the present invention.
- the target evolved network to which the terminal needs to be handed over is the target network of the embodiment of the present invention, and the source network and the target network have a common network anchor point.
- this embodiment includes:
- Step 21 The terminal accesses the source network through the source network mobility management network element and the network anchor, and the terminal can access the service through the source network.
- Step 23 After determining that the target network is to be switched, the terminal sends an attach request (At tach Reques t) of the type to the target network mobility management network element, where the attach request carries the radio access capability information of the terminal, where
- the wireless access capability information includes: single-shot mode or dual-issue mode.
- the single-shot mode may include: a single-single-single (Single Rx/Tx) mode or a dual-single-single-single (Dua l Rx/Sing le Tx) mode; the dual-issue mode may include: Dua l Rx/Tx ) mode, etc.
- Step 25 Initiating an access process of the terminal to the target network.
- Step 27 The target network mobility management network element acquires the terminal according to the received attach request.
- the radio access capability information is used to determine the access capability of the terminal, and the corresponding handover control policy is matched with the radio access capability information of the terminal: If the radio access capability information of the terminal is a single-issue mode, such as: In the send mode or the dual-issue mode, perform steps 219-223.
- step 29-217 is performed, where step 29 and step 211 are optional steps, for example: if the target network mobility management The entity determines that the connection establishment to the network anchor point is not required to be initiated before the target network completes the bearer establishment of the terminal, and step 29 and step 211 need not be performed, and step 21 3-step 217 is directly executed.
- Step 29 If the target network mobility management network element determines that the access capability of the current terminal is in the dual-received dual-issue mode, the first indication information is sent to the network anchor, where the first indication information is used to indicate that the network anchor point is not
- the inter-network handover of the user plane data transmission path (User P ane Da ta Pa th ) is performed, that is, the user plane data transmission path of the terminal is maintained in the source network.
- the target network mobility management network element may send a connection establishment request to the network anchor point, indicating that the network anchor point does not perform the user plane data transmission path.
- the cross-network switching may be performed by the target network mobility management network element.
- the target network mobility management network element may also carry the indication information in the connection establishment request, to indicate that the network anchor point does not perform the cross-network handover of the user plane data transmission path.
- Step 211 The network anchor keeps the user plane data transmission path corresponding to the terminal in the source network according to the first indication information, and sends the first response information to the target network mobility management network element.
- the network anchor sends data to the terminal through the user plane data transmission path of the source network.
- the terminal can receive data from the network anchor through the source network radio and send feedback information to the network anchor.
- the connection establishment response message may be sent to the target network mobility management network element, to notify the target network to move to step 21, due to the target network mobility.
- the management network element determines that the access capability of the current terminal is supported.
- the dual-transmission dual-issue mode is adopted, so the target network initiates the corresponding bearer establishment process of the terminal, and completes the bearer establishment corresponding to the terminal in the target network.
- Step 215 After the target network completes the bearer establishment corresponding to the terminal, the target network mobility management network element sends the second indication information to the network anchor point, where the second indication information is used to indicate that the network anchor point performs the user plane corresponding to the terminal.
- the cross-network switching of the data transmission path is to switch the user plane data transmission path corresponding to the terminal from the source network to the target network.
- the target network mobility management network element may send a connection update request to the network anchor point, indicating that the network anchor point transmits the user plane data transmission path from the network
- the source network may be switched to the target network, or the target network mobility management network element may further carry an indication cell in the connection update request, to indicate that the network anchor switches the user plane data transmission path from the source network to the target network.
- Step 217 The network anchor, when receiving the second indication information, switches the user plane data transmission path corresponding to the terminal from the source network to the target network, and sends the second response information to the target network mobility management network element. Step 225 is performed.
- the network anchor sends data to the terminal through the user plane data transmission path of the target network.
- the terminal can receive data from the network anchor through the target network radio and send feedback information to the network anchor.
- the connection update response message may be sent to the target network mobility management network element, to notify the target network that the mobility management network element has been corresponding to the terminal.
- the user plane data transmission path is switched from the source network to the destination network.
- Step 219 If the target network mobility management network element determines that the current terminal access capability is in the single-receive single-issue mode or the dual-receive single-issue mode, the third indication information is sent to the network anchor, where the third indication information is used. Instructing the network anchor to perform an inter-network handover of the user plane data transmission path (User P Lane Da ta Pa th ), that is, switching the user plane data transmission path of the terminal from the source network to the target network.
- the target network mobility management network element may send a connection establishment request to the network anchor point, indicating that the network anchor point performs the user plane data transmission path.
- the network mobility management network element may also carry an indication cell in the connection establishment request, and is used to indicate that the network anchor performs the cross-network handover of the user plane data transmission.
- Step 221 The network anchor, when receiving the third indication information, switches the user plane data transmission path corresponding to the terminal from the source network to the target network, and sends the third response information to the target network mobility management network element.
- the network anchor sends data to the terminal through the user plane data transmission path of the target network.
- the terminal can receive data from the network anchor through the target network radio and send feedback information to the network anchor.
- the connection response message may be sent to the target network mobility management network element, to notify the target network that the mobility management network element has been corresponding to the terminal.
- the user plane data transmission path is switched from the source network to the destination network.
- Step 223 The target network initiates a corresponding bearer establishment process, and completes bearer establishment corresponding to the terminal in the target network, and step 225 is performed.
- Step 225 Complete the remaining cross-network handover process.
- the remaining inter-network handover process may further include a process of deactivating the allocation of resources corresponding to the network anchor starting source network and the terminal.
- the terminal reports its own radio access capability information to the target network mobility management network element in the handover attach procedure, and the target network mobility management network element performs the cross-network handover of the data transmission path according to the access capability of the terminal.
- Control that is, when the data anchor point indicates that the target network completes the bearer establishment of the terminal, whether the user plane data transmission path corresponding to the terminal needs to be switched from the source network to the target network, so that the terminal supporting different access capabilities is in the process, Both can correctly receive the data sent by the network anchor, which significantly reduces the probability of the terminal losing data and the data. The jitter of the transmission.
- the terminal may also send an attach request of the initial access to the mobility management network element in the initial access procedure of the network, and carry the wireless access of the terminal in the attach request. Capability information.
- the mobility management network element may send the obtained radio access capability information of the terminal to the eNodeB (the eNB for short), so that the eNB needs to use the radio access capability information of the terminal in the process of the terminal being activated from the idle state.
- the S1-AP (S1 application layer) message is obtained from the mobility management network element, thereby reducing the waste of air interface resources caused by the eNB acquiring the terminal radio access capability information from the air interface.
- FIG. 3 is a signaling interaction diagram of a method for controlling a data transmission path according to a third embodiment of the present invention.
- This embodiment differs from the embodiment shown in FIG. 2 of the present embodiment is that the present embodiment the target network is a third generation mobile communication embodiment Partnership Project (3 rd Generation Partnership Project, referred to as 3GPP) network, the source network is a non 3GPP (Non3GPP) Evolved The network, the network anchor point is a data packet network (referred to as PDN-GW), and the terminal supports the access capability as a single-receipt dual-issue or single-receipt single-issue mode.
- 3GPP Third Generation Partnership Project
- Non3GPP Non3GPP
- PDN-GW data packet network
- this embodiment includes:
- Step 31 The terminal accesses the non-3GPP network through the non-3GPP network mobility management network element, and the terminal can access the service through the non-3GPP network.
- the non-3GPP network may include: an untrusted non-3GPP (Nontrusted Non3GPP) evolved network and a trusted non-3GPP (Trusted Non3GPP) evolved network.
- an untrusted non-3GPP Nontrusted Non3GPP
- a trusted non-3GPP Trusted Non3GPP
- FIG. 3b is a schematic diagram of a trusted non-3GPP network structure according to an embodiment of the present invention.
- the terminal accesses the broadband access network
- the broadband access network establishes a tunnel connection to the data gateway
- the data gateway is connected to various service data networks, thereby establishing a terminal.
- the data gateway is a large-scale mobility anchor of the terminal, and is an interface entity of the core network and the packet data network.
- the user data is aggregated between the core network and the packet data network after being aggregated at the data gateway.
- the data gateway can be responsible for implementing access policies, filtering packets for terminals, and assigning IP addresses to terminals.
- the core control entity 1 may be an entity responsible for recording and managing information such as UE location information and authentication information.
- Core Control entity 2 may be the entity responsible for authenticating and charging the UE.
- a trusted non-3GPP (Nontrusted Non3GPP) evolved network such as: Code Division Multiple Access 2000 EV-DO (CDMA Division EV-DO), World Interoperability for Microwave Access (World Interoperability for Microwave Access, Referred to as WIMAX) network.
- CDMA Division EV-DO Code Division Multiple Access 2000 EV-DO
- WIMAX World Interoperability for Microwave Access
- FIG. 3c is a schematic diagram of a non-trusted non-3GPP network structure according to an embodiment of the present invention.
- the terminal in an untrusted non-3GPP network, the terminal establishes a tunnel connection to the border gateway through a specific broadband access network, the border gateway is connected to the data gateway through a tunnel, and the data gateway is connected to various packet data networks. Thereby establishing connectivity between the UE and the packet data network.
- the border gateway is an entity at the core network boundary and is responsible for establishing a secure tunnel between the UE and the core network.
- a data gateway can connect multiple border gateways, and each border gateway is responsible for establishing a secure tunnel for UEs in a local area.
- IWLAN Interworking Wireless Local Area Network
- the specific functional entities of the non-3GPP network mobility management network element are different for different non-3GPP networks.
- the functional entity of the IWLAN network mobility management network element is an IWLAN packet data gateway (Evolved Packet Data Gateway, ePDG); corresponding to the WIMAX network, the functional entity of the WIMAX network mobility management network element is the WIMAX access service.
- Step 33 After determining that the device is to be handed over to the 3GPP network, the terminal sends an attach request (Attach Request) of the type to the 3GPP network mobility management network element, where the attach request carries the wireless access capability information of the terminal, where the wireless connection Incoming capability information includes: Dual Rx/Single Tx mode or Single Rx/Tx mode.
- FIG. 3 is a schematic structural diagram of a 3GPP network according to an embodiment of the present invention.
- the terminal accesses the network through the access network, establishes a tunnel between the access network and the local service gateway under the control of the mobility management entity, and establishes a tunnel between the local service gateway and the data gateway, thereby establishing the UE and the grouping. Connectivity between data networks.
- the mobility management entity may be responsible for managing terminal location information, access authentication, non-access stratum signaling, and signaling security;
- the local service gateway is a small-range mobile data anchor of the terminal, and is a core network and an access network.
- the interface entity is responsible for routing and forwarding user data.
- the core control entity is an entity that records and manages user location information and authentication authorization information.
- the 3GPP network may include a 3G Long Term Evolution (LTE) or Legacy 3GPP, such as a Universal Terrestrial Radio Access Network (UTRAN) or an enhanced GPRS radio access. Network (GPRS Enhancement Radio Acces s Network, referred to as GERAN) and so on.
- LTE Long Term Evolution
- GERAN enhanced GPRS radio access. Network
- the specific functional entities of the 3GPP network mobility management network element are different for different 3GPP networks.
- the functional entity of the LTE network mobility management network element is a Mobility Management Entity (referred to as the E-E); corresponding to the Legacy 3GPP (UTRAN/GERAN) network, Legacy 3GPP (UTRAN/ GERAN)
- the functional entity of the network mobility management network element is a GPRS GPRS Suppering Node (SGSN).
- SGSN GPRS GPRS Suppering Node
- the terminal can report its own radio access capability information to the 3GPP mobility management network element in the initial access procedure, for example, when the terminal can report its own radio access capability information to the 3GPP mobility management network element, for example, Sending an attach request with an attach type as an initial access to the 3GPP mobility management network element, and carrying the radio access capability information of the terminal in the attach request.
- Step 35 Initiate an access process of the terminal to the target network.
- Step 37 The 3GPP network mobility management network element obtains the radio access capability information of the terminal according to the received attach request, and determines the access capability of the terminal, and adopts a corresponding handover control policy that matches the radio access capability information of the terminal. .
- the radio access capability information of the terminal is a dual-receive single-issue mode or a single-receive single-issue mode
- the 3GPP network mobility management network element determines that the user plane data needs to be transmitted during the bearer establishment process for the terminal in the 3GPP network. Switch to Target network.
- Step 39 The 3GPP network mobility management network element sends a connection establishment request message to the PDN-GW via a serving gateway (Serv- ng Ga t eWay, S-GW for short), where the connection establishment request is used to indicate that the PDN-GW is the user of the terminal.
- the face data transmission path is handed over from a non-3GPP network to a 3GPP network.
- Step 31 When receiving the connection establishment request message, the PDN-GW switches the user plane data transmission path corresponding to the terminal from the non-3GPP network to the 3GPP network, and then sends a connection establishment response message to the 3GPP network mobility management network element.
- the PDN-GW transmits data to the terminal through the user plane data transmission path of the 3GPP network.
- the terminal can receive data from the PDN-GW through the 3GPP network radio.
- Step 31 After the bearer establishment procedure of the 3GPP network initiating the terminal, after the bearer establishment corresponding to the terminal in the 3GPP network is completed, step 31 5 is performed.
- Step 31 Complete the remaining cross-network switching process.
- the remaining inter-network handover procedure may further include a process in which the PDN-GW initiates deactivation of allocated resources corresponding to the non-3GPP network and the terminal.
- the 3GPP mobility management network element determines the handover control scheme of the user plane data path for the terminal according to the access capability of the terminal, that is, the 3GPP mobility management.
- the network element acquiring the radio access capability information of the terminal includes supporting the single-issue mode, for example, supporting the dual-receive single-issue mode or supporting the single-receive single-issue mode, and the 3GPP mobility management network element indicates the PDN-GW before the 3GPP network bearer setup is completed.
- the user plane data transmission path of the terminal is switched from the non-3GPP network to the 3GPP network, so that the single-receiving dual-issue terminal or the single-receive single-issue terminal receives data through the data transmission path of the user plane of the 3GPP network in the 3GPP network bearer establishment process.
- FIG. 4 is a signaling interaction diagram of a method for controlling a data transmission path according to a fourth embodiment of the present invention.
- the terminal supports the access capability as dual-received dual-issue.
- this embodiment includes: Step 41: The terminal accesses the non-3GPP network through the non-3GPP network mobility management network element and the network anchor, and the terminal can perform service access through the non-3GPP network.
- the non-3GPP network may include: an untrusted non-3GPP (Non- rusted Non3GPP) evolved network and a trusted non-3GPP (Trusted Non3GPP) evolved network.
- Non-trusted non-3GPP (Non- rusted Non3GPP) evolved networks such as: IWALAN networks, etc.; trusted non-3GPP evolved networks such as: CDMA2000 EV-D0, WIMAX network, etc.
- the specific functional entities of the non-3GPP network mobility management network element are different for different non-3GPP networks.
- the functional entity of the IWLAN network mobility management network element is IWLAN ePDG
- the functional entity of the WIMAX network mobility management network element is WIMAX ASN GW
- CDMA2000 EV-DO network CDMA2000 EV-DO
- the functional entity of the network mobility management network element is HRPD AN or HSGW.
- Step 43 After determining to switch to the 3GPP network, the terminal sends an attach request (At tach Reques t) of the type to the 3GPP network mobility management network element, where the attach request carries the radio access capability information of the terminal, where The wireless access capability information includes: dual-receiving dual-issue (Dua l Rx/Tx) mode.
- the 3GPP network may include LTE or Legacy 3GPP (UTRAN/GERAN) and the like.
- the specific functional entities of the 3GPP network mobility management network element are different for different 3GPP networks.
- the functional entity of the LTE network mobility management network element is ⁇ E
- the functional entity of the Legacy 3GPP (UTRAN/GERAN) network mobility management network element is the SGSN.
- the terminal can report its own radio access capability information to the 3GPP mobility management network element in the initial access procedure, for example, when the terminal can report its own radio access capability information to the 3GPP mobility management network element, for example, Sending an attach request with an attach type as an initial access to the 3GPP mobility management network element, and carrying the radio access capability information of the terminal in the attach request.
- Step 45 Initiate an access process of the terminal to the target network.
- Step 47 The 3GPP network mobility management network element acquires the terminal according to the received attach request.
- the radio access capability information is used to judge the access capability of the terminal, and adopts a corresponding handover control policy that matches the radio access capability information of the terminal.
- the 3GPP network mobility management network element may determine that the user plane data transmission path needs to be maintained in the non-3GPP network before the 3GPP network establishes the bearer for the terminal, but in the 3GPP. After the network establishes a bearer for the terminal, the user plane data transmission path is switched from the non-3GPP network to the 3GPP network.
- the 3GPP network applies different bearer establishment modes based on different communication protocols that are followed between the 3GPP Network Service Gateway (Serving GateWay, S-GW for short) and the PDN-GW.
- the first mode is that the bearer binding control function is on the Serving GW, and the Serving GW can obtain the information required for the establishment of the 3GPP bearer, such as: QoS rules.
- step 49a and steps are performed. 411a (Steps 49a and 411a are not shown in FIG. 4).
- Step 49a The 3GPP network mobility management network element sends a connection establishment request to the serving gateway S-GW.
- Step 411a After receiving the connection establishment request, the S-GW sends a connection establishment response to the 3GPP network mobility management network element, and informs the mobility management network element terminal of the corresponding information in the connection establishment response information.
- the second mode is that the bearer binding control function is on the PDN-GW, and only the PDN GW can obtain the information required for the establishment of the 3GPP bearer, for example, the QoS rule. In this case, after performing step 47, step 49b is performed. Step 411b.
- Step 49b The 3GPP network mobility management network element sends a connection establishment request message to the PDN-GW via a Serving GateWay (S-GW), where the connection establishment request is used to instruct the PDN-GW not to transmit the user plane data of the terminal.
- S-GW Serving GateWay
- the path is switched from the non-3GPP network to the 3GPP network, that is, the user plane data transmission path of the terminal is maintained in the non-3GPP network.
- Step 411b When receiving the connection establishment request message, the PDN-GW maintains the user plane data transmission path corresponding to the terminal in the non-3GPP network, and sends a connection establishment response message to the 3GPP network target network mobility management network element. At this time, the network anchor transmits data to the terminal through the user plane data transmission path of the non-3GPP network. Correspondingly, the terminal can receive data from the PDN-GW through the non-3GPP network radio.
- Step 413 The 3GPP network initiates a corresponding bearer establishment process of the terminal.
- Step 415 When the 3GPP network establishes a bearer corresponding to the terminal, the 3GPP network mobility management network element sends a connection establishment update message to the PDN-GW via the S-GW, where the connection setup update message is used to indicate that the PDN-GW performs the terminal with the terminal.
- the cross-network handover of the corresponding user plane data transmission path, that is, the user plane data transmission path corresponding to the terminal is switched from the non-3GPP network to the 3GPP network.
- Step 417 When receiving the connection establishment update message, the PDN-GW switches the user plane data transmission path corresponding to the terminal from the non-3GPP network to the 3GPP network, and sends a connection update response message to the 3GPP network mobility management network element.
- the PDN-GW transmits data to the terminal through the user plane data transmission path of the 3GPP network.
- the terminal can receive data from the PDN-GW through the 3GPP network radio.
- Step 419 Complete the remaining cross-network handover process.
- the remaining inter-network handover procedure may further include a process in which the PDN-GW initiates deactivation of allocated resources corresponding to the non-3GPP network and the terminal.
- the 3GPP mobility management network element determines the handover control scheme of the user plane data path for the terminal according to the access capability of the terminal, that is, in the 3GPP mobility.
- the management network element obtains the wireless access capability information of the terminal to support the dual-issue mode, for example, supports the dual-receive dual-issue mode, and after the 3GPP network bearer is established, instructs the PDN-GW to transmit the user plane data transmission path of the terminal from the non-3GPP network.
- the dual-receiving dual-issue terminal receives data through the data transmission path of the non-3GPP network user plane during the 3GPP network bearer establishment process, and significantly reduces the jitter in the data transmission process.
- FIG. 5 is a signaling interaction diagram of a method for controlling a data transmission path according to a fifth embodiment of the present invention.
- the source network in this embodiment is a 3GPP network
- the target network is a non-3GPP ( Non3GPP) evolved network
- the network anchor point is a data packet network (referred to as PDN-GW)
- the terminal Support access capability is dual-issue or single-issue single-issue mode.
- this Examples include:
- Step 51 The terminal accesses the 3GPP network through the 3GPP network mobility management network element, and the terminal can access the service through the 3GPP network.
- the 3GPP network may include LTE or Legacy 3GPP, such as UTRAN or GERAN.
- the specific functional entities of the 3GPP network mobility management network element are different for different 3GPP networks.
- the functional entity of the LTE network mobility management network element is the MME;
- the Legacy 3GPP, such as the UTRAN or the GERAN network the functional entity of the network mobility management network element is the SGSN.
- Step 53 After determining that the device is to be switched to the non-3GPP network, the terminal sends an attach request (At tach Reques t) of the type to the non-3GPP network mobility management network element, where the attach request carries the radio access capability information of the terminal.
- the wireless access capability information includes: Dua l Rx/S ing le Tx mode or Single single (S ing le Rx/Tx) mode.
- the non-3GPP network may include: an untrusted non-3GPP (Non- rusted Non3GPP) evolved network and a trusted non-3GPP (Trusted Non3GPP) evolved network.
- Non-trusted non-3GPP (Non- rusted Non3GPP) evolved networks such as: IWALAN networks, etc.; trusted non-3GPP evolved networks such as: CDMA2000 EV-D0, WIMAX network, etc.
- the specific functional entities of the non-3GPP network mobility management network element are different for different non-3GPP networks.
- the functional entity of the IWLAN network mobility management network element is IWLAN ePDG
- the functional entity of the WIMAX network mobility management network element is WIMAX ASN GW
- the functional entity of the network mobility management network element is HRPD AN or HSGW.
- the terminal can report its own radio access capability information to the non-3GPP mobility management network element in the initial access procedure, except that the terminal can report its own radio access capability information to the non-3GPP mobility management network element in the handover attach procedure.
- the attachment request with the attachment type being the initial access is sent to the non-3GPP mobility management network element, and the radio access capability information of the terminal is carried in the attachment request.
- Step 55 Initiating an access process of the terminal to the target network.
- Step 57 The non-3GPP network mobility management network element acquires the terminal according to the received attach request.
- the wireless access capability information, and the access capability of the terminal is judged, and a corresponding handover control strategy matching the wireless access capability information of the terminal is adopted.
- the non-3GPP network mobility management network element determines that the non-3GPP network needs to establish a bearer for the terminal, and the user plane data transmission path is switched to Target network.
- Step 59 The non-3GPP network mobility management network element sends a connection establishment request message to the PDN-GW, where the connection establishment request is used to instruct the PDN-GW to switch the user plane data transmission path of the terminal from the non-3GPP network to the non-3GPP network.
- Step 511 When receiving the connection establishment request message, the PDN-GW switches the user plane data transmission path corresponding to the terminal from the 3GPP network to the non-3GPP network, and then sends a connection establishment response message to the non-3GPP network mobility management network element.
- the PDN-GW transmits data to the terminal through the user plane data transmission path of the non-3GPP network.
- the terminal can receive data from the PDN-GW through the non-3GPP network radio.
- Step 513 A non-3GPP network initiates a corresponding bearer establishment process, and after the bearer establishment corresponding to the terminal in the non-3GPP network is completed, step 515 is performed.
- Step 515 Complete the remaining cross-network handover process.
- the remaining inter-network handover procedure may further include a process in which the PDN-GW initiates deactivation of the allocated resources of the 3GPP network and the terminal.
- the non-3GPP mobility management network element determines the handover control scheme of the user plane data path for the terminal according to the access capability of the terminal, that is, in the non-3GPP.
- the mobility management network element obtains the radio access capability information of the terminal to support a single-issue mode, such as: supporting a dual-receive single-issue mode or a single-receive single-issue mode, and indicating that the PDN-GW will be used before the non-3GPP network bearer is established.
- the user plane data transmission path of the terminal is switched from the 3GPP network to the non-3GPP network, so that the dual-receive single-issue terminal or the single-receive single-issue terminal receives data through the data transmission path of the non-3GPP network user plane in the non-3GPP network bearer establishment process. , significantly reduces the probability of data loss and reduces jitter in the data transfer process.
- FIG. 6 is a signaling interaction diagram of a method for controlling a data transmission path according to a sixth embodiment of the present invention.
- the difference between this embodiment and the embodiment shown in FIG. 5 is that the terminal supports the access capability in the dual-receive dual-issue mode.
- this embodiment includes:
- Step 61 The terminal accesses the 3GPP network through the 3GPP network mobility management network element, and the terminal can access the service through the 3GPP network.
- the 3GPP network may include LTE or Legacy 3GPP, such as UTRAN/GERAN and the like.
- the specific functional entities of the 3GPP network mobility management network element are different for different 3GPP networks.
- the functional entity of the LTE network mobility management network element is ⁇ E;
- Legacy 3GPP such as UTRAN/GERAN, the functional entity of the network mobility management network element is the SGSN.
- Step 63 After determining that the device is to be switched to the non-3GPP network, the terminal sends an attach request (At tach Reques t) of the type to the non-3GPP network mobility management network element, where the attach request carries the radio access capability information of the terminal.
- the wireless access capability information includes: dual-issue dual-issue (Dua l Rx/Tx) mode.
- the non-3GPP network may include: an untrusted non-3GPP (Non- rusted Non3GPP) evolved network and a trusted non-3GPP (Trusted Non3GPP) evolved network.
- Non-trusted non-3GPP (Non- rusted Non3GPP) evolved networks such as: IWLAN networks, etc.; trusted non-3GPP evolved networks such as: CDMA2000 EV-D0, WIMAX network, and the like.
- the specific functional entities of the non-3GPP network mobility management network element are different for different non-3GPP networks.
- the functional entity of the IWLAN network mobility management network element is IWLAN ePDG
- the functional entity of the WIMAX network mobility management network element is WIMAX ASN GW
- the functional entity of the network mobility management network element is HRPD AN or HSGW.
- the terminal can report its own radio access capability information to the non-3GPP mobility management network element in the initial access procedure, except that the terminal can report its own radio access capability information to the non-3GPP mobility management network element in the handover attach procedure.
- the attachment request with the attachment type being the initial access is sent to the non-3GPP mobility management network element, and the radio access capability information of the terminal is carried in the attachment request.
- Step 65 Initiate an access process of the terminal to the target network.
- Step 67 The non-3GPP network mobility management network element acquires radio access capability information of the terminal according to the received attach request, and determines the access capability of the terminal, and adopts corresponding handover control that matches the radio access capability information of the terminal.
- the non-3GPP network mobility management network element determines that the connection establishment to the network anchor point is not initiated before the non-3GPP network establishes the bearer for the terminal, and the radio access capability information of the terminal is in the dual-received dual-issue mode. After the non-3GPP network establishes a bearer for the terminal, the network anchor is instructed to switch the user plane data transmission path from the 3GPP network to the non-3GPP network.
- Step 69 The non-3GPP network initiates a corresponding bearer establishment procedure of the terminal.
- Step 611 When the non-3GPP network establishes a bearer corresponding to the terminal, the non-3GPP network mobility management network element sends a connection establishment update message to the PDN-GW, where the connection setup update message is used to instruct the PDN-GW to perform the corresponding Inter-network handover of the user plane data transmission path, that is, the user plane data transmission path corresponding to the terminal is switched from the 3GPP network to the non-3GPP network.
- Step 613 When receiving the connection establishment update message, the PDN-GW switches the user plane data transmission path corresponding to the terminal from the 3GPP network to the non-3GPP network, and does not send the connection update response message to the 3GPP network mobility management network element.
- the PDN-GW transmits data to the terminal through the user plane data transmission path of the non-3GPP network.
- the terminal can receive data from the PDN-GW through the non-3GPP network radio.
- Step 615 completing the remaining cross-network switching process.
- the remaining inter-network handover procedure may further include a process in which the PDN-GW initiates deactivation of the allocated resources of the 3GPP network and the terminal.
- the non-3GPP mobility management network element determines the handover control scheme of the user plane data path for the terminal according to the access capability of the terminal, that is, in the non-3GPP.
- the mobility management network element obtains the wireless access capability information of the terminal to support the dual-issue mode, for example, supports the dual-receive dual-issue mode, and after the non-3GPP network bearer is established, instructs the PDN-GW to change the user plane data transmission path of the terminal from 3GPP network handover to non-3GPP The network, so that the dual-receiving dual-issue terminal receives data through the data transmission path of the user plane of the 3GPP network during the non-3GPP network bearer establishment process, which significantly reduces the jitter in the data transmission process.
- FIG. 7 is a schematic structural diagram of a mobility management network element according to a seventh embodiment of the present invention. As shown in FIG. 7, the mobility management network element of this embodiment includes: an obtaining module 71 and a control module 72.
- the obtaining module 71 is configured to obtain wireless access capability information of the terminal.
- the control module 72 is configured to perform cross-network handover control of the data transmission path corresponding to the terminal according to the radio access capability information.
- the obtaining module 71 may include: a first acquiring unit 71 1 .
- the first obtaining unit 71 1 is configured to acquire radio access capability information of the terminal in a handover network attaching procedure of the terminal.
- control module 72 may include: a first switching indication unit 721 and a second switching indication unit 722.
- the first handover instructing unit 721 is configured to: when the radio access capability information includes the single-issue mode, instruct the network anchor point to perform a data transmission path corresponding to the terminal before the target network completes the bearer establishment of the terminal The source network switches to the target network.
- the second handover indication unit 722 is configured to: when the radio access capability information includes the dual-issue mode, and after the target network completes the bearer establishment of the terminal, instruct the network anchor to perform a data transmission path corresponding to the terminal, Switch from the source network to the target network.
- the second handover indication unit 722 is further configured to: when the radio access capability information of the terminal is in the dual-issue mode, indicate that the network anchor point is to be connected to the terminal before the target network completes the bearer establishment of the terminal. The corresponding data transmission path remains on the source network.
- the terminal performs the inter-network handover of the user plane data transmission path according to the radio access capability information of the terminal, so that the terminal with different access capabilities adopts a control strategy matching the terminal access capability in the inter-network handover process to ensure The terminal can correctly receive the data sent by the network anchor during the inter-network handover process, thereby reducing the probability of data loss and jitter of data transmission.
- the acquiring module of the mobility management network element in this embodiment may be further configured to acquire radio access capability information of the terminal in an initial network attaching process of the terminal, and send the radio access capability information to a base station. .
- the mobility management network element may send the obtained radio access capability information of the terminal to the eNodeB (the eNB for short), so that the eNB can use the radio access capability information of the terminal in the service processing procedure.
- the Sl-AP (S1 application layer) message is obtained from the mobility management network element, thereby reducing the waste of air interface resources caused by the eNB acquiring the terminal radio access capability information from the air interface.
- FIG. 8 is a schematic structural diagram of a terminal according to an eighth embodiment of the present invention. As shown in FIG. 8, the terminal of this embodiment includes: a radio access capability information sending module 81 and a receiving and feedback module 82.
- the radio access capability information sending module 81 is configured to send its own radio access capability information to the network side.
- the receiving and feedback module 82 is configured to receive data and send feedback information to the network side by using a data transmission path determined by the network side according to the radio access capability information.
- the terminal reports its own radio access capability information to the network side, which facilitates the network side to perform inter-network handover control of the user plane data transmission path according to the access capability of the terminal, so that terminals with different access capabilities are in the cross.
- a control strategy matching the terminal access capability is adopted to ensure that the terminal can correctly receive the data sent by the network anchor point during the inter-network handover process, thereby reducing the probability of data loss and the jitter of data transmission.
- FIG. 9 is a schematic structural diagram of a control system of a data transmission path according to a ninth embodiment of the present invention.
- the control system of the data transmission path of this embodiment includes: a terminal 91 and a network side device 92.
- the terminal 91 is configured to send its own radio access capability information to the network side device 92.
- the network side device 92 is configured to perform inter-network handover control of the data transmission path corresponding to the terminal 91 according to the radio access capability information of the terminal 91. .
- the network side device 92 may include: target network mobility management Network element 922 and network anchor point 923.
- the target network mobility management network element 922 is configured to send an indication of an inter-network handover of the data transmission path corresponding to the terminal 91 to the network anchor 923 according to the radio access capability information of the terminal 91.
- the network anchor 923 is configured to perform handover of the user plane data transmission path corresponding to the terminal 91 from the source network to the target network according to the indication information from the target network mobility management network element 922.
- the terminal reports its own radio access capability information to the network side, which facilitates the network side to perform inter-network handover control of the user plane data transmission path according to the access capability of the terminal, so that terminals with different access capabilities are in the cross.
- a control strategy matching the terminal access capability is adopted to ensure that the terminal can correctly receive the data sent by the network anchor point during the inter-network handover process, thereby reducing the probability of data loss and the jitter of data transmission.
- modules in the apparatus in the embodiments may be distributed in the apparatus of the embodiment as described in the embodiments, or may be correspondingly changed in one or more apparatuses different from the embodiment.
- the modules of the above embodiments may be combined into one module, or may be further split into a plurality of sub-modules.
- the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Description
数据传输路径的控制方法和系统、 移动性管理网元和终端 本申请要求于 2008 年 12 月 30 日提交中国专利局、 申请号为 200810247593. 6 , 发明名称为 "数据传输路径的控制方法和系统、 移动性 管理网元和终端" 的中国专利申请的优先权, 其全部内容通过引用结合在 本申请中。 技术领域 本发明实施例涉及通信技术, 特别是涉及一种数据传输路径的控制方 法和系统、 移动性管理网元和终端。 景技术 移动通信网络与宽带无线接入技术的融合是电信网络的演进趋势。 网 络演进后形成的多种异质演进网络之间, 存在公共的网络锚点。 因此, 终 端可选择接入某一种演进网络, 获得所需的业务服务; 且在保证终端业务 连续性的前提下, 终端还可在异质演进网络之间进行跨网切换。
现有技术在异质演进网络之间进行跨网切换流程中, 如果终端的网络 网络测量报告, 为终端确定目标网络。 之后, 终端将自身射频直接切换到 目标网络; 而网络锚点在目标网络完成终端的承载建立时, 将与终端相应 的用户面数据传输路径从源网络切换到目标网络。
发明人在实现本发明实施例过程中发现, 现有技术异质演进网络之间 进行跨网切换的流程中, 存在跨网切换过程中终端数据丟失几率较高的技 术缺陷。 发明内容
本发明一方面提供一种数据传输路径的控制方法和系统、 移动性管理 网元和终端, 用于降低跨网切换过程中终端数据丟失的几率。
本发明另一方面提供了一种数据传输路径的控制方法, 包括: 获取终端的无线接入能力信息;
根据所述无线接入能力信息, 进行与所述终端相应的数据传输路径的 跨网切换控制。
本发明实施例还提供了一种移动性管理网元, 包括:
获取模块, 用于获取终端的无线接入能力信息;
控制模块, 用于根据所述无线接入能力信息, 进行与所述终端相应的 数据传输路径的跨网切换控制。
本发明实施例还提供了一种终端, 包括:
无线接入能力信息发送模块, 用于向网络侧发送自身的无线接入能力 信息;
接收模块, 用于通过网络侧根据所述无线接入能力信息确定的数据传 输路径, 接收数据。
本发明实施例还提供了一种数据传输路径的控制系统, 包括终端和网 络侧设备; 所述网络侧设备用于根据所述无线接入能力信息, 进行与所述终端相 应的数据传输路径的跨网切换控制。
本发明各实施例分别提供的数据传输路径的控制方法和系统、 移动性 管理网元和终端中, 通过终端向网络侧上报自身的无线接入能力信息, 有 利于网络侧根据终端的接入能力为终端进行用户面数据传输路径的跨网切 换控制, 使得不同接入能力的终端在跨网切换过程中采用与终端接入能力 匹配的控制策略, 保证终端在跨网切换过程中能够正确接收到网络锚点发 送的数据, 从而降低数据丟失的几率和数据传送的抖动。
附图说明 为了更清楚地说明本发明实施例或现有技术中的技术方案, 下面将对 实施例或现有技术描述中所需要使用的附图作简单地介绍, 显而易见地, 下面描述中的附图仅仅是本发明的一些实施例, 对于本领域普通技术人员 来讲, 在不付出创造性劳动性的前提下, 还可以根据这些附图获得其他的 附图。
图 1为本发明第一实施例提供的数据传输路径的控制方法流程图; 图 2为本发明第二实施例提供的数据传输路径的控制方法信令交互图; 图 3a 为本发明第三实施例提供的数据传输路径的控制方法信令交互 图;
图 3b为本发明实施例可信任的非 3GPP网络结构示意图;
图 3c为本发明实施例不可信任的非 3GPP网络结构示意图;
图 3d为本发明实施例 3GPP网络结构示意图;
图 4为本发明第四实施例提供的数据传输路径的控制方法信令交互图; 图 5为本发明第五实施例提供的数据传输路径的控制方法信令交互图; 图 6为本发明第六实施例提供的数据传输路径的控制方法信令交互图; 图 7为本发明第七实施例提供的移动性管理网元结构示意图; 图 8为本发明第八实施例提供的终端结构示意图;
图 9为本发明第九实施例提供的数据传输路径的控制系统结构示意图。 具体实施方式 下面通过附图和实施例, 对本发明的技术方案做进一步的详细描述。 下面将结合本发明实施例中的附图, 对本发明实施例中的技术方案进行清 楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而 不是全部的实施例。 基于本发明中的实施例, 本领域普通技术人员在没有
作出创造性劳动前提下所获得的所有其他实施例, 都属于本发明保护的范 围。
图 1 为本发明第一实施例提供的数据传输路径的控制方法流程图。 如 图 1所示, 本实施例包括:
步骤 11、 获取终端的无线接入能力信息。
终端无线接入能力信息 (UE Radio Capability)用于表示终端接入某 种无线接入技术网络时, 终端与网络侧基站建立空口连接可以支持的各种 参数, 例如:在终端接入演进的通用陆地无线接入网 (Evolved Universal Terrestrial Radio Access Network, 简称 E_UTRAN) 网络时,其终端无线 接入能力信息中的参数包括了: 分组数据聚合协议 ( Packet Data Convergence Protocol , 简称 PDCP ) 参数、 物理层参数、 射频 ( Radio Frequency,简称 RF )参数、测量参数、支持的异质无线接入技术( Inter Radio Access Technology, 简称 Inter - RAT)参数等信息。 其中, Inter - RAT参 数包括: 终端支持的无线接入能力是单收单发(Single Rx/Tx )模式、 双 收单发(Dual Rx/ Single Tx )模式、 或双收双发(Dual Rx/Tx )模式等。
终端的无线接入能力信息可在初始网络附着 ( Initial Attach Procedure)流程中, 上报给网络侧设备, 例如移动性管理网元。 该情形下, 移动性管理网元可将获取的终端的无线接入能力信息发送给基站( eNodeB, 简称 eNB), 以便 eNB在终端从空闲态激活的过程中需要使用终端的无线接 入能力信息时, 可通过 Sl-AP (S1应用层)消息从该移动性管理网元获取, 因而减少了 eNB从空口上获取终端无线接入能力信息而造成的空口资源的 浪费, 有利于节约空口资源。
或者, 终端的无线接入能力信息还可在切换网络附着流程(Handover Attach Procedure ) 中, 上才艮给网络側设备。
终端的无线接入能力信息可包括: 单发模式或双发模式。 其中, 单发 模式可包括: 单收单发 ( Single Rx/Tx )模式或双收单发 ( Dual Rx/ Single
Tx )模式等; 双发模式可包括: 双收双发(Dua l Rx/Tx )模式等。
无线接入能力信息包括双收双发模式的终端, 即支持双收双发的终端, 该终端支持针对不同接入技术的 RF ,多个 RF可在同一时间接收数据和发送 数据的功能。 例如: 终端经由第一网络发送数据和接收数据的同时, 还支 持经由第二网络发送数据和接收数据。
无线接入能力信息包括双收单发模式的终端, 即支持双收单发的终端, 该终端支持针对不同接入技术的 RF , 多个 RF可在同一时间接收数据,但只 有一个 RF可发送数据的功能。 例如: 终端经由第一网络发送数据和接收数 据的同时, 还支持经由第二网络接收数据, 但不支持经由第二网络发送数 据; 该情形下, 终端经由第二网络接收到的数据通常为不需要终端向第二 网络发送反馈信息即可正确接收的广播消息, 如: 系统通知消息、 广告消 息等, 对于需要终端发送反馈的第二网络用户面数据, 由于终端此时不支 持通过第二网络射频向第二网络发送反馈的能力, 第二网络基站将检测不 到终端的上行信号, 在一定时间后, 第二网络基站会认为终端不在覆盖范 围之内, 而停止发送下行数据, 从而导致终端不能正确接收第二网络用户 面数据。
无线接入能力信息包括单收单发模式的终端, 即支持单收单发的终端, 该终端支持针对不同接入技术的 RF ,在同一时间只有一个 RF可接收数据和 发送数据的功能 。 例如: 终端经由第一网络发送数据和接收数据的同时, 不支持经由第二网络发送数据和接收数据。
步骤 1 3、 根据上述无线接入能力信息, 进行与所述终端相应的数据传 输路径的跨网切换控制。
如果终端需要进行跨网切换, 即从源网络切换到目标网络, 在源网络 侧设备为终端确定目标网络后, 终端将自身射频从源网络切换到目标网络。 此时, 目标网络侧设备可根据终端的无线接入能力信息, 为终端的跨网切 换进行相应的用户面数据传输路径的切换控制。 例如:
如果终端的无线接入能力信息为单发模式, 如: 单收单发模式或者双 收单发模式, 则可在目标网络为终端建立好承载之前, 将与终端相应的用 户面数据传输路径由源网络切换到目标网络。 如果终端的无线接入能力信 息为双发模式, 如: 双收双发模式, 则可在目标网络为终端建立好承载之 前, 将与终端相应的用户面数据传输路径保持在源网络, 而在目标网络为 终端建立好承载之后, 再将与终端相应的用户面数据传输路径由源网络切 换到目标网络; 或者, 如果终端的无线接入能力信息为双发模式, 如: 双 收双发模式, 还可仅在目标网络完成所述终端的承载建立之后, 才发起到 网络锚点的连接建立过程, 此时再指示网络锚点将与所述终端相应的数据 传输路径, 从源网络切换到目标网络。
发明人在实现本发明实施例过程中发现, 在跨网切换流程中, 现有技 术终端首先将自身射频从源网络切换到目标网络, 之后, 终端可通过目标 网络射频接收数据; 而网络侧只有在目标网络为终端建立好承载之后, 才 将用户面数据传输路径由源网络切换到目标网络, 在此阶段, 网络锚点通 过源网络的用户面数据传输路径向终端发送数据。 如果终端的接入能力不 支持在通过目标网络射频接收数据的同时还可通过源网络射频接收数据, 如支持单收单发的终端, 那么, 在目标网络为终端建立承载过程中, 这些 终端将无法接收到网络锚点下发的数据, 造成终端数据丟失。 此外, 正确 接收网络锚点下发的数据的要求是: 需要终端支持通过发送数据的相应网 络射频发送反馈消息的能力。 如果终端的接入能力虽然支持通过目标网络 射频接收数据的同时还可通过源网络射频接收数据, 但不支持通过目标网 络射频发送数据的同时还可通过源网络射频发送数据, 即该终端支持双收 单发的接入模式, 那么, 在目标网络为终端建立承载过程中, 这些终端虽 然可接收到网络锚点下发的数据, 但由于这些终端不支持通过源网络射频 向网络锚点发送反馈的能力, 源网络基站将检测不到终端的上行信号, 在 一定时间后, 基站会认为终端不在覆盖范围之内, 而停止发送下行数据,
从而导致终端不能正确接收数据。
区别于现有技术的是, 本实施例根据终端的无线接入能力信息, 为终 端进行用户面数据传输路径的跨网切换, 使得不同接入能力的终端在跨网 切换过程中采用与终端接入能力匹配的控制策略, 保证终端在跨网切换过 程中能够接收到网络锚点发送的数据, 从而降低数据丟失的几率和数据传 送的抖动。 如果终端的无线接入能力信息为单收单发模式或双收单发模式, 则可在目标网络为终端建立好承载之前, 将与终端相应的用户面数据传输 路径由源网络切换到目标网络, 使得终端可通过目标网络的用户面数据传 输路径接收网络锚点的数据并向网络锚点发送反馈, 从而降低终端的数据 丟失, 并降低数据传送的抖动性。
图 2为本发明第二实施例提供的数据传输路径的控制方法信令交互图。 本实施例与图 1 所示的实施例的区别在于, 本实施例以异质演进网络之间 的跨网切换为例, 对本发明实施例的技术方案进行说明。 终端所在的源演 进网络即为本发明实施例的源网络, 终端需切换到的目标演进网络即为本 发明实施例的目标网络, 源网络和目标网络存在着公共的网络锚点。如图 2 所示, 本实施例包括:
步骤 21、 终端已通过源网络移动性管理网元和网络锚点接入源网络, 终端可通过源网络进行业务访问。
步骤 23、 在确定要切换到目标网络后, 终端向目标网络移动性管理网 元发送类型为切换的附着请求(At tach Reques t ), 该附着请求中携带有终 端的无线接入能力信息, 其中无线接入能力信息包括: 单发模式或双发模 式。 其中, 单发模式可包括: 单收单发(S ing le Rx/Tx )模式或双收单发 ( Dua l Rx/ S ing le Tx )模式等; 双发模式可包括: 双收双发 ( Dua l Rx/Tx ) 模式等。
步骤 25、 发起终端到目标网络的接入过程。
步骤 27、 目标网络移动性管理网元根据接收的附着请求, 获取终端的
无线接入能力信息, 并对终端的接入能力进行判断, 采取与终端的无线接 入能力信息匹配的相应切换控制策略: 如果终端的无线接入能力信息为单 发模式, 如: 单收单发模式或双收单发模式时, 执行步骤 219-223。 如果终 端的无线接入能力信息为双发模式(如: 双收双发模式)时, 执行步骤 29- 步骤 217 , 其中, 步骤 29和步骤 211为可选步骤, 例如: 如果目标网络移 动性管理实体确定在目标网络完成终端的承载建立之前, 不需要发起到网 络锚点的连接建立,则不需要执行步骤 29和步骤 211 ,而直接执行步骤 21 3- 步骤 217。
步骤 29、 如果目标网络移动性管理网元确定当前终端的接入能力为支 持双收双发模式时, 则向网络锚点发送第一指示信息, 该第一指示信息用 于指示网络锚点不进行用户面数据传输路径 (User P l ane Da ta Pa th ) 的 跨网切换, 即将终端的用户面数据传输路径保持在源网络。
在目标网络移动性管理网元向网络锚点发送第一指示信息时, 可通过 目标网络移动性管理网元向网络锚点发送连接建立请求的方式, 指示网络 锚点不进行用户面数据传输路径的跨网切换; 或者, 目标网络移动性管理 网元还可在连接建立请求中携带指示信元, 用于指示网络锚点不进行用户 面数据传输路径的跨网切换。
步骤 211、 网络锚点根据第一指示信息,将与终端相应的用户面数据传 输路径保持在源网络, 向目标网络移动性管理网元发送第一回应信息。
此时, 网络锚点通过源网络的用户面数据传输路径向终端发送数据。 相应的, 终端可通过源网络射频接收来自网络锚点的数据并向网络锚点发 送反馈信息。
在网络锚点向目标网络移动性管理网元发送第一回应信息时, 可通过 向目标网络移动性管理网元发送连接建立回应消息, 用于通知目标网络移 步骤 21 3、由于目标网络移动性管理网元确定当前终端的接入能力为支
持双收双发模式, 因而目标网络发起终端相应的承载建立流程, 完成目标 网络中与终端相应的承载建立。
步骤 215、在目标网络完成与终端相应的承载建立后, 目标网络移动性 管理网元向网络锚点发送第二指示信息, 该第二指示信息用于指示网络锚 点进行与终端相应的用户面数据传输路径的跨网切换, 即将与终端相应的 用户面数据传输路径从源网络切换到目标网络。
在目标网络移动性管理网元向网络锚点发送第二指示信息时, 可通过 目标网络移动性管理网元向网络锚点发送连接更新请求的方式, 指示网络 锚点将用户面数据传输路径从源网络切换到目标网络, 或者, 目标网络移 动性管理网元还可在连接更新请求中携带指示信元, 用于指示网络锚点将 用户面数据传输路径从源网络切换到目标网络。
步骤 217、 网络锚点在接收第二指示信息时,将与终端相应的用户面数 据传输路径从源网络切换到目标网络, 向目标网络移动性管理网元发送第 二回应信息; 执行步骤 225。
此时, 网络锚点通过目标网络的用户面数据传输路径向终端发送数据。 相应的, 终端可通过目标网络射频接收来自网络锚点的数据并向网络锚点 发送反馈信息。
在网络锚点向目标网络移动性管理网元发送第二回应信息时, 可通过 向目标网络移动性管理网元发送连接更新回应消息, 用于通知目标网络移 动性管理网元已将与终端相应的用户面数据传输路径从源网络切换到目标 网络。
步骤 219、如果目标网络移动性管理网元确定当前终端的接入能力为支 持单收单发模式或双收单发模式时, 则向网络锚点发送第三指示信息, 该 第三指示信息用于指示网络锚点进行用户面数据传输路径 (User P lane Da ta Pa th ) 的跨网切换, 即将终端的用户面数据传输路径从源网络切换到 目标网络。
在目标网络移动性管理网元向网络锚点发送第三指示信息时 , 可通过 目标网络移动性管理网元向网络锚点发送连接建立请求的方式, 指示网络 锚点进行用户面数据传输路径的跨网切换, 或者, 目标网络移动性管理网 元还可在连接建立请求中携带指示信元, 用于指示网络锚点进行用户面数 据传输的跨网切换。
步骤 221、 网络锚点在接收第三指示信息时,将与终端相应的用户面数 据传输路径从源网络切换到目标网络, 向目标网络移动性管理网元发送第 三回应信息。
此时, 网络锚点通过目标网络的用户面数据传输路径向终端发送数据。 相应的, 终端可通过目标网络射频接收来自网络锚点的数据并向网络锚点 发送反馈信息。
在网络锚点向目标网络移动性管理网元发送第三回应信息时, 可通过 向目标网络移动性管理网元发送连接回应消息, 用于通知目标网络移动性 管理网元已将与终端相应的用户面数据传输路径从源网络切换到目标网 络。
步骤 223、 目标网络发起终端相应的承载建立流程,完成目标网络中与 终端相应的承载建立, 执行步骤 225。
步骤 225、 完成剩余的跨网切换流程。
剩余的跨网切换流程还可包括网络锚点启动源网络与终端相应的分配 资源的去激活等流程。
本实施例通过终端在切换附着流程中, 向目标网络移动性管理网元上 报自身的无线接入能力信息, 由目标网络移动性管理网元根据终端的接入 能力进行数据传输路径的跨网切换控制, 即指示数据锚点在目标网络完成 终端的承载建立时, 是否需要将与终端相应的用户面数据传输路径从源网 络切换到目标网络, 使得支持不同接入能力的终端在该过程中, 都能够正 确接收到网络锚点发送的数据, 明显减低了终端丟失数据的几率以及数据
传输的抖动性。
在本实施例技术方案的基石出上, 终端还可在网络初始接入流程中, 向 移动性管理网元发送类型为初始接入的附着请求, 并在该附着请求中携带 终端的无线接入能力信息。 该情形下, 移动性管理网元可将获取的终端的 无线接入能力信息发送给基站(eNodeB, 简称 eNB), 以便 eNB在终端从空 闲态激活的过程中需要使用终端的无线接入能力信息时, 可通过 S 1 - AP ( S 1 应用层) 消息从该移动性管理网元获取, 因而减少了 eNB从空口上获取终 端无线接入能力信息而造成的空口资源的浪费。
图 3a 为本发明第三实施例提供的数据传输路径的控制方法信令交互 图。 本实施例与图 2 所示的实施例的区别在于, 本实施例目标网络为第三 代移动通信标准化伙伴项目 ( 3rd Generation Partnership Project, 简称 3GPP) 网络, 源网络为非 3GPP (Non3GPP)演进网络, 网络锚点为数据分组 网络(简称 PDN-GW), 终端支持接入能力为单收双发或单收单发模式。 如图 3a所示, 本实施例包括:
步骤 31、 终端已通过非 3GPP网络移动性管理网元接入非 3GPP网络, 终端可通过非 3GPP网络进行业务访问。
非 3GPP网络可包括: 不可信任的非 3GPP (Nontrusted Non3GPP )演进 网络和可信任的非 3GPP (Trusted Non3GPP )演进网络。
图 3b为本发明实施例可信任的非 3GPP网络结构示意图。如图 3b所示, 在可信任的非 3GPP网络中, 终端接入宽带接入网络, 宽带接入网建立到数 据网关的隧道连接, 数据网关再连接到各种业务数据网, 从而建立了终端 和分组数据网 (Packet Data Network, 简称 PDN )之间的连通性。 数据网 关是终端的大范围移动锚点, 并且是核心网和分组数据网的接口实体, 用 户数据在数据网关处聚合后在核心网和分组数据网间传输。 数据网关可以 负责实施访问策略、 为终端过滤数据包及为终端分配 IP地址等。 核心控制 实体 1可以是负责记录和管理 UE位置信息和认证信息等信息的实体。 核心
控制实体 2可以是负责对 UE进行认证授权和计费的实体。
可信任的非 3GPP (Nontrusted Non3GPP ) 演进网络例如: 码分多址接 2000EV-DO ( Code Division Multiple Access2000 EV-DO, 简称 CDMA2000 EV-DO ), 全球微波接入互通技术 (World Interoperability for Microwave Access,简称 WIMAX) 网络等。
图 3c为本发明实施例不可信任的非 3GPP网络结构示意图。如图 3c所 示, 在不可信任的非 3GPP网络中, 终端通过特定的宽带接入网络建立到边 界网关的隧道连接, 边界网关通过隧道连接到数据网关, 数据网关再连接 到各种分组数据网, 从而建立了 UE和分组数据网之间的连通性。 其中, 边 界网关是一个处于核心网边界的实体, 负责建立 UE到核心网之间的安全隧 道。 一个数据网关可以连接多个边界网关, 每个边界网关负责建立一个局 部区域内的 UE的安全隧道。
不可信任的非 3GPP 演进网络例如: 无线局域互联网 ( Interworking Wireless Local Area Network, 简称 IWLAN)等。
针对不同的非 3GPP网络, 非 3GPP网络移动性管理网元具体的功能实 体不同。 例如: 对应 IWLAN网络, IWLAN网络移动性管理网元的功能实体为 IWLAN 分组数据网关(Evolved Packet Data Gateway, 简称 ePDG ); 对应 WIMAX网络, WIMAX网络移动性管理网元的功能实体为 WIMAX接入服务网络 网关(Access Serving Network Gateway,简称 ASN GW);对应 CDMA2000 EV-DO 网络, CDMA2000 EV-DO网络移动性管理网元的功能实体为 HRPD AN或 HRPD 服务网关 (HRPD Serving GateWay, 简称 HSGW)。
步骤 33、 在确定要切换到 3GPP网络后, 终端向 3GPP网络移动性管理 网元发送类型为切换的附着请求(Attach Request ), 该附着请求中携带有 终端的无线接入能力信息,其中无线接入能力信息包括:双收单发( Dual Rx/ Single Tx)模式或单收单发(Single Rx/Tx )模式等。
图 3d为本发明实施例 3GPP网络结构示意图。 如图 3d所示, 在 3GPP
网络中, 终端通过接入网接入网络, 在移动性管理实体的控制下在接入网 和本地服务网关间建立隧道, 本地服务网关和数据网关之间也建立隧道, 从而建立了 UE和分组数据网之间的连通性。 这里也可以是 UE到数据网关 之间直接建立隧道。 其中移动性管理实体可以负责管理终端位置信息、 接 入鉴权、 非接入层信令及信令安全等; 本地服务网关是终端的小范围移动 的数据锚点, 是核心网和接入网的接口实体, 负责用户数据的路由转发。 核心控制实体是记录和管理用户位置信息、 认证授权信息的实体。
3GPP网络可包括 3G长期演进网络 ( Long Term Evolut ion, 简称 LTE ) 或 Legacy 3GPP, 例如通用地面无线接入网 ( Universa l Terres tr ia l Radio Acces s Network , 简称 UTRAN ) 或者增强的 GPRS 无线接入网络 ( GPRS Enhancement Radio Acces s Network, 简称 GERAN ) )等。 针对不同的 3GPP 网络, 3GPP网络移动性管理网元具体的功能实体不同。 例如: 对应 LTE网 络, LTE 网络移动性管理网元的功能实体为移动性管理实体 (Mobi l i ty Management Ent i ty, 简称丽 E ); 对应 Legacy 3GPP ( UTRAN/GERAN ) 网络, Legacy 3GPP ( UTRAN/GERAN ) 网络移动性管理网元的功能实体为 GPRS服务 支持节点 (Serv ing GPRS Suppor t ing Node, 简称 SGSN )。
终端除了在切换附着流程中可向 3GPP移动性管理网元上报自身的无线 接入能力信息时, 也可在初始接入流程中向 3GPP移动性管理网元上报自身 的无线接入能力信息, 例如: 向 3GPP移动性管理网元发送附着类型为初始 接入的附着请求, 并在该附着请求中携带终端的无线接入能力信息。
步骤 35、 发起终端到目标网络的接入过程。
步骤 37、 3GPP网络移动性管理网元根据接收的附着请求, 获取终端的 无线接入能力信息, 并对终端的接入能力进行判断, 采取与终端的无线接 入能力信息匹配的相应切换控制策略。 例如, 由于终端的无线接入能力信 息为双收单发模式或单收单发模式时, 因此, 3GPP 网络移动性管理网元确 定需要在 3GPP网络为终端建立承载过程中, 将用户面数据传输路径切换到
目标网络。
步骤 39、 3GPP网络移动性管理网元经由服务网关(Serv i ng Ga t eWay , 简称 S-GW ) 向 PDN-GW发送连接建立请求消息, 该连接建立请求用于指示 PDN-GW将终端的用户面数据传输路径从非 3GPP网络切换到 3GPP网络。
步骤 31 1、 PDN-GW在接收连接建立请求消息时, 将与终端相应的用户 面数据传输路径从非 3GPP网络切换到 3GPP网络, 之后, 向 3GPP网络移动 性管理网元发送连接建立回应消息。
此时, PDN-GW通过 3GPP网络的用户面数据传输路径向终端发送数据。 相应的, 终端可通过 3GPP网络射频接收来自 PDN-GW的数据。
步骤 31 3、 3GPP网络发起终端相应的承载建立流程, 3GPP网络中与终 端相应的承载建立完成之后, 执行步骤 31 5。
步骤 31 5、 完成剩余的跨网切换流程。
剩余的跨网切换流程还可包括 PDN-GW启动非 3GPP网络与终端相应的 分配资源的去激活等流程。
本实施例终端在非 3GPP网络到 3GPP网络之间的跨网切换过程中 , 3GPP 移动性管理网元根据终端的接入能力, 为终端确定用户面数据路径的切换 控制方案, 即 3GPP移动性管理网元获取终端的无线接入能力信息包括支持 单发模式, 例如支持双收单发模式或支持单收单发模式, 可在 3GPP网络承 载建立完成之前, 3GPP移动性管理网元指示 PDN-GW将终端的用户面数据传 输路径从非 3GPP网络切换到 3GPP网络, 从而使得单收双发终端或单收单 发终端在 3GPP网络承载建立过程中, 通过 3GPP网络用户面的数据传输路 径接收数据, 明显减少了数据的丟失几率且降低了数据传送过程中的抖动 性。
图 4为本发明第四实施例提供的数据传输路径的控制方法信令交互图。 本实施例与图 3a所示的实施例的区别在于, 本实施例终端支持接入能力为 双收双发。 如图 4所示, 本实施例包括:
步骤 41、 终端已通过非 3GPP 网络移动性管理网元和网络锚点接入非 3GPP网络, 终端可通过非 3GPP网络进行业务访问。
非 3GPP网络可包括: 不可信任的非 3GPP ( Nont rus ted Non3GPP )演进 网络和可信任的非 3GPP ( Trus ted Non3GPP )演进网络。 不可信任的非 3GPP ( Nont rus ted Non3GPP )演进网络例如: IWALAN网络等; 可信任的非 3GPP 演进网络例如: CDMA2000 EV-D0、 WIMAX网络等。
针对不同的非 3GPP网络, 非 3GPP网络移动性管理网元具体的功能实 体不同。 例如: 对应 IWLAN网络, IWLAN网络移动性管理网元的功能实体为 IWLAN ePDG; 对应 WIMAX 网络, WIMAX 网络移动性管理网元的功能实体为 WIMAX ASN GW; 对应 CDMA2000 EV-DO网络, CDMA2000 EV-DO网络移动性管 理网元的功能实体为 HRPD AN或 HSGW。
步骤 43、 在确定要切换到 3GPP网络后, 终端向 3GPP网络移动性管理 网元发送类型为切换的附着请求(At tach Reques t ), 该附着请求中携带有 终端的无线接入能力信息,其中无线接入能力信息包括:双收双发( Dua l Rx/ Tx )模式等。
3GPP网络可包括 LTE或 Legacy 3GPP ( UTRAN/GERAN )等。 针对不同的 3GPP 网络, 3GPP 网络移动性管理网元具体的功能实体不同。 例如: 对应 LTE网络, LTE网络移动性管理网元的功能实体为丽 E; 对应 Legacy 3GPP ( UTRAN/GERAN ) 网络, Legacy 3GPP ( UTRAN/GERAN ) 网络移动性管理网元 的功能实体为 SGSN。
终端除了在切换附着流程中可向 3GPP移动性管理网元上报自身的无线 接入能力信息时, 也可在初始接入流程中向 3GPP移动性管理网元上报自身 的无线接入能力信息, 例如: 向 3GPP移动性管理网元发送附着类型为初始 接入的附着请求, 并在该附着请求中携带终端的无线接入能力信息。
步骤 45、 发起终端到目标网络的接入过程。
步骤 47、 3GPP网络移动性管理网元根据接收的附着请求, 获取终端的
无线接入能力信息, 并对终端的接入能力进行判断, 采取与终端的无线接 入能力信息匹配的相应切换控制策略。 终端的无线接入能力信息为双收双 发模式时, 3GPP网络移动性管理网元可确定: 需要在 3GPP网络为终端建 立承载之前, 将用户面数据传输路径保持在非 3GPP网络, 而在 3GPP网络 为终端建立承载之后, 将用户面数据传输路径从非 3GPP 网络切换到 3GPP 网络。
基于 3GPP 网络服务网关(Serving GateWay, 简称 S-GW)与 PDN-GW 之间遵循的通信协议不同, 3GPP 网络应用不同的承载建立方式。 第一种方 式是承载绑定控制功能在 Serving GW上,并且, Serving GW能够获取 3GPP 承载建立需要的信息, 如: QoS规则, 在该情形下, 则在执行步骤 47后, 执行步骤 49a和步骤 411a (图 4中未示出执行步骤 49a和步骤 411a )。
步骤 49a、 3GPP网络移动性管理网元向服务网关 S-GW发送连接建立请 求。
步骤 411a、 在 S-GW在接收连接建立请求后, 向 3GPP网络移动性管理 网元发送连接建立回应, 在连接建立回应信息中告知移动性管理网元终端 载建立的相应信息。
第二种方式是承载绑定控制功能在 PDN-GW上, 并且, 只有 PDN GW能 够获取 3GPP承载建立需要的信息, 如: QoS规则, 该情形下, 则在执行步 骤 47后, 执行步骤 49b和步骤 411b。
步骤 49b、 3GPP网络移动性管理网元经由服务网关( Serving GateWay, 简称 S-GW) 向 PDN-GW发送连接建立请求消息, 该连接建立请求用于指示 PDN-GW不要将终端的用户面数据传输路径从非 3GPP网络切换到 3GPP网络, 即将终端的用户面数据传输路径保持在非 3GPP网络。
步骤 411b、 PDN-GW在接收连接建立请求消息时, 将与终端相应的用户 面数据传输路径保持在非 3GPP网络, 向 3GPP网络目标网络移动性管理网 元发送连接建立回应消息;
此时, 网络锚点通过非 3GPP网络的用户面数据传输路径向终端发送数 据。 相应的, 终端可通过非 3GPP网络射频接收来自 PDN-GW的数据。
步骤 413、 3GPP网络发起终端相应的承载建立流程。
步骤 415、 在 3GPP网络建立与终端相应的承载完成时, 3GPP网络移动 性管理网元经由 S-GW向 PDN-GW发送连接建立更新消息, 该连接建立更新 消息用于指示 PDN-GW进行与终端相应的用户面数据传输路径的跨网切换, 即将与终端相应的用户面数据传输路径从非 3GPP网络切换到 3GPP网络。
步骤 417、 PDN-GW在接收连接建立更新消息时, 将与终端相应的用户 面数据传输路径从非 3GPP网络切换到 3GPP网络, 向 3GPP网络移动性管理 网元发送连接更新回应消息。
此时, PDN-GW通过 3GPP网络的用户面数据传输路径向终端发送数据。 相应的, 终端可通过 3GPP网络射频接收来自 PDN-GW的数据。
步骤 419、 完成剩余的跨网切换流程。
剩余的跨网切换流程还可包括 PDN-GW启动非 3GPP网络与终端相应的 分配资源的去激活等流程。
本实施例终端在非 3GPP网络到 3GPP网络之间的跨网切换过程中, 3GPP 移动性管理网元根据终端的接入能力, 为终端确定用户面数据路径的切换 控制方案, 即在 3GPP移动性管理网元获取终端的无线接入能力信息为支持 双发模式, 如支持双收双发模式, 可在 3GPP网络承载建立完成之后, 指示 PDN-GW将终端的用户面数据传输路径从非 3GPP网络切换到 3GPP网络, 从 而使得双收双发终端在 3GPP网络承载建立过程中, 通过非 3GPP网络用户 面的数据传输路径接收数据, 明显降低了数据传送过程中的抖动性。
图 5为本发明第五实施例提供的数据传输路径的控制方法信令交互图。 本实施例与图 3a所示的实施例的区别在于, 本实施例源网络为 3GPP网络, 目标网络为非 3GPP ( Non3GPP )演进网络, 网络锚点为数据分组网络(简称 PDN-GW ), 终端支持接入能力为双收单发或单收单发模式。 如图 5所示, 本
实施例包括:
步骤 51、 终端已通过 3GPP网络移动性管理网元接入 3GPP网络, 终端 可通过 3GPP网络进行业务访问。
3GPP网络可包括 LTE或 Legacy 3GPP , 如 UTRAN或 GERAN等。 针对不 同的 3GPP网络, 3GPP网络移动性管理网元具体的功能实体不同。 例如: 对应 LTE 网络, LTE 网络移动性管理网元的功能实体为 MME; 对应 Legacy 3GPP , 如 UTRAN或 GERAN网络, 网络移动性管理网元的功能实体为 SGSN。
步骤 53、 在确定要切换到非 3GPP网络后, 终端向非 3GPP网络移动性 管理网元发送类型为切换的附着请求(At tach Reques t ), 该附着请求中携 带有终端的无线接入能力信息, 其中无线接入能力信息包括: 双收单发 ( Dua l Rx/S ing le Tx )模式或单收单发(S ing le Rx/Tx )模式等。
非 3GPP网络可包括: 不可信任的非 3GPP ( Nont rus ted Non3GPP )演进 网络和可信任的非 3GPP ( Trus ted Non3GPP )演进网络。 不可信任的非 3GPP ( Nont rus ted Non3GPP )演进网络例如: IWALAN网络等; 可信任的非 3GPP 演进网络例如: CDMA2000 EV-D0、 WIMAX网络等。
针对不同的非 3GPP网络, 非 3GPP网络移动性管理网元具体的功能实 体不同。 例如: 对应 IWLAN网络, IWLAN网络移动性管理网元的功能实体为 IWLAN ePDG; 对应 WIMAX 网络, WIMAX 网络移动性管理网元的功能实体为 WIMAX ASN GW; 对应 CDMA2000 EV-D0网络, CDMA2000 EV-D0网络移动性管 理网元的功能实体为 HRPD AN或 HSGW。
终端除了在切换附着流程中可向非 3GPP移动性管理网元上报自身的无 线接入能力信息时, 也可在初始接入流程中向非 3GPP移动性管理网元上报 自身的无线接入能力信息, 例如: 向非 3GPP移动性管理网元发送附着类型 为初始接入的附着请求, 并在该附着请求中携带终端的无线接入能力信息。
步骤 55、 发起终端到目标网络的接入过程。
步骤 57、非 3GPP网络移动性管理网元根据接收的附着请求,获取终端
的无线接入能力信息, 并对终端的接入能力进行判断, 采取与终端的无线 接入能力信息匹配的相应切换控制策略。 终端的无线接入能力信息为双收 单发模式或单收单发模式时, 非 3GPP 网络移动性管理网元确定需要在非 3GPP网络为终端建立承载过程中,将用户面数据传输路径切换到目标网络。
步骤 59、 非 3GPP网络移动性管理网元向 PDN-GW发送连接建立请求消 息, 该连接建立请求用于指示 PDN-GW将终端的用户面数据传输路径从非 3GPP网络切换到非 3GPP网络。
步骤 511、 PDN-GW在接收连接建立请求消息时, 将与终端相应的用户 面数据传输路径从 3GPP网络切换到非 3GPP网络, 之后, 向非 3GPP网络移 动性管理网元发送连接建立回应消息。
此时, PDN-GW通过非 3GPP 网络的用户面数据传输路径向终端发送数 据。 相应的, 终端可通过非 3GPP网络射频接收来自 PDN-GW的数据。
步骤 513、非 3GPP网络发起终端相应的承载建立流程,非 3GPP网络中 与终端相应的承载建立完成之后, 执行步骤 515。
步骤 515、 完成剩余的跨网切换流程。
剩余的跨网切换流程还可包括 PDN-GW启动 3GPP网络与终端相应的分 配资源的去激活等流程。
本实施例终端在 3GPP网络到非 3GPP网络之间的跨网切换过程中, 非 3GPP移动性管理网元根据终端的接入能力, 为终端确定用户面数据路径的 切换控制方案, 即在非 3GPP移动性管理网元获取终端的无线接入能力信息 为支持单发模式,如: 支持双收单发模式或支持单收单发模式,可在非 3GPP 网络承载建立完成之前,指示 PDN-GW将终端的用户面数据传输路径从 3GPP 网络切换到非 3GPP网络,从而使得双收单发终端或单收单发终端在非 3GPP 网络承载建立过程中, 通过非 3GPP网络用户面的数据传输路径接收数据, 明显减少了数据的丟失几率且降低了数据传送过程中的抖动性。
图 6为本发明第六实施例提供的数据传输路径的控制方法信令交互图。
本实施例与图 5 所示的实施例的区别在于, 本实施例终端支持接入能力为 双收双发模式。 如图 6所示, 本实施例包括:
步骤 61、 终端已通过 3GPP网络移动性管理网元接入 3GPP网络, 终端 可通过 3GPP网络进行业务访问。
3GPP网络可包括 LTE或 Legacy 3GPP , 如 UTRAN/GERAN等。 针对不同 的 3GPP网络, 3GPP网络移动性管理网元具体的功能实体不同。 例如: 对 应 LTE网络, LTE网络移动性管理网元的功能实体为丽 E;对应 Legacy 3GPP 网络, Legacy 3GPP , 如 UTRAN/GERAN, 网络移动性管理网元的功能实体为 SGSN。
步骤 63、 在确定要切换到非 3GPP网络后, 终端向非 3GPP网络移动性 管理网元发送类型为切换的附着请求(At tach Reques t ), 该附着请求中携 带有终端的无线接入能力信息, 其中无线接入能力信息包括: 双收双发 ( Dua l Rx/ Tx )模式等。
非 3GPP网络可包括: 不可信任的非 3GPP ( Nont rus ted Non3GPP )演进 网络和可信任的非 3GPP ( Trus ted Non3GPP )演进网络。 不可信任的非 3GPP ( Nont rus ted Non3GPP )演进网络例如: IWLAN网络等; 可信任的非 3GPP 演进网络例如: CDMA2000 EV-D0、 WIMAX网络等。
针对不同的非 3GPP网络, 非 3GPP网络移动性管理网元具体的功能实 体不同。 例如: 对应 IWLAN网络, IWLAN网络移动性管理网元的功能实体为 IWLAN ePDG; 对应 WIMAX 网络, WIMAX 网络移动性管理网元的功能实体为 WIMAX ASN GW; 对应 CDMA2000 EV-D0网络, CDMA2000 EV-D0网络移动性管 理网元的功能实体为 HRPD AN或 HSGW。
终端除了在切换附着流程中可向非 3GPP移动性管理网元上报自身的无 线接入能力信息时, 也可在初始接入流程中向非 3GPP移动性管理网元上报 自身的无线接入能力信息, 例如: 向非 3GPP移动性管理网元发送附着类型 为初始接入的附着请求, 并在该附着请求中携带终端的无线接入能力信息。
步骤 65、 发起终端到目标网络的接入过程。
步骤 67、非 3GPP网络移动性管理网元根据接收的附着请求,获取终端 的无线接入能力信息, 并对终端的接入能力进行判断, 采取与终端的无线 接入能力信息匹配的相应切换控制策略。 由于终端的无线接入能力信息为 双收双发模式时, 因此, 非 3GPP网络移动性管理网元确定: 需要在非 3GPP 网络为终端建立承载之前, 不发起到网络锚点的连接建立, 而仅在非 3GPP 网络为终端建立承载之后, 指示网络锚点将用户面数据传输路径从 3GPP网 络切换到非 3GPP网络。
步骤 69、 非 3GPP网络发起终端相应的承载建立流程。
步骤 611、在非 3GPP网络建立与终端相应的承载完成时,非 3GPP网络 移动性管理网元向 PDN-GW发送连接建立更新消息, 该连接建立更新消息用 于指示 PDN-GW进行与终端相应的用户面数据传输路径的跨网切换, 即将与 终端相应的用户面数据传输路径从 3GPP网络切换到非 3GPP网络。
步骤 613、 PDN-GW在接收连接建立更新消息时, 将与终端相应的用户 面数据传输路径从 3GPP网络切换到非 3GPP网络, 非向 3GPP网络移动性管 理网元发送连接更新回应消息。
此时, PDN-GW通过非 3GPP 网络的用户面数据传输路径向终端发送数 据。 相应的, 终端可通过非 3GPP网络射频接收来自 PDN-GW的数据。
步骤 615、 完成剩余的跨网切换流程。
剩余的跨网切换流程还可包括 PDN-GW启动 3GPP网络与终端相应的分 配资源的去激活等流程。
本实施例终端在 3GPP网络到非 3GPP网络之间的跨网切换过程中, 非 3GPP移动性管理网元根据终端的接入能力, 为终端确定用户面数据路径的 切换控制方案, 即在非 3GPP移动性管理网元获取终端的无线接入能力信息 为支持双发模式, 如支持双收双发模式, 可在非 3GPP网络承载建立完成之 后, 指示 PDN-GW将终端的用户面数据传输路径从 3GPP网络切换到非 3GPP
网络, 从而使得双收双发终端在非 3GPP 网络承载建立过程中, 通过 3GPP 网络用户面的数据传输路径接收数据, 明显降低了数据传送过程中的抖动 性。
图 7 为本发明第七实施例提供的移动性管理网元结构示意图。 如图 7 所示, 本实施例移动性管理网元包括: 获取模块 71和控制模块 72。
获取模块 71用于获取终端的无线接入能力信息。
控制模块 72用于根据所述无线接入能力信息,进行与所述终端相应的 数据传输路径的跨网切换控制。
在上述技术方案的基石出上, 获取模块 71可包括: 第一获取单元 71 1。 第一获取单元 71 1用于在所述终端的切换网络附着流程中, 获取所述 终端的无线接入能力信息。
进一步, 在上述技术方案的基 上, 控制模块 72可包括: 第一切换指 示单元 721和第二切换指示单元 722。
第一切换指示单元 721用于在所述无线接入能力信息包括单发模式时, 指示网络锚点在目标网络完成所述终端的承载建立之前, 将与所述终端相 应的数据传输路径, 从源网络切换到目标网络。
第二切换指示单元 722用于在所述无线接入能力信息包括双发模式时, 且在目标网络完成所述终端的承载建立之后, 指示网络锚点将与所述终端 相应的数据传输路径, 从源网络切换到目标网络。 在上述技术方案的基础 上, 第二切换指示单元 722还可用于在终端的无线接入能力信息为双发模 式时, 指示网络锚点在目标网络完成所述终端的承载建立之前, 将与终端 相应的数据传输路径保持在源网络。
本实施例根据终端的无线接入能力信息, 为终端进行用户面数据传输 路径的跨网切换, 使得不同接入能力的终端在跨网切换过程中采用与终端 接入能力匹配的控制策略, 保证终端在跨网切换过程中能够正确接收到网 络锚点发送的数据, 从而降低数据丟失的几率和数据传送的抖动。
此外, 本实施例移动性管理网元的获取模块还可用于在所述终端的初 始网络附着流程中, 获取所述终端的无线接入能力信息, 并将所述无线接 入能力信息向基站发送。
该情形下, 移动性管理网元可将获取的终端的无线接入能力信息发送 给基站( eNodeB , 简称 eNB ), 以便 eNB在业务处理流程中需要使用终端的 无线接入能力信息时, 可通过 Sl-AP ( S1 应用层) 消息从该移动性管理网 元获取, 因而减少了 eNB从空口上获取终端无线接入能力信息而造成的空 口资源的浪费。
图 8为本发明第八实施例提供的终端结构示意图。 如图 8所示, 本实 施例终端包括: 无线接入能力信息发送模块 81和接收和反馈模块 82。
无线接入能力信息发送模块 81用于向网络侧发送自身的无线接入能力 信息。
接收和反馈模块 82用于通过网络侧根据所述无线接入能力信息确定的 数据传输路径, 接收数据并向网络侧发送反馈信息。
本实施例通过终端向网络侧上报自身的无线接入能力信息, 有利于网 络侧根据终端的接入能力为终端进行用户面数据传输路径的跨网切换控 制, 使得不同接入能力的终端在跨网切换过程中采用与终端接入能力匹配 的控制策略, 保证终端在跨网切换过程中能够正确接收到网络锚点发送的 数据, 从而降低数据丟失的几率和数据传送的抖动。
图 9为本发明第九实施例提供的数据传输路径的控制系统结构示意图。 如图 9所示, 本实施例数据传输路径的控制系统包括: 终端 91和网络侧设 备 92。
终端 91用于向所述网络侧设备 92发送自身的无线接入能力信息; 网络侧设备 92用于根据终端 91的无线接入能力信息, 进行与终端 91 相应的数据传输路径的跨网切换控制。
在上述技术方案基石出上, 网络侧设备 92可包括: 目标网络移动性管理
网元 922和网络锚点 923。
目标网络移动性管理网元 922 用于在根据终端 91 的无线接入能力信 息, 向网络锚点 923发送与终端 91相应的数据传输路径的跨网切换的指示 信息。
网络锚点 923用于才艮据来自目标网络移动性管理网元 922的指示信息, 执行与终端 91相应的用户面数据传输路径从源网络到目标网络的切换。
本实施例通过终端向网络侧上报自身的无线接入能力信息, 有利于网 络侧根据终端的接入能力为终端进行用户面数据传输路径的跨网切换控 制, 使得不同接入能力的终端在跨网切换过程中采用与终端接入能力匹配 的控制策略, 保证终端在跨网切换过程中能够正确接收到网络锚点发送的 数据, 从而降低数据丟失的几率和数据传送的抖动。
本领域普通技术人员可以理解: 附图只是一个优选实施例的示意图, 附图中的模块或流程并不一定是实施本发明所必须的。
本领域普通技术人员可以理解: 实施例中的装置中的模块可以按照实 施例描述分布于实施例的装置中, 也可以进行相应变化位于不同于本实施 例的一个或多个装置中。 上述实施例的模块可以合并为一个模块, 也可以 进一步拆分成多个子模块。
上述本发明实施例序号仅仅为了描述, 不代表实施例的优劣。
本领域普通技术人员可以理解: 实现上述方法实施例的全部或部分步 骤可以通过程序指令相关的硬件来完成, 前述的程序可以存储于一计算机 可读取存储介质中, 该程序在执行时, 执行包括上述方法实施例的步骤; 而前述的存储介质包括: R0M、 RAM, 磁碟或者光盘等各种可以存储程序代 码的介质。
最后应说明的是: 以上实施例仅用以说明本发明的技术方案, 而非对 其限制; 尽管参照前述实施例对本发明进行了详细的说明, 本领域的普通 技术人员应当理解: 其依然可以对前述实施例所记载的技术方案进行修改,
或者对其中部分技术特征进行等同替换; 而这些修改或者替换, 并不使相 应技术方案的本质脱离本发明实施例技术方案的精神和范围。
Claims
1、 一种数据传输路径的控制方法, 其特征在于, 包括:
获取终端的无线接入能力信息;
根据所述无线接入能力信息, 进行与所述终端相应的数据传输路径的 跨网切换控制。
2、 根据权利要求 1所述的方法, 其特征在于, 所述获取终端的无线接 入能力信息, 包括:
在所述终端的切换网络附着流程中, 获取所述终端的无线接入能力信 息。
3、 根据权利要求 1或 2所述的方法, 其特征在于, 根据所述无线接入 能力信息, 进行与所述终端相应的数据传输路径的跨网切换控制, 包括: 在所述无线接入能力信息包括单发模式时, 指示网络锚点在目标网络 完成所述终端的承载建立之前, 将与所述终端相应的数据传输路径, 从源 网络切换到目标网络。
4、 根据权利要求 1或 2所述的方法, 其特征在于, 根据所述无线接入 能力信息, 进行与所述终端相应的数据传输路径的跨网切换控制, 包括: 在所述无线接入能力信息包括双发模式时, 指示网络锚点在目标网络 完成所述终端的承载建立之前, 将与所述终端相应的数据传输路径保持在 源网络, 且在目标网络完成所述终端的承载建立之后, 将与所述终端相应 的数据传输路径, 从源网络切换到目标网络。
5、 根据权利要求 1或 2所述的方法, 其特征在于, 根据所述无线接入 能力信息, 进行与所述终端相应的数据传输路径的跨网切换控制, 包括: 在所述无线接入能力信息包括双发模式时, 在目标网络完成所述终端 的承载建立之后, 指示网络锚点将与所述终端相应的数据传输路径, 从源 网络切换到目标网络。
6、 一种移动性管理网元, 其特征在于, 包括:
获取模块, 用于获取终端的无线接入能力信息;
控制模块, 用于根据所述无线接入能力信息, 进行与所述终端相应的 数据传输路径的跨网切换控制。
7、 根据权利要求 6所述的移动性管理网元, 其特征在于, 所述获取模 块包括:
第一获取单元, 用于在所述终端的切换网络附着流程中, 获取所述终 端的无线接入能力信息。
8、 根据权利要求 6或 7所述的移动性管理网元, 其特征在于, 所述控 制模块包括:
第一切换指示单元, 用于在所述无线接入能力信息包括单发模式时, 指示网络锚点在目标网络完成所述终端的承载建立之前, 将与所述终端相 应的数据传输路径, 从源网络切换到目标网络。
9、 根据权利要求 6或 7所述的移动性管理网元, 其特征在于, 所述控 制模块包括:
第二切换指示单元, 用于在所述无线接入能力信息包括双发模式、 且 在目标网络完成所述终端的承载建立之后, 指示网络锚点将与所述终端相 应的数据传输路径, 从源网络切换到目标网络。
1 0、 根据权利要求 8所述的移动性管理网元, 其特征在于, 所述控制 模块还包括:
第二切换指示单元, 用于在所述无线接入能力信息包括双发模式、 且 在目标网络完成所述终端的承载建立之后, 指示网络锚点将与所述终端相 应的数据传输路径, 从源网络切换到目标网络。
1 1、 根据权利要求 9所述的移动性管理网元, 其特征在于, 所述第二 切换指示单元还用于指示网络锚点在目标网络完成所述终端的承载建立之 前, 将与所述终端相应的数据传输路径保持在源网络。
1 2、 根据权利要求 1 0所述的移动性管理网元, 其特征在于, 所述第二 切换指示单元还用于指示网络锚点在目标网络完成所述终端的承载建立之 前, 将与所述终端相应的数据传输路径保持在源网络。
1 3、 一种终端, 其特征在于, 包括:
无线接入能力信息发送模块, 用于向网络侧发送自身的无线接入能力 信息;
接收和反馈模块, 用于通过网络侧根据所述无线接入能力信息确定的 数据传输路径, 接收数据并向网络侧发送反馈信息。
14、 一种数据传输路径的控制系统, 其特征在于, 包括终端和网络侧 设备; 所述网络侧设备用于根据所述无线接入能力信息, 进行与所述终端相 应的数据传输路径的跨网切换控制。
15、 根据权利要求 14所述的数据传输路径的控制系统, 其特征在于所 述网络侧设备包括: 目标网络移动性管理网元和网络锚点;
所述目标网络移动性管理网元用于在根据终端的所述无线接入能力信 息, 向所述网络锚点发送与所述终端相应的数据传输路径的跨网切换的指 示信息;
所述网络锚点用于根据所述指示信息, 执行与终端相应的用户面数据 传输路径从源网络到目标网络的切换。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008102475936A CN101772106B (zh) | 2008-12-30 | 2008-12-30 | 数据传输路径的控制方法和系统、移动性管理网元和终端 |
| CN200810247593.6 | 2008-12-30 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2010075729A1 true WO2010075729A1 (zh) | 2010-07-08 |
Family
ID=42309795
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2009/075439 Ceased WO2010075729A1 (zh) | 2008-12-30 | 2009-12-09 | 数据传输路径的控制方法和系统、移动性管理网元和终端 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN101772106B (zh) |
| WO (1) | WO2010075729A1 (zh) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017166978A1 (zh) * | 2016-03-28 | 2017-10-05 | 电信科学技术研究院 | 一种数据传输方法及装置以及会话管理设备 |
| WO2025054797A1 (zh) * | 2023-09-11 | 2025-03-20 | 北京小米移动软件有限公司 | 通信方法及装置、通信设备、通信系统、存储介质 |
Families Citing this family (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102843665B (zh) * | 2011-06-23 | 2017-12-05 | 中兴通讯股份有限公司 | 一种联合传输的方法和系统 |
| CN103999508B (zh) | 2012-11-30 | 2019-09-03 | 华为技术有限公司 | 迁移方法及装置 |
| CN103906265B (zh) * | 2012-12-28 | 2018-03-20 | 中国电信股份有限公司 | 支持lte与hrpd载波聚合的终端接入方法和基站设备 |
| CN105636087B (zh) * | 2014-10-31 | 2020-09-04 | 中国移动通信集团公司 | 一种网络配置参数的分配方法和装置 |
| CN104796887B (zh) * | 2015-04-14 | 2018-08-21 | 大唐移动通信设备有限公司 | 一种安全信息交互的方法和装置 |
| CN108377459B (zh) | 2016-10-11 | 2020-09-01 | 中国移动通信有限公司研究院 | 一种连接管理方法及装置 |
| CN108282819B (zh) * | 2017-01-06 | 2020-02-21 | 电信科学技术研究院 | 一种减少中断时延的方法、装置及用户设备 |
| CN110637477B (zh) * | 2017-06-13 | 2022-05-13 | 苹果公司 | 用于蜂窝通信系统中的遗留系统回退的系统、方法和设备 |
| US11317447B2 (en) | 2017-10-20 | 2022-04-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Configuration of a packet data network connection |
| CN110839261B (zh) * | 2018-08-15 | 2021-10-26 | 华为技术有限公司 | 数据传输的方法和装置 |
| WO2020191784A1 (zh) * | 2019-03-28 | 2020-10-01 | 华为技术有限公司 | 一种重传信息的传输方法及装置 |
| CN112312489B (zh) | 2019-07-31 | 2021-12-24 | 华为技术有限公司 | 传输数据的方法、通信装置和通信系统 |
| CN115037707B (zh) * | 2021-02-22 | 2025-04-04 | 中国移动通信有限公司研究院 | 一种传输抖动控制方法,用户设备和网络侧设备 |
| US20250193759A1 (en) * | 2022-06-10 | 2025-06-12 | Qualcomm Incorporated | Techniques for backscatter and backscatter-aided advanced communication |
| CN119111105A (zh) * | 2023-04-07 | 2024-12-10 | 北京小米移动软件有限公司 | 定位方法、装置、介质、通信设备及通信系统 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1520203A (zh) * | 2003-01-29 | 2004-08-11 | 埃沃柳姆公司 | 在蜂窝移动无线系统中同时接入电路业务和分组业务的方法 |
| CN1953600A (zh) * | 2005-10-18 | 2007-04-25 | 上海原动力通信科技有限公司 | 移动通信系统中越区切换的控制方法 |
| CN101076192A (zh) * | 2007-03-08 | 2007-11-21 | 中兴通讯股份有限公司 | 双模移动终端与通用地面无线接入网进行信息交互的方法 |
| CN101193440A (zh) * | 2006-12-01 | 2008-06-04 | 华为技术有限公司 | 在切换过程中确定分组数据转发方式的方法、系统及装置 |
-
2008
- 2008-12-30 CN CN2008102475936A patent/CN101772106B/zh not_active Expired - Fee Related
-
2009
- 2009-12-09 WO PCT/CN2009/075439 patent/WO2010075729A1/zh not_active Ceased
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1520203A (zh) * | 2003-01-29 | 2004-08-11 | 埃沃柳姆公司 | 在蜂窝移动无线系统中同时接入电路业务和分组业务的方法 |
| CN1953600A (zh) * | 2005-10-18 | 2007-04-25 | 上海原动力通信科技有限公司 | 移动通信系统中越区切换的控制方法 |
| CN101193440A (zh) * | 2006-12-01 | 2008-06-04 | 华为技术有限公司 | 在切换过程中确定分组数据转发方式的方法、系统及装置 |
| CN101076192A (zh) * | 2007-03-08 | 2007-11-21 | 中兴通讯股份有限公司 | 双模移动终端与通用地面无线接入网进行信息交互的方法 |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017166978A1 (zh) * | 2016-03-28 | 2017-10-05 | 电信科学技术研究院 | 一种数据传输方法及装置以及会话管理设备 |
| US11490443B2 (en) | 2016-03-28 | 2022-11-01 | Datang Mobile Communications Equipment Co., Ltd. | Data transmission method and apparatus, and session management device |
| WO2025054797A1 (zh) * | 2023-09-11 | 2025-03-20 | 北京小米移动软件有限公司 | 通信方法及装置、通信设备、通信系统、存储介质 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101772106B (zh) | 2012-08-08 |
| CN101772106A (zh) | 2010-07-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2010075729A1 (zh) | 数据传输路径的控制方法和系统、移动性管理网元和终端 | |
| CN111165014B (zh) | 用于在无线通信系统中发送和接收与从5gs到eps的切换有关的信号的方法及其装置 | |
| JP7145319B2 (ja) | リリースおよびリダイレクトが続く再開の要求 | |
| US9775075B2 (en) | Providing circuit switched operation in a wireless network | |
| CN102388661B (zh) | 用于在目标无线电接入技术网络中提供非分组交换服务的方法和设备 | |
| EP2981112B1 (en) | Method and apparatus for broadcasting support of selected internet protocol traffic offload | |
| US9848358B2 (en) | Apparatus to enable fallback to circuit switched domain from packet switched domain | |
| US20140051443A1 (en) | Methods and Apparatus for Enhancing Circuit-Switched Call Fallback (CSFB) Service for a Shared Network Node | |
| WO2011006440A1 (zh) | 一种切换方法和装置 | |
| CN102177748B (zh) | 一种网络切换方法、终端、网关和网络系统 | |
| CN105453653A (zh) | 在多无线接入技术环境中应用户设备的请求转变网络节点的状态的方法及其设备 | |
| WO2010012176A1 (zh) | 系统间切换能力信息获取和系统接入的方法、装置及系统 | |
| WO2014108056A1 (zh) | 一种异构网络切换方法、装置及系统 | |
| TWI757714B (zh) | 協作後之特性支援增強技術 | |
| US20220353941A1 (en) | Ma pdu reactivation requested handling | |
| WO2010037313A1 (zh) | 跨网切换方法和系统及接入网设备 | |
| WO2012040918A1 (zh) | 目标无线接入技术选择方法、装置和系统 | |
| WO2024236442A1 (en) | Interworking between congestion information exposure mechanisms for wireless communications | |
| JP2020127212A (ja) | ネットワーク指示の処理装置、方法及び通信システム | |
| HK1230384A1 (zh) | 在增强的通用陆地无线电接入网路中维持电路交换连续性 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 09836016 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: 09836016 Country of ref document: EP Kind code of ref document: A1 |