CN113015265B - Network session self-healing method, device, system, computer equipment and storage medium - Google Patents
Network session self-healing method, device, system, computer equipment and storage medium Download PDFInfo
- Publication number
- CN113015265B CN113015265B CN202110204938.5A CN202110204938A CN113015265B CN 113015265 B CN113015265 B CN 113015265B CN 202110204938 A CN202110204938 A CN 202110204938A CN 113015265 B CN113015265 B CN 113015265B
- Authority
- CN
- China
- Prior art keywords
- terminal
- network
- authentication
- session
- rejection
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 66
- 238000004590 computer program Methods 0.000 claims description 23
- 230000008569 process Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 5
- 239000004973 liquid crystal related substance Substances 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000006855 networking Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000007796 conventional method Methods 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/18—Management of setup rejection or failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Telephonic Communication Services (AREA)
Abstract
The application relates to a network session self-healing method, a device, a system, computer equipment and a storage medium, wherein the network session self-healing method is used for receiving session rejection request information sent by a network end and judging whether a rejection reason carried by the session rejection request information is a preset rejection reason or not; if the reject cause is the preset reject cause, setting the authentication type in the dialing request to be null, and re-initiating the dialing request to the network terminal. According to the network session self-healing method, after the dialing request is refused, the terminal sets the authentication type to be null and then reinitiates the dialing request, so that the terminal can be ensured to normally perform data service.
Description
Technical Field
The present invention relates to the field of terminal technologies, and in particular, to a network session self-healing method, device, system, computer device, and storage medium.
Background
With the development of network communication technology, 5G networks and terminals thereof are also being popularized on a large scale. However, in the initial stage of 5G network deployment, because the network and the terminal are not mature, the situation that the 5G independent networking user cannot access the network often occurs. The specific process is as follows: after the SA network registration process is completed, the user can carry out data service through the PDU session establishment process, PDU carries authentication information to carry out session establishment when carrying out session request, if authentication fails, PDU session establishment can be refused, so that the user can not carry out data service and can not recover autonomously.
In the prior art, a method for ensuring that a user can normally perform data service after authentication failure is not available.
Disclosure of Invention
Based on the foregoing, it is necessary to provide a network session self-healing method, apparatus, system, computer device and storage medium.
In a first aspect, an embodiment of the present application provides a network session self-healing method, including:
receiving session rejection request information sent by a network side, wherein the session rejection request information comprises rejection reasons;
judging whether a rejection reason carried by the session rejection request information is a preset rejection reason or not;
if the reject cause is the preset reject cause, setting the authentication type in the dialing request to be null, and re-initiating the dialing request to the network terminal.
In one embodiment, the preset reject cause is an authentication failure.
In a second aspect, an embodiment of the present application provides a network session self-healing method, including:
receiving a dialing request sent by a terminal;
authenticating the terminal according to the dialing request;
if the authentication is unsuccessful, sending session rejection request information carrying a rejection reason to the terminal, wherein the session rejection request information is used for indicating the terminal to initiate a dialing request to the network again after setting the authentication type to be null under the condition that the rejection reason is a preset rejection reason.
In one embodiment, the dialing request includes user identification information and/or authentication type, and authenticating the terminal according to the dialing request includes:
and authenticating the terminal according to the user identity identification information and/or the authentication type.
In one embodiment, the dialing request includes user identification information, the user identification information includes a user name and a user password, and authenticating the terminal according to the user identification information includes:
judging whether the user name is matched with a preset user name or not, and judging whether the user password is matched with the preset user password or not;
if the user name is not matched with at least one of the preset user name and the user password, determining that the authentication fails.
In one embodiment, the dialing request includes an authentication type, and authenticating the terminal according to the authentication type includes:
judging whether the authentication type is matched with a preset authentication type or not;
if the authentication type is not matched with the preset authentication type, determining that the authentication fails.
In a third aspect, an embodiment of the present application provides a network session self-healing system, including: the terminal and the network end, wherein the terminal end is used for executing the steps of the network session self-healing method provided by the embodiment; the network side is used for executing the steps of the network session self-healing method provided by the embodiment.
In a fourth aspect, an embodiment of the present application provides a network session self-healing device, including:
the first receiving module is used for receiving session rejection request information sent by the network side, wherein the session rejection request information comprises rejection reasons;
the first judging module is used for judging whether the reject reason carried by the session reject request information is a preset reject reason or not;
the setting module is used for setting the authentication type in the dialing request to be null if the reject cause is a preset reject cause, and re-initiating the dialing request to the network terminal.
In a fifth aspect, an embodiment of the present application provides a network session self-healing device, including:
the second receiving module is used for receiving a dialing request sent by the terminal;
the second judging module is used for authenticating the terminal according to the dialing request;
the sending module is used for sending session rejection request information carrying rejection reasons to the terminal if the authentication is unsuccessful, wherein the session rejection request information is used for indicating the terminal to initiate a dialing request to the network terminal again after setting the authentication type to be empty under the condition that the rejection reasons are preset.
In a sixth aspect, an embodiment of the present application provides a computer device, including a memory and a processor, the memory storing a computer program, the processor implementing the steps of the method as provided in the above embodiment when executing the computer program.
In a seventh aspect, an embodiment of the present application further provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the method as provided by the above embodiments.
The embodiment of the application provides a network session self-healing method, a device, a system, computer equipment and a storage medium. The network session self-healing method terminal obtains session rejection request information sent by a network terminal; judging whether the reject reason carried by the session reject request information is a preset reject reason or not; if the reject cause is the preset reject cause, the terminal sets the authentication type in the dialing request to be null, and then initiates the dialing request to the network again. According to the network session self-healing method provided by the embodiment of the application, after the authentication type in the dialing request is set to be null, the dialing request is initiated to the network terminal, and the network terminal can directly pass through the dialing request, so that the terminal can normally conduct data service. In addition, after the terminal refuses the first dialing request, the network session self-healing method provided by the embodiment of the application can initiate the dialing request to the network again after the authentication type in the dialing request is set to be empty, and the network session self-healing method can recover autonomously, so that the user experience is better.
Drawings
In order to more clearly illustrate the technical solutions of embodiments or conventional techniques of the present application, the drawings that are required to be used in the description of the embodiments or conventional techniques will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for different persons skilled in the art.
Fig. 1 is an application scenario diagram of a network session self-healing method according to an embodiment of the present application;
fig. 2 is a schematic flow chart of steps of a network session self-healing method according to an embodiment of the present application;
fig. 3 is a schematic flow chart of steps of a network session self-healing method according to an embodiment of the present application;
fig. 4 is a schematic flow chart of steps of a network session self-healing method according to an embodiment of the present application;
fig. 5 is a schematic flow chart of steps of a network session self-healing method according to an embodiment of the present application;
FIG. 6 is a flowchart illustrating steps of a method for performing self-healing of a network session according to a self-healing system of a network session according to one embodiment of the present application;
fig. 7 is a schematic structural diagram of a network session self-healing device according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a network session self-healing device according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
In order to make the above objects, features and advantages of the present application more comprehensible, embodiments accompanied with figures are described in detail below. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is, however, susceptible of embodiment in many other forms than those described herein and similar modifications can be made by those skilled in the art without departing from the spirit of the application, and therefore the application is not to be limited to the specific embodiments disclosed below.
The network session self-healing method provided by the application can be applied to an application environment shown in fig. 1. The network side 100 refers to a 5G independent networking side, and the terminal 200 refers to a terminal on the user side. The network terminal 100 is connected to the terminal 200 through a 5G communication network. Terminal 200 accesses the 5G network using DNN network access technology. After the terminal 200 completes the registration of the 5G independent networking end, the network end 100 includes registration information of the terminal 200. When the terminal 200 needs to perform a data service, a dialing request, that is, a session request, is initiated to the network end 100; after the dialing is successful, that is, after the network side 100 requests the dialing from the terminal 200, the terminal 200 can perform the data service. However, since the 5G network and the terminal are not mature, the registration information of the terminal 200 included in the network side 100 may be wrong, or the user modifies the information of the terminal 200, so that the network side 100 determines that the terminal 200 has no access right through authentication, and the network side 100 refuses the dialing request of the terminal 200, and the user of the terminal 200 cannot perform the data service. The terminal 200 may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, portable wearable devices, and the like.
The network session self-healing method provided by the application can be realized through computer equipment. Computer devices include, but are not limited to, control chips, personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices. The method provided by the application can be realized by JAVA software and can also be applied to other software.
The following describes the technical solution of the present application and how the technical solution of the present application solves the technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
The numbering of the components itself, e.g. "first", "second", etc., is used herein merely to distinguish between the described objects and does not have any sequential or technical meaning. The terms "coupled" and "connected," as used herein, are intended to encompass both direct and indirect coupling (coupling), unless otherwise indicated.
Referring to fig. 2, an embodiment of the present application provides a network session self-healing method, and the embodiment is applied to a terminal for explanation, where the terminal refers to a terminal on a user side. The network session self-healing method comprises the following specific steps:
step 201, receiving session rejection request information sent by a network side, where the session rejection request information includes a rejection reason.
And the terminal receives the session rejection request information sent by the network terminal. That is, after the terminal sends the dialing request to the network, the network responds according to the dialing request. If the network side determines that the terminal has no access right through authentication, the network side sends session rejection request information to the terminal, namely, the dialing request of the terminal is rejected. The session rejection request information includes a specific reason that the network end rejects the dialing request of the terminal.
Step 202, judging whether the reject reason carried by the session reject request information is a preset reject reason.
After receiving the session rejection request information, the terminal compares the rejection reason carried by the session rejection request information with a preset rejection reason to judge whether the rejection reason is the preset rejection reason. The preset reject cause may be set by a worker according to the cause of authentication failure, which is not limited in this embodiment.
Step 203, if the reject cause is a preset reject cause, setting the authentication type in the dialing request to be null, and re-initiating the dialing request to the network.
If the terminal judges that the reject reason carried by the session reject request information is consistent with the preset reject reason, the network side is stated to determine the access right of the terminal through authentication. At this time, the terminal re-initiates the dialing request to the network terminal after setting the authentication type in the dialing request to null. Authentication refers to the authentication of a terminal by a network end to determine whether the terminal has the right to access the network. Authentication types include CHAP, PAP, NONE, PAP/CHAP. Different authentication types are embodied as different hexadecimal values in the dial request. Wherein, the authentication type represented by 30281 is NONE, the authentication type represented by 49187 is PAP, and the authentication type represented by 49699 is CHAP. CHAP is a challenge-response protocol, three-way handshake authentication is performed, password information is transmitted in an encrypted manner, and safety is high; PAP is a simple two-way handshake authentication protocol, with user name and password plaintext transfer, and security. When the authentication type in the dialing request received by the network is empty, the terminal directly passes through the dialing request, and the terminal successfully dials and can normally perform data service.
The embodiment of the application provides a network session self-healing method, a terminal obtains session rejection request information sent by a network terminal; judging whether the reject reason carried by the session reject request information is a preset reject reason or not; if the reject cause is the preset reject cause, the terminal sets the authentication type in the dialing request to be null, and then initiates the dialing request to the network again. According to the network session self-healing method provided by the embodiment of the application, after the authentication type in the dialing request is set to be null, the dialing request is initiated to the network terminal, and the network terminal can directly pass through the dialing request, so that the terminal can normally conduct data service. In addition, after the terminal refuses the first dialing request, the network session self-healing method provided by the embodiment of the application can initiate the dialing request to the network again after the authentication type in the dialing request is set to be empty, and the network session self-healing method can recover autonomously, so that the user experience is better.
In one embodiment, the preset reject cause is an authentication failure. The authentication fails, and the terminal has no right to access the network. In a specific embodiment, the preset reject cause is indicated by the flag # 29. In this embodiment, it is specifically described that the preset reject cause is authentication failure, so that the efficiency of the terminal in judging the reject cause carried by the session reject request information can be improved, and thus the self-healing time of the network session can be shortened.
Referring to fig. 3, an embodiment of the present application provides a network session self-healing method, and the embodiment is applied to a network end for explanation by the method. The network session self-healing method comprises the following specific steps:
step 301, a dialing request sent by a terminal is received.
And 302, authenticating the terminal according to the dialing request.
After the terminal initiates the dialing request, the terminal receives the dialing request to the corresponding network end. The dialing request includes information stored in the network end when the terminal registers. And the network terminal authenticates the information in the dialing request according to the received dialing request and judges whether the terminal has the right to access the network. The specific process of authenticating the terminal by the network terminal according to the dialing request is not limited in this embodiment, as long as the function can be realized.
Step 303, if the authentication is unsuccessful, sending session rejection request information carrying a rejection reason to the terminal, where the session rejection request information is used to instruct the terminal to initiate a dialing request to the network again after setting the authentication type to be null under the condition that the rejection reason is a preset rejection reason.
If the network side judges that the terminal does not have the right to access the network, the authentication is not successful. At this time, the network side may send session rejection request information to the terminal, where the session rejection request information includes a specific reason that the network side rejects the terminal dialing request. The session rejection request information may further include an ID of the terminal corresponding to the session rejection request information. For a specific description of setting the authentication type to be null when the rejection cause carried by the terminal according to the session rejection request information is a preset rejection cause, reference may be made to the description in the foregoing embodiment, which is not repeated herein.
After the network session self-healing method provided by the application receives a dialing request of a terminal, authenticating the terminal; and after the authentication is unsuccessful, sending session rejection request information to the terminal, setting the authentication type in the dialing request to be sent by the terminal to be null when the terminal receives the rejection reason carried in the session rejection request for a preset rejection reason, and re-initiating the dialing request to the network terminal. Therefore, authentication at the network end is unsuccessful, so that the terminal can perform corresponding processing in time, the terminal can dial successfully as soon as possible, normal data service can be performed, and user experience is good.
Referring to fig. 4, in one embodiment, the dialing request includes user identification information and/or authentication type, and step 302 authenticates the terminal according to the dialing request, including:
step 401, authenticating the terminal according to the user identity information and/or the authentication type.
The dialing request sent by the terminal to the network end can comprise user identification information corresponding to the terminal, authentication type of the user corresponding to the terminal, and user identification information and authentication type corresponding to the terminal. The user identification information is information for identifying the identity of the user corresponding to the terminal. The specific description of the authentication type may refer to the description in the above embodiment, and will not be repeated here.
With continued reference to fig. 4, in one embodiment, when the dialing request includes user identification information, the specific steps of authenticating the terminal according to the user identification information include:
step 402, judging whether the user name is matched with a preset user name or not, and judging whether the user password is matched with the preset user password or not.
Step 403, if the user name is not matched with at least one of the preset user name and the user password, determining that the authentication fails.
The user identification information included in the dialing request sent by the terminal includes a user name and a user password. The network terminal comprises a preset user name and a preset user password which are set by the terminal during registration. After receiving a dialing request sent by a terminal, the network end matches the user name in the received user identification information with a preset user name, and matches the user password in the received user identification information with the preset user password. If the network side judges that the user name is not matched with the preset user name, the authentication is determined to be failed, and the network side determines that the terminal does not have the right to access the network; if the network side judges that the user password is not matched with the preset user password, determining authentication failure; if the network side judges that the user name is not matched with the preset user name and the user password is not matched with the preset user password, the authentication failure is determined.
In this embodiment, the network determines whether the authentication of the network is successful by identifying whether the user name of the terminal matches with a preset user name and/or whether the user password matches with a preset user password, so that the judging method is simple and fast, and the self-healing time of the network session can be shortened.
Referring to fig. 5, in one embodiment, when the dialing request includes an authentication type, authenticating the terminal according to the authentication type includes:
step 504, judging whether the authentication type is matched with the preset authentication type.
Step 502, if the authentication type is not matched with the preset authentication type, determining that the authentication fails.
The network terminal comprises a preset authentication type set by the terminal during registration. After receiving a dialing request sent by a terminal, the network end matches an authentication type in the received dialing request with a preset authentication type. If the network side judges that the authentication type is not matched with the preset authentication type, the authentication failure is determined, and the network side determines that the terminal does not have the right to access the network.
In this embodiment, the network determines whether the authentication of the network is successful by judging whether the authentication type of the terminal is matched with the preset authentication type, so that the authentication speed of the terminal can be improved, and the self-healing time of the network session can be shortened.
It should be understood that, although the steps in the flowcharts in fig. 2-5 are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in fig. 2-5 may include multiple sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, nor do the order in which the sub-steps or stages are performed necessarily occur sequentially, but may be performed alternately or alternately with at least a portion of the sub-steps or stages of other steps or steps.
An embodiment of the application provides a network session self-healing system, which comprises a terminal and a network end. The terminal is configured to execute the steps of the network session self-healing method provided in the embodiment shown in fig. 2 in the foregoing embodiment; the network side is configured to execute the steps of the network session self-healing method provided in the embodiments shown in fig. 3 to 5.
Referring to fig. 6, the steps of executing the network session self-healing method in the network session self-healing system provided in this embodiment include:
step 601, a terminal sends a dialing request to a network terminal;
step 602, the network terminal authenticates the terminal according to the dialing request;
step 603, if the authentication of the network end to the terminal is unsuccessful, sending a session rejection request message carrying a rejection reason to the terminal;
step 604, after receiving the session rejection request information, the terminal determines whether the rejection reason carried by the session rejection request information is a preset rejection reason;
step 605, if the reject cause is a preset reject cause, setting the authentication type in the dialing request to be null, and re-initiating the dialing request to the network.
The specific embodiment process and beneficial effects of the network session self-healing system provided in this embodiment are similar to those described in the foregoing embodiments, and are not described herein again.
Referring to fig. 7, an embodiment of the present application provides a network session self-healing device 10, which includes a first receiving module 11, a first judging module 12, and a setting module 13. Wherein, the liquid crystal display device comprises a liquid crystal display device,
the first receiving module 11 is configured to receive session rejection request information sent by a network side, where the session rejection request information includes a rejection reason;
the first judging module 12 is configured to judge whether a reject reason carried by the session reject request information is a preset reject reason;
the setting module 13 is configured to set the authentication type in the dialing request to null if the reject cause is a preset reject cause, and re-initiate the dialing request to the network.
Referring to fig. 8, an embodiment of the present application provides a network session self-healing device 20, which includes a second receiving module 21, a second judging module 22, and a sending module 23. Wherein, the liquid crystal display device comprises a liquid crystal display device,
the second receiving module 21 is configured to receive a dialing request sent by the terminal;
the second judging module 22 is used for authenticating the terminal according to the dialing request;
the sending module 23 is configured to send, if the authentication is unsuccessful, session rejection request information carrying a rejection reason to the terminal, where the session rejection request information is used to instruct the terminal to initiate a dialing request to the network again after setting the authentication type to null if the rejection reason is a preset rejection reason.
In one embodiment, the second determining module 22 comprises an authentication unit for authenticating the terminal according to the user identification information and/or the authentication type when the dialing request comprises the user identification information and/or the authentication type.
In one embodiment, the authentication unit is configured to determine whether the user name matches a preset user name and determine whether the user password matches a preset user password when the dialing request includes user identification information; if the user name is not matched with at least one of the preset user name and the user password, determining that the authentication fails.
In one embodiment, the authentication unit is further configured to determine, when the dialing request includes an authentication type, whether the authentication type matches a preset authentication type; if the authentication type is not matched with the preset authentication type, determining that the authentication fails.
The specific limitation of the above-mentioned network session self-healing device 10 and the network session self-healing device 20 can be referred to the limitation of the network session self-healing method hereinabove, and will not be repeated here. The respective modules in the network session self-healing device 10 and the network session self-healing device 20 may be implemented in whole or in part by software, hardware, and combinations thereof. The above devices, modules or units may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above devices or modules.
Referring to fig. 9, in one embodiment, a computer device is provided, which may be a server, and an internal structure thereof may be as shown in fig. 9. The computer device includes a processor, memory, network interface, and database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes non-volatile storage media, internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is used for storing dialing requests, preset user names, preset user passwords, preset authentication types and the like. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer device, when executed by the processor, implements a network session self-healing method.
It will be appreciated by those skilled in the art that the structure shown in fig. 9 is merely a block diagram of a portion of the structure associated with the present application and is not limiting of the computer device to which the present application applies, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory having a computer program stored therein and a processor, the processor when executing the computer program performing the steps of:
receiving session rejection request information sent by a network side, wherein the session rejection request information comprises rejection reasons;
judging whether a rejection reason carried by the session rejection request information is a preset rejection reason or not;
if the reject cause is the preset reject cause, setting the authentication type in the dialing request to be null, and re-initiating the dialing request to the network terminal.
In one embodiment, a computer device is provided, comprising a memory having a computer program stored therein and a processor, the processor when executing the computer program performing the steps of:
receiving a dialing request sent by a terminal;
authenticating the terminal according to the dialing request;
if the authentication is unsuccessful, sending session rejection request information carrying a rejection reason to the terminal, wherein the session rejection request information is used for indicating the terminal to initiate a dialing request to the network again after setting the authentication type to be null under the condition that the rejection reason is a preset rejection reason.
In one embodiment, the processor when executing the computer program further performs the steps of: when the dialing request comprises user identification information and/or authentication type, authenticating the terminal according to the user identification information and/or authentication type.
In one embodiment, the processor when executing the computer program further performs the steps of: when the dialing request comprises user identity identification information, judging whether the user name is matched with a preset user name or not, and judging whether the user password is matched with the preset user password or not; if the user name is not matched with at least one of the preset user name and the user password, determining that the authentication fails.
In one embodiment, the processor when executing the computer program further performs the steps of: when the dialing request comprises an authentication type, judging whether the authentication type is matched with a preset authentication type; if the authentication type is not matched with the preset authentication type, determining that the authentication fails.
The specific processes and beneficial effects of executing the computer program by the computer device processor provided in the above embodiments to implement the above method steps are similar to those of the corresponding method embodiments, and are not described herein again.
In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, performs the steps of:
receiving session rejection request information sent by a network side, wherein the session rejection request information comprises rejection reasons;
judging whether a rejection reason carried by the session rejection request information is a preset rejection reason or not;
if the reject cause is the preset reject cause, setting the authentication type in the dialing request to be null, and re-initiating the dialing request to the network terminal.
In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, performs the steps of:
receiving a dialing request sent by a terminal;
authenticating the terminal according to the dialing request;
if the authentication is unsuccessful, sending session rejection request information carrying a rejection reason to the terminal, wherein the session rejection request information is used for indicating the terminal to initiate a dialing request to the network again after setting the authentication type to be null under the condition that the rejection reason is a preset rejection reason.
In one embodiment, the computer program when executed by the processor further performs the steps of: when the dialing request comprises user identification information and/or authentication type, authenticating the terminal according to the user identification information and/or authentication type.
In one embodiment, the computer program when executed by the processor further performs the steps of: when the dialing request comprises user identity identification information, judging whether the user name is matched with a preset user name or not, and judging whether the user password is matched with the preset user password or not; if the user name is not matched with at least one of the preset user name and the user password, determining that the authentication fails.
In one embodiment, the computer program when executed by the processor further performs the steps of: when the dialing request comprises an authentication type, judging whether the authentication type is matched with a preset authentication type; if the authentication type is not matched with the preset authentication type, determining that the authentication fails.
The specific processes and beneficial effects of implementing the steps of the method according to the above embodiment are similar to those of the corresponding method embodiment, and are not described herein.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the various embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), memory bus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples only represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the present application. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application is to be determined by the claims appended hereto.
Claims (11)
1. A network session self-healing method, comprising:
receiving session rejection request information sent by a network side, wherein the session rejection request information comprises rejection reasons; the session rejection information is generated when the network terminal authenticates the terminal according to the user identification information and/or authentication information in the dialing request and the authentication is unsuccessful; the user identity identification information and/or authentication information is information stored in the network end when the terminal is registered;
judging whether the reject reason carried by the session reject request information is a preset reject reason or not;
if the reject cause is the preset reject cause, setting the authentication type in the dialing request to be null, and re-initiating the dialing request to the network end so as to carry out data service after successful dialing.
2. A network session self-healing method, comprising:
receiving a dialing request sent by a terminal; the dialing request comprises user identity identification information and/or authentication information; the user identity identification information and/or authentication information is information stored in a network end when the terminal is registered and is used for judging whether the terminal has the right of accessing a network or not;
authenticating the terminal according to the user identity identification information and/or the authentication type;
if the authentication is unsuccessful, sending session rejection request information carrying a rejection reason to the terminal, wherein the session rejection request information is used for indicating the terminal to initiate a dialing request to the network terminal again after setting the authentication type to be null under the condition that the rejection reason is a preset rejection reason.
3. The network session self-healing method according to claim 2, wherein the dialing request includes user identification information, the user identification information includes a user name and a user password, and the authenticating the terminal according to the user identification information includes:
judging whether the user name is matched with a preset user name or not, and judging whether the user password is matched with a preset user password or not;
and if the user name is not matched with at least one of the preset user name and the user password, determining that authentication fails.
4. The network session self-healing method according to claim 2, wherein the dialing request includes an authentication type, and the authenticating the terminal according to the authentication type includes:
judging whether the authentication type is matched with a preset authentication type or not;
and if the authentication type is not matched with the preset authentication type, determining authentication failure.
5. A network session self-healing system, comprising: a terminal and a network end, wherein the terminal is used for executing the steps of the network session self-healing method according to claim 1; the network side is configured to perform the steps of the network session self-healing method according to any one of claims 2 to 4.
6. A network session self-healing device, comprising:
the first receiving module is used for receiving session rejection request information sent by a network side, wherein the session rejection request information comprises rejection reasons; the session rejection information is generated when the network terminal authenticates the terminal according to the user identification information and/or authentication information in the dialing request and the authentication is unsuccessful; the user identity identification information and/or authentication information is information stored in the network end when the terminal is registered;
the first judging module is used for judging whether the reject reason carried by the session reject request information is a preset reject reason or not;
and the setting module is used for setting the authentication type in the dialing request to be null if the rejection reason is the preset rejection reason, and re-initiating the dialing request to the network terminal so as to carry out data service after successful dialing.
7. A network session self-healing device, comprising:
the second receiving module is used for receiving a dialing request sent by the terminal; the dialing request comprises user identity identification information and/or authentication information; the user identity identification information and/or authentication information is information stored in a network end when the terminal is registered and is used for judging whether the terminal has the right of accessing a network or not;
the second judging module is used for authenticating the terminal according to the user identity identification information and/or the authentication type so as to judge whether the terminal has the right of accessing the network or not;
the sending module is used for sending session rejection request information carrying rejection reasons to the terminal if the authentication is unsuccessful, wherein the session rejection request information is used for indicating the terminal to initiate a dialing request to a network terminal again after setting the authentication type to be empty under the condition that the rejection reasons are preset rejection reasons.
8. The apparatus of claim 7, wherein the dialing request includes user identification information including a user name and a user password; the second judging module comprises an authentication unit, wherein the authentication unit is used for judging whether the user name is matched with a preset user name or not and judging whether the user password is matched with the preset user password or not; and if the user name is not matched with at least one of the preset user name and the user password, determining that authentication fails.
9. The apparatus of claim 7, wherein the dialing request includes an authentication type; the authentication module is also used for judging whether the authentication type is matched with a preset authentication type or not; and if the authentication type is not matched with the preset authentication type, determining authentication failure.
10. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 4 when the computer program is executed.
11. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110204938.5A CN113015265B (en) | 2021-02-24 | 2021-02-24 | Network session self-healing method, device, system, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110204938.5A CN113015265B (en) | 2021-02-24 | 2021-02-24 | Network session self-healing method, device, system, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113015265A CN113015265A (en) | 2021-06-22 |
| CN113015265B true CN113015265B (en) | 2023-07-18 |
Family
ID=76409042
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110204938.5A Active CN113015265B (en) | 2021-02-24 | 2021-02-24 | Network session self-healing method, device, system, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113015265B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115065799B (en) * | 2021-09-03 | 2023-05-16 | 荣耀终端有限公司 | Video call method and electronic equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017197766A1 (en) * | 2016-05-17 | 2017-11-23 | 中兴通讯股份有限公司 | Calling method and device |
| CN108476536A (en) * | 2016-03-29 | 2018-08-31 | Oppo广东移动通信有限公司 | The method and apparatus of wireless communication |
| CN109391940A (en) * | 2017-08-02 | 2019-02-26 | 华为技术有限公司 | A kind of method, equipment and system accessing network |
| WO2020073802A1 (en) * | 2018-10-09 | 2020-04-16 | 华为技术有限公司 | Authentication method and device |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050265318A1 (en) * | 2004-01-08 | 2005-12-01 | Nokia Corporation | Apparatus, system, and method for rejecting a session establishment request |
| US20050154793A1 (en) * | 2004-01-08 | 2005-07-14 | Hisham Khartabil | Apparatus, system, and method for rejecting a session establishment request |
| US20080293407A1 (en) * | 2007-05-24 | 2008-11-27 | Jean-Philippe Cormier | Wireless Device and Method for Determining Which APN to Use |
| CN107743316A (en) * | 2017-09-06 | 2018-02-27 | 深圳天珑无线科技有限公司 | A kind of reminding method, mobile terminal and storage device for recovering network connection |
| CN107948976A (en) * | 2017-12-01 | 2018-04-20 | 广东欧珀移动通信有限公司 | The detection method and device of LTE network access result, computer-readable storage medium |
-
2021
- 2021-02-24 CN CN202110204938.5A patent/CN113015265B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108476536A (en) * | 2016-03-29 | 2018-08-31 | Oppo广东移动通信有限公司 | The method and apparatus of wireless communication |
| WO2017197766A1 (en) * | 2016-05-17 | 2017-11-23 | 中兴通讯股份有限公司 | Calling method and device |
| CN109391940A (en) * | 2017-08-02 | 2019-02-26 | 华为技术有限公司 | A kind of method, equipment and system accessing network |
| WO2020073802A1 (en) * | 2018-10-09 | 2020-04-16 | 华为技术有限公司 | Authentication method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113015265A (en) | 2021-06-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110266656B (en) | Secret-free authentication identity identification method and device and computer equipment | |
| CN110266642A (en) | Identity identifying method and server, electronic equipment | |
| CN106559213B (en) | Equipment management method, equipment and system | |
| CN111586671B (en) | Embedded user identification card configuration method and device, communication equipment and storage medium | |
| CN111880919B (en) | Data scheduling method, system and computer equipment | |
| CN112448956B (en) | Authority processing method and device of short message verification code and computer equipment | |
| CN112187465B (en) | Non-inductive login method, device, computer equipment and storage medium | |
| CN104869121A (en) | 802.1x-based authentication method and device | |
| CN113015265B (en) | Network session self-healing method, device, system, computer equipment and storage medium | |
| EP4057661A1 (en) | System, module, circuitry and method | |
| CN113872990B (en) | VPN network certificate authentication method and device based on SSL protocol and computer equipment | |
| CN114095256B (en) | Terminal authentication method, system, equipment and storage medium based on edge calculation | |
| CN110769482A (en) | Method and device for network connection of wireless equipment and wireless router equipment | |
| CN109711140A (en) | Website logging state control method, device, computer equipment and storage medium | |
| CN110225511B (en) | Method, device and system for acquiring IMEI number of terminal and computer equipment | |
| CN112437068A (en) | Authentication and key agreement method, device and system | |
| CN112422516A (en) | Connection method and device of power system, computer equipment and storage medium | |
| CN104331649A (en) | Identity recognition system and method based on network connection | |
| CN110650132A (en) | Access method and device of edge computing node, computer equipment and storage medium | |
| US11751059B1 (en) | Subscriber identification module (SIM) application authentication | |
| CN111541642B (en) | Bluetooth encryption communication method and device based on dynamic secret key | |
| CN110768886B (en) | Method, device, computer equipment and medium for automatically connecting VPN (virtual private network) by application program | |
| CN114257406A (en) | Equipment communication method and device based on identification algorithm and computer equipment | |
| CN109561093B (en) | Unauthorized behavior detection method and device, computer equipment and storage medium | |
| CN111563247A (en) | Method and device for logging in system by intelligent key equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |