WO2018045533A1 - Procédé de commutation de service et dispositif associé - Google Patents

Procédé de commutation de service et dispositif associé Download PDF

Info

Publication number
WO2018045533A1
WO2018045533A1 PCT/CN2016/098440 CN2016098440W WO2018045533A1 WO 2018045533 A1 WO2018045533 A1 WO 2018045533A1 CN 2016098440 W CN2016098440 W CN 2016098440W WO 2018045533 A1 WO2018045533 A1 WO 2018045533A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
service
identifier
target
source
Prior art date
Application number
PCT/CN2016/098440
Other languages
English (en)
Chinese (zh)
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 PCT/CN2016/098440 priority Critical patent/WO2018045533A1/fr
Publication of WO2018045533A1 publication Critical patent/WO2018045533A1/fr

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0055Transmission or use of information for re-establishing the radio link
    • H04W36/0069Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a service switching method and related devices.
  • the multi-terminal shared number function refers to supporting a mobile phone number corresponding to multiple Subscriber Identify Modules (SIMs) or UMTS Subscriber Identify Modules (USIMs), each card corresponding to a different one.
  • SIMs Subscriber Identify Modules
  • USIMs UMTS Subscriber Identify Modules
  • IMSI International Mobile Subscriber Identification Number
  • users can put SIM cards or USIM cards with the same mobile phone number in multiple terminals, for example, put a SIM card in the mobile phone, put a SIM card into the car phone, and put it in the wearable device.
  • a SIM card is entered, and the user can specify the type of service that each terminal can use, such as voice service, packet data service, and the like. It can be seen that although there are multiple cards, the user only needs to manage the consumption documents of one mobile phone number corresponding to the multiple cards, which is convenient for the user to use.
  • the user may need to change the running service from one terminal to another in some occasions. For example, if the user needs to leave the car when the user uses the car phone to make a call, the user cannot When you continue to use the car phone to talk, the user will want to continue the call in the phone, then the user often disconnects the car phone first, and re-establishes the call with the phone.
  • the manner of operation is complicated, and there is a call interruption, which brings a lot of inconvenience to the user, and reduces the convenience and intelligence of the terminal.
  • the embodiments of the present invention provide a service switching method and related equipment, which can implement a service switching function between multiple terminals, and ensure continuity of service transmission, thereby improving convenience and intelligence of the terminal.
  • an embodiment of the present invention provides a service switching method, including:
  • the first core network device allocates a target bearer identifier to the target terminal
  • the first core network device sends a transmission path modification request to the second core network device, where the transmission path modification request carries the identification information of the to-be-switched service, the identifier of the target terminal, and the target bearer identifier,
  • the transmission path modification request is used to request the second core network device to modify a transmission path of the data packet of the to-be-switched service.
  • the first core network device can send a transmission path modification request to the second core network device to modify the transmission path of the to-be-switched service, so as to implement multiple
  • the service switching function between the terminals ensures the continuity of the service transmission, thereby improving the convenience and intelligence of the terminal.
  • the first terminal is the source terminal.
  • the service switching request carries an identifier of the target terminal
  • the first core network device determines, according to the service switching request
  • the target terminal that describes the handover service includes:
  • the first core network device Determining, by the first core network device, the terminal indicated by the identifier of the target terminal as the target terminal; or, if the target terminal and the source terminal correspond to the same user, the first core network device The terminal indicated by the identifier of the target terminal is determined as the target terminal.
  • the method before the first core network device receives the service switching request sent by the first terminal, the method further includes:
  • the first core network device receives an acquisition request sent by the source terminal, and the acquisition request carries an identifier of the source terminal; the first core network device acquires an identifier of at least one terminal according to the obtaining request, where The user corresponding to each terminal of the at least one terminal is the same as the user corresponding to the source terminal; the first core network device sends the identifier of the at least one terminal to the source terminal, and the identifier of the at least one terminal is used by Determining a target terminal at the source terminal.
  • the method further includes: the first core network device sending indication information to the source terminal, where the indication information is used Indicates whether the at least one terminal supports the service indicated by the service type identifier.
  • the service switching request does not carry the identifier of the target terminal; the first core network device determines the target terminal of the to-be-switched service according to the service switching request, and includes:
  • the first core network device acquires the identifier of the at least one terminal, where the user corresponding to the identifier of each terminal of the at least one terminal is the same as the user corresponding to the source terminal; and the first core network device is according to the at least one The identifier of the terminal determines the target terminal.
  • the first core network device determines the target terminal according to the identifier of the at least one terminal, including: the first The core network device determines, as the target terminal, a terminal that supports the service indicated by the service type identifier in the terminal indicated by the identifier of the at least one terminal.
  • the service switching request further carries the session control indication information of the to-be-switched service, where the session control indication information is used to indicate that the session of the to-be-switched service is managed.
  • the first terminal is the target terminal, and the service switching request further carries an identifier of the target terminal.
  • the first core network device acquires the identifier of the to-be-switched service of the source terminal Information, including:
  • the first core network device obtains the IP address of the source terminal according to the identifier of the source terminal, and Determining, by the IP address of the source terminal, identification information of the to-be-switched service; or
  • the first core network device determines the source bearer identifier as the identification information of the to-be-switched service.
  • the first core network device determines the service flow template as the identification information of the to-be-switched service.
  • the first core network device detects the service flow template corresponding to the source bearer identifier and the service flow of the to-be-switched service Whether the template is the same; or the first core network device detects the to-be-switched service Whether the bearer identifier corresponding to the service flow template is the same as the source bearer identifier; if the same, the first core network device determines the source bearer identifier and/or the service flow template as the to-be-switched service. Identifying information; or, if not, determining, by the first core network device, the source bearer identifier and the service flow template as identification information of the to-be-switched service;
  • the source bearer identifier is used to indicate that the source terminal transmits the bearer of the to-be-switched service, and the bearer indicated by the source bearer identifier includes a radio bearer between the source terminal and the base station, the base station, and a Data bearer between two core network devices.
  • the first core network device allocates a target bearer identifier to the target terminal, include:
  • the first core network device acquires configuration parameters of the bearer for transmitting the to-be-switched service in the context of the source terminal according to the identification information of the to-be-switched service, where the configuration parameter includes an access point name APN and public data.
  • the first core network device detects whether there is a target bearer that satisfies the configuration parameter in the established bearer of the target terminal;
  • the first core network device establishes a target bearer for the target terminal according to the configuration parameter, and allocates a target bearer identifier;
  • the first core network device acquires a target bearer identifier used to indicate the target bearer
  • the target bearer is used to transmit the to-be-switched service, and the target bearer identifier is used to indicate the target bearer, where the target bearer includes a radio bearer between the target terminal and a base station, the base station, and a Data bearer between two core network devices.
  • an embodiment of the present invention provides a service switching method, including:
  • the second core network device Receiving, by the second core network device, a transmission path modification request sent by the first core network device, where the transmission path modification request carries the identification information of the to-be-switched service, the identifier of the target terminal, and the target bearer identifier;
  • the second core network device modifies a transmission path of the data packet of the to-be-switched service according to the identification information of the to-be-switched service, the identifier of the target terminal, and the target bearer identifier.
  • the second core network device modifies the transmission path of the to-be-switched service according to the received transmission path modification request, so that the service switching function between multiple terminals can be implemented. And to ensure the continuity of business transmission, thereby improving the convenience and intelligence of the terminal.
  • the identification information of the to-be-switched service is an IP address of the source terminal
  • the second core network device is configured according to the identification information of the to-be-switched service.
  • the identifier of the target terminal and the target bearer identifier, and the transmission path of the data packet of the to-be-switched service is modified, including:
  • the identification information of the to-be-switched service is a source bearer identifier of the source terminal, and the transmission path modification request further includes an identifier of the source terminal;
  • the second core network device modifies the transmission path of the data packet to be switched according to the identification information of the to-be-switched service, the identifier of the target terminal, and the target bearer identifier, including:
  • the second core network device receives an uplink data packet transmitted on the target bearer, and the second core network device sets a source IP address in the uplink data packet to an IP address of the source terminal; or The second core network device obtains an IP address of the target terminal according to the identifier of the target terminal, and obtains the to-be-switched to be sent to the source terminal according to the IP address of the source terminal and the source bearer identifier.
  • the downlink data packet of the service is set to the IP address of the target terminal in the downlink data packet, and is sent to the target terminal by using the target bearer.
  • the identification information of the to-be-switched service is a service flow template of the to-be-switched service
  • the second core network device modifies a transmission path of the data packet to be switched, including:
  • the second core network device obtains an IP address of the source terminal according to the service flow template of the to-be-switched service, and the second core network device receives an uplink data packet transmitted on the target bearer, and the The source IP address in the uplink data packet is set to the IP address of the source terminal; or the second core network device obtains the IP address of the target terminal according to the identifier of the target terminal, according to the to-be-switched service
  • the service flow template obtains the downlink data packet of the to-be-switched service, sets the destination IP address in the downlink data packet to the IP address of the target terminal, and sends the target IP address to the target terminal.
  • the identification information of the to-be-switched service is a source bearer identifier of the source terminal and a service flow template of the to-be-switched service; Including the identifier of the source terminal;
  • the second core network device modifies a transmission path of the data packet to be switched, including:
  • the second core network device obtains, by the second core network device, the IP address of the target terminal according to the identifier of the target terminal, obtaining a downlink data packet of the to-be-switched service according to the service flow template of the to-be-switched service, and performing the downlink
  • the destination IP address in the data packet is set to the IP address of the target terminal, and is sent to the target terminal by using the target bearer; and/or the second core network device obtains according to the identifier of the target terminal.
  • the IP address of the target terminal Obtaining, by the IP address of the target terminal, the downlink data packet of the to-be-switched service sent to the source terminal according to the IP address of the source terminal and the source bearer identifier, and the destination in the downlink data packet
  • the IP address is set to an IP address of the target terminal, and is sent to the target terminal by using the target bearer.
  • an embodiment of the present invention provides a service switching method, including:
  • the first terminal sends a service switching request to the first core network device, where the service switching request is used for The switching service of the source terminal is switched, and the service switching request carries the identifier of the source terminal.
  • the first terminal initiates a service switching request to the first core network device, so as to implement a modification of the transmission path of the service to be switched by using the first core network device and the second core network device,
  • the service switching function between multiple terminals improves the convenience and intelligence of the terminal.
  • the first terminal is the source terminal.
  • the service switching request further carries an identifier of the target terminal.
  • the method before the sending, by the first terminal, the service switching request to the first core network device, the method further includes:
  • the source terminal sends an acquisition request to the first core network device, where the acquisition request carries the identifier of the source terminal, and the obtaining request is used to obtain the identifier of the at least one terminal from the first core network device.
  • the user corresponding to the identifier of each terminal in the at least one terminal is the same as the user corresponding to the identifier of the source terminal;
  • the source terminal receives the identifier of the at least one terminal sent by the first core network device;
  • the terminal determines the target terminal according to the identifier of the at least one terminal.
  • the method further includes:
  • the source terminal receives the indication information sent by the first core network device, where the indication information is used to indicate whether the at least one terminal supports the service indicated by the service type identifier; and the source terminal is according to the at least one Determining the target terminal, the determining, by the source terminal, determining, according to the indication information, a terminal that supports the service indicated by the service type identifier in the terminal indicated by the identifier of the at least one terminal, as the target terminal .
  • the method before the sending, by the first terminal, the service switching request to the first core network device, the method further includes:
  • the source terminal acquires the identifier of the at least one terminal, and the user corresponding to the identifier of each terminal of the at least one terminal is the same as the user corresponding to the identifier of the source terminal; and the source terminal is configured according to the identifier of the at least one terminal. Determine the target terminal.
  • the source terminal determines the service type identifier of the to-be-switched service, and obtains indication information about whether the at least one terminal supports the service indicated by the service type identifier; the source terminal root Determining the target terminal according to the identifier of the at least one terminal, including: the source terminal, according to the indication information, a terminal that supports the service indicated by the service type identifier in the terminal indicated by the identifier of the at least one terminal , determined as the target terminal.
  • the at least one terminal is a terminal that establishes a communication connection with the source terminal; and the communication connection includes at least one of a device-to-device D2D connection, a Bluetooth connection, and a WIFI connection.
  • the service switching request further carries a source bearer identifier and/or a service flow template.
  • the source bearer identifier is used to indicate that the source terminal transmits the bearer of the to-be-switched service, and the bearer indicated by the source bearer identifier includes a radio bearer between the source terminal and the base station, the base station, and a Data bearer between two core network devices.
  • the first terminal is a target terminal
  • the service switching request further carries an identifier of the target terminal.
  • the method before the sending, by the first terminal, the service switching request to the first core network device, the method further includes:
  • the target terminal determines the service type identifier of the to-be-switched service, and obtains, by the at least one terminal, the indication information of the service indicated by the service type identifier, where the target terminal is configured according to the at least one terminal. And determining, by the target terminal, the terminal that determines the service indicated by the service type identifier in the terminal indicated by the identifier of the at least one terminal, according to the indication information, as the source terminal.
  • the service switching request carries a source bearer identifier and/or a service flow template
  • the target terminal after determining the source terminal according to the identifier of the at least one terminal, further includes:
  • the target terminal after determining the source terminal according to the identifier of the at least one terminal, further includes:
  • the target terminal after determining the source terminal according to the identifier of the at least one terminal, further includes:
  • the target terminal acquires a source bearer identifier and a service flow template of the to-be-switched service to the source terminal according to the service type identifier of the to-be-switched service;
  • the source bearer identifier is used to indicate that the source terminal transmits the bearer of the to-be-switched service, and the bearer indicated by the source bearer identifier includes a radio bearer between the source terminal and the base station, the base station, and a Data bearer between two core network devices.
  • the at least one terminal is a terminal that establishes a communication connection with the target terminal;
  • the communication connection includes at least one of a D2D connection, a Bluetooth connection, and a WIFI connection.
  • an embodiment of the present invention provides a first core network device, including:
  • a receiving unit configured to receive a service switching request sent by the first terminal, where the service switching request is used to request to switch the to-be-switched service of the source terminal, where the service switching request carries the identifier of the source terminal;
  • An obtaining unit configured to acquire, according to the service switching request received by the receiving unit, identification information of the to-be-switched service of the source terminal;
  • a determining unit configured to determine, according to the service switching request received by the receiving unit, a target terminal of the to-be-switched service
  • An allocating unit configured to allocate a target bearer identifier to the target terminal determined by the determining unit
  • a sending unit configured to send a transmission path modification request to the second core network device, where the transmission path modification request carries the identification information of the to-be-switched service, the identifier of the target terminal, and the target bearer identifier, where the transmission path is The modification request is used to request the second core network device to modify a transmission path of the data packet of the to-be-switched service.
  • the first core network device provided by the fourth aspect of the present invention is used to perform the service switching method provided by the first aspect of the present invention.
  • the first core network device provided by the fourth aspect of the present invention is used to perform the service switching method provided by the first aspect of the present invention.
  • the structure of the first core network device includes a processor and a transceiver for performing the service switching method provided by the first aspect of the present invention.
  • a memory may be further included, where the memory is used to store application code that supports the first core network device to perform the above method, and the processor is configured to execute an application stored in the memory.
  • an embodiment of the present invention provides a second core network device, including:
  • a receiving unit configured to receive a transmission path modification request sent by the first core network device, where the transmission path modification request carries the identification information of the service to be switched, the identifier of the target terminal, and the target bearer identifier;
  • a modifying unit configured to modify a transmission path of the data packet of the to-be-switched service according to the identification information of the to-be-switched service, the identifier of the target terminal, and the target bearer identifier received by the receiving unit.
  • the second core network device provided by the fifth aspect of the present invention is used to perform the service switching method provided by the second aspect of the present invention.
  • the second core network device provided by the fifth aspect of the present invention is used to perform the service switching method provided by the second aspect of the present invention.
  • the structure of the second core network device includes a processor and a transceiver for performing the service switching method provided by the second aspect of the present invention.
  • a memory may be further included, where the memory is used to store application code that supports the second core network device to perform the above method, and the processor is configured to execute an application stored in the memory.
  • an embodiment of the present invention provides a first terminal, including:
  • a sending unit configured to send a service switching request to the first core network device, where the service switching request is used to request to switch the to-be-switched service of the source terminal, where the service switching request carries the identifier of the source terminal.
  • the first terminal provided by the sixth aspect of the present invention is used to perform the service switching method provided by the third aspect of the present invention.
  • the third aspect of the embodiment of the present invention is used to perform the service switching method provided by the third aspect of the present invention.
  • the structure of the first terminal includes a processor and a transceiver for performing the service switching method provided by the third aspect of the present invention.
  • a memory may be further included, where the memory is used to store application code that supports the first terminal to execute the foregoing method, and the processor is configured to execute an application stored in the memory.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the first core network device, including a program designed to perform the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the second core network device, including a program designed to perform the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use in the first terminal, including a program designed to perform the above aspects.
  • the names of the first core network device, the second core network device, the first terminal, the source terminal, and the target terminal are not limited to the device itself. In actual implementation, the devices may appear under other names. As long as the functions of the respective devices are similar to the present invention, they are within the scope of the claims and the equivalents thereof.
  • the first core network device receives the service switching request of the to-be-switched service of the switching source terminal sent by the first terminal, obtains the identification information of the to-be-switched service of the source terminal according to the service switching request, and determines the service to be switched. And the destination terminal identifier is allocated to the target terminal, and finally the transmission path of the data packet for modifying the to-be-switched service is sent to the second core network device, so that the transmission path modification of the service to be switched by the second core network device implements the service to be switched.
  • the switching ensures the continuity of the service transmission, thereby improving the convenience and intelligence of the terminal.
  • FIG. 1 is a schematic diagram of a possible network architecture according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of a service switching method according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of step 103 in FIG. 2 according to an embodiment of the present disclosure
  • step 104 in FIG. 2 is a schematic flowchart of step 104 in FIG. 2 according to an embodiment of the present invention
  • FIG. 5 is a schematic flowchart diagram of another service switching method according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic flowchart of a method for determining a target terminal by a source terminal according to an embodiment of the present disclosure
  • FIG. 7 is a schematic flowchart of another method for determining a target terminal by a source terminal according to an embodiment of the present disclosure
  • FIG. 8 is a schematic flowchart diagram of another service switching method according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic diagram of a modularization of a first core network device according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of a modularization of a determining unit according to an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of a first core network device according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic diagram of a modularization of a second core network device according to an embodiment of the present invention.
  • FIG. 13 is a schematic structural diagram of a second core network device according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic diagram of a modularity of a first terminal according to an embodiment of the present invention.
  • FIG. 15 is a schematic diagram of another modularity of a first terminal according to an embodiment of the present disclosure.
  • FIG. 16 is a schematic diagram of another modularity of a first terminal according to an embodiment of the present disclosure.
  • FIG. 17 is a schematic structural diagram of a first terminal according to an embodiment of the present invention.
  • the solution provided by the invention can implement the service switching function between multiple terminals and ensure the continuity of service transmission, thereby improving the convenience and intelligence of the terminal.
  • references to "an embodiment” herein mean that a particular feature, structure, or characteristic described in connection with the embodiments can be included in at least one embodiment of the invention.
  • the appearances of the phrases in various places in the specification are not necessarily referring to the same embodiments, and are not exclusive or alternative embodiments that are mutually exclusive. Those skilled in the art will understand and implicitly understand that the embodiments described herein can be combined with other embodiments.
  • FIG. 1 it is an Evolved Packet System (EPS) network architecture diagram, including user equipment ( User Equipment (UE), Internet of Things (IoT) equipment, Evolved UMTS Terrestrial Radio Access Network (E-UTRAN), Mobility Management Entity (MME), GPRS Service Support Node (SGSN), PDN Gateway (P-GW), Serving Gateway (S-GW, Serving Gateway), Home Subscriber Server (HSS), Server (Service) ).
  • UE User Equipment
  • IoT Internet of Things
  • E-UTRAN Evolved UMTS Terrestrial Radio Access Network
  • MME Mobility Management Entity
  • SGSN PDN Gateway
  • P-GW Serving Gateway
  • S-GW Serving Gateway
  • HSS Home Subscriber Server
  • Service Service
  • the EUTRAN is a network composed of multiple evolved NodeBs (eNodeBs), which implements wireless physical layer functions, resource scheduling and radio resource management, radio access control, and mobility management functions.
  • eNodeB is connected to the S-GW through the user plane interface S1-U for transmitting user data.
  • the S1-AP protocol is connected to the MME through the control plane interface, and the radio access bearer control function is implemented by using the S1-AP protocol.
  • the SGSN is connected to the base station controller (BSC) of the GSM/EDGE radio access network (GERAN) through the Gb interface, or the radio network controller of the UMTS radio access network (URAN) via the Iu-PS interface (Radio) Network Controller (RNC) connects to manage mobile data, such as user identification, encryption, and compression.
  • BSC base station controller
  • GERAN GSM/EDGE radio access network
  • URAN UMTS radio access network
  • RNC Radio Network Controller
  • the MME is mainly responsible for all control plane functions of the user, that is, session management, including NAS signaling and security, tracking area management, P-GW and S-GW selection.
  • the S-GW is mainly responsible for data transmission, forwarding, and routing handover of the UE, and serves as a local mobility anchor point when the UE switches between eNodeBs (for each UE, only one S-GW serves each time) .
  • the P-GW is responsible for IP address allocation of the UE, data packet filtering, rate control, and generation of charging information of the UE.
  • the IoT device can access the network in multiple ways.
  • the IoT device can access the network through a direct link (such as wireless access technology), or can be connected to a relay node (such as a UE) before passing through the medium.
  • a direct link such as wireless access technology
  • a relay node such as a UE
  • the multi-terminal shared number function can be supported, which means that one mobile phone number is supported by multiple SIMs or USIMs, and each card corresponds to a different IMSI identifier, for example, a user's mobile phone and smart bracelet. Smart watches and smart glasses can be configured with different cards, and these cards share the same mobile phone number, so that the user only needs to manage one mobile phone number, which is convenient for the user.
  • the terminal A and the terminal B share the same mobile phone number.
  • the service of the terminal A can be switched to the terminal B, and the switched service can be a voice service, a video service, or a packet.
  • the MME/SGSN receives a service switching request sent by the first terminal, where the service switching request is used to request to switch the to-be-switched service of the source terminal, and the service switching request carries the identifier of the source terminal; the MME/SGSN is configured according to The service switching request acquires the identification information of the to-be-switched service of the source terminal; the MME/SGSN determines the target terminal of the to-be-switched service according to the service switching request; the MME/SGSN is The target terminal allocates a target bearer identifier; the MME/SGSN sends a transport path modification request to the SGW/PGW, where the transport path modification request carries the identification information of the to-be-switched service, the identifier of the target terminal, and the Target bearing And the transmission path modification request is used to request the SGW/PGW to modify a transmission path of the data packet of the to-be-switched service.
  • GSM Global System of Mobile communication
  • CDMA code division multiple access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • the source terminal and the target terminal may be UEs or IoT devices, and the UE or IoT device may include, but is not limited to, a terminal, a mobile station (Mobile Station, MS), or a mobile terminal (Mobile Terminal).
  • the UE or IoT device can communicate with one or more core networks via a radio access network, for example, the UE can be a mobile phone (or "cellular" phone) or a computer with a mobile terminal, etc.
  • IoT can Portable, pocket-sized, hand-held, computer-integrated or in-vehicle mobile devices (smart bracelets, smart watches, smart glasses, etc.) that exchange voice, video and/or packet data with the wireless access network.
  • the first core network device in the embodiment of the present invention is an MME or an SGSN
  • the second core network device is an SGW or a PGW.
  • these devices may appear under other names. As long as the functions of the respective devices are similar to the present invention, they are within the scope of the claims and the equivalents thereof.
  • FIG. 2 is a schematic flowchart of a service switching method according to an embodiment of the present invention.
  • the service switching method in the embodiment of the present invention includes steps 101 to 106.
  • the service switching request in the embodiment of the present invention is initiated by the first terminal, and the switched service to be switched is a service in the source terminal, that is, the source terminal and the second core before the to-be-switched service is switched.
  • a data stream for the to-be-switched service can be transmitted between the network devices.
  • the first terminal may be the source terminal, or may be a target terminal to which the to-be-switched service is to be switched.
  • the switching process please refer to the following details.
  • the first terminal sends a service switching request to the first core network device.
  • the service switching request is used to request to switch the to-be-switched service of the source terminal, where the service switching request carries the identifier of the source terminal.
  • the service switching request may further carry an identifier of the target terminal.
  • the service switching request may further include a source bearer identifier and/or a traffic flow template (TFT) of the to-be-switched service.
  • TFT traffic flow template
  • the service switching request may further carry the service type identifier of the to-be-switched service.
  • the identifier of the terminal involved in the embodiment of the present invention may be an IMSI of the terminal or a Globally Unique Temporary UE Identity (GUTI) of the terminal, where the GUTI is used in the mobile network, and may be reduced.
  • the private parameters of terminals such as IMSI are exposed in the network transmission, which can avoid the security risk caused by directly transmitting the IMSI identity.
  • GUTI and IMSI can be used to uniquely identify a terminal.
  • the to-be-switched service may be one or more services in the source terminal, for example, the first terminal may send a service switch for requesting to switch the voice service and the packet data service of the source terminal.
  • the request is not limited in this embodiment of the present invention.
  • the source bearer identifier in the embodiment of the present invention is used to indicate that the source terminal transmits the bearer of the to-be-switched service, and the bearer indicated by the source bearer identifier includes the source terminal and the base station.
  • the service type identifiers involved in the embodiments of the present invention are identifiers for distinguishing various types of services, and the services may include, but are not limited to, voice, video, and packet data services.
  • the first core network device receives a service switching request sent by the first terminal.
  • the first core network device acquires the identification information of the to-be-switched service of the source terminal according to the service switching request.
  • the first core network device determines, according to the service switching request, a target terminal of the to-be-switched service.
  • the first core network device allocates a target bearer identifier to the target terminal.
  • the target bearer includes a radio bearer between the target terminal and the base station, and a data bearer between the base station and the second core network device, where the target bearer is used to transmit the to-be-switched service, and the target bearer identifier And indicating the target bearer, so that the data packet of the service to be switched can be transmitted in the target terminal by the established target bearer.
  • the first core network device sends a transmission path modification request to the second core network device.
  • the transmission path modification request carries the identification information of the to-be-switched service, the identifier of the target terminal, and the target bearer identifier, where the transmission path modification request is used to request the second core network device to modify the The transmission path of the data packet to be switched.
  • the second core network device receives the transmission path modification request sent by the first core network device.
  • the second core network device modifies a transmission path of the data packet of the to-be-switched service according to the identification information of the to-be-switched service, the identifier of the target terminal, and the target bearer identifier.
  • the second core device is configured to set a source IP address in the uplink data packet of the to-be-switched service to an IP address of the source terminal, where the transmission path of the uplink data packet of the to-be-switched service is modified. Or the second core device is configured to set a destination IP address in the downlink data packet to an IP address of the target terminal. And sending the downlink data packet of the modified destination IP address to the target terminal. This achieves switching the to-be-switched service of the source terminal to the target terminal.
  • step 102 can be implemented by using the following four feasible solutions:
  • the first core network device obtains the identifier of the source terminal carried in the service switching request.
  • the IP address of the source terminal is determined, and the IP address of the source terminal is determined as the identification information of the service to be switched.
  • the to-be-switched service determined by the first core network device according to the IP address of the source terminal is all services of the source terminal.
  • the first core network device determines the source bearer identifier as the identification information of the to-be-switched service. In this case, the first core network device may determine, according to the identifier of the source terminal and the source bearer identifier, the service transmitted by the bearer indicated by the source bearer identifier in the source terminal as the service to be switched.
  • the first core network device determines the service flow template as the identification of the to-be-switched service. information.
  • a service corresponds to a TFT
  • a TFT corresponds to a bearer for transmitting the service.
  • a TFT may include multiple packet filters (also referred to as packet filters), and may be classified into an uplink service flow template and a downlink service flow template.
  • the uplink service flow template is an uplink packet filter in the TFT
  • the downlink service flow template is a downlink packet filter in the TFT.
  • the main content of the filter is an IP five yuan
  • the IP quintuple includes: a source IP address, a destination IP address, a source port, a destination port, and a transport layer protocol number.
  • the transport layer protocol can be classified into a Transmission Control Protocol (TCP) and a User Datagram Protocol. (User Datagram Protocol, UDP), Sequence Packet Exchange Protocol (SPX), and the like.
  • TCP Transmission Control Protocol
  • UDP User Datagram Protocol
  • SPX Sequence Packet Exchange Protocol
  • the process of using the TFT on the terminal and the PGW, the terminal or the PGW matching the service data packet and the filter included in the TFT is to check whether the IP quintuple in the service data packet matches the IP quintuple in the filter, and if it matches, Then, the service data packet is mapped to the bearer corresponding to the matched TFT. Therefore, the service flow template can uniquely indicate the service to be switched in the source terminal.
  • the to-be-switched service is a TCP-based service between the source terminal and the communication peer
  • the IP quintuple included in the filter in the service flow template of the to-be-switched service includes: the IP address of the source terminal, and the communication IP address of the peer end, port of the source terminal, port of the communication peer, and TCP protocol number.
  • the first core network device detects the service flow template corresponding to the source bearer identifier and the Whether the service flow template of the service to be switched is the same; or the first core network device detects whether the bearer identifier corresponding to the service flow template of the to-be-switched service is the same as the source bearer identifier.
  • the first core network device identifies the source bearer and/or the service
  • the service flow template is determined as the identification information of the service to be switched.
  • the first core network device identifies the source bearer and the The service flow template is determined as the identification information of the service to be switched.
  • step 103 can be implemented by using two feasible solutions:
  • the scheme for determining the target terminal by the first core network device may be divided into two types:
  • the first core network device determines the terminal indicated by the identifier of the target terminal as the target terminal.
  • the first core network device determines the terminal indicated by the identifier of the target terminal as the target terminal. Specifically, the first core network device authenticates the identifier of the target terminal, and if the target terminal and the source terminal correspond to the same user, the first core network device authorizes the identifier indication of the target terminal. Terminal And determining, by the target terminal, that the target terminal and the source terminal are different users, the first core network device does not switch the to-be-switched service.
  • the first core network device determines the target terminal according to the identifier of the source terminal.
  • the identifiers of multiple terminals corresponding to the same user may refer to the identifiers of multiple terminals corresponding to the same user identifier, and the user identifiers may include, but are not limited to, international mobile subscriber ISDN/PSTN codes. Mobile Subscriber International ISDN/PSTN number, MSISDN) and session initiation protocol (SIP) identifier.
  • MSISDN Mobile Subscriber International ISDN/PSTN number
  • SIP session initiation protocol
  • the target terminal is a terminal with the same mobile phone number as the source terminal.
  • step 103 if the service switching request does not carry the identifier of the target terminal, the first core network device determines the target terminal according to the identifier of the source terminal.
  • FIG. 3 a schematic flowchart of step 103 is provided according to an embodiment of the present invention.
  • the schematic flowchart shown in FIG. 3 includes step 1031 and step 1032.
  • the first core network device acquires an identifier of at least one terminal.
  • the first core network device After the first core network device receives the service switching request, the identifier of the source terminal is determined, and the identifier of the at least one terminal is obtained according to the identifier of the source terminal, where each terminal in the at least one terminal The user corresponding to the identifier is the same as the user corresponding to the identifier of the source terminal.
  • the first core network device may pre-store the identifiers of the respective terminals and the users corresponding to the respective terminal identifiers, so that the multiple terminal identifiers that are the same as the users corresponding to the identifiers of the source terminals are conveniently obtained.
  • the first core network device determines the target terminal according to the identifier of the at least one terminal.
  • the scheme for determining the target terminal according to the identifier of the at least one terminal by the first core network device may be divided into two types:
  • the first core network device may select one of the identifiers of the at least one terminal as the identifier of the target terminal, and determine the terminal indicated by the identifier of the target terminal as the target terminal.
  • the other is that if the service switching request sent by the source terminal carries the service type identifier of the to-be-switched service, the first core network device supports the terminal indicated by the identifier of the at least one terminal.
  • the terminal of the service indicated by the service type identifier is determined as the target terminal.
  • the first core network device obtains, by the first core network device, whether the at least one terminal supports the indication information of the service indicated by the service type identifier, where the first core network device selects one of the at least one terminal to support the The terminal of the service indicated by the service type identifier is used as the target terminal.
  • FIG. 4 is a schematic flowchart of step 104 according to an embodiment of the present invention. As shown in FIG. 4, the flow diagram includes steps 1041 to 1044. .
  • the first core network device acquires configuration parameters of the bearer transmitting the to-be-switched service in the context of the source terminal according to the identification information of the to-be-switched service.
  • the configuration parameter may include, but is not limited to, at least an Access Point Name (APN), a Public Data Network (PDN) gateway address, and a Quality of Service (Qos) parameter.
  • APN Access Point Name
  • PDN Public Data Network
  • Qos Quality of Service
  • the first core network device obtains The bearer identifier corresponding to all services in the source terminal. Therefore, the first core network device acquires configuration parameters of the bearer indicated by the bearer identifier.
  • the first core network device may obtain, according to the identifier of the source terminal, the configuration parameter of the bearer indicated by the source bearer identifier in the source terminal.
  • the first core network device can obtain the corresponding service to be switched according to the service flow template.
  • the source carries the identifier, and obtains the configuration parameter of the bearer indicated by the source bearer identifier in the source terminal.
  • the identification information of the to-be-switched service is the source bearer identifier of the source terminal and the service flow template of the to-be-switched service
  • the service flow template corresponding to the source bearer identifier and the service to be switched service If the flow template is the same, or if the bearer identifier corresponding to the service flow template of the to-be-switched service is the same as the source bearer identifier, the configuration parameter of the bearer indicated by the source bearer identifier is obtained.
  • the first core network device acquires the configuration parameter of the bearer indicated by the source bearer identifier and the configuration parameter of the bearer indicated by the service flow template.
  • the first core network device detects whether a target bearer that meets the configuration parameter exists in the established bearer of the target terminal.
  • step 1044 is performed. If the target bearer that satisfies the configuration parameter does not exist in the established bearer, step 1043 is performed.
  • step 1044 is performed; if not, step 1043 is performed.
  • the first core network device establishes a target bearer for the target terminal according to the configuration parameter, and allocates a target bearer identifier.
  • the first core network device establishes a target bearer for the target terminal according to the configuration parameter.
  • the first core network device may specifically establish a target bearer according to the obtained configuration parameter by paging the target terminal, where the target bearer includes a radio bearer between the target terminal and the base station, the base station, and the A data bearer between the two core network devices, where the target bearer is used to transmit the to-be-switched service.
  • the first core network device allocates a target bearer identifier for the target bearer, where the target bearer identifier is used to indicate the target bearer.
  • the first core network device acquires a target bearer identifier for indicating a target bearer that satisfies the configuration parameter.
  • the first core network device acquires a target bearer identifier indicating the target bearer, where the target bearer is used for transmission, if the target bearer that meets the configuration parameter exists in the established bearer of the target terminal, The service to be switched.
  • step 106 when the identification information of the to-be-switched service carried by the transmission path modification request is different, the second core network device according to the identification information of the to-be-switched service, the target terminal
  • the identifier and the target bearer identifier are different in the specific implementation manner of modifying the data packet of the to-be-switched service, and the different situations of the identification information of the to-be-switched service in step 102 can be classified into the following four situations:
  • the first case is: if the identification information of the to-be-switched service is an IP address of the source terminal, the second core network device determines the target bearing according to the identifier of the target terminal and the target bearer identifier. Loaded. For modifying the transmission path of the uplink data packet, the second core network device receives the uplink data packet transmitted on the target bearer, and sets the source IP address in the uplink data packet to the IP address of the source terminal. Address: for the case of modifying the transmission path of the downlink data packet, the second core network device obtains the IP address of the target terminal according to the identifier of the target terminal, and obtains the address according to the IP address of the source terminal. Determining, by the source terminal, the downlink data packet of the to-be-switched service, setting a destination IP address in the downlink data packet to an IP address of the target terminal, and sending the target IP address to the target terminal by using the target bearer.
  • the second case is: if the identification information of the to-be-switched service is the source bearer identifier of the source terminal, the transmission path modification request further includes the identifier of the source terminal; and the second core network device is according to the source An identifier of the terminal, determining an IP address of the source terminal, and determining, by the second core network device, the target bearer according to the identifier of the target terminal and the target bearer identifier.
  • the second core network device receives the uplink data packet transmitted on the target bearer, and the second core network device sets the source IP address in the uplink data packet to The IP address of the source terminal; the second core network device obtains an IP address of the target terminal according to the identifier of the target terminal, according to the IP address of the source terminal, And the source bearer identifier, obtaining a downlink data packet of the to-be-switched service sent to the source terminal, setting a destination IP address in the downlink data packet to an IP address of the target terminal, and passing the The target bearer is sent to the target terminal.
  • the third case is: if the identification information of the to-be-switched service is the service flow template of the to-be-switched service, the second core network device determines the target according to the identifier of the target terminal and the target bearer identifier. Hosted. For the case of modifying the transmission path of the uplink data packet, the second core network device obtains an IP address of the source terminal according to the service flow template of the to-be-switched service, and the second core network device receives the target bearer.
  • the second core network device transmitting an uplink data packet, and setting a source IP address in the uplink data packet to an IP address of the source terminal; and in a case of modifying a transmission path of the downlink data packet, the second core network device according to the Obtaining an identifier of the target terminal, obtaining an IP address of the target terminal, obtaining a downlink data packet of the to-be-switched service according to the service flow template of the to-be-switched service, and setting a destination IP address in the downlink data packet as An IP address of the target terminal is sent to the target terminal by using the target bearer.
  • the fourth case is: if the identification information of the to-be-switched service is the source bearer identifier of the source terminal and the service flow template of the to-be-switched service, the transmission path modification request further includes the label of the source terminal.
  • the second core network device determines the target bearer according to the identifier of the target terminal and the target bearer identifier, and the second core network device is configured according to the identifier of the source terminal or the service to be switched.
  • a flow template determines an IP address of the source terminal. For modifying the transmission path of the uplink data packet, the second core network device receives the uplink data packet transmitted on the target bearer, and sets the source IP address in the uplink data packet to the IP address of the source terminal. address.
  • the second core network device obtains the IP address of the target terminal according to the identifier of the target terminal, and obtains the to-be-served according to the service flow template of the to-be-switched service. And switching the downlink data packet of the service, setting the destination IP address in the downlink data packet to an IP address of the target terminal, and sending the target terminal to the target terminal by using the target bearer; and/or, the second core
  • the network device obtains the IP address of the target terminal according to the identifier of the target terminal, and obtains downlink data of the to-be-switched service that is sent to the source terminal according to the IP address of the source terminal and the source bearer identifier.
  • the destination IP address in the downlink data packet is set to an IP address of the target terminal, and is sent to the target terminal by using the target bearer.
  • the bearer identifier corresponding to the service flow template corresponding to the to-be-switched service is the same as the source bearer identifier, the method is performed in an "OR" manner; if the service flow template corresponding to the service to be switched corresponds to the service flow template If the bearer identifier and the source bearer identifier are different, the method is performed in a "and" manner.
  • whether the terminal supports the service indicated by the service type identifier may be represented by an activation state and a deactivation state, where the terminal indicates the service type identifier
  • the terminal indicates the service type identifier
  • the terminal When the service is in an active state, the terminal supports the service indicated by the service type identifier, and when the terminal indicates that the service indicated by the service type identifier is in a deactivated state, the terminal does not support the service.
  • the type identifies the business indicated.
  • the first core network device may save an activation state or a deactivation state of each terminal identifier and various service type identifiers, so that the first core network device directly generates whether the terminal supports the service indicated by the service type identifier. Instructions.
  • the first core network device receives the service switching request of the to-be-switched service of the switching source terminal sent by the first terminal, obtains the identification information of the to-be-switched service of the source terminal according to the service switching request, and determines the service to be switched. And the destination terminal identifier is allocated to the target terminal, and finally the transmission path of the data packet for modifying the to-be-switched service is sent to the second core network device, so that the transmission path modification of the service to be switched by the second core network device implements the service to be switched. Switching, and is to achieve the business switching function between multiple terminals, and to ensure the continuity of service transmission, thereby improving the end Convenience and intelligence.
  • FIG. 5 is a schematic flowchart of another service switching method according to an embodiment of the present invention.
  • the service switching method in the embodiment of the present invention includes steps 201 to 212.
  • the service switching request in the embodiment of the present invention is initiated by the source terminal, and the switched service to be switched is the service in the source terminal, that is, the source terminal and the second core network before the to-be-switched service is switched.
  • the data flow for the to-be-switched service can be transmitted between the devices.
  • details about the switching process refer to the following details.
  • the source terminal sends a service switching request to the first core network device, where the service switching request is used to request to switch the to-be-switched service of the source terminal, where the service switching request carries the identifier of the source terminal.
  • the service switching request is used to request to switch the to-be-switched service of the source terminal, where the service switching request carries the identifier of the source terminal.
  • the service switching request may further carry an identifier of the target terminal.
  • the service switching request may further include a source bearer identifier and/or a service flow template TFT of the to-be-switched service.
  • the service switching request may further carry the service type identifier of the to-be-switched service.
  • the service switching request may further include session control information of the to-be-switched service, where the session control information is used to indicate that the session of the to-be-switched service is managed.
  • the session control information may include, but is not limited to, at least one of a calling identifier, a called identifier, a media format (such as video, voice), and an encoding mode (video/audio encoding).
  • the identifier of the terminal involved in the embodiment of the present invention may be the IMSI of the terminal or the GUTI of the terminal, where the GUTI is used in the mobile network, and the private parameters of the terminal such as the IMSI may be reduced to be exposed in the network transmission. Avoid the direct transmission of security risks from the IMSI identity. Both GUTI and IMSI can be used to uniquely identify a terminal.
  • the to-be-switched service may be one or more services in the source terminal, for example, the first terminal may send a service switch for requesting to switch the voice service and the packet data service of the source terminal.
  • the request is not limited in this embodiment of the present invention.
  • the source bearer identifier in the embodiment of the present invention is used to indicate that the source terminal transmits the bearer of the to-be-switched service, and the bearer indicated by the source bearer identifier includes the source terminal and the base station.
  • the service type identifiers involved in the embodiments of the present invention are identifiers for distinguishing various types of services, and the services may include, but are not limited to, voice, video, and packet data services.
  • the first core network device acquires the identification information of the to-be-switched service of the source terminal according to the service switching request.
  • step 102 For details, refer to the detailed description of step 102 in the embodiment shown in FIG. 2, and details are not described herein again.
  • the first core network device determines, according to the service switching request, a target terminal of the to-be-switched service.
  • step 103 For details, refer to the detailed description of step 103 in the embodiment shown in FIG. 2, and details are not described herein again.
  • the first core network device allocates a target bearer identifier to the target terminal.
  • step 104 For details, refer to the detailed description of step 104 in the embodiment shown in FIG. 2, and details are not described herein again.
  • the first core network device sends a transmission path modification request to the second core network device.
  • step 205 reference may be made to the detailed description of the step 105 in the embodiment shown in FIG. 2, and details are not described herein again.
  • the second core network device receives the transmission path modification request sent by the first core network device.
  • the second core network device determines, according to the transmission path modification request, an IP address of the source terminal, an IP address of the target terminal, and a target bearer.
  • the second core network device determines an IP address of the source terminal, an IP address of the target terminal, and a target bearer according to the transmission path modification request.
  • the identification information of the to-be-switched service is different in the transmission path modification request, the specific process of determining the IP address of the source terminal, the IP address of the target terminal, and the target bearer is different.
  • the specific process of determining the IP address of the source terminal, the IP address of the target terminal, and the target bearer is different. For details, refer to the implementation shown in Figure 2. The detailed description of step 106 in the example will not be repeated here.
  • the second core network device may associate the determined IP address of the source terminal, the IP address of the target terminal, and the target bearer, so that the uplink data packet of the to-be-switched service is detected or When the data packet is downlinked, the transmission path can be modified in time.
  • the target bearer is used to obtain an uplink data packet transmitted on the target bearer;
  • the source terminal IP address is used to modify a source in an uplink data packet transmitted on the target bearer.
  • the IP address of the target terminal is used to modify the destination IP address in the downlink data packet of the to-be-switched service.
  • the second core network device sends a response message to the first core network device.
  • the response message is used to indicate that the second core network device can implement a transmission path modification of a data packet of the to-be-switched service.
  • the first core network device receives a response message sent by the second core network device.
  • the first core network device sends, to the source terminal, a response message that the handover of the service to be switched is completed.
  • the first core network device After the first core network device receives the response message sent by the second core network device, the first core network device sends a response message to the source terminal to complete the handover of the service to facilitate the The source terminal prompts the user to transmit a data packet about the to-be-switched service through the target terminal.
  • the second core network device receives an uplink data packet transmitted on the target bearer.
  • the uplink data packet transmitted by the second core network device and transmitted on the target bearer is sent by the target terminal after the handover of the to-be-switched service is completed.
  • the second core network device sets a source IP address in the uplink data packet to an IP address of the source terminal.
  • the to-be-switched service is the voice service between the terminal A and the terminal C.
  • the source IP address carried by the uplink data packet sent by the terminal B is the IP address of the terminal B.
  • the destination IP address is the IP address of terminal C.
  • the second core network device modifies the source IP address of the uplink data packet from the IP address of the terminal B to the IP address of the terminal A, so that the terminal C receives the uplink.
  • the data packet is considered to be sent by the terminal A, so that the terminal C can also identify that the uplink data packet of the to-be-switched service is sent by the terminal B, that is, the service to be switched is from the terminal A to the terminal B.
  • the switching has no effect on the terminal C, thereby ensuring the continuity of the service transmission to be switched.
  • the second core network device obtains a downlink data packet of the to-be-switched service that is sent to the source terminal, and sets a destination IP address in the downlink data packet to an IP address of the target terminal.
  • the source IP address carried by the downlink data packet sent by the terminal C to the terminal B is the IP address of the terminal C
  • the destination IP address is the IP address of the terminal A.
  • the second core network device obtains the IP quintuple information in the downlink data packet when receiving the downlink data packet, and matches the downlink TFT according to the IP quintuple information in the downlink data packet, and if the downlink TFT is detected, The TFT of the service to be switched sets the destination IP address in the downlink data packet to the IP address of the target terminal.
  • the identification information of the service to be switched corresponding to the four cases is as follows:
  • the identification information of the to-be-switched service is the IP address of the source terminal
  • the service to be switched is the service indicated by all the service type identifiers that the source terminal can support, and then the to-be-switched service
  • the TFT of the switching service is a TFT of all services in the source terminal.
  • the to-be-switched service is a service for transmitting a data packet by using the bearer indicated by the source bearer identifier in the source terminal, and further
  • the TFT of the service to be switched is a TFT that performs a service of transmitting a data packet by using a bearer indicated by the source bearer identifier.
  • the second core network device may directly determine the TFT of the service to be switched.
  • the second core network device detects that the TFT corresponding to the source bearer identifier is The service flow template of the service to be switched, or the second core network device determines that the bearer identifier corresponding to the service flow template of the to-be-switched service is the source bearer identifier, and the second core network device determines The source bearer identifier is the same as the service indicated by the service flow template of the to-be-switched service, and may directly determine the TFT of the service to be switched; otherwise, the second core network device determines the source bearer identifier and the service flow of the to-be-switched service.
  • the services indicated by the template are different, and the TFTs corresponding to the source bearer identifier and the service flow template carried in the transport path modification request are all determined by the TFTs to be switched.
  • the second core network device sends the modified downlink data packet to the target terminal by using the target bearer.
  • the second core network device sends the modified downlink data packet to the target terminal by using the target bearer.
  • the source terminal is switched in the service
  • the identifier of the target terminal carried in the request may be determined in two manners, and the source terminal is determined before performing the service switching request to the first core network device in step 201.
  • FIG. 6 is a schematic flowchart of a method for determining a target terminal by a source terminal according to an embodiment of the present invention. As shown in FIG. 6, the flowchart includes steps 301 to 304.
  • the source terminal sends an acquisition request to the first core network device, where the acquisition request carries an identifier of the source terminal.
  • the obtaining request carries an identifier of the source terminal.
  • the obtaining request is used to acquire the identifier of the at least one terminal from the first core network device, where the user corresponding to the identifier of each terminal of the at least one terminal and the user corresponding to the identifier of the source terminal are the same.
  • the first core network device receives an acquisition request sent by the source terminal.
  • the first core network device acquires an identifier of the at least one terminal according to the obtaining request.
  • the first core network device After receiving the acquisition request, the first core network device obtains the identifier of the source terminal, and then obtains the identifier of the multiple terminals corresponding to the same user according to the identifier of the source terminal according to the identifier of the source terminal.
  • the first core network device sends an identifier of the at least one terminal to the source terminal.
  • the identifier of the at least one terminal is used by the source terminal to determine a target terminal.
  • the source terminal receives the identifier of the at least one terminal sent by the first core network device.
  • the source terminal determines the target terminal according to the identifier of the at least one terminal.
  • the source terminal may select one of the identifiers of the at least one terminal as the identifier of the target terminal, and determine the terminal indicated by the identifier of the target terminal as the target terminal.
  • step 303a may also be performed.
  • the first core network device sends the indication information to the source terminal, where the indication information is used to indicate whether the at least one terminal supports the service indicated by the service type identifier.
  • the source terminal receives the indication information sent by the first core network device.
  • the step 304 may specifically include:
  • the terminal determines, by the source terminal, the terminal that supports the service indicated by the service type identifier in the terminal indicated by the identifier of the at least one terminal, according to the indication information, as the target terminal.
  • the end of the source The terminal selects, from the at least one terminal identifier, a terminal that supports the service indicated by the service type identifier as the target terminal.
  • the premise that the first core network device sends the indication information is that the source terminal carries the service type identifier of the to-be-switched service in the sent request, so that the first core network device can feed back at least one terminal.
  • the indication information of the service indicated by the service type identifier is supported.
  • FIG. 7 is a schematic flowchart of another method for determining a target terminal by a source terminal according to an embodiment of the present invention. As shown in FIG. 7, the flowchart includes steps 401 and 402.
  • the source terminal acquires an identifier of at least one terminal.
  • the at least one terminal is a terminal that establishes a communication connection with the source terminal, and the communication connection includes at least one of a D2D connection, a Bluetooth connection, and a WIFI connection, where the source terminal acquires each through the established communication connection.
  • the identifier of the terminal, and the user corresponding to the identifier of each terminal in the at least one terminal that is finally determined is the same as the user corresponding to the identifier of the source terminal.
  • the source terminal determines the target terminal according to the identifier of the at least one terminal.
  • the source terminal may select one of the identifiers of the at least one terminal as the identifier of the target terminal, and determine the terminal indicated by the identifier of the target terminal as the target terminal.
  • step 401a may also be performed.
  • the source terminal determines a service type identifier of the service to be switched, and obtains, by the at least one terminal, indication information of whether the terminal supports the service indicated by the service type identifier.
  • step 402 may specifically include:
  • the specific manner may be that the source terminal selects, from the at least one terminal identifier, a terminal that supports the service indicated by the service type identifier as the target terminal.
  • whether the terminal supports the service indicated by the service type identifier may be represented by an activation state and a deactivation state, where the terminal indicates the service type identifier
  • the terminal indicates the service type identifier
  • the terminal When the service is in an active state, the terminal supports the service indicated by the service type identifier, and when the terminal indicates that the service indicated by the service type identifier is in a deactivated state, the terminal does not support the service.
  • the type identifies the business indicated.
  • the first core network device may save an activation state or a deactivation state of each terminal identifier and various service type identifiers, to The first core network device is configured to directly generate indication information about whether the terminal supports the service indicated by the service type identifier.
  • the first core network device receives the service switching request of the to-be-switched service of the source terminal, and obtains the identification information of the to-be-switched service of the source terminal according to the service switching request, and determines the service to be switched. And the destination terminal identifier is allocated to the target terminal, and finally the transmission path of the data packet for modifying the to-be-switched service is sent to the second core network device, so that the transmission path modification of the service to be switched by the second core network device implements the service to be switched. Switching, and realizing the service switching function between multiple terminals, and ensuring the continuity of service transmission, thereby improving the convenience and intelligence of the terminal.
  • FIG. 8 is a schematic flowchart of another service switching method according to an embodiment of the present invention.
  • the service switching method in the embodiment of the present invention includes steps 701 to 715.
  • the service switching request in the embodiment of the present invention is initiated by the target terminal, and the switched service to be switched is the service in the source terminal, that is, the source terminal and the second core network before the to-be-switched service is switched.
  • the data flow for the to-be-switched service can be transmitted between the devices. For details about the switching process, refer to the following details.
  • the target terminal acquires an identifier of the at least one terminal.
  • the at least one terminal is a terminal that establishes a communication connection with the target terminal, and the communication connection includes at least one of a D2D connection, a Bluetooth connection, and a WIFI connection, where the target terminal acquires each through the established communication connection.
  • the identifier of the terminal, and the user corresponding to the identifier of each terminal in the at least one terminal that is finally determined is the same as the user corresponding to the identifier of the source terminal.
  • the identifier of the terminal involved in the embodiment of the present invention may be an IMSI or a GUTI of the terminal, where the GUTI is used in the mobile network, and the private parameters of the terminal such as the IMSI may be reduced to be exposed in the network transmission, thereby avoiding direct Deliver the security risks posed by the IMSI logo.
  • Both GUTI and IMSI can be used to uniquely identify a terminal.
  • the target terminal determines the source terminal according to the identifier of the at least one terminal.
  • the target terminal may select one of the identifiers of the at least one terminal as the identifier of the source terminal, and determine the terminal indicated by the identifier of the source terminal as the source terminal.
  • step 702 is further performed before the step 703 is performed by the template terminal.
  • the target terminal determines a service type identifier of the service to be switched, to the at least one terminal. And obtaining, by the terminal, whether the terminal supports the indication information of the service indicated by the service type identifier.
  • the step 703 may specifically include:
  • the target terminal determines, by the target terminal, the terminal that supports the service indicated by the service type identifier in the terminal indicated by the identifier of the at least one terminal, according to the indication information, as the source terminal.
  • the specific manner is that the target terminal selects, from the at least one terminal identifier, a terminal that supports the service indicated by the service type identifier as the target terminal.
  • the target terminal may further obtain the session control information of the to-be-switched service from the source terminal, where the session control information is used to indicate that the session of the to-be-switched service is managed.
  • the session control information may include, but is not limited to, at least one of a calling identifier, a called identifier, a media format (such as video, voice), and an encoding mode (video/audio encoding).
  • the service type identifiers involved in the embodiments of the present invention are identifiers for distinguishing various types of services, and the services may include, but are not limited to, voice, video, and packet data services.
  • the target terminal sends a service switching request to the first core network device.
  • the service switching request carries an identifier of the source terminal and an identifier of the target terminal.
  • the service switching request may further include a source bearer identifier and/or a service flow template TFT of the to-be-switched service.
  • the service switching request may further carry the service type identifier of the to-be-switched service.
  • the first core network device receives a service switching request sent by the target terminal.
  • the first core network device acquires the identification information of the to-be-switched service of the source terminal according to the service switching request.
  • step 104 For details, refer to the detailed description of step 104 in the embodiment shown in FIG. 2, and details are not described herein again.
  • the target terminal after performing step 703, further includes: the target terminal acquiring, according to the service type identifier of the to-be-switched service, the source terminal The source bearer identifier of the handover service is described, so that the source bearer identifier can be carried in the service switch request.
  • the method further includes: the target terminal acquiring, according to the service type identifier of the to-be-switched service, the source terminal
  • the service flow template of the service to be switched is configured to carry the service flow template of the service to be switched in the service switching request.
  • the target terminal after performing step 703, further includes: the target terminal according to the service type identifier of the to-be-switched service, The source terminal obtains the source bearer identifier and the service flow template of the to-be-switched service, so that the source bearer identifier and the service flow template of the to-be-switched service are carried in the service switch request.
  • the first core network device determines, according to the service switching request, the target terminal of the to-be-switched service.
  • the solution for determining the target terminal by the first core network device may be classified into two types according to the identifier of the target terminal in the to-be-switched service request:
  • the first core network device determines the terminal indicated by the identifier of the target terminal as the target terminal.
  • the first core network device determines the terminal indicated by the identifier of the target terminal as the target terminal. Specifically, the first core network device authenticates the identifier of the target terminal, and if the target terminal and the source terminal correspond to the same user, the first core network device authorizes the identifier indication of the target terminal.
  • the terminal is determined to be the target terminal to which the to-be-switched service is to be handed over; if the target terminal and the source terminal correspond to different users, the first core network device does not switch the to-be-switched service.
  • the first core network device allocates a target bearer identifier to the target terminal.
  • step 104 For details, refer to the detailed description of step 104 in the embodiment shown in FIG. 2, and details are not described herein again.
  • the first core network device sends a transmission path modification request to the second core network device.
  • step 105 For details, refer to the detailed description of step 105 in the embodiment shown in FIG. 2, and details are not described herein again.
  • the second core network device receives the transmission path modification request sent by the first core network device.
  • the second core network device determines, according to the transmission path modification request, an IP address of the source terminal, an IP address of the target terminal, and a target bearer.
  • step 206 For details, refer to the detailed description of step 206 in the embodiment shown in FIG. 5, and details are not described herein again.
  • the second core network device sends a response message to the first core network device.
  • the response message is used to indicate that the second core network device can implement a transmission path modification of a data packet of the to-be-switched service.
  • the first core network device receives a response message sent by the second core network device.
  • the first core network device sends, to the target terminal, a response message that the handover of the service to be switched is completed.
  • the first core network device After the first core network device receives the response message sent by the second core network device, the first core network device sends a response message to the target terminal to complete the handover of the service to facilitate the
  • the target terminal indicates to the user that the data packet about the to-be-switched service can be transmitted through the target terminal.
  • the second core network device receives an uplink data packet transmitted on the target bearer.
  • the second core network device sets a source IP address in the uplink data packet to an IP address of the source terminal.
  • the second core network device obtains a downlink data packet of the to-be-switched service that is sent to the source terminal, and sets a destination IP address in the downlink data packet to an IP address of the target terminal.
  • the second core network device sends the modified downlink data packet to the target terminal by using the target bearer.
  • step 712 For details, refer to the detailed description of the corresponding steps in the embodiment shown in FIG. 5 in step 712 to step 715, and details are not described herein again.
  • the first core network device receives the service switching request of the to-be-switched service of the switching source terminal that is sent by the target terminal, obtains the identification information of the to-be-switched service of the source terminal according to the service switching request, and determines the service to be switched. And the destination terminal identifier is allocated to the target terminal, and finally the transmission path of the data packet for modifying the to-be-switched service is sent to the second core network device, so that the transmission path modification of the service to be switched by the second core network device implements the service to be switched. Switching, and realizing the service switching function between multiple terminals, and ensuring the continuity of service transmission, improving the convenience and intelligence of the terminal.
  • each device such as the first core network device, the second core network device, the first terminal, etc., in order to implement the above functions, includes corresponding hardware structures and/or software modules for performing the respective functions.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Now. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the embodiments of the present invention may perform functional unit division on the first core network device, the second core network device, the first terminal, and the like according to the foregoing method.
  • each functional unit may be divided according to each function, or two or two may be divided. More than one function is integrated in one processing unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 9 is a schematic diagram of a modularization of a first core network device according to an embodiment of the present invention.
  • the first core network device in the embodiment of the present invention may be the first core network device provided in any of the embodiments shown in FIG. 2-8.
  • the first core network device 1 of the embodiment of the present invention may include: a receiving unit 11, an obtaining unit 12, a determining unit 13, an allocating unit 14, and a transmitting unit 15.
  • the receiving unit 11 is configured to receive a service switching request sent by the first terminal, where the service switching request is used to request to switch the to-be-switched service of the source terminal, where the service switching request carries the identifier of the source terminal.
  • the obtaining unit 12 is configured to acquire, according to the service switching request received by the receiving unit 11, the identification information of the to-be-switched service of the source terminal.
  • the determining unit 13 is configured to determine the target terminal of the to-be-switched service according to the service switching request received by the receiving unit 11.
  • the allocating unit 14 is configured to allocate a target bearer identifier to the target terminal determined by the determining unit 13.
  • the sending unit 15 is configured to send a transmission path modification request to the second core network device, where the transmission path modification request carries the identification information of the to-be-switched service, the identifier of the target terminal, and the target bearer identifier, where the transmission The path modification request is used to request the second core network device to modify a transmission path of the data packet of the to-be-switched service.
  • the first terminal may be the source terminal, or may be a target terminal to which the to-be-switched service is to be switched.
  • the service switching request may further carry an identifier of the target terminal.
  • the service switching request may further include a source bearer identifier and/or a service flow template of the to-be-switched service.
  • the service switching request may further carry the service type identifier of the to-be-switched service.
  • the obtaining unit 11 determines that the identification information of the to-be-switched service is different, where the to-be-switched service request carries or does not carry the source bearer identifier and/or the service flow template of the to-be-switched service.
  • the obtaining unit 11 is specifically configured to:
  • the service switching request does not carry the source bearer identifier and the service flow template of the to-be-switched service, obtain an IP address of the source terminal according to the identifier of the source terminal, and determine an IP address of the source terminal. Identification information of the service to be switched; or
  • the service switching request further carries the source bearer identifier, determining the source bearer identifier as the identification information of the to-be-switched service;
  • the service switching request further carries the service flow template of the to-be-switched service, determining the service flow template as the identification information of the to-be-switched service;
  • the service switching request further carries the source bearer identifier and the service flow template of the to-be-switched service, detecting whether the service flow template corresponding to the source bearer identifier is the same as the service flow template of the to-be-switched service; or Whether the bearer identifier corresponding to the service flow template of the to-be-switched service is the same as the source bearer identifier; if the same, determining the source bearer identifier and/or the service flow template as the identification information of the to-be-switched service Or, if not, determining the source bearer identifier and the service flow template as the identification information of the to-be-switched service.
  • the source bearer identifier is used to indicate that the source terminal transmits the bearer of the to-be-switched service, and the bearer indicated by the source bearer identifier includes a radio bearer between the source terminal and the base station, the base station, and a Data bearer between two core network devices.
  • the determining unit 13 determines that the manner of the target terminal is different, and may be specifically divided into two manners.
  • the first mode is: if the service switching request does not carry the identifier of the target terminal, refer to FIG. 10, which is a schematic diagram of a modularization of the determining unit, where the determining unit 13 includes the identifier acquiring unit 131 and the terminal. The unit 132 is determined.
  • the identifier obtaining unit 131 is configured to acquire an identifier of the at least one terminal, where the user corresponding to the identifier of each terminal of the at least one terminal is the same as the user corresponding to the source terminal.
  • the terminal determining unit 132 is configured to use the at least one terminal acquired by the identifier acquiring unit 131.
  • the identifier identifies the target terminal.
  • the terminal determining unit 132 is specifically configured to support the service type in the terminal indicated by the identifier of the at least one terminal acquired by the identifier acquiring unit 131.
  • a terminal that identifies the indicated service is determined to be the target terminal.
  • the second method is: the determining unit 13 is specifically configured to: if the service switching request carries the identifier of the target terminal, determine the terminal indicated by the identifier of the target terminal as the target terminal; or if the target terminal And corresponding to the source terminal, the terminal indicated by the identifier of the target terminal is determined as the target terminal.
  • the service switching request must carry the identifier of the target terminal, and the first core network device performs the determination according to the determining unit 13 in the second manner.
  • the service switching request may carry the identifier of the target terminal, or may not carry the identifier of the target terminal, and the first core network device may determine according to the manner in the corresponding manner.
  • Unit 13 performs.
  • the receiving unit 11 is further configured to: if the first terminal is a source terminal, and the service switching request carries the identifier of the target terminal, receive the acquiring request sent by the source terminal, where Acquiring the identifier of the source terminal; the obtaining unit 12 is further configured to acquire the identifier of the at least one terminal according to the obtaining request received by the receiving unit 11, where the user corresponding to each terminal in the at least one terminal The source terminal corresponds to the same user; the sending unit 15 is further configured to send the identifier of the at least one terminal acquired by the acquiring unit 12 to the source terminal, where the identifier of the at least one terminal is used by the source terminal to determine the target terminal.
  • the sending unit 15 is further configured to send the indication information to the source terminal, where the indication information is used to indicate whether the at least one terminal supports the The service indicated by the service type identifier.
  • the allocating unit 14 is configured to: obtain, according to the identification information of the to-be-switched service, a configuration parameter of a bearer that transmits the to-be-switched service in a context of the source terminal, where the configuration parameter includes an access point name.
  • APN a public data network PDN gateway address, and a quality of service Qos parameter
  • detecting whether there is a target bearer that satisfies the configuration parameter in the established bearer of the target terminal if not, according to the configuration parameter, the target The terminal establishes a target bearer and allocates a target bearer identifier; or, if yes, obtains a target bearer identifier used to indicate the target bearer;
  • the target bearer is used to transmit the to-be-switched service, and the target bearer identifier is used to indicate the target bearer, where the target bearer includes a radio bearer between the target terminal and a base station, the base station, and a Data bearer between two core network devices.
  • first core network device shown in the embodiment of the present invention may be used to perform the action or the step of the first core network device in any of the embodiments shown in FIG. 2 to FIG.
  • first core network device shown in the embodiment of the present invention may be used to perform the action or the step of the first core network device in any of the embodiments shown in FIG. 2 to FIG.
  • functional units and technical effects refer to the detailed description of the corresponding method embodiments, and no further details are provided herein.
  • the first core network device in the embodiment shown in FIG. 9 can be implemented by the first core network device shown in FIG.
  • FIG. 11 is a schematic structural diagram of a first core network device according to an embodiment of the present invention.
  • the first core network device 1000 shown in FIG. 11 includes: a processor 1001 and a transceiver 1004.
  • the processor 1001 is connected to the transceiver 1004, such as through the bus 1002.
  • the first core network device 1000 may further include a memory 1003. It should be noted that, in the actual application, the transceiver 1004 is not limited to two, and the structure of the first core network device 1000 does not constitute a limitation on the embodiment of the present invention.
  • the processor 1001 is used in the embodiment of the present invention to implement the functions of the obtaining unit 12, the determining unit 13, and the allocating unit 14 shown in FIG.
  • the transceiver 1004 includes a receiver and a transmitter, and the transceiver 1004 is applied to the embodiment of the present invention for implementing the functions of the receiving unit 11 and the transmitting unit 15 shown in FIG.
  • the processor 1001 may be a central processing unit (CPU), a general-purpose processor, a digital signal processing (DSP), an application specific integrated circuit (ASIC), and a field programmable logic gate array (Field). - Programmable Gate Array, FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor 1001 may also be a combination of computing functions, such as one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • Bus 1002 can include a path for communicating information between the components described above.
  • the bus 1002 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 1002 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one is used in Figure 11. Thick lines indicate, but do not mean that there is only one bus or one type of bus.
  • the memory 1003 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • CD-ROM Compact Disc Read-Only Memory
  • CD-ROM Compact Disc Read-Only Memory
  • disc storage device including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.
  • the memory 1003 is configured to store application code for executing the solution of the present invention, and is controlled by the processor 1001 for execution.
  • the processor 1001 is configured to execute the application code stored in the memory 1003 to implement the actions of the first core network device provided by any of the embodiments shown in FIG. 2-8.
  • a computer storage medium is further provided for storing computer software instructions used by the first core network device, which includes a program designed to execute the foregoing aspect for the first core network device.
  • FIG. 12 is a schematic diagram of a modularization of a second core network device according to an embodiment of the present invention.
  • the second core network device in the embodiment of the present invention may be the second core network device provided in any of the embodiments shown in FIG. 2-8.
  • the second core network device 2 of the embodiment of the present invention may include: a receiving unit 21 and a modifying unit 22.
  • the receiving unit 21 is configured to receive a transmission path modification request sent by the first core network device, where the transmission path modification request carries the identification information of the to-be-switched service, the identifier of the target terminal, and the target bearer identifier.
  • the modifying unit 22 is configured to modify the transmission path of the data packet of the to-be-switched service according to the identification information of the to-be-switched service, the identifier of the target terminal, and the target bearer identifier received by the receiving unit 21.
  • the modification unit 22 can be divided into the following four cases:
  • the identification information of the to-be-switched service is an IP address of the source terminal.
  • the modifying unit 22 is specifically configured to determine a target bearer according to the identifier of the target terminal and the target bearer identifier, and receive an uplink data packet transmitted on the target bearer for modifying a transmission path of the uplink data packet, and
  • the source IP address in the uplink data packet is set to the IP address of the source terminal; for modifying the transmission path of the downlink data packet, obtaining an IP address of the target terminal according to the identifier of the target terminal, according to the Obtaining, by the IP address of the source terminal, a downlink data packet of the to-be-switched service sent to the source terminal, setting a destination IP address in the downlink data packet to an IP address of the target terminal, and passing the target The bearer is sent to the target terminal.
  • the identification information of the to-be-switched service is a source bearer identifier of the source terminal
  • the transmission path modification request further includes an identifier of the source terminal
  • the modifying unit 22 is specifically configured to determine an IP address of the source terminal according to the identifier of the source terminal, determine a target bearer according to the identifier of the target terminal and the target bearer identifier, and modify a transmission path of the uplink data packet.
  • the identification information of the to-be-switched service is a service flow template of the to-be-switched service.
  • the modifying unit 22 is specifically configured to determine the target bearer according to the identifier of the target terminal and the target bearer identifier. For modifying the transmission path of the uplink data packet, obtain the source according to the service flow template of the to-be-switched service.
  • the IP address of the terminal receives the uplink data packet transmitted on the target bearer, and sets the source IP address in the uplink data packet to the IP address of the source terminal; for modifying the transmission path of the downlink data packet, Obtaining, according to the identifier of the target terminal, an IP address of the target terminal, obtaining a downlink data packet of the to-be-switched service according to the service flow template of the to-be-switched service, and setting a destination IP address in the downlink data packet And being set to an IP address of the target terminal, and sent to the target terminal by using the target bearer.
  • the identification information of the to-be-switched service is a source bearer identifier of the source terminal and the to-be-identified Switching a service flow template of the service; the transmission path modification request further includes an identifier of the source terminal.
  • the modifying unit 22 is specifically configured to determine a target bearer according to the identifier of the target terminal and the target bearer identifier, and determine an IP address of the source terminal according to the identifier of the source terminal or the service flow template of the to-be-switched service.
  • For modifying the transmission path of the uplink data packet receiving an uplink data packet transmitted on the target bearer, and setting a source IP address in the uplink data packet to an IP address of the source terminal; Obtaining, in the case of the transmission path of the packet, the IP address of the target terminal according to the identifier of the target terminal, obtaining a downlink data packet of the to-be-switched service according to the service flow template of the to-be-switched service, and performing the downlink
  • the destination IP address in the data packet is set to the IP address of the target terminal, and is sent to the target terminal by using the target bearer; and/or, according to the identifier of the target terminal, obtaining the IP address of the target terminal.
  • the second core network device shown in the embodiment of the present invention may be used to perform the actions or steps of the second core network device in any of the embodiments shown in FIG. 2 to FIG.
  • the functional units and technical effects refer to the detailed description of the corresponding method embodiments, and no further details are provided herein.
  • the second core network device in the embodiment shown in FIG. 12 can be implemented by the second core network device shown in FIG.
  • FIG. 13 is a schematic structural diagram of a second core network device according to an embodiment of the present invention.
  • the second core network device 2000 shown in FIG. 13 includes: a processor 2001 and a transceiver 2004.
  • the processor 2001 is connected to the transceiver 2004, such as through the bus 2002.
  • the second core network device 2000 may further include a memory 2003.
  • the transceiver 2004 is not limited to two, and the structure of the second core network device 2000 does not constitute a limitation on the embodiment of the present invention.
  • the processor 2001 is applied to the embodiment of the present invention to implement the function of the modifying unit 22 shown in FIG.
  • the transceiver 2004 includes a receiver and a transmitter, and the transceiver 2004 is used in the embodiment of the present invention to implement the functions of the receiving unit 21 shown in FIG.
  • Processor 2001 can be a CPU, a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It can be realized or executed The various exemplary logical blocks, modules and circuits described in connection with the present disclosure are incorporated.
  • the processor 2001 can also be a combination of computing functions, such as one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • Bus 2002 can include a path for communicating information between the above components.
  • the bus 2002 can be a PCI bus or an EISA bus or the like.
  • the bus 2002 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 13, but it does not mean that there is only one bus or one type of bus.
  • the memory 2003 can be a ROM or other type of static storage device that can store static information and instructions, RAM or other types of dynamic storage devices that can store information and instructions, or can be an EEPROM, CD-ROM or other optical disk storage, optical disk. Storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other medium accessed by the computer, but is not limited to this.
  • the memory 2003 is used to store application code for executing the solution of the present invention, and is controlled by the processor 2001 for execution.
  • the processor 2001 is configured to execute the application code stored in the memory 2003 to implement the actions of the second core network device in any of the embodiments shown in FIGS. 2 to 8.
  • a computer storage medium for storing computer software instructions used by the second core network device, which includes a program designed to execute the foregoing aspect for the second core network device.
  • FIG. 14 is a schematic diagram of a modularization of a first terminal according to an embodiment of the present invention.
  • the first terminal may be the first terminal provided by any one of the embodiments in FIG. 2-8.
  • the first terminal may be a source terminal.
  • the first terminal 3 of the embodiment of the present invention may include: a sending unit 31.
  • the first terminal 3 may further include a receiving unit 32 and a first determining unit 33.
  • the sending unit 13 is configured to send a service switching request to the first core network device, where the service switching request is used to request to switch the to-be-switched service of the source terminal, where the service switching request carries the identifier of the source terminal.
  • the service switching request further carries an identifier of the target terminal.
  • the service switching request may further carry a source bearer identifier and/or the to-be-switched service.
  • the source bearer identifier is used to indicate that the source terminal transmits the bearer of the to-be-switched service, and the bearer indicated by the source bearer identifier includes a radio bearer between the source terminal and the base station, and the base station Data bearer with the second core network device.
  • the service switching request further carries a service type identifier.
  • the service switching request may further include session control information of the to-be-switched service.
  • the source terminal further needs to determine the identifier of the target terminal, such that the first terminal further includes the receiving unit 32 and the first determining unit 33.
  • the sending unit 13 is further configured to send an acquisition request to the first core network device, where the obtaining request carries an identifier of the source terminal, where the obtaining request is used to acquire at least one of the first core network devices.
  • the identifier of the terminal, the user corresponding to the identifier of each terminal in the at least one terminal is the same as the user corresponding to the identifier of the source terminal.
  • the receiving unit 32 is configured to receive an identifier of the at least one terminal sent by the first core network device.
  • the first determining unit 33 is configured to determine the target terminal according to the identifier of the at least one terminal received by the receiving unit 32.
  • the obtaining request further carries a service type identifier of the to-be-switched service
  • the receiving unit 32 is further configured to receive the indication information that is sent by the first core network device, where the indication information is used to indicate whether the at least one terminal is Supporting the service indicated by the service type identifier; the first determining unit 32 is specifically configured to: according to the indication information received by the receiving unit 32, support the service type identifier in the terminal indicated by the identifier of the at least one terminal The terminal of the indicated service is determined as the target terminal.
  • FIG. 15 is a schematic diagram of a modularization of a first terminal according to an embodiment of the present invention.
  • the first terminal in the embodiment of the present invention may be the first terminal provided in any one of the embodiments of FIG. 2-8.
  • the first terminal may be a source terminal.
  • the first terminal 3 of the embodiment of the present invention may include: a sending unit 31.
  • the first terminal 3 may further include a first obtaining unit 34 and a second determining unit 35.
  • the sending unit 13 is configured to send a service switching request to the first core network device, where the service switching request is used to request to switch the to-be-switched service of the source terminal, where the service switching request carries the identifier of the source terminal.
  • the service switching request further carries an identifier of the target terminal.
  • the service switching request may further include a source bearer identifier and/or a service flow template TFT of the to-be-switched service.
  • the source bearer identifier is used to indicate that the source terminal transmits the bearer of the to-be-switched service, and the bearer indicated by the source bearer identifier includes a radio bearer between the source terminal and the base station, and the base station Data bearer with the second core network device.
  • the service switching request further carries a service type identifier.
  • the service switching request may further include session control information of the to-be-switched service.
  • the source terminal further needs to determine the target terminal, so that the first terminal 3 may further include the first obtaining unit 34 and the second determining unit 35.
  • the first obtaining unit 34 is configured to acquire an identifier of the at least one terminal, where the user corresponding to the identifier of each terminal of the at least one terminal is the same as the user corresponding to the identifier of the source terminal, and the second determining unit 35 uses The target terminal is determined according to the identifier of the at least one terminal acquired by the first obtaining unit 34.
  • the first obtaining unit 34 is further configured to determine the service type identifier of the to-be-switched service, and obtain the indication information of whether the at least one terminal supports the service indicated by the service type identifier; the second determining unit 35 Specifically, the terminal that supports the service indicated by the service type identifier in the terminal indicated by the identifier of the at least one terminal is determined as the target terminal according to the indication information that is obtained by the first acquiring unit 34.
  • the at least one terminal is a terminal that establishes a communication connection with the source terminal; and the communication connection includes at least one of a device-to-device D2D connection, a Bluetooth connection, and a WIFI connection.
  • FIG. 16 is a schematic diagram of a modularization of a first terminal according to an embodiment of the present invention.
  • the first terminal in the embodiment of the present invention may be the first terminal provided in any one of the embodiments of FIG. 2-8.
  • the first terminal may be a target terminal.
  • the first terminal 3 of the embodiment of the present invention may include: a sending unit 31.
  • the first terminal 3 may further include a second obtaining unit 36 and a third determining unit 37.
  • the sending unit 31 is configured to send a service switching request to the first core network device, where the service switching request is used to request to switch the to-be-switched service of the source terminal, where the service switching request carries the identifier of the source terminal and the target terminal. logo.
  • the service switching request may further include a source bearer identifier and/or a service flow template TFT of the to-be-switched service.
  • the service switching request further carries a service type identifier.
  • the first terminal 3 may further include a second obtaining unit 36 and a third determining unit 37, because the service switching request carries the identifier of the source terminal, and the target terminal further needs to determine the source terminal.
  • the second obtaining unit 36 is configured to acquire an identifier of the at least one terminal, where the user corresponding to the identifier of each terminal of the at least one terminal is the same as the user corresponding to the identifier of the target terminal.
  • the third determining unit 37 is configured to determine the source terminal according to the identifier of the at least one terminal acquired by the second obtaining unit 36.
  • the second obtaining unit 36 is further configured to determine the service type identifier of the to-be-switched service, and obtain the indication information of whether the at least one terminal supports the service indicated by the service type identifier.
  • the third determining unit 37 is specifically configured to determine, according to the indication information that is obtained by the second acquiring unit 36, a terminal that supports the service indicated by the service type identifier in the terminal indicated by the identifier of the at least one terminal, as a source. terminal.
  • the second obtaining unit 36 is further configured to acquire the source bearer identifier of the to-be-switched service from the source terminal according to the service type identifier of the to-be-switched service. .
  • the second obtaining unit 36 is further configured to acquire the to-be-to-before the source terminal according to the service type identifier of the to-be-switched service. Switch the service flow template of the service.
  • the second obtaining unit 36 is further configured to: according to the service type identifier of the to-be-switched service, to the source terminal Obtaining a source bearer identifier and a service flow template of the to-be-switched service.
  • the source bearer identifier is used to indicate that the source terminal transmits the to-be-switched service.
  • the bearer indicated by the source bearer identifier includes a radio bearer between the source terminal and the base station, and a data bearer between the base station and the second core network device.
  • the at least one terminal is a terminal that establishes a communication connection with the target terminal;
  • the communication connection includes at least one of a D2D connection, a Bluetooth connection, and a WIFI connection.
  • the first terminal in the embodiment shown in FIG. 14 , FIG. 15 or FIG. 16 can be implemented by the first terminal shown in FIG. 17 , as shown in FIG. 17 , which is a schematic structural diagram of the first terminal according to an embodiment of the present invention.
  • the first terminal 3000 shown in FIG. 17 includes a power source 3001, a user interface 3002, a communication module 3003, a processor 3004, a display system 3005, a sensing system 3006, and an audio system 3007.
  • the structure of the first terminal shown in FIG. 17 does not constitute a limitation on the embodiment of the present invention.
  • the power supply 3001 provides power guarantee for implementing various functions of the first terminal 3000.
  • the user interface 3002 is used by the first terminal 3000 to connect with other devices or devices to implement communication or data transmission between the other devices or devices and the first terminal 3000.
  • the communication module 3003 is configured to implement communication or data transmission between the first terminal 3000 and a network side device such as a base station or a satellite, and is also used to implement communication or data transmission between the first terminal 3000 and other first terminals.
  • the processor 3004 can implement or perform various exemplary logical blocks, modules and circuits described in connection with the present disclosure.
  • Display system 3005 is used for output display of information and for receiving user input operations.
  • Sensing system 3006 includes various sensors, such as temperature sensors, distance sensors, and the like.
  • the audio system 3007 is used for the output of an audio signal.
  • the processor 3003 is configured to implement the functions of the first determining unit 33 in FIG. 14.
  • the communication module 3003 is configured to implement the functions of the receiving unit 32 and the sending unit 31;
  • the processor 3003 is configured to implement The functions of the first obtaining unit 34 and the second determining unit 35 in FIG. 15 , correspondingly, the communication module 3003 is configured to implement the function of the transmitting unit 31;
  • the processor 3003 is configured to implement the second obtaining unit 36 and the third determining in FIG. 16
  • the function of the unit 37 correspondingly, the communication module 3003 is used to implement the functions of the transmitting unit 31.
  • a computer storage medium for storing computer software instructions used by the first terminal, which includes a program designed to execute the foregoing aspect for the first terminal, to implement FIG. 2 to The action of the first terminal in any of the embodiments shown in FIG.
  • embodiments of the present invention can be provided as a method, apparatus (device), or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program is stored/distributed in a suitable medium, provided with other hardware or as part of the hardware, or in other distributed forms, such as over the Internet or other wired or wireless telecommunication systems.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

