Information processing methods, communication equipment, communication systems and storage media
By sending protected service network information between the terminal and the home network's network functions, the problem of service interruption and signaling inefficiency caused by network operators abusing trust relationships is solved. This achieves verifiability and billing compliance of visited networks and reduces the risk of fraud when accessing cross networks.
Patent Information
- Application Number
- CN202680002227.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-06-29
- Publication Date
- 2026-11-17
AI Technical Summary
In roaming scenarios between different network operators, the abuse of trust relationships by network operators can lead to service interruptions and signaling inefficiencies.
The terminal sends protected first service network information to the first network function, and the first network function and the network function of the home network are matched and verified to reduce the risk of spoofing access by impersonating the visited network and ensure the verifiability and billing compliance of the visited network in roaming scenarios.
It reduces fraud attacks in cross-network access scenarios, reduces service interruptions, and improves signaling efficiency.
Smart Images

Figure CN123125918A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of communication technology, and in particular to an information processing method, communication device, communication system and storage medium. Background Technology
[0002] Trust relationships between different network operators are fundamental to roaming. However, if a network operator abuses these trust relationships, trust checks on peer operators are necessary. Summary of the Invention
[0003] The embodiments disclosed herein aim to address the technical problem that the operation of master authentication for each service network function in the visited network leads to service interruption and / or low signaling efficiency.
[0004] According to a first aspect of the present disclosure, an information processing method is proposed, executed by a terminal, the method comprising: sending first information to a first network function, wherein the first information includes protected first service network information; wherein the first service network information is used by a second network function to determine whether the first service network information matches second service network information of the network in which the first network function is located; wherein the first network function is a mobility management function of a non-home network, and the second network function is a network function of a home network.
[0005] According to a second aspect of the present disclosure, an information processing method is proposed, executed by a first network function. The method includes: receiving first information sent by a terminal, wherein the first information includes protected first service network information; sending third information to a second network function, wherein the third information includes the protected first service network information; wherein the first service network information is used by the second network function to determine whether the first service network information matches second service network information of the network where the first network function is located; wherein the first network function is a mobility management function of a non-home network, and the second network function is a network function of a home network.
[0006] According to a third aspect of the present disclosure, an information processing method is proposed, executed by a second network function, the method comprising: receiving third information sent by a first network function, wherein the third information includes protected first service network information; wherein the first service network information is used by the second network function to determine whether the first service network information matches second service network information of the network in which the first network function is located; wherein the first network function is a mobility management function of a non-home network, and the second network function is a network function of a home network.
[0007] According to a fourth aspect of the present disclosure, an information processing method is proposed, executed by a communication system, the communication system including: a terminal, a first network function, and a second network function; the method includes: the terminal sending first information to the first network function, wherein the first information includes protected first service network information; the first network function sending third information to the second network function, wherein the third information includes the protected first service network information; wherein the first service network information is used by the second network function to determine whether the first service network information matches the second service network information of the network where the first network function is located; wherein the first network function is a mobility management function of a non-home network, and the second network function is a network function of a home network.
[0008] According to a fifth aspect of the present disclosure, a terminal is provided, comprising: a first transceiver module configured to send first information to a first network function, wherein the first information includes protected first service network information; wherein the first service network information is used by a second network function to determine whether the first service network information matches second service network information of the network in which the first network function is located; wherein the first network function is a mobility management function of a non-home network, and the second network function is a network function of a home network.
[0009] According to a sixth aspect of the present disclosure, a first network function is provided, comprising: a second transceiver module configured to receive first information sent by a terminal, wherein the first information includes protected first service network information; and to send third information to a second network function, wherein the third information includes the protected first service network information; wherein the first service network information is used by the second network function to determine whether the first service network information matches second service network information of the network in which the first network function is located; wherein the first network function is a mobility management function of a non-home network, and the second network function is a network function of a home network.
[0010] According to a seventh aspect of the present disclosure, a second network function is provided, comprising: a third transceiver module configured to receive third information sent by a first network function, wherein the third information includes protected first service network information; wherein the first service network information is used by the second network function to determine whether the first service network information matches second service network information of the network in which the first network function is located; wherein the first network function is a mobility management function of a non-home network, and the second network function is a network function of a home network.
[0011] According to an eighth aspect of the embodiments of this disclosure, a communication device is provided, which is used to perform an optional implementation of the first aspect, the second aspect, the third aspect, or the first aspect, the second aspect, and the third aspect.
[0012] According to a ninth aspect of the present disclosure, a communication system is provided, comprising: a terminal, a first network function, and a second network function; wherein the terminal is configured to perform a method as described in an optional implementation of the first aspect, the first network function is configured to perform a method as described in an optional implementation of the second aspect, and the second network function is configured to perform a method as described in an optional implementation of the third aspect.
[0013] According to a tenth aspect of the present disclosure, a storage medium is provided that stores instructions which, when executed on a communication device, cause the communication device to perform the method described in the first aspect, the second aspect, the third aspect, or an optional implementation of the first aspect, the second aspect, and the third aspect.
[0014] According to an eleventh aspect of the present disclosure, a program product is provided, including at least one of a program and instructions, wherein when the program and instructions are executed by a communication device, the method described as in the first aspect, the second aspect, the third aspect, or an optional implementation of the first aspect, the second aspect, and the third aspect is implemented.
[0015] The embodiments disclosed herein can increase home network control to reduce cross-network fraud attacks, and simultaneously eliminate the need for each service network function in the visited (or visited) network to perform master authentication, thereby reducing service interruptions and / or improving signaling efficiency. Attached Figure Description
[0016] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.
[0017] Figure 1 This is a schematic diagram of the structure of a communication system according to an embodiment of the present disclosure.
[0018] Figure 2 This is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure.
[0019] Figure 3 This is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure.
[0020] Figure 4A This is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure.
[0021] Figure 4B This is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure.
[0022] Figure 4CThis is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure.
[0023] Figure 5A This is a schematic diagram of the structure of a terminal according to an embodiment of the present disclosure.
[0024] Figure 5B This is a schematic diagram illustrating the structure of a first network function according to an embodiment of the present disclosure.
[0025] Figure 5C This is a schematic diagram illustrating the structure of a second network function according to an embodiment of the present disclosure.
[0026] Figure 6A This is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure.
[0027] Figure 6B This is a schematic diagram of the chip structure provided according to an embodiment of the present disclosure. Detailed Implementation
[0028] This disclosure provides an information processing method, a communication device, a communication system, and a storage medium.
[0029] In a first aspect, embodiments of this disclosure propose an information processing method executed by a terminal. The method includes: sending first information to a first network function, wherein the first information includes protected first service network information; wherein the first service network information is used by a second network function to determine whether the first service network information matches second service network information of the network in which the first network function is located; wherein the first network function is a mobility management function of a non-home network, and the second network function is a network function of a home network.
[0030] In the above embodiments, the terminal can provide the first service network information of the service network where the terminal is located to the first network function, thereby enabling the second network function of the home network to determine whether the service network where the terminal is located is the network where the first network function that requested registration is located. This reduces the risk of spoofing access by fake network functions (or untrusted network functions) in cross-network access scenarios, ensures the verifiability of visited networks in roaming scenarios, and ensures the billing compliance of visited networks.
[0031] In conjunction with some embodiments of the first aspect, in some embodiments, sending first information to a first network function includes: sending first information to a first network function when it is detected that the serving network where the terminal is located has changed and is no longer the home network.
[0032] In the above embodiments, reporting is triggered only when the terminal detects a change in the serving network and that it is not the home network. This clarifies the execution timing in roaming scenarios. Reporting is only triggered in untrusted scenarios between two different networks, eliminating the need to trigger reporting every time the terminal registers, thus reducing signaling overhead.
[0033] In conjunction with some embodiments of the first aspect, in some embodiments, the protected first service network information is protected by a secure association between the terminal and the second network function.
[0034] In the above embodiments, the protection of the first service network information is achieved by utilizing the security association established between the terminal and the home network, which prevents the visited network from tampering with the protected first service network information; thus, the reliability of the second network function check in the home network can be improved.
[0035] In conjunction with some embodiments of the first aspect, in some embodiments, the first information further includes at least one of the following: a random number; a first identifier, wherein the first identifier is used to indicate one of the following: a terminal, the terminal, and the service network in which the terminal is located.
[0036] In the above embodiments, the addition of a random number can effectively resist replay attacks on the visited network; the addition of a first identifier can indicate the unique identity of the terminal or the unique identity of the terminal plus the current serving network; thus, more accurate verification can be achieved.
[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is sent via one of the following: a registration request message; a registration completion message.
[0038] In the above embodiments, the first information can be sent through a registration request message or a registration completion message, that is, the first information can be sent through the registration request process, reusing the existing protocol process, which is compatible with the existing protocol process and requires only minor modifications to the existing protocol process; and sending the first information through a registration request message or a registration completion message does not require the addition of new dedicated signaling to send the first information, thereby improving the utilization rate of the registration request message or registration completion message and reducing the signaling overhead.
[0039] In conjunction with some embodiments of the first aspect, in some embodiments, when the first information is sent via a registration completion message, the method further includes: receiving second information sent by a first network function, wherein the second information includes indication information; wherein the indication information is used to indicate at least one of the following: the terminal's registration is temporary, the home network needs to manage the service network where the terminal is located, and the terminal reports information about the service network where the terminal is located.
[0040] In the above embodiments, after the first network function registers the terminal, if the second network function does not trust the network registered by the terminal, it can send second information including indication information to the first network function, indicating that the terminal's registration is temporary. Before confirming the registration, the service network where the terminal is located needs to be verified. The verification method is to have the terminal report the information of the service network where it is located (i.e., the first service network information). This can realize the control of the service network where the terminal is located and reduce the occurrence of fraudulent activities such as fake service networks forging terminal registration.
[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the second information is received via a registration acceptance message.
[0042] In the above embodiments, the second information sent by the registration receiving message in the registration process can be reused without the need for additional signaling interaction, thereby improving the utilization rate of the registration receiving message and reducing the signaling overhead.
[0043] In conjunction with some embodiments of the first aspect, in some embodiments, the first network function is a mobility management function; and / or, the second network function is one of the following: unified data management, unified data storage, identity authentication storage and processing functions.
[0044] In the above embodiments, the types of network functions of the first network function and / or the second network function are clearly defined, and a communication architecture for implementing the reporting of information of the service network where the terminal is located (i.e., the first service network information) is proposed.
[0045] Secondly, embodiments of this disclosure propose an information processing method executed by a first network function. The method includes: receiving first information sent by a terminal, wherein the first information includes protected first service network information; sending third information to a second network function, wherein the third information includes the protected first service network information; wherein the first service network information is used by the second network function to determine whether the first service network information matches second service network information of the network where the first network function is located; wherein the first network function is a mobility management function of a non-home network, and the second network function is a network function of a home network.
[0046] In the above embodiments, the first network function can forward the first service network information of the service network where the terminal is located to the second network function in the home network. This allows the second network function to determine whether the service network where the terminal is located is the network where the first network function that requested registration is located. This reduces the risk of spoofing access by fake network functions (or untrusted network functions) in cross-network access scenarios, ensures the verifiability of service networks in roaming scenarios, and ensures the billing compliance of visited networks.
[0047] In conjunction with some embodiments of the second aspect, in some embodiments, the protected first service network information is protected by a secure association between the terminal and the second network function.
[0048] In conjunction with some embodiments of the second aspect, in some embodiments the first information further includes at least one of the following: a random number, a first identifier; and / or, the third information further includes at least one of the following: a random number, a first identifier, second service network information; wherein the first identifier is used to indicate one of the following: a terminal, the terminal, and the service network in which the terminal is located.
[0049] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is received via one of the following: a registration request message, a registration completion message; and / or, the third information is sent via one of the following: a terminal context management registration request message, a terminal context management registration update request message.
[0050] In conjunction with some embodiments of the second aspect, in some embodiments, when the first information is received through registration completion message reception, the method further includes: receiving fourth information sent by the second network function, wherein the fourth information includes indication information; sending second information to the terminal, wherein the second information includes indication information; wherein the indication information is used to indicate at least one of the following: the terminal's registration is temporary registration, the home network needs to manage the service network where the terminal is located, and the terminal reports information about the service network where the terminal is located.
[0051] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: receiving fifth information sent by the second network function, wherein the fifth information is used to confirm successful registration.
[0052] In the above embodiments, the first network function receives a registration success confirmation message from the second network function of the home network to synchronously update the local terminal access status (e.g., the network accessed).
[0053] In conjunction with some embodiments of the second aspect, in some embodiments, the fourth information is received via a terminal context management registration response message; and / or, the second information is sent via a registration acceptance message; and / or, the fifth information is received via one of the following: a terminal context management registration response message, or a terminal context management registration update response message.
[0054] In conjunction with some embodiments of the second aspect, in some embodiments, before sending the third information to the second network function, one of the following is further included: determining to skip the main authentication process based on the fact that the first information includes protected first service network information; or determining to trigger the main authentication process based on the fact that the first information does not include first service network information.
[0055] In the above embodiments, the first network function can dynamically select to skip primary authentication or trigger primary authentication based on whether the first information carries protected first service network information; if it carries protected first service network information, it can skip primary authentication, thereby improving access efficiency, etc.
[0056] In conjunction with some embodiments of the second aspect, in some embodiments, the first network function is a mobility management function; and / or, the second network function is one of the following: unified data management, unified data storage, identity authentication storage and processing functions.
[0057] Thirdly, this disclosure provides an information processing method executed by a second network function. The method includes: receiving third information sent by a first network function, wherein the third information includes protected first service network information; wherein the first service network information is used by the second network function to determine whether the first service network information matches second service network information of the network where the first network function is located; wherein the first network function is a mobility management function of a non-home network, and the second network function is a network function of a home network.
[0058] In the above embodiments, the first service network information reported by the terminal can be checked with the second service network information of the network where the first network function is located to achieve trusted verification of roaming access. This reduces the risk of fake access by fake network functions (or untrusted network functions) masquerading as visiting the network in cross-network access scenarios, and reduces fraudulent behavior of untrusted service networks forging terminal registration.
[0059] In conjunction with some embodiments of the third aspect, in some embodiments, the protected first service network information is protected by a secure association between the terminal and the second network function.
[0060] In some embodiments, in conjunction with the third aspect, the method further includes: decoding and verifying the third information to determine the first service network information; and determining whether the first service network information matches the second service network information.
[0061] In the above embodiment, before the second network function performs the check on whether the first service network information matches the second service network, it is also necessary to obtain the first service network information from the third information, so as to obtain the service network information where the terminal that has not been tampered with is located.
[0062] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes: if the first service network information matches the second service network information, performing at least one of the following: accepting the registration requested in the third information; storing the first service network information or replacing the locally stored third service network information with the first service network information.
[0063] In the above embodiments, after the verification is passed, the registration request can be accepted directly, and the real service network information currently accessed by the terminal (i.e., the first service network information) is stored to provide a basis for subsequent mobility updates, etc.
[0064] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes: upon receiving sixth information sent by a third network function, determining whether the fourth service network information included in the sixth information matches the first network service information; the third network function is not a network function of its own network; if the fourth service network information matches the first service network information, accepting the request in the sixth information; or, if the fourth service network information does not match the first service network information, rejecting the request in the sixth information.
[0065] In the above embodiments, after the terminal successfully registers, the second network function can match the service network information (i.e., the fourth service network information) of the network where the service network function that subsequently initiates the request is located with the previously stored legitimate historical service network information (i.e., the first service network information). If the match is successful, the request is accepted; otherwise, it is rejected directly, thereby reducing fraudulent behavior such as untrusted service networks forging terminal registration.
[0066] In conjunction with some embodiments of the third aspect, in some embodiments, the sixth information is sent during the terminal's registration process, or the sixth information is sent after the terminal's registration process is completed.
[0067] In the above embodiments, the verification of the request for the third network function can be achieved during the registration request process (i.e., the registration request process after the verification of the first service network information is completed) and after the registration completion process.
[0068] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes: rejecting the registration request in the third information based on at least one of the following: verification of the first service network information in the third information fails; the first service network information does not match the second service network information; or, initiating a registration / deregistration process to the first network function based on at least one of the following: the third information is not received before the timer expires, wherein the start time of the timer is the time when the fourth information is sent; verification of the first service network information in the third information fails; the first service network information does not match the second service network information.
[0069] In the above embodiments, if the verification fails, the registration request is directly rejected. If the first service network information reported by the terminal is not received within the time limit, the registration and deregistration process is directly triggered, thereby timely intercepting terminal access requests from untrusted service networks.
[0070] In conjunction with some embodiments of the third aspect, in some embodiments, the third information further includes at least one of the following: a random number, a first identifier, and second service network information; wherein the first identifier is used to indicate one of the following: a terminal, the terminal, and the service network in which the terminal is located.
[0071] In conjunction with some embodiments of the third aspect, in some embodiments, before receiving the third information sent by the first network function, the method further includes: sending fourth information to the first network function, wherein the fourth information includes indication information; wherein the indication information is used to indicate at least one of the following: the terminal's registration is temporary registration, the home network needs to manage the service network where the terminal is located, and the terminal reports information about the service network where the terminal is located.
[0072] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes: sending fifth information to the first network function, wherein the fifth information is used to confirm successful registration.
[0073] In conjunction with some embodiments of the third aspect, in some embodiments, the third information is sent via one of the following: a terminal context management registration request message, a terminal context management registration update request message; and / or, the fourth information is sent via a terminal context management registration response message; and / or, the fifth information is sent via one of the following: a terminal context management registration response message, a terminal context management registration update response message.
[0074] In conjunction with some embodiments of the third aspect, in some embodiments, the first network function is a mobility management function; and / or, the second network function is one of the following: unified data management, unified data storage, identity authentication storage and processing functions.
[0075] Fourthly, this disclosure provides an information processing method executed by a communication system, the communication system including: a terminal, a first network function, and a second network function; the method includes: the terminal sending first information to the first network function, wherein the first information includes protected first service network information; the first network function sending third information to the second network function, wherein the third information includes the protected first service network information; wherein the first service network information is used by the second network function to determine whether the first service network information matches the second service network information from the first network function; wherein the first network function is a mobility management function of a non-home network, and the second network function is a network function of a home network.
[0076] Fifthly, embodiments of this disclosure provide a terminal, including: a first transceiver module configured to send first information to a first network function, wherein the first information includes protected first service network information; wherein the first service network information is used by a second network function to determine whether the first service network information matches second service network information from the first network function; wherein the first network function is a mobility management function of a non-home network, and the second network function is a network function of a home network.
[0077] In a sixth aspect, embodiments of this disclosure propose a first network function, comprising: a second transceiver module configured to receive first information sent by a terminal, wherein the first information includes protected first service network information; and to send third information to a second network function, wherein the third information includes the protected first service network information; wherein the first service network information is used by the second network function to determine whether the first service network information matches second service network information from the first network function; wherein the first network function is a mobility management function of a non-home network, and the second network function is a network function of a home network.
[0078] In a seventh aspect, embodiments of this disclosure propose a second network function, including: a third transceiver module configured to receive third information sent by a first network function, wherein the third information includes protected first service network information; wherein the first service network information is used by the second network function to determine whether the first service network information matches the second service network information from the first network function; wherein the first network function is a mobility management function of a non-home network, and the second network function is a network function of a home network.
[0079] Eighthly, embodiments of this disclosure provide a communication device for performing an alternative implementation of the first aspect, the second aspect, the third aspect, or the first aspect, the second aspect, and the third aspect.
[0080] In a ninth aspect, embodiments of this disclosure provide a communication system, including: a terminal, a first network function, and a second network function; wherein the terminal is configured to perform the method described in the optional implementation of the first aspect, the first network function is configured to perform the method described in the optional implementation of the second aspect, and the second network function is configured to perform the method described in the optional implementation of the third aspect.
[0081] In a tenth aspect, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in the first aspect, the second aspect, the third aspect, or an optional implementation of the first aspect, the second aspect, and the third aspect.
[0082] In one aspect, embodiments of this disclosure provide a program product including at least one of a program and instructions, wherein the program and instructions, when executed by a communication device, implement the method described in the first aspect, the second aspect, the third aspect, or an optional implementation of the first aspect, the second aspect, and the third aspect.
[0083] In a twelfth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the information processing method as described in the first aspect, the second aspect, the third aspect, or an optional implementation of the first aspect, the second aspect, and the third aspect.
[0084] In a thirteenth aspect, embodiments of this disclosure provide a chip or chip system including processing circuitry configured to perform the methods described above as in the first, second, third, or alternative implementations of the first, second, and third aspects.
[0085] It is understood that the aforementioned devices (e.g., first network function, second network function, third network function, terminal, etc.), communication systems, storage media, program products, computer programs, chips, or chip systems are all used to execute the methods provided in the embodiments of this disclosure. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.
[0086] This disclosure provides an information processing method, a communication device, a communication system, and a storage medium. In some embodiments, the terms "information processing method" and "information processing apparatus" are interchangeable, as are "information processing system" and "communication system".
[0087] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually utilized. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.
[0088] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.
[0089] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.
[0090] In the embodiments disclosed herein, "multiple" refers to two or more.
[0091] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.
[0092] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.
[0093] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.
[0094] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.
[0095] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
[0096] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.
[0097] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.
[0098] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.
[0099] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.
[0100] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).
[0101] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.
[0102] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriberstation, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, and client can be used interchangeably.
[0103] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.
[0104] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.
[0105] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.
[0106] In some embodiments, data, information, etc., may be obtained with the user's consent.
[0107] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.
[0108] Figure 1 This is a schematic diagram illustrating the structure of a communication system 100 according to an embodiment of this disclosure. For example... Figure 1 As shown, the communication system 100 may include: terminal 101, access network device 102, and core network device 103.
[0109] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home, but is not limited thereto.
[0110] In some embodiments, the access network device 102 may be a node or device that connects a terminal to a wireless network. The access network device may include at least one of the following in a 5G communication system: an evolved Node B (eNB), a next-generation eNB (ng-eNB), a next-generation Node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open RAN, a cloud RAN, a base station in other communication systems, and an access node in a Wi-Fi system, but is not limited thereto.
[0111] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.
[0112] In some embodiments, the technical solutions of this disclosure can be applied to a service-based RAN architecture. In this case, the interfaces between access network devices or between access network devices and core network devices involved in the embodiments of this disclosure can be service-based interfaces. The processes and information interactions between these interfaces can be implemented by software or programs that call one or more corresponding services.
[0113] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.
[0114] In some embodiments, the core network device 103 may be a single device including a first network function 1031, a second network function 1032, a third network function 1033, etc., or it may be multiple devices or a group of devices, each including all or part of the aforementioned first network function 1031, second network function 1032, third network function 1033, etc. Network functions may be virtual or physical. The core network may include, for example, at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), and 6G Core Network (6GCN).
[0115] In some embodiments, the first network function 1031 can be used for terminal mobility management, etc.
[0116] In some embodiments, the first network function 1031 may be a Mobility Management Function (MMF), etc. The name of the first network function 1031 is not limited.
[0117] In some embodiments, the second network function 1032 can be used to manage user data and / or provide services such as user data query and subscription updates.
[0118] In some embodiments, the second network function 1032 can be used to securely store user authentication credential information, etc.
[0119] In some embodiments, the second network function 1032 may include one of the following: Unified Data Management (UDM), Unified Data Repository (UDR), Authentication Credential Repository and Processing Function (ARPF), etc. The name of the second network function 1032 is not limited.
[0120] In some embodiments, the third network function 1033 can be any network function in the core network.
[0121] In some embodiments, the third network function 1033 may include at least one of the following: Mobility Management Function (MMF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF), and User Plane Function (UPF).
[0122] In some embodiments, the third network function 1033 may include the first network function 1031.
[0123] In some embodiments, the first network function 1031 is a network function of a non-home network; the second network function 1032 is a network function of a home network; and the third network function 1033 is a network function of a non-home network. Here, a network function of a non-home network refers to a network function that is not part of the home network.
[0124] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions provided in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in this disclosure are also applicable to similar technical problems.
[0125] The following embodiments of this disclosure can be applied to Figure 1 The communication system 100 shown, or a part thereof, but not limited to it. Figure 1 The entities shown are illustrative; a communication system may include... Figure 1 All or part of the main body, or may include Figure 1 Other entities besides the main body, the number and form of each entity are arbitrary, each entity can be physical or virtual, the connection relationship between the entities is illustrative, the entities can be unconnected or connected, and the connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.
[0126] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), 6th generation mobile communication system (6G), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).
[0127] Trust relationships between different operators are fundamental to roaming. However, if network operators abuse these trust relationships, peer operators need to conduct checks. Otherwise, untrusted networks with valid roaming agreements could harm the roaming ecosystem through malicious fraud, such as charging false service fees when no service is provided, or violating user privacy by unauthorized access to UE subscription data.
[0128] One development in 5G security is the addition of attribution control, which can prevent certain types of fraud from accessing the network. By binding authentication results to subsequent processes, the UDM can decide, based on policies and the user's stored authentication status, to accept or reject the registration of an AMF in a visited VPLMN.
[0129] In 5G, the Home Network Control mechanism is limited to AMF registration. If the AMF in the VPLMN sends a registration request to the UDM in the Home PLMN or Home PLMN (HPLMN) without performing primary authentication, the UDM must either trust the AMF and accept the registration request, or initiate primary authentication to ensure that the UE is indeed registering through the AMF.
[0130] When an endpoint switches its AMF between two VPLMNs, the target VPLMN may not be interested in performing a full master authentication for efficiency reasons. In this case, the HPLMN can trigger the VPLMN to perform master authentication, but the VPLMN may or may not execute the master authentication process triggered by the HPLMN.
[0131] If the VPLMN does not run primary authentication, although the HPLMN can refuse the registration request, this would create complex logic for the HPLMN to make judgments through multiple "if" and "else" conditions, putting the HPLMN in a difficult position: if the VPLMN is not acting maliciously (i.e., avoiding primary authentication for efficiency reasons), the HPLMN's refusal of the registration request would deprive the UE of its services; but accepting the registration request might cause the HPLMN to misjudge the UE's location.
[0132] Providing the UE's incorrect location information to the HPLMN can be used for various attacks, such as billing fraud and redirecting incoming traffic to the wrong VPLMN.
[0133] Furthermore, in some embodiments, the authentication result is associated only with the AMF registration and not with other NFs (such as SMFs). A visited network NF with a valid roaming protocol might impersonate a UE's serving NF (e.g., SMF registration) even when no UE is present, leading to fraudulent charges, privacy violations, or service abuse. For example, a fraudulent SMF in the visited network might invoke service operations (e.g., Nudm_SDM_Get, Nudm_UECM_Registration) to allow access to or modification of subscription data in the UDM.
[0134] Furthermore, in the event of local traffic redirection, the visited network may overcharge for data usage. In the case of local traffic redirection sessions, the home network control mechanism cannot verify the actual data usage and billing information. Instead, it relies on information reports provided by the visited network. How to verify the billing information reported by the visited network in communication systems (e.g., 6G) requires further research and improvement.
[0135] In existing communication systems (such as 5G systems), by binding authentication results to subsequent processes, the UDM can decide whether to accept or reject the registration of an AMF in a VPLMN based on a policy and the stored user authentication status. However, performing master authentication for the registration of each service NF in the visited network would lead to service interruptions and signaling inefficiencies.
[0136] In some embodiments, the UE can be a terminal, or the terminal can be a UE.
[0137] In some embodiments, the first network function is a network function of a non-home network; the second network function is a network function of a home network; and the third network function is a network function of a non-home network. Here, a network function of a non-home network refers to a network function that is not part of the home network.
[0138] In some embodiments, the first network function is a mobility management function; and / or, the second network function is one of the following: unified data management, unified data storage, identity authentication storage and processing functions; and / or, the third network function is one of the following: mobility management function, access and mobility management function, session management function, policy control function, user plane function. Optionally, the third network function is any network function of a non-home network. Optionally, the third network function includes the first network function.
[0139] like Figure 2 This is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure. For example... Figure 2 As shown, this disclosure relates to an information processing method for a communication system 100, the method comprising:
[0140] Step S2101: The second network function sends the fourth information to the first network function.
[0141] In some embodiments, the first network function receives fourth information sent by the second network function.
[0142] In some embodiments, the first network function is a mobility management function of a non-home network, and the second network function is a network function of the home network.
[0143] In some embodiments, the fourth information includes indication information. Optionally, the fourth information may include: indication information and a second identifier, the second identifier being used to indicate the terminal. Optionally, the second identifier may be used to uniquely identify the terminal.
[0144] In some embodiments, the name of the fourth message is not limited, and it may be, for example, a registration completion response message.
[0145] Optionally, the indication information is used to indicate at least one of the following: the terminal's registration is temporary, the home network needs to manage the service network where the terminal is located, and the terminal reports information about the service network where the terminal is located.
[0146] Optionally, the name of the indication information is not limited, and it may be, for example, a temporary registration indication, a home control indication, or a reporting service network indication. For example, the indication information may be a temporary registration indication, used to indicate that the terminal's registration is temporary. For example, the indication information may be a home control indication, used to indicate that the home network needs to manage the service network where the terminal resides. For example, the indication information may be a reporting service network indication, used to instruct the terminal to report information about the service network where it resides; for example, the reporting service network indication could be a reporting service network name (SNN) indication.
[0147] Optionally, the fourth information may be sent by the second network function after receiving the terminal context management registration request message sent by the first network function. For example, after receiving the terminal context management registration request message sent by the first network function, the second network function determines that the terminal is temporarily registered and sends the fourth information to the first network function.
[0148] In some embodiments, the fourth information is sent via a terminal context management registration response message.
[0149] Optionally, the second network function sends a terminal context management registration response message to the first network function, the terminal context management registration response message including the fourth information. Correspondingly, the first network function receives the context management registration response message sent by the second network function, the terminal context management registration response message including the fourth information.
[0150] In some embodiments, step S2101 is optional.
[0151] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.
[0152] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomously implementing, among other meanings.
[0153] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "bit", and "data" can be used interchangeably.
[0154] In some embodiments, terms such as "certain", "preset", "specified", "default", "set", "indicated", "a certain", "any", and "first" can be used interchangeably. "Certain A", "preset A", "specified A", "default A", "set A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, specified A, a certain A, any A, or first A, but are not limited thereto.
[0155] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values (e.g., a comparison with a predetermined value), but is not limited thereto.
[0156] In step S2102, the first network function sends the second information to the terminal.
[0157] In some embodiments, the terminal receives second information sent by the first network function.
[0158] In some embodiments, the first network function is a mobility management function of a non-home network, and the second network function is a network function of the home network.
[0159] In some embodiments, after receiving the fourth information sent by the second network function, the first network function sends the second information to the terminal. Here, the fourth information is used by the first network function to send the second information to the terminal.
[0160] In some embodiments, the second information includes indication information. Optionally, the second information may include: indication information and a second identifier; the second identifier is used to indicate the terminal. Optionally, the second identifier may be used to uniquely identify the terminal.
[0161] In some embodiments, the name of the second information is not limited, and it may be, for example, a registration acceptance message.
[0162] Optionally, the indication information is used to indicate at least one of the following: the terminal's registration is temporary, the home network needs to manage the service network where the terminal is located, and the terminal reports information about the service network where the terminal is located.
[0163] Optionally, the name of the indication information is not limited; it may be, for example, a temporary registration indication or a home control indication. For example, the indication information could be a temporary registration indication, used to indicate that the terminal's registration is temporary. Alternatively, the indication information could be a home control indication, used to indicate that the home network needs to manage the service network to which the terminal resides.
[0164] In some embodiments, the second information is sent via a Registration Accept message.
[0165] Optionally, the second network function sends a registration acceptance message to the terminal, the registration acceptance message including second information. Correspondingly, the terminal receives the registration acceptance message sent by the second network function, the registration acceptance message including the second information.
[0166] In this embodiment of the disclosure, the interaction between the first network function and the terminal is through an access network device. Optionally, the first network function sending second information to the terminal includes: the first network function sending second information to the access network device, and the access network device sending second information to the terminal. Accordingly, the terminal receives the second information sent by the access network device, wherein the second information is received by the access network device from the first network function.
[0167] In some embodiments, step S2102 may be optional.
[0168] Step S2103: The terminal sends the first information to the first network function.
[0169] In some embodiments, the first network function receives first information sent by the terminal.
[0170] In some embodiments, the first network function is a mobility management function of a non-home network, and the second network function is a network function of a home network. In embodiments of this disclosure, the serving network, home network, or non-home network can all refer to any type of network; for example, the serving network, home network, and non-home network can all be PLMNs, etc.
[0171] In some embodiments, the first information includes protected first service network information.
[0172] In some embodiments, the first information may further include at least one of the following: a random number and a first identifier.
[0173] In some embodiments, the first information includes: protected first service network information and a random number.
[0174] In some embodiments, the first information includes: protected first service network information, a random number, and a first identifier.
[0175] In some embodiments, the first information includes: protected first service network information and protected first identifier, and a random number.
[0176] In some embodiments, the name of the first information is not limited, and it may be, for example, service network provided information or service network instruction information.
[0177] Optionally, the first identifier is used to indicate one of the following: the terminal, the terminal, and the serving network where the terminal is located. For example, the first identifier can be used to uniquely identify the terminal, or the first identifier can be used to uniquely identify both the terminal and the serving network where the terminal is located. For example, the first identifier can be a Globally Unique Temporary User Equipment Identity (GUTI).
[0178] In some embodiments, the first service network information is used by the second network function to determine whether the first service network information matches the second service network information of the network in which the first network function is located.
[0179] In some embodiments, the protected first service network information is protected by a secure association between the terminal and the second network function.
[0180] Optionally, the first service network information is used to indicate the service network in which the terminal is located.
[0181] Optionally, the first service network information is protected by end-to-end (e2e) security established between the terminal and the second network function.
[0182] Optionally, the protected first service network information may refer to: first service network information protected by a security key shared between the terminal and the second network function.
[0183] In some embodiments, the first serving network information, the second serving network information, and the third and fourth serving network information mentioned below may each include one of the following: Serving Network Name (SNN) and Serving Network Identifier. Optionally, the first serving network information may also include a first identifier (e.g., GUTI); the first identifier is used to indicate the terminal and the serving network where the terminal is located. Here, the first serving network information can be any information, as long as it can indicate the serving network where the terminal is located. Here, the first serving network information is sent by the terminal; the second serving network information comes from the first network function, or the second serving network information is used to indicate the network where the first network function is located; the third serving network information is stored in the second network function, or the third serving network information is used to indicate the serving network where the terminal was historically located; the fourth serving network information comes from the third network function, or the third serving network information is used to indicate the network where the third network function is located. Here, the third network function is a network function other than the home network.
[0184] In some embodiments, if the terminal detects that the serving network where the terminal is located has changed and is no longer its home network, it sends first information to the first network function.
[0185] In some embodiments, if the terminal receives second information sent by the first network function and determines that the second information includes indication information, it sends first information to the first network function. In other embodiments, the terminal actively sends the first information to the first network function.
[0186] In some embodiments, when the terminal moves and camps on a first cell or when the terminal intends to register with a network, it obtains information about the network it needs to register with. Here, the first cell can be any cell.
[0187] Optionally, the terminal receives system messages within the first cell. The system messages broadcast a first list, which includes one or more network identifiers, with each network identifier indicating a network. The terminal determines the network it needs to register with based on the network identifiers in the first list.
[0188] Optionally, if the first list includes a network identifier, the terminal determines to register with the network corresponding to that network identifier.
[0189] Optionally, if the first list includes multiple network identifiers, the terminal selects one network identifier from the multiple network identifiers and determines to register with the network corresponding to that network identifier; or, the terminal selects one network identifier from the multiple network identifiers according to its preferences and determines to register with the network corresponding to that network identifier.
[0190] Optionally, if the first list includes network identifiers for at least one of the following networks: Home Public Land Mobile Network (HPLMN), Equivalent Home Public Land Mobile Network (EHPLMN), and Visited Public Land Mobile Network (VPLMN), the terminal determines the network to register with based on the network's priority. Here, HPLMMN has a higher priority than EHPLMN, and EHPLMN has a higher priority than VPLMN.
[0191] In some embodiments, the first information is sent via one of the following: a RegistrationRequest message; or a Registration Complete message.
[0192] In some embodiments, the terminal sends a registration request message to a first network function, the registration request message including first information. Correspondingly, the first network function receives the registration request message sent by the terminal, the registration request message including the first information.
[0193] Optionally, when the terminal is in RRC idle state or RRC active state, the terminal sends a registration request message to the first network function, and the registration request message includes the first information.
[0194] Optionally, when the terminal is in RRC connected state, the terminal sends a registration request message to the first network function. The registration request message includes the first information. Here, the terminal sends the registration request message after switching from one network to another.
[0195] Optionally, if the terminal detects that the serving network it is in has changed and is no longer its home network, it sends a registration request message to the first network function. The registration request message includes the first information.
[0196] Optionally, when the first information is sent via a registration request message, steps S2101 and S2102 are not executed in this embodiment of the disclosure.
[0197] In some embodiments, the terminal sends a registration completion message to a first network function, the registration completion message including first information. Correspondingly, the first network function receives the registration completion message sent by the terminal, the registration completion message including the first information. Here, the first information may include: protected first service network information and protected first identifier, as well as a random number.
[0198] Optionally, if the terminal receives the second information sent by the first network function and determines that the second information includes indication information, it sends a registration completion message to the first network function, the registration completion message including the first information.
[0199] Optionally, if the terminal receives the second information sent by the first network function and determines that the second information includes indication information, and determines that the service network where the terminal is located has changed, the terminal sends a registration completion message to the first network function, the registration completion message including the first information.
[0200] Optionally, when the first information is sent via the registration completion message, steps S2101 and S2102 are executed in this embodiment of the disclosure.
[0201] In this embodiment of the disclosure, the interaction between the first network function and the terminal is through an access network device. Optionally, the terminal sending first information to the first network function includes: the terminal sending first information to the access network device, and the access network device sending first information to the first network function. Correspondingly, the first network function receives the first information sent by the access network device, wherein the first information is obtained by the access network device from the terminal.
[0202] In some alternative embodiments, the first network function determines to skip the primary authentication process. Optionally, after receiving the first information, if the first network function determines that the first information includes protected first service network information, it determines to skip the primary authentication process.
[0203] In some optional embodiments, the first network function determines to trigger the main authentication process. Optionally, after receiving the first information, the first network function determines to trigger the main authentication process if it determines that the first information does not include the first service network information.
[0204] In some embodiments, in 5G, the primary authentication process may refer to the core access two-way authentication process triggered by the AMF when the terminal initiates registration via the AMF. Similarly, in 6G or other evolved communication systems, primary authentication may refer to the core access two-way authentication process triggered by the first network function when the terminal initiates registration via the first network function. The primary authentication process may be as specified in existing protocols.
[0205] Step S2104: The first network function sends third information to the second network function.
[0206] In some embodiments, the second network function receives third information sent by the first network function.
[0207] In some embodiments, after receiving first information from the terminal, the first network function sends third information to the second network function. Here, the first information is used by the first network function to send the third information to the second network function.
[0208] In some embodiments, the first network function is a mobility management function of a non-home network, and the second network function is a network function of the home network.
[0209] In some embodiments, before the first network function sends the third information to the second network function, the method further includes: the first network function determining the second network function.
[0210] In some embodiments, the third information includes protected first service network information.
[0211] In some embodiments, the third information may further include at least one of the following: a random number and a first identifier.
[0212] In some embodiments, the third information may further include second service network information. In this disclosure, the second service network information may be carried within the third information and sent to the second network function along with the protected first service network information. Alternatively, in other embodiments, the first network function may send the second service network information to the second network function via other information.
[0213] In some embodiments, the third information includes: protected first service network information and a random number.
[0214] In some embodiments, the third information includes: protected first service network information, a random number, and a first identifier.
[0215] In some embodiments, the third information includes: protected first service network information and protected first identifier, as well as a random number.
[0216] In some embodiments, the name of the third information is not limited, and it may be, for example, information provided by the service network or information indicated by the service network.
[0217] Optionally, the first identifier can be the first identifier from step S2103. For example, the first identifier is used to indicate one of the following: the terminal, the terminal, and the service network to which the terminal resides.
[0218] In some embodiments, the first service network information and the second service network information can be the first service network information and the second service network information in step S2103, respectively.
[0219] In some embodiments, the first service network information is used by the second network function to determine whether the first service network information matches the second service network information of the network in which the first network function is located.
[0220] Optionally, the protected first service network information is protected by a secure association between the terminal and the second network function.
[0221] Optionally, the first service network information is protected by end-to-end security established between the terminal and the second network function.
[0222] Optionally, the protected first service network information may refer to: first service network information protected by a security key shared between the terminal and the second network function.
[0223] Optionally, both the first serving network information and the second serving network information can be one of the following: Serving Network Name (SNN) and Serving Network Identifier. Optionally, the first serving network information may also include a first identifier (e.g., GUTI); the first identifier is used to indicate the terminal and the serving network in which the terminal is located.
[0224] In some embodiments, the third information is sent via one of the following: a terminal context management registration request message, or a terminal context management registration update request message.
[0225] In some embodiments, a first network function sends a terminal context management registration request message to a second network function, the terminal context management registration request message including third information. Correspondingly, the second network function receives the terminal context management registration request message sent by the first network function, the terminal context management registration request message including the third information.
[0226] Optionally, when the terminal is in RRC idle state or RRC active state, the terminal sends a registration request message to the first network function, the registration request message including first information; the first network function sends a terminal context management registration request message to the second network function, the terminal context management registration request message including third information.
[0227] Optionally, when the terminal is in RRC connection state, the terminal sends a registration request message to the first network function, the registration request message including first information; the first network function sends a terminal context management registration request message to the second network function, the terminal context management registration request message including third information.
[0228] Optionally, if the terminal receives the second information sent by the first network function and determines that the second information includes indication information, it sends a registration completion message to the first network function, the registration completion message including the first information; the first network function sends a terminal context management registration request message to the second network function, the terminal context management registration request message including the third information.
[0229] In some embodiments, a first network function sends a Terminal Context Management Registration Update Request message to a second network function, the Terminal Context Management Registration Update Request message including third information. Correspondingly, the second network function receives the Terminal Context Management Registration Update Request message sent by the first network function, the Terminal Context Management Registration Update Request message including the third information. Here, the third information may include: protected first serving network information and protected first identifier, and a random number.
[0230] Optionally, if the terminal receives the second information sent by the first network function and determines that the second information includes indication information, it sends a registration completion message to the first network function, the registration completion message including the first information; the first network function sends a terminal context management registration update request message to the second network function, the terminal context management registration update request message including the third information.
[0231] Step S2105: The second network function determines whether the first service network information and the second service network information match.
[0232] In some embodiments, the first network function is a mobility management function of a non-home network, and the second network function is a network function of the home network.
[0233] In some embodiments, the first service network information and the second service network information are respectively the first service network information and the second service network information in step S2103 (or step S2104).
[0234] In some embodiments, before step S2105, the method further includes: decoding and verifying the third information to determine the first service network information.
[0235] Optionally, after receiving the third information, the second network function decodes and verifies the third information to determine the first service network information. Here, if the verification of the third information is successful, it means that the first service network information obtained by decoding the third information is trustworthy information; or, if the verification of the third information fails, it means that the obtained first service network information is untrustworthy information.
[0236] In some embodiments, the second network function determines that the first service network information and the second service network information match, or the second network function determines that the first service network information and the second service network information do not match.
[0237] Optionally, whether the first service network information matches the second service network information can be determined by whether the first service network information and the second service network information are the same, or whether the service networks indicated by the first service network information and the second service network information are the same.
[0238] Step S2106: The second network function performs the first operation based on the first service network information.
[0239] In some embodiments, the first network function is a mobility management function of a non-home network, and the second network function is a network function of the home network.
[0240] In some embodiments, the first service network information, the second service network information, and the third service network information are respectively the first service network information, the second service network information, and the third service network information in step S2103 (or step S2104).
[0241] In some embodiments, the first operation may include at least one of the following: accepting the registration request in the third information, storing the first service network information, replacing the locally stored third service network information with the first service network information, determining whether to accept the subsequent interaction process with the third network function based on the stored first service network information, rejecting the registration request in the third information, and sending a registration / deregistration process to the first network. Optionally, determining whether to accept the subsequent interaction process with the third network function based on the stored first service network information may include at least one of the following: accepting the request in the sixth information, or rejecting the request in the sixth information.
[0242] In some embodiments, if the first service network information matches the second service network information, the second network function accepts the registration requested in the third information. Optionally, the second network function decodes and verifies the third information to determine the first service network information, and if it determines that the first service network information matches the second service network information, it accepts the registration requested in the third information.
[0243] In some embodiments, if the second network function matches the first service network information, it stores the first service network information or replaces the locally stored third service network information with the first service network information. Optionally, the second network function decodes and verifies the third information to determine the first service network information, and if it determines that the first service network information matches the second service network information, it stores the first service network information or replaces the locally stored third service network information with the first service network information.
[0244] In some embodiments, the second network function may reject the registration requested in the third information and / or initiate a registration / deregistration process to the first network function based on at least one of the following: verification of the first service network information in the third information fails; the first service network information does not match the second service network information. Optionally, the second network function may also send a request for deregistration to the first network function. This applies to situations where the terminal provides the first service network information to the second network function in the registration request (including situations where the terminal is in RRC idle state or RRC non-active state, or the terminal is in RRC connected state).
[0245] Optionally, after receiving the third information, if the verification of the first service network information in the third information fails, the second network function may reject the registration request in the third information and / or initiate a registration / deregistration process to the first network function. Here, failure to verify the first service network information in the third information means that decoding and verifying the third information reveals that the first service network information is untrusted.
[0246] Optionally, after receiving the third information, if the second network function successfully verifies the first service network information in the third information and determines that the first service network information does not match the second service network information, it may reject the registration request in the third information and / or initiate a registration / deregistration process to the first network function. Here, successful verification of the first service network information in the third information means that the first service network information is obtained by decoding and verifying the third information.
[0247] In some embodiments, the second network function initiates a registration / deregistration process to the first network function based on at least one of the following: failure to receive third information before the timer expires, wherein the timer starts at the time when the fourth information is sent; failure to verify the first service network information in the third information; or a mismatch between the first service network information and the second service network information. This is adapted to the situation where the terminal provides the first service network information to the second network function upon completion of registration.
[0248] Optionally, the second network function starts a timer after sending the fourth message. If the third message is not received by the timer expires, it determines to initiate a registration / deregistration process to the first network function.
[0249] Optionally, after receiving the terminal context management registration request message sent by the first network function, the second network function starts a timer. If no third information is received before the timer expires, the second network function determines to initiate a registration / deregistration process to the first network function.
[0250] Optionally, after receiving the third information, if the verification of the first service network information in the third information fails, the second network function may reject the registration request in the third information and / or initiate a registration / deregistration process to the first network function. Here, failure to verify the first service network information in the third information means that decoding and verifying the third information reveals that the first service network information is untrusted. Here, the second network function has already completed the temporary registration of the terminal before receiving the third information.
[0251] Optionally, after receiving the third information, if the second network function successfully verifies the first service network information in the third information and determines that the first service network information does not match the second service network information, it may reject the registration request in the third information and / or initiate a registration / deregistration process to the first network function. Here, successful verification of the first service network information in the third information means that the first service network information is obtained by decoding and verifying the third information. Here, the second network function has already completed the temporary registration of the terminal before receiving the third information.
[0252] In some embodiments, when the second network function receives the sixth information sent by the third network function, it determines whether the fourth service network information included in the sixth information matches the first network service information; the third network function is a network function outside the home network, or the third network function is a network function outside the home network; if the fourth service network information matches the first service network information, it accepts the request in the sixth information; or if the fourth service network information does not match the first service network information, it rejects the request in the sixth information.
[0253] In some embodiments, the third network function sends a sixth message to the second network function.
[0254] Optionally, the sixth information may include a variety of information, so the name is not limited; it may be, for example, a request or a request for authorization.
[0255] Optionally, the sixth piece of information can be any requested information during or after the terminal's registration process. Optionally, the request in the sixth piece of information can be any request, such as a request for contract information, terminal context, management data, or data for performing various business operations.
[0256] For example, the sixth piece of information could be a contract data management retrieval request (e.g., Nudm_SDM_GET) or a contract data management subscription request (Nudm_SDM_Subscribe) during the registration request process.
[0257] For example, the sixth piece of information could be a contract data management information notification (Nudm_SDM_Info) or a terminal context management update request (Nudm_UECM_Update) during the registration request process.
[0258] Optionally, the fourth service network information is used to indicate the service network in which the third network function resides.
[0259] Optionally, during the registration process, the second network function receives a sixth message from the third network function and determines whether the stored first service network information matches the fourth service network information of the network where the third network function resides. If they match, the request in the sixth message is accepted; otherwise, if they do not match, the request in the sixth message is rejected. Here, the sixth message is sent by the terminal during the registration process.
[0260] Optionally, after the second network function completes the registration process, the sixth message sent by the third network function is based on whether the stored first service network information matches the fourth service network information of the network where the third network function is located; if they match, the request in the sixth message is accepted, or if they do not match, the request in the sixth message is rejected. Here, the sixth message is sent by the terminal after the registration process is completed.
[0261] Step S2107: The second network function sends the fifth information to the first network function.
[0262] In some embodiments, the first network function receives fifth information sent by the second network function.
[0263] In some embodiments, the fifth message is used to confirm successful registration. Optionally, the fifth message includes an indication to confirm successful registration.
[0264] In some embodiments, the name of the fifth message is not limited, and it may be, for example, a confirmation of success.
[0265] In some embodiments, the fifth message is sent via one of the following: a terminal context management registration response message, or a terminal context management registration update response message.
[0266] Optionally, the second network function sends a terminal context management registration response message to the first network function, the terminal context management registration response message including the fifth information. Correspondingly, the first network function receives the terminal context management registration response message sent by the second network function, the terminal context management registration response message including the fifth information.
[0267] Optionally, the second network function sends a terminal context management registration update response message to the first network function, the terminal context management registration update response message including the fifth information. Correspondingly, the first network function receives the terminal context management registration update response message sent by the second network function, the terminal context management registration update response message including the fifth information.
[0268] In some embodiments, at least one of steps S2101 to S2107 is performed. For example, the second network function sends fourth information to the first network function; the first network function sends second information to the terminal; the terminal sends first information to the first network function; the first network function sends third information to the second network function; the second network function decodes and verifies the third information to determine first service network information and to determine whether the first service network information matches the second service network information; if the first service network information matches the second service network information, the registration requested in the third information is accepted; if the first service network information does not match the second service network information, the registration requested in the third information is rejected; the second network function sends fifth information to the first network function. Optionally, upon receiving sixth information from the third network function, the second network function determines whether the fourth service network information of the network where the third network function is located matches the first network service information; if the fourth service network information matches the first service network information, the request in the sixth information is accepted; or, if the fourth service network information does not match the first service network information, the request in the sixth information is rejected.
[0269] In some embodiments, at least one of steps S2103 to S2106 is performed. For example, the terminal sends first information to a first network function; the first network function sends third information to a second network function; the second network function decodes and verifies the third information to determine first service network information and whether the first service network information matches the second service network information; if the first service network information matches the second service network information, the registration requested in the third information is accepted; if the first service network information does not match the second service network information, the registration requested in the third information is rejected; if the second network function receives sixth information sent by the third network function, it determines whether fourth service network information of the network where the third network function is located matches the first network service information; if the fourth service network information matches the first service network information, the request in the sixth information is accepted; or, if the fourth service network information does not match the first service network information, the request in the sixth information is rejected. Optionally, the sixth information may be sent during the registration request process.
[0270] In the embodiments disclosed herein, the interaction between networks may be conducted directly or through intermediate nodes or relay nodes (such as Service Communication Proxy (SCP) or gateways or inter-network interaction proxies or routing functions or corresponding network functions with routing functions such as AMF, etc.).
[0271] The information processing method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2107. For example, step S2101 can be implemented as an independent embodiment; step S2102 can be implemented as an independent embodiment; step S2103 can be implemented as an independent embodiment; step S2104 can be implemented as an independent embodiment; step S2105 can be implemented as an independent embodiment; step S2106 can be implemented as an independent embodiment; step S2107 can be implemented as an independent embodiment; the combination of steps S2101 and S2102 can be implemented as an independent embodiment; the combination of steps S2103 and S2104 can be implemented as an independent embodiment; the combination of steps S2101 to S2104 can be implemented as an independent embodiment; the combination of steps S2103 to S2106 can be implemented as an independent embodiment; the combination of steps S2101 to S2106 can be implemented as an independent embodiment; the combination of steps S2101 to S2107 can be implemented as an independent embodiment.
[0272] In some embodiments, steps S2101, S2102 and S2106 may be optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0273] In some embodiments, step S2106 may be optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0274] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0275] Figure 3 This is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure. For example... Figure 3 As shown, this disclosure relates to an information processing method for a communication system 100, the method comprising one of the following steps:
[0276] Step S3101: The terminal sends first information to the first network function, wherein the first information includes protected first service network information.
[0277] For optional implementations of step S3101, please refer to [link / reference]. Figure 2 Optional implementation methods in step S2103, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.
[0278] In step S3102, the first network function sends third information to the second network function, wherein the third information includes protected first service network information.
[0279] For optional implementations of step S3102, please refer to [link / reference]. Figure 2 Optional implementation methods in step S2104, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.
[0280] In some embodiments, the first service network information is used by the second network function to determine whether the first service network information matches the second service network information of the network where the first network function is located; wherein, the first network function is a mobility management function of a non-home network, and the second network function is a network function of the home network.
[0281] In some embodiments, before the first network function sends the third information to the second network function, it further includes one of the following: the first network function determines to skip the main authentication process based on the fact that the first information includes protected first service network information; or determines to trigger the main authentication process based on the fact that the first information does not include first service network information.
[0282] In some embodiments, the terminal sending first information to the first network function includes: when the terminal detects that the serving network where the terminal is located has changed and is no longer its home network, sending first information to the first network function.
[0283] In some embodiments, the protected first service network information is protected by a secure association between the terminal and the second network function.
[0284] In some embodiments, the first information further includes at least one of the following: a random number; a first identifier, wherein the first identifier is used to indicate one of the following: a terminal, the terminal, and the service network in which the terminal is located.
[0285] In some embodiments, the first information is sent via one of the following: a registration request message; or a registration completion message.
[0286] In some embodiments, before the second network function receives the third information sent by the first network function, the method further includes: the second network function sending a fourth information to the first network function, wherein the fourth information includes indication information; wherein the indication information is used to indicate at least one of the following: the terminal's registration is temporary, the home network needs to manage the service network where the terminal is located, and the terminal reports information about the service network where the terminal is located.
[0287] In some embodiments, when the first information is sent via a registration completion message, the method further includes: a first network function sending second information to the terminal, wherein the second information includes indication information; wherein the indication information is used to indicate at least one of the following: the terminal's registration is temporary, the home network needs to manage the service network where the terminal is located, and the terminal reports information about the service network where the terminal is located.
[0288] In some embodiments, the third information further includes at least one of the following: a random number, a first identifier, and second service network information; wherein the first identifier is used to indicate one of the following: a terminal, the terminal, and the service network in which the terminal is located.
[0289] In some embodiments, the third information is sent via one of the following: a terminal context management registration request message, or a terminal context management registration update request message.
[0290] In some embodiments, the method further includes: a second network function sending fifth information to the terminal, wherein the fifth information is used to confirm successful registration.
[0291] In some embodiments, the fifth information is received via one of the following: a terminal context management registration response message, or a terminal context management registration update response message.
[0292] In some embodiments, the method further includes: a second network function decoding and verifying the third information to determine the first service network information; and determining whether the first service network information matches the second service network information.
[0293] In some embodiments, the method further includes: if the second network function matches the first service network information, performing at least one of the following: accepting the registration requested in the third information; storing the first service network information or replacing the locally stored third service network information with the first service network information.
[0294] In some embodiments, the method further includes: when the second network function receives the sixth information sent by the third network function, determining whether the fourth service network information of the network where the third network function is located matches the first network service information; the third network function is not a network function of its own network; if the fourth service network information matches the first service network information, accepting the request in the sixth information; or, if the fourth service network information does not match the first service network information, rejecting the request in the sixth information.
[0295] In some embodiments, the sixth information is sent during the terminal's registration process, or the sixth information is sent after the terminal's registration process is completed.
[0296] In some embodiments, the method further includes: the second network function rejecting the registration request in the third information based on at least one of the following: verification of the first service network information in the third information fails; the first service network information does not match the second service network information; or, the second network function initiating a registration / deregistration process to the first network function based on at least one of the following: the third information is not received before the timer expires, wherein the start time of the timer is the time when the fourth information is sent; verification of the first service network information in the third information fails; the first service network information does not match the second service network information.
[0297] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0298] The primary objective of this disclosure is to implement enhanced home network control to prevent fraudulent attacks across networks (e.g., PLMNs) without requiring master authentication for each serving NF. Here, the UE can be a terminal, or the terminal can be a UE.
[0299] In some embodiments, when a UE intends to connect to the network, it needs to identify the serving PLMN before attempting registration. When the UE reads SIB1 during cell search:
[0300] (1) If the PLMN ID list contains only one PLMN ID (Mobile Country Code (MCC) + Mobile Network Code (MNC)), then it is registered with the broadcast PLMN; or,
[0301] (2) It selects a PLMN from the broadcast PLMN ID list based on Universal Subscriber Identity Module (USIM) preferences or user selection.
[0302] In some embodiments, when the UE sends an initial registration request, the serving AMF indicates the Serving Network Name (SNN) information to the home network. The SNN is a concatenation of the service code and the PLMN ID of the serving network. If the home network confirms the serving PLMN during the primary authentication process, the serving AMF responds with the assigned PLMN and Tracking Area Identity (TAI) in a registration acceptance message encoded in the GUTI assigned to the UE. After successful registration, the UE stores the registered PLMN in its USIM and Non-Access Stratum (NAS) contexts. This means that the UE maintains PLMN information in internal contexts of different layers:
[0303] (1) The currently resident PLMN is stored in the RRC layer context for radio resource management;
[0304] (2) The currently registered PLMN is stored in the NAS layer context and is used for routing and service access;
[0305] (3) The last registered PLMN is stored in the USIM or Mobile Equipment (ME) memory as a priority for future cell selection.
[0306] In some embodiments, the UE learns about its connected PLMN in the following ways:
[0307] (1) System messages (e.g., SIB1) are broadcast upon initial access (MCC / MNC);
[0308] (2) NAS registration confirmation (PLMN registered with AMF);
[0309] (3) GUTI code (embedded with PLMN identifier);
[0310] (4) The internal storage context (the last PLMN registered in the USIM).
[0311] If a UE detects a PLMN change (e.g., due to UE mobility reselection via roaming, handover, or automatically or manually by the user from the PLMN) and is not already registered in that PLMN, it will typically initiate the registration process. This is common when the UE detects the change via system information or mobility events.
[0312] In existing communication systems, since the gNB or AMF knows the PLMN of the serving cell, the UE does not need to send PLMN information to the network. In this embodiment, it is recommended that the UE include the SNN in each registration process triggered by a PLMN change.
[0313] In 6G systems or other evolved systems, we assume that the UE and the home network can establish an end-to-end security mechanism to protect the information exchanged between the UE and the home network. Based on this assumption, the UE can send the serving cell's PLMN information to the home network, which is protected by end-to-end security, so that the serving network or any third party cannot tamper with the serving cell PLMN information received by the home network.
[0314] The home network stores the service PLMN information received from the UE during UE registration. Whenever a serving NF sends a request to the home network (e.g., a UDM), the home network checks whether the PLMN ID of the serving NF matches the service PLMN ID received from the UE. If they match, the home network accepts the request from the serving NF. If they do not match, the home network rejects the request from the serving NF.
[0315] In some embodiments, the UE's primary authentication is performed during the initial registration process. After successful primary authentication, the authentication result and the Service Network Name (SNN) containing the PLMN ID are stored in the UDM. When the UE's response to the authentication request is successfully verified, the AUSF notifies the UDM.
[0316] During the primary authentication process, the SNN constructed by the UE is bound to the RES* calculated by the UE, while the SNN sent from the serving network (e.g., MMF) to the home network is bound to the XERS* calculated by the home network (ARSF). Therefore, the successful verification of the RES* and XRES* match performed by the home network (e.g., AUSF) confirms that the PLMN selected by the UE is the PLMN claimed by the serving network.
[0317] Example 1: The UE reports SNN (UE mobility in RRC_IDLE or RRC_INACTIVE) in the registration request.
[0318] After performing the initial registration process for UE primary authentication, the UE can move across networks in idle mode. It is recommended that whenever the UE detects a change in the PLMN, it include the Service Node Name (SNN) in the registration request message, which is secured using end-to-end security established with the Home Network (UDM). The UDM verifies and stores the SNN, and uses the SNN to check the serving network of the serving NF subsequently requested.
[0319] Figure 4A This is a flowchart illustrating an information processing method according to an embodiment of the present disclosure. Figure 4A As shown, this disclosure relates to an information processing method, which includes:
[0320] In step S4101, the UE detects a change in the PLMN.
[0321] Optionally, the UE moves and camps on the new cell. The UE detects the new PLMN by reading SIB1 broadcast by the aNB. The UE checks the PLMN priority (HPLMN > EHPLMN > VPLMN). If the new PLMN is acceptable, the UE initiates a registration request.
[0322] In step S4102, the UE sends a registration request to the target aNB.
[0323] Optionally, the registration request may include: protected SNN, GUTI, and random numbers.
[0324] Optionally, the UE uses a security key shared with the UDM to protect the SNN.
[0325] Step S4103: The target aNB forwards the registration request to the target MMF.
[0326] Optionally, aNB selects a target MMF and routes the registration request to the selected target MMF.
[0327] Optionally, the registration request includes: a protected SNN, a GUTI, and a random number. The UE uses a security key shared with the UDM to protect the SNN.
[0328] Step S4104: The target MMF sends a communication service UE context transfer request (e.g., Namf_Communication_UEContextTransfer request) to the source MMF.
[0329] Optionally, the target MMF uses the UE's GUTI to determine the source MMF, and then initiates the Namf_Communication_UEContextTransfer procedure to obtain the UE's permanent ID (e.g., Subscription Permanent Identifier (SUPI)) and UE context from the source MMF.
[0330] Step S4105: Select UDM as the target MMF.
[0331] Optionally, after receiving the protected SNN from the UE, the target MMF may determine to skip the main authentication process based on a local policy.
[0332] Optionally, if the target MMF does not receive a protected SNN from the UE, the primary authentication process should be triggered.
[0333] Optionally, the target MMF selects the UDM in the home network based on the UE's SUPI.
[0334] In step S4106, the target MMF sends a UE context management registration request (e.g., Nudm_UECM_Registration Request) to the UDM or ARPF.
[0335] Optionally, the target MMF registers the access to be registered with the UDM (and subscribes to receive notifications when the UDM unregisters the target MMF).
[0336] Optionally, the Nudm_UECM_Registration request includes the protected SNN from the UE.
[0337] Step S4107: UDM or ARPF validates the SNN and examines the SNN.
[0338] Optionally, upon receiving a Nudm_UECM_Registration request, the UDM or ARPF first verifies the protected SNN. If verification is successful, the UDM or ARPF checks whether the SNN from the UE matches the serving network ID of the network where the target MMF resides. Alternatively, if verification fails, or the SNN from the UE does not match the serving network ID of the network where the target MMF resides, the UDM or ARPF rejects the Nudm_UECM_Registration request.
[0339] Optionally, the UDM or ARPF will only accept the Nudm_UECM_Registration request and store the newly received SNN by replacing the old SNN if the SNN is successfully verified and matches the service network ID of the network where the target MMF is located.
[0340] In step S4108, the UDM or ARPF sends a UE context management registration response (e.g., Nudm_UECM_Registration response) to the target MMF.
[0341] Step S4109, UDM or ARPF performs subsequent procedures based on stored SNN.
[0342] Optionally, for subsequent processes from the service network (such as Nudm_SDM_Get, Nudm_SDM Subscription), the UDM or ARPF will check the service network ID of the network where the requesting NF is located based on the stored SNN before accepting the request.
[0343] In step S4110, the target MMF sends a registration acceptance message to the target aNB.
[0344] Step S4111: The target aNB sends a registration acceptance message to the UE.
[0345] Step S4112, UDM or ARPF performs subsequent procedures based on stored SNN.
[0346] Optionally, for subsequent processes from the service network (e.g., Nudm_SDM_Info, Nudm_UECM_Update), the UDM checks the service network ID of the requesting NF based on the stored SNN before accepting the request.
[0347] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0348] Example 2: The UE reports the SNN (Switchover of UE in RRC connected state) in the registration request.
[0349] When a UE moves in connected mode, it can move from one PLMN to another. In this case, N2 handover is performed via MMF reallocation. During handover preparation, the target MMF creates the UE context requested by the source MMF and obtains the UE ID and UE context. During handover execution, the target MMF in the serving network does not interact with the UDM in the home network until the UE initiates the registration process. During registration, the target MMF then requests UECM registration from the UDM. Therefore, it is recommended that whenever a UE initiates the registration process during N2 handover and detects a PLMN change, it includes the SNN in the registration request message, which is protected with end-to-end security established with the home network (UDM). The UDM verifies and stores the SNN, and the UDM checks the serving network of the subsequently requested serving NF based on the SNN.
[0350] Figure 4B This is a flowchart illustrating an information processing method according to an embodiment of the present disclosure. Figure 4B As shown, this disclosure relates to an information processing method, which includes:
[0351] Step S4201: The UE sends a measurement report to the source aNB.
[0352] In step S4202, the source aNB sends a handover request to the source MMF.
[0353] Optionally, the source aNB determines that relocation is triggered via N2 and sends a handover request message to the source MMF.
[0354] In step S4203, the source MMF sends a UE context creation request (e.g., Namf_Communication_CreateUEContext request) to the target MMF.
[0355] Optionally, the source MMF sends a Namf_Communication_CreateUEContext request to the target MMF, which includes the UE ID and UE context.
[0356] Step S4204: The target MMF sends a handover request to the target aNB.
[0357] In step S4205, the target aNB returns a handover request confirmation to the target MMF.
[0358] Step S4206: The target MMF returns a UE context creation response (e.g., Namf_Communication_CreateUEContext response) to the source MMF.
[0359] In step S4207, the source MMF sends a switch command to the source aNB.
[0360] Step S4208: The source aNB sends a handover command to the UE.
[0361] Step S4209: The UE sends a handover confirmation to the target aNB.
[0362] Optionally, after successfully synchronizing with the target cell, the UE sends a handover confirmation to the target aNB. The UE considers the handover successful upon receiving this confirmation.
[0363] Optionally, the UE detects a change in the PLMN during synchronization with the target cell.
[0364] In step S4210, the target aNB sends a handover notification to the target MMF.
[0365] Optionally, a switch notification can be used to determine whether the switch is considered successful in the target aNB.
[0366] Step S4211: Interactive switching notification between the target MMF and the source MMF.
[0367] Optionally, the target MMF may notify the source MMF of the N2 handover notification received from the target aNB by invoking the N2 information notification service (e.g., Namf_Communication_N2InfoNotify) procedure.
[0368] In step S4212, the UE sends a registration request to the target aNB.
[0369] Optionally, the UE initiates a mobility registration update process, such as sending a registration request to the target aNB.
[0370] Optionally, the registration request may include: protected SNN, GUTI, and random numbers.
[0371] Optionally, the UE uses a security key shared with the UDM to protect the SNN.
[0372] Step S4213: The target aNB sends a registration request to the target MMF.
[0373] Optionally, the target aNB selects a target MMF and routes the registration request to the selected target MMF.
[0374] Optionally, the registration request includes: a protected SNN, a GUTI, and a random number. The UE uses a security key shared with the UDM to protect the SNN.
[0375] In step S4214, the target MMF sends a UE context management registration request (e.g., Nudm_UECM_Registration Request) to the UDM or ARPF.
[0376] Optionally, the target MMF registers the access to be registered with the UDM (and subscribes to receive notifications when the UDM unregisters the target MMF).
[0377] Optionally, the Nudm_UECM_Registration request includes the protected SNN from the UE.
[0378] Step S4215: UDM or ARPF validates the SNN and examines the SNN.
[0379] Optionally, upon receiving a Nudm_UECM_Registration request, the UDM or ARPF first verifies the protected SNN. If verification is successful, the UDM or ARPF checks whether the SNN from the UE matches the serving network ID of the network where the target MMF resides. Alternatively, if verification fails, or the SNN from the UE does not match the serving network ID of the network where the target MMF resides, the UDM or ARPF rejects the Nudm_UECM_Registration request.
[0380] Optionally, the UDM or ARPF will only accept the Nudm_UECM_Registration request and store the newly received SNN by replacing the old SNN if the SNN is successfully verified and matches the service network ID of the network where the target MMF is located.
[0381] In step S4216, the UDM or ARPF sends a UE context management registration response (e.g., Nudm_UECM_Registration response) to the target MMF.
[0382] Step S4217, UDM or ARPF performs subsequent procedures based on stored SNN.
[0383] Optionally, for subsequent processes from the service network (such as Nudm_SDM_Get, Nudm_SDM Subscription), the UDM checks the service network ID of the requesting NF based on the stored SNN before accepting the request.
[0384] In step S4218, the target MMF sends a registration acceptance message to the target aNB.
[0385] Step S4219: The target aNB sends a registration acceptance message to the UE.
[0386] In this embodiment of the disclosure, it is not necessary to execute the target MMF to send a communication service UE context transfer request to the source MMF to obtain the UE context; because the UE context transfer has already been performed in steps S4203 and S4206 during the handover preparation phase.
[0387] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0388] Example 3: The UE reports the SNN upon completion of registration.
[0389] If the UE does not report its SNN in the registration request, it is recommended that the UE report its SNN or a new GUTI in the registration completion message after receiving the registration acceptance message. The SNN and / or the new GUTI are protected by end-to-end security between the UE and the UDM. If the UDM does not receive the protected SNN or the new GUTI after receiving the UECM registration request from the MMF, or if the verification of the protected SNN and / or the new GUTI fails, the UDM will deregister the MMF and assume that the UE has not registered with the requested PLMN.
[0390] Figure 4C This is a flowchart illustrating an information processing method according to an embodiment of the present disclosure. Figure 4C As shown, this disclosure relates to an information processing method, which includes:
[0391] In step S4301, the UE detects a change in the PLMN.
[0392] Optionally, the UE moves and camps on the new cell. The UE detects the new PLMN by reading SIB1 broadcast by the aNB. The UE checks the PLMN priority (HPLMN > EHPLMN > VPLMN). If the new PLMN is acceptable, the UE initiates a registration request.
[0393] In step S4302, the UE sends a registration request to the target aNB.
[0394] Optionally, the UE sends a registration request including the old GUTI to the target aNB.
[0395] Step S4303: The target aNB sends a registration request to the target MMF.
[0396] Optionally, the target aNB selects a target MMF and routes the registration request to the selected target MMF.
[0397] Optionally, the registration request may include the old GUTI.
[0398] Step S4304: The target MMF sends a communication service UE context transfer request (e.g., Namf_Communication_UEContextTransfer request) to the source MMF.
[0399] Optionally, the target MMF uses the UE's GUTI to determine the source MMF, and then initiates the Namf_Communication_UEContextTransfer procedure to obtain the UE's permanent ID (e.g., Subscription Permanent Identifier (SUPI)) and UE context from the source MMF.
[0400] In step S4305, the target MMF sends a UE context management registration request (e.g., Nudm_UECM_Registration Request) to the UDM or ARPF.
[0401] Optionally, the target MMF determines to skip the main authentication process based on a local policy. The target MMF then uses the Nudm_UECM_Registration procedure to register the access to be registered with the UDM (and subscribes to receive notifications when the UDM deregisters the target MMF).
[0402] Step S4306: The UDM or ARPF temporarily registers the current PLMN of the UE declared by the target MMF.
[0403] In step S4307, the UDM or ARPF sends a UE context management registration response (e.g., Nudm_UECM_Registration response) to the target MMF.
[0404] Optionally, the Nudm_UECM_Registration response includes an indication of temporary registration or home control, which is protected by an end-to-end security context shared with the UE. Optionally, this temporary registration or home indication can be the indication information found in previous embodiments.
[0405] In step S4308, the target MMF sends a registration acceptance message to the target aNB.
[0406] Optionally, the registration acceptance message may include instructions regarding protected home control.
[0407] Step S4309: The target aNB sends a registration acceptance message to the UE.
[0408] Optionally, the registration acceptance message may include instructions for protected temporary registration or ownership control.
[0409] In step S4310, the UE sends a registration completion message to the target aNB.
[0410] Optionally, if the UE receives a protected indication from the home control in the registration acceptance message, the UE verifies the protected indication and then protects the SNN and / or the new GUTI with the end-to-end security context shared with the UDM.
[0411] Optionally, the UE may include the protected SNN or a new GUTI and a random number in the registration completion message sent to the target MMF via the target aNB.
[0412] Step S4311: The target aNB sends a registration completion message to the target MMF.
[0413] Optionally, the registration completion message includes: a protected SNN or a new GUTI, and a random number.
[0414] In step S4312, the target MMF sends a UE context management registration or registration update request (e.g., Nudm_UECM_Registration / RegistrationUpdate request) to the UDM or ARPF.
[0415] Optionally, the Nudm_UECM_Registration / RegistrationUpdate request includes: a protected SNN and / or a new GUTI, and a random number.
[0416] Step S4313: UDM or ARPF verifies the SNN and confirms the registration.
[0417] Optionally, the UDM or ARPF uses the security context shared with the UE to verify the received SNN and / or the new GUTI. If the verification is successful, the UDM or ARPF will confirm the temporary MMF registration in step S4306.
[0418] Optionally, if verification fails, the UDM or APRF will initiate a deregistration process for the target MMF under the following conditions:
[0419] (1) When the timer that started after receiving the UECM registration request from the target MMF expired, the UDM did not receive the registration completion message;
[0420] (2) The protected SNN and / or the new GUTI validation failed;
[0421] (3) The verified SNN and / or the new GUTI do not match the SNN declared by the target MMF in step S4312.
[0422] In step S4314, the UDM or ARPF sends a UE context management registration or registration update response (e.g., Nudm_UECM_Registration / RegistrationUpdate response) to the target MMF.
[0423] Optionally, the Nudm_UECM_Registration / RegistrationUpdate response includes an indication of registration confirmation.
[0424] Optionally, starting from step S4314, the UDM or ARPF can authorize subsequent requests from the service NF based on the SNN and / or the new GUTI confirmed in step S4313.
[0425] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0426] In some embodiments, protection of the SNN and / or the new GUTI may be based on a communication protocol or a predefined encryption and integrity protection mechanism, the difference being that the random number sent from the UE to the UDM or ARPF replaces the communication protocol or the predefined COUNT value.
[0427] In some embodiments, the UE performs at least one of the following:
[0428] The UE should be able to generate random numbers.
[0429] The UE should be able to use the security context and nonce shared with the UDM to protect the SNN (or to protect the SNN and the new GUTI).
[0430] The UE should be able to include the protected SNN (or the protected SNN and the new GUTI) and HN-COUNT / nonce in the registration request message.
[0431] The UE should be able to send a registration completion message after receiving a registration acceptance based on the received home control indication.
[0432] The UE should be able to include the protected SNN (or the protected SNN and the new GUTI) and a random number in the registration completion message.
[0433] In some embodiments, the UDM performs at least one of the following:
[0434] The UDM should be able to protect and send home control indications to the UE via the MMF.
[0435] The UDM should be able to receive the protected SNN (or the protected SNN and the new GUTI) and a random number from the UE via the MMF in the UECM registration or update request message.
[0436] The UDM should be able to decrypt and verify the received SNN and / or new GUTI using the security context and random number shared with the UDM.
[0437] UDM should be able to store validated SNNs and replace older SNNs when available.
[0438] UDM should be able to return a registration confirmation instruction to MMF.
[0439] The UDM should be able to apply operations to subsequent UE-related processes (such as Nudm_UECM_Registration_Request, Nudm_SDM_Get, Nudm_UECM Registration) based on the stored SNN.
[0440] In some embodiments, MMF performs at least one of the following:
[0441] MMF should be able to receive the protected SNN (or the protected SNN and the new GUTI) and a random number from the UE via a registration request message.
[0442] MMF should be able to receive the protected SNN (or the protected SNN and the new GUTI) and a random number from the UE via a registration completion message.
[0443] MMF should be able to receive the protected SNN (or the protected SNN and the new GUTI) and a random number from the UE via a registration completion message.
[0444] MMF should be able to send a protected SNN (or a protected SNN and a new GUTI) and random numbers to UDM.
[0445] The MMF should be able to receive temporary registration instructions from the UDM.
[0446] The MMF should be able to receive registration confirmation instructions from the UDM.
[0447] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0448] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by network devices (e.g., access network devices, core network functional nodes, core network devices (e.g., first network function, second network function, third network function)) in any of the above methods.
[0449] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an Application-Specific Integrated Circuit (ASIC), and the functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), which can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.
[0450] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).
[0451] Figure 5A This is a schematic diagram of the structure of the terminal 5100 provided in an embodiment of this disclosure. For example... Figure 5A As shown, terminal 5100 includes at least one of a first transceiver module 5101 and a first processing module 5102. In some embodiments, the first transceiver module 5101 is used to send first information to a first network function. Optionally, the first transceiver module 5101 is used to perform at least one of the sending and / or receiving steps performed by terminal 5100 in any of the above methods (e.g., steps S2102 and / or S2103, but not limited thereto), which will not be elaborated here. In some embodiments, the first processing module 5102 is used to perform at least one of the processing steps performed by terminal 5100 in any of the above methods, which will not be elaborated here.
[0452] Figure 5B This is a schematic diagram of the structure of the first network function 5200 provided in an embodiment of this disclosure. For example... Figure 5BAs shown, the first network function 5200 includes a second transceiver module 5201 and a second processing module 5202. In some embodiments, the second transceiver module 5201 is used to receive first information sent by the terminal, etc. Optionally, the second transceiver module 5201 is used to perform at least one of the sending and / or receiving steps performed by the first network function 5200 in any of the above methods (e.g., steps S2101, S2102, S2104 and / or S2107, etc., but not limited thereto), which will not be elaborated here. In some embodiments, the second processing module 5102 is used to perform at least one of the processing steps performed by the first network function 5200 in any of the above methods, which will not be elaborated here.
[0453] Figure 5C This is a schematic diagram of the structure of the second network function 5300 provided in an embodiment of this disclosure. For example... Figure 5C As shown, the second network function 5300 includes a third transceiver module 5301 and a third processing module 5302. In some embodiments, the third transceiver module 5301 is used to receive third information, etc., sent by the first network function. Optionally, the third transceiver module 5301 is used to perform at least one of the sending and / or receiving steps performed by the second network function 5300 in any of the above methods (e.g., steps S2101, S2102, S2104 and / or step S2107, etc., but not limited thereto), which will not be elaborated here. In some embodiments, the third processing module 5302 is used to perform a handover check. Optionally, the third processing module 5302 is used to perform at least one of the processing steps performed by the second network function 5300 in any of the above methods (e.g., steps S2105 and / or step S2106, etc., but not limited thereto), which will not be elaborated here.
[0454] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver. Exemplarily, the first transceiver module described above includes a first transmitting module and / or a first receiving module. Exemplarily, the second transceiver module described above includes a second transmitting module and / or a second receiving module. Exemplarily, the third transceiver module described above includes a third transmitting module and / or a third receiving module.
[0455] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.
[0456] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.
[0457] Figure 6A This is a schematic diagram of the structure of the communication device 6100 proposed in this embodiment. The communication device 6100 can be a network device (e.g., an access network device (e.g., a base station), a core network device (e.g., a first network function, a second network function, a third network function, etc.), a terminal, a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments; please refer to the description in the above method embodiments for details.
[0458] like Figure 6A As shown, the communication device 6100 is used to execute any of the above methods. In some embodiments, the communication device 6100 includes one or more processors 6101. The processor 6101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 6100 is used to execute any of the above methods. Optionally, one or more processors 6101 are used to invoke instructions to cause the communication device 6100 to execute any of the above methods.
[0459] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2102, S2103, S2105, and / or S2107, but not limited thereto), and the processor 6101 performs at least one of other steps (e.g., steps S2105 and / or S2107, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.
[0460] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data and / or instructions. Optionally, one or more processors 6101 are used to invoke instructions stored in the memory 6103 to cause the communication device 6100 to perform any of the above methods. Optionally, all or part of the memory 6103 may also be located outside the communication device 6100. In an optional embodiment, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuit 6104 is connected to the memory 6103 and can be used to receive data and / or instructions from the memory 6103 or other devices, and can be used to send data and / or instructions to the memory 6103 or other devices. For example, the interface circuit 6104 can read data and / or instructions stored in the memory 6103 and send the data and / or instructions to the processor 6101.
[0461] The communication device 6100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may vary. Figure 6A The limitations. The communication device may be a standalone device or part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally including storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.
[0462] Figure 6B This is a schematic diagram of the structure of chip 6200 according to an embodiment of this disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to... Figure 6B The diagram shown is a schematic representation of the structure of chip 6200, but it is not limited to this.
[0463] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.
[0464] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data and / or instructions. Optionally, all or part of the memories 6203 may be located outside of chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data and / or instructions from memory 6203 or other devices, and interface circuit 6202 can be used to send data and / or instructions to memory 6203 or other devices. For example, interface circuit 6202 can read data and / or instructions stored in memory 6203 and send the data and / or instructions to processor 6201.
[0465] In some embodiments, the interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S2101, S2102, S2103, S2105, and / or S2107, but not limited thereto). The interface circuit 6202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 6202 performing data and / or instruction interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of other steps (e.g., steps S2105 and / or S2106, but not limited thereto).
[0466] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.
[0467] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.
[0468] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.
[0469] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.
Claims
1. An information processing method, characterized in that, Executed by the terminal, including: Send first information to a first network function, wherein the first information includes protected first service network information; Wherein, the first service network information is used by the second network function to determine whether the first service network information matches the second service network information of the network in which the first network function is located; The first network function is a mobility management function for a non-home network, and the second network function is a network function for a home network.
2. The method according to claim 1, characterized in that, Sending the first information to the first network function includes: If it is detected that the service network where the terminal is located has changed and is no longer the home network, the first information is sent to the first network function.
3. The method according to claim 1, characterized in that, The protected first service network information is protected by the secure association between the terminal and the second network function.
4. The method according to any one of claims 1 to 3, characterized in that, The first information also includes at least one of the following: Random numbers; A first identifier, wherein the first identifier is used to indicate one of the following: the terminal, the terminal, and the service network to which the terminal is located.
5. The method according to any one of claims 1 to 4, characterized in that, The first information is sent via one of the following: Registration request message; Registration complete message.
6. The method according to claim 5, characterized in that, When the first information is sent via the registration completion message, the method further includes: Receive second information sent by the first network function, wherein the second information includes indication information; The indication information is used to indicate at least one of the following: the terminal's registration is temporary, the home network needs to manage the service network where the terminal is located, and the terminal reports information about the service network where the terminal is located.
7. The method according to claim 6, characterized in that, The second information is received through registration and message acceptance.
8. The method according to any one of claims 1 to 7, characterized in that, The first network function is a mobility management function; and / or, The second network function is one of the following: unified data management, unified data storage, identity authentication storage and processing functions.
9. An information processing method, characterized in that, Performed by the first network function, including: The receiving terminal sends first information, wherein the first information includes protected first service network information; Send a third message to the second network function, wherein the third message includes the protected first service network information; Wherein, the first service network information is used by the second network function to determine whether the first service network information matches the second service network information of the network where the first network function is located; The first network function is a mobility management function for a non-home network, and the second network function is a network function for a home network.
10. The method according to claim 9, characterized in that, The protected first service network information is protected by the secure association between the terminal and the second network function.
11. The method according to claim 9 or 10, characterized in that, The first information further includes at least one of the following: a random number, a first identifier; and / or, The third information also includes at least one of the following: a random number, a first identifier, and the second service network information; The first identifier is used to indicate one of the following: the terminal, the terminal, and the service network to which the terminal is located.
12. The method according to any one of claims 9 to 11, characterized in that, The first information is received via one of the following: a registration request message, a registration completion message; and / or, The third information is sent via one of the following: a terminal context management registration request message, or a terminal context management registration update request message.
13. The method according to claim 12, characterized in that, When the first information is received after registration, the method further includes: Receive fourth information sent by the second network function, wherein the fourth information includes indication information; Send a second message to the terminal, wherein the second message includes the indication message; The indication information is used to indicate at least one of the following: the terminal's registration is temporary, the home network needs to manage the service network where the terminal is located, and the terminal reports information about the service network where the terminal is located.
14. The method according to claim 13, characterized in that, The method further includes: The system receives a fifth message sent by the second network function, wherein the fifth message is used to confirm successful registration.
15. The method according to claim 13 or 14, characterized in that, The fourth information is received via a terminal context management registration response message; and / or, The second information is sent by registering to receive messages; and / or, The fifth message is received via one of the following: Terminal Context Management Registration Response Message, Terminal Context Management Registration Update Response Message.
16. The method according to any one of claims 9 to 15, characterized in that, Before sending the third information to the second network function, one of the following is also included: Based on the fact that the first information includes the protected first service network information, it is determined to skip the main authentication process; Based on the fact that the first service network information is not included in the first information, it is determined that the main authentication process will be triggered.
17. The method according to any one of claims 9 to 16, characterized in that, The first network function is a mobility management function; and / or, The second network function is one of the following: unified data management, unified data storage, identity authentication storage and processing functions.
18. An information processing method, characterized in that, Performed by the second network function, including: Receive third information sent by the first network function, wherein the third information includes protected first service network information; Wherein, the first service network information is used by the second network function to determine whether the first service network information matches the second service network information of the network in which the first network function is located; The first network function is a mobility management function for a non-home network, and the second network function is a network function for a home network.
19. The method according to claim 18, characterized in that, The protected first service network information is protected by a secure association between the terminal and the second network function.
20. The method according to claim 18 or 19, characterized in that, The method further includes: The third information is decoded and verified to determine the first service network information; Determine whether the first service network information matches the second service network information.
21. The method according to claim 20, characterized in that, The method further includes: If the first service network information matches the second service network information, perform at least one of the following: Accept the registration request in the third piece of information; The first service network information can be stored, or the locally stored third service network information can be replaced with the first service network information.
22. The method according to claim 21, characterized in that, The method further includes: Upon receiving the sixth information sent by the third network function, determine whether the fourth service network information included in the sixth information matches the first network service information; the third network function is a non-homed network function. If the fourth service network information matches the first service network information, the request in the sixth information is accepted; or... If the fourth service network information does not match the first service network information, the request in the sixth information is rejected.
23. The method according to claim 22, characterized in that, The sixth piece of information is sent during the terminal's registration process, or it is sent after the terminal's registration process is completed.
24. The method according to claim 20, characterized in that, The method further includes: The registration request in the third information is rejected based on at least one of the following: Verification of the first service network information in the third information failed; The first service network information does not match the second service network information; or, The registration / deregistration process is initiated for the first network function based on at least one of the following: If the third message is not received before the timer expires, wherein the start time of the timer is the time when the fourth message is sent; Verification of the first service network information in the third information failed; The first service network information does not match the second service network information.
25. The method according to any one of claims 18 to 24, characterized in that, The third information also includes at least one of the following: a random number, a first identifier, and the second service network information; The first identifier is used to indicate one of the following: a terminal, the terminal, and the service network in which the terminal is located.
26. The method according to any one of claims 18 to 25, characterized in that, Before receiving the third information sent by the first network function, the method further includes: Send a fourth message to the first network function, wherein the fourth message includes indication information; The indication information is used to indicate at least one of the following: the terminal's registration is temporary, the home network needs to manage the service network where the terminal is located, and the terminal reports information about the service network where the terminal is located.
27. The method according to claim 26, characterized in that, The method further includes: The fifth message sent to the first network function, wherein the fifth message is used to confirm successful registration.
28. The method according to any one of claims 18 to 27, characterized in that, The third information is sent via one of the following: a terminal context management registration request message, a terminal context management registration update request message; and / or, The fourth piece of information is sent via the terminal context management registration response message; and / or, The fifth message is sent via one of the following: Terminal Context Management Registration Response Message, Terminal Context Management Registration Update Response Message.
29. The method according to any one of claims 18 to 28, characterized in that, The first network function is a mobility management function; and / or, The second network function is one of the following: unified data management, unified data storage, identity authentication storage and processing functions.
30. An information processing method, characterized in that, Performed by a communication system, the communication system including a terminal, a first network function, and a second network function, the method includes: The terminal sends first information to the first network function, wherein the first information includes protected first service network information; The first network function sends third information to the second network function, wherein the third information includes protected first service network information; Wherein, the first service network information is used by the second network function to determine whether the first service network information matches the second service network information of the network in which the first network function is located; The first network function is a mobility management function for a non-home network, and the second network function is a network function for a home network.
31. A communication device, characterized in that, The communication device is used to perform the information processing method according to any one of claims 1 to 8, or claims 9 to 17, or claims 18 to 29.
32. A communication system, characterized in that, include: A terminal, a first network function, and a second network function; wherein the terminal is configured to implement the information processing method of any one of claims 1 to 8, the first network function is configured to implement the information processing method of any one of claims 9 to 17, and the second network function is configured to implement the information processing method of any one of claims 18 to 29.
33. A storage medium storing instructions, characterized in that, When the instructions are executed on the communication device, the communication device performs the information processing method as described in any one of claims 1 to 8, or claims 9 to 17, or claims 18 to 29.
34. A computer program product, comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by a communication device, it implements the information processing method according to any one of claims 1 to 8, or claims 9 to 17, or claims 18 to 29.
