A method and communication apparatus for user identity association

Abstract

The application provides a method for associating user identities, which comprises the following steps: a first device receives a first message from a terminal device, the first message is sent by the terminal device in a first user identity, the first message is used for indicating a request of associating the first user identity with a second user identity, and the first message is also used for indicating information of the second user identity; the first device sends a second message to a second device according to the information of the second user identity, and the second message is used for indicating the request of associating the first user identity with the second user identity. The method provided by the application can associate two user identities on one terminal device, so that the purpose of optimizing a communication system is achieved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method and apparatus for user identity association. Background Technology

[0002] With the development of communication technology, many mobile terminals can simultaneously include two user identities. For example, a mobile terminal can have two subscriber identity module (SIM) cards installed at the same time, and both cards can be online and on standby simultaneously. When the two user identities in a mobile terminal belong to the same operator, the communication system can be further optimized. For example, one user identity can proxy the paging, handover, and tracking area update (TAU) of the other user identity to save network resources and reduce the power consumption of the mobile terminal. However, the above optimization is based on the premise that the network can associate the two user identities with the same mobile terminal. Summary of the Invention

[0003] This application provides a method for associating user identities, so as to associate two user identities on the same terminal device.

[0004] In a first aspect, a method for associating user identities is provided. This method is used in a network communication system, which includes a terminal device, a first device, and a second device. The terminal device includes a first user identity and a second user identity. The first device serves the first user identity, and the second device serves the second user identity. The method includes: the first device receiving a first message from the terminal device, the first message being sent by the terminal device using the first user identity, the first message indicating a request to associate the first user identity with the second user identity, and the first message further indicating information about the second user identity; and the first device sending a second message to the second device based on the information about the second user identity, the second message indicating a request to associate the first user identity with the second user identity.

[0005] Based on the above technical solution, a first user identity in a terminal device can send a second message to a second device serving a second user identity through the first device serving it, requesting the association between the first user identity and the second user identity. This allows two user identities to be associated on the same terminal device.

[0006] In conjunction with the first aspect, in some implementations of the first aspect, the first message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0007] In conjunction with the first aspect, in some implementations of the first aspect, the second message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0008] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first device receiving a third message from the second device, the third message being used by the first device to determine that the first user identity is associated with the second user identity, and the third message also being used to indicate information about the first user identity.

[0009] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first device sending a fourth message to the terminal device based on the third message, the fourth message being used by the terminal device to determine that the first user identity is associated with the second user identity.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: after receiving the first message, the first device determines whether to allow the first user identity to be associated with the second user identity based on at least one of the following information: the capability information of the first device, the subscription information of the first user identity, and the location information of the terminal device.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first device sending a fifth message to the terminal device based on the information of the first user identity, the fifth message being used to indicate that the first user identity is allowed to be associated with the second user identity.

[0012] In conjunction with the first aspect, in some implementations of the first aspect, before the first device receives the first message from the terminal device, the method further includes: the first device sending first indication information to the terminal device, the first indication information being used to indicate whether the first device supports user identity association.

[0013] In conjunction with the first aspect, in some implementations of the first aspect, after the first user identity and the second user identity are associated, the method further includes: the first device receiving a sixth message from the terminal device, the sixth message being sent by the terminal device in the form of the first user identity, the sixth message being used to indicate a request to terminate the association between the first user identity and the second user identity, and the sixth message also being used to indicate information about the second user identity.

[0014] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first device sending a seventh message to the second device based on the information of the second user identity, the seventh message being used to indicate the termination of the association between the first user identity and the second user identity.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, the sixth message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, the seventh message may also include one or more of the following: agent paging cancellation instruction, agent TAU ​​cancellation instruction, and agent switching cancellation instruction.

[0017] Secondly, a method for associating user identities is provided. This method is used in a network communication system, which includes a terminal device, a first device, and a second device. The terminal device includes a first user identity and a second user identity. The first device serves the first user identity, and the second device serves the second user identity. The method includes: the second device receiving a second message from the first device, the second message being sent by the first device based on a first message from the terminal device. The first message is sent by the terminal device using the first user identity, and is used to indicate a request to associate the first user identity with the second user identity. The first message also indicates information about the second user identity. The second device then sends a third message to the first device, the third message being used by the first device to determine that the first user identity is associated with the second user identity. The third message also indicates information about the first user identity.

[0018] Based on the above technical solution, a first user identity in a terminal device can send a second message to a second device serving a second user identity through the first device serving it, requesting the association between the first user identity and the second user identity. Furthermore, a third message sent by the second device to the first device can be used by the first device to determine the association between the first user identity and the second user identity. Thus, two user identities can be associated on the same terminal device.

[0019] In conjunction with the second aspect, in some implementations of the second aspect, the first message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0020] In conjunction with the second aspect, in some implementations of the second aspect, the second message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0021] In conjunction with the second aspect, in some implementations of the second aspect, before the second device sends a third message to the first device, the method further includes: the second device receiving an eighth message from the terminal device, the eighth message being sent by the terminal device in the identity of the second user, the eighth message being used to indicate a request to associate the first user identity with the second user identity, and the eighth message also being used to indicate information about the first user identity.

[0022] In conjunction with the second aspect, in some implementations of the second aspect, the eighth message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0023] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: after receiving the eighth message, the second device determines whether to allow the first user identity to be associated with the second user identity based on at least one of the following information: the capability information of the second device, the subscription information of the second user identity, and the location information of the terminal device.

[0024] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: the second device sending a ninth message to the terminal device, the ninth message indicating that the first user identity is allowed to be associated with the second user identity.

[0025] In conjunction with the second aspect, in some implementations of the second aspect, before the second device sends a third message to the first device, the method further includes: the second device sending a tenth message to the terminal device, the tenth message indicating whether the first user identity is allowed to be associated with the second user identity, and the tenth message also indicating information about the first user identity.

[0026] In conjunction with the second aspect, in some implementations of the second aspect, the tenth message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0027] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: the second device receiving an eleventh message from the terminal device, the eleventh message being sent by the terminal device in the identity of the second user, the eleventh message being used to indicate that the first user identity is allowed to be associated with the second user identity.

[0028] In conjunction with the second aspect, in some implementations of the second aspect, before the second device receives the second message from the first device, the method further includes: the second device sending second indication information to the terminal device, the second indication information being used to indicate whether the second device allows user identity association.

[0029] In conjunction with the second aspect, in some implementations of the second aspect, before the second device sends a third message to the first device, the method further includes: the second device determining, based on the second message and at least one of the following information, whether to allow the association of the first user identity with the second user identity: capability information of the second device, subscription information of the second user identity, and location information of the terminal device.

[0030] In conjunction with the second aspect, in some implementations of the second aspect, before the second device sends a third message to the first device, the method further includes: the second device determining, based on the second message and whether an eighth message is received, whether to allow the first user identity to be associated with the second user identity.

[0031] In conjunction with the second aspect, in some implementations of the second aspect, after the first user identity and the second user identity are associated, the method further includes: the second device receiving a seventh message from the first device, the seventh message being sent by the first device based on a sixth message from the terminal device, the sixth message being sent by the terminal device in the form of the first user identity, the sixth message being used to indicate a request to terminate the association between the first user identity and the second user identity, the sixth message also being used to indicate information about the second user identity, and the seventh message being used to indicate the termination of the association between the first user identity and the second user identity.

[0032] In conjunction with the second aspect, in some implementations of the second aspect, the sixth message may also include one or more of the following: agent paging cancellation instruction, agent TAU ​​cancellation instruction, and agent switching cancellation instruction.

[0033] In conjunction with the second aspect, in some implementations of the second aspect, the seventh message may also include one or more of the following: agent paging cancellation instruction, agent TAU ​​cancellation instruction, and agent switching cancellation instruction.

[0034] Thirdly, a method for associating user identities is provided. This method is used in a network communication system, which includes a terminal device, a first device, and a second device. The terminal device includes a first user identity and a second user identity. The first device serves the first user identity, and the second device serves the second user identity. The method includes: the terminal device sending a first message to the first device using the first user identity, the first message indicating a request to associate the first user identity with the second user identity, and the first message further indicating information about the second user identity; the terminal device receiving a fourth message from the first device using the first user identity, the fourth message being sent by the first device based on a third message, the third message used by the first device to determine that the first user identity is associated with the second user identity, the third message further indicating information about the first user identity, and the fourth message used by the terminal device to determine that the first user identity is associated with the second user identity.

[0035] Based on the above technical solution, a first user identity in a terminal device can send a second message to a second device serving a second user identity through the first device serving that first user identity, requesting the association between the first user identity and the second user identity. Furthermore, the terminal device can determine the association between the first user identity and the second user identity based on a fourth message received from the first device. Thus, two user identities can be associated on the same terminal device.

[0036] In conjunction with the third aspect, in some implementations of the third aspect, the first message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0037] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: the terminal device receiving a fifth message from the first device as the first user identity, the fifth message being used to indicate that the first user identity is allowed to be associated with the second user identity.

[0038] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: the terminal device sending an eighth message to the second device in the identity of the second user, the eighth message being used to indicate a request to associate the first user identity with the second user identity, the eighth message containing or indicating information about the first user identity.

[0039] In conjunction with the third aspect, in some implementations of the third aspect, the eighth message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0040] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: the terminal device receiving a ninth message from the second device as the second user identity, the ninth message being used to indicate that the first user identity is allowed to be associated with the second user identity.

[0041] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: the terminal device receiving a tenth message from the second device as the second user identity, the tenth message being used to indicate whether the first user identity is allowed to be associated with the second user identity, and the tenth message also being used to indicate information about the first user identity.

[0042] In conjunction with the third aspect, in some implementations of the third aspect, the tenth message may include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0043] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: the terminal device determining that the first user identity is allowed to be associated with the second user identity; the terminal device sending an eleventh message to the second device using the second user identity, the eleventh message indicating that the first user identity is allowed to be associated with the second user identity.

[0044] In conjunction with the third aspect, in some implementations of the third aspect, after the first user identity and the second user identity are associated, the method further includes: the terminal device sending a sixth message to the first device using the first user identity, the sixth message being used to request an indication to terminate the association between the first user identity and the second user identity, and the sixth message also being used to indicate information about the second user identity.

[0045] In conjunction with the third aspect, in some implementations of the third aspect, the sixth message may also include one or more of the following: agent paging cancellation instruction, agent TAU ​​cancellation instruction, and agent switching cancellation instruction.

[0046] Fourthly, a communication device is provided, including a transceiver unit and a processing unit. The transceiver unit is configured to: receive a first message from a terminal device, the first message being sent by the terminal device in the identity of a first user, the first message indicating a request to associate the first user identity with a second user identity, and the first message further indicating information about the second user identity; the transceiver unit is further configured to: send a second message to a second device based on the information about the second user identity, the second message indicating a request to associate the first user identity with the second user identity; the transceiver unit is further configured to: receive a third message from the second device, the third message being used by the first device to determine that the first user identity is associated with the second user identity, the third message further indicating information about the first user identity; the transceiver unit is further configured to: send a fourth message to the terminal device based on the third message, the fourth message being used by the terminal device to determine that the first user identity is associated with the second user identity.

[0047] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0048] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the second message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0049] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the processing unit is configured to: determine whether the association between the first user identity and the second user identity is permitted based on at least one of the following information: capability information of the first device, subscription information of the first user identity, and location information of the terminal device.

[0050] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further configured to: send a fifth message to the terminal device based on the information of the first user identity, the fifth message being used to indicate that the first user identity is allowed to be associated with the second user identity.

[0051] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further configured to: send first indication information to the terminal device, the first indication information being used to indicate whether the first device supports user identity association.

[0052] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further configured to: receive a sixth message from the terminal device, the sixth message being sent by the terminal device in the identity of the first user, the sixth message being used to indicate a request to terminate the association between the first user identity and the second user identity, and the sixth message being used to indicate information about the second user identity.

[0053] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further configured to: send a seventh message to the second device based on the information of the second user identity, the seventh message being used to indicate the termination of the association between the first user identity and the second user identity.

[0054] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the sixth message may also include one or more of the following: agent paging cancellation instruction, agent TAU ​​cancellation instruction, and agent switching cancellation instruction.

[0055] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the seventh message may also include one or more of the following: agent paging cancellation instruction, agent TAU ​​cancellation instruction, and agent switching cancellation instruction.

[0056] Fifthly, a communication apparatus is provided, including a transceiver unit and a processing unit. The transceiver unit is configured to: receive a second message from a first device, the second message being sent by the first device based on a first message from a terminal device, the first message being sent by the terminal device in the identity of a first user, the first message being used to indicate a request to associate the first user identity with a second user identity, the first message also being used to indicate information about the second user identity; the transceiver unit is further configured to: send a third message to the first device, the third message being used by the first device to determine that the first user identity is associated with the second user identity, the third message also being used to indicate information about the first user identity.

[0057] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0058] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the second message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0059] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the transceiver unit is further configured to: receive an eighth message from the terminal device, the eighth message being sent by the terminal device in the identity of the second user, the eighth message being used to indicate a request to associate the first user identity with the second user identity, and the eighth message being used to indicate information about the first user identity.

[0060] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the eighth message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0061] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the processing unit is configured to: determine whether the association between the first user identity and the second user identity is permitted based on at least one of the following information: capability information of the second device, subscription information of the second user identity, and location information of the terminal device.

[0062] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the transceiver unit is further configured to: send a ninth message to the terminal device, the ninth message being used to indicate that the first user identity is allowed to be associated with the second user identity.

[0063] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the transceiver unit is further configured to: send a tenth message to the terminal device, the tenth message being used to indicate whether the first user identity is allowed to be associated with the second user identity, and the tenth message being used to indicate information about the first user identity.

[0064] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the tenth message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0065] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the transceiver unit is further configured to: receive an eleventh message from the terminal device, the eleventh message being sent by the terminal device in the identity of the second user, the eleventh message being used to indicate that the first user identity is allowed to be associated with the second user identity.

[0066] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the transceiver unit is further configured to: send a second indication message to the terminal device, the second indication message being used to indicate whether the second device allows user identity association.

[0067] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the processing unit is further configured to: determine, based on the second message and at least one of the following information, whether the association between the first user identity and the second user identity is permitted: capability information of the second device, subscription information of the second user identity, and location information of the terminal device.

[0068] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the processing unit is further configured to: determine whether to allow the first user identity to be associated with the second user identity based on the second message and whether the eighth message is received.

[0069] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the transceiver unit is further configured to: receive a seventh message from the first device, the seventh message being sent by the first device based on a sixth message from the terminal device, the sixth message being sent by the terminal device in the identity of the first user, the sixth message being used to indicate a request to terminate the association between the first user identity and the second user identity, the sixth message also being used to indicate information about the second user identity, and the seventh message being used to indicate the termination of the association between the first user identity and the second user identity.

[0070] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the sixth message may also include one or more of the following: agent paging cancellation instruction, agent TAU ​​cancellation instruction, and agent switching cancellation instruction.

[0071] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the seventh message may also include one or more of the following: agent paging cancellation instruction, agent TAU ​​cancellation instruction, and agent switching cancellation instruction.

[0072] In a sixth aspect, a communication device is provided, including a transceiver unit and a processing unit. The transceiver unit is configured to: send a first message to a first device in the identity of a first user, the first message indicating a request to associate the first user identity with a second user identity, the first message further indicating information about the second user identity; the transceiver unit is further configured to: receive a fourth message from the first device in the identity of the first user, the fourth message being sent by the first device based on a third message, the third message being used by the first device to determine that the first user identity is associated with the second user identity, the third message further indicating information about the first user identity, and the fourth message being used by a terminal device to determine that the first user identity is associated with the second user identity.

[0073] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the first message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0074] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the transceiver unit is further configured to: receive a fifth message from the first device in the identity of the first user, the fifth message being used to indicate that the first user identity is allowed to be associated with the second user identity.

[0075] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the transceiver unit is further configured to: send an eighth message to the second device in the identity of the second user, the eighth message being used to indicate a request to associate the first user identity with the second user identity, the eighth message containing or indicating information of the first user identity.

[0076] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the eighth message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0077] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the transceiver unit is further configured to: receive a ninth message from the second device in the identity of the second user, the ninth message being used to indicate that the first user identity is allowed to be associated with the second user identity.

[0078] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the transceiver unit is further configured to: receive a tenth message from the second device in the identity of the second user, the tenth message being used to indicate whether the first user identity is allowed to be associated with the second user identity, the tenth message including or indicating information of the first user identity.

[0079] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the tenth message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0080] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the processing unit is configured to: determine whether the first user identity is allowed to be associated with the second user identity; the transceiver unit is further configured to: send an eleventh message to the second device using the second user identity, the eleventh message being used to indicate whether the first user identity is allowed to be associated with the second user identity.

[0081] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the transceiver unit is further configured to: send a sixth message to the first device in the identity of the first user, the sixth message being used to request an instruction to terminate the association between the first user identity and the second user identity, and the sixth message also being used to indicate information about the second user identity.