L'invention concerne un procédé de commutation de service et un dispositif associé. Le procédé comprend les étapes suivantes : recevoir, par un premier dispositif de réseau central, une demande de commutation de service transmise par un premier terminal, la demande de commutation de service étant utilisée pour demander de commuter un service à commuter d'un terminal source, et la demande de commutation de service portant l'identifiant du terminal source ; acquérir, selon la demande de commutation de service, les informations d'identification du service à commuter du terminal source ; déterminer, selon la demande de commutation de service, le terminal cible du service à commuter ; distribuer un identifiant de porteuse cible pour le terminal cible ; transmettre une demande de modification de trajet de transmission à un second dispositif de réseau central, la demande de modification de trajet de transmission transportant les informations d'identification du service à commuter, ainsi que l'identifiant du terminal cible et l'identifiant de porteuse cible, la demande de modification de trajet de transmission étant utilisée pour demander au second dispositif de réseau central de modifier le trajet de transmission des paquets de données du service à commuter. La présente invention peut réaliser une fonction de commutation de service entre une pluralité de terminaux, et peut assurer la continuité des transmissions de service, améliorant en outre la commodité et l'intelligence des terminaux.
PCT/CN2016/098440 2016-09-08 2016-09-08 Procédé de commutation de service et dispositif associé WO2018045533A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/098440 WO2018045533A1 (fr) 2016-09-08 2016-09-08 Procédé de commutation de service et dispositif associé

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/098440 WO2018045533A1 (fr) 2016-09-08 2016-09-08 Procédé de commutation de service et dispositif associé

Publications (1)

Publication Number Publication Date
WO2018045533A1 true WO2018045533A1 (fr) 2018-03-15

Family

ID=61562423

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/098440 WO2018045533A1 (fr) 2016-09-08 2016-09-08 Procédé de commutation de service et dispositif associé

Country Status (1)

Country Link
WO (1) WO2018045533A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114258102A (zh) * 2020-09-25 2022-03-29 维沃移动通信有限公司 传输业务数据的方法、装置、终端设备和网络设备
CN115243401A (zh) * 2021-04-22 2022-10-25 展讯通信(上海)有限公司 业务处理方法、装置、系统、可读取存储介质和电子设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005122651A (ja) * 2003-10-20 2005-05-12 Nippon Telegr & Teleph Corp <Ntt> サービス切り替えにおける認証方法およびこれを用いるユーザ端末切り替え方法
CN101052044A (zh) * 2007-05-18 2007-10-10 华为技术有限公司 一种ims中iptv流媒体业务实现方法、网络设备及终端设备
CN101557543A (zh) * 2008-04-10 2009-10-14 中兴通讯股份有限公司 一种实现设备间业务切换的系统及方法
CN102082770A (zh) * 2009-11-27 2011-06-01 中国移动通信集团天津有限公司 多媒体业务在不同终端间进行切换的方法及系统
CN103067403A (zh) * 2013-01-10 2013-04-24 中兴通讯股份有限公司 一种业务切换方法、系统及服务器

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005122651A (ja) * 2003-10-20 2005-05-12 Nippon Telegr & Teleph Corp <Ntt> サービス切り替えにおける認証方法およびこれを用いるユーザ端末切り替え方法
CN101052044A (zh) * 2007-05-18 2007-10-10 华为技术有限公司 一种ims中iptv流媒体业务实现方法、网络设备及终端设备
CN101557543A (zh) * 2008-04-10 2009-10-14 中兴通讯股份有限公司 一种实现设备间业务切换的系统及方法
CN102082770A (zh) * 2009-11-27 2011-06-01 中国移动通信集团天津有限公司 多媒体业务在不同终端间进行切换的方法及系统
CN103067403A (zh) * 2013-01-10 2013-04-24 中兴通讯股份有限公司 一种业务切换方法、系统及服务器

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114258102A (zh) * 2020-09-25 2022-03-29 维沃移动通信有限公司 传输业务数据的方法、装置、终端设备和网络设备
CN115243401A (zh) * 2021-04-22 2022-10-25 展讯通信(上海)有限公司 业务处理方法、装置、系统、可读取存储介质和电子设备

