CN114173336A

CN114173336A - Processing method, device, terminal and network side equipment for authentication failure

Info

Publication number: CN114173336A
Application number: CN202010847188.9A
Authority: CN
Inventors: 张鹏飞; 柯小婉; 康艳超
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2020-08-21
Filing date: 2020-08-21
Publication date: 2022-03-11
Anticipated expiration: 2040-08-21
Also published as: CN114173336B; WO2022037619A1

Abstract

The application discloses a processing method, a processing device, a terminal and network side equipment for authentication failure, and belongs to the technical field of wireless communication. The processing method for authentication failure comprises the following steps: under the condition that the authentication of the terminal is failed, an access and mobile management functional entity determines an authentication failure reason value returned to the terminal according to a first message, wherein the first message indicates whether a current network is used for configuring network access (onboarding) of the terminal; and sending a second message to the terminal, wherein the second message carries the authentication failure reason value.

Description

Processing method, device, terminal and network side equipment for authentication failure

Technical Field

The application belongs to the technical field of wireless communication, and particularly relates to a method, a device, a terminal and network side equipment for processing authentication failure.

Background

Configuring Network access (interworking) refers to a terminal accessing a current Network to obtain information such as a certificate of a target independent Non-Public Network (SNPN).

At present, when a terminal selects an independent non-public network (O-SNPN) configured for network access, if there are multiple O-SNPNs, one of the O-SNPNs may be manually selected by a user or randomly selected by the terminal for onboarding, and a registration request is initiated to the O-SNPN, while the network side needs to authenticate the terminal in the process, and in the authentication process, there may be a case of authentication failure. In the related art, when the terminal fails to authenticate in the network, a cause value (cause value) sent by the network side to the terminal includes: #3, #74, #75, etc. However, these cause values specified in the current protocol cannot cover the authentication failure in the onboarding procedure, for example, if the received cause value is #3, the terminal determines that the entry corresponding to the SNPN of the current service in the subscription information list (list of subscriber data) of the terminal is invalid. However, the current service SNPN simply fails to authenticate the UE as an onboarding network, and the subscription information of the terminal in the SNPN is not invalid, so it is not appropriate to invalidate the subscription information corresponding to the current service SNPN.

Therefore, in the related art, when the terminal performs onkeying, after the network fails to authenticate the terminal, the terminal cannot return a corresponding authentication failure cause value to the terminal according to whether the current network is used for onkeying, and further, an operation error executed by the terminal according to the authentication failure cause value returned by the network side may be caused.

Disclosure of Invention

The embodiment of the application provides a processing method, a processing device, a terminal and a network side device for authentication failure, which can solve the problem that the network side device cannot return a corresponding authentication failure cause value to the terminal according to whether the current network is used for onkeying.

In a first aspect, a method for handling authentication failure is provided, where the method includes: under the condition that the authentication of the terminal is failed, an access and mobile management functional entity determines an authentication failure reason value returned to the terminal according to a first message, wherein the first message indicates whether a current network is used for configuring network access (onboarding) of the terminal; and sending a second message to the terminal, wherein the second message carries the authentication failure reason value.

In a second aspect, an apparatus for processing authentication failure is provided, the apparatus comprising: a determining module, configured to determine, according to a first message, an authentication failure cause value returned to a terminal when authentication of the terminal fails, where the first message indicates whether a current network is used for configuring network access establishment of the terminal; and the first transceiver module is configured to send a second message to the terminal, where the second message carries the authentication failure cause value.

In a third aspect, a method for handling authentication failure is provided, where the method includes: the terminal receives a second message, wherein the authentication failure reason value carried in the second message; and if the authentication failure indicated by the authentication failure reason value is determined to be the authentication failure of the onboarding process of the terminal, marking the currently accessed independent non-public network SNPN as the network forbidden to be selected as the onboarding.

In a fourth aspect, there is provided an apparatus for processing authentication failure, the apparatus comprising: the second transceiver module is configured to receive a second message, where the authentication failure cause value is carried in the second message; and the processing module is used for marking the independent non-public network SNPN accessed currently as the network forbidden to be selected as the onboarding if the authentication failure indicated by the authentication failure reason value is determined to be the authentication failure in the onboarding process of the terminal.

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, which when executed by the processor, performs the steps of the method according to the first 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 to implement the method according to the first aspect, or the processor is configured to execute a terminal program or instruction to implement the method according to the third aspect.

In a ninth aspect, there is provided a computer program product 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 first aspect or implementing the steps of the method according to the third aspect.

