CN113728682A

CN113728682A - Registration method and device

Info

Publication number: CN113728682A
Application number: CN202080012131.5A
Authority: CN
Inventors: 胡先鸽; 胡文; 杨林平; 陈功
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-03-26
Filing date: 2020-03-26
Publication date: 2021-11-30
Also published as: WO2021189389A1

Abstract

A registration method and a device are applied to the technical field of wireless communication, wherein the method comprises the following steps: when the terminal equipment determines that the length of the mobile network code MNC is invalid or cannot acquire the length of the MNC, the length of the MNC can be calibrated according to the PLMN information, so that the calibrated length of the MNC is determined; and the terminal equipment sends a first registration request message of the MNC with the calibrated length, so that the problem that the MNC cannot be registered in a network when the length of the MNC is invalid or the length of the MNC cannot be obtained is solved.

Description

Registration method and device

Technical Field

The present application relates to the field of wireless communications technologies, and in particular, to a registration method and apparatus.

Background

Currently, a terminal device needs to register with a mobile network before accessing the network. Currently, in the 5th generation (5G), the terminal device needs to send a Subscription identity (sui) carrying encryption during the registration process, so that the core network device authenticates the terminal device according to the sui. The SUCI includes a Home Network Identifier (Home Network Identifier), which is composed of a Mobile Country Code (MCC) and a Mobile Network Code (MNC). The length of the MCC is fixed, comprising 3 digits; the length of the MNC comprises 2 digits or 3 digits.

Before the terminal device sends the SUCI, the terminal device first reads basic File administration Data (EFAD) in the mobile phone card, and determines the length of the MNC through the EFAD. The terminal device reads a number of a corresponding length from an International Mobile Subscriber Identity (IMSI) as the MNC according to the length of the MNC. However, the EFAD may not exist in the handset card of the terminal device, or the length of the MNC indicated by the EFAD may be an invalid value, for example, the length of the MNC is 4, which may result in that the terminal device may not accurately determine the length of the MNC. If the terminal device cannot accurately determine the length of the MNC, the MNC read by the terminal device is the wrong MNC. Accordingly, the MNC carried by the terminal device in the SUCI may be in error, resulting in the registration of the terminal device being rejected by the network.

Disclosure of Invention

An object of the present invention is to provide a registration method and apparatus, so as to improve the registration success probability.

It should be understood that, in the solutions provided in the embodiments of the present application, the terminal device or the communication apparatus may be a stand-alone communication device, or may be a part of a device in the communication device, such as an integrated circuit product, such as a system chip or a communication chip. The wireless communication device may be a computer device that supports wireless communication functionality.

In particular, the terminal device may be a terminal such as a smartphone, or may be a radio access network device such as a base station. A system-on-chip may also be referred to as a system-on-chip (SoC), or simply as an SoC chip. The communication chip may include a baseband processing chip and a radio frequency processing chip. The baseband processing chip is sometimes also referred to as a modem (modem) or baseband chip. The rf processing chip is also sometimes referred to as a radio frequency transceiver (transceiver) or rf chip. In a physical implementation, part of the communication chip or all of the communication chip may be integrated inside the SoC chip. For example, the baseband processing chip is integrated in the SoC chip, and the radio frequency processing chip is not integrated with the SoC chip.

In a first aspect, a method is provided, comprising: when terminal equipment determines that the length of a mobile network code MNC is invalid or the length of the MNC cannot be obtained, determining the length of the MNC after the MNC is calibrated; the calibrated length is determined according to Public Land Mobile Network (PLMN) information; the terminal equipment sends a first registration request message, wherein the first registration request message is used for requesting registration in a network; the first registration request message includes the MNC of the calibrated length.

By the method, when the terminal equipment determines that the length of the mobile network code MNC is invalid or cannot acquire the length of the MNC, the length of the MNC can be calibrated according to the PLMN information, so that the calibrated length of the MNC is determined, and the problem that the MNC cannot be registered in a network when the length of the MNC is invalid or cannot be acquired is solved.

In an optional implementation manner, the determining, by the terminal device, that the length of the mobile network code MNC is invalid includes: and the terminal equipment determines that the length of the MNC indicated by the basic file management data EFAD is an invalid value, and determines that the length of the MNC cannot be acquired is invalid.

In an optional implementation manner, the determining, by the terminal device, that the length of the MNC cannot be acquired includes: and when the terminal equipment determines that the terminal equipment does not comprise the EFAD, determining that the length of the MNC cannot be acquired.

In an optional implementation manner, the calibrated length is a length of an MNC included in the PLMN information.

In an optional implementation manner, when a value of the third bit of the MNC in the PLMN information is F, the calibrated length is 2.

In an optional implementation manner, when a value of the third bit of the MNC in the PLMN information is any one of 0 to 9, the calibrated length is 3.

In an optional implementation manner, the PLMN information is matched with an international mobile subscriber identity IMSI in the terminal device.

In an optional implementation manner, the PLMN information is obtained by a system broadcast message.

In an optional implementation manner, the PLMN information is a registered public land mobile network RPLMN, or the PLMN information is an equivalent public land mobile network EPLMN.

In an alternative implementation, the MNC is located in an encrypted subscription identity SUCI in the first registration message.

In a second aspect, there is also provided a method comprising: when terminal equipment determines that the length of a mobile network code MNC is invalid or the length of the MNC cannot be obtained, sending a second registration request message, wherein the second registration request message comprises the MNC with the first length; the first length is equal to 2 or 3; if the terminal equipment receives a registration rejection message responding to the second registration request message, sending a third registration request message, wherein the third registration request message comprises the MNC with a second length; the second length is equal to 2 or 3, and the third length is different from the second length.

In an alternative implementation, the first length is a preconfigured length; or, the first length is a length randomly selected by the terminal device.

In a third aspect, the present application further provides a communication device having a function of implementing any one of the methods provided in the first or second aspects. The communication device may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units or units corresponding to the above functions.

In one possible implementation, the communication device includes: a processor configured to enable the communication apparatus to perform the respective functions of the terminal device in the above-illustrated method. The communication device may also include a memory, which may be coupled to the processor, that retains program instructions and data necessary for the communication device.

Optionally, the communication apparatus further comprises an interface circuit, which is configured to support communication between the communication apparatus and a device such as a network device.

In one possible implementation, the communication device comprises corresponding functional units, each for implementing the steps in the above method. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

In a possible implementation manner, the structure of the communication device includes a processing unit and a communication unit, and these units may perform corresponding functions in the above method example, specifically refer to the description in the method provided in the third aspect, and are not described herein again.

In a fourth aspect, there is also provided a communication apparatus, including: a processor and a memory;

wherein the memory is to store program instructions;

the processor is configured to execute the program instructions stored in the memory to cause the communication device to implement the method of any of the above possible designs.

In a fifth aspect, the present application provides a communication device, which may include: a storage unit for storing program instructions; a processing unit for executing the program instructions in the storage unit to implement the method in any one of the possible designs of the aforementioned technical solutions.

The storage unit may be a memory, such as a volatile memory, for caching the program instructions, and the program instructions may be loaded into the storage unit from other nonvolatile memories when the data scheduling method is executed. Of course, the memory unit may also be a non-volatile memory, also integrated inside the chip. The processing unit may be a processor, e.g. one or more processing cores of a chip.

In a sixth aspect, the present application provides a computer-readable storage medium having computer-readable instructions stored thereon that, when read and executed by a computer, cause the communication device to perform the method of any one of the above possible designs.

In a seventh aspect, the present application provides a computer program product, which when read and executed by a computer, causes the communication device to perform the method of any one of the above possible designs.

In an eighth aspect, the present application provides a chip, which is connected to a memory and is configured to read and execute a software program stored in the memory to implement the method in any one of the above possible designs.

Drawings

Fig. 1 is a schematic flowchart of a registration method according to an embodiment of the present application;

fig. 2 is a schematic diagram illustrating a MNC length calibration process according to an embodiment of the present disclosure;

fig. 3 is a schematic flowchart of a registration method according to an embodiment of the present application;

fig. 4 is a schematic flowchart of a registration method according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a communication device according to an embodiment of the present application.

Detailed Description

Embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: the New Radio (NR) in the 5th Generation (5G) system may also be applied to a Long Term Evolution (LTE) system, and the like, without limitation.

In a 2G/3G/4G network, when a terminal device is registered, the IMSI may be reported to a core network device, where the reported IMSI is plaintext information that is not encrypted. The length of the MNC is 2 or 3 bits in the IMSI, and the core network device may try to match the length of the MNC of 2 bits or the length of the MNC of 3 bits, so as to determine an accurate MNC.

For example, the IMSI reported by the terminal device is: 002011912121001. the core network device may consider that there are two possibilities for sequences corresponding to MCC and MNC, which are 00201 and 002011 respectively, and the core network device tries to route and query the subscription information corresponding to the IMSI by using 00201 and 002011 respectively, and if one of the queries is successful, it may consider that the corresponding sequence is the accurate MCC and MNC.

However, in the 5G network, the terminal device reports SUCI at registration, SUCI is a format encrypted by Subscription Permanent identity (SUPI), and SUPI in 5G is IMSI at present. Wherein the SUCI encrypts only the information in the SUPI except for the MCC and MNC.

After receiving the SUCI, the core network device, for example, a SEcurity Anchor Function (SEAF), needs to use MCC and MNC in the SUCI as a routing selection to determine a corresponding Unified Data Management (UDM) network element and a Subscription Identity Decryption Function (SIDF) network element. The SEAF sends the SUCI to the corresponding UDM and SIDF for decryption. If the MCC and MNC carried by the terminal device are not of the same length, the SEAF network element cannot be correctly routed to the corresponding UDM network element and SIDF network element for decryption, so that the identity of the terminal device cannot be identified, and the registration of the terminal device in the network fails.

For example, there are two PLMNs in the real network, PLMNs 1: 310014, where MCC is 310 and MNC is 014; PLMN 2: 310015, wherein the MCC is 310 and the MNC is 015. If the MNC reported by the terminal device is 01, the SEAF obtains that the MCC is 310 and the MNC is 01, and does not know whether the SUCI is sent to the UDM and SIDF corresponding to the MNC of 014 for decryption or sent to the UDM and SIDF corresponding to the MNC of 015 for decryption.

Therefore, the method provided by the embodiment of the application can calibrate the MNC when the length of the MNC cannot be determined, so that the terminal device sends the MNC with the accurate length, and thereby successful registration on the network is realized.

In this embodiment, the terminal device may be a device having a wireless transceiving function or a chip that can be disposed in any device, and may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment. The terminal device in the embodiment of the present application may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal, an Augmented Reality (AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote medical treatment (remote medical), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), and the like.

With reference to the foregoing description, as shown in fig. 1, a flowchart of a registration method provided in an embodiment of the present application is shown. Referring to fig. 1, the method includes:

step 101: and when the terminal equipment determines that the length of the MNC is invalid or cannot acquire the length of the MNC, determining the length of the MNC after calibration.

In a possible implementation manner, if the terminal device determines that the length of the MNC indicated by the EFAD is an invalid value, it may determine that the length of the MNC cannot be obtained.

For example, when the length of the MNC indicated by the EFAD is a value other than a valid value, it may be determined that the length of the MNC is invalid. For example, currently the length of the MNC is valid for 2 or 3, and if the length of the MNC indicated by EFAD is 4, the length of the MNC indicated by EFAD is invalid.

In another possible implementation manner, when the terminal device determines that the terminal device does not include the EFAD, it determines that the length of the MNC cannot be acquired. The terminal device does not include the EFAD, which may mean that the subscriber identity module card in the terminal device does not include the EFAD.

It should be noted that the EFAD is generally stored in a Subscriber Identity Module (SIM) card, which may be a Subscriber Identity Module (SIM) card, a Universal Subscriber Identity Module (USIM), an Embedded Subscriber Identity Module (eSIM) card, or the like, and the Subscriber Identity Module may be integrated with a terminal device, belong to a part of the terminal device, or be a chip card independent from the terminal device. The user identification card is a chip or a virtual electronic card which is issued by an operator and used for storing contract signing information of the operator and providing processes such as identity, authentication and the like during registration.

Further, when the terminal device determines that the length of the MNC is invalid or cannot acquire the length of the MNC, the length of the MNC may be calibrated, and specifically, the calibrated length of the MNC may be determined according to PLMN information, where the PLMN information is matched with the IMSI in the terminal device.

The IMSI may be used to identify the identity of the Mobile Subscriber, and may include information such as an MCC, an MNC, and a Mobile Subscriber Identity Number (MSIN). Although the MCC and the MNC are included in the IMSI, the terminal device cannot accurately read the MNC without determining the length of the MNC.

In the embodiment of the present application, specifically, how to calibrate the length of the MNC, reference may be made to a process shown in fig. 2:

step 201: acquiring PLMN information;

specifically, how to obtain the PLMN information is not limited in the embodiment of the present application. For example, the PLMN information may be a PLMN preconfigured in the terminal device; the PLMN information may be a PLMN acquired by the terminal device through a system broadcast message.

The PLMN information may also be a Non-volatile Data Memory (NV) of the terminal device or a Registered PLMN (Registered PLMN, RPLMN) stored in the subscriber identity card; the PLMN information may also be NV of the terminal device or an Equivalent PLMN (Equivalent PLMN, EPLMN) stored in the subscriber identity card.

The above is only an example, and the PLMN information may also be obtained by other manners, which are not illustrated herein one by one.

It should be noted that the PLMN is an identifier of an operator, and includes MCC and MNC therein. The RPLMN is used for indicating the PLMN when the terminal equipment is successfully registered last time, can be stored in NV and a user identification card of the terminal equipment, and can be conveniently and quickly registered in the original network when the terminal equipment is registered next time. EPLMN, when an operator has a plurality of PLMNs, the terminal equipment can move in the network corresponding to the plurality of PLMNs and enjoy equal charging strategies, after the terminal equipment is successfully registered in the network, the network is configured to the plurality of PLMNs of the terminal equipment, and the plurality of PLMNs are equivalent to each other.

Step 202: and acquiring the MCC and the MNC from the PLMN information.

It should be noted that the terminal device can read the MCC and the MNC from the PLMN information, and mainly performs the determination according to the value of the last bit of the MNC. Taking PLMN information as PLMN as an example, in the PLMN, the length stored by the MNC is 3 bits, and if the 3 rd bit of the MNC in the PLMN is F and the value of the 3 rd bit is an invalid value, the MNC with the length of 2 can be obtained from the PLMN information; if the 3 rd bit of the MNC in the PLMN is any value from 0 to 9, and the value of the 3 rd bit is a valid value, the MNC with the length of 3 can be acquired from the PLMN information.

Step 203: and reading a number sequence with a specified length in the IMSI in the terminal equipment, wherein the specified length is the sum of the lengths of the MCC and the MNC in the PLMN information.

For example, the IMSI is: 002011912121001. since the length of the MNC cannot be determined, the MCC and MNC in the IMSI may be 00201 or 002011. Assuming that the MCC and MNC obtained from the PLMN information are 00201, the specified length may be determined to be 5, so that the first 5 digits may be read from the IMSI, i.e., 00201.

Assuming that the MCC and MNC obtained from the PLMN information are 002011, it can be determined that the specified length is 6, and thus the first 6 digits can be read from the IMSI, that is, 002011 is read as the MCC and MNC.

It should be noted that, in the foregoing example, the description is given by taking as an example that the number sequence read from the IMSI is the same as the MCC and MNC acquired from the PLMN information, and in practical applications, if the acquired PLMN information is wrong, the obtained PLMN information may not be the same.

Step 204: and judging whether the number sequence with the specified length in the IMSI is the same as the MCC and the MNC in the PLMN information, if so, turning to the step 205, otherwise, turning to the step 206.

Step 205: the number sequence of the specified length in the IMSI is the same as the MCC and MNC in the PLMN information, it can be determined that the PLMN information matches the IMSI, and the length of the MNC in the PLMN information is taken as the length after MNC calibration.

Specifically, if the last bit of the MNC in the PLMN is F, it may be determined that the MNC calibrated length is 2; if the last bit of the MNC in the PLMN is any of 0 to 9, it can be determined that the MNC calibrated length is 3.

When determining the SUCI, the terminal device may determine the MNC from the IMSI according to the calibrated length.

Step 206: if the sequence of digits of the specified length in the IMSI is not the same as the MCC and MNC in the PLMN information, it may be determined that the PLMN information does not match the IMSI, and the length of the MNC may not be calibrated.