[0082] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the sixth message may also include one or more of the following: agent paging cancellation instruction, agent TAU ​​cancellation instruction, and agent switching cancellation instruction.

[0083] A seventh aspect provides a communication device including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the methods described in the first aspect and any possible implementation thereof. The communication device further includes a memory. The communication device also includes a communication interface, and the processor is coupled to the communication interface.

[0084] In one implementation, the communication device is a first device. When the communication device is a first device, the communication interface can be a transceiver or an input / output interface.

[0085] In another implementation, the communication device is a chip or chip system configured in the first device. When the communication device is a chip or chip system configured in the first device, the communication interface can be an input / output interface.

[0086] The transceiver can be a transceiver circuit. The input / output interface can be an input / output circuit.

[0087] Eighthly, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the methods of the second aspect and any possible implementation thereof. The communication device further includes a memory. The communication device also includes a communication interface, and the processor is coupled to the communication interface.

[0088] In one implementation, the communication device is a second device. When the communication device is a second device, the communication interface can be a transceiver or an input / output interface.

[0089] In another implementation, the communication device is a chip or chip system configured in the second device. When the communication device is a chip or chip system configured in the second device, the communication interface can be an input / output interface.

[0090] The transceiver can be a transceiver circuit. The input / output interface can be an input / output circuit.

[0091] A ninth aspect provides a communication device including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the methods of the third aspect and any possible implementation thereof. The communication device further includes a memory. The communication device also includes a communication interface, and the processor is coupled to the communication interface.

[0092] In one implementation, the communication device is a terminal device. When the communication device is a terminal device, the communication interface can be a transceiver or an input / output interface.

[0093] In another implementation, the communication device is a chip or chip system configured in a terminal device. When the communication device is a chip or chip system configured in a terminal device, the communication interface can be an input / output interface.

[0094] The transceiver can be a transceiver circuit. The input / output interface can be an input / output circuit.

[0095] A tenth aspect provides a processor, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the methods of the first to third aspects and any possible implementation thereof.

[0096] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0097] Eleventhly, a processing apparatus is provided, including a processor and a memory. The processor is configured to read instructions stored in the memory, receive signals via a receiver, and transmit signals via a transmitter to execute the methods of the first to third aspects and any possible implementation thereof.

[0098] The processor may be one or more, and the memory may be one or more.

[0099] The memory can be integrated with the processor, or it can be set up separately from the processor.

[0100] In the specific implementation process, the memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or set on different chips. The embodiments of this application do not limit the type of memory or the way the memory and processor are set.

[0101] It should be understood that the relevant data interaction process, such as sending indication information, can be the process of the processor outputting indication information, and receiving capability information can be the process of the processor receiving input capability information. Specifically, the data output by the processor can be sent to the transmitter, and the input data received by the processor can come from the receiver. Here, the transmitter and receiver can be collectively referred to as a transceiver.

[0102] The processing device described in the eleventh aspect above can be one or more chips, or it can be a chip system. The processor in the processing device can be implemented in hardware or in software. When implemented in hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. This memory can be integrated into the processor or located outside the processor and exist independently.

[0103] In a twelfth aspect, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions) that, when the computer program is run, causes the methods of the first to third aspects and any possible implementation thereof to be performed.

[0104] In a thirteenth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the methods described in the first to third aspects and any possible implementation thereof.

[0105] In a fourteenth aspect, a communication system is provided, comprising: the aforementioned terminal device, and / or, the aforementioned first device and second device. Attached Figure Description

[0106] Figure 1 This is a schematic diagram of a communication system applicable to the methods provided in the embodiments of this application.

[0107] Figures 2 to 5 This is a schematic flowchart illustrating the user identity association method provided in the embodiments of this application.

[0108] Figure 6 This is a schematic block diagram of a communication device provided in an embodiment of this application.

[0109] Figure 7 This is a schematic block diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0110] The implementation of this embodiment will now be described in detail with reference to the accompanying drawings.

[0111] The technical solutions of this application embodiment can be applied to communication systems, such as: Global System for Mobile Communications (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5th Generation (5G) system and its future evolution networks or New Radio (NR), satellite communication systems, etc.

[0112] It should be understood that the embodiments of this application do not particularly limit the specific structure of the execution subject of the method provided in the embodiments of this application. As long as a program that records the code of the method provided in the embodiments of this application can be run to communicate according to the method provided in the embodiments of this application.

[0113] To facilitate understanding of the embodiments of this application, firstly, in conjunction with Figure 1 The application scenarios applicable to the embodiments of this application are described in detail.

[0114] Figure 1 A network communication system applicable to the methods provided in the embodiments of this application is illustrated. For example... Figure 1As shown, the communication system 100 may include a terminal device, which may include user identity #1 and user identity #2. The terminal device can register to the network using either user identity #1 or user identity #2. User identity #1 can be any of the following: a Universal Subscriber Identity Module (USIM) card, a SIM card, or an embedded subscriber identity module (eSIM) card; this embodiment does not limit this. User identity #2 can be any of the following: a USIM card, a SIM card, or an eSIM card; this embodiment does not limit this.

[0115] The communication system 100 may further include a first device and a second device. The first device serves user identity #1, and the second device serves user identity #2. This application does not limit the specific form of the first and second devices. For example, in a 4th generation (4G) system, both the first and second devices can be mobility management entities (MMEs); in a 5G system, both the first and second devices can be access and mobility management functions (AMFs); or, the first device can be an MME and the second device can be an AMF; or, the first device can be an AMF and the second device can be an MME.

[0116] When user identity #1 and user identity #2 belong to the same operator, the communication system can be further optimized. For example, user identity #1 can act as a proxy for user identity #2's paging, handover, and TAU updates; or, user identity #2 can act as a proxy for user identity #1's paging, handover, and TAU updates, thereby saving network resources and reducing terminal device power consumption. However, achieving the above optimizations requires that the network to which the terminal device belongs needs to know that the two user identities are on the same terminal device. The network needing to know that the two user identities are on the same terminal device can also be understood as the network associating the two user identities with the same terminal device.

[0117] In view of this, this application proposes a method for associating user identities, with the aim of associating two user identities on the same terminal device.

[0118] The user identity association method provided in the embodiments of this application is described in detail below with reference to the accompanying drawings. For ease of explanation, the embodiments of this application are illustrated using the example where both the first device and the second device are AMFs, but this should not be construed as limiting the application. AMF#1 corresponds to the first device, and AMF#2 corresponds to the second device.

[0119] Figure 2 A schematic flowchart illustrating the user identity association method provided in an embodiment of this application is shown. Figure 2 The method 200 shown can be applied to Figure 1 The communication system shown, the method 200 can be made by Figure 1 The terminal device, the first device, and the second device shown execute the commands. For example... Figure 2 As shown, the method 200 may include steps S201-S204, and each step is described in detail below.

[0120] S201, the terminal device sends a first message to AMF#1 (an example of the first device).

[0121] In this process, the terminal device sends a first message to AMF#1 using user identity #1 (an example of the first user identity). The first message is used to indicate that user identity #1 is to be associated with user identity #2 (an example of the second user identity). The first message is also used to indicate information about user identity #2, or the first message may also include information about user identity #2.

[0122] This application does not limit the specific form of the user identity #2 information. For example, the user identity #2 information can be a globally unique temporary identity (GUTI) (for example, for 5G, it can be a 5G GUTI).

[0123] Optionally, the first message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, and agent switching indication information.

[0124] The proxy paging indication information is used to indicate that user identity #1 is requested to act as a proxy for paging user identity #2. User identity #1 acting as a proxy for paging user identity #2 can be understood as follows: when the network needs to paging user identity #2, the network sends the paging of user identity #2 to the terminal device on the radio access technology (RAT) of user identity #1; correspondingly, the terminal device listens for the paging of user identity #2 on the RAT of user identity #1.

[0125] The Proxy TAU indication information is used to indicate the TAU of user identity #1 on behalf of user identity #2. The TAU of user identity #1 on behalf of user identity #2 can be understood as the terminal device interacting with the network through user identity #1 to complete the TAU of user identity #2.

[0126] The proxy switching indication information is used to indicate the switching of the proxy user identity #1 to user identity #2. The switching of the proxy user identity #1 to user identity #2 can be understood as the terminal device interacting with the network through user identity #1 to complete the switching of user identity #2.

[0127] When the first message includes one or more of the aforementioned information, the first message indicating the association between user identity #1 and user identity #2 can be understood as not only indicating the association between user identity #1 and user identity #2, but also indicating the service of user identity #1 acting as an agent for user identity #2. For example, if the first message includes proxy paging indication information, then the first message is not only used to indicate the association between user identity #1 and user identity #2, but also to indicate the paging service of user identity #1 acting as an agent for user identity #2.

[0128] Optionally, the first message can be one of the following messages: a proxy paging request message, a proxy TAU request message, or a proxy handover request message. The proxy paging request message is used to request user identity #1 to act as a proxy for user identity #2 in paging; the proxy TAU request message is used to request user identity #1 to act as a proxy for user identity #2 in TAU; and the proxy handover request message is used to request user identity #1 to act as a proxy for user identity #2 in handover.

[0129] In this case, the first message used to indicate that the requesting user identity #1 is associated with user identity #2 can be understood as the first message used to indicate that the requesting user identity #1 is acting as an agent for user identity #2.

[0130] Optionally, the first message may also include a third instruction or a fourth instruction, wherein the third instruction is used to instruct the user identity #1 to act as an agent for the user identity #2, and the fourth instruction is used to instruct the user identity #2 to act as an agent for the user identity #1.

[0131] S202, AMF#1 sends a second message to AMF#2 (an example of the second AMF).

[0132] The second message is used to indicate that the requesting user identity #1 is associated with user identity #2.

[0133] Optionally, the second message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0134] It is understandable that, since User Identity #1 and User Identity #2 belong to the same operator, AMF #1 serving User Identity #1 and AMF #2 serving User Identity #2 can communicate with each other.

