WO2022057429A1 - 网络注册方法、装置、用户终端及存储介质 - Google Patents
网络注册方法、装置、用户终端及存储介质 Download PDFInfo
- Publication number
- WO2022057429A1 WO2022057429A1 PCT/CN2021/107031 CN2021107031W WO2022057429A1 WO 2022057429 A1 WO2022057429 A1 WO 2022057429A1 CN 2021107031 W CN2021107031 W CN 2021107031W WO 2022057429 A1 WO2022057429 A1 WO 2022057429A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network
- user terminal
- request
- registration
- request identifier
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 70
- 230000004044 response Effects 0.000 claims abstract description 99
- 230000002159 abnormal effect Effects 0.000 claims abstract description 30
- 230000001960 triggered effect Effects 0.000 claims abstract description 18
- 238000004590 computer program Methods 0.000 claims description 35
- 238000004891 communication Methods 0.000 abstract description 6
- 238000010586 diagram Methods 0.000 description 16
- 230000000694 effects Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 4
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
Definitions
- the present application relates to a network registration method, device, user terminal and storage medium.
- a user terminal when a user terminal performs network registration, the user terminal sends a network registration request carrying an Access Point Name (APN) identifier set by the user to the network side, and the network side device passes the verification of the APN.
- APN Access Point Name
- Network registration In a 5G network, the user terminal sends a network registration request carrying the data network name (DNN) identifier set by the user to the network side, and the network side device performs network registration after verifying the DNN.
- DNN data network name
- a first aspect of the present application provides a network registration method, the method comprising:
- the registered network type query the corresponding relationship between the preset network type and the request identifier, if the second request identifier corresponding to the network type registered by the user terminal is found, send the second network carrying the second request identifier to the network device. Registration request.
- a second aspect of the present application provides another network registration method, the method comprising:
- a third aspect of the present application provides a network registration device, the network registration device is configured in a user terminal, and the network registration device includes:
- a first sending module configured to send a first network registration request carrying a first request identifier to the network device
- a first receiving module configured to receive a first registration rejection response fed back by the network device; the first registration rejection response is a response triggered when the network device determines that the first request identifier is abnormal;
- the query module is configured to query the corresponding relationship between the preset network type and the request identifier according to the network type registered by the user terminal, and if the second request identifier corresponding to the network type registered by the user terminal is found, send a data carrying The second network registration request identified by the second request.
- a fourth aspect of the present application provides a network registration device, the network registration device is configured in a network device, and the network registration device includes:
- a first receiving module configured to receive a first network registration request carrying a first request identifier sent by a user terminal
- a sending module configured to send a first registration refusal response to the user terminal if it is determined that the first request identifier is abnormal
- the second receiving module is configured to receive a second network registration request carrying a second request identifier sent by the user terminal; the second request identifier is that the user terminal searches for the relationship between the preset network type and the request identifier according to the network type registered by the user terminal The corresponding relationship is obtained, and the request identifier corresponding to the network type registered by the user terminal is obtained.
- a fifth aspect of the present application provides a computer device, comprising a memory and a processor, the memory stores a computer program, and when the computer program is executed by the processor, any of the above-mentioned first and second aspects is implemented.
- a sixth aspect of the present application provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, implements the network registration according to any one of the first and second aspects above method.
- FIG. 1 is a diagram of an application environment involved in an embodiment of the present application.
- FIG. 2 is a flowchart of a network registration method involved in an embodiment of the present application.
- FIG. 3 is a flowchart of a network registration method involved in an embodiment of the present application.
- FIG. 4 is a flowchart of a method for determining a second request identifier involved in an embodiment of the present application.
- FIG. 5 is a flowchart of determining a correspondence between a registered network type and a request identifier involved in an embodiment of the present application.
- FIG. 6 is a flowchart of a network registration method involved in an embodiment of the present application.
- FIG. 7 is a flowchart of a method for sending a third network registration request according to an embodiment of the application.
- FIG. 8 is a flowchart of a network registration method involved in an embodiment of the present application.
- FIG. 9 is a flowchart of a network registration method involved in an embodiment of the present application.
- FIG. 10 is a block diagram of a network registration apparatus involved in an embodiment of the application.
- FIG. 11 is a block diagram of a network registration apparatus involved in an embodiment of the application.
- FIG. 12 is a block diagram of a network registration apparatus involved in an embodiment of the application.
- FIG. 13 is a block diagram of a network registration apparatus involved in an embodiment of the application.
- FIG. 14 is a block diagram of a network registration apparatus involved in an embodiment of the application.
- FIG. 15 is a block diagram of a network registration apparatus involved in an embodiment of the application.
- FIG. 16 is a block diagram of a network registration apparatus involved in an embodiment of the application.
- FIG. 17 is a block diagram of a user terminal involved in an embodiment of the application.
- FIG. 18 is a block diagram of a network device involved in an embodiment of the application.
- the network registration method provided by this application can be applied to the application environment shown in FIG. 1 .
- the user terminal 102 communicates with the network device 104 through the base station.
- the user terminal 102 may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices.
- a network registration method is provided, and the method is applied to the user terminal in FIG. 1 as an example for description, including the following steps:
- Step 201 Send a first network registration request carrying a first request identifier to a network device.
- the user terminal when it performs network registration, it needs to first send a first network registration request to the network device.
- the first network registration request carries the first request identifier.
- the first request identifier is an identifier carried in the first network registration request when the user terminal performs network registration.
- the first request identifier carried in the first network registration request is an APN identifier.
- the APN identifier may be manually set by the user, or the user terminal may acquire the APN identifier preset in the user terminal.
- the first request identifier carried in the first network registration request is the DNN identifier.
- the DNN identifier may be manually set by the user, or the user terminal may acquire the DNN identifier preset in the user terminal.
- Step 202 Receive a first registration rejection response fed back by the network device; the first registration rejection response is a response triggered when the network device determines that the first request identifier is abnormal.
- the user terminal When the first request identifier is abnormal, the user terminal will receive a first registration rejection response fed back by the network device, and the first registration rejection response is a response triggered when the network device determines that the first request identifier is abnormal.
- the user terminal When the user terminal performs network registration, it sends a first network registration request carrying the first request identifier to the network device, and the server determines that the APN identifier or DNN identifier in the first network registration request is wrong, and feeds back the first network registration request to the user terminal. Once the registration is rejected, the user terminal is notified that the current network registration has failed. Similarly, when the user terminal obtains the APN identifier or DNN identifier preset in the user terminal, the APN identifier or DNN identifier preset in the user terminal may also be wrong, and the user terminal will also receive the network The first denial of registration response returned by the device.
- Step 203 Query the correspondence between the preset network type and the request identifier according to the network type registered by the user terminal, and if the second request identifier corresponding to the network type registered by the user terminal is found, send a message carrying the second request identifier to the network device.
- the network type is the network that the user terminal currently needs to register with.
- the user terminal When the user terminal receives the first registration rejection response fed back by the network device, the user terminal queries the corresponding relationship between the preset network type and the request identifier according to the network type, where the preset network type includes The network type commonly used in practical applications, the preset network type may include the network type registered by the user terminal, and the preset network type and the request identifier may be in a one-to-one correspondence. If the request identifier corresponding to the network type registered by the user terminal is found, the request identifier is used as the second request identifier, and the user terminal re-sends the second network registration request carrying the second request identifier to the network device.
- the user terminal sends a first network registration request carrying the first request identifier to the network device, and after receiving the first registration refusal response fed back by the network device, queries the preset network type and the request identifier according to the network type registered by the user terminal. If the second request identifier corresponding to the network type registered by the user terminal is found, a second network registration request carrying the second request identifier is sent to the network device. That is, after the first network registration request is rejected, the user terminal can also send the second network registration request to the network device, and the second request identifier carried in the second network registration request is preset, and is set in the user terminal.
- the predetermined first request identifier is wrong, the situation that the network cannot be used directly will not occur, and the user terminal may try to perform network registration for many times, thereby improving the success rate of the user terminal performing network registration.
- a network registration method is provided, and the method is applied to the user terminal in FIG. 1 as an example for description, including the following steps:
- Step 301 Parse the first registration rejection response to obtain the first rejection reason.
- the first refusal response includes a first refusal reason, that is, the first refusal reason is packaged in the first refusal response that the user terminal receives feedback from the network device, and the first refusal reason may include an abnormal first request
- the parameter information of the identifier after the user terminal parses the first registration rejection response, it can obtain the first rejection reason. For example, the user terminal can decompress the first registration rejection response according to the Modem 4G protocol stack or the Modem 5G protocol stack. After the data processing operation, the first rejection reason is obtained.
- the first rejection reason is an abnormal cause of the first request identifier, and the first rejection reason may be that the first request identifier parameter is missing, or the first request identifier parameter cannot be identified.
- Step 302 Determine whether the first rejection reason is consistent with the preset triggering reason.
- the preset trigger reason is preset in the rejection reason list, and the first rejection reason may be included in the preset trigger reason, and the preset trigger reason may be the loss of the first request identification parameter, the failure of the first request identification parameter identification, or the first request identification is not supported.
- the preset trigger reason for which the first request identification parameter is lost or the first request identification parameter cannot be identified is code 27 (Missing or unknown APN).
- the default trigger reason for is code 91 (DNN not supported with no slice or in specific slice).
- Step 303 If the first rejection reason is consistent with the preset triggering reason, then execute according to the corresponding relationship between the network type registered by the user terminal, the preset network type and the request identifier to determine the second corresponding to the network type registered by the user terminal. Steps to request identification.
- FIG. 4 shows a flowchart of determining the second request identifier corresponding to the network type registered by the user terminal provided by the embodiment of the present application. This method can be applied in the user terminal. As shown in Figure 4, the method for determining the second request identifier corresponding to the network type registered by the user terminal may include the following steps:
- Step 401 If the first rejection reason is consistent with the preset triggering reason, acquire the switch status of the request identifier.
- the request identifier switch state is used by the user terminal to determine whether the request identifier can be obtained, and the request identifier switch state may include the request identifier switch ON state and the request identifier switch OFF state.
- the request identification switch may be preset in the user terminal, and the user may also control the state of the request identification switch by clicking the trigger button.
- the first rejection reason is consistent with the preset triggering reason, that is, in the 4G network, the first rejection reason is code 27 (Missing or unknown APN), and in the 5G network, the first rejection reason is code 91 ( DNN not supported with no slice or in specific slice), you need to get the request ID switch status.
- Step 402 If the state of the request identifier switch is ON, execute the step of determining the second request identifier corresponding to the network type registered by the user terminal according to the corresponding relationship between the network type registered by the user terminal, the preset network type and the request identifier. .
- the request identifier switch state is an on state, that is, the user terminal can acquire the request identifier.
- the user terminal can detect the switch state of the request identifier, and when it is detected that the switch state of the request identifier is on, an acquisition operation of the user terminal is triggered to acquire the switch state of the request identifier.
- the user terminal determines that the first rejection reason is consistent with the preset triggering cause, it obtains the request identifier switch state, and in the case that the request identifier switch state is the ON state, the user terminal is registered according to the network type, the preset network type and the request identifier. In this way, the user terminal will continue to try to determine the second request corresponding to the network type registered by the user terminal when the switch state of the request identifier is turned off. Therefore, the time for determining the second request identifier corresponding to the network type registered by the user terminal is saved, thereby improving the efficiency of network registration by the user terminal.
- the user can control the switch state of the request identifier by clicking the trigger button, that is, the user can control whether the user terminal can use the second request identifier corresponding to the network type registered by the user terminal, that is, the user can flexibly choose whether to use the first request identifier or not.
- the network registration request fails, the network registration continues, which can meet the requirements of different users and adapt to more scenarios.
- the user terminal obtains the first rejection reason by parsing the first rejection registration response, and judges the first rejection reason and the preset trigger reason.
- the corresponding relationship between the type, the preset network type and the request identifier is used to determine the second request identifier corresponding to the network type registered by the user terminal.
- the type of the first rejection reason can be quickly and accurately located, so that the second network registration request can be sent to the network device in time, which saves the time for the user terminal to perform network registration, thereby improving the efficiency of network registration.
- the situation that the network cannot be used directly will not occur.
- the user terminal After the user terminal obtains the first rejection reason by analyzing the first registration rejection response, the user terminal will query according to the network type registered by the user terminal. According to the preset correspondence between the network type and the request identifier, a second network registration request carrying the second request identifier is sent to the network device.
- the user terminal can also send the second network registration request carrying the second request identifier to the network device, and the second request identifier carried in the second network registration request is preset. Therefore, when the first request identifier set by the user terminal is incorrect, the network will not be directly unavailable, and the user terminal may attempt to perform network registration for many times, thereby improving the success rate of the user terminal for network registration.
- FIG. 5 shows a method for determining the correspondence between the registered network type and the request identifier provided by an embodiment of the present application. Flow chart, the method can be applied in a user terminal. As shown in Figure 5, the method for determining the correspondence between the registered network type and the request identifier may include the following steps:
- Step 501 Obtain the operator type corresponding to the SIM card of the user terminal.
- each SIM card corresponds to an operator type, for example, the operator type corresponding to SIM card 1 is A, the operator type corresponding to SIM card 2 is B, and the operator type corresponding to SIM card 3 is C.
- the SIM card currently used by the user terminal is SIM card 1, then the operator type obtained by the user terminal is A
- Step 502 Determine the network type registered by the user terminal according to the operator type, and establish a correspondence between the network type registered by the user terminal and the request identifier.
- the network type registered by the user terminal may be determined according to the operator type, and the network type registered by the user terminal may be one of the public land mobile network (Public Land Mobile Network, PLMN) types.
- PLMN Public Land Mobile Network
- the PLMN corresponding to operator type A is D
- the PLMN corresponding to operator type B is E
- the PLMN corresponding to operator type C is F. If the operator type of the user terminal is A, then the network type PLMN registered by the user terminal is D.
- the request identifier corresponding to the network type D registered by the user terminal is D_NET
- the request identifier corresponding to the network type E registered by the user terminal is E_NET
- the request identifier corresponding to the registered network type F is F_NET.
- the registration may be unsuccessful, that is, the second registration rejection response sent by the network device may also be received.
- the network registration method may include the following steps:
- Step 601 Receive a second registration rejection response sent by the network device; the second registration rejection response is a response triggered when the network device determines that the second request identifier is abnormal.
- the second network registration request carries a second request identifier, and when the second request identifier is abnormal, the user terminal will receive a second registration rejection response fed back by the network device, and the second registration rejection response is that the network device determines the second request Response triggered when an exception is identified.
- the second request identifier is a request identifier corresponding to the network type preset by the user terminal.
- the user terminal After acquiring the second request identifier preset on the user terminal, the user terminal sends the second network device carrying the second request identifier to the network device. Registration request.
- the second request identifier preset in the user terminal is also wrong, or the correspondence between the network type and the second request identifier preset by the user terminal is wrong.
- the abnormal second request identifier is carried in the network registration request, and the user terminal will also receive the second registration rejection response fed back by the network device, that is, the network registration fails.
- Step 602 Send a third network registration request to the network device; the request identifier in the third network registration request is empty.
- the third network registration request is a request carrying an empty request identifier
- the empty request identifier may be that the parameters of the request identifier are all set to 0, and may also be set to NULL APN or NULL DNN.
- the user terminal receives the second registration rejection response fed back by the network device, the user terminal continues to send a third network registration request carrying a null request identifier to the network device.
- the network device can receive the third network registration request carrying the empty request identifier according to the characteristics of the network protocol, and feed back a default request identifier to the network device, that is, the network registration is successful.
- the user terminal When the second request identifier is abnormal, after receiving the second registration refusal response sent by the network device, the user terminal will continue to send a third network registration request carrying an empty request identifier to the network device, and perform network registration again. An opportunity for a network registration is increased, thereby also improving the success rate of the user terminal performing network registration.
- FIG. 7 shows a flowchart of sending a third network registration request to the network device provided by an embodiment of the present application.
- the method It can be applied to the user terminal.
- the method for sending a third network registration request to a network device may include the following steps:
- Step 701 Parse the second registration rejection response to obtain a second rejection reason.
- the second registration rejection response includes a second rejection reason, and the specific process of parsing the second registration rejection response and obtaining the second rejection reason is similar to step 301, and will not be repeated here.
- Step 702 Determine whether the second rejection reason is consistent with the preset triggering reason.
- step 302 The process of judging whether the second rejection reason is consistent with the preset triggering reason is similar to step 302, and details are not repeated here.
- Step 703 If the second rejection reason is consistent with the preset triggering reason, send a third network registration request to the network device.
- the user terminal obtains the second rejection reason by parsing the second rejection registration response, judges the second rejection reason and the preset trigger reason, and sends a third rejection reason to the network device if the second rejection reason is consistent with the preset trigger reason.
- Network registration request In this way, the second rejection reason type can be quickly and accurately located, so that the third network registration request can be sent to the network device in time, which saves the time for the user terminal to perform network registration, thereby improving the efficiency of network registration.
- a network registration method is provided, and the method is applied to the network device in FIG. 8 as an example for description, including the following steps:
- Step 801 Receive a first network registration request that carries a first request identifier and is sent by a user terminal.
- the user terminal when it performs network registration, it needs to first send a first network registration request to the network device, and the network device will receive the first network registration request carrying the first request identifier sent by the user terminal.
- Step 802 If it is determined that the first request identifier is abnormal, send a first registration rejection response to the user terminal.
- the first network registration request carries a first request identifier, and when the first request identifier is abnormal, the network device will feed back a first registration rejection response to the user terminal, and the first registration rejection response is that the network device determines that the first request identifier is abnormal The response triggered when .
- Step 803 Receive a second network registration request carrying a second request identifier sent by the user terminal; the second request identifier is that the user terminal searches for the correspondence between the preset network type and the request identifier according to the network type registered by the user terminal, Obtain the request identifier corresponding to the network type registered by the user terminal.
- the user terminal after sending the first network registration request carrying the first request identifier to the network device, if receiving the first registration rejection response fed back by the network device, queries the preset network type according to the network type registered by the user terminal The corresponding relationship between the request identifier and the network type registered by the user terminal is found, and the second network registration request carrying the second request identifier is sent to the network device, and the network device will receive the request sent by the user terminal.
- a second network registration request carrying the second request identifier carrying the second request identifier.
- the user terminal can also send the second network registration request to the network device, and the second request identifier carried in the second network registration request is preset, and is set in the user terminal.
- the predetermined first request identifier is wrong, the situation that the network is directly unavailable will not occur, and the user terminal is given more chances to perform network registration, thereby improving the success rate of the user terminal performing network registration.
- an embodiment of the present application further provides a network registration method, and the method includes the following steps:
- Step 901 The user terminal sends a first network registration request carrying a first request identifier to a network device.
- Step 902 the network device feeds back a first registration rejection response.
- Step 903 The user terminal receives a first registration rejection response fed back by the network device.
- Step 904 The user terminal parses the first registration rejection response to obtain the first rejection reason.
- Step 905 The user terminal determines whether the first rejection reason is consistent with the preset triggering reason.
- Step 906 If the first rejection reason is consistent with the preset triggering reason, the user terminal acquires the request identifier switch state.
- Step 907 The user terminal acquires the operator type corresponding to the SIM card of the user terminal.
- Step 908 The user terminal determines the network type registered by the user terminal according to the operator type, and establishes a correspondence between the network type registered by the user terminal and the request identifier.
- Step 909 If the state of the request identifier switch is ON, the user terminal executes to determine the second request identifier corresponding to the network type registered by the user terminal according to the corresponding relationship between the network type registered by the user terminal, the preset network type and the request identifier. A step of.
- Step 910 The user terminal sends a second network registration request carrying the second request identifier to the network device.
- Step 911 the network device feeds back a second registration rejection response.
- Step 912 The user terminal receives a second registration rejection response fed back by the network device.
- Step 913 The user terminal parses the second registration rejection response to obtain the second rejection reason.
- Step 914 The user terminal determines whether the second rejection reason is consistent with the preset triggering reason.
- Step 915 If the second rejection reason is consistent with the preset triggering reason, the user terminal sends a third network registration request to the network device.
- the user terminal After the user terminal sends the first network registration request carrying the first request identifier to the network device, if it receives the first registration rejection response fed back by the network device, it will query the preset network type and request according to the network type registered by the user terminal. The correspondence between the identifiers, if the second request identifier corresponding to the network type registered by the user terminal is found, a second network registration request carrying the second request identifier is sent to the network device. That is, after the first network registration request is rejected, the user terminal can also send the second network registration request to the network device, and the second request identifier carried in the second network registration request is preset, and is set in the user terminal.
- the predetermined first request identifier is wrong, the situation that the network cannot be used directly will not occur, and the user terminal may try to perform network registration for many times, thereby improving the success rate of the user terminal performing network registration.
- steps in the flowcharts of FIGS. 2-9 are sequentially displayed according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, the execution of these steps is not strictly limited to the order, and these steps may be performed in other orders. Moreover, at least a part of the steps in FIG. 2 to FIG. 9 may include multiple steps or multiple stages. These steps or stages are not necessarily executed and completed at the same time, but may be executed at different times. The order of execution is also not necessarily sequential, but may be performed alternately or alternately with other steps or at least a portion of the steps or stages within the other steps.
- FIG. 10 shows a block diagram of a network registration apparatus 100 provided by an embodiment of the present application.
- the network registration apparatus 100 may be configured in a user terminal.
- the network registration device 100 may include a first sending module 101, a first receiving module 102 and a query module 103, wherein:
- the first sending module 101 is configured to send a first network registration request carrying a first request identifier to a network device.
- the first receiving module 102 is configured to receive a first registration rejection response fed back by the network device; the first registration rejection response is a response triggered when the network device determines that the first request identifier is abnormal.
- the query module 103 is configured to query the corresponding relationship between the preset network type and the request identifier according to the network type registered by the user terminal, and if the second request identifier corresponding to the network type registered by the user terminal is found, the network device Send a second network registration request carrying the second request identifier.
- the first registration rejection response includes a first rejection reason;
- the apparatus further includes a first analysis module 111 , a first judgment module 112 and an execution module 113 ;
- the first parsing module 111 is configured to parse the first registration rejection response to obtain the first rejection reason.
- the first judging module 112 is configured to judge whether the first rejection reason is consistent with the preset triggering reason.
- the executing module 113 is configured to determine the network type registered by the user terminal according to the corresponding relationship between the network type registered by the user terminal, the preset network type and the request identifier if the first rejection reason is consistent with the preset trigger cause The corresponding step of the second request identification.
- the execution module 113 includes an acquisition unit 1131 and an execution unit 1132;
- the obtaining unit 1131 is configured to obtain the request identifier switch state if the first rejection reason is consistent with the preset triggering cause.
- the executing unit 1132 is configured to, if the switch state of the request identifier is on, execute, according to the corresponding relationship between the network type registered by the user terminal, the preset network type and the request identifier, to determine the second corresponding to the network type registered by the user terminal. Steps to request identification.
- the apparatus further includes a second receiving module 131 and a second sending module 132;
- the second receiving module 131 is configured to receive a second registration rejection response sent by the network device; the second registration rejection response is a response triggered when the network device determines that the second request identifier is abnormal.
- the second sending module 132 is configured to send a third network registration request to the network device; the request identifier in the third network registration request is empty.
- the second registration rejection response includes a second rejection reason;
- the apparatus further includes a second parsing module 141 , a second judging module 142 and a third sending module 143 ;
- the second parsing module 141 is configured to parse the second registration rejection response to obtain the second rejection reason.
- the second judging module 142 is configured to judge whether the second rejection reason is consistent with the preset triggering reason.
- the third sending module 143 is configured to send a third network registration request to the network device if the second rejection reason is consistent with the preset triggering reason.
- the apparatus further includes an acquiring module 151 and a establishing module 152;
- the obtaining module 151 is configured to obtain the operator type corresponding to the SIM card of the user terminal.
- the establishing module 152 is configured to determine the network type registered by the user terminal according to the operator type, and establish a correspondence between the network type registered by the user terminal and the request identifier.
- FIG. 16 shows a block diagram of a network registration apparatus 160 provided by an embodiment of the present application.
- the network registration apparatus 160 may be configured in a network device.
- the network registration apparatus 160 may include a first receiving module 161, a sending module 162 and a second receiving module 163, wherein:
- the first receiving module 161 is configured to receive a first network registration request that carries a first request identifier and is sent by the user terminal.
- the sending module 162 is configured to send a first registration rejection response to the user terminal if it is determined that the first request identifier is abnormal.
- the second receiving module 163 is configured to receive a second network registration request carrying a second request identifier sent by the user terminal; the second request identifier is that the user terminal queries the preset network type and request identifier according to the network type registered by the user terminal The corresponding relationship between the obtained request identifiers corresponding to the network type registered by the user terminal is obtained.
- the network registration apparatus provided in the embodiments of the present application can implement the above method embodiments, and the implementation principles and technical effects thereof are similar, and details are not described herein again.
- Each module in the above-mentioned apparatus for requesting network registration may be implemented in whole or in part by software, hardware and combinations thereof.
- the above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations of the above modules.
- a computer device is provided, and the computer device may be a user terminal, and its internal structure diagram may be as shown in FIG. 17 .
- the computer equipment includes a processor, memory, a communication interface, a display screen, and an input device connected by a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities.
- the memory of the computer device includes a non-volatile storage medium, an internal memory.
- the nonvolatile storage medium stores an operating system and a computer program.
- the internal memory provides an environment for the execution of the operating system and computer programs in the non-volatile storage medium.
- the communication interface of the computer device is used for wired or wireless communication with an external terminal, and the wireless communication can be realized by WIFI, operator network, NFC (Near Field Communication) or other technologies.
- the computer program when executed by the processor, implements a network registration method.
- the display screen of the computer equipment may be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment may be a touch layer covered on the display screen, or a button, a trackball or a touchpad set on the shell of the computer equipment , or an external keyboard, trackpad, or mouse.
- FIG. 17 is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer equipment to which the solution of the present application is applied. Include more or fewer components than shown in the figures, or combine certain components, or have a different arrangement of components.
- a computer device in an embodiment of the present application, includes a memory and a processor, a computer program is stored in the memory, and the processor implements the following steps when executing the computer program:
- the processor also implements the following steps when executing the computer program: parsing the first rejection registration response to obtain the first rejection reason; judging whether the first rejection reason is consistent with the preset triggering reason; if the first rejection If the cause is the same as the preset trigger cause, the step of determining the second request identifier corresponding to the network type registered by the user terminal according to the corresponding relationship between the network type registered by the user terminal, the preset network type and the request identifier is performed.
- the processor when the processor executes the computer program, the processor further implements the following steps: if the first rejection reason is consistent with the preset trigger reason, acquiring the request flag switch state; if the request flag switch state is on, executing the The corresponding relationship between the network type registered by the user terminal, the preset network type and the request identifier is a step of determining the second request identifier corresponding to the network type registered by the user terminal.
- the processor further implements the following steps when executing the computer program: receiving a second registration rejection response sent by the network device; the second registration rejection response is a response triggered when the network device determines that the second request identifier is abnormal; Send a third network registration request to the network device; the request identifier in the third network registration request is empty.
- the processor further implements the following steps when executing the computer program: parsing the second rejection registration response to obtain a second rejection reason; judging whether the second rejection reason is consistent with the preset triggering reason; if the second rejection If the reason is consistent with the preset triggering reason, a third network registration request is sent to the network device.
- the processor also implements the following steps when executing the computer program: acquiring the operator type corresponding to the SIM card of the user terminal; determining the network type registered by the user terminal according to the operator type, and establishing Correspondence between network type and request ID.
- a computer device is provided, and the computer device may be a network device, and its internal structure diagram may be as shown in FIG. 18 .
- the computer device includes a processor, memory, and a network interface connected by a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities.
- the memory of the computer device includes a non-volatile storage medium, an internal memory.
- the nonvolatile storage medium stores an operating system, a computer program, and a database.
- the internal memory provides an environment for the execution of the operating system and computer programs in the non-volatile storage medium.
- the computer device's database is used for network registration data.
- the network interface of the computer device is used to communicate with an external terminal through a network connection.
- the computer program when executed by the processor, implements a network registration method.
- FIG. 18 is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer equipment to which the solution of the present application is applied. Include more or fewer components than shown in the figures, or combine certain components, or have a different arrangement of components.
- a computer device in an embodiment of the present application, includes a memory and a processor, a computer program is stored in the memory, and the processor implements the following steps when executing the computer program:
- a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:
- the following steps are further implemented: parsing the first registration rejection response to obtain the first rejection reason; judging whether the first rejection reason is consistent with the preset triggering reason; If the rejection reason is the same as the preset triggering cause, the step of determining the second request identifier corresponding to the network type registered by the user terminal according to the corresponding relationship between the network type registered by the user terminal, the preset network type and the request identifier is performed.
- the following steps are further implemented: if the first rejection reason is consistent with the preset triggering reason, obtain the request flag switch state; if the request flag switch state is on, execute The step of determining the second request identifier corresponding to the network type registered by the user terminal according to the correspondence between the network type registered by the user terminal, the preset network type and the request identifier.
- the computer program further implements the following steps when executed by the processor: receiving a second registration rejection response sent by the network device; the second registration rejection response is a response triggered when the network device determines that the second request identifier is abnormal ; Send a third network registration request to the network device; the request identifier in the third network registration request is empty.
- the following steps are further implemented: parsing the second registration rejection response to obtain a second rejection reason; judging whether the second rejection reason is consistent with the preset triggering reason; If the rejection reason is consistent with the preset triggering reason, a third network registration request is sent to the network device.
- the following steps are further implemented: acquiring the operator type corresponding to the SIM card of the user terminal; determining the network type registered by the user terminal according to the operator type, and establishing the user terminal registration The correspondence between the network type and the request identifier.
- a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:
- Nonvolatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
- Volatile memory may include random access memory (RAM) or external cache memory.
- RAM is available in various forms such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain Road (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.
- SRAM static RAM
- DRAM dynamic RAM
- SDRAM synchronous DRAM
- DDRSDRAM double data rate SDRAM
- ESDRAM enhanced SDRAM
- SLDRAM synchronous chain Road (Synchlink) DRAM
- SLDRAM synchronous chain Road (Synchlink) DRAM
- Rambus direct RAM
- DRAM direct memory bus dynamic RAM
- RDRAM memory bus dynamic RAM
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
一种网络注册方法、装置、用户终端及存储介质，属于通信技术领域。所述方法包括: 向网络设备发送携带第一请求标识的第一网络注册请求; 接收网络设备反馈的第一拒绝注册响应; 第一拒绝注册响应为网络设备确定第一请求标识异常时触发的响应; 以及根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，若查找到用户终端注册的网络类型对应的第二请求标识，则向网络设备发送携带第二请求标识的第二网络注册请求。
Description
相关申请交叉引用
本申请要求2020年09月15日递交的、标题为“网络注册方法、装置、用户终端及存储介质”、申请号为2020109651662的中国申请的优先权，其公开内容通过引用全部结合在本申请中。
本申请涉及一种网络注册方法、装置、用户终端及存储介质。
目前，移动通信网络的使用非常广泛，当用户终端进行网络访问时，都需要先进行网络注册。
例如，在4G网络中，用户终端进行网络注册时，用户终端向网络侧发送携带用户设定的接入点名称(Access Point Name，APN)标识的网络注册请求，网络侧设备通过验证APN后进行网络注册。在5G网络中，用户终端向网络侧发送携带用户设定的数据网络名称(Data Network Name，DNN)标识的网络注册请求，网络侧设备通过验证DNN后进行网络注册。
发明内容
根据多个实施例，本申请第一方面提供一种网络注册方法，该方法包括：
向网络设备发送携带第一请求标识的第一网络注册请求；接收网络设备反馈的第一拒绝注册响应；第一拒绝注册响应为网络设备确定第一请求标识异常时触发的响应；以及根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，若查找到用户终端注册的网络类型对应的第二请求标识，则向网络设备发送携带第二请求标识的第二网络注册请求。
根据多个实施例，本申请第二方面提供另一种网络注册方法，该方法包括：
接收用户终端发送的携带第一请求标识的第一网络注册请求；若确定第一请求标识异常，则向用户终端发送第一拒绝注册响应；接收用户终端发送的携带第二请求标识的第二网络注册请求；以及第二请求标识为用户终端根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，得到的用户终端注册的网络类型对应的请求标识。
根据多个实施例，本申请第三方面提供一种网络注册装置，该网络注册装置配置于用户终端中，该网络注册装置包括：
第一发送模块，用于向网络设备发送携带第一请求标识的第一网络注册请求；
第一接收模块，用于接收所述网络设备反馈的第一拒绝注册响应；所述第一拒绝注册响应为所述网络设备确定所述第一请求标识异常时触发的响应；以及
查询模块，用于根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，若查找到用户终端注册的网络类型对应的第二请求标识，则向网络设备发送携带第二请求标识的第二网络注册请求。
根据多个实施例，本申请第四方面提供一种网络注册装置，该网络注册装置配置于 网络设备中，该网络注册装置包括：
第一接收模块，用于接收用户终端发送的携带第一请求标识的第一网络注册请求；
发送模块，用于若确定第一请求标识异常，则向用户终端发送第一拒绝注册响应；以及
第二接收模块，用于接收用户终端发送的携带第二请求标识的第二网络注册请求；第二请求标识为用户终端根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，得到的用户终端注册的网络类型对应的请求标识。
根据多个实施例，本申请第五方面提供一种计算机设备，包括存储器和处理器，该存储器存储有计算机程序，该计算机程序被该处理器执行时实现如上述第一方面和第二方面任一的网络注册方法。
根据多个实施例，本申请第六方面提供一种计算机可读存储介质，其上存储有计算机程序，该计算机程序被处理器执行时实现如上述第一方面和第二方面任一的网络注册方法。
网络直接无法使用本申请的一个或多个实施例的细节在下面的附图和描述中提出。本申请的其它特征和优点将从说明书、附图以及权利要求书变得明显。
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。
图1为本申请实施例涉及到的一种应用环境图。
图2为本申请实施例涉及到的一种网络注册方法的流程图。
图3为本申请实施例涉及到的一种网络注册方法的流程图。
图4为本申请实施例涉及到的一种确定第二请求标识方法的流程图。
图5为本申请实施例涉及到的一种确定注册的网络类型和请求标识之间的对应关系的流程图。
图6为本申请实施例涉及到的一种网络注册方法的流程图。
图7为本申请实施例涉及到的一种发送第三网络注册请求方法的流程图；
图8为本申请实施例涉及到的一种网络注册方法的流程图。
图9为本申请实施例涉及到的一种网络注册方法的流程图。
图10为本申请实施例涉及到的一种网络注册装置的框图。
图11为本申请实施例涉及到的一种网络注册装置的框图。
图12为本申请实施例涉及到的一种网络注册装置的框图。
图13为本申请实施例涉及到的一种网络注册装置的框图。
图14为本申请实施例涉及到的一种网络注册装置的框图。
图15为本申请实施例涉及到的一种网络注册装置的框图。
图16为本申请实施例涉及到的一种网络注册装置的框图。
图17为本申请实施例涉及到的一种用户终端的框图。
图18为本申请实施例涉及到的一种网络设备的框图。
采用背景技术中的网络注册方式，当用户设定的APN标识或DNN标识错误时，就无法成功进行网络注册，从而导致网络注册成功率低。
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作进一步地详细描述。
本申请提供的网络注册方法，可以应用于如图1所示的应用环境中。其中，用户终端102通过基站与网络设备104进行通信。用户终端102可以但不限于是各种个人计算机、笔记本电脑、智能手机、平板电脑和便携式可穿戴设备。
在一个实施例中，如图2所示，提供了一种网络注册方法，以该方法应用于图1中的用户终端为例进行说明，包括以下步骤：
步骤201、向网络设备发送携带第一请求标识的第一网络注册请求。
在本申请实施例中，用户终端进行网络注册时，需要先向网络设备发送第一网络注册请求。其中，第一网络注册请求中携带有第一请求标识。
具体地，第一请求标识为用户终端进行网络注册时，第一网络注册请求中携带的标识。例如，在4G网络中，用户终端进行网络注册时，第一网络注册请求中携带的第一请求标识为APN标识。可选地，APN标识可以由用户自己手动设定，也可以是由用户终端获取预置在用户终端里面的APN标识。在5G网络中，用户终端进行网络注册时，第一网络注册请求中携带的第一请求标识为DNN标识。可选地，DNN标识可以由用户自己手动设定，也可以是由用户终端获取预置在用户终端里面的DNN标识。
步骤202、接收网络设备反馈的第一拒绝注册响应；第一拒绝注册响应为网络设备确定第一请求标识异常时触发的响应。
当第一请求标识异常时，用户终端会接收到网络设备反馈的第一拒绝注册响应，第一拒绝注册响应为网络设备确定第一请求标识异常时触发的响应。
当用户终端进行网络注册时，向网路设备发送携带第一请求标识的第一网络注册请求，服务器确定第一网络注册请求中的APN标识或DNN标识出现错误的情况下，向用户终端反馈第一拒绝注册响应，通知用户终端本次网络注册失败了。同样地，在由用户终端获取预置在用户终端里面的APN标识或DNN标识的情况下，会出现预置在用户终端里面的APN标识或DNN标识也是错误的情况，用户终端同样会接收到网络设备反馈的第一拒绝注册响应。
步骤203、根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，若查找到用户终端注册的网络类型对应的第二请求标识，则向网络设备发送携带第二请求标识的第二网络注册请求。
由于不同的用户终端进行第一网络注册时，都会有一个与第一请求标识对应的网络类型，其中，网络类型也就是用户终端当前需要注册的网络。
在用户终端接收到网络设备反馈的第一拒绝注册响应的情况下，用户终端根据该网络类型，查询预设的网络类型和请求标识之间的对应关系，其中，预设的网络类型包括了在实际应用中常用到的网络类型，预设的网络类型可以包括用户终端注册的网络类型，预设的网络类型与请求标识可以是一一对应的关系。若查找到用户终端注册的网络类型对应的请求标识，将该请求标识作为第二请求标识，用户终端重新向网络设备发送携带第二请求标识的第二网络注册请求。
用户终端向网络设备发送携带第一请求标识的第一网络注册请求，接收到网络设备反馈的第一拒绝注册响应后，则根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，若查找到用户终端注册的网络类型对应的第二请求标识，则向网络设备发送携带第二请求标识的第二网络注册请求。也就是，在第一网络注册请求被拒绝后，用户终端还能够向网络设备发送第二网络注册请求，并且，第二网络注册请求携带的第二请求标识是预设好的，在用户终端设定的第一请求标识错误时，不会出现网络直接无法使用的情况，用户终端可以多次尝试进行网络注册，从而提高用户终端进行网络注册的成功率。
在一个实施例中，如图3所示，提供了一种网络注册方法，以该方法应用于图1中的用户终端为例进行说明，包括以下步骤：
步骤301、解析第一拒绝注册响应，得到第一拒绝原因。
其中，第一拒绝注册响应包括第一拒绝原因，也就是说，第一拒绝原因被打包在用户终端接收到网络设备反馈的第一拒绝注册响应中，第一拒绝原因中可以包含异常第一请求标识的参数信息，用户终端对该第一拒绝注册响应进行解析后，可以得到第一拒绝原因，例如，用户终端可以根据Modem 4G协议栈或Modem 5G协议栈对该第一拒绝注册响应进行解压、数据处理操作后，得到第一拒绝原因。第一拒绝原因是第一请求标识的异常原因，该第一拒绝原因可以是第一请求标识参数丢失，或是第一请求标识参数无法识别。
步骤302、判断第一拒绝原因是否与预设触发原因一致。
其中，预设触发原因是预先设置在拒绝原因列表里面的，第一拒绝原因可以被包含在预设触发原因中，该预设触发原因可以是第一请求标识参数丢失、第一请求标识参数无法识别，还可以是不支持第一请求标识。具体地，在4G网络中，第一请求标识参数丢失或第一请求标识参数无法识别对应的预设触发原因为代码27(Missing or unknown APN)，在5G网络中，不支持第一请求标识对应的预设触发原因为代码91(DNN not supported with no slice or in specific slice)。
步骤303、若第一拒绝原因与预设触发原因一致，则执行根据用户终端注册的网络类型、预设的网络类型和请求标识之间的对应关系，确定用户终端注册的网络类型对应的第二请求标识的步骤。
若第一拒绝原因与预设触发原因一致，请参考图4，其示出了本申请实施例提供的一种确定用户终端注册的网络类型对应的第二请求标识的流程图，该方法可以应用于用户终端中。如图4所示，该确定用户终端注册的网络类型对应的第二请求标识的方法可以包括以下步骤：
步骤401、若第一拒绝原因与预设触发原因一致，则获取请求标识开关状态。
其中，请求标识开关状态是用户终端用来确定能否获取请求标识的，请求标识开关状态可以包括请求标识开关开启状态和请求标识开关关闭状态。可选地，请求标识开关可以是预先设置在用户终端里面的，用户也可以通过点击触发按钮来控制请求标识开关状态。
在第一拒绝原因与预设触发原因一致的情况下，也就是，在4G网络中，第一拒绝原因为代码27(Missing or unknown APN)，在5G网络中，第一拒绝原因为代码91(DNN not supported with no slice or in specific slice)，就需要获取请求标识开关状态。
步骤402、若请求标识开关状态为开启，则执行根据用户终端注册的网络类型、预设的网络类型和请求标识之间的对应关系，确定用户终端注册的网络类型对应的第二请求标识的步骤。
其中，请求标识开关状态为开启状态，也就是说，用户终端能够获取请求标识。可选地，用户终端可以对请求标识的开关状态进行检测，在检测到请求标识开关状态为开启状态的情况下，就会触发用户终端的获取操作，从而获取请求标识开关状态。
用户终端判断第一拒绝原因与预设触发原因一致时，获取请求标识开关状态，在请求标识开关状态为开启状态的情况下，则根据用户终端注册的网络类型、预设的网络类型和请求标识之间的对应关系，确定用户终端注册的网络类型对应的第二请求标识，这样避免了请求标识开关状态为关闭状态时，用户终端还会继续尝试确定用户终端注册的网络类型对应的第二请求标识的情况，从而节省了确定用户终端注册的网络类型对应的第二请求标识的时间，从而提高了用户终端进行网络注册的效率。进一步地，由于用户可以通过点击触发按钮来控制请求标识开关状态，也就是，用户可以控制用户终端是否可以使用用户终端注册的网络类型对应的第二请求标识，即用户可以灵活选择是否在第一网络注册请求失 败后继续进行网络注册，从而可以满足不同用户的要求，适应更多的场景。
用户终端通过解析第一拒绝注册响应，得到第一拒绝原因，对第一拒绝原因与预设触发原因进行判断，在第一拒绝原因与预设触发原因一致的情况下，根据用户终端注册的网络类型、预设的网络类型和请求标识之间的对应关系，确定用户终端注册的网络类型对应的第二请求标识。这样可以快速、准确定位第一拒绝原因类型，从而能够及时向网络设备发送第二网络注册请求，节省了用户终端进行网络注册的时间，从而提高网络注册的效率。并且，这样在用户终端接收到第一拒绝注册响应后，不会出现网络直接无法使用的情况，用户终端通过解析第一拒绝注册响应得到第一拒绝原因后，根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，向网络设备发送携带第二请求标识的第二网络注册请求。
也就是，在第一网络注册请求被拒绝后，用户终端还能够向网络设备发送携带第二请求标识的第二网络注册请求，并且，第二网络注册请求携带的第二请求标识是预设好的，在用户终端设定的第一请求标识错误时，不会出现网络直接无法使用的情况，用户终端可以多次尝试进行网络注册，从而提高用户终端进行网络注册的成功率。
上述用户终端注册的网络类型和请求标识之间的对应关系的确定方法，请参考图5，其示出了本申请实施例提供的一种确定注册的网络类型和请求标识之间的对应关系的流程图，该方法可以应用于用户终端中。如图5所示，该确定注册的网络类型和请求标识之间的对应关系的方法可以包括以下步骤：
步骤501、获取用户终端的SIM卡对应的运营商类型。
其中，每张SIM卡都对应着一个运营商类型，例如，SIM卡1对应的运营商类型为A，SIM卡2对应的运营商类型为B，SIM卡3对应的运营商类型为C。用户终端当前使用的SIM卡为SIM卡1，那么，用户终端获取到的运营商类型就为A
步骤502、根据运营商类型确定用户终端注册的网络类型，并建立用户终端注册的网络类型和请求标识之间的对应关系。
其中，用户终端注册的网络类型可以根据运营商类型确定，用户终端注册的网络类型可以为公共陆地移动网络(Public Land Mobile Network，PLMN)类型的一种。例如，运营商类型A对应的PLMN为D，运营商类型B对应的PLMN为E，运营商类型C对应的PLMN为F。用户终端的运营商类型为A，那么，用户终端注册的网络类型PLMN就为D。
用户终端注册的网络类型和请求标识之间为一一对应的关系，例如，用户终端注册的网络类型D对应的请求标识为D_NET，用户终端注册的网络类型E对应的请求标识为E_NET，用户终端注册的网络类型F对应的请求标识为F_NET。
在实际应用中，用户终端向网络设备发送携带第二请求标识的第二网络注册请求后，也会出现注册不成功的情况，也就是，同样会出现接收到网络设备发送的第二拒绝注册响应。在这种情况下的网络注册方法请参考图6，其示出了本申请实施例提供的一种网络注册方法的流程图，该方法可以应用于用户终端中。如图6所示，该网络注册方法可以包括以下步骤：
步骤601、接收网络设备发送的第二拒绝注册响应；第二拒绝注册响应为网络设备确定第二请求标识异常时触发的响应。
其中，第二网络注册请求中携带有第二请求标识，当第二请求标识异常时，用户终端会接收到网络设备反馈的第二拒绝注册响应，第二拒绝注册响应为网络设备确定第二请求标识异常时触发的响应。
具体地，第二请求标识为用户终端预先设置的与网络类型对应的请求标识，用户终端获取到预置在用户终端的第二请求标识后，向网络设备发送携带第二请求标识的第二网络注册请求。但在实际应用中，会出现预置在用户终端里面的第二请求标识也是错误的，或 是用户终端预先设置的与网络类型与第二请求标识的对应关系错误的情况，此时，第二网络注册请求中就携带了异常的第二请求标识，用户终端同样会接收到网络设备反馈的第二拒绝注册响应，也就是网络注册失败了。
步骤602、向网络设备发送第三网络注册请求；第三网络注册请求中的请求标识为空。
其中，第三网络注册请求为携带空请求标识的请求，空请求标识可以是请求标识的参数都设置为0，还可以设置为NULL APN或NULL DNN。在用户终端接收到网络设备反馈的第二拒绝注册响应的情况下，用户终端向网络设备继续发送携带空请求标识的第三网络注册请求。在这种情况下，网络设备可以根据网络协议的特性接收该携带空请求标识的第三网络注册请求，并会反馈给网络设备一个默认的请求标识，也就是网络注册成功了。
在第二请求标识异常时，用户终端接收到网络设备发送的第二拒绝注册响应后，会向网络设备继续发送携带空请求标识的第三网络注册请求，重新进行网络注册，从而又给用户终端增加了一次网络注册的机会，从而也能够提高用户终端进行网络注册的成功率。
在用户终端接收到网络设备发送的第二拒绝注册响应的情况下，请参考图7，其示出了本申请实施例提供的一种向网络设备发送第三网络注册请求的流程图，该方法可以应用于用户终端中。如图7所示，该向网络设备发送第三网络注册请求的方法可以包括以下步骤：
步骤701、解析第二拒绝注册响应，得到第二拒绝原因。
其中，第二拒绝注册响应包括第二拒绝原因，具体的解析第二拒绝注册响应、得到第二拒绝原因的过程与步骤301类似，在此不再赘述。
步骤702、判断第二拒绝原因是否与预设触发原因一致。
其中，判断第二拒绝原因是否与预设触发原因一致的过程与步骤302类似，在此不再赘述。
步骤703、若第二拒绝原因与预设触发原因一致，则向网络设备发送第三网络注册请求。
用户终端通过解析第二拒绝注册响应，得到第二拒绝原因，对第二拒绝原因与预设触发原因进行判断，在第二拒绝原因与预设触发原因一致的情况下，向网络设备发送第三网络注册请求。这样可以快速、准确定位第二拒绝原因类型，从而能够及时向网络设备发送第三网络注册请求，节省了用户终端进行网络注册的时间，从而提高网络注册的效率。
在一个实施例中，如图8所示，提供了一种网络注册方法，以该方法应用于图8中的网络设备为例进行说明，包括以下步骤：
步骤801、接收用户终端发送的携带第一请求标识的第一网络注册请求。
其中，用户终端进行网络注册时，需要先向网络设备发送第一网络注册请求，网络设备会接收到用户终端发送的携带第一请求标识的第一网络注册请求。
步骤802、若确定第一请求标识异常，则向用户终端发送第一拒绝注册响应。
其中，第一网络注册请求中携带有第一请求标识，当第一请求标识异常时，网络设备会向用户终端反馈第一拒绝注册响应，第一拒绝注册响应为网络设备确定第一请求标识异常时触发的响应。
步骤803、接收用户终端发送的携带第二请求标识的第二网络注册请求；第二请求标识为用户终端根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，得到的用户终端注册的网络类型对应的请求标识。
其中，用户终端在向网络设备发送携带第一请求标识的第一网络注册请求后，若接收到网络设备反馈的第一拒绝注册响应，则根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，若查找到用户终端注册的网络类型对应的第二请求标 识，则向网络设备发送携带第二请求标识的第二网络注册请求，网络设备会接收用户终端发送的携带第二请求标识的第二网络注册请求。
也就是，在第一网络注册请求被拒绝后，用户终端还能够向网络设备发送第二网络注册请求，并且，第二网络注册请求携带的第二请求标识是预设好的，在用户终端设定的第一请求标识错误时，不会出现网络直接无法使用的情况，给用户终端更多次的机会进行网络注册，从而提高用户终端进行网络注册的成功率。
如图9所示，本申请实施例还提供一种网络注册方法，该方法包括以下步骤：
步骤901、用户终端向网络设备发送携带第一请求标识的第一网络注册请求。
步骤902、网络设备反馈第一拒绝注册响应。
步骤903、用户终端接收到网络设备反馈的第一拒绝注册响应。
步骤904、用户终端解析第一拒绝注册响应，得到第一拒绝原因。
步骤905、用户终端判断第一拒绝原因是否与预设触发原因一致。
步骤906、若第一拒绝原因与预设触发原因一致，用户终端则获取请求标识开关状态。
步骤907、用户终端获取用户终端的SIM卡对应的运营商类型。
步骤908、用户终端根据运营商类型确定用户终端注册的网络类型，并建立用户终端注册的网络类型和请求标识之间的对应关系。
步骤909、若请求标识开关状态为开启，用户终端则执行根据用户终端注册的网络类型、预设的网络类型和请求标识之间的对应关系，确定用户终端注册的网络类型对应的第二请求标识的步骤。
步骤910、用户终端向网络设备发送携带第二请求标识的第二网络注册请求。
步骤911、网络设备反馈第二拒绝注册响应。
步骤912、用户终端接收到网络设备反馈的第二拒绝注册响应。
步骤913、用户终端解析第二拒绝注册响应，得到第二拒绝原因。
步骤914、用户终端判断第二拒绝原因是否与预设触发原因一致。
步骤915、若第二拒绝原因与预设触发原因一致，用户终端向网络设备发送第三网络注册请求。
用户终端在向网络设备发送携带第一请求标识的第一网络注册请求后，若接收到网络设备反馈的第一拒绝注册响应，则根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，若查找到用户终端注册的网络类型对应的第二请求标识，则向网络设备发送携带第二请求标识的第二网络注册请求。也就是，在第一网络注册请求被拒绝后，用户终端还能够向网络设备发送第二网络注册请求，并且，第二网络注册请求携带的第二请求标识是预设好的，在用户终端设定的第一请求标识错误时，不会出现网络直接无法使用的情况，用户终端可以多次尝试进行网络注册，从而提高用户终端进行网络注册的成功率。
应该理解的是，虽然图2-图9的流程图中的各个步骤按照箭头的指示依次显示，但是这些步骤并不是必然按照箭头指示的顺序依次执行。除非本文中有明确的说明，这些步骤的执行并没有严格的顺序限制，这些步骤可以以其它的顺序执行。而且，图2-图9中的至少一部分步骤可以包括多个步骤或者多个阶段，这些步骤或者阶段并不必然是在同一时刻执行完成，而是可以在不同的时刻执行，这些步骤或者阶段的执行顺序也不必然是依次进行，而是可以与其它步骤或者其它步骤中的步骤或者阶段的至少一部分轮流或者交替地执行。
请参考图10，其示出了本申请实施例提供的一种网络注册装置100的框图，该网络注册装置100可以配置于用户终端中。如图10所示，该网络注册装置100可以包括第一 发送模块101、第一接收模块102和查询模块103，其中：
该第一发送模块101，用于向网络设备发送携带第一请求标识的第一网络注册请求。
该第一接收模块102，用于接收所述网络设备反馈的第一拒绝注册响应；所述第一拒绝注册响应为所述网络设备确定所述第一请求标识异常时触发的响应。
该查询模块103，用于根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，若查找到用户终端注册的网络类型对应的第二请求标识，则向网络设备发送携带第二请求标识的第二网络注册请求。
在其中一个实施例中，如图11所示，第一拒绝注册响应包括第一拒绝原因；该装置还包括第一解析模块111、第一判断模块112和执行模块113；
该第一解析模块111，用于解析第一拒绝注册响应，得到第一拒绝原因。
该第一判断模块112，用于判断第一拒绝原因是否与预设触发原因一致。
该执行模块113，用于若第一拒绝原因与预设触发原因一致，则执行根据用户终端注册的网络类型、预设的网络类型和请求标识之间的对应关系，确定用户终端注册的网络类型对应的第二请求标识的步骤。
在其中一个实施例中，如图12所示，该执行模块113包括获取单元1131和执行单元1132；
该获取单元1131，用于若第一拒绝原因与预设触发原因一致，则获取请求标识开关状态。
该执行单元1132，用于若请求标识开关状态为开启，则执行根据用户终端注册的网络类型、预设的网络类型和请求标识之间的对应关系，确定用户终端注册的网络类型对应的第二请求标识的步骤。
在其中一个实施例中，如图13所示，该装置还包括接第二收模块131和第二发送模块132；
该第二接收模块131，用于接收网络设备发送的第二拒绝注册响应；第二拒绝注册响应为网络设备确定第二请求标识异常时触发的响应。
该第二发送模块132，用于向网络设备发送第三网络注册请求；第三网络注册请求中的请求标识为空。
在其中一个实施例中，如图14所示，第二拒绝注册响应包括第二拒绝原因；该装置还包括第二解析模块141、第二判断模块142和第三发送模块143；
该第二解析模块141，用于解析第二拒绝注册响应，得到第二拒绝原因。
该第二判断模块142，用于判断第二拒绝原因是否与预设触发原因一致。
该第三发送模块143，用于若第二拒绝原因与预设触发原因一致，则向网络设备发送第三网络注册请求。
在其中一个实施例中，如图15所示，该装置还包括获取模块151和建立模块152；
该获取模块151，用于获取用户终端的SIM卡对应的运营商类型。
该建立模块152，用于根据运营商类型确定用户终端注册的网络类型，并建立用户终端注册的网络类型和请求标识之间的对应关系。
请参考图16，其示出了本申请实施例提供的一种网络注册装置160的框图，该网络注册装置160可以配置于网络设备中。如图16所示，该网络注册装置160可以包括第一接收模块161，发送模块162和第二接收模块163，其中：
该第一接收模块161，用于接收用户终端发送的携带第一请求标识的第一网络注册请求。
该发送模块162，用于若确定第一请求标识异常，则向用户终端发送第一拒绝注册响应。
该第二接收模块163，用于接收用户终端发送的携带第二请求标识的第二网络注册请求；第二请求标识为用户终端根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，得到的用户终端注册的网络类型对应的请求标识。
本申请实施例提供的网络注册装置，可以实现上述方法实施例，其实现原理和技术效果类似，在此不再赘述。
关于网络注册装置的具体限定可以参见上文中对于网络注册方法的限定，在此不再赘述。上述请求网络注册装置中的各个模块可全部或部分通过软件、硬件及其组合来实现。上述各模块可以硬件形式内嵌于或独立于计算机设备中的处理器中，也可以以软件形式存储于计算机设备中的存储器中，以便于处理器调用执行以上各个模块的操作。
在一个实施例中，提供了一种计算机设备，该计算机设备可以是用户终端，其内部结构图可以如图17所示。该计算机设备包括通过系统总线连接的处理器、存储器、通信接口、显示屏和输入装置。其中，该计算机设备的处理器用于提供计算和控制能力。该计算机设备的存储器包括非易失性存储介质、内存储器。该非易失性存储介质存储有操作系统和计算机程序。该内存储器为非易失性存储介质中的操作系统和计算机程序的运行提供环境。该计算机设备的通信接口用于与外部的终端进行有线或无线方式的通信，无线方式可通过WIFI、运营商网络、NFC(近场通信)或其他技术实现。该计算机程序被处理器执行时以实现一种网络注册方法。该计算机设备的显示屏可以是液晶显示屏或者电子墨水显示屏，该计算机设备的输入装置可以是显示屏上覆盖的触摸层，也可以是计算机设备外壳上设置的按键、轨迹球或触控板，还可以是外接的键盘、触控板或鼠标等。
本领域技术人员可以理解，图17中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的计算机设备的限定，具体地计算机设备可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
在本申请的一个实施例中，提供了一种计算机设备，该计算机设备包括存储器和处理器，存储器中存储有计算机程序，该处理器执行计算机程序时实现以下步骤：
向网络设备发送携带第一请求标识的第一网络注册请求；接收网络设备反馈的第一拒绝注册响应；第一拒绝注册响应为网络设备确定第一请求标识异常时触发的响应；根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，若查找到用户终端注册的网络类型对应的第二请求标识，则向网络设备发送携带第二请求标识的第二网络注册请求。
在本申请的一个实施例中，处理器执行计算机程序时还实现以下步骤：解析第一拒绝注册响应，得到第一拒绝原因；判断第一拒绝原因是否与预设触发原因一致；若第一拒绝原因与预设触发原因一致，则执行根据用户终端注册的网络类型、预设的网络类型和请求标识之间的对应关系，确定用户终端注册的网络类型对应的第二请求标识的步骤。
在本申请的一个实施例中，处理器执行计算机程序时还实现以下步骤：若第一拒绝原因与预设触发原因一致，则获取请求标识开关状态；若请求标识开关状态为开启，则执行根据用户终端注册的网络类型、预设的网络类型和请求标识之间的对应关系，确定用户终端注册的网络类型对应的第二请求标识的步骤。
在本申请的一个实施例中，处理器执行计算机程序时还实现以下步骤：接收网络设备发送的第二拒绝注册响应；第二拒绝注册响应为网络设备确定第二请求标识异常时触发的响应；向网络设备发送第三网络注册请求；第三网络注册请求中的请求标识为空。
在本申请的一个实施例中，处理器执行计算机程序时还实现以下步骤：解析第二拒绝注册响应，得到第二拒绝原因；判断第二拒绝原因是否与预设触发原因一致；若第二拒绝原因与预设触发原因一致，则向网络设备发送第三网络注册请求。
在本申请的一个实施例中，处理器执行计算机程序时还实现以下步骤：获取用户终端的SIM卡对应的运营商类型；根据运营商类型确定用户终端注册的网络类型，并建立用户终端注册的网络类型和请求标识之间的对应关系。
本申请实施例提供的计算机设备，其实现原理和技术效果与上述方法实施例类似，在此不再赘述。
在一个实施例中，提供了一种计算机设备，该计算机设备可以是网络设备，其内部结构图可以如图18所示。该计算机设备包括通过系统总线连接的处理器、存储器和网络接口。其中，该计算机设备的处理器用于提供计算和控制能力。该计算机设备的存储器包括非易失性存储介质、内存储器。该非易失性存储介质存储有操作系统、计算机程序和数据库。该内存储器为非易失性存储介质中的操作系统和计算机程序的运行提供环境。该计算机设备的数据库用于网络注册数据。该计算机设备的网络接口用于与外部的终端通过网络连接通信。该计算机程序被处理器执行时以实现一种网络注册方法。
本领域技术人员可以理解，图18中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的计算机设备的限定，具体地计算机设备可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
在本申请的一个实施例中，提供了一种计算机设备，该计算机设备包括存储器和处理器，存储器中存储有计算机程序，该处理器执行计算机程序时实现以下步骤：
接收用户终端发送的携带第一请求标识的第一网络注册请求；若确定第一请求标识异常，则向用户终端发送第一拒绝注册响应；接收用户终端发送的携带第二请求标识的第二网络注册请求；第二请求标识为用户终端根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，得到的用户终端注册的网络类型对应的请求标识。
本申请实施例提供的计算机设备，其实现原理和技术效果与上述方法实施例类似，在此不再赘述。
在本申请的一个实施例中，提供了一种计算机可读存储介质，其上存储有计算机程序，计算机程序被处理器执行时实现以下步骤：
向网络设备发送携带第一请求标识的第一网络注册请求；接收网络设备反馈的第一拒绝注册响应；第一拒绝注册响应为网络设备确定第一请求标识异常时触发的响应；根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，若查找到用户终端注册的网络类型对应的第二请求标识，则向网络设备发送携带第二请求标识的第二网络注册请求。
在本申请的一个实施例中，计算机程序被处理器执行时还实现以下步骤：解析第一拒绝注册响应，得到第一拒绝原因；判断第一拒绝原因是否与预设触发原因一致；若第一拒绝原因与预设触发原因一致，则执行根据用户终端注册的网络类型、预设的网络类型和请求标识之间的对应关系，确定用户终端注册的网络类型对应的第二请求标识的步骤。
在本申请的一个实施例中，计算机程序被处理器执行时还实现以下步骤：若第一拒绝原因与预设触发原因一致，则获取请求标识开关状态；若请求标识开关状态为开启，则执行根据用户终端注册的网络类型、预设的网络类型和请求标识之间的对应关系，确定用户终端注册的网络类型对应的第二请求标识的步骤。
在本申请的一个实施例中，计算机程序被处理器执行时还实现以下步骤：接收网络设备发送的第二拒绝注册响应；第二拒绝注册响应为网络设备确定第二请求标识异常时触发的响应；向网络设备发送第三网络注册请求；第三网络注册请求中的请求标识为空。
在本申请的一个实施例中，计算机程序被处理器执行时还实现以下步骤：解析第二拒 绝注册响应，得到第二拒绝原因；判断第二拒绝原因是否与预设触发原因一致；若第二拒绝原因与预设触发原因一致，则向网络设备发送第三网络注册请求。
在本申请的一个实施例中，计算机程序被处理器执行时还实现以下步骤：获取用户终端的SIM卡对应的运营商类型；根据运营商类型确定用户终端注册的网络类型，并建立用户终端注册的网络类型和请求标识之间的对应关系。
本实施例提供的计算机可读存储介质，其实现原理和技术效果与上述方法实施例类似，在此不再赘述。
在本申请的一个实施例中，提供了一种计算机可读存储介质，其上存储有计算机程序，计算机程序被处理器执行时实现以下步骤：
接收用户终端发送的携带第一请求标识的第一网络注册请求；若确定第一请求标识异常，则向用户终端发送第一拒绝注册响应；接收用户终端发送的携带第二请求标识的第二网络注册请求；第二请求标识为用户终端根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，得到的用户终端注册的网络类型对应的请求标识。
本实施例提供的计算机可读存储介质，其实现原理和技术效果与上述方法实施例类似，在此不再赘述。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的计算机程序可存储于一非易失性计算机可读取存储介质中，该计算机程序在执行时，可包括如上述各方法的实施例的流程。其中，本申请所提供的各实施例中所使用的对存储器、存储、数据库或其它介质的任何引用，均可包括非易失性和/或易失性存储器。非易失性存储器可包括只读存储器(ROM)、可编程ROM(PROM)、电可编程ROM(EPROM)、电可擦除可编程ROM(EEPROM)或闪存。易失性存储器可包括随机存取存储器(RAM)或者外部高速缓冲存储器。作为说明而非局限，RAM以多种形式可得，诸如静态RAM(SRAM)、动态RAM(DRAM)、同步DRAM(SDRAM)、双数据率SDRAM(DDRSDRAM)、增强型SDRAM(ESDRAM)、同步链路(Synchlink)DRAM(SLDRAM)、存储器总线(Rambus)直接RAM(RDRAM)、直接存储器总线动态RAM(DRDRAM)、以及存储器总线动态RAM(RDRAM)等。
以上实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对申请专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干变形和改进，这些都属于本申请的保护范围。因此，本申请专利的保护范围应以所附权利要求为准。
Claims (14)
- 一种网络注册方法，包括：向网络设备发送携带第一请求标识的第一网络注册请求；接收所述网络设备反馈的第一拒绝注册响应；所述第一拒绝注册响应为所述网络设备确定所述第一请求标识异常时触发的响应；以及根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，若查找到所述用户终端注册的网络类型对应的第二请求标识，则向所述网络设备发送携带所述第二请求标识的第二网络注册请求。
- 根据权利要求1所述的方法，其中所述第一拒绝注册响应包括第一拒绝原因；所述方法还包括：解析所述第一拒绝注册响应，得到所述第一拒绝原因；判断所述第一拒绝原因是否与预设触发原因一致；以及若所述第一拒绝原因与所述预设触发原因一致，则执行根据用户终端注册的网络类型、预设的网络类型和请求标识之间的对应关系，确定所述用户终端注册的网络类型对应的第二请求标识的步骤。
- 根据权利要求2所述的方法，其中若所述第一拒绝原因与所述预设触发原因一致，则执行根据用户终端注册的网络类型、预设的网络类型和请求标识之间的对应关系，确定所述用户终端注册的网络类型对应的第二请求标识的步骤，包括：若所述第一拒绝原因与所述预设触发原因一致，则获取请求标识开关状态；以及若所述请求标识开关状态为开启，则执行所述根据用户终端注册的网络类型、预设的网络类型和请求标识之间的对应关系，确定所述用户终端注册的网络类型对应的第二请求标识的步骤。
- 根据权利要求1-3任一项所述的方法，还包括：接收所述网络设备发送的第二拒绝注册响应；所述第二拒绝注册响应为所述网络设备确定所述第二请求标识异常时触发的响应；以及向所述网络设备发送第三网络注册请求；所述第三网络注册请求中的请求标识为空。
- 根据权利要求4所述的方法，其中所述第二拒绝注册响应包括第二拒绝原因；所述方法还包括：解析所述第二拒绝注册响应，得到所述第二拒绝原因；判断所述第二拒绝原因是否与预设触发原因一致；以及若所述第二拒绝原因与所述预设触发原因一致，则向所述网络设备发送第三网络注册请求。
- 根据权利要求1-3任一项所述的方法，还包括：获取所述用户终端的SIM卡对应的运营商类型；以及根据所述运营商类型确定所述用户终端注册的网络类型，并建立所述用户终端注册的网络类型和请求标识之间的对应关系。
- 根据权利要求1所述的方法，其中所述第一请求标识为所述用户终端进行所述网络注册时，所述第一网络注册请求中携带的标识。
- 根据权利要求3所述的方法，其中所述请求标识开关是预先设置在所述用户终端里面的，用户通过点击触发按钮来控制所述请求标识开关状态。
- 根据权利要求8所述的方法，其中所述用户终端对所述请求标识的开关状态进行检测，响应于检测到所述请求标识开关状态为开启状态的情况下，触发所述用户终端的获取操作，从而获取所述请求标识开关状态。
- 根据权利要求4所述的方法，其中所述第二请求标识为所述用户终端预先设置的与所述网络类型对应的请求标识，所述用户终端获取到预置在所述用户终端的所述第二请求标识后，向所述网络设备发送携带所述第二请求标识的所述第二网络注册请求。
- 一种网络注册方法，包括：接收用户终端发送的携带第一请求标识的第一网络注册请求；若确定所述第一请求标识异常，则向所述用户终端发送第一拒绝注册响应；以及接收所述用户终端发送的携带第二请求标识的第二网络注册请求；所述第二请求标识为所述用户终端根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，得到的所述用户终端注册的网络类型对应的请求标识。
- 一种网络注册装置，包括：第一发送模块，用于向网络设备发送携带第一请求标识的第一网络注册请求；第一接收模块，用于接收所述网络设备反馈的第一拒绝注册响应；所述第一拒绝注册响应为所述网络设备确定所述第一请求标识异常时触发的响应；以及查询模块，用于根据用户终端注册的网络类型，查询预设的网络类型和请求标识之间的对应关系，若查找到所述用户终端注册的网络类型对应的第二请求标识，则向所述网络设备发送携带所述第二请求标识的第二网络注册请求。
- 一种用户终端，包括存储器和处理器，所述存储器存储有计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至10任一项所述的方法的步骤。
- 一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至10任一项所述的方法的步骤。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010965166.2 | 2020-09-15 | ||
| CN202010965166.2A CN112261717B (zh) | 2020-09-15 | 2020-09-15 | 网络注册方法、装置、用户终端及存储介质 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2022057429A1 true WO2022057429A1 (zh) | 2022-03-24 |
Family
ID=74232934
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2021/107031 WO2022057429A1 (zh) | 2020-09-15 | 2021-07-19 | 网络注册方法、装置、用户终端及存储介质 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112261717B (zh) |
| WO (1) | WO2022057429A1 (zh) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114916056A (zh) * | 2022-04-01 | 2022-08-16 | 西安广和通无线通信有限公司 | 数据网络名称获取方法、系统、基站、终端及存储介质 |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112261717B (zh) * | 2020-09-15 | 2024-06-21 | 深圳市广和通无线股份有限公司 | 网络注册方法、装置、用户终端及存储介质 |
| CN113015265B (zh) * | 2021-02-24 | 2023-07-18 | 西安广和通无线软件有限公司 | 网络会话自愈方法、装置、系统、计算机设备和存储介质 |
| CN113194549B (zh) * | 2021-03-22 | 2022-07-22 | 深圳市广和通无线股份有限公司 | 数据连接方法、装置、终端设备和计算机可读存储介质 |
| CN117319987A (zh) * | 2022-06-23 | 2023-12-29 | 中兴通讯股份有限公司 | 限制机卡分离的方法及装置、系统、存储介质、电子装置 |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080293407A1 (en) * | 2007-05-24 | 2008-11-27 | Jean-Philippe Cormier | Wireless Device and Method for Determining Which APN to Use |
| CN107484239A (zh) * | 2017-08-22 | 2017-12-15 | 奇酷互联网络科技（深圳）有限公司 | 网络注册异常处理方法、装置及用户终端 |
| CN107948976A (zh) * | 2017-12-01 | 2018-04-20 | 广东欧珀移动通信有限公司 | Lte网络接入结果的检测方法及装置、计算机存储介质 |
| CN111065139A (zh) * | 2019-12-31 | 2020-04-24 | 深圳市有方科技股份有限公司 | 一种物联网设备开机附着的方法及设备 |
| CN112261717A (zh) * | 2020-09-15 | 2021-01-22 | 深圳市广和通无线股份有限公司 | 网络注册方法、装置、用户终端及存储介质 |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104955045B (zh) * | 2015-06-12 | 2019-02-05 | 联想(北京)有限公司 | 一种接入控制方法、装置、终端及系统 |
-
2020
- 2020-09-15 CN CN202010965166.2A patent/CN112261717B/zh active Active
-
2021
- 2021-07-19 WO PCT/CN2021/107031 patent/WO2022057429A1/zh active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080293407A1 (en) * | 2007-05-24 | 2008-11-27 | Jean-Philippe Cormier | Wireless Device and Method for Determining Which APN to Use |
| CN107484239A (zh) * | 2017-08-22 | 2017-12-15 | 奇酷互联网络科技（深圳）有限公司 | 网络注册异常处理方法、装置及用户终端 |
| CN107948976A (zh) * | 2017-12-01 | 2018-04-20 | 广东欧珀移动通信有限公司 | Lte网络接入结果的检测方法及装置、计算机存储介质 |
| CN111065139A (zh) * | 2019-12-31 | 2020-04-24 | 深圳市有方科技股份有限公司 | 一种物联网设备开机附着的方法及设备 |
| CN112261717A (zh) * | 2020-09-15 | 2021-01-22 | 深圳市广和通无线股份有限公司 | 网络注册方法、装置、用户终端及存储介质 |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114916056A (zh) * | 2022-04-01 | 2022-08-16 | 西安广和通无线通信有限公司 | 数据网络名称获取方法、系统、基站、终端及存储介质 |
| CN114916056B (zh) * | 2022-04-01 | 2024-06-14 | 西安广和通无线通信有限公司 | 数据网络名称获取方法、系统、基站、终端及存储介质 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112261717A (zh) | 2021-01-22 |
| CN112261717B (zh) | 2024-06-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2022057429A1 (zh) | 网络注册方法、装置、用户终端及存储介质 | |
| JP6726426B2 (ja) | 端末間のログイン不要方法及び装置 | |
| WO2022001554A1 (zh) | 配置文件切换方法、装置、计算机设备和存储介质 | |
| CN106714206B (zh) | 检测无线网络接入点连接网络的方法和装置 | |
| US20220210757A1 (en) | Multi-card user equipment and communication method therefor, and network device | |
| CN111752641A (zh) | 微服务容器之间服务启动方法、装置、设备及存储介质 | |
| WO2020057400A1 (zh) | 多卡漫游注册网络的方法、装置、计算机设备和存储介质 | |
| CN111193716B (zh) | 业务数据调用方法、装置、计算机设备和存储介质 | |
| CN107371234B (zh) | 注册方法、装置及终端 | |
| CN109379779B (zh) | 拨号联网方法、装置、计算机设备和存储介质 | |
| CN112738046B (zh) | 一种一键登录的方法、终端及系统服务器 | |
| CN109257426B (zh) | 业务线资源加载方法、装置、计算机设备和存储介质 | |
| CN108595280B (zh) | 接口适配方法、装置、计算机设备和存储介质 | |
| CN112566078A (zh) | 设备连接方法及装置、存储介质及电子装置 | |
| CN111328068B (zh) | 写卡方法、装置、计算机设备和存储介质 | |
| CN114585002A (zh) | 通信处理方法、装置、终端设备和计算机可读存储介质 | |
| CN112804651B (zh) | 绑定方法、装置和计算机设备 | |
| CN112788545A (zh) | 绑定方法、计算机设备和存储介质 | |
| CN112423288B (zh) | 拨号分析方法、装置、计算机设备和存储介质 | |
| WO2019033981A1 (zh) | 终端可达性管理方法、核心网及接入网 | |
| CN111343627B (zh) | 网络注册方法、装置及终端设备 | |
| CN114979072A (zh) | 自动拨号上网方法、主机、无线模块和终端设备 | |
| CN113194521A (zh) | 5g通信模块搜网方法、装置、计算机设备和存储介质 | |
| CN114556891A (zh) | 确定设备状态的方法、装置、设备及存储介质 | |
| CN113225756B (zh) | 驻留网络的方法、装置、终端和计算机可读存储介质 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21868258 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 21868258 Country of ref document: EP Kind code of ref document: A1 |