At this time, the terminal device may use the preconfigured length as the length of the MNC, or may randomly select one of the lengths 2 and 3 as the length of the MNC.

After the terminal device calibrates the length of the MNC, the MNC with the calibrated length may be used to initiate a registration request, which may specifically refer to step 102.

Step 102: the terminal equipment sends a first registration request message, wherein the first registration request message is used for requesting registration in the network.

The first registration request message may include a SUCI, in which the MNC of the calibrated length may be included.

The first registration request message may be a registration request message (registration request) in the 5G NR, or may be a registration request message in other types of networks.

The above process is described in detail below by way of specific examples.

Fig. 3 is a schematic flow chart of a process for calibrating the MNC length according to an embodiment of the present disclosure.

Step 301: the terminal device acquires the EFAD.

The terminal device may read the EFAD from a SIM card or the like.

Step 302: whether the length of MNC indicated by EFAD is valid, if not, go to step 303; if so, go to step 308.

It should be noted that, if the terminal device does not acquire the EFAD, step 303 may be directly executed.

Step 303: if the NV of the terminal equipment stores the PLMN, judging whether the PLMN can be matched with the IMSI in the terminal equipment, and if not, turning to step 304; if there is a match, then go to step 309.

Note that, the PLMN stored in the NV may be a PLMN used when the terminal device is last registered in the network.

Step 304: if the terminal equipment has a pre-configured PLMN, judging whether the PLMN can be matched with the IMSI in the terminal equipment, and if not, turning to step 305; if there is a match, go to step 308.

Step 305: if NV in the terminal equipment or the user identification card has RPLMN or EPLMN, judging whether the RPLMN or EPLMN can be matched with IMSI in the terminal equipment, if not, going to step 306; if there is a match, go to step 308.

Step 306: acquiring a PLMN through a system broadcast message, judging whether the PLMN can be matched with the IMSI in the terminal equipment, and if not, turning to step 307; if there is a match, go to step 308.

It should be noted that the system broadcast message herein may refer to a system broadcast message in an NR network.

Further, if there is no NR network currently, the terminal device may not be able to acquire the system broadcast message in the NR network at this time. In this case, the terminal device may search for the 2G/3G/4G network, then register in the 2G/3G/4G network, and obtain the EPLMN delivered by the 2G/3G/4G network, and at this time, the terminal device may match the obtained EPLMN with the IMSI. And when the matching is successful, the length of the MNC can be calibrated by adopting the EPLMN issued by the 2G/3G/4G network and the RPLMN registered in the 2G/3G/4G network.

Step 307: the default length configured in the terminal device is taken as the length of the MNC.

Alternatively, the terminal device may randomly select one of 2 or 3 as the length of the MNC.

Step 308: and calibrating the length of the MNC to obtain the calibrated length of the MNC.

The specific calibration process may refer to the flow shown in fig. 2.

Step 309: MNC is determined from the length of the EFAD indication.

The order of step 303 to step 306 is not limited, and other execution orders may exist.

As can be seen from the foregoing procedure, when the method provided in this embodiment is not used, the terminal device can only use the default MNC length in the SUCI in the registration request message sent by the air interface, and the MNC length is not accurate at this time. If the default MNC length is not consistent with the actual MNC length, an error occurs, which may cause an error in the MCC and MNC carried in the SUCI. For example, the IMSI in the terminal device is 002011912121001, and the actual PLMN is 00201. If the default MNC length is 3, the MCC and MNC carried by the SUCI in the registration request message are 002011, which results in that the network issues registration rejection during registration, resulting in that the terminal device cannot successfully register.

By the method provided by the embodiment of the application, the terminal equipment can calibrate the length of the MNC from the acquired PLMN information if the length of the MNC is invalid or the length of the MNC cannot be determined. For example, the IMSI is 002011912121001, the actual PLMN is 00201, the MCC and MNC carried by the SUCI in the registration request message are 00201, the core network device can correctly route according to the MCC and MNC carried by the SUCI, and the terminal device can successfully register.

Further, an embodiment of the present application further provides a method, specifically, as shown in fig. 4, the method includes:

step 401: and when the terminal equipment determines that the length of the MNC is invalid or cannot acquire the length of the MNC, sending a second registration request message.

The second registration request message includes the MNC of a first length.

The first length is a preconfigured length, or the first length is a length randomly selected by the terminal device. It should be noted that, currently, the MNC has a length of 2 or 3, and thus the first length is equal to 2 or 3.

How the terminal device determines that the length of the MNC is invalid may refer to the description in step 201, and is not described herein again.

It should be noted that the terminal device may send the second registration request message to the network device, and the network device may be, for example, an SEAF, or may be another network device, which is not described herein again.

Optionally, step 402: and if the terminal equipment receives the registration rejection message responding to the second registration request message, sending a third registration request message.

The third registration request message comprises the MNC of a second length; the third length is different from the second length.

For example, if the first length is equal to 2, then the second length is equal to 3; the first length is equal to 3, the second length is equal to 2.

The terminal device may determine that the length of the MNC is the first length if the terminal device receives a registration accept message in response to the second registration request message.

The terminal device may determine that the length of the MNC is the third length if the terminal device receives a registration accept message in response to the third registration request message.

Further, when the terminal device determines that the registration is successful, the MNC length used when the registration is successful may be stored, and when the terminal device registers next time, the MNC length is used for registration.

By the method, the terminal equipment can try to register by adopting different MNC lengths for a plurality of times, so that the situation that the terminal equipment cannot register when the MNC length cannot be determined is avoided.

The various embodiments described herein may be implemented as stand-alone solutions or combined in accordance with inherent logic and are intended to fall within the scope of the present application.

It is to be understood that, in the above-described method embodiments, the method and operations implemented by the terminal device may also be implemented by a component (e.g., a chip or a circuit) that can be used for the terminal device.

In the embodiments provided in the present application, the method provided in the embodiments of the present application is introduced from the perspective of interaction between the devices. In order to implement the functions in the method provided by the embodiment of the present application, the terminal device and the network device may include a hardware structure and/or a software module, and the functions are implemented in the form of a hardware structure, a software module, or a hardware structure and a software module. Whether any of the above-described functions is implemented as a hardware structure, a software module, or a hardware structure plus a software module depends upon the particular application and design constraints imposed on the technical solution.

The division of the modules in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. In addition, functional modules in the embodiments of the present application may be integrated into one processor, may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode.

Similar to the above concept, as shown in fig. 5, an apparatus 500 is further provided in the present embodiment to implement the functions of the terminal device in the above method. The device may be a software module or a system-on-a-chip, for example. In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip and other discrete devices. The apparatus 500 may comprise: a processing unit 501 and a communication unit 502.

In this embodiment of the present application, the communication unit may also be referred to as a transceiver unit, and may include a transmitting unit and/or a receiving unit, which are respectively configured to perform the steps of transmitting and receiving by the terminal device in the foregoing method embodiments.

Hereinafter, the communication device according to the embodiment of the present application will be described in detail with reference to fig. 5 to 6. It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments, and therefore, for brevity, details are not repeated here, since the details that are not described in detail may be referred to the above method embodiments.

In one possible design, the apparatus 500 may implement the steps or the flow executed by the terminal device corresponding to the above method embodiment, which is described below separately.

Illustratively, when the apparatus 500 implements the functions of the terminal device in the flow shown in fig. 2:

a processing unit 501, configured to determine a length of a mobile network code MNC after calibration when the length of the MNC is invalid or the length of the MNC cannot be obtained; the calibrated length is determined according to Public Land Mobile Network (PLMN) information;

a communication unit 502, configured to send a first registration request message, where the first registration request message is used to request registration in a network;

the first registration request message includes the MNC of the calibrated length.

In an alternative implementation manner, the processing unit 501 is configured to:

and determining that the length of the MNC indicated by the basic file management data EFAD is an invalid value, and determining that the length of the MNC cannot be acquired is invalid.

and when determining that the terminal equipment does not include the EFAD, determining that the length of the MNC cannot be acquired.

Illustratively, when the apparatus 500 implements the functions of the terminal device in the flow shown in fig. 4:

a processing unit 501, configured to send a second registration request message through a communication unit 502 when it is determined that the length of a mobile network code MNC is invalid or the length of the MNC cannot be obtained, where the second registration request message includes the MNC with a first length; the first length is equal to 2 or 3;

