CN112261717B - Network registration method, device, user terminal and storage medium - Google Patents
Network registration method, device, user terminal and storage medium Download PDFInfo
- Publication number
- CN112261717B CN112261717B CN202010965166.2A CN202010965166A CN112261717B CN 112261717 B CN112261717 B CN 112261717B CN 202010965166 A CN202010965166 A CN 202010965166A CN 112261717 B CN112261717 B CN 112261717B
- Authority
- CN
- China
- Prior art keywords
- network
- request
- user terminal
- registration
- request identifier
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 68
- 230000004044 response Effects 0.000 claims abstract description 111
- 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 25
- 238000004891 communication Methods 0.000 abstract description 6
- 238000010586 diagram Methods 0.000 description 14
- 230000000694 effects Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 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
- 230000003068 static effect Effects 0.000 description 1
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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The application discloses a network registration method, a network registration device, a user terminal and a storage medium, and belongs to the technical field of communication. The method comprises the following steps: transmitting a first network registration request carrying a first request identifier to network equipment; receiving a first rejection registration response fed back by the network equipment; the first refusal registration response is a response triggered when the network equipment determines that the first request identification is abnormal; inquiring a corresponding relation between a preset network type and a request identifier according to the network type registered by the user terminal, and if a second request identifier corresponding to the network type registered by the user terminal is found, sending a second network registration request carrying the second request identifier to the network equipment. The technical scheme provided by the embodiment of the application can improve the success rate of network registration of the user terminal.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a network registration method, a device, a user terminal, and a storage medium.
Background
Currently, mobile communication networks are widely used, and when a user terminal performs network access, network registration is required first.
For example, in the 4G network, when the user terminal performs network registration, the user terminal sends a network registration request carrying an access point name (Access Point Name, APN) identifier set by the user to the network side, and the network side device performs network registration after verifying the APN. In the 5G network, the user terminal sends a network registration request carrying a data network name (Data Network Name, DNN) identifier set by the user to the network side, and the network side equipment performs network registration after verifying the DNN.
However, with the network registration method, when the APN identifier or the DNN identifier set by the user is wrong, the network registration cannot be successfully performed, which results in poor network registration success rate.
Disclosure of Invention
Based on the above, the embodiment of the application provides a network registration method, a device, a user terminal and a storage medium, which can improve the success rate of network registration of the user terminal.
In a first aspect, a network registration method is provided, the method including:
Transmitting a first network registration request carrying a first request identifier to network equipment; receiving a first rejection registration response fed back by the network equipment; the first refusal registration response is a response triggered when the network equipment determines that the first request identification is abnormal; inquiring a corresponding relation between a preset network type and a request identifier according to the network type registered by the user terminal, and if a second request identifier corresponding to the network type registered by the user terminal is found, sending a second network registration request carrying the second request identifier to the network equipment.
In one embodiment, the first reject registration response includes a first reject cause; the method further comprises the steps of:
analyzing the first rejection registration response to obtain a first rejection reason; judging whether the first reject cause is consistent with a preset trigger cause or not; and if the first reject cause is consistent with the preset trigger cause, executing the step of determining a second request identifier corresponding to the network type registered by the user terminal according to the corresponding relation among the network type registered by the user terminal, the preset network type and the request identifier.
In one embodiment, if the first reject cause is consistent with 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, including:
if the first reject reason is consistent with the preset trigger reason, acquiring a request identification switch state; and if the request identification switch state is on, executing the step of determining a second request identification corresponding to the network type registered by the user terminal according to the corresponding relation among the network type registered by the user terminal, the preset network type and the request identification.
In one embodiment, the method further comprises:
Receiving a second rejection registration response sent by the network equipment; the second refusal registration response is a response triggered when the network equipment determines that the second request identification is abnormal; sending a third network registration request to the network device; the request identification in the third network registration request is null.
In one embodiment, the second reject registration response includes a second reject cause; the method further comprises the steps of:
Analyzing the second rejection registration response to obtain a second rejection reason; judging whether the second reject cause is consistent with a preset trigger cause or not; and if the second reject cause is consistent with the preset trigger cause, sending a third network registration request to the network equipment.
In one embodiment, the method further comprises:
acquiring an operator type corresponding to a SIM card of a user terminal; and determining the network type registered by the user terminal according to the operator type, and establishing a corresponding relation between the network type registered by the user terminal and the request identifier.
In a second aspect, there is provided another network registration method, the method comprising:
Receiving a first network registration request carrying a first request identifier sent by a user terminal; if the first request identification is determined to be abnormal, a first rejection registration response is sent to the user terminal; receiving a second network registration request carrying a second request identifier sent by a user terminal; the second request identifier is a request identifier corresponding to the network type registered by the user terminal, which is obtained by inquiring the corresponding relation between the preset network type and the request identifier according to the network type registered by the user terminal.
In a third aspect, there is provided a network registration apparatus configured in a user terminal, the network registration apparatus comprising:
The first sending module is used for sending a first network registration request carrying a first request identifier to the network equipment;
The first receiving module is used for receiving a first rejection registration response fed back by the network equipment; the first rejection registration response is a response triggered when the network equipment determines that the first request identification is abnormal;
the query module is used for querying the corresponding relation 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, a second network registration request carrying the second request identifier is sent to the network equipment.
In a fourth aspect, there is provided a network registration apparatus configured in a network device, the network registration apparatus comprising:
the first receiving module is used for receiving a first network registration request carrying a first request identifier sent by the user terminal;
the sending module is used for sending a first rejection registration response to the user terminal if the first request identification is determined to be abnormal;
The second receiving module is used for receiving a second network registration request carrying a second request identifier sent by the user terminal; the second request identifier is a request identifier corresponding to the network type registered by the user terminal, which is obtained by inquiring the corresponding relation between the preset network type and the request identifier according to the network type registered by the user terminal.
In a fifth aspect, there is provided a computer device comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, implements a network registration method as in any of the first and second aspects above.
In a sixth aspect, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements a network registration method as in any of the first and second aspects above.
The technical scheme provided by the embodiment of the application has the beneficial effects that at least:
The user terminal sends a first network registration request carrying a first request identifier to the network equipment, after receiving a first rejection registration response fed back by the network equipment, the user terminal inquires a corresponding relation between a preset network type and a request identifier according to the network type registered by the user terminal, and if a second request identifier corresponding to the network type registered by the user terminal is found, a second network registration request carrying a second request identifier is sent to the network equipment. That is, after the first network registration request is refused, the user terminal can also send a second network registration request to the network device, and the second request identifier carried by the second network registration request is preset, when the first request identifier set by the user terminal is wrong, the situation that the network cannot be used directly is avoided, and the user terminal is given more opportunities to perform network registration, so that the success rate of the user terminal for performing network registration is improved.
Drawings
FIG. 1 is a diagram of an application environment in accordance with an embodiment of the present application;
Fig. 2 is a flowchart of a network registration method according to an embodiment of the present application;
fig. 3 is a flowchart of a network registration method according to an embodiment of the present application;
FIG. 4 is a flowchart of a method for determining a second request identification according to an embodiment of the present application;
FIG. 5 is a flowchart of determining a correspondence between registered network types and request identifications according to an embodiment of the present application;
fig. 6 is a flowchart of a network registration method according to 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 present application;
fig. 8 is a flowchart of a network registration method according to an embodiment of the present application;
Fig. 9 is a flowchart of a network registration method according to an embodiment of the present application;
Fig. 10 is a block diagram of a network registration apparatus according to an embodiment of the present application;
fig. 11 is a block diagram of a network registration apparatus according to an embodiment of the present application;
fig. 12 is a block diagram of a network registration device according to an embodiment of the present application;
fig. 13 is a block diagram of a network registration device according to an embodiment of the present application;
fig. 14 is a block diagram of a network registration apparatus according to an embodiment of the present application;
Fig. 15 is a block diagram of a network registration apparatus according to an embodiment of the present application;
fig. 16 is a block diagram of a network registration apparatus according to an embodiment of the present application;
Fig. 17 is a block diagram of a user terminal according to an embodiment of the present application;
fig. 18 is a block diagram of a network device according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.
The network registration method provided by the application can be applied to an application environment shown in figure 1. Wherein the user terminal 102 communicates with the network device 104 via a 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.
In one embodiment, as shown in fig. 2, a network registration method is provided, and the method is applied to the user terminal in fig. 1 for illustration, and includes the following steps:
step 201, a first network registration request carrying a first request identifier is sent to a network device.
In the embodiment of the application, when the user terminal performs network registration, a first network registration request needs to be sent to the network equipment. The first network registration request carries a first request identifier.
Specifically, when the first request identifier is the identifier carried in the first network registration request during network registration of the user terminal. For example, in the 4G network, when the user terminal performs network registration, the first request identifier carried in the first network registration request is an APN identifier. Alternatively, the APN identifier may be set manually by the user, or the user terminal may obtain the APN identifier preset in the user terminal. In the 5G network, when the user terminal performs network registration, a first request identifier carried in a first network registration request is a DNN identifier. Alternatively, the DNN identifier may be set manually by the user, or the user terminal may obtain the DNN identifier preset in the user terminal.
Step 202, receiving a first rejection registration response fed back by the network equipment; the first reject registration response is a response triggered by the network device determining that the first request identification is abnormal.
When the first request identification is abnormal, the user terminal receives a first rejection registration response fed back by the network equipment, wherein the first rejection registration response is a response triggered when the network equipment determines that the first request identification is abnormal.
When the user terminal performs network registration, a first network registration request carrying a first request identifier is sent to network equipment, and when the server determines that an APN identifier or DNN identifier in the first network registration request is wrong, a first rejection registration response is fed back to the user terminal, so that the user terminal is informed of the network registration failure. Similarly, in the case that the user terminal obtains the APN identifier or the DNN identifier preset in the user terminal, the user terminal also receives the first rejection registration response fed back by the network device when the APN identifier or the DNN identifier preset in the user terminal is also wrong.
Step 203, according to the network type registered by the user terminal, inquiring a corresponding relation between the preset network type and the request identifier, and if a second request identifier corresponding to the network type registered by the user terminal is found, sending a second network registration request carrying the second request identifier to the network device.
Since different ues register with the first network, there is a network type corresponding to the first request identifier, where the network type is the network that the ue needs to register currently.
Under the condition that the user terminal receives a first rejection registration response fed back by the network equipment, the user terminal inquires a corresponding relation between a preset network type and a request identifier according to the network type, wherein the preset network type comprises a network type commonly used in practical application, the preset network type can comprise a network type registered by the user terminal, and the preset network type and the request identifier can be in 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 a second request identifier, and the user terminal sends a second network registration request carrying the second request identifier to the network equipment again.
The user terminal sends a first network registration request carrying a first request identifier to the network equipment, after receiving a first rejection registration response fed back by the network equipment, the user terminal inquires a corresponding relation between a preset network type and a request identifier according to the network type registered by the user terminal, and if a second request identifier corresponding to the network type registered by the user terminal is found, a second network registration request carrying a second request identifier is sent to the network equipment. That is, after the first network registration request is refused, the user terminal can also send a second network registration request to the network device, and the second request identifier carried by the second network registration request is preset, when the first request identifier set by the user terminal is wrong, the situation that the network cannot be used directly is avoided, and the user terminal can try to perform network registration for many times, so that the success rate of the network registration of the user terminal is improved.
In one embodiment, as shown in fig. 3, a network registration method is provided, and the method is applied to the user terminal in fig. 1 for illustration, and includes the following steps:
step 301, analyzing the first rejection registration response to obtain a first rejection reason.
The first reject registration response includes a first reject reason, that is, the first reject reason is packaged in a first reject registration response that the user terminal receives feedback from the network device, where the first reject reason may include parameter information of an abnormal first request identifier, and after the user terminal parses the first reject registration response, the user terminal may obtain the first reject reason, for example, after the user terminal may decompress the first reject registration response according to a Modem 4G protocol stack or a Modem 5G protocol stack, and perform a data processing operation, the user terminal obtains the first reject reason. The first reject cause is an abnormal cause of the first request identifier, and the first reject cause may be that the first request identifier parameter is lost or the first request identifier parameter cannot be identified.
Step 302, determining whether the first reject cause is consistent with a preset trigger cause.
The preset trigger reason is preset in the reject reason list, and the first reject reason may be included in the preset trigger reason, where the preset trigger reason may be that the first request identifier parameter is lost, the first request identifier parameter cannot be identified, or the first request identifier is not supported. Specifically, in the 4G network, the first request identifier parameter is lost or the first request identifier parameter cannot identify the corresponding preset trigger source as code 27 (Missing or unknown APN), and in the 5G network, the corresponding preset trigger source as code 91 (DNN not supported with no slice or IN SPECIFIC SLICE) is not supported.
Step 303, if the first reject cause is consistent with the preset trigger cause, executing the step of determining a second request identifier corresponding to the network type registered by the user terminal according to the corresponding relation among the network type registered by the user terminal, the preset network type and the request identifier.
If the first reject cause is consistent with the preset trigger cause, please refer to fig. 4, which shows a flowchart for determining a second request identifier corresponding to a network type registered by a user terminal according to an embodiment of the present application, the method may be applied to the user terminal. As shown in fig. 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 reject cause is consistent with the preset trigger cause, acquiring a request identification switch state.
Wherein the request identification switch state is used by the user terminal to determine whether the request identification can be acquired, and the request identification switch state can comprise a request identification switch on state and a request identification switch off state. Optionally, the request identification switch may be preset in the user terminal, and the user may also control the status of the request identification switch by clicking a trigger button.
In case the first reject cause is consistent with the preset trigger cause, i.e. in the 4G network the first reject cause is code 27 (Missing or unknown APN) and in the 5G network the first reject cause is code 91 (DNN not supported with no slice or IN SPECIFIC SLICE), the request identification switch state needs to be acquired.
Step 402, if the request identifier switch state is on, a step of determining a second request identifier corresponding to the network type registered by the user terminal according to the corresponding relationship among the network type registered by the user terminal, the preset network type and the request identifier is executed.
Wherein the request identifier switch state is an on state, that is, the user terminal can acquire the request identifier. Optionally, the user terminal may detect the switch state of the request identifier, and when detecting that the switch state of the request identifier is an on state, the user terminal may trigger an obtaining operation of the user terminal, so as to obtain the switch state of the request identifier.
When the user terminal judges that the first reject reason is consistent with the preset trigger reason, the request identification switch state is acquired, and when the request identification switch state is in an on state, the second request identification corresponding to the network type registered by the user terminal is determined according to the corresponding relation among the network type registered by the user terminal, the preset network type and the request identification, so that the situation that the user terminal still continuously tries to determine the second request identification corresponding to the network type registered by the user terminal when the request identification switch state is in an off state is avoided, the time for determining the second request identification corresponding to the network type registered by the user terminal is saved, and the network registration efficiency of the user terminal is improved. Further, the user can control the state of the request identifier switch 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 select whether to continue network registration after the first network registration request fails, so that the requirements of different users can be met, and more scenes are adapted.
The user terminal analyzes the first refusing registration response to obtain a first refusing reason, judges the first refusing reason and a preset triggering reason, and determines a second request identifier corresponding to the network type registered by the user terminal according to the corresponding relation among the network type registered by the user terminal, the preset network type and the request identifier under the condition that the first refusing reason is consistent with the preset triggering reason. Therefore, the first reject cause type can be rapidly and accurately positioned, so that the second network registration request can be timely sent to the network equipment, the time for network registration of the user terminal is saved, and the network registration efficiency is improved. And in this way, after the user terminal receives the first rejection registration response, the situation that the network cannot be used directly does not occur, after the user terminal obtains the first rejection reason by analyzing the first rejection registration response, the user terminal inquires the corresponding relation between the preset network type and the request identifier according to the network type registered by the user terminal, and sends a second network registration request carrying a second request identifier to the network equipment.
That is, after the first network registration request is refused, the user terminal can also send a second network registration request carrying a second request identifier to the network device, and the second request identifier carried by the second network registration request is preset, when the first request identifier set by the user terminal is wrong, the situation that the network cannot be used directly is avoided, and the user terminal can try to perform network registration for many times, so that the success rate of the user terminal for performing network registration is improved.
Referring to fig. 5, a flowchart of determining a correspondence between a registered network type and a request identifier is shown, where the method may be applied to a user terminal. As shown in fig. 5, the method of determining the correspondence between the registered network type and the request identifier may include the steps of:
step 501, obtaining an operator type corresponding to a SIM card of a user terminal.
Each SIM card corresponds to one 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 current SIM card used by the user terminal is SIM card 1, and the type of the operator acquired by the user terminal is A
Step 502, determining the network type registered by the user terminal according to the operator type, and establishing a corresponding relation between the network type registered by the user terminal and the request identifier.
Wherein the network type of the user terminal registration may be determined according to the operator type, and the network type of the user terminal registration may be one of public land mobile network (Public Land Mobile Network, PLMN) types. For example, the PLMN corresponding to the operator type a is D, the PLMN corresponding to the operator type B is E, and the PLMN corresponding to the operator type C is F. The operator type of the user terminal is a, and the network type PLMN registered by the user terminal is D.
The network types registered by the user terminal and the request identifiers are in one-to-one correspondence, for example, 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, and the request identifier corresponding to the network type F registered by the user terminal is F_NET.
In practical application, after the user terminal sends a second network registration request carrying a second request identifier to the network device, the situation that the registration is unsuccessful also occurs, that is, the situation that a second registration rejection response sent by the network device is received also occurs. Network registration method in this case referring to fig. 6, a flowchart of a network registration method provided by an embodiment of the present application is shown, and the method may be applied to a user terminal. As shown in fig. 6, the network registration method may include the steps of:
step 601, receiving a second rejection registration response sent by the network equipment; the second reject registration response is a response triggered by the network device determining that the second request identifies an anomaly.
The second network registration request carries a second request identifier, when the second request identifier is abnormal, the user terminal receives a second registration rejection response fed back by the network equipment, and the second registration rejection response is a response triggered when the network equipment determines that the second request identifier is abnormal.
Specifically, the second request identifier is a request identifier preset by the user terminal and corresponding to the network type, and after the user terminal obtains the second request identifier preset in the user terminal, the user terminal sends a second network registration request carrying the second request identifier to the network device. However, in practical application, the second request identifier preset in the user terminal is also wrong, or the preset correspondence between the network type and the second request identifier is wrong, and at this time, the second network registration request carries an abnormal second request identifier, and the user terminal also receives a second rejection registration response fed back by the network device, that is, the network registration fails.
Step 602, sending a third network registration request to the network device; the request identification in the third network registration request is null.
The third network registration request is a request carrying a NULL request identifier, where the NULL request identifier may be a parameter of the request identifier set to 0, and may also be a NULL APN or a NULL DNN. And under the condition that the user terminal receives a second rejection registration response fed back by the network equipment, the user terminal continuously sends a third network registration request carrying an empty request identifier to the network equipment. In this case, the network device may receive the third network registration request carrying the null request identifier according to the characteristics of the network protocol, and may feed back a default request identifier to the network device, that is, the network registration is successful.
When the second request identifier is abnormal, after receiving a second rejection registration response sent by the network equipment, the user terminal continuously sends a third network registration request carrying an empty request identifier to the network equipment, and network registration is performed again, so that the opportunity of network registration for the user terminal is increased, and the success rate of network registration of the user terminal can be improved.
In the case that the ue receives the second reject registration response sent by the network device, please refer to fig. 7, which shows a flowchart of sending a third network registration request to the network device according to an embodiment of the present application, the method may be applied to the ue. As shown in fig. 7, the method for transmitting the third network registration request to the network device may include the steps of:
and 701, analyzing the second rejection registration response to obtain a second rejection reason.
The second reject registration response includes a second reject cause, and the specific process of resolving the second reject registration response to obtain the second reject cause is similar to step 301, and is not described herein again.
Step 702, determining whether the second reject cause is consistent with the preset trigger cause.
The process of determining whether the second reject cause is consistent with the preset trigger cause is similar to step 302, and will not be described herein.
Step 703, if the second reject cause is consistent with the preset trigger cause, sending a third network registration request to the network device.
The user terminal analyzes the second refusing registration response to obtain a second refusing reason, judges the second refusing reason and a preset trigger reason, and sends a third network registration request to the network equipment under the condition that the second refusing reason is consistent with the preset trigger reason. Therefore, the second reject cause type can be rapidly and accurately positioned, so that the third network registration request can be timely sent to the network equipment, the time for network registration of the user terminal is saved, and the network registration efficiency is improved.
In one embodiment, as shown in fig. 8, a network registration method is provided, and the method is applied to the network device in fig. 8 for illustration, and includes the following steps:
step 801, a first network registration request carrying a first request identifier sent by a user terminal is received.
When the user terminal performs network registration, a first network registration request needs to be sent to the network device, and the network device receives 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, a first rejection registration response is sent to the user terminal.
When the first request identifier is abnormal, the network device feeds back a first rejection registration response to the user terminal, wherein the first rejection registration response is a response triggered when the network device determines that the first request identifier is abnormal.
Step 803, receiving a second network registration request carrying a second request identifier sent by the user terminal; the second request identifier is a request identifier corresponding to the network type registered by the user terminal, which is obtained by inquiring the corresponding relation between the preset network type and the request identifier according to the network type registered by the user terminal.
After sending a first network registration request carrying a first request identifier to a network device, if a first rejection registration response fed back by the network device is received, the user terminal inquires a corresponding relation between a preset network type and a request identifier according to the network type registered by the user terminal, if a second request identifier corresponding to the network type registered by the user terminal is found, a second network registration request carrying a second request identifier is sent to the network device, and the network device receives the second network registration request carrying the second request identifier sent by the user terminal.
That is, after the first network registration request is refused, the user terminal can also send a second network registration request to the network device, and the second request identifier carried by the second network registration request is preset, when the first request identifier set by the user terminal is wrong, the situation that the network cannot be used directly is avoided, and the user terminal is given more opportunities to perform network registration, so that the success rate of the user terminal for performing network registration is improved.
As shown in fig. 9, the embodiment of the present application further provides a network registration method, which includes the following steps:
step 901, a 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 rejection registration response.
Step 903, the ue receives a first rejection registration response fed back by the network device.
Step 904, the user terminal analyzes the first rejection registration response to obtain a first rejection reason.
In step 905, the user terminal determines whether the first reject cause is consistent with a preset trigger cause.
Step 906, if the first reject cause is consistent with the preset trigger cause, the user terminal obtains the request identifier switch state.
Step 907, the user terminal obtains 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 corresponding relationship between the network type registered by the user terminal and the request identifier.
If the request identifier switch state is on, the user terminal executes a step of determining a 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.
Step 910, the user terminal sends a second network registration request carrying a second request identifier to the network device.
Step 911, the network device feeds back a second reject registration response.
Step 912, the user terminal receives a second rejection registration response fed back by the network device.
Step 913, the user terminal analyzes the second rejection registration response to obtain a second rejection reason.
Step 914, the ue determines whether the second reject cause is consistent with the preset trigger cause.
In step 915, if the second reject cause is consistent with the preset trigger cause, the ue sends a third network registration request to the network device.
After the user terminal sends a first network registration request carrying a first request identifier to the network device, if a first rejection registration response fed back by the network device is received, according to the network type registered by the user terminal, inquiring the corresponding relation between the preset network type and the request identifier, and if a second request identifier corresponding to the network type registered by the user terminal is found, sending a second network registration request carrying a second request identifier to the network device. That is, after the first network registration request is refused, the user terminal can also send a second network registration request to the network device, and the second request identifier carried by the second network registration request is preset, when the first request identifier set by the user terminal is wrong, the situation that the network cannot be used directly is avoided, and the user terminal can try to perform network registration for many times, so that the success rate of the network registration of the user terminal is improved.
It should be understood that, although the steps in the flowcharts of fig. 2-9 are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least a portion of the steps of fig. 2-9 may include multiple steps or stages that are not necessarily performed at the same time, but may be performed at different times, nor does the order in which the steps or stages are performed necessarily occur sequentially, but may be performed alternately or alternately with at least a portion of the steps or stages in other steps or other steps.
Referring to fig. 10, a block diagram of a network registration apparatus 100 according to an embodiment of the present application is shown, where the network registration apparatus 100 may be configured in a user terminal. As shown in fig. 10, the network registration apparatus 100 may include a first transmitting module 101, a first receiving module 102, and a querying 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 rejection registration response fed back by the network device; the first reject registration response is a response triggered by the network device determining that the first request identification is abnormal.
The query module 103 is configured to query a corresponding relationship between a preset network type and a request identifier according to a network type registered by the user terminal, and if a second request identifier corresponding to the network type registered by the user terminal is found, send a second network registration request carrying the second request identifier to the network device.
In one embodiment, as shown in fig. 11, the first reject registration response includes a first reject cause; the device further comprises 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 rejection registration response to obtain a first rejection reason.
The first determining module 112 is configured to determine whether the first reject cause is consistent with a preset trigger cause.
The execution module 113 is configured to execute, if the first reject cause is consistent with the preset trigger cause, a step of determining a second request identifier corresponding to the network type registered by the user terminal according to a correspondence between the network type registered by the user terminal, the preset network type, and the request identifier.
In one embodiment, as shown in fig. 12, 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 reject cause is consistent with the preset trigger cause.
The execution unit 1132 is configured to 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 if the request identifier switch state is on.
In one embodiment, as shown in fig. 13, the apparatus further includes a second receiving module 131 and a second transmitting module 132;
The second receiving module 131 is configured to receive a second rejection registration response sent by the network device; the second reject registration response is a response triggered by the network device determining that the second request identifies an anomaly.
The second sending module 132 is configured to send a third network registration request to the network device; the request identification in the third network registration request is null.
In one embodiment, as shown in fig. 14, the second reject registration response includes a second reject cause; the device further comprises a second analysis module 141, a second judgment module 142 and a third sending module 143;
the second parsing module 141 is configured to parse the second rejection registration response to obtain a second rejection reason.
The second determining module 142 is configured to determine whether the second reject cause is consistent with the preset trigger cause.
The third sending module 143 is configured to send a third network registration request to the network device if the second reject cause is consistent with the preset trigger cause.
In one embodiment, as shown in fig. 15, the apparatus further includes an acquisition module 151 and a setup module 152;
the obtaining module 151 is configured to obtain an operator type corresponding to a SIM card of the user terminal.
The establishing module 152 is configured to determine a network type of the user terminal registration according to the operator type, and establish a correspondence between the network type of the user terminal registration and the request identifier.
Referring to fig. 16, a block diagram of a network registration device 160 according to an embodiment of the present application is shown, where the network registration device 160 may be configured in a network device. As shown in fig. 16, the network registration apparatus 160 may include a first receiving module 161, a transmitting module 162, and a second receiving module 163, wherein:
The first receiving module 161 is configured to receive a first network registration request carrying a first request identifier sent by a 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 a request identifier corresponding to the network type registered by the user terminal, which is obtained by inquiring the corresponding relation between the preset network type and the request identifier according to the network type registered by the user terminal.
The network registration device provided by the embodiment of the application can realize the embodiment of the method, and the implementation principle and the technical effect are similar, and are not repeated here.
The specific limitation of the network registration device may be referred to as limitation of the network registration method hereinabove, and will not be described herein. The above-described respective modules in the requesting network registration apparatus may be implemented in whole or in part by software, hardware, and a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may invoke and perform the operations of the above modules.
In one embodiment, a computer device is provided, which may be a user terminal, and the internal structure of which may be as shown in fig. 17. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a network registration method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, can also be keys, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by those skilled in the art that the structure shown in FIG. 17 is merely a block diagram of some of the structures associated with the present inventive arrangements and is not limiting of the computer device to which the present inventive arrangements may be applied, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.
In one embodiment of the present application, there is provided a computer device including a memory and a processor, the memory having stored therein a computer program which when executed by the processor performs the steps of:
Transmitting a first network registration request carrying a first request identifier to network equipment; receiving a first rejection registration response fed back by the network equipment; the first refusal registration response is a response triggered when the network equipment determines that the first request identification is abnormal; inquiring a corresponding relation between a preset network type and a request identifier according to the network type registered by the user terminal, and if a second request identifier corresponding to the network type registered by the user terminal is found, sending a second network registration request carrying the second request identifier to the network equipment.
In one embodiment of the application, the processor when executing the computer program further performs the steps of: analyzing the first rejection registration response to obtain a first rejection reason; judging whether the first reject cause is consistent with a preset trigger cause or not; and if the first reject cause is consistent with the preset trigger cause, executing the step of determining a second request identifier corresponding to the network type registered by the user terminal according to the corresponding relation among the network type registered by the user terminal, the preset network type and the request identifier.
In one embodiment of the application, the processor when executing the computer program further performs the steps of: if the first reject reason is consistent with the preset trigger reason, acquiring a request identification switch state; and if the request identification switch state is on, executing the step of determining a second request identification corresponding to the network type registered by the user terminal according to the corresponding relation among the network type registered by the user terminal, the preset network type and the request identification.
In one embodiment of the application, the processor when executing the computer program further performs the steps of: receiving a second rejection registration response sent by the network equipment; the second refusal registration response is a response triggered when the network equipment determines that the second request identification is abnormal; sending a third network registration request to the network device; the request identification in the third network registration request is null.
In one embodiment of the application, the processor when executing the computer program further performs the steps of: analyzing the second rejection registration response to obtain a second rejection reason; judging whether the second reject cause is consistent with a preset trigger cause or not; and if the second reject cause is consistent with the preset trigger cause, sending a third network registration request to the network equipment.
In one embodiment of the application, the processor when executing the computer program further performs the steps of: acquiring an operator type corresponding to a SIM card of a user terminal; and determining the network type registered by the user terminal according to the operator type, and establishing a corresponding relation between the network type registered by the user terminal and the request identifier.
The implementation principle and technical effects of the computer device provided by the embodiment of the present application are similar to those of the above method embodiment, and are not described herein.
In one embodiment, a computer device is provided, which may be a network device, and the internal structure of which may be as shown in fig. 18. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is used for network registration data. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a network registration method.
It will be appreciated by those skilled in the art that the structure shown in FIG. 18 is merely a block diagram of some of the structures associated with the present inventive arrangements and is not limiting of the computer device to which the present inventive arrangements may be applied, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.
In one embodiment of the present application, there is provided a computer device including a memory and a processor, the memory having stored therein a computer program which when executed by the processor performs the steps of:
Receiving a first network registration request carrying a first request identifier sent by a user terminal; if the first request identification is determined to be abnormal, a first rejection registration response is sent to the user terminal; receiving a second network registration request carrying a second request identifier sent by a user terminal; the second request identifier is a request identifier corresponding to the network type registered by the user terminal, which is obtained by inquiring the corresponding relation between the preset network type and the request identifier according to the network type registered by the user terminal.
The implementation principle and technical effects of the computer device provided by the embodiment of the present application are similar to those of the above method embodiment, and are not described herein.
In one embodiment of the present application, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of:
Transmitting a first network registration request carrying a first request identifier to network equipment; receiving a first rejection registration response fed back by the network equipment; the first refusal registration response is a response triggered when the network equipment determines that the first request identification is abnormal; inquiring a corresponding relation between a preset network type and a request identifier according to the network type registered by the user terminal, and if a second request identifier corresponding to the network type registered by the user terminal is found, sending a second network registration request carrying the second request identifier to the network equipment.
In one embodiment of the application, the computer program when executed by the processor further implements the steps of: analyzing the first rejection registration response to obtain a first rejection reason; judging whether the first reject cause is consistent with a preset trigger cause or not; and if the first reject cause is consistent with the preset trigger cause, executing the step of determining a second request identifier corresponding to the network type registered by the user terminal according to the corresponding relation among the network type registered by the user terminal, the preset network type and the request identifier.
In one embodiment of the application, the computer program when executed by the processor further implements the steps of: if the first reject reason is consistent with the preset trigger reason, acquiring a request identification switch state; and if the request identification switch state is on, executing the step of determining a second request identification corresponding to the network type registered by the user terminal according to the corresponding relation among the network type registered by the user terminal, the preset network type and the request identification.
In one embodiment of the application, the computer program when executed by the processor further implements the steps of: receiving a second rejection registration response sent by the network equipment; the second refusal registration response is a response triggered when the network equipment determines that the second request identification is abnormal; sending a third network registration request to the network device; the request identification in the third network registration request is null.
In one embodiment of the application, the computer program when executed by the processor further implements the steps of: analyzing the second rejection registration response to obtain a second rejection reason; judging whether the second reject cause is consistent with a preset trigger cause or not; and if the second reject cause is consistent with the preset trigger cause, sending a third network registration request to the network equipment.
In one embodiment of the application, the computer program when executed by the processor further implements the steps of: acquiring an operator type corresponding to a SIM card of a user terminal; and determining the network type registered by the user terminal according to the operator type, and establishing a corresponding relation between the network type registered by the user terminal and the request identifier.
The computer readable storage medium provided in this embodiment has similar principles and technical effects to those of the above method embodiment, and will not be described herein.
In one embodiment of the present application, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of:
Receiving a first network registration request carrying a first request identifier sent by a user terminal; if the first request identification is determined to be abnormal, a first rejection registration response is sent to the user terminal; receiving a second network registration request carrying a second request identifier sent by a user terminal; the second request identifier is a request identifier corresponding to the network type registered by the user terminal, which is obtained by inquiring the corresponding relation between the preset network type and the request identifier according to the network type registered by the user terminal.
The computer readable storage medium provided in this embodiment has similar principles and technical effects to those of the above method embodiment, and will not be described herein.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (SYNCHLINK) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The foregoing examples illustrate only a few embodiments of the application, which are described in detail and are not to be construed as limiting the scope of the claims. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of protection of the present application is to be determined by the appended claims.
Claims (10)
1. A method of network registration, the method comprising:
Transmitting a first network registration request carrying a first request identifier to network equipment; the first request identifier comprises a DNN identifier;
Receiving a first rejection registration response fed back by the network equipment; the first rejection registration response is a response triggered when the network equipment determines that the first request identification is abnormal; the first reject registration response includes a first reject cause;
analyzing the first refusal registration response to obtain the first refusal reason;
Judging whether the first reject cause is consistent with a preset trigger cause or not; the preset triggering reasons comprise that the first request identification parameters are lost, and the first request identification parameters cannot be identified or the first request identification is not supported;
If the first reject cause is consistent with the preset trigger cause, inquiring a corresponding relation between a preset network type and a request identifier according to the network type registered by the user terminal, and if a second request identifier corresponding to the network type registered by the user terminal is found, sending a second network registration request carrying the second request identifier to the network equipment; the preset network type and the request identifier are in one-to-one correspondence.
2. The method according to claim 1, wherein if the first reject cause is consistent with the preset trigger cause, the step of determining a second request identifier corresponding to the network type registered by the user terminal according to a correspondence between the network type registered by the user terminal, the preset network type, and the request identifier is performed, includes:
If the first reject reason is consistent with the preset trigger reason, acquiring a request identification switch state;
And if the request identification switch state is on, executing the step of determining a second request identification corresponding to the network type registered by the user terminal according to the corresponding relation among the network type registered by the user terminal, the preset network type and the request identification.
3. The method of claim 2, wherein the acquisition request identifies a switch state, comprising:
and detecting the switch state of the request identifier, and acquiring the switch state of the request identifier under the condition that the switch state of the request identifier is detected to be in an on state.
4. A method according to any one of claims 1-3, wherein the method further comprises:
Receiving a second rejection registration response sent by the network equipment; the second rejection registration response is a response triggered when the network equipment determines that the second request identification is abnormal;
sending a third network registration request to the network device; the request identification in the third network registration request is null.
5. The method of claim 4, wherein the second reject registration response comprises a second reject cause; the method further comprises the steps of:
analyzing the second refusal registration response to obtain the second refusal reason;
judging whether the second reject cause is consistent with a preset trigger cause or not;
And if the second reject cause is consistent with the preset trigger cause, sending a third network registration request to the network equipment.
6. A method according to any one of claims 1-3, wherein the method further comprises:
acquiring an operator type corresponding to the SIM card of the user terminal;
And determining the network type registered by the user terminal according to the operator type, and establishing a corresponding relation between the network type registered by the user terminal and the request identifier.
7. A method of network registration, the method comprising:
receiving a first network registration request carrying a first request identifier sent by a user terminal; the first request identifier comprises a DNN identifier;
if the first request identification is determined to be abnormal, a first rejection registration response is sent to the user terminal; the first reject registration response includes a first reject cause;
Receiving a second network registration request carrying a second request identifier sent by the user terminal; the second request identifier is a request identifier corresponding to the network type registered by the user terminal, which is obtained by analyzing the first rejection registration response to obtain the first rejection reason, judging whether the first rejection reason is consistent with a preset trigger reason, and if the first rejection reason is consistent with the preset trigger reason, inquiring the corresponding relation between the preset network type and the request identifier according to the network type registered by the user terminal; the preset network type and the request mark are in one-to-one correspondence; the preset triggering reasons comprise that the first request identification parameter is lost, the first request identification parameter cannot be identified or the first request identification is not supported.
8. A network registration apparatus, the apparatus comprising:
The first sending module is used for sending a first network registration request carrying a first request identifier to the network equipment; the first request identifier comprises a DNN identifier;
the first receiving module is used for receiving a first rejection registration response fed back by the network equipment; the first rejection registration response is a response triggered when the network equipment determines that the first request identification is abnormal; the first reject registration response includes a first reject cause;
The query module is used for analyzing the first rejection registration response to obtain the first rejection reason; judging whether the first reject cause is consistent with a preset trigger cause or not; the preset triggering reasons comprise that the first request identification parameters are lost, and the first request identification parameters cannot be identified or the first request identification is not supported; if the first reject cause is consistent with the preset trigger cause, inquiring a corresponding relation between a preset network type and a request identifier according to the network type registered by the user terminal, and if a second request identifier corresponding to the network type registered by the user terminal is found, sending a second network registration request carrying the second request identifier to the network equipment; the preset network type and the request identifier are in one-to-one correspondence.
9. A user terminal comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, implements the steps of the method according to any of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010965166.2A CN112261717B (en) | 2020-09-15 | 2020-09-15 | Network registration method, device, user terminal and storage medium |
| PCT/CN2021/107031 WO2022057429A1 (en) | 2020-09-15 | 2021-07-19 | Network registration method and apparatus, and user terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010965166.2A CN112261717B (en) | 2020-09-15 | 2020-09-15 | Network registration method, device, user terminal and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112261717A CN112261717A (en) | 2021-01-22 |
| CN112261717B true CN112261717B (en) | 2024-06-21 |
Family
ID=74232934
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010965166.2A Active CN112261717B (en) | 2020-09-15 | 2020-09-15 | Network registration method, device, user terminal and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112261717B (en) |
| WO (1) | WO2022057429A1 (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112261717B (en) * | 2020-09-15 | 2024-06-21 | 深圳市广和通无线股份有限公司 | Network registration method, device, user terminal and storage medium |
| CN113015265B (en) * | 2021-02-24 | 2023-07-18 | 西安广和通无线软件有限公司 | Network session self-healing method, device, system, computer equipment and storage medium |
| CN113194549B (en) * | 2021-03-22 | 2022-07-22 | 深圳市广和通无线股份有限公司 | Data connection method, device, terminal equipment and computer readable storage medium |
| CN114916056B (en) * | 2022-04-01 | 2024-06-14 | 西安广和通无线通信有限公司 | Data network name acquisition method, system, base station, terminal and storage medium |
| CN117319987A (en) * | 2022-06-23 | 2023-12-29 | 中兴通讯股份有限公司 | Method and device for limiting separation of machine and card, system, storage medium and electronic device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107948976A (en) * | 2017-12-01 | 2018-04-20 | 广东欧珀移动通信有限公司 | The detection method and device of LTE network access result, computer-readable storage medium |
| CN111065139A (en) * | 2019-12-31 | 2020-04-24 | 深圳市有方科技股份有限公司 | Method and device for starting up and attaching Internet of things device |
Family Cites Families (4)
| 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 |
| CN104955045B (en) * | 2015-06-12 | 2019-02-05 | 联想(北京)有限公司 | A kind of connection control method, device, terminal and system |
| CN107484239B (en) * | 2017-08-22 | 2020-12-25 | 奇酷互联网络科技（深圳）有限公司 | Network registration exception handling method and device and user terminal |
| CN112261717B (en) * | 2020-09-15 | 2024-06-21 | 深圳市广和通无线股份有限公司 | Network registration method, device, user terminal and storage medium |
-
2020
- 2020-09-15 CN CN202010965166.2A patent/CN112261717B/en active Active
-
2021
- 2021-07-19 WO PCT/CN2021/107031 patent/WO2022057429A1/en active Application Filing
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107948976A (en) * | 2017-12-01 | 2018-04-20 | 广东欧珀移动通信有限公司 | The detection method and device of LTE network access result, computer-readable storage medium |
| CN111065139A (en) * | 2019-12-31 | 2020-04-24 | 深圳市有方科技股份有限公司 | Method and device for starting up and attaching Internet of things device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112261717A (en) | 2021-01-22 |
| WO2022057429A1 (en) | 2022-03-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112261717B (en) | Network registration method, device, user terminal and storage medium | |
| US20220210757A1 (en) | Multi-card user equipment and communication method therefor, and network device | |
| CN110650516B (en) | Network distribution method and device, Internet of things equipment, terminal equipment and storage medium | |
| CN110809255B (en) | Card information activation method and device and storage medium | |
| CN106714206B (en) | Method and device for detecting wireless network access point connecting network | |
| EP3337219A1 (en) | Carrier configuration processing method, device and system, and computer storage medium | |
| CN111866850A (en) | Configuration file switching method and device, computer equipment and storage medium | |
| CN108282521B (en) | BIP protocol data transmission method and device, computer equipment and storage medium | |
| CN110475242B (en) | LTE network registration method, device, storage medium and computer equipment | |
| US9143963B2 (en) | Correlating radio link failure and minimization of drive test reports | |
| CN110636590B (en) | Hotspot list generation method and device, computer equipment and storage medium | |
| CN112469092A (en) | Multi-card mobile terminal optimal network selection method and device, computer equipment and storage medium | |
| CN114585002A (en) | Communication processing method, communication processing device, terminal equipment and computer readable storage medium | |
| CN110769482A (en) | Method and device for network connection of wireless equipment and wireless router equipment | |
| CN112804651B (en) | Binding method and device and computer equipment | |
| CN111328068B (en) | Card writing method and device, computer equipment and storage medium | |
| CN109951549B (en) | Network page access method and device and computer readable storage medium | |
| CN110704498A (en) | Data extraction method, device, equipment and computer readable storage medium | |
| CN114338132B (en) | Secret-free login method, client application, operator server and electronic equipment | |
| CN112769845B (en) | Vulnerability testing method and device, electronic device and computer equipment | |
| CN112423288B (en) | Dialing analysis method, device, computer equipment and storage medium | |
| CN114979072A (en) | Automatic dialing network access method, host, wireless module and terminal equipment | |
| CN113194521A (en) | 5G communication module network searching method and device, computer equipment and storage medium | |
| CN113242541B (en) | Network registration method and device, electronic equipment and storage medium | |
| CN113364842B (en) | Network data transmission method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |