WO2019149029A1

WO2019149029A1 - Service equipment switching method, and device for same

Info

Publication number: WO2019149029A1
Application number: PCT/CN2019/070320
Authority: WO
Inventors: 周凯; 何国洲; 卢金华
Original assignee: 华为技术有限公司
Priority date: 2018-01-31
Filing date: 2019-01-04
Publication date: 2019-08-08
Also published as: CN110099430A; CN110099430B

Abstract

Embodiments of the present application provide a service equipment switching method and a device for the same. The method comprises the following steps: if a second service equipment unit is faulty, a first service equipment unit determining, according to a user equipment migration policy, a user equipment unit to be migrated from user equipment units connected to the second service equipment unit; and the first service equipment unit notifying the user equipment unit to be migrated to register with the first service equipment unit. The embodiments of the present application do not require a user equipment unit to detect whether a service equipment unit is operating normally or to trigger switching of service equipment units, thereby reducing power consumption of a user equipment unit.

Description

Service device switching method and device thereof

This application claims the priority of the Chinese patent application filed on January 31, 2018 by the State Intellectual Property Office of China, application number 201810101111.X, and the invention name is "a service device switching method and its device". The citations are incorporated herein by reference.

Technical field

The embodiment of the present invention relates to the technical field of the Internet of Things, and particularly to a service device switching method and device thereof.

Background technique

The disaster recovery system refers to the establishment of two or more sets of functionally identical internet technology (IT) systems in remote locations, where health monitoring and function switching can be performed between each other. When the work is stopped, such as a fire, earthquake, etc., the entire application system can be switched to another location, so that the system function can continue to work normally. The disaster recovery system of the narrowband internet of things (NB-IoT) scenario can be switched to the standby service device to establish the user equipment and standby in the event that the primary service device that is linked with the user equipment fails. A connection between service devices to ensure data interaction between the user device and the service device.

At present, the user equipment configures the internet protocol (IP) address of the primary service device and the backup service device before leaving the factory, and configures the user equipment to use the constrained application protocol (CoAP) confirmation ( The confirmable, CON) message mode performs data interaction with the service device, and the data interaction may include user equipment registration, data reporting, and the like. When the data is reported by the user equipment, the data is first reported to the evolved packet core (EPC), and the EPC reports the data to the primary service device. In this process, if the primary service device is working normally, the response message is fed back to the EPC, and the EPC feeds back the response message to the user equipment when receiving the response message, and the user equipment receives the response message of the EPC feedback. , to determine that the main service device is working properly. If the user equipment does not receive the response message of the EPC feedback within the specified time, the user equipment retransmits the message. If the user equipment fails to resend the preset number of times, the data is reported to the backup service device, that is, the primary service device is switched to the standby service device.

According to the above process, if the user equipment does not receive the response message of the EPC feedback, the user equipment retransmits multiple times to detect whether the primary service device works normally, and if the primary service device fails, the user equipment triggers the slave device. The service device switches to the alternate service device, which increases the additional power consumption of the user device.

Summary of the invention

The technical problem to be solved by the embodiments of the present application is to provide a service device switching method and a device thereof, which can reduce the power consumption of the user equipment without triggering the switching of the service device by the user equipment.

A first aspect of the embodiments of the present application provides a service device switching method, including:

In the case that the second service device is faulty, the first service device determines, according to the user equipment migration policy, the user equipment to be migrated from the user equipment that establishes a connection with the second service device;

The first service device notifies the user equipment to be migrated to register with the first service device.

It can be understood that the second service device is the primary service device, and the first service device is the backup service device.

In the first aspect of the embodiment of the present application, the first service device determines, according to the user equipment migration policy, that the user equipment to be migrated from the second service device to the second service device is to be The migrating user equipment registers with the first service device to establish a connection between the user equipment to be migrated and the first service device, and the user equipment is not required to trigger the switching of the service device, and the power consumption of the user equipment can be reduced. Moreover, the location of the first service device and the second service device in the same city or the same area may be limited, and the disaster recovery deployment cost of the operator may be reduced.

With reference to the first aspect, in a possible implementation manner, the first service device notifies the user equipment to be migrated to register with the first service device by using the following steps:

The first service device sends the addressing information of the first service device and the addressing information of the user equipment to be migrated to the core network gateway, so that the core network gateway sends the first service to the user equipment to be migrated according to the addressing information of the user equipment to be migrated. The addressing information of the device, the addressing information of the first service device is used to register the user equipment to be migrated with the first service device. The addressing information may include at least one of a device identifier and an internet protocol (IP) address, and the device identifier may be a device ID or an international mobile subscriber identification number (IMSI). It can also be a media access control (MAC) address.

With reference to the first aspect, in a possible implementation manner, after the first service device notifies the user equipment to be migrated to register with the first service device, the first service device further receives registration information from the core network gateway, where the registration information includes the user equipment to be migrated. The device identifier may further include a device identifier of the user equipment to be migrated. The core network gateway, when receiving the device identifier of the user equipment to be migrated from the user equipment to be migrated, locates the user equipment to be migrated, and determines the user equipment to be migrated. location information;

The first service device registers the user equipment to be migrated according to the registration information, and sends the registration confirmation information to the core network gateway, and the core network gateway forwards the registration confirmation information to the user equipment to be migrated, where the registration confirmation information is used to indicate the user equipment to be migrated. The connection with the first service device is established successfully.

The first service device sends the addressing information of the first service device to the user equipment to be migrated through the core network gateway, so as to establish a connection between the first service device and the user equipment to be migrated, and switch the user equipment to be migrated from the second service device. To the first service device. In this process, the core network gateway is equivalent to a transit station between the first service device and the user equipment to be migrated. In this process, the user equipment to be migrated is passively switched instead of actively triggering, so the power consumption of the user equipment can be reduced.

In the case that the addressing information of the user equipment to be migrated includes the device identifier or the IP address, the core network gateway may be configured to determine which address device or devices to send the addressing information of the first service device; and the addressing information of the user equipment to be migrated In the case of the device identification and the IP address, the core network gateway can be facilitated to better determine which address device or devices to transmit the addressing information of the first service device.

With reference to the first aspect, in a possible implementation manner, before receiving the registration information from the core network gateway, the first serving device sends an authorization check code to the core network gateway, where the authorization check code is used by the core network gateway. A service device performs security verification. The authorization check code may be sent together with the addressing information of the first service device and the addressing information of the user equipment to be migrated. When the addressing information of the first service device and the addressing information of the user equipment to be migrated are sent in a non-encrypted manner, the authorization check code performs security check on the first service device, which improves security.

With reference to the first aspect, in a possible implementation manner, before the second service device fails, the first service device receives real-time data from the second service device, where the real-time data includes a user equipment that establishes a connection with the second service device. The device identifier is configured to perform data synchronization between the first service device and the second service device, so that the first service device determines the user device to be migrated from the user device that establishes a connection with the second service device according to the user device migration policy.

With reference to the first aspect, in a possible implementation, the foregoing real-time data further includes attribute information of the user equipment that establishes a connection with the second service device, where the attribute information may include user interaction information, rule information, data report information, and At least one of area information, device type, and activity information. The first service device selects the user equipment that meets the user equipment migration policy from the user equipment that establishes the connection with the second service device according to the attribute information of the user equipment that establishes the connection with the second service device, and the user equipment that meets the user equipment migration policy Determined as the user device to be migrated.

It can be understood that the second service device synchronizes the information of the user equipment with which the connection is established to the first service device, so that the first service device determines the user equipment to be migrated from the user devices according to the user equipment migration policy.

With reference to the first aspect, in a possible implementation, the first serving device may determine whether the second serving device is faulty by periodically sending a request message to the second serving device, and the request message may not carry any parameters to reduce the network. Load and pressure.

The first service device periodically sends a request message to the second service device. If the response message is received for each request message sent, the second service device can be determined to work normally, and there is no fault; If the response message is not received within the time period, it is determined that the second service device is faulty, that is, the consecutive preset number of request messages do not receive the response message, and then the second service device is determined to be faulty. The preset time period may be related to the period of sending the request message, and the preset time period and the specific number of the preset number are not limited.

The first serving device determines whether the second serving device is faulty by periodically sending a request message to the second serving device, and does not need to detect whether the second serving device works normally, and can reduce the participation of the user device, thereby reducing the user equipment. Power consumption.

With reference to the first aspect, in a possible implementation, the first service device may determine whether the second service device is faulty by periodically sending a request message to the second service device and the participation of the administrator, and the request message may not be carried. Any parameters to reduce network load and stress.

The first service device periodically sends a request message to the second service device. If the response message is received for each request message sent, the second service device can be determined to work normally, and there is no fault; If the response message is not received within the time period, the second service device may be faulty, but the final failure is determined by the administrator.

The first service device may send a fault estimation message to the administrator device, where the fault estimation message is used to notify the administrator that the second service device may be faulty, and the administrator logs in to the second service device to detect if the fault estimation message is received. And in the case of determining that the second service device is faulty, sending, by the administrator device, an acknowledgement instruction to the first service device, the determining command indicating, for the fault estimation message, that the second service device is faulty, and the first service device receives the acknowledgement In the case of an instruction, the second service device failure is determined.

The first service device may output a fault estimation message in the form of an alarm log, so that the administrator detects whether the second service device is faulty, and sends a confirmation command to the first service device or directly in the first service if the second service device fails. A confirmation command is input on the device, so that the first service device determines that the second service device is faulty.

In combination with the administrator's method, the accuracy is higher than that determined by the first service device, but it may take a little longer than the method determined by the first service device.

With reference to the first aspect, in a possible implementation manner, the first service device may determine the user equipment migration policy by receiving the migration policy from the second service device, and the first service device receives all the information that will be received from the second service device. The migration policy is determined as a user equipment migration policy. One or more of the migration policies may be selected randomly or by default, and the one or more are determined as user equipment migration policies, and the user equipment migration policy may also be determined according to the selection instruction. The method for determining the user equipment migration policy is flexible, so that the method for determining the user equipment to be migrated is flexible, and flexible user equipment migration can be implemented.

With reference to the first aspect, in a possible implementation, the foregoing migration policy includes at least one of an interactive migration policy, a rule triggered migration policy, a data report migration policy, a regional migration policy, a type migration policy, and an activity migration policy. .

A second aspect of the embodiments of the present application provides a service device switching apparatus, where the service device switching apparatus has a function of implementing the method provided by the first aspect. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a possible implementation manner, the service device switching apparatus includes: a processing module and a first transceiver module; and a processing module, configured to: from the second service device according to the user equipment migration policy, in case the second service device fails Determining the user equipment to be migrated in the user equipment that establishes the connection; the first transceiver module is configured to notify the user equipment to be migrated to register with the first service equipment.

In a possible implementation manner, the service device switching device includes: a processor, a transceiver, and a memory, wherein the transceiver is configured to receive and transmit information, the memory stores computer execution instructions, and the processor passes the bus and the memory and the transceiver Connected, the processor executes a computer execution instruction stored in the memory, so that the service device switching device performs the following operation: in case the second service device fails, the user device establishes a connection with the second service device according to the user device migration policy Determining the user equipment to be migrated; notifying the user equipment to be migrated to register with the first service device.

Based on the same inventive concept, the principle and the beneficial effects of the device can be referred to the method described in the first aspect and the beneficial effects thereof. Therefore, the implementation of the device can be referred to the implementation of the method, and the repeated description is not repeated.

A third aspect of embodiments of the present application provides a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the method of the first aspect described above.

A fourth aspect of an embodiment of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the first aspect described above.

A fifth aspect of the embodiments of the present application provides another service device switching method, including:

The core network gateway receives the addressing information of the first service device and the addressing information of the user equipment to be migrated from the first serving device, where the addressing information includes at least one of a device identifier and an IP address;

The core network gateway sends the addressing information of the first service device to the user equipment to be migrated according to the addressing information of the user equipment to be migrated. The addressing information of the first service device is used to register the user equipment to be migrated with the first service device.

In the fifth aspect of the embodiment of the present application, the core network gateway does not need to have the addressing information of the first service device, and the first service device notifies when the handover is needed, so that the transit function of the core network gateway is flexible.

With reference to the fifth aspect, in a possible implementation manner, after the core network gateway sends the addressing information of the first service device to the user equipment to be migrated according to the addressing information of the user equipment to be migrated, the registration is received from the user equipment to be migrated. And sending the registration information to the first service device, where the registration information includes the device identifier of the user equipment to be migrated; receiving the registration confirmation information from the first service device, and sending the registration confirmation information to the user equipment to be migrated, and the registration confirmation information is used. The connection between the user equipment to be migrated and the first service device is successfully established. At this point, the first service device has completed registration with the user equipment to be migrated, and the connection between the two has been established. The user equipment to be migrated can report data to the first service device, and the first service device can send an instruction to the user equipment to be migrated.

With reference to the fifth aspect, in a possible implementation, the core network gateway sends the addressing information of the first service device to the user equipment to be migrated according to the device mode of the user equipment to be migrated, and the device mode may be classified into a discontinuous reception mode. Extended discontinuous reception mode and power saving mode. The user equipment to be migrated can directly report the device mode to the core network gateway, and the core network gateway can also determine the device mode of the user equipment to be migrated according to the information sent by the user equipment to be migrated.

If the device mode of the user equipment to be migrated is in the discontinuous reception mode, the core network gateway immediately obtains the addressing information of the user equipment to be migrated and the addressing information of the user equipment to be migrated. The address information sends the addressing information of the first service device to the user equipment to be migrated.

If the device mode of the user equipment to be migrated is in the discontinuous reception mode, the core network gateway does not immediately send the standby to the user equipment to be migrated when receiving the addressing information of the standby service device and the addressing information of the user equipment to be migrated. The addressing information of the service device is first cached, and the addressing information of the standby service device is sent to the user equipment to be migrated according to the addressing information of the user equipment to be migrated when the next paging time window arrives.

If the device mode of the user equipment to be migrated is in the power saving mode, the core network gateway does not immediately send the standby service device to the user equipment to be migrated when receiving the addressing information of the standby service device and the addressing information of the user equipment to be migrated. The addressing information is first cached, and when the data reported by the user equipment to be migrated is received, the addressing information of the standby service device is sent to the user equipment to be migrated according to the addressing information of the user equipment to be migrated.

With reference to the fifth aspect, in a possible implementation, the core network gateway receives the addressing information of the first serving device from the user equipment to be migrated according to the addressing information of the user equipment to be migrated, and receives the addressing information from the first serving device. Authorizing the verification code, and performing security verification on the first service device according to the authorization verification code, and sending the content to the user equipment to be migrated according to the addressing information of the user equipment to be migrated, if the first service device passes the security check Addressing information of the first service device.

A sixth aspect of the embodiments of the present application provides a service device switching apparatus, where the service device switching apparatus has a function of implementing the method provided by the fifth aspect. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a possible implementation, the service device switching device includes: a first transceiver module and a second transceiver module; and a first transceiver module, configured to receive, by the first service device, addressing information of the first service device and to be migrated The addressing information of the user equipment, the addressing information includes at least one of a device identifier and an IP address, and the second transceiver module is configured to send the first service device to the user equipment to be migrated according to the addressing information of the user equipment to be migrated. The address information, the addressing information of the first service device is used to register the user equipment to be migrated with the first service device.

In a possible implementation manner, the service device switching device includes: a processor, a transceiver, and a memory, wherein the transceiver is configured to receive and transmit information, the memory stores computer execution instructions, and the processor passes the bus and the memory and the transceiver Connected, the processor executes a computer execution instruction stored in the memory to cause the service device switching device to perform: receiving, by the transceiver, the addressing information of the first service device and the addressing information of the user device to be migrated from the first serving device Transmitting the addressing information of the first service device to the user equipment to be migrated according to the addressing information of the user equipment to be migrated, where the addressing information includes at least one of a device identifier and an IP address, where the addressing information of the first serving device is used. The user equipment to be migrated is registered with the first service device.

Based on the same inventive concept, the principle and the beneficial effects of the device can be referred to the method described in the fifth aspect and the beneficial effects thereof. Therefore, the implementation of the device can be referred to the implementation of the method, and the repeated description is not repeated.

A seventh aspect of the present application provides a computer readable storage medium having instructions stored therein that, when run on a computer, cause the computer to perform the method described in the fifth aspect above.

An eighth aspect of the embodiments of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the above fifth aspect.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background art, the drawings to be used in the embodiments of the present application or the background art will be described below.

1 is a schematic diagram of a network architecture to which an embodiment of the present application is applied;

2 is a schematic flowchart of an existing user equipment reporting data to a service device;

3 is a schematic flowchart of a method for switching a service device in an existing manner;

FIG. 4 is a schematic flowchart of a method for switching a service device according to an embodiment of the present disclosure;

FIG. 5 is a schematic flowchart of detecting whether a primary service device is faulty by a backup service device according to an embodiment of the present disclosure;

FIG. 5 is a schematic diagram of a process for detecting whether a primary service device is faulty by a backup service device according to an embodiment of the present disclosure;

FIG. 6 is a schematic flowchart of establishing a connection between a backup service device and a user equipment according to an embodiment of the present disclosure;

FIG. 7 is a schematic diagram of a logical structure of a service device according to an embodiment of the present application;

FIG. 8 is a simplified schematic diagram of a physical structure of a service device according to an embodiment of the present application;

FIG. 9 is a schematic diagram of a logical structure of a core network gateway according to an embodiment of the present application;

FIG. 10 is a simplified schematic diagram of a physical structure of a core network gateway according to an embodiment of the present application.

Detailed ways

The words involved in the embodiments of the present application will be introduced below:

The service device, which is an Internet of Things (IoT) platform, provides data collection and management functions for various sensors and subscriber identity module (SIM) cards, and can open data to third-party application systems. Let applications quickly build their own IoT business. In other words, the service device is responsible for establishing a connection with the IoT user equipment, and managing and processing the data reported by the IoT user equipment, which can be deployed in the cloud. It can be understood that the IoT platform integrates the IoT connection management platform and the server, and the IoT connection management platform assists in establishing a connection with the user equipment. The server is used to manage and process the data reported by the IoT user equipment, and issue commands. In the embodiment of the present application, the service device is an NB-IoT platform, and the disaster recovery system can be divided into a primary service device (ie, a primary NB-IoT platform) and a backup service device (ie, a standby NB-IoT platform). In the event of a service device failure, the device can be switched to the alternate service device to ensure data interaction between the NB-IoT user device and the service device.

The user equipment, which is applied to the user equipment in the NB-IoT scenario, may include, but is not limited to, a smart meter, a smart water meter, a smart gas meter, a smart parking sensor, a smart home device, a shared bicycle, and a shared application. The physical equipment of the NB-IoT chip or module is integrated in the streetlights of automobiles and road traffic. It should be noted that the user equipments involved in the embodiments of the present application are all NB-IoT user equipments.

The user equipment to be migrated is a user equipment that needs to be migrated from the primary service device to the standby service device in the event of a failure of the primary service device, or may be migrated from the backup service device to the case where the backup service device fails. User device of the primary service device.

A migration strategy, a migration algorithm, is used to determine which user devices or devices are migrated from the primary service device to the backup service device or from the backup service device to the primary service device. The migration policy may include, but is not limited to, at least one of an interactive migration policy, a rule triggered migration policy, a data report migration policy, a zone migration policy, a type migration policy, and an activity migration policy.

An interactive migration strategy for migrating user-aware user devices, such as shared bicycles, smart parking sensors, and more. The user equipment is instructed by the user to determine which user equipments interact with the user. The service device stores a history of user commands. Each time a user issues a command, the service device records a history of user commands. The user command history records the device ID of the user device. The user command history records the user devices that interact with the user, and then determines to migrate the user devices. The device identifier may be a device ID, an IMSI, or a MAC address.

The rule triggers the migration policy, and is used to migrate the user equipment that meets the rule information. The rule information may include the device identifier, trigger time, and trigger condition of the user equipment. The third-party application system can set the rule information to the primary service device, or the backup service device, or the primary service device and the backup service device. For example, if the primary service device fails in the early morning, and the user equipment collected in batches is about to trigger the collection of data, the user equipment needs to be migrated to the backup service device. By analyzing the rule information, it is possible to predict which user devices are about to meet the rules and migrate these user devices.

The data is reported to be migrated to the user equipment that needs to report data in the current time period. The service device records the historical data of the user equipment according to the time when the data is reported by the user equipment. Each time the user equipment reports a data, the service device stores a data in the database, and the stored information includes the device identifier of the user equipment. The historical data can be used to analyze the possible reporting time of the user equipment, and compare the fault time of the service equipment with the data time reported by the user equipment. It can be determined which user equipments will report data and migrate these user equipments.

The area migration policy is used to migrate user equipment in a specified area, for example, to migrate user equipment in the government location and hotspot area. When the user equipment firstly registers and subsequently reports data, the EPC locates the geographic location of the user equipment by using the cell information, and reports the geographic location of the user equipment to the service device, where the service device stores the geographic location of the user equipment. The service device can determine the user devices that need to be migrated according to the specified area, and migrate the user devices.

A type migration policy for migrating user devices of the specified type. When a user equipment accesses a service device, each user equipment is classified into a certain category, for example, a smart refrigerator belongs to one category, a smart water meter is classified into one category, and a shared bicycle belongs to one category. It can be understood that the service device has already determined the type of the user device when adding the user device for management, and then the user device of the type can be migrated according to the specified type.

An active mobility migration policy is used to migrate user devices with specified activeness. Activeness refers to the active interaction between user devices and service devices. The service device can count the active status of the user equipment according to the historical record of the data reported by the user equipment and the commands sent by the user equipment, and sort according to the activity level of the user equipment. The activity level can be divided into three levels: high, medium, and low. User equipment can be migrated in batches according to activity.

The user equipment migration policy is the finalized migration policy, that is, the final determination of which migration strategy or migration policies are used to migrate the user equipment. The user equipment migration policy may be one or more of the foregoing six migration strategies, and may be other migration strategies than the foregoing six migration policies.

The core network gateway is used to provide user session management and bearer control, data forwarding, internet protocol (IP) address allocation, and non-3rd generation partnership project (3GPP) user access. Features. The core network gateway may be a public data network gateway (PGW/P-GW) in the fourth generation mobile communication (4th-generation) core network architecture, that is, a PGW in the EPC, or may be a third generation. The gateway generalized radio service (GPRS) support node (GGSN) in the 3rd-generation core network architecture, or the fifth-generation mobile communication (5th-generation) core A network element with similar functions to the PGW in the network architecture or in the future core network architecture.

The device mode refers to the power-saving technology mode of the NB-IoT user equipment, which can be divided into discontinuous reception mode (DRX), extended discontinuous reception (eDRX), and power saving mode. , PSM).

DRX, the DRX cycle is configured by the base station and broadcast to the user equipment through system messages. When the user equipment is in the idle state, the paging channel is monitored every DRX cycle to check whether downlink service is reached. When the user equipment is idle, the EPC receives the downlink data packet, caches the data packet, and pages the user equipment, triggers the user equipment to establish an air interface connection, and then forwards the downlink data packet. The DRX period of NB-IoT ranges from 1.28s, 2.56s, 5.12s or 10.24s. For a DRX user device, the service device can assume that the user device is reachable at any time.

eDRX, in each eDRX cycle, has a paging time window (PTW). The user equipment only listens to the paging channel in the PTW according to the eDRX cycle, so as to receive the downlink service, and the time outside the PTW is in a sleep state. Do not listen to the paging signal and cannot receive downlink traffic. The length of the eDRX and the length of the PTW are configurable. The user equipment and the mobility management entity (MME) negotiate the value of the MME to the user equipment. The MME can use the access point name. , APN) or IMSI segment configuration. The EPC receives the downlink data packet outside the PTW, and caches the data packet (only one can be cached for each user equipment). When entering the PTW, the MME pages the user equipment, triggers the user equipment to establish an air interface connection, and then forwards the data packet to User equipment. The service device can issue commands to the user equipment at any time, but if the user equipment is not online, the EPC can only cache one message. After the message is sent, it takes up to one eDRX cycle to reach the user equipment.

For scenarios where the downlink service delay is not required (for example, the smart water meter, the downlink service is mainly parameter location, firmware, etc., and the user equipment can wait for the uplink data to enter the connection state and then initiate), and the PSM can be used to further save the power consumption of the user equipment. Once the user equipment accesses the PSM mode, the receiver will be shut down and the system message and paging message of the air interface will no longer be received. The network side cannot actively contact the user equipment. Only when the user equipment needs to send uplink data or needs to perform periodic location update, Will actively wake up to perform the upstream business process. The base station considers that it is in the connected state after being received by the base station for a period of time (for example, 5 s, specifically configured according to the base station inactivity timer), and can be immediately sent.

Please refer to FIG. 1 , which is a schematic diagram of a network architecture in which an embodiment of the present application is applied. The network architecture shown in Figure 1 includes user equipment, access networks, core networks, and IoT platforms. It should be noted that the configuration and the number of the devices and network elements shown in FIG. 1 are not sufficient to limit the embodiments of the present application.

The user equipment may include, but is not limited to, a physical device integrated with an NB-IoT chip and a module such as a smart water meter, a smart meter, a shared bicycle, and a smart refrigerator.

The access network mainly completes the communication and management functions between the mobile communication network and the user equipment. The access network includes a base station, which may be a base station (node B, NB) in 3G, or an evolved node B (eNB) in 4G, or may be a base station in 5G or a future communication system.

The function of the core network is mainly to provide a user connection, management of the user, and completion of the service, as an interface provided by the bearer network to the external network. The establishment of user connections includes mobility management, call management, switching/routing, and recording notifications. User management includes user description, quality of service (QoS), user communication records, security, and the like. The bearer connection includes an external public switched telephone network (PSTN), an external circuit data network and a packet data network, a server, and the like. The basic services that the core network can provide include mobile office, e-commerce, communications, entertainment services, travel and location-based services, remote sensing services, simple messaging services (such as surveillance control), and more.

The core network shown in FIG. 1 is an EPC in 4G, including a PGW, an MME, a serving gateway (SGW), a policy and charging rules function (PCRF), and a user subscriber server (home subscriber server). , HSS). It should be noted that the core network shown in FIG. 1 does not constitute a limitation on the embodiment of the present application, and may also be a core network in a 5G communication system or a core network in a future communication system.

The core network is connected to the primary service device. In the event that the primary service device fails, the core network switches to connect with the backup service device to ensure data interaction between the user device and the service device.

Referring to FIG. 2, a schematic diagram of a process for reporting data to an existing user equipment to a service device may include, but is not limited to, the following steps:

Step S201: The user equipment sends first registration information to the EPC, where the first registration information includes an IP address of the service device and an IMSI value of the user equipment. Accordingly, the EPC receives the first registration information from the user equipment.

The user equipment sends the first registration information to the EPC through the access network, and specifically sends the first registration information to the PGW in the EPC. The first registration information includes an IP address of the service device and an IMSI value of the user equipment, so that the EPC sends the IMSI value of the user equipment to the service device corresponding to the IP address.

Step S202: The EPC sends second registration information to the service device, where the second registration information includes an IMSI value of the user equipment. Accordingly, the service device receives the second registration information from the EPC.

The EPC, when receiving the first registration message, caches the device information of the user equipment, and sends the second registration information to the service device according to the IP address of the service device, where the second registration information includes the IMSI value of the user equipment. The device information of the user equipment includes an IMSI value of the user equipment, a device mode (DRX, eDRX, or PSM) of the user equipment, a device type of the user equipment, and a device ID of the user equipment.

Step S203, the service device sends a subscription message to the EPC. Accordingly, the EPC receives the subscription message from the service device.

When receiving the second registration information, the service device registers the user equipment according to the IMSI value of the user equipment, and stores the IMSI value of the user equipment. Upon completion of the registration of the user equipment, a connection between the user equipment and the service device is established, and the service device sends a subscription message to the EPC, the subscription message being used to subscribe to the data of the user equipment.

Step S204: The EPC sends a subscription message to the user equipment. Accordingly, the user equipment receives the subscription message from the EPC.

When receiving the subscription message sent by the service device, the EPC sends a subscription message to the user equipment, where the subscription message is used to subscribe to the data of the user equipment.

Step S205, the user equipment sends data to the EPC. Accordingly, the EPC receives data from the user equipment.

