Communication method and related apparatus

Abstract

Provided in the present application are a communication method and a related apparatus. The method comprises: when mobility registration update conditions for a first universal integrated circuit card (UICC) and a second UICC are met, sending a first registration request message, wherein the first registration request message is used for mobility registration update for the first UICC and the second UICC. Compared with the existing protocols, using a single registration request message to perform mobility registration update for a first UICC and a second UICC enables completion of mobility registration update for two UICCs by means of a single mobility registration update procedure, without the need to perform a separate mobility registration update procedure for each UICC. That is, mobility registration update for two UICCs can be implemented by means of a single set of mobility registration update signaling, thereby reducing signaling overhead and thus reducing the signaling burden on a network.

Description

Communication methods and related devices

[0001] This application claims priority to Chinese Patent Application No. 2024119852543, filed on December 27, 2024, entitled "Communication Method and Related Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of mobile communication technology, and in particular to a communication method and related apparatus. Background Technology

[0003] Mobility registration update is a common service process in mobile communications, requiring multiple signaling steps. In some scenarios, such as NTN (non-terrestrial network) networks, where network capacity is limited and satellite movement causes changes in tracking areas, simultaneous mobility registration updates by devices within the same tracking area can place a high signaling burden on the network. Summary of the Invention

[0004] This application provides a communication method and related apparatus to solve the problem of high signaling burden in communication networks. The disclosed technical solution is as follows:

[0005] The first aspect of this application provides a communication method, comprising: sending a first registration request message when the mobility registration update conditions of a first general-purpose integrated circuit card (UICC) and a second UICC are met, wherein the first registration request message is used for the first UICC and the second UICC to perform mobility registration update. Compared with existing protocols, using a single registration request message to perform mobility registration update for the first UICC and the second UICC may allow the mobility registration update of both UICCs to be completed in a single mobility registration update process, without requiring each UICC to undergo a separate mobility registration update process. That is, the mobility registration update of both UICCs can be achieved through a single set of mobility registration update signaling, saving signaling overhead and thus reducing the signaling burden on the network.

[0006] In some implementations, the first registration request message includes a first field, a second field, a third field, and a fourth field. The first field instructs the first UICC to perform a mobility registration update, the second field indicates the identity information of the first UICC (such as temporary identity authentication information), the third field instructs the second UICC to perform a mobility registration update, and the fourth field indicates the identity information of the second UICC. Compared with existing protocols, the first registration request message adds the third and fourth fields to indicate relevant information for the mobility registration update of the second UICC, thus expanding the functionality of the registration request message.

[0007] In some implementations, the method further includes receiving a first registration acceptance message, which indicates the mobility registration update information of the first UICC (such as successful mobility registration update, updated identity information, tracking area list, etc.) and the mobility registration update information of the second UICC. Compared with existing protocols, the first registration acceptance message adds the function of indicating the mobility registration update information of the second UICC, thus further saving signaling.

[0008] In some implementations, the method further includes receiving a second registration acceptance message, which indicates that the mobility registration update information of the first UICC and the mobility registration update of the second UICC have failed. Compared with existing protocols, the second registration acceptance message adds the function of indicating that the mobility registration update of the second UICC has failed, thus further saving signaling.

[0009] In some implementations, after receiving the second registration acceptance message, the process further includes sending a second registration request message, which is used for the mobility registration update of the second UICC. The second registration acceptance message indicates that the mobility registration update of the second UICC has failed; therefore, performing the mobility registration update of the second UICC via the second registration request message helps ensure the normal communication of the second UICC.

[0010] In some implementations, sending a first registration request message includes: sending the first registration request message if request conditions are met. The request conditions include at least one of a first condition and a second condition. The first condition includes: the first UICC and the second UICC belong to the same operator; the second condition includes: the first UICC and the second UICC belong to the same tracking area. The first condition ensures normal communication between the first UICC and the second UICC. If the first UICC and the second UICC do not belong to the same tracking area, in some cases, updating the mobility registration of the first UICC and the second UICC via the first registration request message may increase signaling overhead. Therefore, the second condition ensures a reduction in network signaling burden.

[0011] A second aspect of this application provides a communication method comprising: receiving a registration request message for mobility registration updates of a first UICC and a second UICC; sending a first registration acceptance message or a second registration acceptance message, wherein the first registration acceptance message indicates mobility registration update information of the first UICC and the second UICC, and the second registration acceptance message indicates that the mobility registration update information of the first UICC and the mobility registration update of the second UICC failed. Using a first registration acceptance message or a second registration acceptance message to indicate tracking area update information or success / failure results for the first UICC and the second UICC helps to save signaling, thereby reducing the signaling burden on the network.

[0012] In some implementations, the first registration acceptance message indicates the mobility registration update information of both the first UICC and the second UICC. This includes: the first registration acceptance message contains a fifth, sixth, seventh, and eighth field; the fifth field indicates successful mobility registration update for the first UICC; the sixth field indicates updated identity information for the first UICC; the seventh field indicates successful mobility registration update for the second UICC; and the eighth field indicates updated identity information for the second UICC. Compared to existing protocols, this expands the functionality of the registration acceptance message, laying the foundation for saving signaling.

[0013] In some implementations, the second registration acceptance message indicates the mobility registration update information of the first UICC and the mobility registration update of the second UICC failed. This includes: the second registration acceptance message contains a fifth field, a sixth field, and a seventh field, where the fifth field indicates that the mobility registration update of the first UICC was successful, the sixth field indicates the updated identity information of the first UICC, and the seventh field indicates that the mobility registration update of the second UICC failed.

[0014] A third aspect of this application provides a communication device, comprising: a memory for storing computer programs or computer instructions, and a processor for executing the computer programs or computer instructions stored in the memory, causing the communication device to perform the methods provided in the first or second aspect of this application.

[0015] A fourth aspect of this application provides a computer-readable storage medium for storing a computer program, which, when executed, implements the method provided in the first or second aspect of this application.

[0016] The fifth aspect of this application provides a computer program product that, when run on an electronic device, causes the electronic device to implement the method provided in the first or second aspect of this application.

[0017] A sixth aspect of this application provides a chip system comprising: at least one processor and an interface for receiving code instructions and transmitting them to the at least one processor, wherein the at least one processor executes the code instructions to implement the method provided in the first or second aspect of this application.

[0018] The seventh aspect of this application provides a communication device, including a processing module and a transceiver module, which is used to perform the method provided in the first or second aspect of this application.

[0019] The eighth aspect of this application provides a communication system, including the communication device provided in the seventh aspect of this application. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 is a flowchart of a communication method provided in an embodiment of this application;

[0022] Figure 2 is a flowchart of another communication method provided in an embodiment of this application;

[0023] Figure 3 is a flowchart of another communication method provided in an embodiment of this application;

[0024] Figure 4 is an example diagram of a communication device provided in an embodiment of this application;

[0025] Figure 5 is an example diagram of another communication device provided in an embodiment of this application;

[0026] Figure 6 is an example diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0027] The terms "first," "second," and "third," etc., used in this application specification, claims, and drawings are used to distinguish different objects, not to limit a specific order.

[0028] In the embodiments of this application, the words "in some implementations" or "for example" are used to indicate examples, illustrations or descriptions, and should not be construed as being more preferred or more advantageous than other embodiments or designs.

[0029] The communication systems applicable to the embodiments of this application can be second-generation (2G) communication systems, third-generation (3G) communication systems, long-term evolution (LTE) systems, fifth-generation (5G) communication systems, LTE and 5G hybrid architectures, 5G new radio (5G NR) systems, and new communication systems that will emerge in the future development of communication.

[0030] A communication system includes terminals and network equipment. Network equipment includes access network equipment and core network equipment.

[0031] Terminals can take various forms, such as mobile phones, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, vehicle-mounted terminal devices, wireless terminals in self-driving vehicles, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, wearable terminal devices, and so on. Terminals are sometimes also referred to as terminal equipment, user equipment (UE), access terminal equipment, vehicle-mounted terminals, industrial control terminals, UE units, UE stations, mobile stations, mobile stations, remote stations, remote terminal equipment, mobile devices, UE terminal equipment, terminal equipment, wireless communication equipment, UE agents, or UE devices, etc. Terminals can also be fixed terminals or mobile terminals.

