CN114828293A

CN114828293A - Connection maintaining method and device and electronic equipment

Info

Publication number: CN114828293A
Application number: CN202110113857.4A
Authority: CN
Inventors: 王文; 康艳超; 韩鲁峰; 张鹏飞
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2021-01-27
Filing date: 2021-01-27
Publication date: 2022-07-29
Also published as: WO2022161313A1

Abstract

The application discloses a connection keeping method, a connection keeping device and electronic equipment, and belongs to the field of mobile communication. The method comprises the following steps: acquiring a disaster relief message of a second network side; and responding to the disaster relief message, and executing a first operation to enable the terminal to maintain network connection. By the embodiment of the application, the terminal can still maintain network connection under the condition that the disaster of the second network is relieved, and service interruption is avoided.

Description

Connection keeping method and device and electronic equipment

Technical Field

The application belongs to the technical field of mobile communication, and particularly relates to a connection keeping method, a connection keeping device and electronic equipment.

Background

In the event of a Disaster Condition (DC), such as a fire, the second network may not be able to provide service, and in this case, a terminal or Disaster-access roamer (DIR) located in the second network will access the first network and be served by the first network.

In a minimum service interruption (MINT) scenario, after the first network obtains that the second network has been released from the DC, the first network may directly release the connection of the terminal switched from the second network or the disaster access roamer to ensure the service experience of the network user of the first network, but this operation may cause the service of the terminal or the disaster access roamer to be directly interrupted.

Disclosure of Invention

An object of the embodiments of the present application is to provide a connection maintaining method and apparatus, and an electronic device, which can solve a problem of direct service interruption of a terminal or a disaster access roamer.

In order to solve the technical problem, the present application is implemented as follows:

in a first aspect, a connection maintaining method is provided, and is applied to a first network-side device, where the method includes:

acquiring a disaster relief message of a second network side;

and responding to the disaster relief message, and executing a first operation to enable a terminal to maintain network connection, wherein the terminal is accessed to a first network side by a second network side when the second network side is in a disaster state.

In a second aspect, there is provided a connection retention apparatus, the apparatus comprising:

the acquisition module is used for acquiring the disaster relief message of the second network side;

and the execution module is used for responding to the disaster relief message and executing a first operation so as to enable a terminal to maintain network connection, wherein the terminal is accessed to the first network side by the second network side when the second network side is in a disaster state.

In a third aspect, a connection maintaining method is provided, which is applied to a terminal, and includes:

acquiring a disaster relief message of a second network side;

and responding to the disaster relief message, and executing a second operation according to second information so as to enable the terminal to maintain network connection.

In a fourth aspect, there is provided a connection retention apparatus, the apparatus comprising:

the receiving module is used for acquiring a disaster relief message of the second network side;

and the operation module is used for responding to the disaster relief message and executing second operation according to second information so as to enable the terminal to keep network connection.

In a fifth aspect, a network-side device is provided, which comprises a processor, a memory, and a program or instructions stored on the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method according to the first aspect.

In a sixth aspect, a terminal is provided, comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method according to the third aspect.

In a seventh aspect, there is provided a readable storage medium on which a program or instructions are stored, which program or instructions, when executed by a processor, implement the steps of the method according to the first aspect, or implement the steps of the method according to the third aspect.

In an eighth aspect, a chip is provided, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a network-side device program or instruction, implement the method according to the first aspect, or implement the method according to the third aspect.

In the embodiment of the application, the disaster relief message of the second network side is acquired; and responding to the disaster relief message, executing a first operation to enable the terminal to maintain network connection, so that the terminal can still maintain network connection and avoid service interruption under the condition that the second network disaster is relieved.

Drawings

FIG. 1 illustrates a block diagram of a wireless communication system to which embodiments of the present application are applicable;

fig. 2 is a schematic flow chart illustrating a connection maintaining method according to an embodiment of the present application;

fig. 3 is a schematic flow chart of a connection maintaining method provided in an embodiment of the present application;

fig. 4 is a schematic flow chart of a connection maintaining method provided in an embodiment of the present application;

fig. 5 is a schematic flow chart of a connection maintaining method provided in an embodiment of the present application;

fig. 6 is a schematic flow chart of a connection maintaining method provided in an embodiment of the present application;

FIG. 7 is a schematic diagram illustrating an exemplary configuration of a connection retaining apparatus according to an embodiment of the present disclosure;

fig. 8 is a schematic flow chart of a connection maintaining method provided in an embodiment of the present application;

fig. 9 is a schematic flow chart of a connection maintaining method provided in an embodiment of the present application;

FIG. 10 is a schematic view of another embodiment of a connection retaining device according to the present application;

fig. 11 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

fig. 12 is a schematic structural diagram of a network-side device for implementing an embodiment of the present application;

fig. 13 is a schematic hardware structure diagram of a terminal for implementing the embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used are interchangeable under appropriate circumstances such that embodiments of the application can be practiced in sequences other than those illustrated or described herein, and the terms "first" and "second" used herein generally do not denote any order, nor do they denote any order, for example, the first object may be one or more. In addition, "and/or" in the specification and the claims means at least one of connected objects, and a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

It is noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, but may also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described techniques can be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for purposes of example, and NR terminology is used in much of the description below, although the techniques may also be applied to applications other than NR system applications, such as 6 th generation (6 th generation) ^th Generation, 6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network-side device 12. Wherein, the terminal 11 may also be called as a terminal Device or a User Equipment (UE), the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer) or a notebook Computer, a Personal Digital Assistant (PDA), a palmtop Computer, a netbook, a super-Mobile Personal Computer (UMPC), a Mobile Internet Device (MID), a Wearable Device (Wearable Device) or a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), and other terminal side devices, the Wearable Device includes: bracelets, earphones, glasses and the like. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network-side device 12 may be a Base Station or a core network, where the Base Station may be referred to as a node B, an evolved node B, an access Point, a Base Transceiver Station (BTS), a radio Base Station, a radio Transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a node B, an evolved node B (eNB), a home node B, a WLAN access Point, a WiFi node, a Transmit Receiving Point (TRP), or some other suitable terminology in the field, as long as the same technical effect is achieved, the Base Station is not limited to a specific technical vocabulary, and it should be noted that, in the embodiment of the present application, only the Base Station in the NR system is taken as an example, but a specific type of the Base Station is not limited.

The connection maintaining method provided by the embodiment of the present application is described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios thereof.

Fig. 2 shows a flowchart of a connection maintaining method provided in an embodiment of the present application, which may be performed by a first network-side device, in other words, the method may be performed by software or hardware installed in the first network-side device. As shown in fig. 2, the method may include the following steps.

Step S201, a disaster relief message of the second network side is acquired.

The second Network side is a Network in a disaster state (DC) or a Public Land Mobile Network (PLMN).

The first network side is a network or PLMN that can serve terminals of the second network side in DC state. When the second network side releases the disaster state, the first network side equipment acquires the disaster release message of the second network side.

The first network-side device comprises at least one of:

access mobile Management Function (AMF), Radio Access Network (RAN) devices.

Step S202, in response to the disaster relief message, executing a first operation to enable a terminal to maintain network connection, where the terminal is a terminal accessed from the second network side to the first network side when the second network side is in a disaster state.

After acquiring the disaster relief message of the second network side, the first network side device executes a first operation for minimizing service interruption received by the terminal, so that the terminal maintains network connection.

The terminal is User Equipment (UE) or DIR using the second Network side as a main Network or a main Public Land Mobile Network (HPLMN). The terminal accesses the first network side when the second network side is in a DC scenario.

In one embodiment, the first operation includes at least one of:

stopping a release process of triggering terminal connection, wherein the release process comprises a non-access stratum signaling release process and/or an access stratum signaling release process;

sending first timer related information, wherein the first timer is related to the release of connection and network selection executed by the terminal; for example, the first timer related information may be sent to the terminal, so that the terminal sets the first timer according to the related information, and performs connection release and network selection according to the first timer;

starting a second timer; during the operation of the second timer, the first network side device may stop triggering a release process of the terminal connection and/or reject a non-emergency or high-priority registration of the terminal, a Protocol Data Unit (PDU) session establishment or a service request process;

accepting the first request; the first request may be sent by the terminal after acquiring the disaster relief message of the second network side.

Therefore, according to the connection maintaining method provided by the embodiment of the application, the disaster relief message of the second network side is acquired; and responding to the disaster relief message, executing a first operation to enable the terminal to maintain network connection, so that the terminal can still maintain network connection and avoid service interruption under the condition that the second network disaster is relieved.

Fig. 3 shows another schematic flow chart of the connection maintaining method provided in the embodiment of the present application, which may be executed by the first network-side device, in other words, the method may be executed by software or hardware installed in the first network-side device. As shown in fig. 3, the method may include the following steps.

Step S301, obtaining the disaster relief message of the second network side.

The method executed in step S301 is the same as or similar to the method executed in step S201 in fig. 2, and the same or similar beneficial effects are obtained, and the description of the same parts is omitted here.

Step S302, responding to the disaster relief message, and executing a first operation according to at least one item of the following first information so as to enable the terminal to maintain network connection;

wherein the first information comprises:

a type of a protocol data unit session of the terminal; wherein the type of the PDU session comprises at least one of: an emergency type protocol data unit session type, an initiated protocol data unit session type in a disaster scenario, other high priority protocol data unit session types;

the registration type of the terminal; wherein the registration type includes at least one of: an emergency registration type, a registration type in a disaster scene, and other high-priority registration types;

a service request of the terminal; wherein the service request is for at least one of: emergency services (emergency services), emergency service fallback (emergency service fallback), high priority access (high priority access);

emergency service data being received or transmitted by the terminal;

the terminal is receiving or sending the high-priority service; wherein the description of the high priority traffic comprises at least one of:

a Data Network Name (DNN);

slice-specific Single Network Slice Selection Assistance Information (S-NSSAI);

a specific 5G Quality of Service Identifier (5G Quality of Service Identifier, 5 QI).

The first operation comprises at least one of:

sending first timer related information, wherein the first timer is related to the release of connection and network selection executed by the terminal;

starting a second timer;

the first request is accepted.

Therefore, according to the connection maintaining method provided by the embodiment of the application, the disaster relief message of the second network side is acquired; and responding to the disaster relief message, executing a first operation according to the acquired first message to enable the terminal to keep network connection, so that the terminal can still keep network connection under the condition that the disaster of the second network is relieved, and service interruption is avoided.

Fig. 4 shows another schematic flowchart of the connection maintaining method provided in the embodiment of the present application, where the method may be executed by the first network-side device, in other words, the method may be executed by software or hardware installed in the first network-side device. As shown in fig. 4, the method may include the following steps.

Step S401, obtaining a disaster relief message of the second network side.

The method executed in step S401 is the same as or similar to the method executed in step S301 in fig. 3, and the same or similar beneficial effects are obtained, and the description of the same parts is omitted here.

Step S402, responding to the disaster relief message, executing a first operation according to the first information to enable the terminal to maintain network connection, wherein the first operation comprises accepting a first request.

In one embodiment, the first request may be sent by a terminal.

In an instance in which the first operation comprises accepting a first request, the first request comprises at least one of:

a registration request; wherein the registration type of the registration request comprises at least one of: an emergency registration type, a registration type in a disaster scene, and other high-priority registration types; the registration process of the registration request is triggered by the terminal or the first network side;

a request for deregistration;

a protocol data unit session establishment request; wherein the type of the PDU session comprises at least one of: an emergency type protocol data unit session type, an initiated protocol data unit session type in a disaster scenario, other high priority protocol data unit session types;

a protocol data unit session modification request; wherein the type of the PDU session comprises at least one of: an emergency type protocol data unit session type, an initiated protocol data unit session type in a disaster scenario, other high priority protocol data unit session types;

a protocol data unit session release request;

a service request; wherein, the request process of the service request is triggered by the terminal or the first network side, and the service request is used for one of the following purposes:

emergency services;

emergency service fallback;

high priority access.

Step S403, replying at least one of the following first request acceptance messages according to the first request.

The first request acceptance message includes:

a registration acceptance message;

a PDU session establishment accept message;

a PDU session modification acceptance message;

a PDU release accept message;

a service request accept message.

Therefore, according to the connection maintaining method provided by the embodiment of the application, the disaster relief message of the second network side is acquired; and responding to the disaster relief message, receiving the first request and replying so that the first network side equipment assists the terminal to maintain network connection after acquiring the second network disaster relief message, thereby avoiding service interruption.

Fig. 5 shows another schematic flow chart of the connection maintaining method provided in the embodiment of the present application, which may be executed by the first network-side device, in other words, the method may be executed by software or hardware installed in the first network-side device. As shown in fig. 5, the method may include the following steps.

Step S501, a disaster relief message of the second network side is acquired.

The method executed in step S501 is the same as or similar to the method executed in step S301 in fig. 3, and the same or similar beneficial effects are obtained, and the description of the same parts is omitted here.