[0135] As mentioned earlier, the first message received by AMF#1 from the terminal device also indicates information about user identity #2. AMF#1 can locate the AMF#2 serving user identity #2 based on this information. Further, AMF#1 sends a second message to AMF#2. This second message can be the same as the first message; for example, AMF#1 can forward the first message to AMF#2. Alternatively, the second message can be different from the first message. For example, AMF#1 decapsulates the received first message to obtain its content; then, AMF#1 encapsulates the obtained content according to its communication protocol with AMF#2 to generate the second message; and then sends the second message to AMF#2.

[0136] For example, if the first message also includes one or more of the following information: agent paging indication information, agent TAU ​​indication information, and agent switching indication information, after receiving the first message, AMF#1 can first send a second message to AMF#2 that does not include the above information. After AMF#2 determines that user identity #1 is allowed to be associated with user identity #2, AMF#1 then sends the above information to AMF#2.

[0137] Taking the first message and the second message being the same as an example, if the first message is used to indicate that user identity #1 is associated with user identity #2, then correspondingly, the second message is also used to indicate that user identity #1 is associated with user identity #2; if the first message is used to indicate that user identity #1 is associated with user identity #2 and that user identity #1 acts as an agent for user identity #2, then correspondingly, the second message is also used to indicate that user identity #1 is associated with user identity #2 and that user identity #1 acts as an agent for user identity #2; if the first message is used to indicate that user identity #1 acts as an agent for user identity #2, then correspondingly, the second message is also used to indicate that user identity #1 acts as an agent for user identity #2.

[0138] S203, AMF#2 sends a third message to AMF#1.

[0139] The third message is used by AMF#1 to determine the association between user identity #1 and user identity #2. That is, AMF#1 can determine that user identity #1 and user identity #2 are already associated based on the third message.

[0140] The third message may also be used to indicate information about user identity #1, or the third message may also include information about user identity #1.

[0141] S204, AMF#1 sends the fourth message to the terminal device.

[0142] AMF#1 sends a fourth message to the terminal device based on the third message. Correspondingly, the terminal device receives the fourth message as user identity #1. This fourth message is used by the terminal device to determine that user identity #1 and user identity #2 are associated; that is, the terminal device can determine from this fourth message that user identity #1 and user identity #2 are already associated. This fourth message may be the same as the third message, or it may be different. For example, AMF#1 may delete the information about user identity #1 carried in the third message to generate the fourth message, and then send the fourth message to AMF#2.

[0143] It is understood that the embodiments in this application are only used as examples of requesting user identity #1 to act as an agent for user identity #2, and should not be construed as limiting this application. The first and second messages can also be used to request user identity #2 to act as an agent for user identity #1.

[0144] In this embodiment, user identity #1 in the terminal device can send a second message to AMF #2, which serves user identity #2, through AMF #1. AMF #2, having allowed user identity association itself, can allow user identity #1 to associate with user identity #2, thereby establishing an association between user identity #1 and user identity #2. Furthermore, the second message may also include proxy paging indication information, proxy TAU indication information, and proxy handover indication information. Based on this second message, AMF #2 can allow user identity #1 to act as a proxy for user identity #2's related services. In this case, user identity #2 can be in a disabled state, thus saving power consumption and network resources for the terminal device.

[0145] like Figure 3 As shown, the method 200 may also include steps S205-S211, which are described in detail below.

[0146] Optionally, before S201, the method 200 may also include S205-S206.

[0147] S205, the terminal device obtains the first instruction information and the second instruction information.

[0148] The first instruction information is used to instruct AMF#1 to support user identity association, and the second instruction information is used to instruct AMF#2 to support user identity association.

[0149] This application does not limit the specific method by which the terminal device obtains the first indication information and the second indication information. For example, during the registration process of user identity #1 in the terminal device to the core network, the registration acceptance message received by the terminal device from AMF #1 may include the first indication information. For example, during the registration process of user identity #2 in the terminal device to the core network, the registration acceptance message received by the terminal device from AMF #2 may include the second indication information.

[0150] S206, Information of user identity #1 and information of user identity #2.

[0151] This means that User Identity #1 and User Identity #2 can exchange information with each other. The method by which User Identity #1 and User Identity #2 exchange information can refer to existing technologies, and will not be elaborated here for the sake of simplicity.

[0152] This application does not limit the specific form of the information of user identity #1 and user identity #2. For example, the information of user identity #1 and user identity #2 can both be 5G-GUTI.

[0153] Optionally, before S202, the method 200 may also include S207.

[0154] S207, AMF#1 sends the fifth message to the terminal device.

[0155] The fifth message is used to instruct user identity #1 to be associated with user identity #2.

[0156] Before AMF#1 sends the fifth message to the terminal device, AMF#1 can determine whether to allow user identity #1 to be associated with user identity #2.

[0157] This application embodiment does not limit the method by which AMF#1 determines whether to associate user identity #1 with user identity #2. After receiving the first message, AMF#1 may determine whether to associate user identity #1 with user identity #2 based on at least one of the following information: AMF#1 capability information, user identity #1 subscription information, and terminal device location information.

[0158] Among them, the capability information of AMF#1 indicates whether AMF#1 supports user identity association. If AMF#1 determines whether to allow user identity #1 to be associated with user identity #2 based on the capability information of AMF#1, then if AMF#1 supports user identity association, AMF#1 determines that user identity #1 can be associated with user identity #2; otherwise, it determines that user identity #1 cannot be associated with user identity #2.

[0159] The contract information of user identity #1 indicates whether the contract information of user identity #1 includes information that supports user identity association. Therefore, AMF #1 determines whether to allow user identity #1 to associate with user identity #2 based on the contract information of user identity #1. If the contract information of user identity #1 includes information that supports user identity association, AMF #1 determines to allow user identity #1 to associate with user identity #2; otherwise, it determines not to allow user identity #1 to associate with user identity #2.

[0160] The location information of the terminal device indicates that if the location of the terminal device is a pre-agreed location, user identity #1 and user identity #2 can be associated. If AMF #1 determines whether to allow user identity #1 and user identity #2 to be associated based on the location information of the terminal device, then if the location of the terminal device is a pre-agreed location, AMF #1 determines that user identity #1 and user identity #2 can be associated; otherwise, user identity #1 and user identity #2 cannot be associated.

[0161] It is understandable that if AMF#1 determines whether to allow user identity #1 to associate with user identity #2 based on two or three of the above information, then if each piece of information satisfies the above conditions, AMF#1 will determine to allow user identity #1 to associate with user identity #2; otherwise, it will not allow user identity #1 to associate with user identity #2.

[0162] Optionally, before S203, the method 200 may also include S208-S211.

[0163] S208, AMF#2 determines whether association is allowed.

[0164] As mentioned above, if the second message is used to indicate that user identity #1 is associated with user identity #2, then AMF #2 determines whether to allow user identity #1 to associate with user identity #2; if the second message is used to indicate that user identity #1 is associated with user identity #2 and that user identity #1 acts as an agent for user identity #2, then AMF #2 determines whether to allow user identity #1 to associate with user identity #2 and whether to allow user identity #1 to act as an agent for user identity #2; if the second message is used to indicate that user identity #1 acts as an agent for user identity #2, then AMF #2 determines whether to allow user identity #1 to act as an agent for user identity #2.

[0165] This application does not limit the specific method by which AMF#2 determines whether to allow user identity #1 to be associated with user identity #2.

[0166] In one implementation, AMF#2 can determine whether to allow user identity #1 to be associated with user identity #2 based on a second message and at least one of the following: AMF#2's capability information, user identity #2's subscription information, and terminal device's location information.

[0167] Among them, the capability information of AMF#2 indicates whether AMF#2 supports user identity association. If AMF#2 determines whether to allow user identity #1 to be associated with user identity #2 based on the second message and the capability information of AMF#2, then if AMF#2 supports user identity association, AMF#2 determines that user identity #1 can be associated with user identity #2; otherwise, it determines that user identity #1 cannot be associated with user identity #2.

[0168] The subscription information of user identity #2 indicates whether the subscription information of user identity #2 includes information that supports user identity association. AMF #2 determines whether to allow user identity #1 to associate with user identity #2 based on the second message and the subscription information of user identity #2. If the subscription information of user identity #2 includes information that supports user identity association, AMF #2 determines to allow user identity #1 to associate with user identity #2; otherwise, it determines not to allow user identity #1 to associate with user identity #2.

[0169] The location information of the terminal device indicates that if the location of the terminal device is a pre-agreed location, user identity #1 can be associated with user identity #2. If AMF #2 determines whether to allow user identity #1 to be associated with user identity #2 based on the second message and the location information of the terminal device, then if the location of the terminal device is a pre-agreed location, AMF #2 determines that user identity #1 can be associated with user identity #2; otherwise, user identity #1 cannot be associated with user identity #2.

[0170] It is understandable that if AMF#2 determines whether to allow user identity #1 to associate with user identity #2 based on two or three of the information in the second message and the above information, then if each information satisfies the above conditions, AMF#2 will determine to allow user identity #1 to associate with user identity #2; otherwise, it will not allow user identity #1 to associate with user identity #2.

[0171] In another implementation, AMF#2 determines whether to allow user identity #1 to associate with user identity #2 based on whether the eighth message is received. The eighth message is sent by the terminal device using user identity #2, and it indicates a request to associate user identity #1 with user identity #2. The eighth message also indicates information about user identity #1. This implementation will be described in conjunction with other embodiments later, and will not be detailed here.

[0172] In the case where the second message is used to indicate that user identity #1 is associated with user identity #2, if AMF #2 determines to allow user identity #1 to associate with user identity #2, it can be understood that AMF #2 only allows user identity #1 to associate with user identity #2, or it can be understood that AMF #2 both allows user identity #1 to associate with user identity #2 and allows user identity #1 to act as an agent for user identity #2's business.

[0173] When the second message indicates a request to associate user identity #1 with user identity #2 and for user identity #1 to act as an agent for user identity #2, AMF #2 may determine whether to allow user identity #1 to act as an agent for user identity #2 after determining whether to allow user identity #1 to associate with user identity #2; or, AMF #2 may determine whether to allow user identity #1 to act as an agent for user identity #2 simultaneously with determining whether to allow user identity #1 to associate with user identity #2. If AMF #2 first determines whether to allow user identity #1 to associate with user identity #2, then if AMF #2 determines not to allow user identity #1 to associate with user identity #2, AMF #2 may determine not to allow user identity #1 to act as an agent for user identity #2 without performing a judgment process; or, if AMF #2 determines to allow user identity #1 to associate with user identity #2, AMF #2 may determine not to allow user identity #1 to act as an agent for user identity #2 without performing a judgment process.

[0174] This application does not limit the method by which AMF#2 determines whether to allow user identity #1 to act as an agent for user identity #2.

[0175] In one implementation, AMF#2 determines whether to allow user identity #1 to act as an agent for user identity #2's business based on at least one of the following: AMF#2's capability information, user identity #2's subscription information, and terminal device's location information.

[0176] In another implementation, AMF#2 determines whether to allow user identity #1 to act as an agent for user identity #2's business based on whether user identity #1 and user identity #2 are associated. If user identity #1 and user identity #2 are not associated, it is not allowed; if user identity #1 and user identity #2 are associated, it is allowed.

[0177] In another implementation, AMF#2 determines whether to allow user identity #1 to act as an agent for user identity #2's business based on whether the eighth message has been received. This implementation will be described in detail later with reference to other embodiments, and will not be elaborated here.

[0178] S209, AMF#2 sends the tenth message to the terminal device.

[0179] Correspondingly, the terminal device receives the tenth message as user identity #2. The tenth message is used to indicate whether user identity #1 is allowed to associate with user identity #2. The tenth message is also used to indicate information about user identity #1, or the tenth message is also used to indicate information about user identity #1.

[0180] Optionally, the tenth message may also include one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

[0181] The tenth message may be the same as the second message, or it may be different from the second message. For example, AMF#2 decapsulates the received second message to obtain the specific content of the second message. Then, AMF#2 encapsulates the obtained specific content according to its communication protocol with the terminal device to generate the tenth message, and then sends the tenth message to the terminal device.

[0182] If AMF#2 determines that user identity #1 is associated with user identity #2, send the tenth message to user identity #2.

[0183] S210, User identity #2: Determine if association is possible.

[0184] This application does not limit the method by which user identity #2 determines whether user identity #1 and user identity #2 can be associated. For example, user identity #2 can determine whether user identity #1 and user identity #2 can be associated based on the subscription information of user identity #2. The subscription information of user identity #2 indicates whether the subscription information of user identity #2 includes information that supports the association of multiple user identities. If the subscription information of user identity #2 includes information that supports the association of multiple user identities, then user identity #2 determines that user identity #1 and user identity #2 can be associated; otherwise, it determines that user identity #1 and user identity #2 cannot be associated.

[0185] If user identity #2 confirms that card # and user identity #2 cannot be associated, then execution method 200 ends; if user identity #2 confirms that user identity #1 and user identity #2 can be associated, then execution S211 is executed.

[0186] S211, the terminal device sends the eleventh message to AMF#2.

[0187] The terminal device sends an eleventh message to AMF#2 using user identity #2. The eleventh message is used to indicate that user identity #1 can be associated with user identity #2.

[0188] If user identity #2 determines that user identity #1 and user identity #2 cannot be associated, the terminal device will not send the eleventh message. Conversely, if AMF #2 does not receive the eleventh message, it determines that user identity #1 and user identity #2 cannot be associated.

[0189] Figure 4 This is a schematic flowchart illustrating a method for user identity association provided in another embodiment of this application. Figure 4 The illustrated embodiment provides a more detailed description of an example in which AMF#2, mentioned in S208, determines whether to allow user identity #1 to be associated with user identity #2 based on whether the eighth message has been received.

[0190] like Figure 4 As shown, method 300 may include steps S301-S311. Steps S301-S306 are the same as steps S201-S206 in method 200, and will not be repeated here for brevity. Other steps that differ from method 200 are described in detail below.

[0191] S307, the terminal device sends the eighth message to AMF#2 (an example of the second device).

[0192] In this process, the terminal device sends an eighth message to AMF#2 using user identity #2 (an example of the second user identity). The eighth message is used to indicate that user identity #2 is to be associated with user identity #1 (an example of the second user identity). The eighth message also contains information about user identity #1, or the eighth message may also include information about user identity #1.

[0193] Optionally, the eighth message may also include one or more of the following: proxy paging indication information, proxy TAU indication information, and proxy switching indication information. Similar to the function of the first message, when the eighth message includes the above information, the eighth message is also used to indicate the service requesting user identity #1 to act as a proxy for user identity #2.

[0194] Optionally, the eighth message can be one of the following: a proxy paging request message, a proxy TAU request message, or a proxy handover request message. Similar to the function of the first message, when the eighth message is one of the above messages, the eighth message is used to indicate the service requesting user identity #1 to act as a proxy for user identity #2.

[0195] Optionally, the eighth message may also include a third instruction or a fourth instruction, wherein the third instruction is used to instruct the user identity #1 to act as an agent for the user identity #2, and the fourth instruction is used to instruct the user identity #2 to act as an agent for the user identity #1.

[0196] S308, AMF#2 determines whether association is allowed.

[0197] After receiving the eighth message, AMF#2 can determine whether to allow user identity #1 to be associated with user identity #2 based on at least one of the following information: AMF#2's capability information, user identity #2's subscription information, and terminal device's location information.