In the embodiment of the application, when the authentication of the terminal fails, the access and mobile management functional entity determines an authentication failure cause value returned to the terminal according to a first message indicating whether the current network is used for the onboarding of the terminal, and sends the authentication failure cause value to the terminal, so that the network serving as the onboarding can select a corresponding cause value after the authentication of the terminal fails.

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 flowchart illustrating a method for handling authentication failure according to an embodiment of the present application;

fig. 3 is a schematic flowchart illustrating another method for handling authentication failure according to an embodiment of the present application;

fig. 4 is a schematic flowchart illustrating a method for handling authentication failure according to an embodiment of the present application;

fig. 5 is a schematic flowchart illustrating a method for handling authentication failure according to an embodiment of the present application;

fig. 6 is a schematic flowchart illustrating a method for handling authentication failure according to an embodiment of the present application;

fig. 7 is a schematic structural diagram illustrating a device for processing failure of authentication according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a processing apparatus for failure authentication according to an embodiment of the present application;

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

fig. 10 is a schematic diagram illustrating a hardware structure of a terminal according to an embodiment of the present application;

fig. 11 shows a hardware structure diagram of a network-side device according to an 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 technology described in the embodiments of the present application is 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 (OFD), or Frequency Division Multiple Access (ofdm)MA), 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, but the techniques may also be applied to applications other than NR system applications, such as 6 th generation (6 th generation) NR systems^thGeneration, 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, wherein 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 home evolved node B, a WLAN access Point, a WiFi node, a Transmit Receiving Point (TRP), or some other suitable terminology in the field, and the Base Station is not limited to a specific technical vocabulary as long as the same technical effect is achieved.

The core network may include Access and Mobility Management Function (AMF) entities, Session Management Function (SMF) entities, Authentication service Function (AUSF) entities, Digital Certificate Service (DCS) entities, and other functional entities.

The following describes in detail the method for processing authentication failure according to the embodiments of the present application with reference to the accompanying drawings.

Fig. 2 shows a flowchart of a method for processing an authentication failure in the embodiment of the present application, where the method 200 may be performed by a network side device (e.g., an AMF entity of a core network). In other words, the method may be performed by software or hardware installed on the network-side device. As shown in fig. 2, the method may include the following steps.

S210, under the condition that the authentication of the terminal is failed, the AMF entity determines an authentication failure reason value returned to the terminal according to a first message, wherein the first message indicates whether the current network is used for the onboarding of the terminal.

The current network refers to a network to which the terminal is currently accessed.

In this embodiment of the present application, configuring Network access (onboarding) refers to a terminal accessing a current Network to obtain information such as a certificate of a target independent Non-Public Network (SNPN).

In one possible implementation, the information carried in the first message includes but is not limited to: the registration type of the terminal and/or the authentication parameter of the terminal are not limited to this, and in practical applications, the first message may also carry other information, as long as the network side can determine whether the current network is used for the onbroadcasting of the terminal according to the information, which is not limited in the embodiment of the present application.

In one possible implementation, the first message may be sent by the terminal, and therefore, in this possible implementation, before S210, the method may further include: and receiving the first message sent by the terminal.

In the foregoing possible implementation manner, the first message may include: a registration request message, for example, a terminal-initiated registration request message for onkeying. Through the registration request message, the AMF may determine whether the current network is used for the onbroadcasting of the terminal.

In a possible implementation manner, if the first message indicates that the current network is used for the onboarding of the terminal, the authentication failure cause value determined by the AMF may be a newly added cause value, that is, a first target cause value, and the first target cause value is used in the system to indicate that the authentication in the onboarding process of the terminal fails, where the first target cause value may be dedicated to indicate that the authentication in the onboarding process of the terminal fails, the authentication failure in the onboarding process of the terminal may be directly indicated by the first target cause value, and the terminal may determine that the authentication fails when the current network is used as the onboarding network according to the first target cause value, and may identify the current network as a network that is not applicable to the onboarding.

Or, in another possible implementation manner, if the first message indicates that the current network is used for the onboarding of the terminal, the authentication failure cause value determined by the AMF may also be a second target cause value, where the second target cause value is used for indicating an authentication failure of the terminal, that is, the second target cause value is not dedicated to indicate an authentication failure in the onboarding process of the terminal. For example, the second target cause value may be #3, #74 and #75 already existing in the system, but is not limited thereto, and in practical application, the second target cause value may also be other specific values, and the value may be a cause value indicating that the authentication of the terminal is failed in other cases in the system. By adopting the possible implementation mode, the terminal side can determine the reason of authentication failure by combining the registration type.