[0032] Access network equipment can be terrestrial base stations or non-terrestrial network (NTN) equipment. NTN equipment can also be called base stations and / or satellite access nodes (SAN).

[0033] A base station is any device located on the network side with wireless transceiver capabilities, including but not limited to: evolved Node Bs (NodeBs, eNBs, or e-NodeBs) in LTE, base stations (gNodeBs or gNBs) or transmission receiving points / transmission reception points (TRPs) in new radio (NR), base stations evolved later in 3GPP, access nodes, wireless relay nodes, and wireless backhaul nodes in Wi-Fi systems. Base stations can be macro base stations, micro base stations, pico base stations, small cells, relay stations, or balloon stations, etc. A base station can contain one or more co-located or non-co-located TRPs. A base station can also be a radio controller, centralized unit (CU), and / or distributed unit (DU) in a cloud radio access network (CRAN) scenario. Base stations can communicate with terminals directly or via relay stations.

[0034] Taking non-terrestrial networks (NTNs) as an example, in NTN scenarios, if the coverage area of ​​the tracking area is too large, it may lead to a heavy paging load within that tracking area. Conversely, if the coverage area of ​​the tracking area is too small, it may result in excessive signaling overhead due to frequent TAUs. This issue is mentioned in the relevant chapters of TR38.821, which relates to NTNs.

[0035] Especially when a terminal is equipped with two SIM cards, each SIM card needs to undergo a TAU (Transmission and Unloading) process, resulting in higher signaling overhead.

[0036] To address the aforementioned issues, embodiments of this application provide a communication method applied to a terminal performing mobility registration updates to a core network device. The purpose of the mobility registration update includes, but is not limited to, tracking area updates.

[0037] The terminal described in this embodiment is equipped with two universal integrated circuit cards (UICCs), referred to as the first UICC and the second UICC, respectively.

[0038] UICC cards can perform at least one of the following functions: Universal Subscriber Identity Module (USIM), Subscriber Identity Module (SIM), or Embedded SIM (eSIM). Therefore, UICC cards can also be called SIM cards, USIM cards, or eSIM cards, etc.

[0039] In one example, the first UICC is the primary card and the second UICC is the secondary card; in another example, the first UICC is the secondary card and the second UICC is the primary card.

[0040] Figure 1 illustrates a communication method provided by an embodiment of this application, comprising the following steps:

[0041] S11. If the terminal meets the mobility registration update conditions of the first UICC and the second UICC, it sends a first registration request message. Correspondingly, the base station receives the first registration request message and transparently transmits it to the core network equipment. Correspondingly, the core network equipment receives the first registration request message.

[0042] The first registration request message is used for mobility registration updates between the first UICC and the second UICC. That is, the type of the first registration request sent in this step is mobility registration updating (MRU).

[0043] Transparent transmission can be understood as forwarding. In the following steps, all messages transmitted between the terminal and the core network equipment are transparently transmitted by the base station, and the steps of base station transparent transmission will not be described again.

[0044] S12. The core network equipment sends a first registration request acceptance message or a second registration acceptance message, and the terminal receives the first registration acceptance message or the second registration acceptance message accordingly.

[0045] The first registration accept message indicates the mobility registration update information for both the first and second UICCs. The second registration accept message indicates that the mobility registration update information for both the first and second UICCs failed.

[0046] The failure of the additional update request means that the second UICC mobility registration update, which was initiated by the first registration request message, failed. However, since the network sent a registration acceptance message, the mobility registration update of the first UICC was successful.

[0047] The method provided in this embodiment can perform mobility registration and update of two UICCs in one mobility registration and update process, which reduces the signaling interaction between the second UICC and the network, thereby reducing signaling overhead and thus reducing the signaling burden on the network.

[0048] Figure 2 illustrates another communication method provided by an embodiment of this application, which includes the following steps:

[0049] S21. The terminal sends a Registration Request message. Correspondingly, the base station receives and transmits the Registration Request message to the core network equipment. The core network equipment then receives the Registration Request message.