The user equipment sends the data to be reported to the EPC in the non-confirmable (NON) message mode of the CoAP when the data needs to be reported. It can be understood that the non-acknowledgement message mode does not require a receiver feedback acknowledgement message, and the acknowledgement message mode needs to receive a method feedback acknowledgement message.

Step S206, the EPC sends data to the service device. Accordingly, the service device receives data from the EPC.

When receiving the data that needs to be reported sent by the user equipment, the EPC sends the data that needs to be reported to the service device. The EPC can process the received data and send the processed data to the service device. The service device performs subsequent processing in the case that the data sent by the EPC is received. The embodiment of the present application does not introduce the subsequent processing. Because it is a non-acknowledgment message mode, the service device does not need to feed back an acknowledgment message to the EPC.

Currently, in the disaster recovery scenario, the user equipment configures the IP addresses of the primary service device and the backup service device, and configures the user device to acknowledge the message mode to report data to the service device. It can be understood that the acknowledgement message mode requires a service device feedback response message. The response message may be sent to the EPC by a cloud inter-gateway (CIG) in the service device. The cloud gateway is a protocol conversion module in the IoT platform, which is used for protocol conversion between different protocol data of the user equipment and user equipment access protocol data of the IoT platform standard.

FIG. 3 is a schematic flowchart of a method for switching a service device in an existing manner, where the process may include, but is not limited to, the following steps:

Step S301, the user equipment sends the first data to the EPC. Accordingly, the EPC receives the first data from the user equipment.

Step S302, the EPC sends the first data to the primary service device. Accordingly, the primary serving device receives the first data from the EPC.

Step S303, the primary service device sends a first response message to the EPC. Accordingly, the EPC receives the first response message from the primary service device.

Step S304, the EPC sends a first response message to the user equipment. Accordingly, the user equipment receives the first response message from the EPC.

Step S301 - Step S304 is a process in the case that the primary service device is in normal working condition. If the user equipment does not receive the first response message within a specified time, indicating that the primary service device may be faulty, the user equipment resends the first data to the EPC. If the response message is still not received after retransmission, it indicates that the primary service device is faulty, then the user equipment switches to the standby service device, and the following steps are performed:

Step S305, the user equipment sends the second data to the EPC. Accordingly, the EPC receives the second data from the user equipment.

It should be noted that the second data may be the same as or different from the first data.

Step S306, the EPC sends the second data to the standby service device. Accordingly, the alternate service device receives the second data from the EPC.

Step S307, the standby service device sends a second response message to the EPC. Accordingly, the EPC receives a second response message from the alternate serving device.

Step S308, the EPC sends a second response message to the user equipment. Accordingly, the user equipment receives a second response message from the EPC.

It can be seen from the process shown in FIG. 3 that, if the user equipment does not receive the response message of the EPC feedback, the user equipment retransmits multiple times to detect whether the primary service device works normally, and the user equipment triggers the handover from the primary service device to the backup service. The device, which increases the extra power consumption of the user device. For example, the smart water meter has a battery life of about 5 years. If it is retransmitted multiple times to detect whether the main service equipment is working properly, the battery life will be reduced, and the replacement of the smart water meter battery is not as simple as the replacement of the mobile phone battery, in other words, replacement. Smart water meter batteries are more troublesome.

In view of this, the embodiment of the present application provides a service device switching method and device thereof, which does not require the user equipment to detect whether the service device works normally, and does not need the user equipment to trigger the switching of the service device, and can reduce the power consumption of the user equipment.

The service device switching method provided by the embodiment of the present application will be described below with reference to FIG.

FIG. 4 is a schematic flowchart of a method for switching a service device according to an embodiment of the present disclosure. The method may include, but is not limited to, the following steps:

Step S401: In the case that the second service device is faulty, the first service device determines, according to the user equipment migration policy, the user equipment to be migrated from the user equipment that establishes a connection with the second service device.

The first service device may be a primary service device or a backup service device, and the second service device may be a primary service device or a backup service device. If the first service device is the primary service device, the second service device is the backup service device; if the first service device is the backup service device, the second service device is the primary service device. In the embodiment of the present application, the second service device is a service device to which the user equipment is to be migrated before the handover, and the first service device is the service device to which the user equipment is to be migrated after the handover. The embodiment of the present application introduces the first service device as the backup service device and the second service device as the primary service device.

The first service device may determine whether the second service device is faulty, that is, the backup service device may detect whether the primary service device is faulty, and the backup service device may detect whether the primary service device is faulty in the following two manners.

In a first manner, the first service device periodically sends a request message to the second service device. If the first service device does not receive the response message within the preset time period, determining that the second service device is faulty, that is, determining that the primary service device is faulty. . The preset time period may be related to the period of sending the request message, for example, the period is 10s, and the preset time period is 30s. See the description of Figure 5a for details.

In a second manner, the first service device periodically sends a request message to the second service device. If the first service device does not receive the response message within the preset time period, the device sends a fault estimation message, where the fault estimation message indicates the second service. The device may be faulty, and in the event that the first serving device receives an acknowledgment command for the fault speculative message, determining that the second serving device is faulty, ie, determining that the primary serving device is faulty. See the description of Figure 5b for details.

The first service device may send a fault speculative message to the administrator device, may also send a fault speculative message to the operation and maintenance system, and may output a fault speculative message or the like in the form of the alarm log in the first service device. The operation and maintenance system can operate and maintain the primary service device and the backup service device.

In the above two manners, it is detected by the backup service device whether the primary service device is faulty, and the power consumption of the user equipment is reduced as compared with whether the user equipment detects whether the primary service device is faulty.

In a possible implementation manner, before the second service device fails, the first service device may receive real-time data sent by the second service device, that is, the first service device performs hot backup with the second service device. A hot backup is a backup of a system that is in normal operation.

The real-time data may include a device identifier of the user equipment that establishes a connection with the second service device, where the device identifier may be a device ID, an IMSI, or a MAC address. It can be understood that there is more than one user equipment establishing a connection with the second service device, and the real-time data includes the device identifiers of all the user equipments that establish a connection with the second service device. And, in a case that the new user equipment is connected to the second service device, the second service device sends the device identifier of the new user device to the first service device, so that the first service device adds the device identifier of the new user device. . In the case that the user equipment is disconnected from the second service device, the second service device sends the device identifier of the disconnected user device to the first service device, so that the first service device deletes the disconnected user device. Device identification.

The real-time data may further include attribute information of the user equipment that establishes a connection with the second service device, and the attribute information may include, but is not limited to, at least user interaction information, rule information, data report information, area information, device type, and activity information. One.

The user interaction information includes multiple user command history records. Each time a user sends a command to the user device, the second service device records a history of the user command. User interaction information can be used to determine whether an interactive migration policy is met.

The rule information may be used to determine whether the rule triggers the migration policy, and the rule information may include a trigger time, a trigger condition, and the like.

The data reporting information is used to determine whether the data reporting migration policy is met, and the data reporting information may include the reporting time.

The area information is the geographic location of the user equipment that is connected to the second service device by the EPC, and is used to determine whether the area migration policy is met.

The device type can be reported by the user device or by the EPC or the second service device. The device type is used to determine whether the type migration policy is met.

The activity information includes a history record of the data reported by the user equipment and a command sent by the second service device, and may be used by the second service device to determine whether the activity migration policy is met.

The real-time data may further include an IP address of the user equipment that establishes a connection with the second service device, so that after determining the user equipment to be migrated, the information may be sent to the user equipment to be migrated according to the IP address or according to the device identifier and the IP address.

The first service device may acquire the user equipment migration policy before determining the user equipment to be migrated from the user equipment that establishes a connection with the second service device according to the user equipment migration policy. It can be understood that the first service device acquiring the user equipment migration policy may be before determining that the primary service device is faulty, or after determining that the primary service device is faulty.

In a possible implementation manner, the first serving device receives the migration policy from the second serving device, and determines the received migration policy as the user device migration policy. In other words, which migration policies are sent by the primary service device to the alternate service device, these migration policies are determined as user device migration policies. The second service device may selectively send the migration policy to the first service device, and the first service device determines the received migration policy as the user migration policy. The administrator can log in to the maintenance interface of the second service device and select the migration policy to be sent to the first service device.

In a possible implementation manner, the first service device receives the migration policy from the second service device, and the administrator can log in to the maintenance interface of the first service device, where the maintenance interface displays the migration policy received from the second service device, and the management A selection instruction can be input for these migration policies, and one or more of the migration policies are selected, and the first service device determines the selected migration policy as the user equipment migration policy. In other words, one or more of the migration policies sent by the administrator from the primary service device to the alternate service device are selected, and the selected migration policy is determined as the user device migration policy.

The migration policy received by the first service device from the second service device may include, but is not limited to, an interactive migration policy, a rule triggered migration policy, a data reporting migration policy, a regional migration policy, a type migration policy, and an active mobility migration. At least one of the strategies.

The second service device may store the migration policy in an operation and maintenance (O&M) portal. When the migration policy needs to be sent to the first service device, the O&M portal sends the migration policy to the first service device. The O&M portal can be located on the second service device and is open to the administrator, that is, the administrator can control when the migration policy is sent to the first service device.

The first serving device selects the user equipment that satisfies the user equipment migration policy from the user equipment that establishes the connection with the second service device according to the real-time data received from the second service device, and determines the user equipment that meets the user equipment migration policy as User equipment to be migrated.

If the number of user equipment migration policies is one, the user equipment that meets the user equipment migration policy is determined as the user equipment to be migrated. If the number of the user equipment migration policies is two or more, the user equipment that satisfies the user equipment migration policies is determined as the user equipment to be migrated.

For example, the user equipment migration policy includes a zone migration policy, and the area information of a user equipment matches the area specified by the area migration policy, that is, the area information of the user equipment meets the area migration policy, and the user can be the user. The device is determined to be the user device to be migrated.

The user equipment to be migrated is determined according to the user equipment migration policy, so that the user equipment migration is performed in a targeted manner, that is, the targeted migration according to the attribute information of the user equipment can reduce the service loss.

Step S402: The first service device notifies the user equipment to be migrated to register with the first service device.

The first service device notifies the user equipment to be migrated to register with the first service device to establish a connection with the user equipment to be migrated. It can be understood that, in the case of a failure of the second service device, the connection between the user equipment to be migrated and the user equipment may have been disconnected, so the first service device needs to establish a connection with the user equipment to be migrated. Or, in the case of a fault, the second service device cannot process the data reported by the user equipment to be migrated, and the command cannot be sent to the user equipment to be migrated. Therefore, the user equipment to be migrated needs to be registered with the first service device. The connection between the two service devices is switched to the connection with the first service device.

The first service device notifies the user equipment to be migrated to register with the first service device through the core network gateway. In an implementation manner, the first serving device sends the addressing information of the first serving device and the addressing information of the user device to be migrated to the core network gateway, and the core network gateway sends the user to be migrated according to the addressing information of the user device to be migrated. The device sends the addressing information of the first service device, and the user equipment to be migrated registers with the first service device through the core network gateway when receiving the addressing information of the first service device. In another implementation manner, the first serving device sends the addressing information of the user equipment to be migrated to the core network gateway, and the core network gateway obtains the addressing of the first service device from the source address information of the message sent by the first serving device. And transmitting the addressing information of the first service device to the user equipment to be migrated according to the addressing information of the user equipment to be migrated, and the user equipment to be migrated passes through the core network after receiving the addressing information of the first service device. The gateway registers with the first service device. A person skilled in the art may think that the core network gateway may further determine that the user equipment migration is to be performed through a pre-agreed message or a cell sent by the backup service device, and obtain the first service according to the source address of the message or the pre-configured information. Addressing information for the device.

It can be understood that a user equipment is registered on the service device, that is, a connection between the user equipment and the service device is established, and the user equipment can report data to the service device, and can receive a command sent by the service device.

The process of establishing a connection between the first service device and the user equipment to be migrated can be referred to the description of FIG. 6.

In the embodiment shown in FIG. 4, in the case that the primary service device is faulty, the user equipment to be migrated is determined from the user equipment that establishes a connection with the primary service device according to the user equipment migration policy, and the user equipment to be migrated is notified to the first The service device is registered to establish a connection between the backup service device and the user device to be migrated, without the user device triggering the switching of the service device, reducing the dependence on the user device, reducing the power consumption of the user device, and facilitating the promotion of the NB-IoT. Application of user equipment.

It should be noted that the location of the first service device and the second service device in the embodiment of the present application is flexible, and it is not necessary to limit the two to be in the same city or the same region, which can reduce the disaster recovery deployment cost of the operator.

FIG. 5 is a schematic flowchart of a method for detecting whether a primary service device is faulty by a backup service device according to an embodiment of the present disclosure, which may include:

Step S501a, the standby service device sends a request message to the primary service device. Accordingly, the primary serving device receives the request message from the alternate serving device.

The request message may be a hypertext transfer protocol (HTTP) request message, and the request message does not carry any parameters.

In one possible implementation, the alternate serving device may periodically send a request message to the primary serving device, for example, the alternate serving device sends a request message to the primary serving device every 10 seconds. The specific period value is not limited in the embodiment of the present application.

Step S502a, the primary service device sends an acknowledgement message to the backup service device. Accordingly, the alternate service device receives an acknowledgment message from the primary service device.

The confirmation message may be an HTTP 200 acknowledgment message, and the acknowledgment message does not carry any parameters. The acknowledgment message is used to respond to the request message indicating that the primary service device has received the request message. The standby service device receives the confirmation message, indicating that the primary service device is working normally and there is no fault.

Step S503a, the standby service device sends a request message to the primary service device. Accordingly, the primary serving device receives the request message from the alternate serving device.

Step S504a, the standby service device sends a request message to the primary service device. Accordingly, the primary serving device receives the request message from the alternate serving device.

Step S505a, the standby service device sends a request message to the primary service device. Accordingly, the primary serving device receives the request message from the alternate serving device.

It can be understood that after performing step S503a - step S505a, that is, the standby service device does not receive the acknowledgement message after sending the request message three times to the master service device.

Step S506a, the standby service device determines that the primary service device is faulty.

If the standby service device does not receive the acknowledgment message after sending the three-time request message, it can be determined that the primary service device is faulty at this time. It can be understood that, in the case that the backup service device does not receive the confirmation message, the primary service device may be determined to be faulty. The specific value of the preset number of times is not limited in the embodiment of the present application.

In a possible implementation, if the backup service device does not receive the acknowledgment message within the preset time period, it may be determined that the primary service device is faulty at this time, and the specific value of the preset time period is not used in the embodiment of the present application. limited. For example, the period in which the standby service device sends the request message to the primary service device is 10 s, and the preset time period is 30 s. If the acknowledgment message is not received within 30 s, the primary service device failure may be determined at this time.

It can be understood that the standby service device can directly determine that the primary service device is faulty if the acknowledgment message is not received by the preset number of times request message, or if the acknowledgment message is not received within the preset time period.

FIG. 5 is a schematic flowchart of another method for detecting whether a primary service device is faulty by the backup service device according to an embodiment of the present disclosure, which may include:

Step S501b, the standby service device sends a request message to the primary service device. Accordingly, the primary serving device receives the request message from the alternate serving device.

Step S502b, the primary service device sends an acknowledgement message to the backup service device. Accordingly, the alternate service device receives an acknowledgment message from the primary service device.

Step S503b, the standby service device sends a request message to the primary service device. Accordingly, the primary serving device receives the request message from the alternate serving device.

Step S504b, the standby service device sends a request message to the primary service device. Accordingly, the primary serving device receives the request message from the alternate serving device.

Step S505b, the standby service device sends a request message to the primary service device. Accordingly, the primary serving device receives the request message from the alternate serving device.

For the detailed description of the steps S501a-S505, refer to the description of the steps S501b-S505b, and details are not described herein again.

Step S506b, the backup service device sends a fault estimation message to the administrator device. Accordingly, the administrator device receives the fault speculative message from the alternate serving device.

If the standby service device does not receive the acknowledgement message after sending the three-time request message, it may be considered that the primary service device may be faulty at this time. It can be understood that, in the case that the standby service device does not receive the acknowledgment message, the primary service device may be faulty at this time, and the specific value of the preset number of times is not limited in the embodiment of the present application. .

In a possible implementation, if the backup service device does not receive the acknowledgment message within the preset time period, it may be considered that the primary service device may be faulty at this time, and the specific value of the preset time period is in the embodiment of the present application. Not limited. For example, the period in which the backup service device sends the request message to the primary service device is 10s, and the preset time period is 30s. If the confirmation message is not received within 30s, the primary service device may be considered to be faulty.

In the event that the primary serving device may fail, the alternate serving device may send fault guessing information to the administrator device indicating that the primary serving device may be faulty. The administrator device is a device operated by the administrator, and is used to monitor the service device, receive information sent by the service device, and send information to the service device, such as a mobile phone. The administrator can be the maintenance engineer of the primary service device or the maintenance engineer of the primary service device and the backup service device. The backup service device can send a fault speculative message to the administrator device by sending a short message or sending an email.

In the case that the primary service device may be faulty, the backup service device may also send a fault estimation message to the operation and maintenance system, and the operation and maintenance system may perform fault detection on the primary service device if the fault estimation message is received.

In the case that the primary service device may be faulty, the backup service device may also output a fault estimation message on the standby service device side in a manner of alerting the log to notify the administrator that the primary service device may be faulty.

It should be noted that, in the case that the primary service device may be faulty, the backup service device may also send or output a fault estimation message in other manners, which is not enumerated in the embodiments of the present application.

In step S507b, the administrator device sends an acknowledgement command to the backup service device. Accordingly, the alternate service device receives a confirmation command from the administrator device.

When the administrator device receives the fault estimation message, the administrator can log in to the primary service device to check whether the primary service device is faulty. When the primary service device fails, the administrator sends the backup device to the backup service device. The confirmation command or the administrator directly enters a confirmation command on the alternate service device, which is used to indicate that the primary service device is faulty. The administrator device can send a confirmation command to the backup service device by replying to the short message, replying to the email, and clicking the fault confirmation button.

The operation and maintenance system, when receiving the fault estimation message, performs fault detection on the primary service device, and in the case of determining that the primary service device is faulty, sends an acknowledgement instruction to the backup service device, where the acknowledgement command is used to indicate that the primary service device is faulty. . It is also possible for the administrator of the operation and maintenance system to check whether the primary service device is faulty, and to send the confirmation command to the backup service device through the operation and maintenance system in the event that the primary service device is determined to be faulty.

When the backup service device outputs the fault estimation message in the manner of the alarm log, the administrator checks whether the primary service device is faulty. When the primary service device fails, the administrator can directly input a confirmation command on the backup service device. The confirmation command is used to indicate that the primary service device is faulty.

Step S508b, the standby service device determines that the primary service device is faulty.

The standby service device may determine that the primary service device is faulty upon receiving the confirmation command.

It can be understood that the standby service device determines that the primary service device is faulty upon receiving the confirmation command sent by the administrator.

The processes shown in FIG. 5a and FIG. 5b are all determined by the backup service device to determine the failure of the primary service device. Compared with the method for detecting whether the primary service device works normally by the user device, the power consumption of the user equipment can be reduced, and the pressure on the wireless network can be reduced. And the load (because of the method detected by the user equipment to confirm the message mode, the feedback response message is needed, which will cause pressure and load on the wireless network).

FIG. 6 is a schematic diagram of a process of establishing a connection between a backup service device and a user equipment according to an embodiment of the present disclosure, which may include:

Step S601: The backup service device sends the addressing information of the standby service device and the addressing information of the user equipment to be migrated to the core network gateway. Correspondingly, the core network gateway receives the addressing information of the standby service device and the addressing information of the user equipment to be migrated from the standby service device.

The backup service device sends the addressing information of the standby service device and the addressing information of the user equipment to be migrated to the core network gateway in the case that the user equipment to be migrated is determined. The addressing information may include at least one of a device identification and an IP address. The device identifier can be a device ID, an IMSI, or a MAC address. The device ID and IP address of the user equipment to be migrated can be obtained from real-time data.

In a possible implementation, the backup service device may send the addressing information of the backup service device and the addressing information of the user equipment to be migrated to the core network gateway by using a message, that is, the message carries the addressing information of the standby service device and Addressing information of the user equipment to be migrated. The specific name of this message is not limited in the embodiment of the present application.

In another possible implementation manner, the backup service device may send the addressing information of the user equipment to be migrated to the core network gateway by using a message, that is, the message carries the addressing information of the user equipment to be migrated. The specific name of this message is not limited in the embodiment of the present application. The core network gateway can obtain the addressing information of the standby service device by using other methods, for example, the source address of the message sent by the backup service device, and the addressing information of the backup service device is obtained, and the core network gateway obtains the information through the pre-configured information, for example, the pre-configured information. The configuration information includes addressing information of the alternate service device.

If the addressing information of the backup service device includes the device identifier of the standby service device, the core network gateway or the user device to be migrated may search for the IP address of the standby service device according to the device identifier of the backup service device, for example, according to the device identifier of the backup service device. Find the IP address of the alternate service device in the domain name system (DNS). If the addressing information of the standby service device includes the IP address of the standby service device, the core network gateway may directly send the IP address of the standby service device to the user equipment to be migrated. If the addressing information of the standby service device includes the device identifier and the IP address, the core network gateway may directly send the device identifier and the IP address of the standby service device to the user equipment to be migrated. The addressing information may also include other information for determining the IP address of the alternate serving device.

In a possible implementation manner, the backup service device further sends an authorization check code to the core network gateway, where the authorization check code can be sent together with the addressing information of the standby service device and the addressing information of the user equipment to be migrated, that is, carried Sent in the same message. The authorization check code can also be sent together with the addressing information of the user equipment to be migrated. The authorization check code is used by the core network gateway to perform security check on the standby service device. In the case of non-encrypted transmission between the backup service device and the core network gateway, the security of the transmission can be ensured by the authorization check code.

Step S602: The core network gateway sends the addressing information of the standby service device to the user equipment to be migrated. Correspondingly, the user equipment to be migrated receives the addressing information of the standby service device from the core network gateway.

The core network gateway, when receiving the addressing information of the standby service device and the addressing information of the user equipment to be migrated, may send the addressing information of the standby service device to the user equipment to be migrated according to the addressing information of the user equipment to be migrated. The user equipment to be migrated is registered with the backup service device according to the addressing information of the standby service device.

In a possible implementation, the core network gateway sends the addressing information of the standby service device to the user equipment to be migrated according to the device mode of the user equipment to be migrated. The user equipment to be migrated can directly report the device mode to the core network gateway, and the core network gateway can also determine the device mode of the user equipment to be migrated according to the information sent by the user equipment to be migrated.

If the device mode of the user equipment to be migrated is DRX, the core network gateway immediately sends the addressing information of the user equipment to be migrated according to the addressing information of the user equipment to be migrated when receiving the addressing information of the standby service device and the addressing information of the user equipment to be migrated. The device sends addressing information for the alternate service device.

If the device mode of the user equipment to be migrated is eDRX, the core network gateway does not immediately send the backup service device to the user equipment to be migrated when receiving the addressing information of the standby service device and the addressing information of the user equipment to be migrated. The address information is cached first, and the addressing information of the standby service device is sent to the user equipment to be migrated according to the addressing information of the user equipment to be migrated when the next PTW arrives.

If the device mode of the user equipment to be migrated is PSM, the core network gateway does not immediately send the backup service device to the user equipment to be migrated when receiving the addressing information of the standby service device and the addressing information of the user equipment to be migrated. The address information is cached first, and when the data reported by the user equipment to be migrated is received, the addressing information of the standby service device is sent to the user equipment to be migrated according to the addressing information of the user equipment to be migrated.

Step S603: The user equipment to be migrated sends registration information to the core network gateway, where the registration information includes the equipment identifier of the user equipment to be migrated. Correspondingly, the core network gateway receives the registration information from the user equipment to be migrated.

The device identifier of the user equipment to be migrated included in the registration information is used to identify which or which user equipment to be migrated requests registration, that is, request to establish a connection with the backup service device. The device ID of the user equipment to be migrated may be a device ID, an IMSI, or a MAC address.

The user equipment to be migrated, when receiving the addressing information of the standby service device, sends registration information to the core network gateway according to the addressing information of the standby service device, for requesting registration on the backup service device.

Step S604, the core network gateway sends the registration information to the backup service device. Accordingly, the alternate service device receives the registration information from the core network gateway.

In a possible implementation manner, the core network gateway sending the registration information to the backup service device may further include the device identifier of the user equipment to be migrated. After receiving the registration information sent by the user equipment to be migrated, the core network gateway locates the geographic location of the user equipment to be migrated by using the cell information, determines the location information of the user equipment to be migrated, that is, the geographic location, and sends the location information to the backup service device. The registration information of the device identifier and the location information of the user equipment to be migrated is carried, so that the backup service device obtains the geographical location of the user equipment to be migrated. For example, the core network gateway determines the geographical location of the smart water meter installation, and sends the registration information of the device identifier and the location information of the user equipment to be migrated to the backup service device, so that the backup service device obtains the installation geographic location of the smart water meter.

Step S605, the standby service device sends registration confirmation information to the core network gateway. Accordingly, the core network gateway receives registration confirmation information from the alternate service device.

When receiving the registration information, the standby service device registers the user equipment to be migrated, and sends registration confirmation information to the core network gateway. The registration confirmation information is used to respond to the registration information sent by the core network gateway, that is, the backup service device receives the registration information, and registers the user equipment to be migrated, and the connection between the user equipment to be migrated and the first service device is successfully established.

Step S606: The core network gateway sends registration confirmation information to the user equipment to be migrated. Correspondingly, the user equipment to be migrated receives the first registration confirmation information from the core network gateway.

The registration confirmation information sent by the core network gateway to the user equipment to be migrated is used to respond to the registration information sent by the user equipment to be migrated, that is, the backup service device receives the registration information, and the backup service device registers the user equipment to be migrated. The connection with the first service device is established successfully.

If the connection between the user equipment to be migrated and the backup service device is successfully established, the user equipment to be migrated can report data to the backup service device through the core network gateway, that is, the data is first sent to the core. The network gateway sends the data to the backup service device by the core network gateway. The backup service device can also send commands to the user equipment to be migrated through the core network gateway.

It can be seen that, in the process shown in FIG. 6, the user equipment is not required to trigger the handover of the service device, and the connection between the user equipment and the user equipment is directly established by the backup service device to implement the handover of the service device.

It should be noted that, in the embodiment of the present application, the interaction process between the user equipment to be migrated and the base station is omitted, that is, the access network procedure is omitted. The base station is equivalent to a relay station between the user equipment to be migrated and the core network gateway.

The above describes the method of the embodiment of the present application in detail, and the apparatus of the embodiment of the present application is provided below.

FIG. 7 is a schematic diagram of a logical structure of a service device according to an embodiment of the present disclosure. The service device may be a first service device, that is, a backup service device. The service device 70 can include a processing module 701 and a first transceiver module 702.

The processing module 701 is configured to determine, in the case that the second service device is faulty, the user equipment to be migrated from the user equipment that establishes a connection with the second service device according to the user equipment migration policy.

The first transceiver module 702 is configured to notify the user equipment to be migrated to register with the first service device.

The processing module 701 is configured to perform step S401 in the embodiment shown in FIG. 4, where the first transceiver module is configured to perform step S402 in the embodiment shown in FIG.

In an implementation manner, the first transceiver module 702 is specifically configured to send, to the core network gateway, addressing information of the first service device and addressing information of the user equipment to be migrated, where the addressing information includes the device identifier and the network interconnection protocol. At least one of the IP addresses, the addressing information of the user equipment to be migrated is used to enable the core network gateway to send the addressing information of the first serving device to the user equipment to be migrated, where the addressing information of the first serving device is used to be migrated. The user equipment registers with the first service device.

In an implementation manner, the first transceiver module 702 is further configured to receive registration information from a core network gateway, where the registration information includes a device identifier of the user equipment to be migrated, and send registration confirmation information to the core network gateway according to the registration information, where the registration confirmation information is used. The connection between the user equipment to be migrated and the first service device is successfully established.

In an implementation manner, the service device 70 further includes a second transceiver module 703, configured to receive an authorization verification code from the second service device, and is further configured to receive real-time data from the second service device, and is also used to periodically The service device sends a request message, and is further configured to receive a response message sent by the second service device, and is further configured to receive a migration policy from the second service device.

In an implementation manner, the service device 70 further includes a third transceiver module 704, configured to send a fault estimation message, and further configured to receive a confirmation instruction for the fault estimation message.

The first transceiver module 702 is configured to execute S601, step S604, and step S605 in the embodiment shown in FIG. 6; the second transceiver module 703 is configured to perform step S501a-step S505a in the embodiment shown in FIG. 5a, FIG. 5b. Step S501b to step S505b in the illustrated embodiment; the third transceiver module 704 is configured to perform step S506b and step S507b in the embodiment shown in FIG. 5b.

It can be understood that the first transceiver module 702 is configured to communicate with a core network gateway, the second transceiver module 703 is configured to communicate with a second service device, and the third transceiver module 704 is configured to communicate with an administrator device.

FIG. 8 is a simplified schematic diagram of a physical structure of a service device according to an embodiment of the present application. The service device may be a first service device, that is, a backup service device. The service device 80 includes a transceiver 801, a processor 802, and a memory 803. The transceiver 801, the processor 802, and the memory 803 may be connected to one another via a bus 804, or may be connected in other manners. Related functions implemented by the processing module 701 shown in FIG. 7 may be implemented by one or more processors 802. The related functions implemented by the first transceiver module 702, the second transceiver module 703, and the third transceiver module 704 shown in FIG. 7 can be implemented by the transceiver 801.

The memory 803 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read only memory (EPROM), or A compact disc read-only memory (CD-ROM) for storing related instructions and data.

The transceiver 801 is configured to transmit data and/or signaling, as well as receive data and/or signaling. Application In the embodiment of the present application, in view of communicating with different devices, the transceiver 801 can be divided into a transceiver 8011 that communicates with a core network gateway, a transceiver 8012 that communicates with a primary service device, and a transceiver 8013 that communicates with an administrator device. . The transceiver 8011 is configured to perform S601, step S604, and step S605 in the embodiment shown in FIG. 6; the transceiver 8012 is configured to perform steps S501a-S505a in the embodiment shown in FIG. 5a, in the embodiment shown in FIG. 5b. Step S501b - step S505b; the transceiver 8013 is configured to perform step S506b and step S507b in the embodiment shown in Fig. 5b.

The processor 802 may include one or more processors, for example, including one or more central processing units (CPUs). In the case where the processor 802 is a CPU, the CPU may be a single core CPU, It can be a multi-core CPU. The processor 802 is configured to perform step S401 in the embodiment shown in FIG. 4, step S506a in the embodiment shown in FIG. 5a, and step S508b in the embodiment shown in FIG. 5b.

The memory 803 is used to store program codes and data of the service device switching device 80.

For details about the steps performed by the processor 802 and the transceiver 801, refer to the description of the embodiment shown in FIG. 4 to FIG. 6 , and details are not described herein again.

It will be appreciated that Figure 8 only shows a simplified design of the service device. In practical applications, the service device may also include other necessary components, including but not limited to any number of transceivers, processors, controllers, memories, communication units, etc., and all devices that can implement the present application are in this application. Within the scope of protection.

FIG. 9 is a schematic diagram of a logical structure of a core network gateway according to an embodiment of the present application. The core network gateway may be a PGW. The core network gateway 90 can include a first transceiver module 901 and a second transceiver module 902.

The first transceiver module 901 is configured to receive, by the first serving device, addressing information of the first serving device and addressing information of the user device to be migrated, where the addressing information includes at least one of a device identifier and an IP address.

The second transceiver module 902 is configured to send the addressing information of the first service device to the user equipment to be migrated according to the addressing information of the user equipment to be migrated, where the addressing information of the first service device is used to be The migration user device registers with the first service device.

In an implementation manner, the second transceiver module 902 is further configured to receive registration information from the user equipment to be migrated.

The first transceiver module 901 is further configured to send the registration information to the first service device, where the registration information includes a device identifier of the user equipment to be migrated.

The first transceiver module 901 is further configured to receive registration confirmation information from the first serving device.

The second transceiver module 902 is further configured to send the registration confirmation information to the user equipment to be migrated, where the registration confirmation information is used to indicate that the connection between the user equipment to be migrated and the first service device is successfully established. .

In an implementation, the core network gateway 90 may further include a processing module 903. The processing module 903 is configured to determine a device mode of the user equipment to be migrated, where the device mode is a discontinuous reception mode, or an extended discontinuous reception mode, or a power saving mode.

The first transceiver module 901 is configured to perform step S601, step S604, and step S605 in the embodiment shown in FIG. 6; the second transceiver module 902 is configured to perform step S602, step S603, and step in the embodiment shown in FIG. S606. It can be understood that the first transceiver module 901 is configured to communicate with a backup service device, and the second transceiver module 902 is configured to communicate with a user device to be migrated.

FIG. 10 is a simplified schematic diagram of a physical structure of a core network gateway according to an embodiment of the present application. The core network gateway may be a PGW. The core network gateway 100 includes a transceiver 1001, a processor 1002, and a memory 1003. The transceiver 1001, the processor 1002, and the memory 1003 may be connected to one another via a bus 1004 or may be connected in other manners. The related functions implemented by the first transceiver module 901 and the second transceiver module 902 shown in FIG. 9 can be implemented by the transceiver 1001. Related functions implemented by the processing module 903 shown in FIG. 9 may be implemented by one or more processors 1002.

The memory 1003 includes, but is not limited to, a RAM, a ROM, an EPROM, a CD-ROM, and the memory 1003 is used for related instructions and data.

The transceiver 1001 is configured to transmit data and/or signaling, as well as receive data and/or signaling. Application In the embodiment of the present application, in view of communicating with different devices, the transceiver 1001 can be divided into a transceiver 1001a that communicates with the backup service device and a transceiver 1001b that communicates with the user device to be migrated. The transceiver 1001a is configured to perform step S601, step S604, and step S605 in the embodiment shown in FIG. 6; the transceiver 1001b is configured to perform step S602, step S603, and step S606 in the embodiment shown in FIG. 6.

The processor 1002 may include one or more processors, for example, including one or more CPUs. In the case where the processor 1002 is a CPU, the CPU may be a single core CPU or a multi-core CPU. In the embodiment of the present application, the processor 1002 is configured to determine a device mode of the user equipment to be migrated.

The memory 1003 is used to store program codes and data of the core network gateway 100.

It will be appreciated that Figure 10 only shows a simplified design of the core network gateway. In practical applications, the core network gateway may also include other necessary components, including but not limited to any number of transceivers, processors, controllers, memories, communication units, etc., and all devices that can implement the present application are in this embodiment. Within the scope of protection of the application.

The embodiment of the present application further provides a service device switching system, including a first service device, a second service device, a core network gateway, and a user device to be migrated.

One of ordinary skill in the art can understand all or part of the process of implementing the above embodiments, which can be completed by a computer program to instruct related hardware, the program can be stored in a computer readable storage medium, when the program is executed The flow of the method embodiments as described above may be included. The foregoing storage medium includes various media that can store program codes, such as a ROM or a random access memory RAM, a magnetic disk, or an optical disk. Accordingly, yet another embodiment of the present application provides a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the methods described in the various aspects above.

Yet another embodiment of the present application also provides a computer program product comprising instructions that, when executed on a computer, cause the computer to perform the methods described in the various aspects above.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing module, or each unit may exist physically separately, or two or more units may be integrated into one unit.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in or transmitted by a computer readable storage medium. The computer instructions may be from a website site, computer, server or data center via a wired (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) Another website site, computer, server, or data center for transmission. The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.

Claims

A service device switching method, comprising:

In the case that the second service device is faulty, the first service device determines, according to the user equipment migration policy, the user equipment to be migrated from the user equipment that establishes a connection with the second service device;

The first service device notifies the user equipment to be migrated to register with the first service device.
The method according to claim 1, wherein the notifying the user equipment to be migrated to the first service device by the first service device comprises:

Transmitting, by the first serving device, addressing information of the first serving device and addressing information of the user equipment to be migrated to a core network gateway, where the addressing information includes a device identifier and a network interconnection protocol IP address At least one of the addressing information of the user equipment to be migrated is used to enable the core network gateway to send addressing information of the first serving device to the user equipment to be migrated, and the addressing of the first serving device The information is used to register the user equipment to be migrated with the first service device.
The method according to claim 1 or 2, wherein after the first serving device notifies the user equipment to be migrated to register with the first serving device, the method further includes

The first service device receives the registration information from the core network gateway, where the registration information includes the device identifier of the user equipment to be migrated;

The first service device sends the registration confirmation information to the core network gateway according to the registration information, where the registration confirmation information is used to indicate that the connection between the user equipment to be migrated and the first service device is successfully established.
The method according to claim 3, wherein before the first serving device receives the registration information from the core network gateway, the method further includes:

The first service device sends an authorization check code to the core network gateway, where the authorization check code is used by the core network gateway to perform security check on the first service device.
The method according to any one of claims 1 to 4, wherein before the second service device fails, the method further comprises:

Receiving, by the first service device, real-time data from the second service device, where the real-time data includes a device identifier of a user equipment that establishes a connection with the second service device, where the real-time data is used by the first service device Data synchronization with the second service device.
The method according to claim 5, wherein the real-time data further includes attribute information of the user equipment that establishes a connection with the second service device, where the attribute information includes user interaction information, rule information, and data report information. At least one of the area information, the device type, and the activity information;

Determining, by the first service device, the user equipment to be migrated from the user equipment that establishes a connection with the second service device according to the user equipment migration policy, including:

