CN115842776A

CN115842776A - Hot backup method and device, computer readable storage medium and user equipment

Info

Publication number: CN115842776A
Application number: CN202110932809.8A
Authority: CN
Inventors: 韩立锋
Original assignee: Spreadtrum Communications Shanghai Co Ltd
Current assignee: Spreadtrum Communications Shanghai Co Ltd
Priority date: 2021-08-13
Filing date: 2021-08-13
Publication date: 2023-03-24

Abstract

A hot backup method and device, a computer readable storage medium and user equipment are provided, wherein the hot backup method comprises the following steps: monitoring a backup trigger event; and responding to the monitored backup trigger event, and sending a first message, wherein the first message is used for indicating the backup user equipment to carry out data transmission, and the first message comprises an identifier of the service needing to be backed up. The technical scheme of the invention can carry out hot backup between the UE in time.

Description

Hot backup method and device, computer readable storage medium and user equipment

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a hot backup method and apparatus, a computer-readable storage medium, and a user equipment.

Background

In industrial control and other scenarios, the requirement on the reliability of transmission is relatively high, and one solution is to ensure the reliability of transmission by using a hot backup method among a plurality of User Equipments (UEs).

However, how to perform hot backup between UEs in time is a problem to be solved.

Disclosure of Invention

The technical problem solved by the invention is how to perform hot backup between the UEs in time.

In order to solve the foregoing technical problem, an embodiment of the present invention provides a hot backup method, where the hot backup method includes: monitoring a backup trigger event; and responding to the monitored backup trigger event, and sending a first message, wherein the first message is used for indicating the backup user equipment to carry out data transmission, and the first message comprises an identifier of the service needing to be backed up.

Optionally, the backup trigger event includes one or more of the following: the data transmission failure times reach a first preset number; the data receiving failure times reach a second preset number; when the wireless link is monitored, a third preset number of continuous out-of-step indications occur; and when the wireless link is monitored, the third preset number of out-of-step instructions occur continuously, and the started first timer is overtime.

Optionally, the first message further includes receiving status information of downlink data.

Optionally, the receiving status information includes a maximum sequence number of successfully received consecutive data packets, an unsuccessfully received data packet sequence number, and a successfully received discontinuous data packet sequence number.

Optionally, the first message further includes sending status information of uplink data.

Optionally, the sending status information includes a maximum sequence number of a successfully sent continuous data packet, an unsuccessfully sent data packet sequence number, and a successfully received discontinuous data packet sequence number.

Optionally, the sending the first message includes a backup reason, where the backup reason includes one or more of the following: data transmission failure, data reception failure, radio link degradation, radio link failure, and terminal movement.

Optionally, the sending the first message includes: sending the first message through a direct communication interface with the backup user device; or forwarding the first message through a base station, where the first message includes an identifier of a cell where the backup user equipment is located or an identifier of a connected base station.

Optionally, the hot backup method further includes: sending a fourth message, wherein the fourth message instructs the backup user equipment to cancel data transmission.

Optionally, the sending the fourth message includes: sending the fourth message through a direct communication interface with the backup user equipment; or forwarding the fourth message through the base station, where the fourth message includes an identifier of a cell where the backup user equipment is located or an identifier of a connected base station.

Optionally, the first message further includes a backup type, and the backup type is selected from a temporary backup and a permanent backup.

The embodiment of the invention also discloses a hot backup method, which comprises the following steps: receiving a first message, wherein the first message comprises an identifier of a service needing to be backed up; and responding to the received first message, and performing data transmission on the data of the service indicated by the identification of the service needing backup.

Optionally, the hot backup method further includes: and sending a second message, wherein the second message indicates that the data transmission is allowed or indicates that the backup is failed.

Optionally, the hot backup method further includes: and sending a third message to the network equipment, wherein the third message is used for indicating the occurrence of the backup event to the network equipment.

Optionally, the third message includes one or more of: an identity of a primary user equipment, an identity of a backup user equipment, and a backup reason.

Optionally, the hot backup method further includes: receiving a sixth message from the network device, the sixth message indicating to perform a backup, the sixth message including a backup type, the backup type being selected from a temporary backup and a permanent backup.

Optionally, the hot backup method further includes: and when the backup type is temporary backup, starting a second timer.

Optionally, the hot backup method further includes: and if the fourth message is not received and the second timer is overtime, the backup type is adjusted from the temporary backup to the permanent backup, and the fourth message indicates that the data transmission is cancelled.

Optionally, the hot backup method further includes: converting the device type into a master user device; or starting a third timer, and converting the device type into the primary user device after the third timer is overtime.

Optionally, the hot backup method further includes: and sending a fifth message to the network equipment, wherein the fifth message indicates the conversion of the equipment type, and the fifth message comprises the identification of the primary user equipment.

The embodiment of the invention also discloses a hot backup device, which comprises: the monitoring module is used for monitoring a backup trigger event; and the sending module is used for responding to the monitored backup triggering event and sending a first message, wherein the first message is used for indicating the backup user equipment to carry out data transmission and comprises the identification of the service needing to be backed up.

The embodiment of the invention also discloses a hot backup device, which comprises: a receiving module, configured to receive a first message, where the first message includes an identifier of a service that needs to be backed up; and the data transmission module is used for responding to the received first message and performing data transmission aiming at the service data indicated by the identification of the service needing to be backed up.

The embodiment of the invention also discloses a hot backup updating method, which comprises the following steps: sending a seventh message, wherein the seventh message is used for inquiring backup user equipment; receiving an eighth message, the eighth message including an identification of the backup user equipment.

Optionally, the seventh message further includes an identifier of a service that needs to be backed up.

The embodiment of the invention also discloses a hot backup updating method, which comprises the following steps: receiving a seventh message, wherein the seventh message is used for inquiring backup user equipment; and sending an eighth message, where the eighth message includes an identifier of the backup user equipment, and the identifier of the backup user equipment corresponds to the identifier of the service to be backed up in the seventh message.

Optionally, after receiving the seventh message, the method further includes: and selecting one or more user equipment from a user equipment group where the main user equipment is located to serve as the backup user equipment.

The embodiment of the invention also discloses a hot backup updating method, which comprises the following steps: broadcasting a ninth message, wherein the ninth message is used for indicating to search for backup user equipment and comprises an identifier of a service needing to be backed up; receiving a tenth message, wherein the tenth message contains an indication which can be used as a candidate backup user device, determining the backup user device according to the tenth message, or sending an eleventh message, wherein the eleventh message contains a candidate backup user identifier, receiving a twelfth message, and determining the candidate backup user device.

Optionally, the sending the eleventh message includes: detecting candidate backup equipment, wherein the candidate backup equipment can transmit data of the service indicated by the identification of the service needing to be backed up; and sending the eleventh message containing the candidate backup equipment identification to the network equipment.

Optionally, the detecting the candidate backup device further includes: acquiring an initial backup relation when registering to a network; and/or receiving a non-access stratum signaling, wherein the non-access stratum signaling carries the updated backup relationship.

The embodiment of the invention also discloses a hot backup updating method, which comprises the following steps: receiving a ninth message, wherein the ninth message is used for indicating to search for backup user equipment and comprises an identifier of a service needing to be backed up; sending a tenth message indicating an indication of a candidate backup user device, the candidate backup user device for determining the backup user device.

Optionally, the sending the tenth message includes: judging whether a backup relation exists between the master user equipment and the master user equipment; and if the backup relation exists with the main user equipment, sending the tenth message.

Optionally, before the determining whether the backup relationship exists with the primary user device, the method further includes: acquiring an initial backup relationship when registering to a network; and/or receiving a non-access stratum signaling, wherein the non-access stratum signaling carries the updated backup relationship.

The embodiment of the invention also discloses a hot backup updating device, which comprises: a sending module, configured to send a seventh message, where the seventh message is used to query a backup user equipment; a receiving module, configured to receive an eighth message, where the eighth message includes an identifier of the backup user equipment.

The embodiment of the invention also discloses another hot backup updating device, which comprises: a receiving module, configured to receive a seventh message, where the seventh message is used to query a backup user equipment; a sending module, configured to send an eighth message, where the eighth message includes an identifier of the backup user equipment, and the identifier of the backup user equipment corresponds to the identifier of the service that needs to be backed up in the seventh message.

The embodiment of the invention also discloses a hot backup updating device, which comprises: a broadcast module, configured to broadcast a ninth message, where the ninth message is used to indicate to search for a backup user equipment, and the ninth message includes an identifier of a service that needs to be backed up; and the backup user equipment determining module is used for receiving a tenth message, wherein the tenth message contains an instruction which can be used as candidate backup user equipment, determining the backup user equipment according to the tenth message, or sending an eleventh message, wherein the eleventh message contains a candidate backup user identifier, receiving a twelfth message, and determining the candidate backup user equipment.

The embodiment of the invention also discloses a hot backup updating device, which comprises: a receiving module, configured to receive a ninth message, where the ninth message is used to indicate to search for a backup user equipment, and the ninth message includes an identifier of a service that needs to be backed up; a sending module, configured to send a tenth message, where the tenth message indicates an indication that the candidate backup user equipment can be used as an indication of the candidate backup user equipment, and the candidate backup user equipment is configured to determine the backup user equipment.

The embodiment of the invention also discloses a computer readable storage medium, on which a computer program is stored, and the computer program executes the steps of the hot backup method or the steps of the hot backup updating method when being executed by a processor.

The embodiment of the invention also discloses user equipment which comprises a memory and a processor, wherein the memory is stored with a computer program capable of running on the processor, and the processor executes the steps of the hot backup method or the steps of the hot backup updating method when running the computer program.

Compared with the prior art, the technical scheme of the embodiment of the invention has the following beneficial effects:

in the technical scheme of the invention, a backup trigger event is monitored; and responding to the monitored backup trigger event, and sending a first message, wherein the first message is used for indicating the backup user equipment to carry out data transmission, and the first message comprises an identifier of the service needing to be backed up. In the technical scheme of the invention, the backup trigger event can indicate that hot backup needs to be carried out, so that the user equipment sends the first message to the backup user equipment for data transmission after monitoring the backup trigger event, and the hot backup can be carried out in time to ensure the reliability of transmission.

Further, the first message further includes receiving status information of downlink data or sending status information of uplink data. According to the technical scheme, the receiving state information of the downlink data or the sending state information of the uplink data is sent to the backup user equipment in the first message, so that the backup user equipment can receive or send the data packet according to the indication of the first message, packet loss or repeated packet sending is avoided, and the reliability of transmission is further realized.

Drawings

FIG. 1 is a flow chart of a hot backup method according to an embodiment of the present invention;