S220, sending a second message to the terminal, wherein the second message carries the authentication failure reason value.

For example, the AMF may send a registration reject message to the terminal, where the registration reject message carries the authentication failure cause value. Of course, the AMF may also send the authentication failure cause value to the terminal through other messages, which is not limited in this embodiment of the present application.

By the method for processing authentication failure provided by the embodiment of the application, under the condition that the terminal authentication fails, the access and mobile management functional entity determines the authentication failure reason value returned to the terminal according to the first message indicating whether the current network is used for the onboarding of the terminal, and sends the authentication failure reason value to the terminal, so that the network serving as the onboarding can select the corresponding reason value after the terminal authentication fails.

Fig. 3 is a schematic flow chart of another method for handling authentication failure in the embodiment of the present application, where the method 300 may be executed by a terminal. In other words, the method may be performed by software or hardware installed on the terminal. As shown in fig. 3, the method may include the following steps.

S310, the terminal receives a second message, wherein the authentication failure reason value carried in the second message.

The second message is the same as the second message in the method 200, and the authentication failure cause value carried in the second message is the same as that in the method 200, which may be specifically referred to as the description in the method 200.

S320, if it is determined that the authentication failure indicated by the authentication failure cause value is the authentication failure in the onboarding process of the terminal, marking the independent non-public network SNPN currently accessed as the network prohibited from being selected as the onboarding.

In a possible implementation manner, if the authentication failure cause value is the first target cause value in the method 200, the terminal may determine, according to the first target cause value, that the authentication failure indicated by the authentication failure cause value is the authentication failure in the onboarding procedure of the terminal. Therefore, in this possible implementation manner, determining that the authentication failure indicated by the authentication failure cause value is the authentication failure in the onboarding procedure of the terminal includes: and if the authentication failure reason value is a first target reason value, determining that the authentication failure indicated by the authentication failure reason value is the authentication failure in the onboarding process of the terminal, wherein the first target reason value is used for indicating the reason value of the authentication failure in the onboarding process of the terminal.

Alternatively, in another possible implementation manner, if the authentication failure cause value is the second target cause value in the method 200, the terminal may determine, in combination with whether the current registration is for onbinding, that the authentication failure indicated by the authentication failure cause value is the authentication failure of the onbinding procedure of the terminal. Therefore, in this possible implementation manner, determining that the authentication failure indicated by the authentication failure cause value is the authentication failure in the onboarding procedure of the terminal includes: and if the reason value for the authentication failure is a second target reason value and the current registration purpose is determined to be for onboarding, determining that the authentication failure indicated by the reason value for the authentication failure is the authentication failure in the onboarding process of the terminal, wherein the second target reason value is used for indicating the authentication failure of the terminal.

Optionally, the second target cause value may include any one of: 3. 74, 75. That is, the second target cause value may be one of #3, #74, and #75 in the existing system, but of course, the second target cause value is not limited thereto, and the second target cause value may be another cause value in the existing system.

In one possible implementation, if the second target cause value is #3, if the current registration type is not for the onkeying purpose, an entry corresponding to the SNPN of the current service in a subscription information list (list of subscriber data) of the terminal may be set as unavailable. If the second target cause value is #74 or #75, if the current registration type is not for onkeying, the SNPN ID of the current access network may be stored in a temporary forbidden SNPN (temporal forbidden SNPNs) list, where #75 is different from #74 in that if the second target cause value is #74, the stored SNPN ID is a globally unique identification of the SNPN network.

In one possible implementation, marking the currently accessed SNPN as prohibited to be selected as an onbroadcasting network may include: and recording the SNPN identification of the currently accessed SNPN into a target list, wherein the target list is used for recording the SNPN identification of the network which is forbidden to be selected as the onboarding by the terminal. Through the target list, the network which is forbidden to be selected as the onbroadcasting by the terminal can be managed in a unified way.

In a specific application, after it is determined that the authentication failure indicated by the authentication failure cause value is the authentication failure in the onboarding process of the terminal, if the target list currently exists, the SNPN identifier of the currently accessed SNPN is added to the target list, and if the target list does not currently exist, the target list may be created, and the SNPN identifier of the currently accessed SNPN is recorded in the target list.

In one possible implementation manner, after marking the currently accessed SNPN as a network prohibited from being selected as an onboarding, in the case of being set to the automatic network selection mode, the terminal prohibits selecting an SNPN network corresponding to the SNPN identifier recorded in the target list as a network of the onboarding. With this possible implementation, in the case where the terminal is set to the automatic network selection mode, the SNPN network corresponding to the SNPN identifier recorded in the target list is prohibited from being used as the network for the onboarding.

Or, in another possible implementation manner, if the terminal is set to the manual network selection mode, after marking the currently accessed SNPN as a network that is prohibited from being selected as an onboarding, the method may further include: in a case of being set to the manual network selection mode, in response to an input network selection command, a process of one of:

(1) not displaying the SNPN identifications recorded in the target list; for example, if the input network selection command selects a network as an onboarding, the SNPN identities recorded in the target list are not displayed, so that the user does not select the SNPN network recorded in the target list as the onboarding network.

(2) Displaying SNPN identifications recorded in the target list; for example, if the input network selection command selects a network that is not an onboarding, the SNPN identities recorded in the target list may be displayed, so that the user may select the SNPN network recorded in the target list as a network for other purposes than onboarding.

(3) And displaying the SNPN identifications recorded in the target list, and identifying the SNPN identifications recorded in the target list as the identifications of the SNPN networks forbidden to be selected as the onboarding. Through the possible implementation manner, when the SNPN identifications recorded in the target list are displayed, the user is prompted that the SNPN networks corresponding to the SNPN identifications are prohibited to be selected as the enhancing, so that the user does not select the SNPN recorded in the target list when selecting the enhancing network.

By the method for processing authentication failure provided by the embodiment of the application, when the terminal receives the second message carrying the cause value of authentication failure, if the authentication failure indicated by the cause value of authentication failure is determined to be the authentication failure in the onboarding process of the terminal, the current accessed SNPN is marked as the network forbidden to be selected as the onboarding, so that the terminal can not select the current accessed SNPN as the onboarding network any more in the subsequent processes when the onboarding is performed, and the success rate of the onboarding is improved.

Fig. 4 is a flowchart of a method for processing authentication failure according to an embodiment of the present application, where the method 400 may be executed by a terminal and a network side device. In other words, the method may be performed by software or hardware installed on the terminal and the network-side device. The network side device may include: AMF entity, AUSF entity and DCS entity. As shown in fig. 4, the method may include the following steps.

S410, the UE initiates a registration request for onboarding.

S420, the AMF initiates an authentication Request (Nausf _ UEauthentication _ Authenticate Request) to the AUSF.

S430, the AUSF authenticates the UE through the DCS, for example, the UE is authenticated using default credentials.

S440, the authentication result is failure, for example, the DCS does not have the authentication information of the UE, etc.;

s450, the AMF sends a registration reject message to the UE, where the registration reject message includes cause: # X. Wherein X is a cause value dedicated to indicate authentication failure in the onkeying procedure of the terminal, for example, a newly defined authentication failure cause value.

S460, the UE receives the message containing cause: after # X registration reject message, the SNPN ID is stored, and the storing process may be implemented in the form of creating or updating a list of SNPN IDs for storing SNPN IDs prohibited from being selected as onboarding (forbidden SNPN IDs).

S470, the UE selects other O-SNPN to register.

In the automatic network selection mode, according to the stored forbidden routing SNPN IDs information and the SNPN IDs information supporting the routing, the UE selects other available routing networks to register.

In manual network selection mode: for the forbidden associating SNPN IDs, there are several processing methods:

not presented to the user, or

Is presented to the user, or

When presented to a user, the SNPN IDs may be indicated as the forbidden SNPN IDs.

Fig. 5 is a flowchart of a method for processing authentication failure according to an embodiment of the present application, where the method 500 may be executed by a terminal and a network side device. In other words, the method may be performed by software or hardware installed on the terminal and the network-side device. The network side device may include: AMF entity, AUSF entity and DCS entity. As shown in fig. 5, the method may include the following steps.

S510-S540 are the same as S S410-S440 in method 400 and will not be described herein.

S550, sending cause value #3 in registration rejection indicates authentication failure.

S560, when the UE receives the cause value #3, it determines that the current registration type is for associating.

S570, storing the SNPN ID, the storing process may be implemented by creating or updating a form of SNPN IDs list for storing forbidden onkeying SNPN IDs, instead of setting the SNPN ID as unavailable.

In this embodiment, if the purpose of the current registration type is for initial registration or the like (i.e. the registration request is not for onkeying), in one embodiment, the entry of "list of subscriber data" corresponding to the current SNPN is set as unavailable, that is, the entry corresponding to the current service SNPN in the subscription information list of the terminal is set as unavailable, that is, the SNPN ID is set as unavailable.