The first service device selects a user equipment that satisfies the user equipment migration policy from the user equipment that establishes a connection with the second service device according to the attribute information of the user equipment that establishes the connection with the second service device, and satisfies the user. The user equipment of the device migration policy is determined as the user equipment to be migrated.
The method according to any one of claims 1 to 6, wherein before the second service device fails, the method further comprises:

The first serving device periodically sends a request message to the second serving device;

If the first serving device does not receive a response message from the second serving device within a preset time period, the first serving device determines that the second serving device is faulty.
The method according to any one of claims 1 to 6, wherein before the second service device fails, the method further comprises:

The first serving device periodically sends a request message to the second serving device;

If the first serving device does not receive a response message from the second serving device within a preset time period, the first serving device sends a fault estimation message, and receives an acknowledgement for the fault estimation message. In the case of an instruction, the second service device is determined to be faulty.
The method according to any one of claims 1 to 6, wherein before the second service device fails, the method further comprises:

The first service device receives a migration policy from the second service device, and determines the migration policy as a user equipment migration policy.
The method according to claim 9, wherein the migration policy comprises at least one of an interactive migration policy, a rule triggered migration policy, a data reporting migration policy, a regional migration policy, a type migration policy, and an activity migration policy. .
A service device switching method, comprising:

The core network gateway receives the addressing information of the first service device and the addressing information of the user equipment to be migrated from the first serving device, where the addressing information includes at least one of a device identifier and an IP address;

Transmitting, by the core network gateway, addressing information of the first serving device to the user equipment to be migrated according to the addressing information of the user equipment to be migrated, where the addressing information of the first serving device is used to enable the The user equipment to be migrated registers with the first service device.
The method according to claim 11, wherein after the core network gateway sends the addressing information of the first service device to the user equipment to be migrated according to the addressing information of the user equipment to be migrated, The method further includes:

The core network gateway receives the registration information from the user equipment to be migrated, and sends the registration information to the first service device, where the registration information includes the device identifier of the user equipment to be migrated;

The core network gateway receives the registration confirmation information from the first service device, and sends the registration confirmation information to the user equipment to be migrated, where the registration confirmation information is used to indicate the user equipment to be migrated and the first The connection between a service device is established successfully.
The method according to claim 11 or 12, wherein the core network gateway sends the addressing information of the first service device to the user equipment to be migrated according to the addressing information of the user equipment to be migrated. Previously, the method further includes:

Determining, by the core network gateway, a device mode of the user equipment to be migrated, where the device mode is a discontinuous reception mode, or an extended discontinuous reception mode, or a power saving mode;

And the sending, by the core network gateway, the addressing information of the first serving device to the user equipment to be migrated according to the addressing information of the user equipment to be migrated, including:

If the device mode is the discontinuous reception mode, the core network gateway immediately sends the addressing information of the first service device to the user equipment to be migrated according to the addressing information of the user equipment to be migrated;

If the device mode is the extended discontinuous reception mode, the core network gateway buffers an IP address of the first service device, and according to the addressing information of the user equipment to be migrated in a next paging time window Transmitting, by the user equipment to be migrated, addressing information of the first service device;

If the device mode is the power saving mode, the core network gateway, according to the data reported by the user equipment to be migrated, is to be migrated according to the addressing information of the user equipment to be migrated. The user equipment sends the addressing information of the first service device.
The method according to any one of claims 11 to 13, wherein the core network gateway sends the first service device to the user equipment to be migrated according to the addressing information of the user equipment to be migrated. Before addressing the information, the method further includes:

Receiving, by the core network gateway, an authorization check code from the first service device;

The core network gateway performs security check on the first service device according to the authorization check code;

And if the first service device security check is passed, the core network gateway sends the addressing information of the first service device to the user equipment to be migrated according to the addressing information of the user equipment to be migrated.
A service device switching device, comprising: a processing module and a first transceiver module;

The processing module is configured to determine, according to the user equipment migration policy, the user equipment to be migrated from the user equipment that establishes a connection with the second service device according to the user equipment migration policy;

The first transceiver module is configured to notify the user equipment to be migrated to register with the first service device.
The device of claim 15 wherein:

When the first transceiver module is configured to notify the user equipment to be migrated to register with the first service device, specifically, the method is used to send the addressing information of the first service device and the user to be migrated to a core network gateway. Device addressing information, the addressing information includes at least one of a device identifier and an IP address, and the addressing information of the user equipment to be migrated is used to send the core network gateway to the user equipment to be migrated. Addressing information of the first service device, the addressing information of the first service device is used to register the user equipment to be migrated with the first service device.
The device according to claim 15 or 16, wherein the first transceiver module is configured to notify the user equipment to be migrated to register with the first service device, and further to use the core network gateway Receiving registration information, the registration information includes a device identifier of the user equipment to be migrated; sending, by the first transceiver module, registration confirmation information to the core network gateway according to the registration information, where the registration confirmation information is used to indicate The connection between the user equipment to be migrated and the first service device is successfully established.
The device according to claim 17, wherein the first transceiver module is configured to send an authorization check to the core network gateway by using the first transceiver module before receiving the registration information from the core network gateway. And the authorization check code is used by the core network gateway to perform security check on the first service device.
The device according to any one of claims 15 to 18, wherein the device further comprises a second transceiver module,

The second transceiver module is configured to receive real-time data from the second service device before the second service device fails, where the real-time data includes a device identifier of a user device that establishes a connection with the second service device, The real-time data is used for data synchronization between the first service device and the second service device.
The device according to claim 19, wherein the real-time data further includes attribute information of a user equipment that establishes a connection with the second service device, where the attribute information includes user interaction information, rule information, and data report information. At least one of the area information, the device type, and the activity information;

The processing module is configured to determine, according to a user equipment migration policy, a user equipment that is to be migrated from a user equipment that establishes a connection with the second service device, specifically, according to an attribute of the user equipment that establishes a connection with the second service device. The user equipment that meets the user equipment migration policy is selected from the user equipment that is connected to the second service device, and the user equipment that meets the user equipment migration policy is determined as the user equipment to be migrated.
The device according to any one of claims 15 to 20, wherein the second transceiver module is further configured to periodically send a request message to the second serving device;

And if the first serving device does not receive the response message from the second serving device within the preset time period, the processing module is further configured to determine that the second service device is faulty.
The device according to any one of claims 15 to 20, wherein the device further comprises a third transceiver module,

The second transceiver module is further configured to periodically send a request message to the second serving device;

If the first serving device does not receive the response message from the second serving device within the preset time period, the third transceiver module is configured to send a fault estimation message, and receive the fault in the third transceiver module. The processing module is further configured to determine that the second service device is faulty, in the case of a confirmation instruction for the fault estimation message.
The device according to any one of claims 15 to 20, wherein the processing module is configured to determine, before the user equipment to be migrated, from the user equipment that establishes a connection with the second service device according to the user equipment migration policy, The second transceiver module is further configured to receive a migration policy from the second service device, where the processing module is further configured to determine the migration policy as a user equipment migration policy.
The apparatus according to claim 23, wherein the migration policy comprises at least one of an interactive migration policy, a rule triggered migration policy, a data report migration policy, a regional migration policy, a type migration policy, and an activity migration policy. .
A first service device, comprising: a processor, a transceiver, and a memory, wherein the transceiver is configured to receive and transmit information, the memory stores computer execution instructions, and the processor communicates with the A memory is coupled to the transceiver, the processor executing computer executed instructions stored in the memory to cause the first service device to perform the method of any of claims 1-10.
A service device switching device, comprising: a first transceiver module and a second transceiver module;

The first transceiver module is configured to receive, by the first serving device, addressing information of the first serving device and addressing information of the user device to be migrated, where the addressing information includes at least one of a device identifier and an IP address. Species

The second transceiver module is configured to send the addressing information of the first service device to the user equipment to be migrated according to the addressing information of the user equipment to be migrated, where the addressing information of the first service device is used. The user equipment to be migrated is registered with the first service device.
The device of claim 26, wherein said device further comprises a processing module,

The processing module is configured to determine a device mode of the user equipment to be migrated, where the device mode is a discontinuous reception mode, or an extended discontinuous reception mode, or a power saving mode;

If the device mode is the discontinuous reception mode, the second transceiver module is configured to send the first service device to the user equipment to be migrated according to the addressing information of the user equipment to be migrated. Addressing information;

If the device mode is the extended discontinuous reception mode, the processing module is configured to buffer addressing information of the first serving device, and the second transceiver module is specifically configured to use the next paging time window according to the Transmitting the addressing information of the first user equipment to the user equipment to be migrated;

If the device mode is the power saving mode, the second transceiver module is specifically configured to: according to the information that is reported by the user equipment to be migrated, according to the addressing information of the user equipment to be migrated The user equipment to be migrated sends the addressing information of the first service device.
A core network gateway, comprising: a module, a transceiver, and a memory, wherein the transceiver is configured to receive and transmit information, the memory stores computer execution instructions, and the processor communicates with the memory through a bus and The transceiver is coupled, the processor executing computer executed instructions stored in the memory to cause the core network gateway to perform the method of any of claims 11-14.
A computer readable storage medium, characterized in that the computer storage medium stores a computer program, the computer program comprising program instructions that, when executed by a module, cause the module to perform as claimed in claims 1-10 The method of any of the preceding claims.
A computer readable storage medium, characterized in that the computer storage medium stores a computer program, the computer program comprising program instructions that, when executed by a module, cause the module to perform as claimed in claims 11-14 The method of any of the preceding claims.