[0050] Compared to existing protocols, the registration request message in this step includes new fields. To distinguish it from the registration request message specified in existing protocols, the registration request message in this step is referred to as the first registration request message.

[0051] The first registration request message includes a first field, a second field, a third field, and a fourth field. The first field instructs the first UICC to update its mobility registration, and the second field indicates the temporary identity verification information of the first UICC.

[0052] The newly added fields include a third field and a fourth field. The third field indicates an additional update request, which is a request to update the mobility registration of the second UICC. The fourth field indicates the temporary identity authentication information currently assigned to the second UICC.

[0053] In some implementations, the currently assigned temporary identity authentication information is the 5G globally unique temporary identifier (5g-GUTI), while in others it is the 5G-S-temporary mobile subscriber identity (5G-S-TMSI). 5G-S-TMSI is a shortened form of 5G-GUTI. Both 5g-GUTI and 5G-S-TMSI are temporary identifiers assigned by the network during initial network registration and have a limited validity period. Compared to long-term valid identifiers, using 5g-GUTI or 5G-S-TMSI offers higher security.

[0054] The current 5g-GUTI or 5g-S-TMSI of UICC is the temporary identity authentication identifier information assigned to UICC by the network during the previous initial registration or mobility registration update process.

[0055] In some implementations, such as in LTE systems, the first registration request message carries a Tracking Area Update Request (TAU req). The first, second, third, and fourth fields mentioned above are included in the Tracking Area Update Request, which may be referred to as the TAU.

[0056] Transparent transmission can be understood as forwarding. In the following steps, all messages transmitted between the terminal and the core network equipment are transparently transmitted by the base station, and the steps of base station transparent transmission will not be described again.

[0057] S22. The core network equipment sends an authentication request, and the terminal receives the authentication request accordingly.

[0058] S23. The terminal sends an authentication response, and the core network equipment receives the authentication response accordingly.

[0059] S24. The core network device sends a secure mode command, and the terminal receives the secure mode command accordingly.

[0060] S25. The terminal sends a Secure mode command complete message, and the core network receives the Secure mode command complete message accordingly.

[0061] S26. The core network equipment sends a Registration Accept message, and the terminal receives the Registration Accept message accordingly.

[0062] The registration acceptance message contains a fifth field and a sixth field. The fifth field indicates that the mobility registration update of the first UICC was successful, and the sixth field indicates the updated temporary identity authentication information of the first UICC. The updated temporary identity authentication information is the temporary identity authentication information updated in this mobility registration update process.

[0063] The first UICC's successful mobility registration update and temporary identity authentication information are included in the mobility registration update information. In addition, the mobility registration update information also includes other information such as the tracking area list.

[0064] In some implementations, the registration acceptance message also includes a new seventh and eighth field. The seventh field indicates the result of the additional update request. In one example, the value of the seventh field is a boolean value. For example, a value of true indicates that the additional update request was successful, and a value of false indicates that the additional update request failed.

[0065] If the seventh field indicates that the additional update request was successful, the eighth field indicates the temporary identity authentication identifier information newly assigned by the network to the second UICC. Examples of temporary identity identifier information are 5g-GUTI or 5g-S-TMSI.

[0066] If the seventh field indicates that the additional update request failed, the eighth field is a preset reason value indicating the failure (representing the reason for the failure).

[0067] In some implementations, the registration acceptance message also includes a seventh field indicating that the additional update request failed, but excludes the eighth field. That is, in the event of a failed additional update request, the registration acceptance message does not include the eighth field to save transmission resources.

[0068] The failure of the additional update request means that the mobility registration update of the second UICC failed via the first registration request message, but since the network sent a registration acceptance message, the mobility registration update of the first UICC was successful.

[0069] In some implementations, the first registration request message is triggered and sent by the first UICC or related components. After receiving the registration acceptance message, if the mobility registration update of the second UICC is successful, the first UICC sends the temporary identity authentication information of the second UICC as indicated in the registration acceptance message to the second UICC. If the mobility registration update of the second UICC fails, the first UICC sends the mobility registration update failure information to the second UICC, so that the second UICC can independently carry out the mobility registration update process.

[0070] It is understood that the fields included in the registration acceptance message described in this embodiment are merely examples, and the registration acceptance message may also include other fields.

[0071] S27. The terminal sends a "Register complete" message, and the core network equipment receives the "Register complete" message accordingly.

[0072] The process provided in this embodiment performs mobility registration update of the second UICC simultaneously during the mobility registration update of the first UICC. Therefore, it is possible to update the tracking area of ​​the first UICC and the tracking area of ​​the second UICC in a single mobility registration update process, thus saving signaling overhead.

[0073] It is understandable that if the additional update request fails in the above process, the second UICC also needs to perform mobility registration update, as shown in Figure 3. In this embodiment, the first UICC is referred to as card 1 and the second UICC is referred to as card 2, and it is assumed that card 1 triggers the sending of the first registration request message.

[0074] Figure 3 includes steps S301-S307. Steps S301-S307 can be found in steps S21-S27 of Figure 2, and will not be repeated here.

[0075] In S306, this embodiment assumes that the core network device sends a second registration acceptance message. In this case, the following steps are performed:

[0076] S308. If the mobility registration update conditions of SIM 2 are met, the terminal sends a second registration request message, and the core network equipment receives the second registration request message accordingly.

[0077] The second registration request message sent in this step is of the mobility registration update type.

[0078] The second registration request message is used to request an update to the tracking area of ​​card 2, but not to request an update to the tracking area of ​​card 1. That is, the registration request message sent in this step is the registration request message for mobility registration update as specified in the existing protocol, which is different from the first registration request message sent by card 1 in the above embodiment.

[0079] In some implementations, the second registration request message is triggered and sent by card 2.

[0080] S309. The core network equipment sends an authentication request, and the terminal receives the authentication request accordingly.

[0081] S310: The terminal sends an authentication response, and the core network equipment receives the authentication response accordingly.

[0082] S311. The core network device sends a secure mode command, and the terminal receives the secure mode command accordingly.

[0083] S312. The terminal sends a secure mode command complete message, and the core network receives the secure mode command complete message accordingly.

[0084] S313, the core network equipment sends a registration accept message, and the terminal receives the registration accept message accordingly.

[0085] In this embodiment, taking the successful mobility registration update of card 2 as an example, the message transmitted in S313 is the registration acceptance message. If the mobility registration update of card 3 fails, the message will be transmitted according to the existing protocol, which will not be elaborated here.

[0086] S314. The terminal sends a registration complete message, and the core network equipment receives the registration complete message accordingly.

[0087] The process described in this embodiment is executed when SIM 1 fails to update the tracking area of ​​SIM 2 (i.e., SIM 2's mobility registration update fails). In other words, SIM 2 performs a mobility registration update independently. SIM 2 can request to update the tracking area of ​​SIM 1 at the same time (i.e., perform a mobility registration update of SIM 1), or it can choose not to request to update the tracking area of ​​SIM 1. In either case, SIM 2 can update the tracking area in a timely manner to ensure normal communication functions.

[0088] It is understandable that after the core network receives the mobility registration update request, the terminal's mobility registration update may fail for some reason. For example, in the process shown in Figure 2, the first UICC may receive a registration rejection message instead of a registration acceptance message. In this case, the first UICC cannot communicate normally. In order to ensure that the second UICC can communicate normally, and thus ensure that the terminal can at least communicate normally based on the second UICC, in the embodiments of this application, the network indicates in the registration rejection message that the mobility registration update of the second UICC has failed, or does not respond to the mobility registration update request of the second UICC indicated by the first registration request message in S21 (such as the third field and the fourth field).

[0089] Figure 4 is an example of the composition of a communication device provided in an embodiment of this application. The communication device can be a terminal, including but not limited to mobile phones, smart wearable devices (such as smartwatches), and other electronic devices. Taking a mobile phone as an example, the communication device may include a processor 410, internal memory 420, display screen 430, antenna 1, antenna 2, mobile communication module 440, and wireless communication module 450, etc.

[0090] It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the communication device. In other embodiments, the communication device may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0091] Processor 410 may include one or more processing units, such as application processor (AP), modem processor, digital signal processor (DSP) and / or baseband processor.

[0092] Internal memory 420 can be used to store executable program code, which includes instructions. Processor 410 performs various functions of the electronic device by executing the instructions stored in internal memory 420.

[0093] The wireless communication function of electronic devices can be realized through antenna 1, antenna 2, mobile communication module 440, wireless communication module 450, modem processor and baseband processor, etc.

[0094] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals.

[0095] The mobile communication module 440 can provide solutions for wireless communication applications, including 2G / 3G / 4G / 5G, in electronic devices.

[0096] In some embodiments, the mobile communication module 440 includes a communication interface coupled to the processor 410. This communication interface may be a transceiver or an input / output interface. In some embodiments, when the communication device is a chip configured in a terminal, the communication interface may be an input / output interface.

[0097] The wireless communication module 450 can provide solutions for wireless communication applications in electronic devices, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies.

[0098] In addition, an operating system runs on top of the aforementioned components. Examples include iOS, Android, and Windows. Applications can be installed and run on this operating system.

[0099] This application also provides a communication device.

[0100] As shown in Figure 5, the communication device 500 can correspondingly implement the functions or steps implemented by the core network equipment in the above-described method embodiments. The communication device 500 includes a transceiver module 501. In some embodiments, the communication device may further include a storage module 502 and a processing module 503. The storage module can be used to store instructions (code or programs) and / or data. The transceiver module 501 can be coupled to the storage module 502. The above modules can be set independently, or partially or completely integrated.

[0101] In one possible design, the communication device 500 may correspond to the core network device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the core network device. The communication device 500 can be used to perform the steps or processes performed by the core network device in any of the above method embodiments.

[0102] For example, the transceiver module 501 is configured to receive a registration request message for mobility registration update of a first UICC and a second UICC; and send a first registration acceptance message or a second registration acceptance message, wherein the first registration acceptance message indicates mobility registration update information of the first UICC and the second UICC, and the second registration acceptance message indicates that the mobility registration update information of the first UICC and the mobility registration update of the second UICC failed.

[0103] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0104] In one possible design, the communication device 500 may correspond to the terminal in the above method embodiments, or a component (such as a circuit, chip, or chip system) configured in the terminal. The communication device 500 can be used to execute the steps or processes performed by the terminal in any of the above method embodiments.

[0105] For example, the processing module 503 is used to determine that the mobility registration update conditions of the first general-purpose integrated circuit card (UICC) and the second general-purpose integrated circuit card (UICC) are met, and the transceiver module 501 is used to send a first registration request message when the mobility registration update conditions of the first general-purpose integrated circuit card (UICC) and the second general-purpose integrated circuit card (UICC) are met. The first registration request message is used for the mobility registration update of the first UICC and the second UICC.

[0106] Figure 6 is another schematic block diagram of the communication device 600 provided in an embodiment of this application. The communication device 600 may be a chip, chip system, or processor, etc., used by a terminal or core network device to implement the above-described methods. The communication device 600 can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.

[0107] As shown in Figure 6, the communication device 600 may include one or more processors 610, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 610 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device 600 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0108] In an alternative design, the processor 610 may also store instructions and / or data that can be executed by the processor 610 to cause the communication device 600 to perform the methods described in the above method embodiments.

[0109] In another alternative design, the communication device 600 may include a communication interface 620 for implementing receiving and transmitting functions. For example, the communication interface 620 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0110] Optionally, the communication device 600 may include one or more memories 630, which may store instructions that can be executed on the processor 610, causing the communication device 600 to perform the methods described in the above method embodiments. Optionally, the memories 630 may also store data. Optionally, the processor 610 may also store instructions and / or data. The processor 610 and the memories 630 may be provided separately or integrated together.

[0111] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0112] In one implementation, the communication device 600 may correspond to the core network device in the above method embodiments, and may be used to execute the various steps and / or processes executed by the core network device in the above method embodiments. The processor 610 may be used to execute instructions stored in the memory 630, and when the processor 610 executes the instructions stored in the memory, the processor 610 is used to execute the various steps and / or processes corresponding to the core network device.

[0113] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0114] It is understood that the memory in the embodiments of this application can be volatile memory or 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 (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. 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 synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0115] An embodiment of the application also provides a computer-readable storage medium having instructions stored thereon that, when executed on an electronic device, cause the electronic device to perform the communication method described in the above embodiments.

[0116] An embodiment of the application also provides a computer program product that stores an executable program, which, when run on an electronic device, causes the electronic device to implement the communication method described in the above embodiments.

[0117] This application also provides a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods described in the above embodiments to be executed. The chip system may be composed of a chip or may include chips and other discrete devices. The chip system may include input circuitry or interfaces for transmitting information or data, and output circuitry or interfaces for receiving information or data.

[0118] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.

[0119] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0120] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0121] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, include: If the mobility registration update conditions of the first general-purpose integrated circuit card (UICC) and the second UICC are met, a first registration request message is sent. The first registration request message is used for the mobility registration update of the first UICC and the second UICC.

2. The method according to claim 1, characterized in that, The first registration request message includes a first field, a second field, a third field, and a fourth field. The first field indicates that the first UICC should perform a mobility registration update, the second field indicates the identity information of the first UICC, the third field indicates that the second UICC should perform a mobility registration update, and the fourth field indicates the identity information of the second UICC.

3. The method according to claim 1 or 2, characterized in that, Also includes: Receive a first registration acceptance message, which indicates the mobility registration update information of the first UICC and the mobility registration update information of the second UICC.

4. The method according to claim 1 or 2, characterized in that, Also includes: A second registration acceptance message is received, indicating that the mobility registration update information of the first UICC and the mobility registration update of the second UICC failed.

5. The method according to claim 4, characterized in that, Following the receipt of the second registration acceptance message, the following is also included: A second registration request message is sent, which is used by the second UICC to update its mobility registration.

6. The method according to any one of claims 1-5, characterized in that, Sending the first registration request message includes: If the request conditions are met, the first registration request message is sent. The request conditions include at least one of a first condition and a second condition. The first condition includes that the first UICC and the second UICC belong to the same operator. The second condition includes that the first UICC and the second UICC belong to the same tracking area.

7. A communication method, characterized in that, include: Receive a registration request message, which is used for the first UICC and the second UICC to perform mobility registration updates; Send a first registration acceptance message or a second registration acceptance message. The first registration acceptance message indicates the mobility registration update information of the first UICC and the mobility registration update information of the second UICC. The second registration acceptance message indicates that the mobility registration update information of the first UICC and the mobility registration update of the second UICC failed.

8. The method according to claim 7, characterized in that, The first registration acceptance message indicates the mobility registration update information of the first UICC and the mobility registration update information of the second UICC, including: The first registration acceptance message includes a fifth field, a sixth field, a seventh field, and an eighth field. The fifth field indicates that the mobility registration of the first UICC has been successfully updated. The sixth field indicates the updated identity information of the first UICC. The seventh field indicates that the mobility registration of the second UICC has been successfully updated. The eighth field indicates the updated identity information of the second UICC.

9. The method according to claim 7, characterized in that, The second registration acceptance message indicates that the mobility registration update information of the first UICC and the mobility registration update of the second UICC failed, including: The second registration acceptance message includes a fifth field, a sixth field, and a seventh field. The fifth field indicates that the mobility registration update of the first UICC was successful, the sixth field indicates the updated identity information of the first UICC, and the seventh field indicates that the mobility registration update of the second UICC failed.

10. A communication device, characterized in that, include: Memory is used to store computer programs or computer instructions; A processor for executing a computer program or computer instructions stored in the memory, causing the communication device to perform the method as described in any one of claims 1 to 6, or the method as described in any one of claims 7 to 9.

11. A computer-readable storage medium, characterized in that, Used to store a computer program, which, when executed, is used to implement the method of any one of claims 1 to 9.

12. A computer program product, characterized in that, When the computer program product is run on an electronic device, it causes the electronic device to perform the method as described in any one of claims 1 to 9.

13. A chip system, characterized in that, include: At least one processor and an interface, the interface being used to receive code instructions and transmit them to the at least one processor; The at least one processor executes the code instructions to implement the method according to any one of claims 1 to 9.

Images