[0198] For detailed judgment methods, please refer to the description in S208. For the sake of brevity, it will not be repeated here.

[0199] S309, AMF#2 sends the ninth message to the terminal device.

[0200] Correspondingly, the terminal device receives the ninth message as user identity #2. This ninth message is used to instruct AMF #2 to determine whether user identity #1 is associated with user identity #2.

[0201] S310, AMF#2 determines whether association is allowed.

[0202] AMF#2 determines whether to allow user identity #1 to be associated with user identity #2 based on whether the eighth message from the terminal device is received.

[0203] For example, if the second message is used to indicate that user identity #1 is to be associated with user identity #2, then when AMF #2 receives an eighth message from the terminal device, and that eighth message is also used to indicate that user identity #1 is to be associated with user identity #2, AMF #2 determines to allow user identity #1 to be associated with user identity #2.

[0204] For example, if the second message is used to indicate the request for user identity #1 to associate with user identity #2 and for user identity #1 to act as an agent for user identity #2, then when AMF #2 receives the eighth message from the terminal device, and this eighth message is also used to indicate the request for user identity #1 to associate with user identity #2 and for user identity #1 to act as an agent for user identity #2, AMF #2 allows user identity #1 to associate with user identity #2 and for user identity #1 to act as an agent for user identity #2. If the eighth message indicates the request for user identity #1 to associate with user identity #2, AMF #2 first determines that user identity #1 can associate with user identity #2. If the eighth message indicates the request for user identity #1 to associate with user identity #2 and for user identity #2 to act as an agent for user identity #1, AMF #2 first determines that user identity #1 can associate with user identity #2, and then determines the order in which the second and eighth messages are received. If the second message is received first, then user identity #1 can act as an agent for user identity #2; if the eighth message is received first, then user identity #2 can act as an agent for user identity #1.

[0205] For example, if the second message is used to indicate a request for user identity #1 to act as an agent for user identity #2, then when AMF #2 receives the eighth message from the terminal device, and the eighth message is also used to indicate a request for user identity #1 to act as an agent for user identity #2, AMF #2 determines to allow user identity #1 to act as an agent for user identity #2. If the eighth message is used to request user identity #2 to act as an agent for user identity #1, AMF #2 determines the order in which the second message and the eighth message are received. If the second message is received first, then it determines to allow user identity #1 to act as an agent for user identity #2; if the eighth message is received first, then it determines to allow user identity #2 to act as an agent for user identity #1.

[0206] S311, User ID #2 sends the twelfth message to User ID #1.

[0207] The twelfth message is used by user identity 1 to determine that user identity #1 is allowed to associate with user identity #2. That is, user identity #1 can determine that user identity #1 and user identity #2 are in an associated state based on the twelfth message.

[0208] In this embodiment, user identity #1 in the terminal device can send a second message to AMF #2 serving user identity #2 through AMF #1 serving user identity #2. Upon receiving the eighth message from the terminal device, AMF #2 can allow user identity #1 to associate with user identity #2, thereby establishing an association between user identity #1 and user identity #2. Furthermore, the second message may also include proxy paging indication information, proxy TAU indication information, and proxy handover indication information. Based on this second message, AMF #2 can allow user identity #1 to act as a proxy for the relevant services of user identity #2. In this case, user identity #2 can be in a disabled state, thus saving power consumption and network resources for the terminal device.

[0209] After establishing an association between User Identity #1 and User Identity #2, if the terminal device determines that both User Identity #1 and User Identity #2 are functional, it can disassociate them. For example, if the terminal device determines that both User Identity #1 and User Identity #2 can receive paging messages normally, it determines to disassociate either User Identity #1 acting as a proxy for User Identity #2's paging, or User Identity #2 acting as a proxy for User Identity #1's paging; as another example, if the terminal device determines that both User Identity #1 and User Identity #2 can perform TAU normally, it determines to disassociate either User Identity #1 acting as a proxy for User Identity #2's TAU, or User Identity #2 acting as a proxy for User Identity #1's TAU; and as yet another example, if the terminal device determines that both User Identity #1 and User Identity #2 can perform handover normally, it determines to disassociate either User Identity #1 acting as a proxy for User Identity #2's handover, or User Identity #2 acting as a proxy for User Identity #1's handover.

[0210] Alternatively, if the terminal device determines that user identity #1 or user identity #2 is no longer enabled, it can sever the association between user identity #1 and user identity #2.

[0211] Alternatively, if the terminal device determines that power saving is not necessary, it can detach the association between user identity #1 and user identity #2. For example, the terminal device can determine that the association between user identity #1 and user identity #2 can be detached while charging.

[0212] Alternatively, if the terminal device determines that the signal quality of the card that is currently acting as a proxy for another card's service is poor, it can terminate the proxy relationship between the two cards. For example, if user identity #1 is acting as a proxy for user identity #2's service, the terminal device, upon determining that user identity #1 has poor signal quality, will terminate the proxy service between user identity #1 and user identity #2.

[0213] The following is combined with Figure 5 This application provides a detailed description of the method for detaching the association between user identity #1 and user identity #2, as described in the embodiments. Figure 5 As shown, the method 400 includes steps S401-S408, each of which is described in detail below.

[0214] S401, User identity #1 (an example of the first user identity) and User identity #2 (an example of the second user identity) are in an associated state.

[0215] The association between user identity #1 and user identity #2 can be understood as: user identity #1 is associated with user identity #2, user identity #1 is associated with user identity #2 and user identity #1 acts as an agent for user identity #2 in business, and user identity #1 is associated with user identity #2 and user identity #2 acts as an agent for user identity #1 in business.

[0216] S402, the terminal device has been determined to no longer be associated.

[0217] The basis for the terminal device's determination that it does not need to associate user identity #1 with user identity #2 is as described above, and will not be repeated here for the sake of brevity.

[0218] S403, the terminal device sends a sixth message to AMF#1 (an example of the first device).

[0219] In this process, the terminal device sends a sixth message to AMF#1 using user identity #1. The sixth message is used to indicate a request to terminate the association between user identity #1 and user identity #2. The sixth message is also used to indicate information about user identity #2, or the sixth message may also include information about user identity #2.

[0220] Optionally, the sixth message may also include one or more of the following: agent paging cancellation instruction, agent TAU ​​cancellation instruction, and agent switching cancellation instruction.

[0221] The content of the sixth message can be determined based on the association between user identity #1 and user identity #2. For example, if user identity #1 is associated with user identity #2 and user identity #1 acts as a paging agent for user identity #2, then the sixth message may include a cancellation paging agent instruction; if user identity #1 is associated with user identity #2 and user identity #1 acts as a TAU and handover agent for user identity #2, then the sixth message may include a cancellation TAU instruction and a cancellation handover instruction.

[0222] S404, AMF#1 sends a seventh message to AMF#2 (an example of the second device).

[0223] The seventh message is used to indicate the removal of the association between user identity #1 and user identity #2. The seventh message may also include one or more of the following: removal of agent paging instruction, removal of agent TAU ​​instruction, and removal of agent switching instruction.

[0224] As mentioned earlier, the sixth message received by AMF#1 from the terminal device includes information about user identity #2. AMF#1 can locate the AMF#2 serving user identity #2 based on this information. Further, AMF#1 sends a seventh message to AMF#2. This seventh message can be the same as the sixth message; for example, AMF#1 can forward the sixth message to AMF#2. Alternatively, the seventh message can be different from the sixth message. For example, AMF#1 decapsulates the received sixth message to obtain its content; then, AMF#1 encapsulates the obtained content according to its communication protocol with AMF#2 to generate the seventh message; and then sends the seventh message to AMF#2.

[0225] Optionally, the seventh message can be used to indicate information about user identity #1 and user identity #2.

[0226] S405, AMF#2 sends a notification to the terminal device to unassociate.

[0227] Correspondingly, the terminal device receives the deassociation notification as user identity #2. This deassociation notification is used to inform user identity #2 that the association relationship with user identity #1 is being severed.

[0228] Optionally, the notification to sever the association can be the same as the seventh message.

[0229] Optionally, the unassociation notification can be used to indicate information about user identity #1.

[0230] S406, the terminal device sends the first unassociation response message to AMF#2.

[0231] The terminal device sends the first unassociation response message to AMF#2 using user identity #2. This first unassociation response message is used to determine the unassociation relationship between user identity #1 and user identity #2.

[0232] Optionally, the first unassociation response message can be the same as the seventh message.

[0233] S407, AMF#2 sends a second unassociation response message to AMF#1.