S580 is the same as S470, and is not described herein again.

Fig. 6 is a flowchart of a method for processing authentication failure according to an embodiment of the present application, where the method 600 may be executed by a terminal and a network side device. In other words, the method may be performed by software or hardware installed on the terminal and the network-side device. The network side device may include: AMF entity, AUSF entity and DCS entity. As shown in fig. 6, the method may include the following steps.

S610-S640 are the same as S S410-S440 in method 400, and are not described in detail here.

S650, sending cause value #74 or #75 in registration reject indicates authentication failure.

If the onkeying SNPN which the UE attempts to access currently has the globally unique SNPN identification, if the authentication fails, the AMF sends cause value #75 to the UE, otherwise, the AMF sends cause value #74 to the UE.

S660, when the UE receives cause value #74 or 75, it is determined that the current registration type is for associating.

S670, storing the SNPN ID, wherein the storing process can be realized by creating or updating a form of SNPN IDs list for storing forbidden onkeying SNPN IDs, instead of setting the SNPN ID as unavailable.

In this embodiment, if the current registration type is not for purposes of onkeying or the like (i.e., the registration request is not for onkeying), then in one embodiment, the SNPN ID is stored in a temporary forbidden SNPN networks (temporary forbidden SNPNs) list.

S680 is the same as S470, and is not described herein again.

It should be noted that, in the processing method for failure authentication provided in the embodiment of the present application, the execution main body may be a processing device for failure authentication, or a control module for executing the processing method for failure authentication in the processing device for failure authentication. In the embodiment of the present application, a processing method for performing authentication failure by a processing device that fails authentication is taken as an example to describe the processing device that fails authentication provided in the embodiment of the present application.

Fig. 7 is a schematic structural diagram of a processing device for authentication failure according to an embodiment of the present application, and as shown in fig. 3, the processing device for authentication failure mainly includes: a determination module 701 and a first transceiver module 702.

In this embodiment of the present application, the determining module 701 is configured to determine, according to a first message, an authentication failure cause value returned to a terminal when authentication of the terminal fails, where the first message indicates whether a current network is used for configuring network entry barring of the terminal; a first transceiver module 702, configured to send a second message to the terminal, where the second message carries the authentication failure cause value.

In a possible implementation manner, the first message carries a registration type of the terminal and/or an authentication parameter of the terminal.

In a possible implementation manner, the determining module 701 determines, according to the first message, an authentication failure cause value returned to the terminal, including: and if the first message indicates that the current network is used for the onboarding of the terminal, determining that the authentication failure reason value is a first target reason value, wherein the first target reason value is used for indicating authentication failure in the onboarding process of the terminal.

In a possible implementation manner, the determining module 701 determines, according to the first message, an authentication failure cause value returned to the terminal, including: and if the first message indicates that the current network is used for the onkeying of the terminal, determining that the authentication failure reason value is a second target reason value, wherein the second target reason value is used for indicating the authentication failure of the terminal.

In a possible implementation manner, the first transceiver module 702 is further configured to receive the first message sent by the terminal before determining, according to the first message, an authentication failure cause value returned to the terminal.

With the processing apparatus for authentication failure provided in this embodiment of the present application, when the terminal is unsuccessfully authenticated, the determining module 701 determines an authentication failure cause value returned to the terminal according to a first message indicating whether a current network is used for onboarding of the terminal, and the first transceiver module 702 sends the authentication failure cause value to the terminal, so that the network serving as onboarding may select a corresponding cause value after the terminal is unsuccessfully authenticated.

The processing device for authentication failure in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a network side device. The apparatus may be a network side device. For example, the network-side device may include, but is not limited to, the AMF entity described above, and the embodiment of the present application is not particularly limited.

The network side device in the embodiment of the present application may be an apparatus 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 network side device provided in the embodiment of the present application can implement each process implemented by the network side device in each method embodiment of fig. 2 to fig. 6, and achieve the same technical effect, and for avoiding repetition, details are not repeated here.

Fig. 8 is another schematic structural diagram of a processing device failing to authenticate according to an embodiment of the present application, and as shown in fig. 8, the processing device failing to authenticate may include: a second transceiver module 801 and a processing module 802.

In this embodiment of the present application, the second transceiver module 801 is configured to receive a second message, where the authentication failure cause value is carried in the second message; a processing module 802, configured to mark the currently accessed SNPN as a network prohibited from being selected as an authentication if it is determined that the authentication failure indicated by the authentication failure cause value is the authentication failure in the onboarding process of the terminal.

In a possible implementation manner, the determining, by the processing module 802, that the authentication failure indicated by the authentication failure cause value is the authentication failure in the onboarding procedure of the terminal includes: and if the authentication failure reason value is a first target reason value, determining that the authentication failure indicated by the authentication failure reason value is the authentication failure in the onboarding process of the terminal, wherein the first target reason value is used for indicating the reason value of the authentication failure in the onboarding process of the terminal.

In a possible implementation manner, the determining, by the processing module 802, that the authentication failure indicated by the authentication failure cause value is the authentication failure in the onboarding procedure of the terminal includes:

and if the reason value for the authentication failure is a second target reason value and the current registration purpose is determined to be for onboarding, determining that the authentication failure indicated by the reason value for the authentication failure is the authentication failure in the onboarding process of the terminal, wherein the second target reason value is used for indicating the authentication failure of the terminal.

In one possible implementation manner, the processing module 802 marks the independent non-public network SNPN currently accessed as a network prohibited from being selected as an enhancing, including: and recording the SNPN identification of the current accessed SNPN into a target list, wherein the target list is used for recording the SNPN identification of the network which is forbidden to be selected as the onboarding by the terminal.

In a possible implementation manner, the processing module 802 is further configured to, after marking the currently accessed independent non-public network SNPN as a network prohibited from being selected as an onboarding, prohibit selecting, in a case of being set to the automatic network selection mode, an SNPN network corresponding to the SNPN identifier recorded in the target list as a network of the onboarding.

In a possible implementation manner, the processing module 802 is further configured to, after marking the currently accessed independent non-public network SNPN as a network prohibited from being selected as an onboarding, in response to an input network selection command, perform, in a case of being set to a manual network selection mode, processing of one of the following:

not displaying the SNPN identifications recorded in the target list;

displaying SNPN identifications recorded in the target list;

and displaying the SNPN identifications recorded in the target list, and identifying the SNPN identifications recorded in the target list as the identifications of the SNPN networks forbidden to be selected as the onboarding.

The processing device for authentication failure in the embodiment 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 processing device that fails in authentication 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 processing device for authentication failure provided in the embodiment of the present application can implement each process implemented by the terminal in the embodiments of the methods in fig. 2 to fig. 6, and achieve the same technical effect, and is not described here again to avoid repetition.

Optionally, as shown in fig. 9, an embodiment of the present application further provides a communication device 900, which includes a processor 901, a memory 902, and a program or an instruction stored in the memory 902 and executable on the processor 901, for example, when the communication device 900 is a terminal, the program or the instruction is executed by the processor 901 to implement the processes of the processing method embodiment of the authentication failure, and the same technical effect can be achieved. When the communication device 900 is a network-side device, the program or the instruction is executed by the processor 901 to implement each process implemented by the AMF or the network-side device in the processing method embodiment of the authentication failure, and the same technical effect can be achieved, and in order to avoid repetition, details are not described here again. When the communication device 900 is a terminal, the program or the instruction is executed by the processor 901 to implement each process implemented by the terminal in the processing method embodiment of the authentication failure, and the same technical effect can be achieved, and in order to avoid repetition, the description is omitted here.

Fig. 10 is a schematic hardware structure diagram of a terminal implementing the embodiment of the present application.

The terminal 1000 includes, but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009, and a processor 1010.