the communication unit 502 is configured to send a third registration request message if a registration reject message responding to the second registration request message is received, where the third registration request message includes the MNC with the second length; the second length is equal to 2 or 3, and the third length is different from the second length.

As shown in fig. 6, which is a device 600 provided in the embodiment of the present application, the device shown in fig. 6 may be implemented as a hardware circuit of the device shown in fig. 5. The communication device can be applied to the flow chart shown in fig. 2, and performs the functions of the terminal device in the above method embodiment. For ease of illustration, fig. 6 shows only the main components of the communication device.

The apparatus 600 shown in fig. 6 includes at least one processor 620 for implementing any of the methods of fig. 2 provided by the embodiments of the present application.

The apparatus 600 may also include at least one memory 630 for storing program instructions and/or data. The memory 630 is coupled to the processor 620. The coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, and may be an electrical, mechanical or other form for information interaction between the devices, units or modules. The processor 620 may operate in conjunction with the memory 630. Processor 620 may execute program instructions stored in memory 630. At least one of the at least one memory may be included in the processor.

In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The steps of the method disclosed in connection with the embodiments of the present application may be embodied as hardware processor, or may be implemented as a combination of hardware and software modules in a processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor. To avoid repetition, it is not described in detail here.

It should be noted that the processor in the embodiments of the present application may be an integrated circuit chip having signal processing capability. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The processor may be a general purpose processor, a Digital Signal Processing (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied as being performed by a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, Synchronous Link DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

The apparatus 600 may also include an interface circuit 610 for communicating with other devices over a transmission medium so that the apparatus used in the apparatus 600 may communicate with other devices. In embodiments of the present application, the interface circuit may be a transceiver, a circuit, a bus, a module, or other type of interface circuit. In the embodiment of the present application, when the interface circuit is a transceiver, the transceiver may include an independent receiver and an independent transmitter; a transceiver that integrates transceiving functions, or an interface circuit may be used.

The apparatus 600 may also include communication lines 640. Wherein the interface circuit 610, the processor 620, and the memory 630 may be connected to each other through a communication line 640; the communication line 640 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication line 640 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 6, but this is not intended to represent only one bus or type of bus.

Illustratively, when the apparatus 600 implements the functions of the terminal device in the flow shown in fig. 2:

a processor 620, configured to determine a length of a mobile network code MNC after calibration when it is determined that the length of the MNC is invalid or the length of the MNC cannot be obtained; the calibrated length is determined according to Public Land Mobile Network (PLMN) information;

an interface circuit 610, configured to send a first registration request message, where the first registration request message is used to request registration in a network;

In an alternative implementation, the processor 620 is configured to:

Illustratively, when the apparatus 600 implements the functions of the terminal device in the flow shown in fig. 4:

a processor 620, configured to send a second registration request message through an interface circuit 610 when it is determined that the length of a mobile network code MNC is invalid or the length of the MNC cannot be obtained, where the second registration request message includes the MNC with a first length; the first length is equal to 2 or 3;

the interface circuit 610 is configured to send a third registration request message if a registration reject message responding to the second registration request message is received, where the third registration request message includes the MNC with the second length; the second length is equal to 2 or 3, and the third length is different from the second length.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

A registration method, comprising:

when terminal equipment determines that the length of a mobile network code MNC is invalid or the length of the MNC cannot be obtained, determining the length of the MNC after the MNC is calibrated; the calibrated length is determined according to Public Land Mobile Network (PLMN) information;

the terminal equipment sends a first registration request message, wherein the first registration request message is used for requesting registration in a network;

the first registration request message includes the MNC of the calibrated length.
The method according to claim 1, wherein the terminal device determines that the length of the mobile network code MNC is invalid, comprising:

and the terminal equipment determines that the length of the MNC indicated by the basic file management data EFAD is an invalid value, and determines that the length of the MNC cannot be acquired is invalid.
The method of claim 1, wherein the determining, by the terminal device, that the length of the MNC cannot be obtained comprises:

and when the terminal equipment determines that the terminal equipment does not comprise the EFAD, determining that the length of the MNC cannot be acquired.
A method according to any of claims 1 to 3, wherein the calibrated length is the length of the MNC included in the PLMN information.
The method of claim 4, wherein the calibrated length is 2 when the value of the third bit of the MNC in the PLMN information is F.
The method of claim 4, wherein the calibrated length is 3 when a value of a third bit of the MNC in the PLMN information is any one of 0 to 9.
The method according to any of claims 1 to 6, characterized in that the PLMN information matches an international mobile subscriber identity, IMSI, in the terminal device.
The method according to any one of claims 1 to 7, wherein the PLMN information is a PLMN obtained through a system broadcast message.
The method according to any of claims 1 to 7, wherein the PLMN information is a registered public land mobile network, RPLMN, or wherein the PLMN information is an equivalent public land mobile network, EPLMN.
Method according to any of claims 1 to 9, wherein said MNC is located in an encrypted subscription identity SUCI in said first registration message.
A registration method, comprising:

when terminal equipment determines that the length of a mobile network code MNC is invalid or the length of the MNC cannot be obtained, sending a second registration request message, wherein the second registration request message comprises the MNC with the first length; the first length is equal to 2 or 3;

if the terminal equipment receives a registration rejection message responding to the second registration request message, sending a third registration request message, wherein the third registration request message comprises the MNC with a second length; the second length is equal to 2 or 3, and the third length is different from the second length.
The method of claim 11, wherein the first length is a preconfigured length;

or, the first length is a length randomly selected by the terminal device.
A communications apparatus, comprising:

the device comprises a processing unit and a processing unit, wherein the processing unit is used for determining the length of a mobile network code MNC after the MNC is calibrated when the length of the MNC is invalid or the length of the MNC cannot be obtained; the calibrated length is determined according to Public Land Mobile Network (PLMN) information;

a communication unit configured to transmit a first registration request message, the first registration request message being used to request registration in a network; the first registration request message includes the MNC of the calibrated length.
The apparatus according to claim 13, wherein the processing unit is specifically configured to:

and determining that the length of the MNC indicated by the basic file management data EFAD is an invalid value, and determining that the length of the MNC cannot be acquired is invalid.
The apparatus according to claim 13, wherein the processing unit is specifically configured to:

and when determining that the terminal equipment does not include the EFAD, determining that the length of the MNC cannot be acquired.
The apparatus according to any of claims 13 to 15, wherein the calibrated length is a length of an MNC included in the PLMN information.
The apparatus of claim 16, wherein when a value of a third bit of the MNC in the PLMN information is F, the calibrated length is 2.
The apparatus of claim 16, wherein the calibrated length is 3 when a value of a third bit of the MNC in the PLMN information is any one of 0 to 9.
The arrangement according to any of the claims 13-18, characterized in that said PLMN information is matched to the international mobile subscriber identity IMSI in the terminal equipment.
The apparatus according to any of claims 13 to 19, wherein the PLMN information is a PLMN obtained through system broadcast message.
The apparatus according to any of claims 13 to 19, wherein the PLMN information is a registered public land mobile network, RPLMN, or wherein the PLMN information is an equivalent public land mobile network, EPLMN.
The arrangement according to any of claims 13 to 21, wherein said MNC is located in an encrypted subscription identity SUCI in said first registration message.
A communications apparatus, comprising:

the mobile network terminal comprises a processing unit and a communication unit, wherein the processing unit is used for sending a second registration request message through the communication unit when the length of a mobile network code MNC is determined to be invalid or the length of the MNC cannot be obtained, and the second registration request message comprises the MNC with the first length; the first length is equal to 2 or 3;

the communication unit is configured to send a third registration request message if a registration reject message responding to the second registration request message is received, where the third registration request message includes the MNC of the second length; the second length is equal to 2 or 3, and the third length is different from the second length.
The apparatus of claim 23, wherein the first length is a preconfigured length;

or, the first length is a length randomly selected by the terminal device.
A communications apparatus, comprising: a processor and an interface circuit;

wherein the interface circuit is configured to access a memory having stored therein program instructions;

the processor is configured to access the memory through the interface circuit and execute program instructions stored in the memory to cause the communication device to implement the method of any of claims 1-12.
A computer-readable storage medium, characterized in that a program code is stored in the computer-readable storage medium, which program code, when executed by a computer, implements the method of any of claims 1 to 12.
A computer program product comprising program code means for performing the method of any one of claims 1 to 12 when said program code means is executed by a computer.