[0234] The second unassociation response message is used to determine the unassociation relationship between user identity #1 and user identity #2.

[0235] Optionally, the second unassociation response message can be the same as the first unassociation response message.

[0236] S408, AMF#1 sends a third unassociation response message to the terminal device.

[0237] Correspondingly, the terminal device receives the third deassociation response message as user identity #1. This third deassociation response message is used to determine the deassociation relationship between user identity #1 and user identity #2.

[0238] Optionally, the third unassociation response message can be the same as the first unassociation response message.

[0239] It should be understood that method 400 may execute S405-S406 first and then S407-S408, or it may execute S407-S408 first and then S405-S406. This application embodiment does not limit this.

[0240] It should also be understood that the embodiments in this application are only illustrated by the example of a terminal device sending a sixth message as user identity #1, and this should not be construed as limiting the application. The terminal device may also send a sixth message to AMF #2 as user identity #2 to request the removal of the association between user identity #1 and user identity #2.

[0241] The above, combined with Figures 2 to 5 The method for user identity association provided in the embodiments of this application is described in detail below. The following, in conjunction with... Figures 6 to 7 The communication device provided in the embodiments of this application is described in detail.

[0242] Figure 6 This is a schematic block diagram of a communication device 500 provided in an embodiment of this application. As shown in the figure, the communication device 500 may include a transceiver unit 510 and a processing unit 520.

[0243] In one possible design, the communication device 500 may be the first device in the above method embodiment, or it may be a chip used to implement the functions of the first device in the above method embodiment.

[0244] Specifically, the communication device 500 may correspond to the first device in methods 200 to 400 according to embodiments of this application, and the communication device 500 may include tools for performing... Figure 2 Method 200 to Figure 5 The first device in method 400 is a unit that executes the method. Furthermore, each unit in the communication device 500 and the other operations and / or functions described above are respectively for implementing... Figures 2 to 3 Method 200 Figure 4 Method 300 Figure 5 The corresponding process of method 400 is described above. It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0245] In another possible design, the communication device 500 can be the second device in the above method embodiment, or it can be a chip used to implement the functions of the second device in the above method embodiment.

[0246] Specifically, the communication device 500 may correspond to the second device in methods 200 to 400 according to embodiments of this application, and the communication device 500 may include tools for performing... Figure 2 Method 200 to Figure 5 The second device in method 400 is a unit that executes the method. Furthermore, each unit in the communication device 500 and the aforementioned other operations and / or functions are respectively for implementing... Figures 2 to 3 Method 200 Figure 4 Method 300 Figure 5 The corresponding process of method 400 is described above. It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0247] In another possible design, the communication device 500 can be the terminal device in the above method embodiment, or it can be a chip used to implement the functions of the terminal device in the above method embodiment.

[0248] Specifically, the communication device 500 may correspond to the terminal device in methods 200 to 400 according to embodiments of this application, and the communication device 500 may include tools for performing... Figure 2 Method 200 to Figure 5 The terminal device in method 400 is a unit that executes the method. Furthermore, each unit in the communication device 500 and the other operations and / or functions described above are respectively for implementing... Figures 2 to 3 Method 200 Figure 4 Method 300 Figure 5 The corresponding process of method 400 is described above. It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0249] It should be understood that the transceiver unit in the communication device 500 can correspond to Figure 7 The transceiver 610 in the communication device 600 shown in the figure, and the processing unit 520 in the communication device 500 may correspond to Figure 7 The transceiver 620 in the communication device 600 shown in the figure.

[0250] Figure 7This is a schematic block diagram of a communication device 600 provided in an embodiment of this application. As shown, the communication device 600 includes a processor 610 and a transceiver 620. The processor 610 is coupled to a memory and is used to execute instructions stored in the memory to control the transceiver 620 to transmit and / or receive signals. Optionally, the communication device 600 also includes a memory 630 for storing instructions.

[0251] It should be understood that the processor 610 and memory 630 described above can be combined into a single processing device, with the processor 610 executing the program code stored in the memory 630 to achieve the aforementioned functions. In specific implementations, the memory 630 can be integrated into the processor 610 or independent of the processor 610.

[0252] It should also be understood that transceiver 620 may include a receiver (or receiver unit) and a transmitter (or transmitter unit). The transceiver may further include antennas, and the number of antennas may be one or more.

[0253] In one possible design, the communication device 600 can be the first device in the above method embodiment, or it can be a chip used to implement the functions of the first device in the above method embodiment.

[0254] Specifically, the communication device 600 may correspond to the first device in methods 200 to 400 according to embodiments of this application, and the communication device 600 may include tools for performing... Figure 2 Method 200 to Figure 5 The first device in method 400 is a unit that executes the method. Furthermore, each unit in the communication device 600 and the other operations and / or functions described above are respectively for implementing... Figures 2 to 3 Method 200 Figure 4 Method 300 Figure 5 The corresponding process of method 400 is described above. It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0255] In another possible design, the communication device 600 may be the second device in the above method embodiment, or it may be a chip used to implement the functions of the second device in the above method embodiment.

[0256] Specifically, the communication device 600 may correspond to the second device in methods 200 to 400 according to embodiments of this application, and the communication device 600 may include tools for performing... Figure 2 Method 200 to Figure 5 The second device in method 400 is a unit that executes the method. Furthermore, each unit in the communication device 600 and the other operations and / or functions described above are respectively for implementing... Figures 2 to 3 Method 200 Figure 4 Method 300 Figure 5 The corresponding process of method 400 is described above. It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0257] In another possible design, the communication device 600 can be the terminal device in the above method embodiment, or it can be a chip used to implement the functions of the terminal device in the above method embodiment.

[0258] Specifically, the communication device 600 may correspond to the terminal device in methods 200 to 400 according to embodiments of this application, and the communication device 600 may include tools for performing... Figure 2 Method 200 to Figure 5 The terminal device in method 400 is a unit that executes the method. Furthermore, each unit in the communication device 600 and the other operations and / or functions described above are respectively for implementing... Figures 2 to 3 Method 200 Figure 4 Method 300 Figure 5 The corresponding process of method 400 is described above. It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0259] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0260] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute... Figures 2 to 5 The user identity association method in any of the embodiments shown.

[0261] According to the method provided in the embodiments of this application, this application also provides a computer-readable medium storing program code, which, when run on a computer, causes the computer to perform... Figures 2 to 5 The user identity association method in any of the embodiments shown.

[0262] According to the method provided in the embodiments of this application, this application also provides a system, which includes the aforementioned first device, second A device and terminal device.

[0263] 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 the 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. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0264] Each network element in the above device embodiments can completely correspond to each network element in the method embodiments. The corresponding unit or unit executes the corresponding steps. For example, the transceiver unit (transceiver) executes the receiving or transmitting steps in the method embodiments, while other steps besides transmitting and receiving can be executed by the processing unit (processor). The specific functions of each unit can be found in the corresponding method embodiments. There can be one or more processors.

[0265] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b, and c, where a, b, or c can be single or multiple.

[0266] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence number of the above-described processes does not imply a sequential 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 the present invention.

[0267] As used in this specification, the terms "unit," "system," etc., are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. As illustrated, applications running on computing devices and computing devices can both be components. One or more components may reside in a process and / or an execution thread, and components may be located on a single computer and / or distributed among two or more computers. Furthermore, these components can be executed from various computer-readable media on which various data structures are stored. Components can communicate, for example, via local and / or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, and / or a network, such as the Internet interacting with other systems via signals).

[0268] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0269] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0270] 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.

[0271] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0272] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0273] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0274] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for user identity association, characterized in that, The method is used in a network communication system, which is a fifth-generation communication system or its future evolution communication system. The network communication system includes a terminal device, a first device, and a second device. The terminal device includes a first user identity and a second user identity. The first device serves the first user identity, and the second device serves the second user identity. The method includes: The first device receives a first message from the terminal device. The first message is sent by the terminal device in the identity of the first user. The first message is used to indicate a request for the first user identity to be associated with the second user identity. The first message is also used to indicate information about the second user identity. The first message includes third indication information or fourth indication information. The third indication information is used to indicate a request for the first user identity to act as an agent for the services of the second user identity. The fourth indication information is used to indicate a request for the second user identity to act as an agent for the services of the first user identity. The first device sends a second message to the second device based on the information of the second user identity. The second message is used to indicate a request to associate the first user identity with the second user identity. Before the first device receives the first message from the terminal device, the method further includes: The first device sends a first indication message to the terminal device, the first indication message being used to indicate that the first device supports user identity association; After receiving the first message, the first device determines whether to allow the association of the first user identity with the second user identity based on at least one of the following pieces of information: The capability information of the first device, the contract information of the first user, and the location information of the terminal device; The first device sends a fifth message to the terminal device based on the information of the first user identity. The fifth message is used to indicate that the first user identity is allowed to be associated with the second user identity.