FIG. 2 is a flow chart of another hot backup method of an embodiment of the present invention;

FIG. 3 is a diagram illustrating an exemplary application scenario of the present invention;

FIG. 4 is a schematic structural diagram of a hot-standby apparatus according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of another hot-standby apparatus according to an embodiment of the present invention;

FIG. 6 is a flowchart of a hot backup update method according to an embodiment of the present invention;

fig. 7 is a flowchart of another hot backup update method according to an embodiment of the present invention.

Detailed Description

As described in the background, how to perform hot backup between UEs in time is a problem to be solved.

In the technical scheme of the invention, the backup trigger event can indicate that hot backup needs to be carried out, so that the user equipment sends the first message to the backup user equipment for data transmission after monitoring the backup trigger event, and the hot backup can be carried out in time to ensure the reliability of transmission.

The main user equipment in the embodiments of the present invention refers to a user equipment that performs service data transmission, such as receiving or sending data. The service data is data that needs to be transmitted in a backup mode. The backup transmission refers to transmission by a backup user equipment.

The backup user equipment in the embodiment of the present invention refers to user equipment capable of performing backup transmission on the service data of the main equipment. The backup user equipment and the main user equipment are in a hot backup relationship, and the backup user equipment and the main user equipment can transmit data of the same task.

The term "hot backup" in the embodiments of the present invention refers to a process in which the primary user equipment and the backup user equipment transmit data of the same service.

The technical scheme of the invention can be applied to fifth generation (5Generation, 5G) communication systems, 4G and 3G communication systems, and various future new communication systems such as 6G and 7G.

In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in detail below.

Fig. 1 is a flowchart of a hot backup method according to an embodiment of the present invention.

The hot backup method of the embodiment of the invention can be used for the user equipment side, particularly the main user equipment side, namely, the main user equipment can execute all the steps of the method.

Specifically, the hot backup method may include the steps of:

step 101: monitoring a backup trigger event;

step 102: and responding to the monitored backup trigger event, and sending a first message, wherein the first message is used for indicating the backup user equipment to carry out data transmission, and the first message comprises an identifier of the service needing to be backed up.

It should be noted that the sequence numbers of the steps in this embodiment do not represent a limitation on the execution sequence of the steps.

It is understood that in a specific implementation, the hot backup method may be implemented by using a software program running in a processor integrated inside a chip or a chip module.

In the embodiment of the invention, the master user equipment can monitor the backup trigger event. Monitoring a backup trigger event means that a hot backup of data is required, or in other words, the backup trigger event indicates a data backup.

The master user equipment sends a first message to the backup user equipment after monitoring the backup triggering event, wherein the first message comprises the identification of the service needing to be backed up. And the backup user equipment performs data transmission aiming at the data of the service indicated in the first message.

In one non-limiting embodiment, the backup trigger event includes one or more of: triggering event one: the data transmission failure times reach a first preset number; and triggering an event II: the data receiving failure times reach a second preset number; triggering an event III: when the wireless link is monitored, a third preset number of out-of-step instructions occur continuously; and C, triggering an event IV: and when the wireless link is monitored, the third preset number of out-of-step instructions occur continuously, and the started first timer is overtime.

In a specific embodiment, UE1 serves as primary user equipment for transmitting data of service 1. UE2 is a backup user equipment for UE 1. If a triggering event for backup occurs, the backup is triggered, i.e. the backup UE2 of UE1 performs data transmission. The trigger event includes one or more of the following: triggering event one: if the data transmission of the UE1 fails N1 times, specifically, HARQ retransmission may be N2 times, or RLC PDU retransmission may be N3 times; and triggering an event II: if the data reception of the UE1 fails for N4 times, the number of reception failures may be PDCP PDU, RLC PDU, MAC PCU; triggering an event III: monitoring a wireless link of UE1, wherein N5 continuous out-of-step indications occur; and C, triggering an event IV: and monitoring the wireless link of the UE1, and after N5 continuous out-of-step instructions occur, starting a timer T1 to time out.

The UE1 sends a message 1 (i.e. a first message) to the UE2, and notifies the UE2 to perform backup, where the message 1 includes a service identifier to be backed up.

Further, the message 1 further includes a backup reason, where the backup reason includes one or more of the following items: data transmission failure, data reception failure, radio link degradation, radio link failure, and terminal movement. The terminal moving means that the terminal moves to another area and cannot continue to support the service 1 (that is, the service currently being performed by the primary user equipment), or the terminal moves to another cell. The backup reason corresponds to a backup trigger event that triggers the backup. For example, if the triggering event is that data transmission of UE1 fails N1 times, the backup reason is that data transmission fails; the triggering event is the wireless link monitoring of the UE1, and if N5 continuous out-of-step instructions occur, the backup reason is the wireless link deterioration, and the like.

It should be noted that N1, N2, N3, N4, and N5 are all integers greater than zero, and specific numerical values may be set according to an actual application scenario, which is not limited in this embodiment of the present invention.

In one non-limiting embodiment, the first message further includes reception status information of downlink data.

Further, the receiving status information includes the maximum sequence number of the successfully received continuous data packet, the sequence number of the unsuccessfully received data packet and the sequence number of the successfully received discontinuous data packet.

In this embodiment, if the service 1 is downlink transmission, the first message may include receiving status information of downlink Data, where the downlink Data may be a Protocol Data Unit (PDU) of different Protocol layers, for example, a receiving status of a Packet Data Convergence layer Protocol (PDCP) Protocol Data Unit (PDU), and the receiving status information includes receiving status information of a successfully received Data Packet and a receiving status information of an unsuccessfully received Data Packet. For example, the reception status information includes: the maximum sequence number of successfully received continuous data packets is 100, the sequence numbers of unsuccessfully received data packets are 101, 103 and 104, and the sequence numbers of successfully received discontinuous data packets are 102 and 105.

In another non-limiting embodiment, the first message further includes transmission status information of uplink data. The upstream Data may be Protocol Data Units (PDUs) of different Protocol layers.

Further, the sending status information includes the maximum sequence number of the successfully sent continuous data packet, the sequence number of the unsuccessfully sent data packet and the sequence number of the successfully received discontinuous data packet.

In this embodiment, if the service 1 is uplink transmission, the first message may include sending status information of uplink data, where the sending status information may include a maximum sequence number of a successful continuous data packet, information of a successful discontinuous data packet that has been sent, and information of a data packet that has not been successfully sent. For example, transmitting the status information includes: the data packets before the data packet number 10 have been successfully transmitted, the data packet number 15 has been successfully transmitted, and the data packets number 11, 12, 13, and 14 have not been successfully transmitted.

In one non-limiting embodiment, step 102 shown in FIG. 1 may include the following steps: sending the first message through a direct communication interface with the backup user device; or forwarding the first message through a base station, where the first message includes an identifier of a cell where the backup user equipment is located or an identifier of a connected base station.

In this embodiment, the first message may be transmitted through a direct communication interface between UE1 and UE2, for example, a PC5 interface. Or may be forwarded through a base station, if UE1 and UE2 are connected to different base stations, the first message may further include an identifier of a cell or base station where UE2 is located, where the identifier of the cell or base station is used for transmitting a route of the first message.

In one non-limiting embodiment, the method shown in FIG. 1 may further include the steps of: sending a fourth message, wherein the fourth message instructs the backup user equipment to cancel data transmission.

Further, sending the fourth message through a direct communication interface with the backup user equipment; or forwarding the fourth message through the base station, where the fourth message includes an identifier of a cell where the backup user equipment is located or an identifier of a connected base station.

In this embodiment, if the data transmission/reception or the radio link status or the like in the UE1 is restored, the UE1 may instruct the UE2 to cancel the backup. UE1 sends a message 4 (i.e. a fourth message) to UE2 indicating the cancellation of the backup operation. The message 4 may be transmitted over a direct communication interface between the UEs, such as a PC5 interface. Or may be forwarded by a base station, if UE1 and UE2 are connected to different base stations, message 4 further includes an identifier of a cell or base station where UE2 is located, and the identifier of the cell or base station is used for routing message 4.

In a specific implementation, the fourth message may be a message between UEs, such as a Radio Resource Control (RRC) message, a Media Access Control (MAC) Control Element (CE), direct link Control Information (SCI), and the like, or may be a message between a UE and a base station.

The embodiment of the invention can realize the backup operation in time and rapidly by the triggering of the backup event between the main user equipment and the backup user equipment, the notification of the backup and other operations, thereby ensuring the transmission reliability of the service data.

In one non-limiting embodiment, the first message further includes a backup type, the backup type selected from the group consisting of a temporary backup and a permanent backup.

In this embodiment, when the backup type is temporary backup, the backup user equipment is used as backup equipment to perform data transmission; and when the backup type is long backup, the backup user equipment is converted into the main user equipment for data transmission.

In a specific implementation, the backup type corresponds to a trigger event. For example, the backup types corresponding to the trigger event one, the trigger event two and the trigger event four are permanent backups; and the backup type corresponding to the triggering event III is temporary backup.

Fig. 2 is a flowchart of another hot backup method according to an embodiment of the present invention.

The hot backup method of the embodiment of the invention can be used for a user equipment side, particularly for a backup user equipment side, namely, the backup user equipment can execute each step of the method.

Specifically, the hot backup method may include the steps of:

step 201: receiving a first message, wherein the first message comprises an identifier of a service needing to be backed up;

step 202: and responding to the received first message, and performing data transmission aiming at the data of the service indicated by the identification of the service needing to be backed up.

In this embodiment, the UE2 serves as a backup user equipment, and the UE2 starts to perform backup after receiving the first message. Specifically, if the first message indicates to perform backup of service 1, UE2 starts to transmit data of service 1, that is, to transmit or receive data packets of service 1.

In one non-limiting embodiment, the method shown in FIG. 2 may further include the steps of: and sending a second message, wherein the second message indicates that the data transmission is allowed or indicates that the backup is failed.

In a specific implementation, UE2 may send message 2 (i.e., the second message) to UE1, indicating to receive the backup application, and may perform backup of service 1.

Or, due to the self-service, the UE2 may also send the message 2 to indicate that the backup fails, that is, the UE2 cannot perform the backup of the data. In this case, UE1 selects another UE to transmit the first message.

In one non-limiting embodiment, the method shown in FIG. 2 may further include the steps of: and sending a third message to the network equipment, wherein the third message is used for indicating the occurrence of the backup event to the network equipment.

Further, the third message includes one or more of: an identity of a primary user equipment, an identity of a backup user equipment, and a backup reason.

In this embodiment, the UE2 may notify the network side of the occurrence of the backup event. Specifically, UE2 may send message 3 (i.e., a third message) to the base station or core network device indicating that a backup event has occurred.

Message 3 may be just one message indicating that backup action is taking place. The message 3 may also include at least one of the identity of the UE1, the identity of the UE2, and the backup cause value. The base station or the core network device may perform operations such as radio link reply and handover of the UE1 according to the received message 3, so as to ensure reliable transmission of data.

In a specific implementation, the message 3 may be a RRC message, a message between UEs such as MAC CE and SCI, or a message between a UE and a base station.

In one non-limiting embodiment, the first message further includes a backup type; or, the UE2 receives a sixth message from the network device, where the sixth message indicates to perform backup, and the sixth message includes a backup type.

Further, when the backup type is temporary backup, the UE2 starts a second timer.

Further, if a fourth message is not received and the second timer is overtime, the UE2 adjusts the backup type from the temporary backup to the permanent backup, and the fourth message indicates to cancel the data transmission.

Further, UE2 may directly convert the device type into primary user equipment;

or, the UE2 starts a third timer, and converts the device type to the primary user device after the third timer times out.

Further, UE2 sends a fifth message to the network device, where the fifth message indicates the device type conversion, and the fifth message includes an identifier of the primary user equipment.

In this embodiment, the UE2 starts the timer T2 (i.e. the second timer) when receiving the first message or the sixth message indicating the temporary backup. If the cancel notification of the backup from the UE1 is not received, the temporary backup is changed to the permanent backup after the timer T2 times out.

After the UE2 is converted into the permanent backup, the switching operation between the primary user equipment and the backup user equipment is realized, and the UE2 is converted into the primary user equipment, that is, the UE2 is a UE mainly responsible for data transmission of the service. Or, the UE2 may start the timer T3 (i.e., a third timer) when entering the permanent backup state, and when the timer T3 times out, the UE2 changes to the primary user equipment again.

After the primary user equipment is converted, the UE2 sends a message 5 (i.e., a fifth message) to the network side, indicating a change of the backup relationship, where the message 5 includes an identifier of the primary user equipment, i.e., an identifier of the UE2.

Specifically, if the base station indicates the backup and the backup type through a message 6 (i.e., a sixth message), the message 6 may further include a timer T2.

The embodiment of the invention realizes the operation from temporary backup to long backup and the operation of main-standby switching through the modes of a timer or message notification and the like, thereby ensuring the reliability of data transmission.

In a specific application scenario of the present invention, referring to fig. 3, UE1 is a primary user equipment, UE2 is a backup user equipment, and a network device may be a base station or a core network.

In step 301, UE1 monitors for a backup trigger event.

In step 302, after monitoring the backup triggering event, UE1 sends a first message to UE2 to instruct UE2 to perform backup.

In step 303, the network device sends a sixth message to UE2 to instruct UE2 to perform a hot backup on the data of UE 1. Step 303 is an optional step of step 301 and step 302.

In step 304, UE2 sends a second message to UE1 indicating that UE2 allows the backup. The UE2 may also indicate a backup failure in the second message, in which case the subsequent steps are no longer performed.

In step 305, UE2 sends a third message to the network device to indicate that a backup event has occurred.

In step 306, UE1 sends a fourth message to UE2 to indicate that the backup is cancelled. This step is optional and if step 306 is performed, subsequent steps are not performed.

In step 307, the UE2 starts a second timer when the backup type is temporary backup, and if the fourth message is not received and the second timer is over time, the backup type is adjusted from temporary backup to permanent backup.

In step 308, UE2 sends a fifth message to the network device to indicate that the backup relationship change occurs, that is, the primary user device is converted from UE1 to UE2.

Referring to fig. 4, an embodiment of the present invention further discloses a hot-standby apparatus 40, where the hot-standby apparatus 40 may include:

a monitoring module 401, configured to monitor a backup trigger event;

a sending module 402, configured to send a first message in response to the monitored backup trigger event, where the first message is used to instruct the backup user equipment to perform data transmission, and the first message includes an identifier of a service that needs to be backed up.

Referring to fig. 5, an embodiment of the present invention further discloses a hot-standby apparatus 50, where the hot-standby apparatus 50 may include:

a receiving module 501, configured to receive a first message, where the first message includes an identifier of a service that needs to be backed up;

a data transmission module 502, configured to perform data transmission on the data of the service indicated by the identifier of the service requiring backup in response to receiving the first message.

For more details of the operation principle and the operation manner of the hot-backup apparatus 40 or the hot-backup apparatus 50, reference may be made to the related descriptions in fig. 1 to fig. 3, and details are not repeated here.

In a specific implementation, the hot backup device may correspond to a Chip having a hot backup function in the user equipment, such as a System-On-a-Chip (SOC), a baseband Chip, or the like; or the user equipment comprises a chip module with a hot backup function; or to a chip module having a chip with data processing function, or to a user equipment.

Referring to fig. 6, an embodiment of the present invention further discloses a hot backup updating method.

The hot backup updating method may be used for a user equipment side, specifically, a primary user equipment side, that is, the primary user equipment may execute each step of the hot backup updating method.

Specifically, the hot backup updating method may include the following steps:

step 601: sending a seventh message, wherein the seventh message is used for inquiring backup user equipment;

step 602: receiving an eighth message, the eighth message comprising an identification of the backup user device.