Step S502, responding to the disaster relief message, and executing a first operation according to the first information to enable the terminal to maintain network connection, wherein the first operation comprises starting a second timer.

In one embodiment, the first network-side device performs at least one of the following before the second timer expires:

stopping the process of releasing the connection of the trigger terminal;

stopping triggering the protocol data unit session release process;

rejecting an initiated Non Access Stratum (NAS) signaling procedure of the terminal; wherein the initiated non-access stratum signaling procedure of the terminal comprises at least one of:

non-access stratum signaling process that does not meet high priority;

non-access stratum signaling procedures that do not satisfy emergency services;

the non-access stratum signaling procedure triggered by the first network side is not satisfied.

In another embodiment, the first network side performs the release procedure of the terminal connection when the second timer expires.

The release process of the terminal connection comprises at least one of the following:

a release process of the non-access layer connection, including a de-registration process;

the release process of the access layer connection comprises a radio resource control connection release process;

a release procedure of a protocol data unit session.

Therefore, according to the connection maintaining method provided by the embodiment of the application, the disaster relief message of the second network side is acquired; and responding to the disaster relief message, and starting a second timer, so that the first network side equipment assists the terminal to maintain network connection after acquiring the second network disaster relief message, and service interruption is avoided.

Fig. 6 shows another schematic flow chart of the connection maintaining method provided in the embodiment of the present application, which may be executed by the first network-side device, in other words, the method may be executed by software or hardware installed in the first network-side device. As shown in fig. 6, the method may include the following steps.

Step S601, obtaining a disaster relief message of the second network side.

The method executed in step S601 is the same as or similar to the method executed in step S301 in fig. 3, and the same or similar beneficial effects are obtained, and the description of the same parts is omitted here.

Step S602, in response to the disaster relief message, executing a first operation according to the first information to enable the terminal to maintain network connection, where the first operation includes sending first timer related information.

In one embodiment, the first timer related information sent by the first network-side device to the terminal may be included in one of the following information: a deregistration request, a configuration update command, other NAS information.

The terminal starts a first timer according to the received related information of the first timer, and before the first timer expires, the terminal executes at least one of the following operations:

deregister;

network selection and PLMN selection; wherein the network selection comprises performing selecting a second network;

protocol data unit PDU session release;

non-access stratum NAS release.

Therefore, according to the connection maintaining method provided by the embodiment of the application, the disaster relief message of the second network side is acquired; and responding to the disaster relief message, and sending related information of the first timer to the terminal so as to enable the terminal to start the first timer, so that the first network side equipment assists the terminal to maintain network connection after acquiring the second network disaster relief message, and service interruption is avoided.

In the connection holding method provided in the embodiments of the present application, the execution main body may be a connection holding device, or a control module in the connection holding device for executing the connection holding method. In the embodiments of the present application, a method for performing connection holding by using a connection holding device is taken as an example, and a connection holding device provided in the embodiments of the present application is described.

Fig. 7 shows a schematic structural diagram of a connection retaining device 700 provided in the embodiment of the present application, and as shown in fig. 7, the device includes: an acquisition module 701 and an execution module 702.

The obtaining module 701 is configured to obtain a disaster relief message of a second network side; the executing module 702 is configured to execute a first operation in response to the disaster relief message, so as to enable a terminal to maintain a network connection, where the terminal is a terminal accessed to a first network side by a second network side when the second network side is in a disaster state.

Further, the first operation includes at least one of:

starting a second timer;

the first request is accepted.

Therefore, the embodiment of the application acquires the disaster relief message of the second network side; and responding to the disaster relief message, executing a first operation to enable the terminal to maintain network connection, so that the terminal can still maintain network connection and avoid service interruption under the condition that the second network disaster is relieved.

Based on the foregoing embodiment, further, the execution module is configured to:

performing a first operation according to at least one of the following first information;

wherein the first information comprises:

a service request of the terminal; wherein the service request is for at least one of: emergency service, emergency service fallback, high priority access;

emergency service data being received or transmitted by the terminal;

the terminal is receiving or sending the high priority service; wherein the description of the high priority traffic comprises at least one of:

a particular data network name;

slice-specific individual network slice selection assistance information;

a specific 5G quality of service identifier.

Therefore, the embodiment of the application acquires the disaster relief message of the second network side; and responding to the disaster relief message, executing a first operation according to the acquired first message to enable the terminal to keep network connection, so that the terminal can still keep network connection under the condition that the disaster of the second network is relieved, and service interruption is avoided.

Further, where the first operation comprises accepting a first request, the first request comprises at least one of:

a request for deregistration;

a protocol data unit session release request;

emergency services;

emergency service fallback;

high priority access.

Therefore, the embodiment of the application acquires the disaster relief message of the second network side; and responding to the disaster relief message, receiving the first request and replying so that the first network side equipment assists the terminal to maintain network connection after acquiring the second network disaster relief message, thereby avoiding service interruption.

Based on the foregoing embodiment, further, in a case that the first operation includes starting a second timer, the execution module is further configured to:

before the second timer expires, performing at least one of the following:

stopping the process of releasing the connection of the trigger terminal;

stopping triggering the protocol data unit session release process;

rejecting a non-access stratum signaling process initiated by the terminal; wherein the initiated non-access stratum signaling procedure of the terminal comprises at least one of:

non-access stratum signaling process that does not meet high priority;

non-access stratum signaling procedures that do not satisfy emergency services;

Further, in a case that the first operation includes starting a second timer, the execution module is further configured to:

performing a release procedure of the terminal connection in case the second timer expires.

Further, the release process of the terminal connection includes at least one of the following:

a release procedure of a protocol data unit session.

Therefore, the embodiment of the application acquires the disaster relief message of the second network side; and responding to the disaster relief message, and starting a second timer, so that the first network side equipment assists the terminal to maintain network connection after acquiring the second network disaster relief message, and service interruption is avoided.

The connection maintaining device in the embodiment of the present application may be a device or a network side device. Illustratively, the network-side device may include, but is not limited to, the types of network-side device 12 listed above.

The connection retaining device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.

The connection holding device provided in the embodiment of the present application can implement each process implemented by the method embodiments of fig. 2 to fig. 6, and achieve the same technical effect, and is not described herein again to avoid repetition.

Fig. 8 shows another flow chart of the connection maintaining method provided in the embodiment of the present application, which may be executed by the terminal, in other words, the method may be executed by software or hardware installed in the terminal. As shown in fig. 8, the method may include the following steps.

Step S801, a disaster relief message on the second network side is acquired.

The second Network side is a Network in a Disaster (DC) state or a Public Land Mobile Network (PLMN).

It should be understood that the terminal is a terminal accessed to the first network side by the second network side when the second network side is in a disaster state.

The terminal is UE or DIR taking the second network side as a main network or HPLMN, and the terminal is accessed to the first network side when the second network side is in a DC scene.

And step S802, responding to the disaster relief message, and executing a second operation according to the second information so as to enable the terminal to maintain network connection.

In one embodiment, the second information includes at least one of:

the terminal is transmitting target service data; wherein the target traffic comprises at least one of: emergency service, high priority access service, specific data network name related service, and specific slice related service;

the terminal is transmitting data using a target protocol data unit session; wherein the target protocol data unit session comprises at least one of: an emergency type protocol data unit session, an association specific data network name, an association specific slice;

receiving paging or non-access stratum notification message (NAS notification) of a first network side;

the terminal triggers a session establishment process of a target protocol data unit; wherein the target protocol data unit session comprises at least one of: protocol data unit session of emergency type, association specific data network name, association specific slice;

the terminal triggers a target registration updating process; wherein the registration type of the target registration update procedure comprises at least one of: the method comprises the following steps of an emergency registration type, a registration type triggered by a first network side in a registration updating process, and a registration type in a disaster scene.

In one embodiment, the second operation comprises:

and stopping executing the releasing process of the terminal connection, wherein the releasing process comprises a non-access stratum signaling releasing process and/or an access stratum signaling releasing process.

Therefore, according to the connection maintaining method provided by the embodiment of the application, the disaster relief message of the second network side is acquired; and responding to the disaster relief message, executing a second operation according to the second information to enable the terminal to maintain network connection, so that the terminal can still maintain network connection under the condition of second network disaster relief, and service interruption is avoided.

Fig. 9 is a schematic flow chart of another connection maintaining method provided in the embodiment of the present application, which may be executed by a terminal, in other words, the method may be executed by software or hardware installed in the terminal. As shown in fig. 9, the method may include the following steps.

Step S901, a disaster relief message of the second network side is acquired.

The method executed in step S901 is the same as or similar to the method executed in step S801 in fig. 8, so as to obtain the same or similar beneficial effects, and the description of the same parts is omitted here.

