WO2021189389A1 - 一种注册方法及装置 - Google Patents

一种注册方法及装置 Download PDF

Info

Publication number
WO2021189389A1
WO2021189389A1 PCT/CN2020/081518 CN2020081518W WO2021189389A1 WO 2021189389 A1 WO2021189389 A1 WO 2021189389A1 CN 2020081518 W CN2020081518 W CN 2020081518W WO 2021189389 A1 WO2021189389 A1 WO 2021189389A1
Authority
WO
WIPO (PCT)
Prior art keywords
length
mnc
terminal device
request message
registration request
Prior art date
Application number
PCT/CN2020/081518
Other languages
English (en)
French (fr)
Inventor
胡先鸽
胡文
杨林平
陈功
Original Assignee
华为技术有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN202080012131.5A priority Critical patent/CN113728682A/zh
Priority to PCT/CN2020/081518 priority patent/WO2021189389A1/zh
Publication of WO2021189389A1 publication Critical patent/WO2021189389A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices

Definitions

  • This application relates to the field of wireless communication technology, and in particular to a registration method and device.
  • the terminal device needs to be registered in the network before accessing the mobile network.
  • the terminal device needs to send an encrypted subscription identity (Subscription Concealed Identifier, SUCI) during the registration process, so that the core network device can authenticate the terminal device according to the SUCI.
  • the SUCI includes a home network identifier (Home Network Identifier), which is composed of a mobile country code (Mobile Country Code, MCC) and a mobile network code (Mobile Network Code, MNC).
  • Home Network Identifier Home Network Identifier
  • MCC mobile country code
  • MNC Mobile Network Code
  • the terminal device Before the terminal device sends the SUCI, the terminal device first reads the elementary file administrative data (EFAD) in the mobile phone card, and determines the length of the MNC through EFAD. According to the length of the MNC, the terminal device reads the number of the corresponding length from the international mobile subscriber identity (IMSI) as the MNC.
  • the EFAD may not exist in the mobile phone card of the terminal device, or the length of the MNC indicated by the EFAD may be an invalid value.
  • the length of the indicated MNC is 4, which will cause the terminal device to be unable to accurately determine the length of the MNC.
  • the MNC read by the terminal device is the wrong MNC.
  • the MNC carried by the terminal device in the SUCI will have an error, causing the registration of the terminal device to be rejected by the network.
  • the purpose of the embodiments of the present application is to provide a registration method and device to improve the probability of successful registration.
  • the terminal device or the communication device may be an independent communication device, or may be a part of the communication device, such as integrated circuit products such as a system chip or a communication chip.
  • the wireless communication device may be a computer device that supports wireless communication functions.
  • the terminal device may be a terminal such as a smart phone, or a wireless access network device such as a base station.
  • the system chip may also be referred to as a system on chip (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 called a modem or baseband chip.
  • the radio frequency processing chip is sometimes called a radio frequency transceiver (transceiver) or radio frequency chip.
  • part or all of the chips in the communication chip can be integrated inside the SoC chip.
  • the baseband processing chip is integrated in the SoC chip, and the radio frequency processing chip is not integrated with the SoC chip.
  • a method which includes: when the terminal device determines that the length of the mobile network code MNC is invalid or the length of the MNC cannot be obtained, determining the calibrated length of the MNC; the calibrated length is based on The public land mobile network PLMN information is determined; the terminal device sends a first registration request message, the first registration request message is used to request registration in the network; the first registration request message includes the calibrated length The MNC.
  • the length of the MNC can be calibrated according to the PLMN information to determine the calibrated length of the MNC, thereby realizing the solution
  • the length of the MNC is invalid or the length of the MNC cannot be obtained, the problem cannot be registered in the network.
  • the terminal device determining that the length of the mobile network code MNC is invalid includes: the terminal device determines that the length of the MNC indicated by the basic file management data EFAD is an invalid value, and then determining that it cannot be obtained The length of the MNC is invalid.
  • the terminal device determining that the length of the MNC cannot be obtained includes: when the terminal device determines that the terminal device does not include EFAD, determining that the length of the MNC cannot be obtained.
  • the calibrated length is the length of the MNC included in the PLMN information.
  • the calibrated length is 2.
  • the calibrated length is 3.
  • the PLMN information matches the international mobile subscriber identity IMSI in the terminal device.
  • the PLMN information is a PLMN obtained through a system broadcast message.
  • the PLMN information is a registered public land mobile network RPLMN, or the PLMN information is an equivalent public land mobile network EPLMN.
  • the MNC is located in the encrypted subscription identity SUCI in the first registration message.
  • a method including: when the terminal device determines that the length of the mobile network code MNC is invalid or the length of the MNC cannot be obtained, sending a second registration request message, the second registration request message including the first The length of the MNC; the first length is equal to 2 or 3; if the terminal device receives a registration rejection message in response to the second registration request message, it sends a third registration request message, the third registration request The message includes the MNC of a second length; the second length is equal to 2 or 3, and the third length is different from the second length.
  • the first length is a pre-configured length; or, the first length is a length randomly selected by the terminal device.
  • the present application also provides a communication device, the communication device having any method provided in the first aspect or the second aspect.
  • the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or units corresponding to the above-mentioned functions.
  • the communication device includes: a processor configured to support the communication device to perform corresponding functions of the terminal device in the method shown above.
  • the communication device may further include a memory, and the storage may be coupled with the processor, which stores program instructions and data necessary for the communication device.
  • the communication device further includes an interface circuit for supporting communication between the communication device and equipment such as network equipment.
  • the communication device includes corresponding functional units, which are respectively used to implement the steps in the above method.
  • the function can be realized by hardware, or the corresponding software can be executed by hardware.
  • the hardware or software includes one or more units corresponding to the above-mentioned functions.
  • the structure of the communication device includes a processing unit and a communication unit, and these units can perform corresponding functions in the foregoing method examples.
  • these units can perform corresponding functions in the foregoing method examples.
  • a communication device including: a processor and a memory;
  • the memory is used to store program instructions
  • the processor is configured to execute program instructions stored in the memory, so that the communication device implements any of the above-mentioned possible design methods.
  • 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 aforementioned various technical solutions Any of the possible design methods.
  • the storage unit may be a memory, such as a volatile memory, for caching these program instructions. These program instructions may be loaded into the storage unit from other non-volatile memories when the data scheduling method is running. Of course, the storage unit may also be a non-volatile memory, which is also integrated inside the chip.
  • the processing unit may be a processor, such as one or more processing cores of a chip.
  • the present application provides a computer-readable storage medium in which computer-readable instructions are stored.
  • the communication device is caused to execute any of the above Possible design methods.
  • this application provides a computer program product, which when a computer reads and executes the computer program product, causes the communication device to execute any of the above-mentioned possible design methods.
  • the present application provides a chip, which is connected to a memory, and is used to read and execute a software program stored in the memory, so as to implement any of the above-mentioned possible design methods.
  • FIG. 1 is a schematic flowchart of a registration method provided by an embodiment of the application
  • FIG. 2 is a schematic diagram of an MNC length calibration process provided by an embodiment of the application.
  • FIG. 3 is a schematic flowchart of a registration method provided by an embodiment of the application.
  • FIG. 4 is a schematic flowchart of a registration method provided by an embodiment of the application.
  • FIG. 5 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • FIG. 6 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • NR New Radio
  • 5G 5th Generation
  • LTE Long Term Evolution
  • a terminal device when a terminal device registers, it can report an IMSI to the core network device, and the reported IMSI is plaintext information without encryption.
  • the IMSI includes an MNC with a length of 2 or 3 digits.
  • the core network equipment can try to match the length of the MNC with a length of 2 digits or a MNC with a length of 3 digits to determine an accurate MNC.
  • the IMSI reported by the terminal device is: 002011912121001.
  • the core network equipment can think that there are two possibilities for the sequence corresponding to MCC and MNC, which are 002 01 and 002 011 respectively.
  • the core network equipment uses 002 01 and 002 011 to try to route and query the subscription information corresponding to the IMSI. If one of the queries is successful, It can be considered that the corresponding sequence is accurate MCC and MNC.
  • the terminal device reports the SUCI when registering, and the SUCI is a subscription permanent identity (Subscription Permanent Identifier, SUPI) encrypted format.
  • SUPI Subscribe Permanent Identifier
  • the SUPI in 5G is the IMSI.
  • SUCI only encrypts information except MCC and MNC in SUPI.
  • SEcurity Anchor Function After the core network equipment, such as the SEcurity Anchor Function (SEAF) receives the SUCI, it needs to use the MCC and MNC in the SUCI as routing selection to determine the corresponding Unified Data Management (UDM) network element, Subscription Identity De-concealing Function (Subscription Identifier De-concealing Function, SIDF) network element. SEAF sends SUCI to its corresponding UDM and SIDF for decryption. If the lengths of the MCC and MNC carried by the terminal device are incorrect, the SEAF network element cannot be correctly routed to the corresponding UDM network element and SIDF network element for decryption, and the identity of the terminal device cannot be recognized, resulting in the failure of the terminal device to register on the network.
  • UDM Unified Data Management
  • SIDF Subscribescription Identifier De-concealing Function
  • PLMN1 310 014, where MCC is 310 and MNC is 014; PLMN2: 310 015, where MCC is 310 and MNC is 015.
  • MNC reported by the terminal device is 01
  • SEAF obtains that the MCC is 310 and the MNC is 01
  • SEAF does not know whether to send SUCI to the UDM and SIDF corresponding to MNC 014 for decryption, or to send it to the MNC corresponding to 015 Decryption in UDM and SIDF.
  • the embodiments of the present application provide a method that can calibrate the MNC when the length of the MNC cannot be determined, so that the terminal device sends an MNC of an accurate length, thereby achieving successful registration on the network.
  • the terminal device may be a device with a wireless transceiver function or a chip that can be installed in any device, and may also be referred to as user equipment (UE), access terminal, Subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user device.
  • UE user equipment
  • the terminal equipment in the embodiments of the present application may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, an industrial Wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, transportation safety Wireless terminals in the smart city (smart city), wireless terminals in the smart home (smart home), etc.
  • FIG. 1 it is a schematic flowchart of a registration method provided by an embodiment of this application.
  • the method includes:
  • Step 101 When the terminal device determines that the length of the MNC is invalid or cannot obtain the length of the MNC, it determines the calibrated length of the MNC.
  • the terminal device determines that the length of the MNC indicated by the EFAD is an invalid value, it can be determined that the length of the MNC cannot be obtained as invalid.
  • the length of the MNC indicated by EFAD is a value other than the valid value, it can be determined that the length of the MNC is invalid.
  • the current effective value of the length of the MNC is 2 or 3. If the length of the MNC indicated by EFAD is 4, the length of the MNC indicated by EFAD is invalid.
  • the terminal device determines that the terminal device does not include EFAD, it determines that the length of the MNC cannot be obtained.
  • the terminal device does not include EFAD, which may mean that the user identification card in the terminal device does not include EFAD.
  • EFAD is generally stored in a subscriber identity card.
  • the subscriber identity card can refer to a Subscriber Identity Module (SIM) card, or a Universal Subscriber Identity Module (USIM), or embedded Subscriber Identity Module (Embedded Subscriber Identity Module, eSIM) card, etc.
  • SIM Subscriber Identity Module
  • USIM Universal Subscriber Identity Module
  • eSIM embedded Subscriber Identity Module
  • the subscriber identity card can be integrated with the terminal device, is a part of the terminal device, or can be a chip card independent of the terminal device, which is not limited in this embodiment of the application .
  • the user identification card is a chip or virtual electronic card issued by the operator that stores the operator's contract information and provides processes such as identity and authentication during registration.
  • the length of the MNC may be calibrated. Specifically, the length of the calibrated MNC may be determined according to the PLMN information, wherein the PLMN The information matches the IMSI in the terminal device.
  • the IMSI can be used to identify the identity of a mobile user, and can include information such as MCC, MNC, and mobile subscriber identification number (Mobile Subscriber Identification Number, MSIN). Although the IMSI includes MCC and MNC, the terminal device cannot accurately read the MNC when the length of the MNC is uncertain.
  • Step 201 Obtain PLMN information
  • the PLMN information may be a PLMN pre-configured in the terminal device; the PLMN information may be a PLMN acquired by the terminal device through a system broadcast message.
  • the PLMN information can also be a non-volatile data memory (Non-volatile Data Memory, NV) of the terminal device or a registered PLMN (Registered PLMN, RPLMN) stored in a subscriber identification card; the PLMN information can also be The NV of the terminal device or the equivalent PLMN (Equivalent PLMN, EPLMN) stored in the subscriber identification card.
  • NV Non-volatile Data Memory
  • PLMN information can also be obtained in other ways, which will not be described one by one here.
  • PLMN is an operator's logo, which contains MCC and MNC.
  • RPLMN is used to indicate the PLMN when the terminal device was successfully registered last time, and it can be stored in the NV and subscriber identification card of the terminal device, which can facilitate rapid registration on the original network during the next registration.
  • EPLMN when an operator has multiple PLMNs, terminal equipment can move in the network corresponding to these multiple PLMNs and enjoy the same charging policy. After the terminal equipment is successfully registered in the network, the network will configure multiple PLMNs for the terminal equipment. These multiple PLMNs are equivalent to each other.
  • Step 202 Obtain MCC and MNC from the PLMN information.
  • the terminal device can read the MCC and MNC from the PLMN information, mainly based on the value of the last bit of the MNC to make judgments.
  • the PLMN information as PLMN as an example
  • the length of MNC saved is 3 bits. If the third bit of MNC in PLMN is F and the value of the third bit is an invalid value, the length can be obtained from the PLMN information as The MNC of 2; if the third bit of the MNC in the PLMN is any value from 0 to 9, and the value of the third bit is a valid value, the MNC of length 3 can be obtained from the PLMN information.
  • Step 203 Read the digit sequence of the designated length in the IMSI in the terminal device, and the designated length is the sum of the length of the MCC and the MNC in the PLMN information.
  • the IMSI is: 002011912121001. Since the length of the MNC cannot be determined, the MCC and MNC in the IMSI can be 002 01 or 002 011. Assuming that the MCC and MNC obtained from the PLMN information are 002 01, it can be determined that the specified length is 5, so that the first 5 digits can be read from the IMSI, that is, 002 01.
  • the specified length can be determined to be 6, so that the first 6 digits can be read from the IMSI, that is, 002 011 is read as the MCC and MNC.
  • the number sequence read from the IMSI is the same as the MCC and MNC obtained from the PLMN information. In actual applications, if the obtained PLMN information is wrong, It may not be the same.
  • Step 204 Determine whether the digit sequence of the specified length in the IMSI is the same as the MCC and MNC in the PLMN information, if they are the same, go to step 205, otherwise go to step 206.
  • Step 205 The digit 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 MNC calibrated length.
  • the MNC calibration can be determined The length of the back is 3.
  • the terminal device determines the SUCI, it can determine the MNC from the IMSI according to the calibrated length.
  • Step 206 The digit sequence of the specified length in the IMSI is not the same as the MCC and MNC in the PLMN information, it can 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 can use the pre-configured length as the length of the MNC, or randomly select one of 2 and 3 as the length of the MNC.
  • the terminal device After the terminal device calibrates the length of the MNC, it can use the calibrated length of the MNC to initiate a registration request. For details, refer to step 102.
  • Step 102 The terminal device sends a first registration request message, where the first registration request message is used to request registration in the network.
  • the first registration request message may include SUCI, and SUCI may include the MNC of the calibrated length.
  • the first registration request message may be a registration request message in 5G NR, or a registration request message in other types of networks.
  • FIG. 3 it is a schematic diagram of a process of calibrating the length of an MNC provided by an embodiment of this application.
  • Step 301 The terminal device obtains the EFAD.
  • the terminal device can read the EFAD from the SIM card, etc.
  • Step 302 Whether the length of the MNC indicated by EFAD is valid, if it is invalid, go to step 303; if it is valid, go to step 308.
  • step 303 may be directly executed.
  • Step 303 If a PLMN is stored in the NV of the terminal device, determine whether the PLMN can match the IMSI in the terminal device, if it does not match, go to step 304; if it matches, go to step 309.
  • the PLMN stored in the NV may refer to the PLMN used when the terminal device was registered in the network last time.
  • Step 304 If there is a pre-configured PLMN in the terminal device, judge whether the PLMN can match the IMSI in the terminal device, if it does not match, go to step 305; if it matches, go to step 308.
  • Step 305 If there is an RPLMN or EPLMN in the NV in the terminal device or the subscriber identification card, determine whether the RPLMN or EPLMN can match the IMSI in the terminal device, if it does not match, go to step 306; if it matches, go to step 308.
  • Step 306 Obtain the PLMN through the system broadcast message, then determine whether the PLMN can match the IMSI in the terminal device, if it does not match, go to step 307; if it matches, go to step 308.
  • system broadcast message here may refer to the system broadcast message in the NR network.
  • the terminal device may not be able to obtain the system broadcast message in the NR network at this time.
  • the terminal device can search for the 2G/3G/4G network, and then register in the 2G/3G/4G network to obtain the EPLMN issued by the 2G/3G/4G network.
  • the terminal device can compare the obtained EPLMN with IMSI matches.
  • the EPLMN issued by the 2G/3G/4G network and the RPLMN registered in the 2G/3G/4G network can be used to calibrate the length of the MNC.
  • Step 307 Use the default length configured in the terminal device as the length of the MNC.
  • the terminal device can also randomly select one from 2 or 3 as the length of the MNC.
  • Step 308 Calibrate the length of the MNC to obtain the calibrated length of the MNC.
  • the specific calibration process can refer to the process shown in Figure 2.
  • Step 309 Determine the MNC according to the length indicated by the EFAD.
  • step 303 to step 306 is not limited, and other execution orders may also exist.
  • 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 inconsistent with the actual MNC length, an error will occur, which will cause the MCC and MNC errors carried in the SUCI.
  • the IMSI in the terminal device is 002011912121001, and the actual PLMN is 002 01. If the default MNC length is 3, the MCC and MNC carried in the SUCI in the registration request message are 002 011, which results in a registration rejection issued by the network during registration, and the terminal device cannot successfully register.
  • the terminal device can calibrate the MNC length from the acquired PLMN information. For example, if the IMSI is 002011912121001 and the actual PLMN is 002 01, then the MCC and MNC carried in the SUCI in the registration request message are 002 01. The core network device can correctly route according to the MCC and MNC carried in the SUCI, and the terminal device can register successfully. .
  • the embodiment of the present application also provides a method. Specifically, as shown in FIG. 4, the method includes:
  • Step 401 When determining that the length of the MNC is invalid or the length of the MNC cannot be obtained, the terminal device sends a second registration request message.
  • the second registration request message includes the MNC of the first length.
  • the first length is a pre-configured length, or the first length is a length randomly selected by the terminal device. It should be noted that the current length of the MNC is 2 or 3, so the first length is equal to 2 or 3.
  • step 201 For how the terminal device determines that the length of the MNC is invalid, reference may be made to the description in step 201, which will not be repeated here.
  • the terminal device may send a second registration request message to the network device, and the network device may be, for example, a SEAF or other network devices, which will not be repeated here.
  • step 402 if the terminal device receives a registration rejection message in response to the second registration request message, it sends a third registration request message.
  • the third registration request message includes the MNC of a second length; the third length is different from the second length.
  • the second length is equal to 3; if 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.
  • the terminal device may determine that the length of the MNC is the third length.
  • the terminal device when the terminal device determines that the registration is successful, it can also store the MNC length used when the registration is successful, and when registering next time, the MNC length is used for registration.
  • the terminal device can try to register with different MNC lengths multiple times, so as to avoid the situation that it cannot register when the MNC length cannot be determined.
  • the methods and operations implemented by the terminal device may also be implemented by components (for example, a chip or a circuit) that can be used for the terminal device.
  • the terminal device and the network device may include a hardware structure and/or software module, and the above functions are implemented in the form of a hardware structure, a software module, or a hardware structure plus a software module. . Whether a certain function among the above-mentioned functions is executed by a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraint conditions of the technical solution.
  • the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • the functional modules in the various embodiments of the present application may be integrated in one processor, or may exist alone physically, or two or more modules may be integrated in one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software function modules.
  • an embodiment of the present application further provides an apparatus 500 for implementing the function of the terminal device in the above-mentioned method.
  • the device may be a software module or a chip system.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the apparatus 500 may include: a processing unit 501 and a communication unit 502.
  • the communication unit may also be referred to as a transceiving unit, and may include a sending unit and/or a receiving unit, which are respectively configured to perform the sending and receiving steps of the terminal device in the above method embodiment.
  • the apparatus 500 can implement the steps or processes executed by the terminal device corresponding to the above method embodiments, which will be described separately below.
  • the processing unit 501 is configured to determine the calibrated length of the MNC when the length of the mobile network code MNC is invalid or the length of the MNC cannot be obtained; the calibrated length is determined according to the public land mobile network PLMN information ;
  • the communication unit 502 is configured to send a first registration request message, where the first registration request message is used to request registration in the network;
  • the first registration request message includes the MNC of the calibrated length.
  • the processing unit 501 is configured to:
  • the processing unit 501 is configured to:
  • the terminal device does not include EFAD, it is determined that the length of the MNC cannot be obtained.
  • the calibrated length is the length of the MNC included in the PLMN information.
  • the calibrated length is 2.
  • the calibrated length is 3.
  • the PLMN information matches the international mobile subscriber identity IMSI in the terminal device.
  • the PLMN information is a PLMN obtained through a system broadcast message.
  • the PLMN information is a registered public land mobile network RPLMN, or the PLMN information is an equivalent public land mobile network EPLMN.
  • the MNC is located in the encrypted subscription identity SUCI in the first registration message.
  • the processing unit 501 is configured to send a second registration request message through the communication unit 502 when the length of the mobile network code MNC is invalid or the length of the MNC cannot be obtained, and the second registration request message includes the first length of the MNC; 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 rejection message in response 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 first length is a pre-configured length; or, the first length is a length randomly selected by the terminal device.
  • FIG. 6 shows a device 600 provided by an embodiment of the application.
  • the device shown in FIG. 6 may be a hardware circuit implementation of the device shown in FIG. 5.
  • the communication device can be applied to the flowchart shown in FIG. 2 to perform the functions of the terminal device in the foregoing method embodiment.
  • FIG. 6 only shows the main components of the communication device.
  • the apparatus 600 shown in FIG. 6 includes at least one processor 620, configured to implement any method in FIG. 2 provided in the embodiment of the present application.
  • the device 600 may also include at least one memory 630 for storing program instructions and/or data.
  • the memory 630 and the processor 620 are coupled.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 620 may cooperate with the memory 630 to operate.
  • the processor 620 may execute program instructions stored in the memory 630. At least one of the at least one memory may be included in the processor.
  • each step of the above method can be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software.
  • the steps of the method disclosed in combination with the embodiments of the present application may be embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.
  • the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments may be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processing circuit (digital signal processor, DSP), a dedicated integrated circuit (application specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processing circuit
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • Programming logic devices discrete gates or transistor logic devices, discrete hardware components.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • static random access memory static random access memory
  • dynamic RAM dynamic RAM
  • DRAM dynamic random access memory
  • synchronous dynamic random access memory synchronous DRAM, SDRAM
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory serial DRAM, SLDRAM
  • direct rambus RAM direct rambus RAM
  • the apparatus 600 may further include an interface circuit 610 for communicating with other devices through a transmission medium, so that the apparatus used in the apparatus 600 can communicate with other devices.
  • the interface circuit may be a transceiver, circuit, bus, module, or other type of interface circuit.
  • the transceiver when the interface circuit is a transceiver, the transceiver may include an independent receiver and an independent transmitter; it may also be a transceiver with integrated transceiver functions, or an interface circuit.
  • the device 600 may also include a communication line 640.
  • 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 or an extended industry standard architecture (extended industry standard architecture) , Referred to as EISA) bus and so on.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the communication line 640 can be divided into an address bus, a data bus, a control bus, and so on. For ease of representation, only one thick line is used in FIG. 6, but it does not mean that there is only one bus or one type of bus.
  • the processor 620 is configured to determine the calibrated length of the MNC when the length of the mobile network code MNC is invalid or the length of the MNC cannot be obtained; the calibrated length is determined according to the public land mobile network PLMN information ;
  • the interface circuit 610 is configured to send a first registration request message, where the first registration request message is used to request registration in the network;
  • the first registration request message includes the MNC of the calibrated length.
  • the processor 620 is configured to:
  • the processor 620 is configured to:
  • the terminal device does not include EFAD, it is determined that the length of the MNC cannot be obtained.
  • the calibrated length is the length of the MNC included in the PLMN information.
  • the calibrated length is 2.
  • the calibrated length is 3.
  • the PLMN information matches the international mobile subscriber identity IMSI in the terminal device.
  • the PLMN information is a PLMN obtained through a system broadcast message.
  • the PLMN information is a registered public land mobile network RPLMN, or the PLMN information is an equivalent public land mobile network EPLMN.
  • the MNC is located in the encrypted subscription identity SUCI in the first registration message.
  • the processor 620 is configured to: when determining that the length of the mobile network code MNC is invalid or the length of the MNC cannot be obtained, send a second registration request message through the interface circuit 610, where the second registration request message includes the first length of the MNC; 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 rejection message in response 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 first length is a pre-configured length; or, the first length is a length randomly selected by the terminal device.
  • this application can be provided as methods, systems, or computer program products. Therefore, this application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) containing computer-usable program codes.
  • a computer-usable storage media including but not limited to disk storage, optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种注册方法及装置，应用于无线通信技术领域，其中方法包括：终端设备确定移动网络码MNC的长度无效或者无法获取到所述MNC的长度时，可以根据PLMN信息对MNC的长度进行校准，从而确定所述MNC校准后的长度；所述终端设备发送包括所述校准后的长度的所述MNC的第一注册请求消息，从而实现解决了MNC的长度无效或者无法获取到MNC长度时，无法在网络中注册的问题。

