WO2018058529A1 - 建立承载的方法及装置 - Google Patents

建立承载的方法及装置 Download PDF

Info

Publication number
WO2018058529A1
WO2018058529A1 PCT/CN2016/101085 CN2016101085W WO2018058529A1 WO 2018058529 A1 WO2018058529 A1 WO 2018058529A1 CN 2016101085 W CN2016101085 W CN 2016101085W WO 2018058529 A1 WO2018058529 A1 WO 2018058529A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
terminal
request message
bearer
access network
Prior art date
Application number
PCT/CN2016/101085
Other languages
English (en)
French (fr)
Inventor
邓强
杨艳梅
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP16917279.8A priority Critical patent/EP3506677B1/en
Priority to PCT/CN2016/101085 priority patent/WO2018058529A1/zh
Priority to CN201680084907.8A priority patent/CN109076420B/zh
Publication of WO2018058529A1 publication Critical patent/WO2018058529A1/zh
Priority to US16/359,536 priority patent/US10728805B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0077—Transmission or use of information for re-establishing the radio link of access information of target access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point

Definitions

  • the present application relates to the field of communications, and in particular, to a method and an apparatus for establishing a bearer.
  • V2V Intelligent Transportation System
  • V2I vehicle to Vehicle to Infrastructure
  • V2P vehicle to Pedestrian
  • V2N Vehicle to Network
  • a typical PDN connection includes a radio bearer 11, an S1 bearer 12, and an S5/S8 bearer 13.
  • the radio bearer 11 is a bearer between the UE and the evolved base station (eNode B, eNB)
  • the S1 bearer 12 is a bearer between the eNB and the Serving GateWay (SGW)
  • SGW Serving GateWay
  • the S5/S8 bearer 13 is the SGW and the packet.
  • Bearer between data gateways (PDN GateWay, PGW).
  • the PGW deployment location is high, and the PGW corresponding to the UE remains unchanged during the cell handover process.
  • the PGW is deployed in the vicinity of the eNB in the form of a Local GateWay (LGW), so the UE may also need to switch between different PGWs.
  • the cell handover process 22 and the PGW handover process 24 are separated from each other. Usually, the cell handover process 22 is performed first, and then the PGW handover process 24 is performed. As shown in FIG.
  • the MME in the cell handover process 22 based on the X2 interface, after the target eNB establishes a second radio bearer with the UE, the MME sends a request message to the MME, and after receiving the request message, the MME performs a modification session (Modify Session).
  • the process, the modified session process modifies the first S1 bearer to the second S1 bearer, and keeps the first S5/S8 bearer between the source SGW and the source PGW unchanged.
  • TAU Tracking Area Update
  • the MME also It will be decided whether the UE needs to perform PGW handover.
  • the MME triggers the target eNB to release the second S1 bearer, and the trigger source SGW releases the first S5/S8 bearer.
  • the MME also triggers the target eNB to create a third S1 bearer, and triggers the target SGW to establish the second S1 bearer. /S8 bearer.
  • the UE communicates with the application server in the Internet through the second radio bearer, the third S1 bearer, and the second S5/S8 bearer. Since the second S5/S8 bearer is performed after the cell handover process, the UE needs to take a long switching time from the start of the cell handover to the communication with the application server in the Internet, and cannot meet the transmission delay of the V2X communication. Performance requirements.
  • the present application provides a method and an apparatus for establishing a bearer.
  • the technical solution is as follows:
  • the present application provides a technical solution for establishing a bearer for a terminal in a cell handover process, so that the PGW handover process and the cell handover process are performed simultaneously, thereby reducing the time consuming of the entire handover process.
  • a method for establishing a bearer comprising:
  • the mobility management entity receives the first request message sent by the access network device, where the first request message is sent by the access network device in a cell handover process of the terminal, where the access network device is the terminal a source access network device or a target access network device of the terminal;
  • the mobility management entity sends a second request message to the target serving gateway, where the second request message is used to request the target serving gateway to establish a first bearer for the terminal, where the first bearer is the target a bearer between the serving gateway and the target packet data gateway;
  • the mobility management entity sends the IP address to the terminal.
  • the first request message is a message that is sent by the access network device to the mobility management entity during the cell handover process of the terminal, and after receiving the first request message by the mobility management entity, the mobility management entity is configured by the mobility management entity. Determining the target service gateway and the target packet data gateway, and requesting the target serving gateway to establish a first bearer for the terminal, so that the establishment process of the first bearer is completed in parallel with the cell handover process, and the terminal can use the cell after the cell handover. a bearer for communication, thereby reducing The time required for the entire switching process is reduced, and the requirement of the V2X message in the transmission delay is satisfied.
  • the first request message carries an identifier of a target cell of the terminal, and the mobility management entity determines a target service of the terminal according to the first request message.
  • the gateway and the target packet data gateway of the terminal including:
  • the mobility management entity may select a target serving gateway with the smallest transmission delay between the target cell and the target cell.
  • the target packet data gateway satisfies the requirement of V2X message transmission delay as much as possible.
  • the access network device is a source access network device of the terminal,
  • the first request message is a handover request message; or the access network device is a target access network device of the terminal, and the first request message is a path switch request message.
  • the first request message is a path switch request message; for the S1 interface-based handover process, the first request message is a handover request message, so that the implementation manner can be applied to
  • the switching process of the X2 interface can also be applied to the switching process based on the S1 interface, and the applicable scenario range of the implementation manner is increased.
  • the second request message includes : first indication information
  • the first indication information is used to indicate that the target serving gateway establishes the first bearer for the terminal.
  • the fourth possibility in the first aspect further includes:
  • the mobility management entity sends a third request message to the source service gateway of the terminal, where the third request message is used to request the source service gateway to delete the second bearer corresponding to the terminal, where the second bearer is a bearer between the source serving gateway and a source packet data gateway of the terminal;
  • the mobility management entity receives a third response message sent by the source serving gateway.
  • the first bearer between the target serving gateway and the target packet data gateway is first established for the UE, and the second bearer on the source serving gateway and the source packet data gateway side is released for the UE, which belongs to “soft handover”. Thereby ensuring session continuity of the user equipment without interruption.
  • the third request message includes: second indication information, where the second indication information is used to indicate that the source serving gateway deletes the terminal corresponding to The information of the second bearer.
  • the second aspect provides a device for establishing a bearer, where the device includes at least one unit, and the at least one unit is configured to implement the method for establishing a bearer provided by the foregoing first aspect or any one of the possible implementation manners of the first aspect. .
  • an embodiment of the present invention provides a mobility management entity, where the mobility management entity includes a processor, a memory, and a communication interface.
  • the processor is configured to store one or more instructions, where the instruction is indicated as Executed by the processor, the processor is used to implement the method for establishing a bearer provided by the foregoing first aspect or any one of the possible implementation manners of the first aspect.
  • an embodiment of the present invention provides a computer readable storage medium, where the computer readable storage medium stores a method for establishing a bearer provided by implementing the foregoing first aspect or any possible design of the first aspect. Executable program.
  • 1 is a schematic diagram of three bearers included in a PDN connection
  • FIG. 2 is a schematic diagram of a principle of a cell handover procedure and a PGW handover procedure in the prior art
  • FIG. 3 is a schematic structural diagram of a communication system according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of a method for establishing a bearer according to an embodiment of the present invention
  • FIG. 5A is a flowchart of a first part of a method for establishing a bearer according to an embodiment of the present invention
  • FIG. 5B is a flowchart of a second part of a method for establishing a bearer according to an embodiment of the present invention.
  • 5C is a transmission path diagram of uplink/downlink data of a UE in a PDN connection according to an embodiment of the present invention
  • FIG. 6 is a structural block diagram of an MME according to an embodiment of the present invention.
  • FIG. 7 is a block diagram of an apparatus for establishing a bearer according to an embodiment of the present invention.
  • FIG. 3 shows a schematic structural diagram of a communication system 30 according to an embodiment of the present invention.
  • the communication system 10 can be a vehicle networking system for transmitting V2X messages.
  • the communication system 30 includes a terminal 31, a source access network device 32, a target access network device 33, an MME 34, a source SGW 35, a target SGW 36, a source PGW 37, a target PGW 38, and an application server 39.
  • the terminal 31 is a terminal for transmitting and receiving a V2X message.
  • the terminal 31 is a terminal disposed above a vehicle.
  • a V2X application runs on the terminal 31.
  • the terminal 31 in the embodiment of the present invention may be referred to as a Subscriber Unit, a Subscriber Station, a Mobile Station, a Mobile Station, and a Remote Station (Remote). Station), Access Point, Remote Terminal, Access Terminal, User Terminal, User Agent, User Equipment (UE), etc. This application does not limit this.
  • the terminal 31 communicates with the source access network device 32 over the air interface, or the terminal 31 communicates with the target access network device 33 over the air interface.
  • the source access network device 12 and the target access network device 13 are any two adjacent access network devices in the communication system 10, and the access network devices are also referred to as access network elements. Each access network device is responsible for all wireless related functions in one or more cells.
  • the source access network device 32 and the target access network device 33 may be base stations.
  • the base station may be a Global System for Mobilecommunications (GSM) or a Base Transceiver Station (BTS) in Code-Division Multiple Access (CDMA), or may be a wideband code.
  • GSM Global System for Mobilecommunications
  • BTS Base Transceiver Station
  • CDMA Code-Division Multiple Access
  • a base station (NodeB) in the case of a multiple access (Wideband Code-Division Multiple Access WCDMA) may also be an evolutional Node B (eNB or an e-NodeB) in the LTE, which is not limited in this application.
  • eNB Evolutional Node B
  • e-NodeB evolutional Node B
  • the source access network device 12 and the target access network device 13 are connected through an X2 interface.
  • Each access network device is connected to the core network through an S1 interface.
  • the core network is also known as the Evolved Packet Core (EPC).
  • EPC Evolved Packet Core
  • both the source access network device 32 and the target access network device 33 are connected to the MME 34 through an S1 control plane portion (S1-C interface in the figure), and the source access network device 32 passes through the S1 user plane portion (S1 in the figure)
  • S1-C interface S1 control plane portion
  • S1-U interface is connected to the source SGW 35
  • the target access network device 12 is connected to the target SGW 36 through the S1-U interface.
  • the MME 14 is a control plane node of the EPC.
  • the work of the MME 34 includes: bearer connection/release to the terminal 31.
  • the functional operation between the MME 14 and the terminal 31 may be referred to as a NonAccess Stratum (NAS).
  • NAS NonAccess Stratum
  • AS Access Stratum mainly handles the functional operations between the terminal 31 and the access network device.
  • the source SGW 35 and the target SGW 36 are user plane nodes of the EPC.
  • the SGW is a mobility anchor when the terminal 31 moves between different access network devices.
  • the MME 14 is connected to the source SGW 15 through an S11 interface, and the MME 14 is connected to the target SGW 36 through an S11 interface.
  • the source SGW 35 is also connected to the source PGW 37 via the S5/S8 interface, and the target SGW 16 is also connected to the target PGW 38 via the S5/S8 interface.
  • the source PGW 37 and the target PGW 38 are deployed in the vicinity of the access network device in the form of LGW.
  • the source PGW 37 and the target PGW 38 are used to connect the EPC to the Internet.
  • the source PGW 37 and the target PGW 38 are connected to the V2X application server 39 in the Internet.
  • the V2X application server 39 is used to provide background services for V2X applications in the terminal 31.
  • the communication system 30 also includes other types of nodes, such as a Multimedia Broadcast/Multicast Service (MBMS) or a Home Subscriber Server (HSS). Not all possible nodes are shown in FIG. 3, but do not constitute a limitation to the communication system 30.
  • MBMS Multimedia Broadcast/Multicast Service
  • HSS Home Subscriber Server
  • each of the nodes described above are logical nodes. In actual physical implementations, some of these nodes are likely to be merged together.
  • source SGW 35 and source PGW 37 are typically implemented in the same physical node
  • target SGW 36 and target PGW 38 are typically combined to be implemented in the same physical node.
  • the foregoing network elements may have different names in the 5G system, but have the same or similar functions, which is not limited in this application.
  • FIG. 4 is a flowchart of a method for establishing a bearer according to an embodiment of the present invention. This embodiment is exemplified by the method being applied to the communication system 30 shown in FIG. The method includes:
  • Step 401 The mobility management entity receives the first request message sent by the access network device.
  • the first request message is sent by the access network device to the mobility management entity during the cell handover process of the terminal.
  • the access network device is a source access network device or a target access network device of the terminal.
  • the cell handover process is a cell handover in the access network device
  • the source cell and the target cell belong to the same access network device, that is, the source access network device and the target access network device may be the same access network device.
  • the terminal set on the vehicle moves at a high speed
  • cell switching is performed. Moving from the source cell of the source access network device to the target cell of the target access network device.
  • the cell handover is initiated by the source access network device on the network side.
  • the terminal measures the signal quality of the current cell (source cell) and the neighboring cell, and reports the signal quality to the source access network device.
  • the source access network device determines whether to initiate cell handover and which cell to switch according to the signal quality of the current cell and the neighboring cell reported by the terminal.
  • the cell handover process may include: a first process for determining whether the terminal performs cell handover, a second process of establishing a radio bearer between the terminal and the target access network device, and releasing a radio bearer between the terminal and the source access network device.
  • the third process may include: a first process for determining whether the terminal performs cell handover, a second process of establishing a radio bearer between the terminal and the target access network device, and releasing a radio bearer between the terminal and the source access network device.
  • the first request message is a message that the source access network device sends to the mobility management entity after the first process, or the first request message is that the target access network device sends the mobility management entity to the mobility management entity after the second process.
  • the message sent is a message that the source access network device sends to the mobility management entity after the first process, or the first request message is that the target access network device sends the mobility management entity to the mobility management entity after the second process.
  • the cell handover procedure includes: a cell handover procedure based on an S1 interface and a cell handover procedure based on an X2 interface.
  • the access network device is a source access network device
  • the first request message is a HO Required message, which is sent by the source access network device after the first process.
  • the first request message is sent by the source access network device after receiving the measurement report reported by the terminal and determining that the terminal needs to perform cell handover according to the measurement report.
  • the access network device is the target access network device
  • the first request message is a Path Switch Request message, which is sent by the target access network device after the second process.
  • the target access network device sends a first request message after receiving the RRC Connection Reconfigration Complete message sent by the terminal.
  • the RRC Connection Reconfigration Complete message is used to indicate that the terminal and the target access network device have established a radio bearer.
  • the mobility management entity receives the first request message sent by the access network device.
  • Step 402 The mobility management entity determines the target serving gateway and the target packet data gateway according to the first request message.
  • the mobility management entity obtains the identifier of the target cell from the first request message, and determines the target serving gateway and the target packet data gateway for the terminal according to the identifier of the target cell.
  • the identity of the target cell may be represented using a Local Network ID or a cell identity.
  • each target cell corresponds to a respective serving gateway and packet data gateway.
  • the cell 1 corresponds to the serving gateway 1 and the packet data gateway 1
  • the cell 2 corresponds to the serving gateway 2 and the packet data gateway 2.
  • Step 403 The mobility management entity sends a second request message to the target service gateway.
  • the second request message is a Create Session Request message.
  • the second request message is used to request the target serving gateway to establish a first bearer for the terminal, where the first bearer is a bearer between the target serving gateway and the target packet data gateway.
  • the target serving gateway receives the second request message sent by the mobility management entity.
  • Step 404 The target serving gateway establishes a first bearer according to the second request message.
  • the target serving gateway acquires address information of the target packet data gateway from the second request message, and establishes a first bearer according to the address information of the target packet data gateway and the target packet data gateway.
  • the target packet data gateway allocates an IP address to the terminal.
  • Step 405 The target service gateway acquires an IP address assigned by the target packet data gateway to the terminal.
  • Step 406 The target service gateway sends a second response message to the mobility management entity.
  • the second response message is a Create Session Response message.
  • the second response message carries an IP address assigned to the terminal.
  • the mobility management entity receives the second response message sent by the target service gateway.
  • step 407 the mobility management entity sends an IP address to the terminal.
  • the first request message is a message that the access network device sends to the mobility management entity during the cell handover process of the terminal, and after receiving the first request message by the mobility management entity, the mobility management entity is configured by the mobility management entity. Determining the target service gateway and the target packet data gateway, and requesting the target serving gateway to establish a first bearer for the terminal, so that the establishment process of the first bearer is completed in parallel with the cell handover process, and the terminal can use the cell after the cell handover. A bearer communicates, thereby reducing the time consuming of the entire handover process and meeting the transmission delay requirement of the V2X message.
  • the cell handover procedure includes two forms: a cell handover procedure based on the X2 interface and a cell handover procedure based on S1.
  • the cell switching process based on the X2 interface is more common.
  • the next embodiment combines the cell switching process based on the X2 interface to describe the embodiment of the present invention in detail.
  • the terminal is a UE
  • the access network device is an eNB
  • FIG. 5A and FIG. 5B a flowchart of a method for establishing a bearer according to an embodiment of the present invention is shown. This embodiment is exemplified by the method of establishing a bearer applied to the communication system shown in FIG. 3.
  • the method includes:
  • Step 501 The source eNB sends a radio resource control (RRC) connection configuration message to the UE, where the RRC connection configuration message carries measurement configuration information.
  • RRC radio resource control
  • the measurement configuration information is used to configure a measurement strategy when the UE performs cell measurement.
  • the UE receives the RRC connection configuration message sent by the source eNB, and acquires measurement configuration information from the RRC connection configuration message.
  • Step 502 The UE performs measurement according to the measurement configuration information, and generates a measurement report.
  • the Measurement Report includes: the signal quality of each cell that can be measured at the location of the UE.
  • step 503 the UE sends a measurement report to the source eNB.
  • the source eNB receives the measurement report sent by the UE.
  • Step 504 The source eNB determines, according to the measurement report, that the UE switches to the target cell of the target eNB.
  • the source eNB determines, according to the measurement report of the UE, that the UE switches from the currently camped source cell to the target cell of the target eNB.
  • the UE is determined to need to switch from the source cell to the target cell.
  • This embodiment is exemplified by a UE that needs to switch from a source cell to a target cell.
  • Step 505 The source eNB sends a handover request message to the target eNB.
  • a Handover Request message is used to query whether the target eNB allows the current handover.
  • the target eNB receives the handover request message sent by the source eNB.
  • the target eNB reserves corresponding resources for the UE according to the handover request message. For example, a resource for establishing a radio bearer between a terminal and a target eNB, a Cell Radio-Network Temporaty Identifier (C-RNTI), a dedicated random access pilot, and the like.
  • C-RNTI Cell Radio-Network Temporaty Identifier
  • Step 506 The target eNB sends a handover request acknowledgement message to the source eNB.
  • the target eNB After the target eNB reserves the resource, it sends a Handover Request Acknowledge message to the source eNB.
  • the handover request acknowledgement message is used to indicate that the target eNB allows the current handover, and the corresponding resources are reserved.
  • the handover request acknowledgement message carries: a dedicated access pilot allocated by the target eNB to the UE.
  • the source eNB receives the handover request acknowledgement message sent by the target eNB.
  • step 507 the source eNB sends an RRC connection configuration message to the UE.
  • the RRC connection configuration message is used to instruct the UE to perform cell handover.
  • the RRC connection configuration message carries: a dedicated access pilot allocated by the target eNB to the UE.
  • the UE receives an RRC Connection Configuration message.
  • Step 508 The UE establishes a radio bearer according to the RRC connection configuration message.
  • the radio bearer is a bearer between the UE and the target eNB.
  • the UE obtains the dedicated access pilot from the RRC connection configuration message, and establishes the radio bearer of the target side with the target eNB through the dedicated access pilot.
  • step 509 the UE sends an RRC connection configuration confirmation message to the target eNB.
  • the RRC connection configuration acknowledgement message is used to indicate that the UE has accessed the target cell, and establishes a radio bearer on the target side with the target eNB.
  • Step 510 The target eNB sends a first request message to the MME.
  • the first request message is a path switch request message.
  • the first request message is sent by the target eNB during the cell handover process of the UE.
  • the first request message is used to request the MME to determine the target SGW of the UE and the target PGW of the UE.
  • the first request message carries: a local network identifier or a cell identifier corresponding to the target cell, an identifier of the UE, a bearer information that needs to be established for the UE, and a GPRS tunnel protocol (GPRS) of the target eNB on the S1-U interface.
  • GPRS GPRS tunnel protocol
  • GTP Tunneling Protocol
  • TEID Tunnel Endpoint ID
  • the GTP "address + TEID" of the target eNB on the S1-U interface is address information for receiving downlink data in the S1 bearer of the target side.
  • the S1 bearer on the target side is a bearer between the target eNB and the target SGW.
  • the GTP "address + TEID” refers to the IP address and TEID in the GTP.
  • the MME receives the path switch request message sent by the target eNB.
  • Step 511 The MME determines the target SGW and the target PGW according to the first request message.
  • the MME acquires an identifier of the target cell according to the first request message; and the MME determines the target SGW and the target PGW for the UE according to the identifier of the target cell.
  • the identifier of the target cell may be: a local network identifier corresponding to the target cell, or a cell identifier corresponding to the target cell.
  • the MME stores a correspondence between a “local network identifier and/or a cell identifier” of the target cell and “SGW+PGW”.
  • the corresponding relationship includes “local network identifier 1, SGW1, PGW1”, “cell identity 2, SGW2, PGW2”, “cell identity 3, SGW3, PGW3” and the like.
  • the MME queries the target SGW and the target PGW in the corresponding relationship according to the local network identifier and/or the cell identifier of the target cell.
  • the cell identity 2 is the target cell
  • the PGW2 is the local gateway disposed near the target eNB. Since the distance between the PGW2 and the target eNB is relatively close, the PGW2 can be The target cell provides a PDN service capability with a small delay; and for the corresponding relationship "Cell ID 3, SGW3, PGW3", the cell identity 3 is the target cell, and the PGW3 is the local gateway set near the target eNB, due to the PGW3 and the target. The distance of the eNB is relatively close, and the PGW3 can provide the target cell with a PDN service capability with a small delay.
  • the MME sends the identifier of the target cell to other network elements, such as a Domain Name System (DNS), and the DNS determines the target SGW of the UE and the UE according to the identifier of the target cell.
  • DNS Domain Name System
  • the target PGW is then fed back to the target SGW and the target PGW by the DNS.
  • the correspondence between the “local network identifier and/or the cell identifier” and the “SGW+PGW” of the target cell is stored in the DNS.
  • the corresponding relationship includes “local network identifier 2, SGW4, PGW4”, “cell identity 4, SGW5, PGW5”, “cell identity 5, SGW6, PGW6” and the like.
  • Step 512 The MME sends a second request message to the target SGW.
  • the second request message is used to request the target SGW to establish a first bearer for the UE, where the first bearer is a bearer between the target SGW and the target PGW.
  • the bearer is an S5/S8 bearer.
  • the second request message is a Create Session Request message.
  • the create session request message carries: address information of the target PGW and first indication information.
  • the first indication information is information used to indicate that the target SGW establishes a first bearer for the UE.
  • the first indication information may also be referred to as new PDN connection indication information.
  • the second request message further carries: the GTP of the target eNB on the S1-U interface.
  • Address + TEID the identity of the UE, the quality of service (QoS) information of the first bearer, the GTP "address + TEID” of the MME on the S11 interface, and the like.
  • the MME sends a second request message to the target SGW on the S11 interface.
  • the target SGW receives the second request message sent by the MME.
  • Step 513 The target SGW sends a fourth request message to the target PGW according to the second request message.
  • the target SGW obtains, from the second request message, the address information of the target PGW, the first indication information, the GTP "address + TEID" of the target eNB on the S1-U interface, the identifier of the UE, and the quality of service of the first bearer (Quality of Service) , QoS) information, GTP "address + TEID" of the MME on the S11 interface.
  • the target SGW After obtaining the GTP "address + TEID" of the target eNB on the S1-U interface, the target SGW has the capability of transmitting downlink data to the target eNB, that is, constructing the downlink GTP tunnel in the S1 bearer of the target side.
  • the target SGW transmits a fourth request message to the target PGW on the S5/S8 interface according to the information of the target PGW.
  • the fourth request message is used to request the target PGW to establish the first bearer.
  • the fourth request message is a create session request message.
  • the fourth request message carries: an identifier of the UE, a GTP “address+TEID” and QOS information of the target SGW on the S5/S8 interface.
  • the GTP "address + TEID" of the target SGW on the S5/S8 interface is address information for receiving downlink data in the first bearer (S5/S8 bearer on the target side).
  • the target SGW sends a fourth request message to the target PGW on the S5/S8 interface.
  • the target PGW receives the fourth request message sent by the target SGW.
  • the target PGW acquires the identifier of the UE, the GTP "address + TEID" and the QOS information of the target SGW on the S5/S8 interface from the fourth request message.
  • Step 514 the target PGW returns a fourth response message to the target SGW.
  • the target PGW obtains the identifier of the UE from the fourth request message, and the GTP "address + TEID" of the target SGW on the S5/S8 interface.
  • the target PGW After obtaining the GTP "address + TEID" of the target SGW on the S5/S8 interface, the target PGW has the capability of transmitting downlink data to the target SGW, that is, constructing the downlink GTP in the first bearer (the S5/S8 bearer on the target side). tunnel.
  • the target PGW also assigns an IP address to the UE according to the identity of the UE, and establishes a UE context.
  • the target PGW generates a fourth response message.
  • the fourth response message is a Create Session Response message.
  • the fourth response message carries: the identifier of the UE, and is the UE.
  • the GTP "address + TEID" of the target PGW on the S5/S8 interface is address information for receiving uplink data in the first bearer (S5/S8 bearer on the target side).
  • the target PGW sends a fourth response message to the target SGW on the S5/S8 interface.
  • the target SGW receives the fourth response message sent by the target PGW.
  • the target SGW After obtaining the GTP "address + TEID" of the target PGW on the S5/S8 interface, the target SGW has the capability of transmitting uplink data to the target PGW, that is, constructing the uplink GTP in the first bearer (the S5/S8 bearer on the target side). tunnel.
  • step 515 the target SGW returns a second response message to the MME.
  • the second response message carries: an identifier of the UE, an IP address allocated for the UE, and a GTP “address+TEID” of the target SGW on the S1-U interface.
  • the GTP "address + TEID" of the target SGW on the S1-U interface is address information for receiving uplink data in the S1 bearer on the target side.
  • the target SGW sends a second response message to the MME through the S11 interface.
  • the destination address of the second response message is the GTP "address + TEID" of the MME.
  • the MME receives the second response message sent by the target SGW.
  • step 516 the MME sends a first acknowledgement message to the target eNB.
  • the first acknowledgement message is a Path Switch Acknowledge message.
  • the first acknowledgment message carries: third indication information, where the third indication information is used to request the target eNB to establish an S1 bearer for the UE, where the S1 bearer is a bearer between the target eNB and the target SGW.
  • the foregoing first indication information and third indication information may also be referred to as: newly created PDN connection indication information.
  • the first acknowledgement message further carries: a GTP "address + TEID" of the target SGW on the S1-U interface.
  • the MME sends a first acknowledgement message to the target eNB through the S1-C interface.
  • the target eNB receives the first acknowledgement message sent by the MME.
  • the target eNB establishes an S1 bearer of the target side for the UE according to the first acknowledgement message, where the S1 bearer is a bearer between the target eNB and the target SGW. That is, after obtaining the GTP "address + TEID" of the target SGW on the S1-U interface, the target eNB has the capability of transmitting uplink data to the target SGW, that is, the uplink GTP tunnel in the S1 bearer of the target side is constructed.
  • Step 517 the MME sends an IP address to the UE.
  • the MME sends an IP address to the UE through the NAS message, the IP address being an IP address used in the target side PDN connection.
  • the PDN connection on the target side includes three target side bearers: a radio bearer 51, an S1 bearer 52, and an S5/S8 bearer 53.
  • the application server When transmitting the downlink data, the application server sends the downlink data to the target PGW by using the IP address "UE IP" of the UE as the target address; the target PGW uses the GTP "address + TEID" of the target SGW on the S5/S8 port as the destination address, The target PGW sends the downlink data to the target eNB by using the GTP "address + TEID" of the target eNB on the S1-U interface as the destination address; and the target eNB uses the radio bearer ID (Radio Bearer ID, RB ID) of the UE.
  • the downlink data is transmitted to the UE as a target address.
  • the RB ID is assigned by the target eNB.
  • the UE When transmitting the uplink data, the UE sends the uplink data to the target eNB by using the RB ID of the target eNB as the target address; the target eNB sends the uplink to the target SGW by using the GTP "address + TEID" of the target SGW on the S1-U interface as the destination address. Data; the target SGW sends the uplink data to the target PGW with the GTP "address + TEID" of the target PGW on the S5/S8 interface as the destination address; the target PGW uses the IP address "Svr IP" of the application server as the destination address to the application server. Send upstream data.
  • Step 518 The target eNB sends a release resource message to the source eNB.
  • the Release Resource message is used to release the radio bearer between the source eNB and the UE.
  • the release resource message carries a fourth indication information, where the fourth indication information is used to indicate that the source eNB releases the radio bearer and the S1 bearer, where the radio bearer is a bearer between the source eNB and the UE, and the S1 bearer is a source. Bearer between the eNB and the source SGW.
  • the fourth indication information may also be referred to as a release source side PDN connection indication.
  • the target eNB sends a release resource message to the source eNB through the X2 interface.
  • the source eNB receives the release resource message.
  • the source eNB releases the radio bearer and the S1 bearer corresponding to the UE.
  • Step 519 The MME sends a third request message to the source SGW.
  • the third request message is a Delete Session Request message.
  • the third request message is used to request the source SGW to delete the second bearer corresponding to the UE, where the second bearer is an S5/S8 bearer between the source SGW and the source PGW.
  • the third request message carries the second indication information, where the second indication information is used to indicate that the source SGW deletes the second bearer corresponding to the UE.
  • the second indication information is also used to Instructing the source SGW to delete the third bearer corresponding to the UE, where the third bearer is an S1 bearer between the source SGW and the source eNB.
  • the MME sends a third request message to the source SGW through the S11 interface.
  • the source SGW receives the third request message sent by the MME.
  • the source SGW deletes the second bearer and the third bearer corresponding to the UE according to the third request message, that is, deletes the S5/S8 bearer and the S1 bearer corresponding to the UE located on the source SGW.
  • Step 520 The source SGW sends a fifth request message to the source PGW.
  • the fifth request message is a Delete Session Request message.
  • the fifth request message is used to request the source PGW to delete the second bearer corresponding to the UE.
  • the source SGW sends a fifth request message to the source PGW through the S5/S8 interface.
  • the source PGW receives the fifth request message, and the source PGW deletes the second bearer corresponding to the UE, that is, deletes the S5/S8 bearer corresponding to the UE located on the source PGW.
  • Step 521 The source PGW sends a fifth response message to the source SGW.
  • the fifth response message is a Delete Session Response message.
  • the fifth response message is used to indicate that the source SGW has deleted the second bearer.
  • Step 522 The source SGW sends a third response message to the MME.
  • the third response message is a delete session response message.
  • the third response message is used to indicate that the source SGW has deleted the second bearer corresponding to the UE, that is, the S5/S8 bearer between the source SGW and the source PGW.
  • the third response message is further used to indicate that the source SGW has deleted the third bearer corresponding to the UE, and the third bearer is an S1 bearer between the source eNB and the source SGW.
  • step 523 the UE and the MME perform a tracking area update process.
  • the UE After entering the new target cell (tracking area), the UE performs a Tracking Area Update (TAU) process with the MME.
  • TAU Tracking Area Update
  • the first request message is a message that the access network device sends to the mobility management entity during the cell handover process of the terminal, and after receiving the first request message by the mobility management entity, The mobility management entity determines the target service gateway and the target packet data gateway according to the first request message, and requests the target service gateway to establish a first bearer for the terminal, so that the establishment process of the first bearer is completed in parallel with the cell handover process, and the terminal can
  • the first bearer is used for communication after the cell handover, thereby reducing the time consuming of the entire handover process and satisfying the requirement of the V2X message in the transmission delay.
  • the first between the target SGW and the target PGW is established for the UE.
  • the bearer and the second bearer between the source SGW and the source PGW are deleted for the UE, and belong to the “soft handover”, thereby ensuring the continuity of the session of the UE without interruption.
  • the handover procedure based on the S1 interface is similar to the embodiment shown in FIG. 5A and FIG. 5B, but since the source eNB and the target eNB no longer exchange information through the X2 interface, the path switch request sent by the target eNB in step 510 is performed. The message is changed to the handover request message sent by the source eNB.
  • FIG. 6 is a structural block diagram of an MME according to an embodiment of the present invention.
  • the MME includes a processor 610, a memory 620, and a communication interface 630.
  • the processor 610 is coupled to the memory 620 and the communication interface 630 via a bus, respectively.
  • Communication interface 630 is used to communicate with other network elements, such as communication with an eNB, or with an SGW.
  • Processor 610 includes one or more processing cores.
  • the processor 610 implements the functions of the MME in FIG. 4, FIG. 5A or FIG. 5B by running an operating system or an application module.
  • the memory 620 can store an operating system 622, an application module 624 required for at least one function.
  • the application module 624 includes: a receiving module 624a, a processing module 624b, and a sending module 624c.
  • the receiving module 624a is configured to implement steps related to receiving;
  • the processing module 624b is configured to implement steps related to computing or processing;
  • the transmitting module 624c is configured to implement steps related to transmitting.
  • memory 620 can be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable In addition to Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Disk or Optical Disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Disk Disk
  • Disk Disk or Optical Disk
  • FIG. 6 does not constitute a limitation of the above-described MME, and may include more or less components or combinations of certain components, or different component arrangements.
  • FIG. 7 is a block diagram of an apparatus for establishing a bearer according to an embodiment of the present invention.
  • the device can be implemented as all or part of the MME by software or hardware.
  • the apparatus includes a receiving unit 710, a processing unit 720, and a transmitting unit 730.
  • the receiving unit 710 is configured to implement the foregoing embodiment of FIG. 4 or the embodiment of FIG. 5A or the embodiment of FIG. 5B. Steps of step 401, step 406, step 510, step 515, step 522, etc., and other implicit receiving steps performed by the MME;
  • the processing unit 720 is configured to implement the processing steps of step 402, step 511, and the like in the foregoing embodiment of FIG. 4 or the embodiment of FIG. 5A or the embodiment of FIG. 5B, and other implicit processing steps performed by the MME;
  • the sending unit 730 is configured to implement the sending steps of step 403, step 507, step 509, step 512, step 516, step 517, step 519, etc. in the foregoing embodiment of FIG. 4 or the embodiment of FIG. 5A or the embodiment of FIG. 5B, and other hidden steps.
  • the receiving unit 710 can be implemented by the processor 610 in FIG. 6 executing the receiving module 624a in the memory 620; the processing unit 720 can be implemented by the processor 610 in FIG. 6 executing the processing module 624b in the memory 620; the sending unit 730 can The implementation of the transmitting module 624c in the memory 620 is performed by the processor 610 in FIG.
  • a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
  • the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

Landscapes

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

Abstract

本发明实施例提供了一种建立承载的方法、装置及系统，涉及通信领域，所述方法包括：在UE的切换过程中，eNB向MME发送第一请求消息，MME根据第一请求消息确定UE的目标SGW和目标PGW，MME还请求目标SGW为UE建立第一承载，该第一承载是目标SGW和目标PGW之间的承载；在建立第一承载之后，MME还请求源eNB释放源侧的无线承载，以及请求源SGW删除源侧的第二承载。本发明使得第一承载的建立过程与小区切换过程并行完成，终端能够在小区切换之后使用第一承载进行通信，从而减少了整个切换过程的耗时，满足V2X消息在传输时延上的需求。

Description

建立承载的方法及装置 技术领域
本申请涉及通信领域，特别涉及一种建立承载的方法及装置。
背景技术
在智能交通系统(Intelligent Transportation System,ITS)中，通过车辆与车辆之间(Vehicle to Vehicle，V2V)通信，或者车辆与路边基础设施(Vehicle to Infrastructure，V2I)通信，或者车辆与行人之间的(Vehicle to Pedestrian，V2P)通信，或者车辆与网络(Vehicle to Network，V2N)通信来及时获取有关交通的各种信息，这些通信方式可以统称为车辆与外界(Vehicle to X，V2X)通信。X是车辆、路边基础设施、行人和网络的统称。
在通过长期演进(Long Term Evolution，LTE)技术将V2X消息从一个用户设备(User Equipment，UE)传输至另一个UE时，需要通过分组数据网(Packet Data Network，PDN)连接进行传输。如图1所示，一个典型的PDN连接包括：无线承载11、S1承载12和S5/S8承载13。其中，无线承载11是UE与演进型基站(eNode B，eNB)之间的承载、S1承载12是eNB与服务网关(Serving GateWay，SGW)之间的承载、S5/S8承载13是SGW与分组数据网关(PDN GateWay，PGW)之间的承载。
在传统的小区切换(Handover)过程中，PGW的部署位置较高，UE对应的PGW在小区切换过程中保持不变。但在V2X通信中，PGW以本地网关(Local GateWay，LGW)的形式部署在eNB的附近，因此UE还可能需要在不同的PGW之间切换。具体地，小区切换过程22和PGW切换过程24是互相分离的，通常先执行小区切换过程22，再执行PGW切换过程24。如图2所示，在基于X2接口的小区切换过程22中，目标eNB与UE建立第二无线承载之后，会向MME发送请求消息，MME在接收到该请求消息后，执行修改会话(Modify Session)流程，该修改会话流程会将第一S1承载修改为第二S1承载，保持源SGW和源PGW之间的第一S5/S8承载不变。在小区切换过程结束22后，由于跟踪区更新流程(Tracking Area Update，TAU)之类的因素触发，MME还 会判决该UE是否需要进行PGW切换。若需要切换，则MME触发目标eNB释放掉第二S1承载，触发源SGW释放掉第一S5/S8承载，另外，MME还会触发目标eNB新建第三S1承载，并触发目标SGW建立第二S5/S8承载。之后，UE通过第二无线承载、第三S1承载和第二S5/S8承载与互联网中的应用服务器进行通信。由于第二S5/S8承载是在小区切换过程之后进行的，导致UE从小区切换开始到能够与互联网中的应用服务器进行通信，需要耗费较长的切换时间，无法满足V2X通信在传输时延上的性能要求。
发明内容
为了解决整个切换过程的耗时较长，无法满足V2X通信在传输时延上的性能要求的问题，本申请提供了一种建立承载的方法及装置。所述技术方案如下：
本申请提供一种在小区切换过程中为终端建立承载的技术方案，使得PGW切换过程与小区切换过程同时执行，从而减少整个切换过程的耗时。
第一方面，提供了一种建立承载的方法，所述方法包括：
移动性管理实体接收接入网设备发送的第一请求消息，所述第一请求消息是所述接入网设备在终端的小区切换过程中发送的，所述接入网设备是所述终端的源接入网设备或所述终端的目标接入网设备；
所述移动性管理实体根据所述第一请求消息，确定所述终端的目标服务网关和所述终端的目标分组数据网关；
所述移动性管理实体向所述目标服务网关发送第二请求消息，所述第二请求消息用于请求所述目标服务网关为所述终端建立第一承载，所述第一承载是所述目标服务网关和所述目标分组数据网关之间的承载；
所述移动性管理实体接收所述目标服务网关发送的第二响应消息，所述第二响应消息携带有所述目标分组数据网关为所述终端分配的IP地址；
所述移动性管理实体向所述终端发送所述IP地址。
在该实现方式中，第一请求消息是接入网设备在终端的小区切换过程中向移动性管理实体发送的消息，通过移动性管理实体接收到第一请求消息后，由移动性管理实体根据第一请求消息来确定目标服务网关和目标分组数据网关，并请求目标服务网关为终端建立第一承载，使得将第一承载的建立过程与小区切换过程并行完成，终端能够在小区切换之后使用第一承载进行通信，从而减 少了整个切换过程的耗时，满足V2X消息在传输时延上的需求。
在第一方面的第一种可能的实现方式中，所述第一请求消息携带所述终端的目标小区的标识；所述移动性管理实体根据所述第一请求消息确定所述终端的目标服务网关和所述终端的目标分组数据网关，包括：
所述移动性管理实体从所述第一请求消息中获取所述目标小区的标识；
所述移动性管理实体根据所述目标小区的标识，确定所述终端的所述目标服务网关和所述终端的所述目标分组数据网关。
在该实现方式中，由于移动性管理实体是根据目标小区的标识来确定目标服务网关和目标分组数据网关，移动性管理实体可以选择出与目标小区之间的传输时延最小的目标服务网关和目标分组数据网关，尽可能满足V2X消息在传输时延上的需求。
结合第一方面或第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，所述接入网设备是所述终端的源接入网设备，所述第一请求消息是切换请求消息；或，所述接入网设备是所述终端的目标接入网设备，所述第一请求消息是路径切换请求消息。
在该实现方式中，对于基于X2接口的切换过程，第一请求消息为路径切换请求消息；对于基于S1接口的切换过程，第一请求消息为切换请求消息，使得该实现方式既能应用于基于X2接口的切换过程，也能应用于基于S1接口的切换过程，增加了该实现方式的适用场景范围。
结合第一方面或第一方面的第一种可能的实现方式或第一方面的第二种可能的实现方式，在第一方面的第三种可能的实现方式中，所述第二请求消息包括：第一指示信息；
所述第一指示信息是用于指示所述目标服务网关为所述终端建立所述第一承载。
结合第一方面或第一方面的第一种可能的实现方式或第一方面的第二种可能的实现方式或第一方面的第三种可能的实现方式，在第一方面的第四种可能的实现方式中，所述移动性管理实体接收所述目标服务网关发送的第二响应消息之后，还包括：
所述移动性管理实体向所述终端的源服务网关发送第三请求消息，所述第三请求消息用于请求所述源服务网关删除所述终端对应的第二承载，所述第二承载是所述源服务网关与所述终端的源分组数据网关之间的承载；
所述移动性管理实体接收所述源服务网关发送的第三响应消息。
在该实现方式中，由于先为UE建立目标服务网关和目标分组数据网关之间的第一承载，再为UE释放源服务网关和源分组数据网关侧的第二承载，属于“软切换”，从而保证用户设备的会话连续性，不会产生中断。
结合第一方面或第一方面的第一种可能的实现方式或第一方面的第二种可能的实现方式或第一方面的第三种可能的实现方式或第一方面的第四种可能的实现方式，在第一方面的第五种可能的实现方式中，所述第三请求消息包括：第二指示信息，所述第二指示信息是用于指示所述源服务网关删除所述终端对应的所述第二承载的信息。
第二方面，提供了一种建立承载的装置，该装置包括至少一个单元，该至少一个单元用于实现上述第一方面或第一方面中任意一种可能的实现方式所提供的建立承载的方法。
第三方面，本发明实施例提供了一种移动性管理实体，该移动性管理实体包括处理器、存储器和通信接口；所述处理器用于存储一个或一个以上的指令，所述指令被指示为由所述处理器执行，所述处理器用于实现上述第一方面或第一方面中任意一种可能的实现方式所提供的建立承载的方法。
第四方面，本发明实施例提供一种计算机可读存储介质，该计算机可读存储介质中存储有用于实现上述第一方面或第一方面中任意一种可能的设计所提供的建立承载的方法的可执行程序。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是一个PDN连接所包括的三个承载的示意图；
图2是现有技术中的小区切换过程和PGW切换过程的原理示意图；
图3是本发明一个实施例提供的通信系统的结构示意图；
图4是本发明一个实施例提供的建立承载的方法的流程图；
图5A是本发明一个实施例提供的建立承载的方法的第一部分流程图；
图5B是本发明一个实施例提供的建立承载的方法的第二部分流程图
图5C是本发明一个实施例提供的UE在一个PDN连接中的上/下行数据的传输路径图；
图6是本发明一个实施例提供的MME的结构框图；
图7是本发明一个实施例提供的建立承载的装置的框图。
具体实施方式
为使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明实施方式作进一步地详细描述。
请参考图3，其示出了本发明一个实施例提供的通信系统30的结构示意图。该通信系统10可以是用于传输V2X消息的车联网系统。该通信系统30包括：终端31、源接入网设备32、目标接入网设备33、MME34、源SGW35、目标SGW36、源PGW37、目标PGW38和应用服务器39。
终端31是用于收发V2X消息的终端。可选地，终端31是设置在车辆(Vehicle)上面的终端。终端31上运行有V2X应用程序。在采用不同的通信协议时，本发明实施例中的终端31可以称为订户单元(Subscriber Unit)、订户站(Subscriber Station)，移动站(Mobile Station)、移动台(Mobile)、远程站(Remote Station)、接入点(Access Point)、远程终端(Remote Terminal)、接入终端(Access Terminal)、用户终端(User Terminal)、用户代理(User Agent)、用户设备(User Equipment，UE)等，本申请对此不作限定。
终端31通过空中接口与源接入网设备32通信，或者，终端31通过空中接口与目标接入网设备33通信。
源接入网设备12和目标接入网设备13是通信系统10中任意两个相邻的接入网设备，接入网设备也称接入网网元。每个接入网设备负责一个或多个小区中所有无线相关的功能。源接入网设备32和目标接入网设备33可以是基站。例如，基站可以是全球移动通信系统(Global System forMobilecommunications，GSM)或码分多址(英文：Code-Division Multiple Access,简称：CDMA)中的基站(Base Transceiver Station，BTS)，也可以是宽带码分多址(Wideband Code-Division Multiple Access WCDMA)中的基站(NodeB)，还可以是LTE中的演进型基站(evolutional Node B，eNB或e-NodeB)，本申请对此不作限定。
源接入网设备12和目标接入网设备13通过X2接口相连。
每个接入网设备均通过S1接口与核心网相连。核心网又称演进的分组核心网(Evolved Packet Core,EPC)。具体来讲，源接入网设备32和目标接入网设备33均通过S1控制平面部分(图中S1-C接口)连接到MME34，源接入网设备32通过S1用户平面部分(图中S1-U接口)连接到源SGW35，目标接入网设备12通过S1-U接口连接到目标SGW36。
MME14是EPC的控制平面节点。MME34的工作包括：对终端31的承载连接/释放。可选地，MME14与终端31之间的功能操作可称为非接入层(NonAccess Stratum，NAS)。与其不同的是，接入层(Access Stratum，AS)主要处理终端31与接入网设备之间的功能操作。
源SGW35和目标SGW36是EPC的用户平面节点。SGW是终端31在不同接入网设备之间移动时的移动性锚点。
MME14通过S11接口与源SGW15相连，MME14通过S11接口与目标SGW36相连。源SGW35还通过S5/S8接口与源PGW37相连，目标SGW16还通过S5/S8接口与目标PGW38相连。
可选地，源PGW37和目标PGW38以LGW的形式部署在接入网设备的附近。源PGW37和目标PGW38用于将EPC连接到互联网。在本实施例中，源PGW37和目标PGW38与互联网中的V2X应用服务器39相连。
V2X应用服务器39用于为终端31中的V2X应用提供后台服务。
另外，通信系统30中还包含其它类型的节点，比如，多媒体广播多播业务(Multimedia Broadcast/Multicast Service，MBMS)或者归属用户服务器(Home Subscriber Server，HSS)。图3中未示出全部可能的节点，但不构成对该通信系统30的限定。
应当注意的是，以上描述的各个节点均为逻辑节点。在实际的物理实现中，其中有些节点很可能被合并在一起。例如，源SGW35和源PGW37通常被合并实现在同一个物理节点中，目标SGW36和目标PGW38通常被合并实现在同一个物理节点中。
还需要说明的是，当上述通信系统采用第五代移动通信技术5G时，上述各个网元在5G系统中可能会具有不同的名称，但具有相同或相似的功能，本申请对此不作限定。
请参考图4，其示出了本发明一个实施例提供的建立承载的方法的流程图。本实施例以该方法应用于图3所示的通信系统30中来举例说明。该方法包括：
步骤401，移动性管理实体接收接入网设备发送的第一请求消息。
其中，该第一请求消息是在终端的小区切换过程中由接入网设备向移动性管理实体发送的。该接入网设备是终端的源接入网设备或目标接入网设备。当该小区切换过程是接入网设备内的小区切换时，源小区和目标小区属于同一接入网设备，也即源接入网设备和目标接入网设备可以为同一个接入网设备。
需要指出的是，当设置在车辆上的终端高速移动时，会进行小区切换。从源接入网设备的源小区移动到目标接入网设备的目标小区。小区切换(Handover)是由网络侧的源接入网设备发起的，终端测量当前所在小区(源小区)及邻区的信号质量，上报给源接入网设备。源接入网设备再根据终端上报的当前小区及邻区的信号质量决定是否发起小区切换、以及向哪个小区切换。
小区切换过程可以包括：用于判决终端是否进行小区切换的第一过程、建立终端与目标接入网设备之间的无线承载的第二过程、释放终端与源接入网设备之间的无线承载的第三过程。
可选地，第一请求消息是源接入网设备在第一过程之后向移动性管理实体发送的消息，或者，第一请求消息是目标接入网设备在第二过程之后向移动性管理实体发送的消息。
示意性的，在LTE中，小区切换过程包括：基于S1接口的小区切换过程和基于X2接口的小区切换过程。
在基于S1接口的小区切换过程中，接入网设备是源接入网设备，该第一请求消息是切换请求(HO Required)消息，由源接入网设备在第一过程之后发送。示意性的，由源接入网设备在接收到终端上报的测量报告且根据该测量报告判决该终端需要执行小区切换后，发送第一请求消息。
在基于X接口的小区切换过程中，接入网设备是目标接入网设备，该第一请求消息是路径切换请求(Path Switch Request)消息，由目标接入网设备在第二过程之后发送。示意性的，目标接入网设备在接收到终端发送的无线资源控制连接配置完毕(RRC Connection Reconfigration Complete)消息后，发送第一请求消息。该RRC Connection Reconfigration Complete消息用于表示终端和目标接入网设备已经建立了无线承载。
对应地，移动性管理实体接收接入网设备发送的第一请求消息。
步骤402，移动性管理实体根据第一请求消息确定目标服务网关和目标分组数据网关。
可选地，移动性管理实体从第一请求消息中获取目标小区的标识；根据目标小区的标识为终端确定目标服务网关和目标分组数据网关。目标小区的标识可以使用本地网络标识(Local Network ID)或小区标识来表示。
通常，每个目标小区的标识对应各自的服务网关和分组数据网关。比如，小区1对应服务网关1和分组数据网关1，小区2对应服务网关2和分组数据网关2。
步骤403，移动性管理实体向目标服务网关发送第二请求消息；
可选地，该第二请求消息是创建会话请求(Create Session Request)消息。该第二请求消息用于请求目标服务网关为终端建立第一承载，第一承载是目标服务网关与目标分组数据网关之间的承载。
对应地，目标服务网关接收移动性管理实体发送的第二请求消息。
步骤404，目标服务网关根据第二请求消息建立第一承载；
可选地，目标服务网关从第二请求消息中获取目标分组数据网关的地址信息，根据目标分组数据网关的地址信息与目标分组数据网关建立第一承载。
在建立第一承载的过程中，目标分组数据网关为终端分配IP地址。
步骤405，目标服务网关获取目标分组数据网关为终端分配的IP地址；
步骤406，目标服务网关向移动性管理实体发送第二响应消息；
可选地，第二响应消息是创建会话响应(Create Session Response)消息。该第二响应消息携带有为终端分配的IP地址。
对应地，移动性管理实体接收目标服务网关发送的第二响应消息。
步骤407，移动性管理实体向终端发送IP地址。
在上述实施例中，第一请求消息是接入网设备在终端的小区切换过程中向移动性管理实体发送的消息，通过移动性管理实体接收到第一请求消息后，由移动性管理实体根据第一请求消息来确定目标服务网关和目标分组数据网关，并请求目标服务网关为终端建立第一承载，使得将第一承载的建立过程与小区切换过程并行完成，终端能够在小区切换之后使用第一承载进行通信，从而减少了整个切换过程的耗时，满足V2X消息在传输时延上的需求。
小区切换过程包括两种形式：基于X2接口的小区切换过程和基于S1的小区切换过程。由于基于X2接口的小区切换过程更为常见，下一实施例结合基于X2接口的小区切换过程，对本发明实施例进行详细阐述。
在下一实施例中，以终端是UE，接入网设备是eNB来举例说明。
请参考图5A和图5B，其示出了本发明一个实施例提供的建立承载的方法的流程图。本实施例以该建立承载的方法应用于图3所示的通信系统中来举例说明。该方法包括：
步骤501，源eNB向UE下发无线资源控制(Radio Resource Control，RRC)连接配置消息，该RRC连接配置消息携带有测量配置信息；
该测量配置信息是用于配置UE进行小区测量时的测量策略。
对应的，UE接收源eNB发送的RRC连接配置消息，从该RRC连接配置消息中获取测量配置信息。
步骤502，UE根据测量配置信息进行测量，生成测量报告；
测量报告(Measurement Report)包括：UE所在位置所能测量得到的各个小区的信号质量。
步骤503，UE向源eNB发送测量报告。
对应地，源eNB接收UE发送的测量报告。
步骤504，源eNB根据测量报告判决该UE切换至目标eNB的目标小区。
具体地，源eNB根据UE的测量报告，判决该UE从当前驻留的源小区切换至目标eNB的目标小区。示意性的，当UE所测量到的源小区的信号质量差于第一条件，目标小区的信号质量优于第二条件时，判决该UE需要从源小区切换至目标小区。
本实施例以UE需要从源小区切换至目标小区来举例说明。
步骤505，源eNB向目标eNB发送切换请求消息；
可选地，切换请求(Handover Request)消息用于询问目标eNB是否允许本次切换。
对应的，目标eNB接收源eNB发送的切换请求消息。目标eNB根据切换请求消息为UE预留相应的资源。比如，用于建立终端与目标eNB之间的无线承载的资源、小区无线网络临时识别符(Cell Radio-Network Temporaty Identifier,C-RNTI)、专用随机接入导频等。
步骤506，目标eNB向源eNB发送切换请求确认消息。
目标eNB在预留资源后，向源eNB发送切换请求确认(Handover Request Acknowledge)消息。切换请求确认消息用于表示目标eNB允许本次切换，且预留了相应的资源。
可选地，切换请求确认消息中携带有：目标eNB向UE分配的专用接入导频。
对应地，源eNB接收目标eNB发送的切换请求确认消息。
步骤507，源eNB向UE发送RRC连接配置消息。
该RRC连接配置消息用于指示UE执行小区切换。可选地，该RRC连接配置消息中携带有：目标eNB向UE分配的专用接入导频。
对应地，UE接收RRC连接配置消息。
步骤508，UE根据RRC连接配置消息，建立无线承载；
该无线承载是UE与目标eNB之间的承载。
UE从RRC连接配置消息中获取专用接入导频，通过专用接入导频与目标eNB建立目标侧的无线承载。
步骤509，UE向目标eNB发送RRC连接配置确认消息。
该RRC连接配置确认消息用于指示UE已经接入目标小区，并与目标eNB建立了目标侧的无线承载。
至此，建立了UE与目标eNB之间的无线承载。
步骤510，目标eNB向MME发送第一请求消息；
可选地，第一请求消息是路径切换请求消息。
该第一请求消息是目标eNB在UE的小区切换过程中发送的。在本实施例中，该第一请求消息用于请求MME确定该UE的目标SGW和该UE的目标PGW。
可选地，该第一请求消息携带有：目标小区对应的本地网络标识或小区标识、UE的标识、需要为UE建立的承载的信息、目标eNB在S1-U接口上的GPRS隧道协议(GPRS Tunnelling Protocol，GTP)“地址+隧道端点标识(Tunnel Endpoint ID，TEID)”。
目标eNB在S1-U接口上的GTP“地址+TEID”是用于在目标侧的S1承载中接收下行数据的地址信息。目标侧的S1承载是目标eNB与目标SGW之间的承载。GTP“地址+TEID”是指在GTP中的IP地址和TEID。
对应地，MME接收目标eNB发送的路径切换请求消息。
步骤511，MME根据第一请求消息确定目标SGW和目标PGW。
可选地，MME根据第一请求消息获取目标小区的标识；MME根据目标小区的标识为UE确定目标SGW和目标PGW。
其中，目标小区的标识可以是：与该目标小区对应的本地网络标识，或者，与该目标小区对应的小区标识。
作为本步骤的第一种实现方式，MME存储有目标小区的“本地网络标识和/或小区标识”与“SGW+PGW”的对应关系。比如：该对应关系中包括“本地网络标识1、SGW1、PGW1”、“小区标识2、SGW2、PGW2”、“小区标识3、SGW3、PGW3”等。MME根据目标小区的本地网络标识和/或小区标识，在对应关系中查询出目标SGW和目标PGW。
示意性的，对于对应关系“小区标识2、SGW2、PGW2”来讲，小区标识2是目标小区，PGW2是设置在目标eNB附近的本地网关，由于PGW2与目标eNB的距离较近，PGW2能够为目标小区提供时延较小的PDN服务能力；而对于对应关系“小区标识3、SGW3、PGW3”来讲，小区标识3是目标小区，PGW3是设置在目标eNB附近的本地网关，由于PGW3与目标eNB的距离较近，PGW3能够为目标小区提供时延较小的PDN服务能力。
作为本步骤的第二种实现方式，MME将目标小区的标识发送给其它网元，比如域名系统(Domain Name System，DNS)，由DNS根据目标小区的标识确定该UE的目标SGW和该UE的目标PGW，然后由DNS反馈目标SGW和目标PGW的信息。
可选地，DNS中存储有目标小区的“本地网络标识和/或小区标识”与“SGW+PGW”的对应关系。比如：该对应关系中包括“本地网络标识2、SGW4、PGW4”、“小区标识4、SGW5、PGW5”、“小区标识5、SGW6、PGW6”等。
步骤512，MME向目标SGW发送第二请求消息；
可选地，第二请求消息用于请求目标SGW为UE建立第一承载，第一承载是目标SGW和目标PGW之间的承载。示意性的，该承载是S5/S8承载。
可选地，该第二请求消息是创建会话请求(Create Session Request)消息。该创建会话请求消息携带有：目标PGW的地址信息和第一指示信息。第一指示信息是用于指示目标SGW为UE建立第一承载的信息。该第一指示信息还可称为新建PDN连接指示信息。
可选地，该第二请求消息还携带有：目标eNB在S1-U接口上的GTP“地 址+TEID”、UE的标识、第一承载的服务质量(Quality of Service，QoS)信息、MME在S11接口上的GTP“地址+TEID”等。
MME在S11接口上向目标SGW发送第二请求消息。对应的，目标SGW接收MME发送的第二请求消息。
步骤513，目标SGW根据第二请求消息，向目标PGW发送第四请求消息；
目标SGW从第二请求消息中获取目标PGW的地址信息、第一指示信息、目标eNB在S1-U接口上的GTP“地址+TEID”、UE的标识、第一承载的服务质量(Quality of Service，QoS)信息、MME在S11接口上的GTP“地址+TEID”等。
目标SGW获得目标eNB在S1-U接口上的GTP“地址+TEID”后，具有向目标eNB发送下行数据的能力，也即构建了目标侧的S1承载中的下行GTP隧道。
目标SGW根据目标PGW的信息，在S5/S8接口上向目标PGW发送第四请求消息。该第四请求消息用于请求目标PGW建立第一承载。可选地，该第四请求消息是创建会话请求消息。
可选地，该第四请求消息携带有：UE的标识、目标SGW在S5/S8接口上的GTP“地址+TEID”和QOS信息。
目标SGW在S5/S8接口上的GTP“地址+TEID”是用于在第一承载(目标侧的S5/S8承载)中接收下行数据的地址信息。
目标SGW在S5/S8接口上向目标PGW发送第四请求消息。对应地，目标PGW接收目标SGW发送的第四请求消息。目标PGW从第四请求消息中获取UE的标识、目标SGW在S5/S8接口上的GTP“地址+TEID”和QOS信息。
步骤514，目标PGW向目标SGW返回第四响应消息；
目标PGW从第四请求消息中获取UE的标识、目标SGW在S5/S8接口上的GTP“地址+TEID”。
目标PGW获得目标SGW在S5/S8接口上的GTP“地址+TEID”后，具有向目标SGW发送下行数据的能力，也即构建了第一承载(目标侧的S5/S8承载)中的下行GTP隧道。
目标PGW还根据UE的标识为UE分配IP地址，以及建立UE上下文。
目标PGW生成第四响应消息。可选地，该第四响应消息是创建会话响应(Create Session Response)消息。第四响应消息携带有：UE的标识、为UE 分配的IP地址、目标PGW在S5/S8接口上的GTP“地址+TEID”和协商后的QOS信息。
目标PGW在S5/S8接口上的GTP“地址+TEID”是用于在第一承载(目标侧的S5/S8承载)中接收上行数据的地址信息。
目标PGW在S5/S8接口上向目标SGW发送第四响应消息。对应地，目标SGW接收目标PGW发送的第四响应消息。
目标SGW获得目标PGW在S5/S8接口上的GTP“地址+TEID”后，具有向目标PGW发送上行数据的能力，也即构建了第一承载(目标侧的S5/S8承载)中的上行GTP隧道。
步骤515，目标SGW向MME返回第二响应消息。
可选地，第二响应消息携带有：UE的标识、为UE分配的IP地址、目标SGW在S1-U接口上的GTP“地址+TEID”。
目标SGW在S1-U接口上的GTP“地址+TEID”是用于在目标侧的S1承载中接收上行数据的地址信息。
目标SGW通过S11接口向MME发送第二响应消息，可选地，第二响应消息的目的地址是MME的GTP“地址+TEID”。相应地，MME接收目标SGW发送的第二响应消息。
步骤516，MME向目标eNB发送第一确认消息。
可选地，第一确认消息是路径切换确认(Path Switch Acknowledge)消息。该第一确认消息携带有：第三指示信息，该第三指示信息用于请求目标eNB为UE建立S1承载，该S1承载是目标eNB和目标SGW之间的承载。上述的第一指示信息和第三指示信息还可称为：新建PDN连接指示信息。
可选地，第一确认消息还携带有：目标SGW在S1-U接口上的GTP“地址+TEID”。
MME通过S1-C接口向目标eNB发送第一确认消息。相应地，目标eNB接收MME发送的第一确认消息。
目标eNB根据第一确认消息为UE建立目标侧的S1承载，该S1承载是目标eNB与目标SGW之间的承载。也即，目标eNB获得目标SGW在S1-U接口上的GTP“地址+TEID”后，具有了向目标SGW发送上行数据的能力，也即构建了目标侧的S1承载中的上行GTP隧道。
步骤517，MME向UE发送IP地址；
可选地，MME通过NAS消息向UE发送IP地址，该IP地址是用于在目标侧PDN连接中使用的IP地址。
至此，目标侧的整个PDN连接建立完毕。参考图5，目标侧的PDN连接包括三个目标侧承载：无线承载51、S1承载52和S5/S8承载53。
在发送下行数据时，应用服务器采用UE的IP地址“UE IP”为目标地址向目标PGW发送下行数据；目标PGW将目标SGW在S5/S8端口上的GTP“地址+TEID”作为目的地址，向目标PGW发送下行数据；目标SGW将目标eNB在S1-U接口上的GTP“地址+TEID”作为目的地址，向目标eNB发送下行数据；目标eNB以UE的无线承载标识(Radio Bearer ID，RB ID)作为目标地址向UE发送下行数据。该RB ID是由目标eNB所分配的。
在发送上行数据时，UE以目标eNB的RB ID作为目标地址向目标eNB发送上行数据；目标eNB以目标SGW在S1-U接口上的GTP“地址+TEID”作为目的地址，向目标SGW发送上行数据；目标SGW以目标PGW在S5/S8接口上的GTP“地址+TEID”作为目的地址，向目标PGW发送上行数据；目标PGW以应用服务器的IP地址“Svr IP”为目标地址，向应用服务器发送上行数据。
步骤518，目标eNB向源eNB发送释放资源消息；
该释放资源(Release Resource)消息用于释放源eNB和UE之间的无线承载。
可选地，释放资源消息中携带有第四指示信息，该第四指示信息用于指示源eNB释放无线承载和S1承载，该无线承载是源eNB和UE之间的承载，该S1承载是源eNB和源SGW之间的承载。第四指示信息还可称为释放源侧PDN连接指示。
对应地，目标eNB通过X2接口向源eNB发送释放资源消息。对应地，源eNB接收到释放资源消息。源eNB释放UE对应的无线承载和S1承载。
步骤519，MME向源SGW发送第三请求消息；
可选地，第三请求消息是删除会话请求(Delete Session Request)消息。该第三请求消息用于请求源SGW删除UE对应的第二承载，该第二承载是源SGW和源PGW之间的S5/S8承载。
可选地，第三请求消息中携带有第二指示信息，第二指示信息是用于指示源SGW删除UE对应的第二承载的指示信息。可选地，第二指示信息还用于 指示源SGW删除UE对应的第三承载，第三承载是源SGW和源eNB之间的S1承载。
MME通过S11接口向源SGW发送第三请求消息，对应地，源SGW接收MME发送的第三请求消息。源SGW根据第三请求消息删除与该UE对应的第二承载以及第三承载，也即，删除位于源SGW上与该UE对应的S5/S8承载和S1承载。
步骤520，源SGW向源PGW发送第五请求消息；
可选地，第五请求消息是删除会话请求(Delete Session Request)消息。该第五请求消息用于请求源PGW删除UE对应的第二承载。
源SGW通过S5/S8接口向源PGW发送第五请求消息。对应地，源PGW接收第五请求消息，源PGW删除UE对应的第二承载，也即，删除位于源PGW上与该UE对应的S5/S8承载。
步骤521，源PGW向源SGW发送第五响应消息；
可选地，第五响应消息是删除会话响应(Delete Session Response)消息。第五响应消息用于表示源SGW已经删除了第二承载。
步骤522，源SGW向MME发送第三响应消息；
可选地，第三响应消息是删除会话响应消息。第三响应消息用于表示源SGW已经删除了UE对应的第二承载，也即源SGW和源PGW之间的S5/S8承载。可选地，该第三响应消息还用于表示源SGW已经删除了UE对应的第三承载，第三承载是源eNB和源SGW之间的S1承载。
步骤523，UE与MME执行跟踪区更新流程。
可选地，UE在进入新的目标小区(跟踪区)后，与MME执行跟踪区(Tracking Area Update，TAU)流程。
至此，整个切换过程完毕。
综上所述，在该实现方式中，第一请求消息是接入网设备在终端的小区切换过程中向移动性管理实体发送的消息，通过移动性管理实体接收到第一请求消息后，由移动性管理实体根据第一请求消息来确定目标服务网关和目标分组数据网关，并请求目标服务网关为终端建立第一承载，使得将第一承载的建立过程与小区切换过程并行完成，终端能够在小区切换之后使用第一承载进行通信，从而减少了整个切换过程的耗时，满足V2X消息在传输时延上的需求。
另外，由于本实施例中是先为UE建立目标SGW和目标PGW之间的第一 承载，再为UE删除源SGW和源PGW之间的第二承载，属于“软切换”，从而保证UE的会话连续性，不会产生中断。
需要说明的是，基于S1接口的切换过程与图5A和图5B所示实施例类似，但由于源eNB和目标eNB不再通过X2接口交换信息，所以步骤510中由目标eNB发送的路径切换请求消息，改为由源eNB发送的切换请求消息。
以下为本发明的装置实施例，对于装置实施例中未详细阐述的部分，可以参考上述方法实施例中的细节。
请参考图6，其示出了本发明一个实施例提供的MME的结构框图。该MME包括：处理器610、存储器620和通信接口630。
处理器610通过总线分别与存储器620和通信接口630相连。
通信接口630用于与实现其它网元之间的通信，比如，与eNB之间的通信，或者，与SGW之间的通信。
处理器610包括一个或一个以上处理核心。处理器610通过运行操作系统或应用程序模块，以实现图4，图5A或图5B中MME的功能。
可选地，存储器620可存储操作系统622、至少一个功能所需的应用程序模块624。可选地，应用程序模块624包括：接收模块624a、处理模块624b和发送模块624c。其中，接收模块624a用于实现有关接收的步骤；处理模块624b用于实现有关计算或处理的步骤；发送模块624c用于实现有关发送的步骤。
此外，存储器620可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
本领域技术人员可以理解，图6中所示出的结构并不构成上述MME的限定，可以包括比图示更多或更少的部件或组合某些部件，或者不同的部件布置。
请参考图7，其示出了本发明一个实施例提供的建立承载的装置的框图。该装置可以通过软件或硬件实现成为MME的全部或一部分。该装置包括：接收单元710、处理单元720和发送单元730。
接收单元710用于实现上述图4实施例或图5A实施例或图5B实施例中 的步骤401、步骤406、步骤510、步骤515、步骤522等接收步骤，以及其它隐含的由MME执行的接收步骤；
处理单元720用于实现上述图4实施例或图5A实施例或图5B实施例中的步骤402、步骤511等处理步骤，以及其它隐含的由MME执行的处理步骤；
发送单元730用于实现上述图4实施例或图5A实施例或图5B实施例中的步骤403、步骤507、步骤509、步骤512、步骤516、步骤517、步骤519等发送步骤，以及其它隐含的由MME执行的发送步骤；
其中，接收单元710可以由图6中的处理器610执行存储器620中的接收模块624a实现；处理单元720可以由图6中的处理器610执行存储器620中的处理模块624b实现；发送单元730可以由图6中的处理器610执行存储器620中的发送模块624c实现。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述仅为本发明的较佳实施例，并不用以限制本发明，凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (18)

  1. 一种建立承载的方法，其特征在于，所述方法包括：
    移动性管理实体接收接入网设备发送的第一请求消息，所述第一请求消息是所述接入网设备在终端的小区切换过程中发送的，所述接入网设备是所述终端的源接入网设备或所述终端的目标接入网设备；
    所述移动性管理实体根据所述第一请求消息，确定所述终端的目标服务网关和所述终端的目标分组数据网关；
    所述移动性管理实体向所述目标服务网关发送第二请求消息，所述第二请求消息用于请求所述目标服务网关为所述终端建立第一承载，所述第一承载是所述目标服务网关和所述目标分组数据网关之间的承载；
    所述移动性管理实体接收所述目标服务网关发送的第二响应消息，所述第二响应消息携带有所述目标分组数据网关为所述终端分配的IP地址；
    所述移动性管理实体向所述终端发送所述IP地址。
  2. 根据权利要求1所述的方法，其特征在于，所述第一请求消息携带所述终端的目标小区的标识；所述移动性管理实体根据所述第一请求消息确定所述终端的目标服务网关和所述终端的目标分组数据网关，包括：
    所述移动性管理实体从所述第一请求消息中获取所述目标小区的标识；
    所述移动性管理实体根据所述目标小区的标识，确定所述终端的所述目标服务网关和所述终端的所述目标分组数据网关。
  3. 根据权利要求1或2所述的方法，其特征在于，
    所述接入网设备是所述终端的源接入网设备，所述第一请求消息是切换请求消息；
    或，
    所述接入网设备是所述终端的目标接入网设备，所述第一请求消息是路径切换请求消息。
  4. 根据权利要求1至3任一所述的方法，其特征在于，所述第二请求消息包括：第一指示信息；
    所述第一指示信息是用于指示所述目标服务网关为所述终端建立所述第一承载。
  5. 根据权利要求1至4任一所述的方法，其特征在于，所述移动性管理实体接收所述目标服务网关发送的第二响应消息之后，还包括：
    所述移动性管理实体向所述终端的源服务网关发送第三请求消息，所述第三请求消息用于请求所述源服务网关删除所述终端对应的第二承载，所述第二承载是所述源服务网关与所述终端的源分组数据网关之间的承载；
    所述移动性管理实体接收所述源服务网关发送的第三响应消息。
  6. 根据权利要求5所述的方法，其特征在于，所述第三请求消息包括：第二指示信息，所述第二指示信息是用于指示所述源服务网关删除所述终端对应的所述第二承载的信息。
  7. 一种建立承载的装置，其特征在于，所述装置包括：
    接收单元，用于接收接入网设备发送的第一请求消息，所述第一请求消息是所述接入网设备在终端的小区切换过程中发送的，所述接入网设备是所述终端的源接入网设备或所述终端的目标接入网设备；
    处理单元，用于根据所述接收单元接收到的所述第一请求消息，确定所述终端的目标服务网关和所述终端的目标分组数据网关；
    发送单元，用于向所述处理单元所确定出的所述目标服务网关发送第二请求消息，所述第二请求消息用于请求所述处理单元所确定出的所述目标服务网关为所述终端建立第一承载，所述第一承载是所述目标服务网关和所述目标分组数据网关之间的承载；
    所述接收单元，还用于接收所述目标服务网关发送的第二响应消息，所述第二响应消息携带有所述处理单元所确定出的所述目标分组数据网关为所述终端分配的IP地址；
    所述发送单元，还用于向所述终端发送所述接收单元接收到的所述IP地址。
  8. 根据权利要求7所述的装置，其特征在于，所述第一请求消息携带所 述终端的目标小区的标识；
    所述处理单元，用于从所述第一请求消息中获取所述目标小区的标识；根据所述目标小区的标识，确定所述终端的所述目标服务网关和所述终端的所述目标分组数据网关。
  9. 根据权利要求7或8所述的装置，其特征在于，
    所述接入网设备是所述终端的源接入网设备，所述第一请求消息是切换请求消息；
    或，
    所述接入网设备是所述终端的目标接入网设备，所述第一请求消息是路径切换请求消息。
  10. 根据权利要求7至9任一所述的装置，其特征在于，所述第二请求消息包括：所述第一指示信息；
    所述第一指示信息是用于指示所述目标服务网关为所述终端建立所述第一承载的信息。
  11. 根据权利要求7至10任一所述的装置，其特征在于，
    所述发送单元，还用于向所述终端的源服务网关发送第三请求消息，所述第三请求消息用于请求所述源服务网关删除所述终端对应的第二承载，所述第二承载是所述源服务网关与所述终端的源分组数据网关之间的承载；
    所述接收单元，还用于接收所述源服务网关发送的第三响应消息，所述第三响应消息是所述发送单元发送的所述第三请求消息的响应消息。
  12. 根据权利要求11所述的装置，其特征在于，所述第三请求消息包括：第二指示信息，所述第二指示信息是用于指示所述源服务网关删除所述终端对应的所述第二承载的信息。
  13. 一种建立承载的装置，其特征在于，所述装置包括：处理器和通信接口；
    所述通信接口，用于接收接入网设备发送的第一请求消息，所述第一请求 消息是所述接入网设备在终端的切换过程中发送的，所述接入网设备是所述终端的源接入网设备或所述终端的目标接入网设备；
    所述处理器，用于根据所述第一请求消息，确定所述终端的目标服务网关和所述终端的目标分组数据网关；
    所述通信接口，用于向所述目标服务网关发送第二请求消息，所述第二请求消息用于请求所述目标服务网关为所述终端建立第一承载，所述第一承载是所述目标服务网关和所述目标分组数据网关之间的承载；
    所述通信接口，还用于接收所述目标服务网关发送的第二响应消息，所述第二响应消息携带有所述目标分组数据网关为所述终端分配的IP地址；
    所述通信接口，还用于向所述终端发送所述IP地址。
  14. 根据权利要求13所述的装置，其特征在于，所述第一请求消息携带所述终端的目标小区的标识；
    所述处理器，用于从所述第一请求消息中获取所述目标小区的标识；
    所述处理器，还用于根据所述目标小区的标识，确定所述终端的所述目标服务网关和所述终端的所述目标分组数据网关。
  15. 根据权利要求13或14所述的装置，其特征在于，
    所述接入网设备是所述终端的源接入网设备，所述第一请求消息是切换请求消息；
    或，
    所述接入网设备是所述终端的目标接入网设备，所述第一请求消息是路径切换请求消息。
  16. 根据权利要求13至15任一所述的装置，其特征在于，所述第二请求消息包括：第一指示信息；
    所述第一指示信息是用于指示所述目标服务网关为所述终端建立所述第一承载的信息。
  17. 根据权利要求13至16任一所述的装置，其特征在于，
    所述通信接口，用于向所述终端的源服务网关发送第三请求消息，所述第 三请求消息用于请求所述源服务网关删除所述终端对应的第二承载，所述第二承载是所述源服务网关与所述终端的源分组数据网关之间的承载；
    所述通信接口，还用于接收所述源服务网关发送的第三响应消息。
  18. 根据权利要求17所述的装置，其特征在于，所述第三请求消息包括：第二指示信息，所述第二指示信息是用于指示所述源服务网关删除所述终端对应的所述第二承载的信息。