2. The method according to claim 1, characterized in that, The first message also includes one or more of the following: agent paging indication information, agent tracking area update (TAU) indication information, and agent switching indication information.

3. The method according to claim 1 or 2, characterized in that, The second message also includes one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

4. The method according to claim 1 or 2, characterized in that, The method further includes: The first device receives a third message from the second device. The third message is used by the first device to determine that the first user identity is associated with the second user identity. The third message is also used to indicate information about the first user identity.

5. The method according to claim 4, characterized in that, The method further includes: The first device sends a fourth message to the terminal device based on the third message, the fourth message being used by the terminal device to determine that the first user identity is associated with the second user identity.

6. The method according to claim 1 or 2, characterized in that, After associating the first user identity and the second user identity, the method further includes: The first device receives a sixth message from the terminal device. The sixth message is sent by the terminal device in the identity of the first user. The sixth message is used to indicate a request to sever the association between the first user identity and the second user identity. The sixth message is also used to indicate information about the second user identity.

7. The method according to claim 6, characterized in that, The method further includes: The first device sends a seventh message to the second device based on the information of the second user identity. The seventh message is used to indicate the removal of the association between the first user identity and the second user identity.

8. The method according to claim 7, characterized in that, The sixth message also includes one or more of the following: agent paging cancellation instruction, agent TAU ​​cancellation instruction, and agent switching cancellation instruction.

9. The method according to claim 7, characterized in that, The seventh message also includes one or more of the following: agent paging cancellation instruction, agent TAU ​​cancellation instruction, and agent switching cancellation instruction.

10. A method for user identity association, characterized in that, The method is used in a network communication system, which is a fifth-generation communication system or its future evolution communication system. The network communication system includes a terminal device, a first device, and a second device. The terminal device includes a first user identity and a second user identity. The first device serves the first user identity, and the second device serves the second user identity. The method includes: The second device receives a second message from the first device. The second message is sent by the first device based on a first message from the terminal device. The first message is sent by the terminal device in the identity of the first user. The first message is used to indicate a request to associate the first user identity with the second user identity. The first message is also used to indicate information about the second user identity. The second message is used to indicate a request to associate the first user identity with the second user identity. The first message includes third indication information or fourth indication information. The third indication information is used to indicate a request for the first user identity to act as an agent for the services of the second user identity. The fourth indication information is used to indicate a request for the second user identity to act as an agent for the services of the first user identity. The second device sends a third message to the first device. The third message is used by the first device to determine that the first user identity is associated with the second user identity. The third message is also used to indicate information about the first user identity. Before the second device sends a third message to the first device, the method further includes: The second device sends a tenth message to the terminal device. The tenth message is used to indicate whether the first user identity is allowed to be associated with the second user identity. The tenth message is also used to indicate information about the first user identity. The second device receives an eleventh message from the terminal device, the eleventh message being sent by the terminal device using the second user identity, the eleventh message indicating permission to associate the first user identity with the second user identity; or Before the second device sends a third message to the first device, the method further includes: The second device receives an eighth message from the terminal device. The eighth message is sent by the terminal device in the identity of the second user. The eighth message is used to indicate a request to associate the first user identity with the second user identity. The eighth message is also used to indicate information about the first user identity. After receiving the eighth message, the second device determines whether to allow the association between the first user identity and the second user identity based on at least one of the following information: The capability information of the second device, the subscription information of the second user, and the location information of the terminal device; The second device sends a ninth message to the terminal device, the ninth message indicating that the first user identity can be associated with the second user identity.

11. The method according to claim 10, characterized in that, The first message also includes one or more of the following: agent paging indication information, agent tracking area update (TAU) indication information, and agent switching indication information.

12. The method according to claim 10 or 11, characterized in that, The second message also includes one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

13. The method according to claim 10 or 11, characterized in that, The eighth message also includes one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

14. The method according to claim 10 or 11, characterized in that, The tenth message also includes one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

15. The method according to claim 10 or 11, characterized in that, After associating the first user identity and the second user identity, the method further includes: The second device receives a seventh message from the first device, which is sent by the first device based on a sixth message from the terminal device. The sixth message is sent by the terminal device in the identity of the first user. The sixth message is used to indicate a request to sever the association between the first user identity and the second user identity. The sixth message is also used to indicate information about the second user identity. The seventh message is used to indicate the severance of the association between the first user identity and the second user identity.

16. The method according to claim 15, characterized in that, The sixth message also includes one or more of the following: agent paging cancellation instruction, agent TAU ​​cancellation instruction, and agent switching cancellation instruction.

17. The method according to claim 16, characterized in that, The seventh message also includes one or more of the following: agent paging cancellation instruction, agent TAU ​​cancellation instruction, and agent switching cancellation instruction.

18. A method for user identity association, characterized in that, The method is used in a network communication system, which is a fifth-generation communication system or its future evolution communication system. The network communication system includes a terminal device, a first device, and a second device. The terminal device includes a first user identity and a second user identity. The first device serves the first user identity, and the second device serves the second user identity. The method includes: The terminal device sends a first message to the first device in the identity of the first user. The first message is used to indicate a request to associate the first user identity with the second user identity. The first message is also used to indicate information of the second user identity. The first message includes third indication information or fourth indication information. The third indication information is used to indicate a request for the first user identity to act as an agent for the services of the second user identity. The fourth indication information is used to indicate a request for the second user identity to act as an agent for the services of the first user identity. The terminal device receives a fourth message from the first device in the identity of the first user. The fourth message is sent by the first device based on the third message. The third message is used by the first device to determine that the first user identity is associated with the second user identity. The third message is also used to indicate information about the first user identity. The fourth message is used by the terminal device to determine that the first user identity is associated with the second user identity. The terminal device receives a fifth message from the first device using the first user identity, the fifth message being used to indicate that the first user identity is allowed to be associated with the second user identity; The terminal device receives a tenth message from the second device using the second user identity. The tenth message is used to indicate whether the first user identity is allowed to be associated with the second user identity. The tenth message is also used to indicate information about the first user identity. The terminal device determines that the first user identity can be associated with the second user identity; The terminal device sends an eleventh message to the second device in the identity of the second user, the eleventh message being used to indicate that the first user identity is allowed to be associated with the second user identity; The terminal device sends an eighth message to the second device using the second user identity. The eighth message is used to indicate a request to associate the first user identity with the second user identity. The eighth message contains or indicates information about the first user identity. The terminal device receives a ninth message from the second device in the identity of the second user, the ninth message being used to indicate that the first user identity is allowed to be associated with the second user identity.

19. The method according to claim 18, characterized in that, The first message also includes one or more of the following: agent paging indication information, agent tracking area update (TAU) indication information, and agent switching indication information.

20. The method according to claim 18 or 19, characterized in that, The eighth message also includes one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

21. The method according to claim 18 or 19, characterized in that, The tenth message includes one or more of the following: agent paging indication information, agent TAU ​​indication information, agent switching indication information.

22. The method according to claim 18 or 19, characterized in that, After associating the first user identity and the second user identity, the method further includes: The terminal device sends a sixth message to the first device using the first user identity. The sixth message is used to request an indication to sever the association between the first user identity and the second user identity. The sixth message is also used to indicate information about the second user identity.

23. The method according to claim 22, characterized in that, The sixth message also includes one or more of the following: agent paging cancellation instruction, agent TAU ​​cancellation instruction, and agent switching cancellation instruction.

24. A communication device, characterized in that, Includes units for implementing the method as described in any one of claims 1 to 9.

25. A communication device, characterized in that, Includes units for implementing the method as described in any one of claims 10 to 17.

26. A communication device, characterized in that, Includes units for implementing the method as described in any one of claims 18 to 23.

27. A communication device, characterized in that, include: A processor for executing computer instructions stored in memory to cause the communication device to perform the method as described in any one of claims 1 to 9.

28. A communication device, characterized in that, include: A processor for executing computer instructions stored in memory to cause the communication device to perform the method as described in any one of claims 10 to 17.

29. A communication device, characterized in that, include: A processor for executing computer instructions stored in memory to cause the communication device to perform the method as described in any one of claims 18 to 23.

30. A computer-readable storage medium, characterized in that, It stores a computer program thereon, which, when executed by a processor, causes the method as described in any one of claims 1 to 23 to be performed.

Images