Description

一种注册方法及装置 技术领域
本申请涉及无线通信技术领域，特别涉及一种注册方法及装置。
背景技术
目前，终端设备在接入移动网络之前，需要在网络中进行注册。目前，在第5代移动通信(the 5th generation，5G)中，终端设备在注册过程中需要发送携带加密的签约身份(Subscription Concealed Identifier，SUCI)，以便核心网设备根据SUCI对终端设备进行认证。其中SUCI中包括归属网络标识(Home Network Identifier)，是由移动国家码(Mobile Country Code，MCC)和移动网络码(Mobile Network Code，MNC)来组成。MCC的长度是固定的，包括3位数字；MNC的长度包括2位数字或者3位数字。
终端设备在发送SUCI之前，终端设备先读取手机卡中的基本文件管理数据(Elementary File Administrative Data，EFAD)，通过EFAD确定MNC的长度。终端设备根据MNC的长度，从国际移动用户识别码(international mobile subscriber identity，IMSI)中读取相应长度的数字作为MNC。然而，终端设备的手机卡中可能不存在EFAD，或者EFAD指示的MNC的长度可能是无效值，例如指示MNC的长度为4，这样就会导致终端设备无法准确的确定MNC的长度。如果终端设备无法准确的确定MNC的长度，那么终端设备读取到的MNC就是错误的MNC。相应的，终端设备在SUCI中携带的MNC就会出现错误，导致终端设备的注册被网络拒绝。
发明内容
本申请实施方式的目的在于提供一种注册方法及装置，用以提升注册成功概率的问题。
应理解，本申请实施例提供的方案中，终端设备或通信装置可以是独立的通信设备，也可以是通信设备中的部分器件，如系统芯片或通信芯片等集成电路产品。无线通信设备可以是支持无线通信功能的计算机设备。
具体地，终端设备可以是诸如智能手机这样的终端，也可以是诸如基站这样的无线接入网设备。系统芯片也可称为片上系统(system on chip，SoC)，或简称为SoC芯片。通信芯片可包括基带处理芯片和射频处理芯片。基带处理芯片有时也被称为调制解调器(modem)或基带芯片。射频处理芯片有时也被称为射频收发机(transceiver)或射频芯片。在物理实现中，通信芯片中的部分芯片或者全部芯片可集成在SoC芯片内部。例如，基带处理芯片集成在SoC芯片中，射频处理芯片不与SoC芯片集成。
第一方面，提供了一种方法，包括：终端设备确定移动网络码MNC的长度无效或者无法获取到所述MNC的长度时，确定所述MNC校准后的长度；所述校准后的长度是根据公共陆地移动网络PLMN信息确定的；所述终端设备发送第一注册请求消息，所述第一注册请求消息用于请求在网络中注册；所述第一注册请求消息包括所述校准后的长度的所述MNC。
通过上面的方法，终端设备确定移动网络码MNC的长度无效或者无法获取到所述 MNC的长度时，可以根据PLMN信息对MNC的长度进行校准，从而确定所述MNC校准后的长度，从而实现解决了MNC的长度无效或者无法获取到MNC长度时，无法在网络中注册问题。
一种可选的实现方式中，所述终端设备确定移动网络码MNC的长度无效，包括：所述终端设备确定基本文件管理数据EFAD指示的所述MNC的长度为无效值，则确定不能获取到所述MNC的长度无效。
一种可选的实现方式中，所述终端设备确定无法获取到所述MNC的长度，包括：所述终端设备确定所述终端设备中不包括EFAD时，确定不能获取到所述MNC的长度。
一种可选的实现方式中，所述校准后的长度为所述PLMN信息中包括的MNC的长度。
一种可选的实现方式中，当所述PLMN信息中的所述MNC的第三位的取值为F时，所述校准后的长度为2。
一种可选的实现方式中，当所述PLMN信息中的所述MNC的第三位的取值为0至9中的任一值时，所述校准后的长度为3。
一种可选的实现方式中，所述PLMN信息与所述终端设备中的国际移动用户识别码IMSI匹配。
一种可选的实现方式中，所述PLMN信息为通过系统广播消息获取到的PLMN。
一种可选的实现方式中，所述PLMN信息为已注册的公共陆地移动网络RPLMN，或者所述PLMN信息为等效公共陆地移动网络EPLMN。
一种可选的实现方式中，所述MNC位于所述第一注册消息中的加密的签约身份SUCI中。
第二方面，还提供一种方法，包括：终端设备确定移动网络码MNC的长度无效或者无法获取到所述MNC的长度时，发送第二注册请求消息，所述第二注册请求消息包括第一长度的所述MNC；所述第一长度等于2或3；所述终端设备若接收到响应所述第二注册请求消息的注册拒绝消息，则发送第三注册请求消息，所述第三注册请求消息包括第二长度的所述MNC；所述第二长度等于2或3，且所述第三长度与所述第二长度不同。
一种可选的实现方式中，所述第一长度为预配置的长度；或者，所述第一长度为所述终端设备随机选择的长度。
第三方面，本申请还提供一种通信装置，该通信装置具有实现上述第一方面或第二方面提供的任一方法。该通信装置可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或单元。
在一种可能的实现方式中，该通信装置包括：处理器，该处理器被配置为支持该通信装置执行以上所示方法中终端设备的相应功能。该通信装置还可以包括存储器，该存储可以与处理器耦合，其保存该通信装置必要的程序指令和数据。
可选地，该通信装置还包括接口电路，该接口电路用于支持该通信装置与网络设备等设备之间的通信。
在一种可能的实现方式中，该通信装置包括相应的功能单元，分别用于实现以上方法中的步骤。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的单元。
在一种可能的实施方式中，通信装置的结构中包括处理单元和通信单元，这些单元可以执行上述方法示例中相应功能，具体参见第三方面提供的方法中的描述，此处不做赘述。
第四方面，还提供了一种通信装置，包括：处理器和存储器；
其中，所述存储器用于存储程序指令；
所述处理器用于执行所述存储器中存储的程序指令，以使所述通信装置实现上述任一种可能的设计中的方法。
第五方面，本申请提供了一种通信装置，该装置可包括：存储单元，用于存储程序指令；处理单元，用于执行所述存储单元中的程序指令，以实现前述多种技术方案中的任一种可能的设计中的方法。
其中，该存储单元可以是存储器，例如易失性存储器，用于缓存这些程序指令，这些程序指令可以是所述数据调度方法运行时，从其他非易失性存储器中加载到该存储单元中。当然，所述存储单元也可以是非易失性存储器，也集成在所述芯片内部。该处理单元可以是处理器，例如芯片的一个或多个处理核心。
第六方面，本申请提供一种计算机可读存储介质，所述计算机存储介质中存储有计算机可读指令，当计算机读取并执行所述计算机可读指令时，使得通信装置执行上述任一种可能的设计中的方法。
第七方面，本申请提供一种计算机程序产品，当计算机读取并执行所述计算机程序产品时，使得通信装置执行上述任一种可能的设计中的方法。
第八方面，本申请提供一种芯片，所述芯片与存储器相连，用于读取并执行所述存储器中存储的软件程序，以实现上述任一种可能的设计中的方法。
附图说明
图1为本申请实施例提供的一种注册方法流程示意图；
图2为本申请实施例提供的一种MNC长度校准流程示意图；
图3为本申请实施例提供的一种注册方法流程示意图；
图4为本申请实施例提供的一种注册方法流程示意图；
图5为本申请实施例提供的一种通信装置结构示意图；
图6为本申请实施例提供的一种通信装置结构示意图。
具体实施方式
下面将结合附图对本申请实施例作进一步地详细描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：第五代(5th Generation，5G)系统中的新无线(New Radio，NR)，还可以应用于长期演进(Long Term Evolution，LTE)系统等，在此不做限制。
在2G/3G/4G网络中，终端设备在注册时，可以上报IMSI给核心网设备，上报的IMSI是没有经过加密的明文信息。IMSI中包括长度为2位或3位的MNC，核心网设备可以将2位长度的MNC或3位长度的MNC长度都尝试匹配，从而确定准确的MNC。
举例来说，终端设备上报的IMSI为：002011912121001。核心网设备可以认为MCC、MNC对应的序列存在两种可能，分别为002 01和002 011，核心网设备分别采用002 01和002 011来尝试路由查询IMSI对应的签约信息，如果其中一个查询成功，则可以认为对 应的序列为准确的MCC、MNC。
然而在5G网络中，终端设备在注册时上报的是SUCI，SUCI是签约永久身份(Subscription Permanent Identifier，SUPI)加密的格式，目前5G中的SUPI就是IMSI。其中SUCI只对SUPI中除了MCC和MNC之外的信息进行加密。
核心网设备，例如安全锚点功能(SEcurity Anchor Function，SEAF)接收到SUCI之后，需要通过SUCI中的MCC、MNC来作为路由选择，确定对应的统一数据管理(Unified Data Management，UDM)网元、签约身份解密功能(Subscription Identifier De-concealing Function，SIDF)网元。SEAF将SUCI发送到其对应的UDM、SIDF里做解密。如果终端设备携带的MCC和MNC长度不对，将导致SEAF网元无法正确路由到对应的UDM网元、SIDF网元上解密，从而无法识别终端设备的身份，导致终端设备在网络中注册失败。
举例来说，实网中存在两个PLMN，分别为PLMN1:310 014，其中MCC为310 MNC为014；PLMN2：310 015，其中MCC为310，MNC为015。假如终端设备上报的MNC为01，那SEAF获取到MCC为310、MNC为01时，SEAF就不知道将SUCI发送至MNC为014对应的UDM、SIDF里进行解密，还是发送至MNC为015对应的UDM、SIDF里进行解密。
为此，本申请实施例提供一种方法，可以在无法确定MNC长度时，对MNC进行校准，使得终端设备发送准确长度的MNC，从而实现在网络上注册成功。
需要说明的是，本申请实施例中，终端设备，可以为具有无线收发功能的设备或可设置于任一设备中的芯片，也可以称为用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线通信设备、用户代理或用户装置。本申请实施例中的终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
结合前面的描述，如图1所示，为本申请实施例提供的一种注册方法流程示意图。参见图1，该方法包括：
步骤101：终端设备确定MNC的长度无效或者无法获取到所述MNC的长度时，确定所述MNC校准后的长度。
一种可能的实现方式中，所述终端设备确定EFAD指示的MNC的长度为无效值是，则可以确定不能获取到所述MNC的长度无效。
举例来说，EFAD指示的MNC的长度为除了有效值之外的值时，可以确定MNC的长度无效。例如，目前MNC的长度的有效值为2或3，如果EFAD指示的MNC的长度为4，则EFAD指示的MNC的长度无效。
另一种可能的实现方式中，所述终端设备确定所述终端设备中不包括EFAD时，确定不能获取到所述MNC的长度。其中，所述终端设备中不包括EFAD，可以是指终端设备中的用户识别卡中不包括EFAD。
需要说明的是，EFAD一般存储于用户识别卡中的，用户识别卡可以是指用户识别模块(Subscriber Identity Module，SIM)卡，或者全球用户识别模块(Universal Subscriber  Identity Module，USIM)，或者嵌入式用户识别模块(Embedded Subscriber Identity Module，eSIM)卡等，用户识别卡可以与终端设备集成在一起，属于终端设备的一部分，也可以是与终端设备相互独立的芯片卡，本申请实施例并不限定。用户识别卡是运营商发布的存储运营商签约信息，为注册时提供身份、鉴权等流程的芯片或虚拟电子卡等。
进一步的，终端设备确定MNC的长度无效或者无法获取到所述MNC的长度时，可以对MNC的长度进行校准，具体的，可以根据PLMN信息确定所述校准后的MNC的长度，其中所述PLMN信息与所述终端设备中的IMSI匹配。
需要说明的是，IMSI，可以用于标识移动用户的身份，可以包括MCC、MNC以及移动用户识别码(Mobile Subscriber Identification Number，MSIN)等信息。IMSI中虽然包括MCC和MNC，但是终端设备在不确定MNC的长度的情况下，无法准确读取MNC。
本申请实施例中，具体如何对MNC的长度进行校准，可以参考如图2所示的过程：
步骤201：获取PLMN信息；
具体如何获取PLMN信息，本申请实施例并不限定。例如，PLMN信息可以为预配置在终端设备中的PLMN；PLMN信息可以为终端设备通过系统广播消息获取到的PLMN。
所述PLMN信息还可以为终端设备的非易失性数据存储器(Non-volatile Data Memory，NV)或者用户识别卡中存储的已注册的PLMN(Registered PLMN，RPLMN)；所述PLMN信息还可以为终端设备的NV或者用户识别卡中存储的等效PLMN(Equivalent PLMN，EPLMN)。
以上只是示例，还可以通过其他方式获取PLMN信息，在此不再逐一举例说明。
需要说明的是，PLMN，是一个运营商的标识，里面包含了MCC和MNC。RPLMN用于指示终端设备上次注册成功时的PLMN，可以存储在终端设备的NV和用户识别卡中，可以方便下次注册时能快速的在原来的网络注册。EPLMN，当一个运营商有多个PLMN时，终端设备可以在这多个PLMN对应的网络中移动并享受相等的收费策略，终端设备在网络中注册成功后，由网络配置给终端设备多个PLMN，这多个PLMN之间相互等效。
步骤202：从所述PLMN信息中获取MCC以及MNC。
需要说明的是，终端设备能够从PLMN信息中读取MCC和MNC，主要是根据MNC的最后一位的取值进行判断的。以PLMN信息为PLMN为例，PLMN中，MNC保存的长度为3位，如果PLMN中的MNC的第3位为F，第3位的取值为无效值，则可以从PLMN信息中获取长度为2的MNC；如果PLMN中的MNC的第3位为0至9中的任一值，第3位的取值为有效值，则可以从PLMN信息中获取长度为3的MNC。
步骤203：读取终端设备中的IMSI中指定长度的数字序列，该指定长度为PLMN信息中的MCC以及MNC长度之和。
举例来说，IMSI为：002011912121001。由于无法确定MNC的长度，所以IMSI中的MCC和MNC可以为002 01或者002 011。假设从PLMN信息中获取到的MCC以及MNC为002 01，则可以确定指定长度为5，从而可以从IMSI中读取前5位数字，即读取002 01。
假设从PLMN信息中获取到的MCC以及MNC为002 011，则可以确定指定长度为6，从而可以从IMSI中读取前6位数字，即读取002 011作为MCC以及MNC。
需要说明的是，前面的例子中，以从IMSI中读取的数字序列与PLMN信息中获取到的MCC以及MNC相同为例进行描述，在实际应用中，如果获取到的PLMN信息是错误 的，则可能不相同。
步骤204：判断IMSI中指定长度的数字序列与PLMN信息中的MCC以及MNC是否相同，如果相同，则转至步骤205，否则转至步骤206。
步骤205：IMSI中指定长度的数字序列与PLMN信息中的MCC以及MNC相同，可以确定所述PLMN信息与所述IMSI匹配，并将所述PLMN信息中的所述MNC的长度作为MNC校准后的长度。
具体的，如果PLMN中的MNC的最后一位为F，则可以确定MNC校准后的长度是2；如果PLMN中的MNC的最后一位为0至9中的任一值，则可以确定MNC校准后的长度是3。
终端设备在确定SUCI时，可以根据校准后的长度从IMSI中确定MNC。
步骤206：IMSI中指定长度的数字序列与PLMN信息中的MCC以及MNC不相同，则可以确定所述PLMN信息与所述IMSI不匹配，此时可以不对MNC的长度进行校准。
此时终端设备可以将预配置的长度作为MNC的长度，也可以从2和3中随机选择一个作为MNC的长度。
终端设备对MNC的长度校准之后，可以使用校准后的长度的MNC发起注册请求，具体可以参考步骤102。
步骤102：终端设备发送第一注册请求消息，所述第一注册请求消息用于请求在网络中注册。
所述第一注册请求消息可以包括SUCI，SUCI中可以包括所述校准后的长度的所述MNC。
所述第一注册请求消息可以是5G NR中的注册请求消息(registration request)，也可以是其它类型的网络中的注册请求消息。
下面通过具体的实施例详细描述上面的过程。
如图3所示，为本申请实施例提供的一种校准MNC长度流程示意图。
步骤301：终端设备获取EFAD。
终端设备可以从SIM卡等中读取EFAD。
步骤302：EFAD指示的MNC的长度是否有效，如果无效则转至步骤303；如果有效则转至步骤308。
需要说明的是，如果终端设备没有获取到EFAD，则可以直接执行步骤303。
步骤303：如果终端设备的NV中存储了PLMN，则判断该PLMN是否能和终端设备中的IMSI匹配，如果不匹配则转至步骤304；如果匹配则转至步骤309。
需要说明的是，NV中存储的PLMN，可以是指当此终端设备上一次在网络中注册时使用的PLMN。
步骤304：如果终端设备中存在预配置的PLMN，则判断该PLMN是否能和终端设备中的IMSI匹配，如果不匹配则转至步骤305；如果匹配则转至步骤308。
步骤305：如果终端设备中的NV或者用户识别卡中存在RPLMN或EPLMN，则判断该RPLMN或EPLMN是否能和终端设备中的IMSI匹配，如果不匹配则转至步骤306；如果匹配则转至步骤308。
步骤306：通过系统广播消息获取PLMN，则判断该PLMN是否能和终端设备中的IMSI 匹配，如果不匹配则转至步骤307；如果匹配则转至步骤308。
需要说明的是，这里的系统广播消息可以是指NR网络中的系统广播消息。
进一步的，如果当前不存在NR网络，此时终端设备可能无法获取NR网络中的系统广播消息。在该情况下，终端设备可以搜索2G/3G/4G网络，然后在2G/3G/4G网络中注册，获取2G/3G/4G网络下发的EPLMN，此时终端设备可以将获取到的EPLMN与IMSI进行匹配。在匹配成功时，可以采用2G/3G/4G网络下发的EPLMN和在2G/3G/4G网络中注册的RPLMN对MNC的长度进行校准。
步骤307：将终端设备中配置的默认长度作为MNC的长度。
或者，终端设备也可以从2或3中随机选择一个作为MNC的长度。
步骤308：对MNC的长度进行校准，获得校准后的MNC的长度。
具体校准过程可以参考图2所示的流程。
步骤309：根据EFAD指示的长度确定MNC。
需要说明的是，步骤303至步骤306的顺序并不限定，也可以存在其他执行顺序。
结合前面的流程可知，不使用本申请实施例提供的方法时，终端设备在空口发送的注册请求消息中的SUCI中，只能使用默认的MNC长度，此时MNC的长度并不准确。如果默认的MNC长度和实际的MNC长度不一致，就会出现错误，会导致SUCI中携带的MCC、MNC错误。比如终端设备中的IMSI为002011912121001，实际的PLMN为002 01。如果默认的MNC长度为3时，则注册请求消息中的SUCI携带的MCC、MNC为002 011，导致注册时网络下发注册拒绝，导致终端设备不能注册成功。
通过本申请实施例提供的方法，如果MNC长度无效或者无法确定MNC长度的情况下，终端设备可以从获取到的PLMN信息来校准MNC的长度。比如IMSI为002011912121001，实际的PLMN为002 01，那注册请求消息中的SUCI携带的MCC、MNC为002 01，核心网设备能够根据该SUCI中携带的MCC、MNC正确路由，终端设备从而能够注册成功。
进一步的，本申请实施例还提供一种方法，具体的，如图4所示，该方法包括：
步骤401：终端设备确定MNC的长度无效或者无法获取到所述MNC的长度时，发送第二注册请求消息。
所述第二注册请求消息包括第一长度的所述MNC。
其中，所述第一长度为预配置的长度，或者，所述第一长度为所述终端设备随机选择的长度。需要说明的是，目前MNC的长度为2或3，因此所述第一长度等于2或3。
终端设备如何确定MNC的长度无效，可以参考步骤201中的描述，在此不再赘述。
需要说明的是，终端设备可以向网络设备发送第二注册请求消息，网络设备例如可以是SEAF，也可以是其它网络设备，在此不再赘述。
可选的，步骤402：终端设备若接收到响应所述第二注册请求消息的注册拒绝消息，则发送第三注册请求消息。
所述第三注册请求消息包括第二长度的所述MNC；所述第三长度与所述第二长度不同。
举例来说，第一长度等于2，则所述第二长度等于3；第一长度等于3，则所述第二长度等于2。
如果终端设备接收到响应所述第二注册请求消息的注册接受消息，那么终端设备可以确定MNC的长度为所述第一长度。
如果终端设备接收到响应所述第三注册请求消息的注册接受消息，那么终端设备可以确定MNC的长度为所述第三长度。
进一步的，当终端设备确定注册成功时，还可以存储注册成功时采用的MNC长度，当下次注册时，采用该MNC长度进行注册。
通过上面的方法，终端设备可以多次尝试采用不同的MNC长度进行注册，从而避免在无法确定MNC长度时无法注册的情况发生。
本文中描述的各个实施例可以为独立的方案，也可以根据内在逻辑进行组合，这些方案都落入本申请的保护范围中。
可以理解的是，上述各个方法实施例中，由终端设备实现的方法和操作，也可以由可用于终端设备的部件(例如芯片或者电路)实现。
上述本申请提供的实施例中，分别从各个设备之间交互的角度对本申请实施例提供的方法进行了介绍。为了实现上述本申请实施例提供的方法中的各功能，终端设备与网络设备可以包括硬件结构和/或软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能以硬件结构、软件模块、还是硬件结构加软件模块的方式来执行，取决于技术方案的特定应用和设计约束条件。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
与上述构思相同，如图5所示，本申请实施例还提供一种装置500用于实现上述方法中终端设备的功能。例如，该装置可以为软件模块或者芯片系统。本申请实施例中，芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。该装置500可以包括：处理单元501和通信单元502。
本申请实施例中，通信单元也可以称为收发单元，可以包括发送单元和/或接收单元，分别用于执行上文方法实施例中终端设备发送和接收的步骤。
以下，结合图5至图6详细说明本申请实施例提供的通信装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，这里不再赘述。
在一种可能的设计中，该装置500可实现对应于上文方法实施例中的终端设备执行的步骤或者流程，下面分别进行描述。
示例性地，当该装置500实现图2所示的流程中终端设备的功能时：
处理单元501，用于确定移动网络码MNC的长度无效或者无法获取到所述MNC的长度时，确定所述MNC校准后的长度；所述校准后的长度是根据公共陆地移动网络PLMN信息确定的；
通信单元502，用于发送第一注册请求消息，所述第一注册请求消息用于请求在网络中注册；
所述第一注册请求消息包括所述校准后的长度的所述MNC。
一种可选的实现方式中，所述处理单元501用于：
确定基本文件管理数据EFAD指示的所述MNC的长度为无效值，则确定不能获取到所述MNC的长度无效。
一种可选的实现方式中，所述处理单元501用于：
确定所述终端设备中不包括EFAD时，确定不能获取到所述MNC的长度。
一种可选的实现方式中，所述校准后的长度为所述PLMN信息中包括的MNC的长度。
一种可选的实现方式中，当所述PLMN信息中的所述MNC的第三位的取值为F时，所述校准后的长度为2。
一种可选的实现方式中，当所述PLMN信息中的所述MNC的第三位的取值为0至9中的任一值时，所述校准后的长度为3。
一种可选的实现方式中，所述PLMN信息与所述终端设备中的国际移动用户识别码IMSI匹配。
一种可选的实现方式中，所述PLMN信息为通过系统广播消息获取到的PLMN。
一种可选的实现方式中，所述PLMN信息为已注册的公共陆地移动网络RPLMN，或者所述PLMN信息为等效公共陆地移动网络EPLMN。
一种可选的实现方式中，所述MNC位于所述第一注册消息中的加密的签约身份SUCI中。
示例性地，当该装置500实现图4所示的流程中终端设备的功能时：
处理单元501，用于确定移动网络码MNC的长度无效或者无法获取到所述MNC的长度时，通过通信单元502发送第二注册请求消息，所述第二注册请求消息包括第一长度的所述MNC；所述第一长度等于2或3；
所述通信单元502，用于若接收到响应所述第二注册请求消息的注册拒绝消息，则发送第三注册请求消息，所述第三注册请求消息包括第二长度的所述MNC；所述第二长度等于2或3，且所述第三长度与所述第二长度不同。
一种可选的实现方式中，所述第一长度为预配置的长度；或者，所述第一长度为所述终端设备随机选择的长度。
如图6所示为本申请实施例提供的装置600，图6所示的装置可以为图5所示的装置的一种硬件电路的实现方式。该通信装置可适用于图2所示出的流程图中，执行上述方法实施例中终端设备的功能。为了便于说明，图6仅示出了该通信装置的主要部件。
图6所示的装置600包括至少一个处理器620，用于实现本申请实施例提供的图2中任一方法。
装置600还可以包括至少一个存储器630，用于存储程序指令和/或数据。存储器630和处理器620耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器620可能和存储器630协同操作。处理器620可能执行存储器630中存储的程序指令。所述至少一个存储器中的至少一个可以包括于处理器中。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储 介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理电路(digital signal processor，DSP)、专用集成芯片(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
装置600还可以包括接口电路610，用于通过传输介质和其它设备进行通信，从而用于装置600中的装置可以和其它设备进行通信。在本申请实施例中，接口电路可以是收发器、电路、总线、模块或其它类型的接口电路。在本申请实施例中，接口电路为收发器时，收发器可以包括独立的接收器、独立的发射器；也可以集成收发功能的收发器、或者是接口电路。
装置600还可以包括通信线路640。其中，接口电路610、处理器620以及存储器630可以通过通信线路640相互连接；通信线路640可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。所述通信线路640可以分为地址总线、数据总线、控制总线等。为便于表示，图6中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
示例性地，当该装置600实现图2所示的流程中终端设备的功能时：
处理器620，用于确定移动网络码MNC的长度无效或者无法获取到所述MNC的长度时，确定所述MNC校准后的长度；所述校准后的长度是根据公共陆地移动网络PLMN信息确定的；
接口电路610，用于发送第一注册请求消息，所述第一注册请求消息用于请求在网络中注册；
所述第一注册请求消息包括所述校准后的长度的所述MNC。
一种可选的实现方式中，所述处理器620用于：
确定基本文件管理数据EFAD指示的所述MNC的长度为无效值，则确定不能获取到所述MNC的长度无效。
一种可选的实现方式中，所述处理器620用于：
确定所述终端设备中不包括EFAD时，确定不能获取到所述MNC的长度。
一种可选的实现方式中，所述校准后的长度为所述PLMN信息中包括的MNC的长度。
一种可选的实现方式中，当所述PLMN信息中的所述MNC的第三位的取值为F时，所述校准后的长度为2。
一种可选的实现方式中，当所述PLMN信息中的所述MNC的第三位的取值为0至9中的任一值时，所述校准后的长度为3。
一种可选的实现方式中，所述PLMN信息与所述终端设备中的国际移动用户识别码IMSI匹配。
一种可选的实现方式中，所述PLMN信息为通过系统广播消息获取到的PLMN。
一种可选的实现方式中，所述PLMN信息为已注册的公共陆地移动网络RPLMN，或者所述PLMN信息为等效公共陆地移动网络EPLMN。
一种可选的实现方式中，所述MNC位于所述第一注册消息中的加密的签约身份SUCI中。
示例性地，当该装置600实现图4所示的流程中终端设备的功能时：
处理器620，用于确定移动网络码MNC的长度无效或者无法获取到所述MNC的长度时，通过接口电路610发送第二注册请求消息，所述第二注册请求消息包括第一长度的所述MNC；所述第一长度等于2或3；
所述接口电路610，用于若接收到响应所述第二注册请求消息的注册拒绝消息，则发送第三注册请求消息，所述第三注册请求消息包括第二长度的所述MNC；所述第二长度等于2或3，且所述第三长度与所述第二长度不同。
一种可选的实现方式中，所述第一长度为预配置的长度；或者，所述第一长度为所述终端设备随机选择的长度。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现 在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (27)

  1. 一种注册方法，其特征在于，包括：
    终端设备确定移动网络码MNC的长度无效或者无法获取到所述MNC的长度时，确定所述MNC校准后的长度；所述校准后的长度是根据公共陆地移动网络PLMN信息确定的；
    所述终端设备发送第一注册请求消息，所述第一注册请求消息用于请求在网络中注册；
    所述第一注册请求消息包括所述校准后的长度的所述MNC。
  2. 根据权利要求1所述的方法，其特征在于，所述终端设备确定移动网络码MNC的长度无效，包括：
    所述终端设备确定基本文件管理数据EFAD指示的所述MNC的长度为无效值，则确定不能获取到所述MNC的长度无效。
  3. 根据权利要求1所述的方法，其特征在于，所述终端设备确定无法获取到所述MNC的长度，包括：
    所述终端设备确定所述终端设备中不包括EFAD时，确定不能获取到所述MNC的长度。
  4. 根据权利要求1至3任一所述的方法，其特征在于，所述校准后的长度为所述PLMN信息中包括的MNC的长度。
  5. 根据权利要求4所述的方法，其特征在于，当所述PLMN信息中的所述MNC的第三位的取值为F时，所述校准后的长度为2。
  6. 根据权利要求4所述的方法，其特征在于，当所述PLMN信息中的所述MNC的第三位的取值为0至9中的任一值时，所述校准后的长度为3。
  7. 根据权利要求1至6任一所述的方法，其特征在于，所述PLMN信息与所述终端设备中的国际移动用户识别码IMSI匹配。
  8. 根据权利要求1至7任一所述的方法，其特征在于，所述PLMN信息为通过系统广播消息获取到的PLMN。
  9. 根据权利要求1至7任一所述的方法，其特征在于，所述PLMN信息为已注册的公共陆地移动网络RPLMN，或者所述PLMN信息为等效公共陆地移动网络EPLMN。
  10. 根据权利要求1至9任一所述的方法，其特征在于，所述MNC位于所述第一注册消息中的加密的签约身份SUCI中。
  11. 一种注册方法，其特征在于，包括：
    终端设备确定移动网络码MNC的长度无效或者无法获取到所述MNC的长度时，发送第二注册请求消息，所述第二注册请求消息包括第一长度的所述MNC；所述第一长度等于2或3；
    所述终端设备若接收到响应所述第二注册请求消息的注册拒绝消息，则发送第三注册请求消息，所述第三注册请求消息包括第二长度的所述MNC；所述第二长度等于2或3，且所述第三长度与所述第二长度不同。
  12. 根据权利要求11所述的方法，其特征在于，所述第一长度为预配置的长度；
    或者，所述第一长度为所述终端设备随机选择的长度。
  13. 一种通信装置，其特征在于，包括：
    处理单元，用于确定移动网络码MNC的长度无效或者无法获取到所述MNC的长度时，确定所述MNC校准后的长度；所述校准后的长度是根据公共陆地移动网络PLMN信息确定的；
    通信单元，用于发送第一注册请求消息，所述第一注册请求消息用于请求在网络中注册；所述第一注册请求消息包括所述校准后的长度的所述MNC。
  14. 根据权利要求13所述的装置，其特征在于，所述处理单元具体用于：
    确定基本文件管理数据EFAD指示的所述MNC的长度为无效值，则确定不能获取到所述MNC的长度无效。
  15. 根据权利要求13所述的装置，其特征在于，所述处理单元具体用于：
    确定终端设备中不包括EFAD时，确定不能获取到所述MNC的长度。
  16. 根据权利要求13至15任一所述的装置，其特征在于，所述校准后的长度为所述PLMN信息中包括的MNC的长度。
  17. 根据权利要求16所述的装置，其特征在于，当所述PLMN信息中的所述MNC的第三位的取值为F时，所述校准后的长度为2。
  18. 根据权利要求16所述的装置，其特征在于，当所述PLMN信息中的所述MNC的第三位的取值为0至9中的任一值时，所述校准后的长度为3。
  19. 根据权利要求13至18任一所述的装置，其特征在于，所述PLMN信息与终端设备中的国际移动用户识别码IMSI匹配。
  20. 根据权利要求13至19任一所述的装置，其特征在于，所述PLMN信息为通过系统广播消息获取到的PLMN。
  21. 根据权利要求13至19任一所述的装置，其特征在于，所述PLMN信息为已注册的公共陆地移动网络RPLMN，或者所述PLMN信息为等效公共陆地移动网络EPLMN。
  22. 根据权利要求13至21任一所述的装置，其特征在于，所述MNC位于所述第一注册消息中的加密的签约身份SUCI中。
  23. 一种通信装置，其特征在于，包括：
    处理单元，用于确定移动网络码MNC的长度无效或者无法获取到所述MNC的长度时，通过通信单元发送第二注册请求消息，所述第二注册请求消息包括第一长度的所述MNC；所述第一长度等于2或3；
    所述通信单元，用于若接收到响应所述第二注册请求消息的注册拒绝消息，则发送第三注册请求消息，所述第三注册请求消息包括第二长度的所述MNC；所述第二长度等于2或3，且所述第三长度与所述第二长度不同。
  24. 根据权利要求23所述的装置，其特征在于，所述第一长度为预配置的长度；
    或者，所述第一长度为所述终端设备随机选择的长度。
  25. 一种通信装置，其特征在于，包括：处理器和接口电路；
    其中，所述接口电路用于访问存储器，所述存储器中存储有程序指令；
    所述处理器用于通过所述接口电路访问所述存储器，并执行所述存储器中存储的程序指令，以使所述通信装置实现所述权利要求1至12中任一项所述的方法。
  26. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储了程序代码，所述程序代码被计算机执行时，实现所述权利要求1至12中任一项所述的方法。
  27. 一种计算机程序产品，其特征在于，所述计算机程序产品包含的程序代码被计算机执行时，实现所述权利要求1至12中任一项所述的方法。
PCT/CN2020/081518 2020-03-26 2020-03-26 一种注册方法及装置 WO2021189389A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202080012131.5A CN113728682A (zh) 2020-03-26 2020-03-26 一种注册方法及装置
PCT/CN2020/081518 WO2021189389A1 (zh) 2020-03-26 2020-03-26 一种注册方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/081518 WO2021189389A1 (zh) 2020-03-26 2020-03-26 一种注册方法及装置

Publications (1)

Publication Number Publication Date
WO2021189389A1 true WO2021189389A1 (zh) 2021-09-30

Family

ID=77889881

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/081518 WO2021189389A1 (zh) 2020-03-26 2020-03-26 一种注册方法及装置

Country Status (2)

Country Link
CN (1) CN113728682A (zh)
WO (1) WO2021189389A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113766486B (zh) * 2021-09-23 2024-03-26 展讯通信（上海）有限公司 归属公共陆地移动网络标识的修正方法及设备

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20050054795A (ko) * 2003-12-06 2005-06-10 엘지전자 주식회사 이동통신망의 국제 이동국 식별자 및 그를 이용한 이동망식별 방법
CN1741673A (zh) * 2004-08-23 2006-03-01 华为技术有限公司 获取和处理移动网络码的方法
CN101622895A (zh) * 2007-02-02 2010-01-06 艾利森电话股份有限公司 用户设备标识符的导出
CN101657005A (zh) * 2009-09-04 2010-02-24 深圳华为通信技术有限公司 一种终端接入网络的方法以及终端
CN103313204A (zh) * 2012-03-13 2013-09-18 中兴通讯股份有限公司 基于移动终端接收小区广播的方法及装置
CN105338614A (zh) * 2014-08-07 2016-02-17 华为技术有限公司 一种网络注册方法及装置
CN106257952A (zh) * 2015-06-16 2016-12-28 西安中兴新软件有限责任公司 一种切换移动网络的方法及移动终端

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20050054795A (ko) * 2003-12-06 2005-06-10 엘지전자 주식회사 이동통신망의 국제 이동국 식별자 및 그를 이용한 이동망식별 방법
CN1741673A (zh) * 2004-08-23 2006-03-01 华为技术有限公司 获取和处理移动网络码的方法
CN101622895A (zh) * 2007-02-02 2010-01-06 艾利森电话股份有限公司 用户设备标识符的导出
CN101657005A (zh) * 2009-09-04 2010-02-24 深圳华为通信技术有限公司 一种终端接入网络的方法以及终端
CN103313204A (zh) * 2012-03-13 2013-09-18 中兴通讯股份有限公司 基于移动终端接收小区广播的方法及装置
CN105338614A (zh) * 2014-08-07 2016-02-17 华为技术有限公司 一种网络注册方法及装置
CN106257952A (zh) * 2015-06-16 2016-12-28 西安中兴新软件有限责任公司 一种切换移动网络的方法及移动终端

Also Published As

Publication number Publication date
CN113728682A (zh) 2021-11-30

Similar Documents

Publication Publication Date Title
US11722891B2 (en) User authentication in first network using subscriber identity module for second legacy network
US11778458B2 (en) Network access authentication method and device
EP3114862B1 (en) Communication system
US20230379709A1 (en) Registration method and apparatus, authentication method and apparatus, routing indicator determination method and apparatus, entity, and terminal
US20240121606A1 (en) Pc5 root key processing method, device, ausf and remote terminal
CN111132146B (zh) 一种无线网络接入和校准方法、装置及设备
CN107820246B (zh) 用户认证的方法、装置和系统
US10820265B2 (en) IoT device connectivity provisioning
US20220295272A1 (en) Authentication server function selection in an authentication and key agreement
WO2021189389A1 (zh) 一种注册方法及装置
CN114450991A (zh) 用于注册程序的无线通信方法
US20200359184A1 (en) Privacy-enhanced method for linking an esim profile
WO2022116809A1 (zh) 随机接入的方法、装置和系统
WO2020071980A1 (en) Method for identifying terminal capabilities in a wireless communication system
EP4132016A1 (en) Method and apparatus for using proximity discovery identification, and storage medium
KR102642804B1 (ko) 다중 대역 통신 방법 및 장치
CN111770488B (zh) Ehplmn更新方法、相关设备及存储介质
CN114339720A (zh) 一种云卡鉴权方法、装置、终端及存储介质
CN114640992A (zh) 更新用户身份标识的方法和装置
WO2021004022A1 (zh) 一种单imsi用于多网终端重复注册的方法
CN115396126A (zh) Nswo业务的认证方法、设备和存储介质
CN114827898B (zh) 上网配置方法、装置、设备和介质
KR20110017520A (ko) 무선통신시스템에서 듀얼 모드 단말의 인증 장치 및 방법
WO2024067047A1 (zh) 一种通信方法及装置
US20220272530A1 (en) Securing user equipment identifier for use external to communication network

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20927750

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20927750

Country of ref document: EP

Kind code of ref document: A1