Step S902, receiving related information of a first timer sent by a first network side, and starting the first timer.

The relevant information of the first timer is that the first network side equipment sends the disaster relief message of the second network side to the terminal according to at least one item of the following first information after acquiring the disaster relief message.

Wherein the first information comprises:

emergency service data being received or transmitted by the terminal;

a particular data network name;

slice-specific individual network slice selection assistance information;

a specific 5G quality of service identifier.

Step S903, before the first timer finishes counting, executing at least one of the following:

deregister;

selecting a network; wherein the network selection comprises performing selecting a second network;

releasing the protocol data unit session;

and releasing the non-access stratum.

Therefore, according to the connection maintaining method provided by the embodiment of the application, the disaster relief message of the second network side is acquired; and starting the first timer according to the received related information of the first timer, and executing related operations before the first timer expires, so that the terminal can still maintain network connection and avoid service interruption under the condition that the disaster of the second network is relieved.

Fig. 10 is a schematic view illustrating another structure of the connection retaining device 100 according to the embodiment of the present application, and as shown in fig. 10, the device includes: a receiving module 101 and an operating module 102.

The receiving module 101 is configured to obtain a disaster relief message of a second network side; the operation module 102 is configured to, in response to the disaster relief message, execute a second operation according to the second information, so that the terminal maintains a network connection.

Further, the terminal is a terminal which is accessed to the first network side by the second network side when the second network side is in a disaster state.

Further, the second information includes at least one of the following:

the terminal is transmitting data using a target protocol data unit session; wherein the target protocol data unit session comprises at least one of: protocol data unit sessions of the emergency type, associated specific data network names, associated specific slices;

receiving a paging or non-access stratum notification message of a first network side;

Further, the second operation includes:

Therefore, the embodiment of the application acquires the disaster relief message of the second network side; and responding to the disaster relief message, executing a second operation according to the second information to enable the terminal to maintain network connection, so that the terminal can still maintain network connection and avoid service interruption under the condition that the disaster of the second network side is relieved.

Based on the foregoing embodiment, further, the receiving module is further configured to:

and receiving related information of a first timer sent by a first network side, and starting the first timer.

Further, the operation module is further configured to:

before the first timer is timed out, at least one of the following is executed:

deregister;

releasing the protocol data unit session;

and releasing the non-access stratum.

Therefore, the embodiment of the application acquires the disaster relief message of the second network side; and starting the first timer according to the received related information of the first timer, and executing related operations before the first timer expires, so that the terminal can still maintain network connection and avoid service interruption under the condition that the disaster of the second network side is relieved.

The connection holding means in the embodiments of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal. The device can be a mobile terminal or a non-mobile terminal. By way of example, the mobile terminal may include, but is not limited to, the above-listed type of terminal 11, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine, a kiosk, or the like, and the embodiments of the present application are not limited in particular.

The connection holding device provided in the embodiment of the present application can implement each process implemented by the method embodiments of fig. 8 to 9, and achieve the same technical effect, and is not described here again to avoid repetition.

Optionally, as shown in fig. 11, an embodiment of the present application further provides a communication device 110, which includes a processor 111, a memory 112, and a program or an instruction stored on the memory 112 and executable on the processor 111, for example, when the communication device 110 is a terminal, the program or the instruction is executed by the processor 111 to implement each process of the foregoing connection maintaining method embodiment, and the same technical effect can be achieved. When the communication device 110 is a network-side device, the program or the instruction is executed by the processor 111 to implement the processes of the connection maintaining method embodiment, and the same technical effect can be achieved.

Specifically, the embodiment of the application further provides a network side device. As shown in fig. 12, the network-side device 120 includes: antenna 121, rf device 122, and baseband device 123. The antenna 121 is connected to a radio frequency device 122. In the uplink direction, the rf device 122 receives information through the antenna 121 and sends the received information to the baseband device 123 for processing. In the downlink direction, the baseband device 123 processes information to be transmitted and transmits the information to the rf device 122, and the rf device 122 processes the received information and transmits the processed information through the antenna 121.

The above band processing means may be located in the baseband device 123, and the method performed by the network side device in the above embodiment may be implemented in the baseband device 123, where the baseband device 123 includes a processor 124 and a memory 125.

The baseband device 123 may include, for example, at least one baseband board, on which a plurality of chips are disposed, as shown in fig. 12, where one of the chips, for example, the processor 124, is connected to the memory 125 to call up the program in the memory 125 to perform the network-side device operation shown in the above method embodiment.

The baseband device 123 may further include a network interface 126 for exchanging information with the radio frequency device 122, for example, a Common Public Radio Interface (CPRI).

Specifically, the network side device in the embodiment of the present application further includes: the instructions or programs stored in the memory 125 and capable of being executed on the processor 124, and the processor 124 calls the instructions or programs in the memory 125 to execute the methods executed by the modules shown in fig. 7, and achieve the same technical effects, which are not described herein for avoiding repetition.

The terminal 1300 includes but is not limited to: a radio frequency unit 131, a network module 132, an audio output unit 133, an input unit 134, a sensor 135, a display unit 136, a user input unit 137, an interface unit 138, a memory 139, and a processor 130.

It will be understood by those skilled in the art that the terminal 130 may further include a power supply (such as a battery) for supplying power to various components, and the power supply may be logically connected to the processor 130 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system. The terminal structure shown in fig. 13 does not constitute a limitation of the terminal, and the terminal may include more or less components than those shown, or combine some components, or have a different arrangement of components, and thus will not be described again.

It should be understood that, in the embodiment of the present application, the input Unit 134 may include a Graphics Processing Unit (GPU) 1341 and a microphone 1342, and the Graphics Processing Unit 1341 processes image data of still pictures or videos obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The display unit 136 may include a display panel 1361, and the display panel 1361 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 137 includes a touch panel 1371 and other input devices 1372. The touch panel 1371 is also referred to as a touch screen. The touch panel 1371 may include two parts of a touch detection device and a touch controller. Other input devices 1372 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

In the embodiment of the present application, the radio frequency unit 131 receives downlink data from a network side device and then processes the downlink data to the processor 130; in addition, the uplink data is sent to the network side equipment. Generally, the radio frequency unit 131 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory 139 may be used to store software programs or instructions as well as various data. The memory 139 may mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area may store an operating system, an application program or instruction (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. In addition, the Memory 139 may include a high-speed random access Memory, and may further include a nonvolatile Memory, wherein the nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), or a flash Memory. Such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.

Processor 130 may include one or more processing units; alternatively, the processor 130 may integrate an application processor, which primarily handles operating systems, user interfaces, and applications or instructions, etc., and a modem processor, which primarily handles wireless communications, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 130.

The radio frequency unit 131 is configured to obtain a disaster relief message of the second network side;

and a processor 130 for performing a first operation to maintain the network connection of the terminal in response to the disaster relief message.

The first operation comprises at least one of:

starting a second timer;

the first request is accepted.

According to the embodiment of the application, the terminal can still maintain network connection under the condition that the disaster of the second network is relieved, and service interruption is avoided.

Optionally, the processor 130 is further configured to perform a first operation according to at least one of the following first information;

wherein the first information comprises:

emergency service data being received or transmitted by the terminal;

a particular data network name;

slice-specific individual network slice selection assistance information;

a specific 5G quality of service identifier.

The first request includes at least one of:

a request for deregistration;

a protocol data unit session release request;

emergency services;

emergency service fallback;

high priority access.

Optionally, in a case that the first operation includes starting a second timer, the processor 130 is further configured to perform at least one of the following before the second timer expires:

stopping the process of releasing the connection of the trigger terminal;

stopping triggering the protocol data unit session release process;

non-access stratum signaling process that does not meet high priority;

non-access stratum signaling procedures that do not satisfy emergency services;

a non access stratum signaling procedure triggered by the first network side.

The processor 130 is further configured to execute a release procedure of the terminal connection when the second timer expires.

a release procedure of a protocol data unit session.

According to the embodiment of the application, after the first network side device acquires the second network disaster relief message, the first network side device assists the terminal to maintain network connection, and service interruption is avoided.

The embodiments of the present application further provide a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the process of the embodiment of the connection maintaining method is implemented, and the same technical effect can be achieved, and in order to avoid repetition, details are not repeated here.

Wherein, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a network-side device program or an instruction, to implement each process of the connection maintaining method embodiment, and achieve the same technical effect, and in order to avoid repetition, the details are not repeated here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatuses in the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions recited, e.g., the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application or portions thereof that contribute to the prior art may be embodied in the form of a software product, where the computer software product is stored in a storage medium (such as a ROM/RAM, a magnetic disk, and an optical disk), and includes several instructions for enabling a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network-side device, etc.) to execute the method described in the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A connection maintaining method, performed by a first network-side device, includes:

acquiring a disaster relief message of a second network side;

2. The method of claim 1, wherein the first operation comprises at least one of:

starting a second timer;

the first request is accepted.

3. The method of claim 1, wherein the performing the first operation comprises:

wherein the first information comprises:

emergency service data being received or transmitted by the terminal;

a particular data network name;

slice-specific individual network slice selection assistance information;

a specific 5G quality of service identifier.

4. The method of claim 2, wherein in the case that the first operation comprises accepting a first request, the first request comprises at least one of:

a request for deregistration;

a protocol data unit session modification request; wherein the type of the PDU session comprises at least one of: an emergency type protocol data unit session type, an initiated protocol data unit session type in a disaster scene, and other protocol data unit session types with high priority;

a protocol data unit session release request;

emergency services;

emergency service fallback;

high priority access.

5. The method of claim 2, wherein, in the event that the first operation comprises starting a second timer, the method further comprises:

before the second timer expires, performing at least one of the following:

stopping the process of releasing the connection of the trigger terminal;

stopping triggering the protocol data unit session release process;

non-access stratum signaling process that does not meet high priority;

non-access stratum signaling procedures that do not satisfy emergency services;

6. The method of claim 2, wherein, in the event that the first operation comprises starting a second timer, the method further comprises:

7. The method according to claim 6, wherein the terminal connection release procedure comprises at least one of:

a release procedure of a protocol data unit session.

8. A connection retention apparatus, comprising:

9. The apparatus of claim 8, wherein the first operation comprises at least one of:

starting a second timer;

the first request is accepted.

10. The apparatus of claim 8, wherein the execution module is configured to:

wherein the first information comprises:

emergency service data being received or transmitted by the terminal;

a particular data network name;

slice-specific individual network slice selection assistance information;

a specific 5G quality of service identifier.

11. The apparatus of claim 9, wherein in the case that the first operation comprises accepting a first request, the first request comprises at least one of:

a request for deregistration;

a protocol data unit session release request;

emergency services;

emergency service fallback;

high priority access.

12. The apparatus of claim 9, wherein in the event that the first operation comprises starting a second timer, the execution module is further configured to:

before the second timer expires, performing at least one of the following:

stopping the process of releasing the connection of the trigger terminal;

stopping triggering the protocol data unit session release process;

non-access stratum signaling process that does not meet high priority;

non-access stratum signaling procedures that do not satisfy emergency services;

13. The apparatus of claim 9, wherein in the event that the first operation comprises starting a second timer, the execution module is further configured to:

14. The apparatus of claim 13, wherein the release procedure of the terminal connection comprises at least one of:

a release procedure of a protocol data unit session.

15. A connection maintenance method, performed by a terminal, comprising:

acquiring a disaster relief message of a second network side;

16. The method according to claim 15, wherein the terminal is a terminal accessed from the second network side to the first network side when the second network side is in a disaster state.

17. The method of claim 15, wherein the second information comprises at least one of:

18. The method of claim 15, wherein the second operation comprises:

19. The method of claim 15, wherein after obtaining the disaster relief message for the second network, the method further comprises:

20. The method of claim 19, wherein after starting the first timer, the method further comprises:

before the first timer is timed out, at least one of the following is executed:

deregister;

releasing the protocol data unit session;

and releasing the non-access stratum.

21. A connection retention apparatus, comprising:

22. The apparatus of claim 21, wherein the terminal is a terminal accessed from the second network side to the first network side when the second network side is in a disaster state.

23. The apparatus of claim 21, wherein the second information comprises at least one of:

24. The apparatus of claim 21, wherein the second operation comprises:

25. The apparatus of claim 21, wherein the receiving module is further configured to:

26. The apparatus of claim 25, wherein the operation module is further configured to:

before the first timer is timed out, at least one of the following is executed:

deregister;

releasing the protocol data unit session;

and releasing the non-access stratum.

27. A network-side device comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the connection maintaining method according to any one of claims 1 to 7.

28. A terminal comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing the steps of the connection maintenance method according to any one of claims 15 to 20.

29. A readable storage medium, characterized in that a program or instructions are stored on the readable storage medium, which program or instructions, when executed by a processor, implement the connection maintaining method according to any one of claims 1-7, or the steps of the connection maintaining method according to any one of claims 15 to 20.