Similar Documents

Publication Publication Date Title
US10674363B2 (en) Access control method, user equipment, and network device
US9450667B2 (en) Method for device to device communication and base station and user equipment using the same
US9554406B2 (en) Method for device to device communication and control node using the same
US10750418B2 (en) SDN based connectionless architecture with dual connectivity and carrier aggregation
WO2018090491A1 (fr) Procédé d&#39;indication et dispositif associé
WO2018006215A1 (fr) Procédé, appareil, et système de gestion d&#39;état d&#39;imsi de dispositif terminal
US10165472B2 (en) Systems and methods for managing circuit switched fallback calls
US9949198B2 (en) Long term evolution communication system to perform a mobility management entity reselection
US9713176B2 (en) Telecommunication method and telecommunication system
KR102461898B1 (ko) 음성 통화 확립
US11283770B2 (en) Deriving a security key for relayed communication
KR101669165B1 (ko) 사설망 서비스 제공방법 및 이를 위한 이동성관리장치
WO2016201796A1 (fr) Procédé et système pour la réalisation d&#39;enregistrement de réseau privé, dispositifs d&#39;élément de réseau et support de stockage informatique
US10750357B2 (en) Data transmission method and apparatus, and related device
WO2018027799A1 (fr) Procédé, dispositif et système de communication de transmission d&#39;informations
WO2020011134A1 (fr) Procédé et appareil de transmission de données
WO2018045533A1 (fr) Procédé de commutation de service et dispositif associé
CN111557102B (zh) 信息传输方法、装置、通信设备及存储介质
KR101805637B1 (ko) VoLTE 응급통화 연결 방법 및 이를 위한 싱글 LTE 단말
US10499443B2 (en) Data transmission method, related device, and system
US10129920B2 (en) Control apparatus, radio communication device, and method therefor
CN107294867B (zh) 一种用以促成点对点通信的方法及其相关装置
WO2018176372A1 (fr) Procédé de communication, appareil terminal et appareil de réseau d&#39;accès
TW201820917A (zh) 資料傳輸的方法和設備
CN103856931A (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: 16915468

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

Country of ref document: EP

Kind code of ref document: A1