In this embodiment, before triggering backup, the primary user equipment needs to obtain the backup user equipment corresponding to the primary user equipment, and may initiate query and management of the backup relationship. Or, in the case of switching between the primary user equipment and the backup user equipment, the primary user equipment may initiate query and management of the backup relationship.

In specific implementation, the master user equipment sends a message 7 (i.e. a seventh message) to the base station, information of backup user equipment is inquired, and the base station acquires the backup user equipment of the master user equipment as UE3/UE4; the base station sends a message 8 (i.e. an eighth message) to the primary user equipment, and the message 8 carries the identity of the backup user equipment, i.e. the identity of the UE3/UE 4.

In a non-limiting embodiment, the seventh message further includes an identification of a service that needs to be backed up.

In specific implementation, the master user equipment may perform query and management according to a service that needs to be backed up. The message 7 may carry a Service identifier, such as a Quality of Service flow id (QoS flow id), that needs to be backed up.

That is to say, when the service of the primary user equipment needs backup transmission, query and management of the backup relationship may be initiated. For example, when the UE1 initiates data transmission of the service 1, the backup relationship is queried through the above steps; when UE1 sends service 2, UE1 may also query the backup relationship through the above steps.

Accordingly, the following steps of the hot-backup updating method are performed by the network device: receiving a seventh message, wherein the seventh message is used for inquiring backup user equipment; and sending an eighth message, where the eighth message includes an identifier of the backup user equipment, and the identifier of the backup user equipment corresponds to the identifier of the service to be backed up in the seventh message.

Further, the network device selects one or more user devices from a user device group in which the primary user device is located, to serve as the backup user device.

In a specific implementation, the base station may request, from a core network element, a backup user equipment corresponding to the master user equipment, and the core network element notifies the base station of the backup user equipment corresponding to the master user equipment.

In a specific implementation, the base station may also select one or more backup UEs in one UE group, where the UE group refers to a group of multiple UEs that can transmit the service 1, and the multiple UEs may serve as backup UEs. The UE group information is configured by a network manager or notified to the base station by a network element of a core network.

Referring to fig. 7, an embodiment of the present invention further discloses a hot backup updating method.

Specifically, the hot backup updating method may include the following steps:

step 701: broadcasting a ninth message, wherein the ninth message is used for indicating to search for backup user equipment and comprises an identifier of a service needing to be backed up;

step 702: receiving a tenth message, wherein the tenth message contains an indication of candidate backup user equipment, and determining the backup user equipment according to the tenth message.

In a specific implementation, the UE2 sends a message 9 (also called a ninth message) to the surrounding UEs, that is, sends the message 9 in a broadcast manner, where the message 9 is to find a suitable backup UE, and the message 9 includes a service identifier to be backed up, such as a QoS flow id. If the surrounding UE, for example, UE5, can be a backup UE, UE5 sends a message 10 (i.e., a tenth message) to UE2, indicating that UE5 can be a candidate UE for backup.

In one variation, step 702 may also be replaced with the following steps: sending an eleventh message, wherein the eleventh message contains a candidate backup user identifier; and receiving the twelfth message, and determining candidate backup user equipment.

In this embodiment, the primary user equipment detects candidate UEs that can be backed up around. The primary user equipment reports the candidate UEs that can be backed up to the network side, that is, sends a message 11 (eleventh message), where the message 11 includes the candidate backup user identities. The network side is a base station or a core network element. Indicating available backup user equipment of main user equipment by network side

In the embodiment, the primary user equipment acquires an initial backup relationship when registering to a network; and/or receiving a non-access stratum signaling, wherein the non-access stratum signaling carries the updated backup relationship. Candidate UEs that may be backups are UEs from which a backup relationship exists.

Accordingly, other devices than the primary user equipment (such as the UE5 mentioned above) may perform the following steps of the hot-backup update method: receiving a ninth message, wherein the ninth message is used for indicating to search for backup user equipment and comprises an identifier of a service needing to be backed up; sending a tenth message indicating an indication of a candidate backup user device for determining the backup user device.

Further, judging whether a backup relation exists between the master user equipment and the master user equipment; and if the backup relationship exists with the main user equipment, sending the tenth message.

Further, when registering to the network, obtaining an initial backup relationship; and/or receiving a non-access stratum signaling, wherein the non-access stratum signaling carries the updated backup relationship.

In this embodiment, when the UE registers in the communication network, the network side configures an initial backup relationship, and the network side may update the backup relationship. Wherein, the configuration and the update of the backup relationship are sent through Non-Access Stratum (NAS) signaling. Candidate UEs that may be backed up are from UEs with a backup relationship. For example, for the case that the primary user equipment is UE2, if UE5 finds that UE5 and UE2 have a backup relationship, UE5 may send a message 10 (i.e., a tenth message) to UE2 to indicate that UE5 may be a candidate backup user equipment for UE2.

The embodiment of the invention can realize the configuration of the backup user equipment corresponding to the main user equipment through the management of the backup relation, thereby realizing the main-backup switching and ensuring the reliability of data transmission.

Each module/unit included in each apparatus and product described in the above embodiments may be a software module/unit, or may also be a hardware module/unit, or may also be a part of a software module/unit and a part of a hardware module/unit. For example, for each device or product applied to or integrated into a chip, each module/unit included in the device or product may be implemented by hardware such as a circuit, or at least a part of the module/unit may be implemented by a software program running on a processor integrated within the chip, and the rest (if any) part of the module/unit may be implemented by hardware such as a circuit; for each device or product applied to or integrated with the chip module, each module/unit included in the device or product may be implemented by using hardware such as a circuit, and different modules/units may be located in the same component (e.g., a chip, a circuit module, etc.) or different components of the chip module, or at least some of the modules/units may be implemented by using a software program running on a processor integrated within the chip module, and the rest (if any) of the modules/units may be implemented by using hardware such as a circuit; for each device and product applied to or integrated in the terminal, each module/unit included in the device and product may be implemented by using hardware such as a circuit, and different modules/units may be located in the same component (e.g., a chip, a circuit module, etc.) or different components in the terminal, or at least part of the modules/units may be implemented by using a software program running on a processor integrated in the terminal, and the rest (if any) part of the modules/units may be implemented by using hardware such as a circuit.

The embodiment of the invention also discloses a storage medium which is a computer readable storage medium and is stored with a computer program, and the steps of the hot backup method or the hot backup updating method can be executed when the computer program runs.

The embodiment of the invention also discloses user equipment which can comprise a memory and a processor, wherein the memory is stored with a computer program which can run on the processor. The processor, when executing the computer program, may perform the steps of the hot-backup method or hot-backup update method. The user equipment includes but is not limited to a mobile phone, a computer, a tablet computer and other terminal equipment.

The technical solution of the present invention is also applicable to different network architectures, including but not limited to relay network architecture, dual link architecture, vehicle-to-event architecture, and the like.

In this embodiment of the present application, the Core Network may be an evolved packet Core (EPC for short), a 5G Core Network (5G Core Network), or may be a novel Core Network in a future communication system. The 5G Core Network is composed of a set of devices, and implements Access and Mobility Management functions (AMF) of functions such as Mobility Management, user Plane Functions (UPF) providing functions such as packet routing and forwarding and QoS (Quality of Service) Management, session Management Functions (SMF) providing functions such as Session Management, IP address allocation and Management, and the like. The EPC may be composed of an MME providing functions such as mobility management, gateway selection, etc., a Serving Gateway (S-GW) providing functions such as packet forwarding, etc., and a PDN Gateway (P-GW) providing functions such as terminal address allocation, rate control, etc.

A Base Station (BS) in the embodiment of the present application, which may also be referred to as a base station device, is a device deployed in a Radio Access Network (RAN) to provide a wireless communication function. For example, a device providing a base station function in a 2G network includes a Base Transceiver Station (BTS), a device providing a base station function in a 3G network includes a node B (NodeB), a device providing a base station function in a 4G network includes an Evolved node B (eNB), and in a Wireless Local Area Network (WLAN), the device providing a base station function is an Access Point (AP), a device providing a base station function in a 5G New Radio (NR) is a gNB, and a node B (ng-eNB) continues to evolve, where the gNB and the terminal communicate with each other by using an NR technique, the ng-eNB and the terminal communicate with each other by using an E-a (Evolved Universal Radio Access) technique, and both the gNB and the ng-eNB may be connected to the 5G core network. The base station in the embodiment of the present application also includes a device and the like that provide a function of the base station in a future new communication system.

The base station controller in the embodiment of the present application is a device for managing a base station, for example, a Base Station Controller (BSC) in a 2G network, a Radio Network Controller (RNC) in a 3G network, or a device for controlling and managing a base station in a future new communication system.

The network on the network side in the embodiment of the present invention refers to a communication network providing communication services for a terminal, and includes a base station of a radio access network, a base station controller of the radio access network, and a device on the core network side.

A terminal in this embodiment may refer to various forms of User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station (mobile station, MS), a remote station, a remote terminal, a mobile device, a user terminal, a terminal device (terminal equipment), a wireless communication device, a user agent, or a user equipment. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with a Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G Network or a terminal device in a future evolved Public Land Mobile Network (PLMN), and the like, which is not limited in this embodiment.

In the embodiment of the application, a unidirectional communication link from an access network to a terminal is defined as a downlink, data transmitted on the downlink is downlink data, and the transmission direction of the downlink data is called as a downlink direction; the unidirectional communication link from the terminal to the access network is an uplink, the data transmitted on the uplink is uplink data, and the transmission direction of the uplink data is referred to as an uplink direction.

It should be understood that the term "and/or" herein is only one kind of association relationship describing the association object, and means that there may be three kinds of relationships, for example, a and/or B, and may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein indicates that the former and latter associated objects are in an "or" relationship.

The "plurality" appearing in the embodiments of the present application means two or more.

The descriptions of the first, second, etc. appearing in the embodiments of the present application are only for illustrating and differentiating the objects, and do not represent the order or the particular limitation of the number of the devices in the embodiments of the present application, and do not constitute any limitation to the embodiments of the present application.

The term "connection" in the embodiment of the present application refers to various connection manners such as direct connection or indirect connection, so as to implement communication between devices, which is not limited in this embodiment of the present application.

It should be understood that, in the embodiment of the present application, the processor may be a Central Processing Unit (CPU), and the processor may also be other general-purpose processors, digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It will also be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example and not limitation, many forms of Random Access Memory (RAM) are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM), synchronous DRAM (SLDRAM), synchronous Link DRAM (SLDRAM), and direct bus RAM (DR RAM).

The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer instructions or computer programs. The procedures or functions according to the embodiments of the present application are wholly or partially generated when the computer instructions or the computer program are loaded or executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire or wirelessly. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more collections of available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. The semiconductor medium may be a solid state disk.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

In the several embodiments provided in the present application, it should be understood that the disclosed method, apparatus and system may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative; for example, the division of the unit is only a logic function division, and there may be another division manner in actual implementation; for example, various elements or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be physically included alone, or two or more units may be integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute some steps of the methods according to the embodiments of the present invention.

Although the present invention is disclosed above, the present invention is not limited thereto. Various changes and modifications may be effected therein by one skilled in the art without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A hot backup method, comprising:

monitoring a backup trigger event;

and responding to the monitored backup trigger event, and sending a first message, wherein the first message is used for indicating the backup user equipment to carry out data transmission, and the first message comprises an identifier of the service needing to be backed up.

2. The hot-backup method of claim 1, wherein the backup triggering event comprises one or more of:

the data transmission failure times reach a first preset number;

the data receiving failure times reach a second preset number;

when the wireless link is monitored, a third preset number of continuous out-of-step indications occur;

and when the wireless link is monitored, the third preset number of out-of-step instructions occur continuously, and the started first timer is overtime.

3. The hot-backup method according to claim 1, wherein the first message further comprises reception status information of downstream data.

4. The method of claim 3, wherein the receiving status information comprises a maximum sequence number of successfully received consecutive packets, an unsuccessfully received packet sequence number, and a successfully received non-consecutive packet sequence number.

5. The hot-standby method according to claim 1, wherein the first message further includes transmission status information of upstream data.

6. The method of claim 5, wherein the transmission status information comprises a maximum sequence number of consecutive successfully transmitted packets, an unsuccessfully transmitted packet sequence number, and a successfully received discontinuous packet sequence number.

7. The method of claim 1, wherein the sending the first message comprises a backup reason comprising one or more of:

data transmission failure, data reception failure, radio link degradation, radio link failure, and terminal movement.

8. The hot backup method of claim 1, wherein sending the first message comprises: sending the first message through a direct communication interface with the backup user device;

or forwarding the first message through a base station, where the first message includes an identifier of a cell where the backup user equipment is located or an identifier of a connected base station.

9. The hot-standby method according to claim 1, further comprising:

sending a fourth message, wherein the fourth message instructs the backup user equipment to cancel data transmission.

10. The method of claim 9, wherein sending the fourth message comprises: sending the fourth message through a direct communication interface with the backup user device;

or forwarding the fourth message through the base station, where the fourth message includes an identifier of a cell where the backup user equipment is located or an identifier of a connected base station.

11. The method of hot backup according to claim 1, wherein the first message further comprises a backup type, the backup type being selected from the group consisting of temporary backup and permanent backup.

12. A hot backup method, comprising:

receiving a first message, wherein the first message comprises an identifier of a service needing to be backed up;

and responding to the received first message, and performing data transmission on the data of the service indicated by the identification of the service needing backup.

13. The hot-standby method of claim 12, further comprising:

and sending a second message, wherein the second message indicates that the data transmission is allowed or indicates that the backup is failed.

14. The hot-standby method of claim 12, further comprising:

and sending a third message to the network equipment, wherein the third message is used for indicating the occurrence of the backup event to the network equipment.

15. The hot-standby method of claim 14, wherein the third message comprises one or more of: an identity of a primary user equipment, an identity of a backup user equipment, and a backup reason.

16. The method of hot backup according to claim 12, wherein the first message further comprises a backup type, the backup type being selected from the group consisting of temporary backup and permanent backup.

17. The hot-standby method of claim 12, further comprising:

receiving a sixth message from the network device, the sixth message indicating to perform the backup, the sixth message including a backup type, the backup type being selected from a temporary backup and a permanent backup.

18. The hot-standby method according to claim 16 or 17, further comprising:

and when the backup type is temporary backup, starting a second timer.

19. The hot-standby method of claim 18, further comprising:

and if the fourth message is not received and the second timer is overtime, the backup type is adjusted from the temporary backup to the permanent backup, and the fourth message indicates that the data transmission is cancelled.

20. The hot-standby method of claim 19, further comprising:

converting the device type into a master user device;

or starting a third timer, and converting the device type into the primary user device after the third timer is overtime.

21. The hot-standby method of claim 20, further comprising:

and sending a fifth message to the network equipment, wherein the fifth message indicates the conversion of the equipment type, and the fifth message comprises the identification of the primary user equipment.

22. A hot standby device, comprising:

the monitoring module is used for monitoring a backup trigger event;

and the sending module is used for responding to the monitored backup triggering event and sending a first message, wherein the first message is used for indicating the backup user equipment to carry out data transmission and comprises the identification of the service needing to be backed up.

23. A hot-standby apparatus, comprising:

a receiving module, configured to receive a first message, where the first message includes an identifier of a service that needs to be backed up; and the data transmission module is used for responding to the received first message and performing data transmission aiming at the service data indicated by the identification of the service needing to be backed up.

24. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the hot backup method according to any one of claims 1 to 21.

25. A user equipment comprising a memory and a processor, the memory having stored thereon a computer program being executable on the processor, characterized in that the processor, when executing the computer program, performs the steps of the hot-backup method of any one of claims 1 to 10, or the steps of the hot-backup method of any one of claims 11 to 20.