Those skilled in the art will appreciate that terminal 1000 can also include a power supply (e.g., a battery) for powering the various components, which can be logically coupled to processor 1010 via a power management system to provide management of charging, discharging, and power consumption via the power management system. The terminal structure shown in fig. 10 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 1004 may include a Graphics Processing Unit (GPU) 10041 and a microphone 10042, and the Graphics Processing Unit 10041 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 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and other input devices 10072. The touch panel 10071 is also referred to as a touch screen. The touch panel 10071 may include two parts, a touch detection device and a touch controller. Other input devices 10072 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 this embodiment of the application, the radio frequency unit 1001 receives downlink data from a network side device and then processes the downlink data to the processor 1010; in addition, the uplink data is sent to the network side equipment. In general, radio frequency unit 1001 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 1009 may be used to store software programs or instructions and various data. The memory 1009 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, and the like) required for at least one function, and the like. Further, the Memory 1009 may include a high-speed random access Memory and may also include a nonvolatile Memory, where the nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable Programmable PROM (EPROM), an Electrically Erasable Programmable ROM (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 1010 may include one or more processing units; alternatively, processor 1010 may integrate an application processor that handles primarily the operating system, user interface, and application programs or instructions, and a modem processor that handles primarily wireless communications, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into processor 1010.

The radio frequency unit 1001 is configured to receive a second message, where the authentication failure cause value is carried in the second message.

A processor 1010, configured to mark the currently accessed independent non-public network SNPN as a network prohibited from being selected as an authentication if it is determined that the authentication failure indicated by the authentication failure cause value is the authentication failure in the onboarding procedure of the terminal.

Specifically, the embodiment of the application further provides a network side device. As shown in fig. 11, the network device 1100 includes: antenna 1101, radio frequency device 1102, baseband device 1103. An antenna 1101 is connected to the radio frequency device 1102. In the uplink direction, the rf device 1102 receives information via the antenna 1101, and sends the received information to the baseband device 1103 for processing. In the downlink direction, the baseband device 1103 processes information to be transmitted and transmits the processed information to the rf device 1102, and the rf device 1102 processes the received information and transmits the processed information through the antenna 1101.

The above-mentioned band processing means may be located in the baseband apparatus 1103, and the method performed by the network side device in the above embodiment may be implemented in the baseband apparatus 1103, where the baseband apparatus 1103 includes a processor 1104 and a memory 1105.

The baseband apparatus 1103 may include at least one baseband board, for example, and a plurality of chips are disposed on the baseband board, as shown in fig. 11, where one chip, for example, the processor 1104, is connected to the memory 1105 and calls the program in the memory 1105 to perform the network device operations shown in the above method embodiments.

The baseband apparatus 1103 may further include a network interface 1106, such as a Common Public Radio Interface (CPRI), for exchanging information with the rf apparatus 1102.

Specifically, the network side device of the embodiment of the present invention further includes: the instructions or programs stored in the memory 1105 and capable of being executed on the processor 1104, and the processor 1104 invokes the instructions or programs in the memory 1105 to execute the methods executed by the modules shown in fig. 8, so as to achieve the same technical effects, and are not described herein in detail in order to avoid repetition.

The embodiment of the present application further provides 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 program or the instruction implements each process of the embodiment of the processing method for authentication failure, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

The processor may be the processor in the terminal described in the above embodiment, or the processor in the network side device 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 program or an instruction of a network-side device or a terminal, so as to implement each process of the above-mentioned processing method embodiment for an authentication failure, and achieve the same technical effect, and in order to avoid repetition, the details are not repeated here.

The embodiment of the present application further provides a computer program product, where the computer program product includes a processor, a memory, and a program or an instruction stored in the memory and executable on the processor, and when the program or the instruction is executed by the processor, the process of the embodiment of the processing method for authentication failure is implemented, and the same technical effect can be achieved, and in order to avoid repetition, 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 apparatus of 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 involved, e.g., the methods described may be performed in an order different than 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 may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to 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 method for handling authentication failure, the method comprising:

under the condition that the authentication of the terminal is failed, an access and mobile management functional entity determines an authentication failure reason value returned to the terminal according to a first message, wherein the first message indicates whether the current network is used for configuring network access establishment of the terminal;

and sending a second message to the terminal, wherein the second message carries the authentication failure reason value.

2. The method according to claim 1, wherein the first message carries a registration type of the terminal and/or an authentication parameter of the terminal.

3. The method of claim 1, wherein the determining, by the access and mobility management function entity, the authentication failure cause value returned to the terminal according to the first message comprises:

and if the first message indicates that the current network is used for the onboarding of the terminal, determining that the authentication failure reason value is a first target reason value, wherein the first target reason value is used for indicating authentication failure in the onboarding process of the terminal.

4. The method of claim 1, wherein the determining, by the access and mobility management function entity, the authentication failure cause value returned to the terminal according to the first message comprises:

and if the first message indicates that the current network is used for the onkeying of the terminal, determining that the authentication failure reason value is a second target reason value, wherein the second target reason value is used for indicating the authentication failure of the terminal.

5. The method of claim 4, wherein the second target cause value comprises any one of: 3. 74, 75.

6. The method according to any of claims 1 to 5, wherein before the access and mobility management functional entity determines the authentication failure cause value returned to the terminal according to the first message, the method further comprises:

and receiving the first message sent by the terminal.

7. The method of claim 6, wherein the first message comprises: a registration request message.

8. A method for handling authentication failure, the method comprising:

the terminal receives a second message, wherein the authentication failure reason value carried in the second message;

and if the authentication failure indicated by the authentication failure reason value is determined to be the authentication failure of the onboarding process of the terminal, marking the currently accessed independent non-public network SNPN as the network forbidden to be selected as the onboarding.

9. The method according to claim 8, wherein determining that the authentication failure indicated by the authentication failure cause value is the authentication failure of the onboarding procedure of the terminal comprises:

and if the authentication failure reason value is a first target reason value, determining that the authentication failure indicated by the authentication failure reason value is the authentication failure in the onboarding process of the terminal, wherein the first target reason value is used for indicating the reason value of the authentication failure in the onboarding process of the terminal.

10. The method according to claim 8, wherein determining that the authentication failure indicated by the authentication failure cause value is the authentication failure of the onboarding procedure of the terminal comprises:

11. The method of claim 10, wherein the second target cause value comprises any one of: 3. 74, 75.

12. Method according to any of claims 8 to 11, wherein marking the currently accessed independent non-public network SNPN as a network prohibited from being selected as an onboarding comprises:

and recording the SNPN identification of the current accessed SNPN into a target list, wherein the target list is used for recording the SNPN identification of the network which is forbidden to be selected as the onboarding by the terminal.

13. The method according to claim 12, characterized in that after marking the currently accessed independent non-public network SNPN as a network forbidden to be selected as an onboarding, the method further comprises:

and under the condition of being set to an automatic network selection mode, the terminal forbids to select an SNPN network corresponding to the SNPN identifier recorded in the target list as an onboarding network.

14. The method according to claim 12, characterized in that after marking the currently accessed independent non-public network SNPN as a network forbidden to be selected as an onboarding, the method further comprises:

in a case of being set to the manual network selection mode, in response to an input network selection command, a process of one of:

not displaying the SNPN identifications recorded in the target list;

displaying SNPN identifications recorded in the target list;

15. An apparatus for handling authentication failure, the apparatus comprising:

a determining module, configured to determine, according to a first message, an authentication failure cause value returned to a terminal when authentication of the terminal fails, where the first message indicates whether a current network is used for onboarding of the terminal;

and the first transceiver module is configured to send a second message to the terminal, where the second message carries the authentication failure cause value.

16. The apparatus of claim 15, wherein the first message carries a registration type of the terminal and/or an authentication parameter of the terminal.

17. The apparatus of claim 15, wherein the determining module determines the value of the cause of authentication failure returned to the terminal according to the first message, comprising:

18. The apparatus of claim 15, wherein the determining module determines the value of the cause of authentication failure returned to the terminal according to the first message, comprising:

19. The apparatus according to any one of claims 15 to 18, wherein the first transceiver module is further configured to receive the first message sent by the terminal before determining an authentication failure cause value returned to the terminal according to the first message.

20. An apparatus for handling authentication failure, the apparatus comprising:

the second transceiver module is configured to receive a second message, where the authentication failure cause value is carried in the second message;

and the processing module is used for marking the independent non-public network SNPN accessed currently as the network forbidden to be selected as the onboarding if the authentication failure indicated by the authentication failure reason value is determined to be the authentication failure in the onboarding process of the terminal.

21. The apparatus of claim 20, wherein the processing module determines that the authentication failure indicated by the authentication failure cause value is authentication failure of an onboarding procedure of the terminal, and comprises:

22. The apparatus of claim 20, wherein the processing module determines that the authentication failure indicated by the authentication failure cause value is authentication failure of an onboarding procedure of the terminal, and comprises:

23. The apparatus according to any of the claims 20 to 22, wherein the processing module marks the currently accessed independent non-public network SNPN as a network prohibited from being selected as an onboarding, comprising:

24. The apparatus of claim 23, wherein the processing module is further configured to, after marking the currently accessed independent non-public network SNPN as a network prohibited from being selected as an onboarding, prohibit the SNPN network corresponding to the SNPN identifier recorded in the target list from being selected as a network of the onboarding when the mode is set to the automatic network selection mode.

25. The apparatus of claim 23, wherein the processing module is further configured to, after marking the currently accessed independent non-public network SNPN as a network prohibited from being selected as an onkeying, perform, in response to an input network selection command, one of the following processes in a case of being set to a manual network selection mode:

not displaying the SNPN identifications recorded in the target list;

displaying SNPN identifications recorded in the target list;

26. A network-side device, comprising 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 for handling authentication failure according to any one of claims 1 to 7.

27. 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 method of handling authentication failure according to any one of claims 8 to 14.

28. A readable storage medium, characterized in that a program or instructions are stored thereon, which when executed by the processor implement the method of processing an authentication failure according to any one of claims 1 to 7, or the steps of the method of processing an authentication failure according to any one of claims 8 to 14.