PCT/CN2016/101085 2016-09-30 2016-09-30 建立承载的方法及装置 WO2018058529A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP16917279.8A EP3506677B1 (en) 2016-09-30 2016-09-30 Method and device for establishing bearer
PCT/CN2016/101085 WO2018058529A1 (zh) 2016-09-30 2016-09-30 建立承载的方法及装置
CN201680084907.8A CN109076420B (zh) 2016-09-30 2016-09-30 建立承载的方法及装置
US16/359,536 US10728805B2 (en) 2016-09-30 2019-03-20 Bearer establishment method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/101085 WO2018058529A1 (zh) 2016-09-30 2016-09-30 建立承载的方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/359,536 Continuation US10728805B2 (en) 2016-09-30 2019-03-20 Bearer establishment method and apparatus

Publications (1)

Publication Number Publication Date
WO2018058529A1 true WO2018058529A1 (zh) 2018-04-05

Family

ID=61762404

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/101085 WO2018058529A1 (zh) 2016-09-30 2016-09-30 建立承载的方法及装置

Country Status (4)

Country Link
US (1) US10728805B2 (zh)
EP (1) EP3506677B1 (zh)
CN (1) CN109076420B (zh)
WO (1) WO2018058529A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020001539A1 (zh) * 2018-06-27 2020-01-02 南京中兴软件有限责任公司 一种小区切换判决方法、装置、设备和边缘计算节点
CN114071606A (zh) * 2020-08-06 2022-02-18 北京佰才邦技术股份有限公司 一种切换方法、装置及控制设备

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10805848B2 (en) * 2016-12-30 2020-10-13 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Information transmission method, network device and terminal device
CN109673003B (zh) * 2017-10-17 2021-10-26 华为技术有限公司 一种切换的方法、移动性管理网元和通信系统
CN111065135B (zh) * 2019-11-29 2021-11-12 北京长焜科技有限公司 一种3g网关到4g网关的切换方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010113528A1 (en) * 2009-04-03 2010-10-07 Panasonic Corporation Mobile communication method, mobile communication system, and corresponding apparatus
CN105517073A (zh) * 2015-12-09 2016-04-20 北京交控科技股份有限公司 Lte组网架构及核心网跨线切换信令与数据通信方法
CN105611590A (zh) * 2016-01-25 2016-05-25 北京全路通信信号研究设计院集团有限公司 一种车载接入单元的无缝切换方法及系统
CN105657756A (zh) * 2016-01-11 2016-06-08 平顶山学院 车载lte ue跨epc切换时的网络移交方法

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090109132A (ko) * 2007-02-12 2009-10-19 인터디지탈 테크날러지 코포레이션 Ｌｔｅ／ｅｕｔｒａｎ으로부터 ｇｐｒｓ／ｇｅｒａｎ으로의 핸드오버를 지원하기 위한 방법 및 장치
US9480092B2 (en) * 2009-04-23 2016-10-25 Qualcomm Incorporated Establishing packet data network connectivity for local internet protocol access traffic
CN102036325B (zh) * 2009-09-28 2013-06-05 华为终端有限公司 一种建立或修改本地ip接入承载的方法和设备
CN102131259B (zh) * 2010-01-13 2013-06-05 华为技术有限公司 切换控制方法和相关设备及系统
CN102388651B (zh) * 2010-06-10 2013-12-18 华为技术有限公司 公众陆地移动网的选择方法、装置及系统
EP2509347B1 (en) * 2011-04-05 2017-11-15 Samsung Electronics Co., Ltd. Method and apparatus for controlling inter-PLMN handover to CSG cell
CN102740268B (zh) * 2011-04-07 2017-04-12 中兴通讯股份有限公司 分组数据网络网关及终端移动性管理的系统
CN111601315B (zh) * 2012-09-29 2023-12-01 北京三星通信技术研究有限公司 一种支持对家用基站进行验证的方法
US9942909B2 (en) * 2014-02-28 2018-04-10 Futurewei Technologies, Inc. System and method for connection rehoming
US20170251405A1 (en) * 2014-10-03 2017-08-31 Intel IP Corporation Packet data network connection establishment during handover
EP3445090A1 (en) * 2016-05-11 2019-02-20 NTT Docomo, Inc. Communication method

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010113528A1 (en) * 2009-04-03 2010-10-07 Panasonic Corporation Mobile communication method, mobile communication system, and corresponding apparatus
CN105517073A (zh) * 2015-12-09 2016-04-20 北京交控科技股份有限公司 Lte组网架构及核心网跨线切换信令与数据通信方法
CN105657756A (zh) * 2016-01-11 2016-06-08 平顶山学院 车载lte ue跨epc切换时的网络移交方法
CN105611590A (zh) * 2016-01-25 2016-05-25 北京全路通信信号研究设计院集团有限公司 一种车载接入单元的无缝切换方法及系统

Non-Patent Citations (1)

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

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020001539A1 (zh) * 2018-06-27 2020-01-02 南京中兴软件有限责任公司 一种小区切换判决方法、装置、设备和边缘计算节点
CN110650507A (zh) * 2018-06-27 2020-01-03 中兴通讯股份有限公司 一种小区切换判决方法、装置、设备和边缘计算节点
CN110650507B (zh) * 2018-06-27 2022-03-08 中兴通讯股份有限公司 一种小区切换判决方法、装置、设备和边缘计算节点
CN114071606A (zh) * 2020-08-06 2022-02-18 北京佰才邦技术股份有限公司 一种切换方法、装置及控制设备
CN114071606B (zh) * 2020-08-06 2023-10-27 北京佰才邦技术股份有限公司 一种切换方法、装置及控制设备

Also Published As

Publication number Publication date
EP3506677B1 (en) 2021-03-31
EP3506677A1 (en) 2019-07-03
CN109076420B (zh) 2020-06-16
US10728805B2 (en) 2020-07-28
EP3506677A4 (en) 2019-07-03
US20190223061A1 (en) 2019-07-18
CN109076420A (zh) 2018-12-21

Similar Documents

Publication Publication Date Title
US10911990B2 (en) Network handover method and related device
US10873889B2 (en) Handover apparatus and method
US10728805B2 (en) Bearer establishment method and apparatus
US8107433B2 (en) Changing LTE specific anchor with simple tunnel switching
CN109156040B (zh) 一种通信控制的方法及相关网元
US20170238215A1 (en) Mobility management method, apparatus, and system
US10945180B2 (en) Mobility management method, apparatus, and system
WO2019104858A1 (zh) 报文转发的方法、控制面网关和用户面网关
EP3627900B1 (en) Bearer handover control method and serving gateway
CN114600508A (zh) Iab节点双连接建立的方法和通信装置
WO2021051313A1 (zh) 切换方法及装置
US20210360392A1 (en) Mobility management method and apparatus
KR101682925B1 (ko) 무선 통신 시스템에서 통신 시스템 노드와 데이터 서비스 망 노드 간 연결 설정 방법
WO2018023544A1 (zh) 通信方法、用户设备、基站、控制面网元和通信系统
US20220408317A1 (en) Handover method and communication apparatus
WO2017084042A1 (zh) 一种业务流的传输方法及装置
CN111629406B (zh) 一种切换处理的方法、相关设备、程序产品以及存储介质
WO2009152757A1 (zh) 一种数据报文发送方法、装置及通信系统
WO2011088606A1 (zh) 实现无固定锚点切换的wimax系统及其切换方法
WO2015176256A1 (zh) 一种位置区更新的信息处理方法及装置
WO2019084914A1 (zh) 小区切换方法及装置
WO2013000289A1 (zh) 直连隧道的移动性管理方法、网元及系统
CN114079870B (zh) 通信方法及装置
WO2011103707A1 (zh) 实现锚点切换的全球微波互联接入（wimax）系统及其切换方法
WO2023143270A1 (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: 16917279

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2016917279

Country of ref document: EP

Effective date: 20190326