Communication method and device, communication equipment, communication system and storage medium

Abstract

The embodiment of the invention provides a communication method and device, communication equipment, a communication system and a storage medium. The method comprises the following steps: sending a first NAI to network equipment; wherein the first NAI comprises first information and second information, the first information is used for indicating a first domain corresponding to the network equipment, the second information is used for indicating a second domain corresponding to a certificate holder of the terminal, and the first domain is an NPN. According to the technical scheme provided by the embodiment of the invention, NSWO can be realized under the condition that the certificate holder and the WLAN-AN are in different domains.

Description

Communication method and device, communication equipment, communication system and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a communication method and apparatus, communication equipment, a communication system, and a storage medium. Background Art

[0002] In the field of communications technology, non-seamless WLAN offload (NSWO) allows a terminal to access an access network under a non-public network (NPN) without requiring the access network to register with the fifth-generation system (5GS). During NSWO, the terminal and the NPN can achieve mutual authentication based on a shared key.

[0003] Summary of the Invention

[0004] In an NPN scenario, if the NPN and the credentials holder (CH) of the terminal are in different domains, the access network in the NPN needs to route authentication-related messages from the terminal to the credentials holder.

[0005] Embodiments of the present disclosure provide a communication method and apparatus, a communication device, a communication system, and a storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, a communication method is provided. The method is performed by a terminal. The method includes: sending a first network access identifier (NAI) to a network device; wherein the first NAI includes first information and second information, the first information is used to indicate a first domain corresponding to the network device, and the second information is used to indicate a second domain corresponding to a credential holder of the terminal, where the first domain is an NPN.

[0007] According to a second aspect of an embodiment of the present disclosure, a communication method is provided. The method is performed by a network device. The method includes receiving a first NAI from a terminal; the first NAI includes first information and second information, the first information indicating a first domain corresponding to the network device, and the second information indicating a second domain corresponding to a credential holder of the terminal, where the first domain is an NPN.

[0008] According to a third aspect of an embodiment of the present disclosure, a communication device is provided. The device is disposed in a terminal. The device includes: a sending module configured to send a first NAI to a network device; the first NAI includes first information and second information, the first information indicating a first domain corresponding to the network device, and the second information indicating a second domain corresponding to a credential holder of the terminal, where the first domain is an NPN.

[0009] According to a fourth aspect of an embodiment of the present disclosure, a communication device is provided. The device is disposed in a network device. The device includes: a receiving module configured to receive a first NAI from a terminal; the first NAI includes first information and second information, the first information indicating a first domain corresponding to the network device, and the second information indicating a second domain corresponding to a credential holder of the terminal, where the first domain is an NPN.

[0010] According to a fifth aspect of an embodiment of the present disclosure, a communication device is provided. The communication device includes at least one processor. The processor is configured to invoke instructions to execute the communication method described in the first aspect or the second aspect.

[0011] According to a sixth aspect of an embodiment of the present disclosure, a communication system is provided. The communication system includes a terminal and a network device. The terminal is configured to implement the communication method described in the first aspect. The network device is configured to implement the communication method described in the second aspect.

[0012] According to a seventh aspect of the embodiments of the present disclosure, a storage medium is provided. The storage medium stores instructions. When the instructions are executed by a processor, the communication method according to the first aspect or the second aspect is performed.

[0013] According to an eighth aspect of the embodiments of the present disclosure, a computer program or computer program product is provided. The computer program or computer program product includes code. When the instructions are executed by a processor, the communication method according to the first or second aspect is performed.

[0014] According to an embodiment of the present disclosure, the first NAI sent by a terminal to a network device contains both first and second information. The first information indicates the domain corresponding to the network device, and the second information indicates the domain corresponding to the terminal's credential holder. Based on the received first NAI, the network device obtains the domain corresponding to the network device and the domain corresponding to the credential holder, thereby routing verification-related information from the terminal to the credential holder. This allows the credential holder in the second domain to complete verification of the NPN in the first domain, achieving NSWO.

[0015] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory and do not constitute limitations on the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present invention and, together with the description, serve to explain the principles of the embodiments of the present invention.

[0017] FIG1 is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0018] FIG2 is a schematic diagram of a specific NSWO architecture of a communication system provided according to an embodiment of the present disclosure.

[0019] FIG3 is an interactive diagram of a communication method provided according to an embodiment of the present disclosure.

[0020] FIG4 is a flow chart of a communication method according to an embodiment of the present disclosure.

[0021] FIG5 is a flow chart of a communication method according to an embodiment of the present disclosure.

[0022] FIG6 is an interactive diagram of a communication method provided according to an embodiment of the present disclosure.

[0023] FIG7 is an interactive diagram of a communication method provided according to an embodiment of the present disclosure.

[0024] FIG8 is a schematic structural diagram of a communication device provided according to an embodiment of the present disclosure.

[0025] FIG9 is a schematic structural diagram of a communication device provided according to an embodiment of the present disclosure.

[0026] FIG10 is a schematic structural diagram of a communication device provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0027] Embodiments of the present disclosure provide a communication method and apparatus, a communication device, a communication system, and a storage medium.

[0028] In a first aspect, embodiments of the present disclosure provide a communication method. The method is performed by a terminal. The method includes: sending a first NAI to a network device. The first NAI includes first information and second information. The first information indicates a first domain corresponding to the network device. The second information indicates a second domain corresponding to a credential holder of the terminal. The first domain is an NPN.

[0029] According to an embodiment of the present disclosure, the first NAI sent by a terminal to a network device contains both first and second information. The first information indicates the domain corresponding to the network device, and the second information indicates the domain corresponding to the terminal's credential holder. Based on the received first NAI, the network device obtains the domain corresponding to the network device and the domain corresponding to the credential holder, thereby routing verification-related information from the terminal to the credential holder. This allows the credential holder in the second domain to complete verification of the NPN in the first domain, achieving NSWO.

[0030] In combination with some embodiments of the first aspect, in some embodiments, the second domain may be one of the following types: a PLMN, an NPN, or a domain to which an AAA server belongs.

[0031] In conjunction with some embodiments of the first aspect, in some embodiments, the first NAI may satisfy the following format: CHrealm! username@NPNrealm; wherein CHrealm represents the second information, username represents the user name, and NPNrealm represents the first information, and CHrealm, username, and NPNrealm are separated by ! and @.

[0032] According to an embodiment of the present disclosure, for NSWO in NPN, second information of the domain corresponding to the credential holder is added on the basis of the existing NAI format. This can simultaneously include information of the first domain where the NPN is located and the second domain where the credential holder is located on the basis of making minimal modifications to the NAI format in the existing standard.

[0033] In combination with some embodiments of the first aspect, in some embodiments, the first information may include a first NID, a first MNC, and a first MCC of the first domain.

[0034] In conjunction with some embodiments of the first aspect, in some embodiments, the second domain may be a PLMN. The second information may include a second MNC and a second MCC of the second domain.

[0035] In combination with some embodiments of the first aspect, in some embodiments, the second domain may be a PLMN. The second information may satisfy the following format: 5gc-nswo..mnc <chmnc>.mcc <chmcc>.3gppnetwork.org; 5gc-nswo is the NSWO label, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>It is used to indicate the second MCC of the second domain, where 3gppnetwork.org is the domain name.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, the second domain may be a PLMN. The first NAI may satisfy the following format: 5gc-nswo.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org!<username of SUCI in NAI format>@5gc-nswo.nid <nid>.mnc <servingmnc>.mcc <servingmcc>.3gppnetwork.org; 5gc-nswo is the NSWO label, 3gppnetwork.org is the domain name, username is used to indicate the user name in SUCI, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>Used to indicate the second MCC of the second domain, nid <nid>Used to indicate the first NID of the first domain, mnc <servingmnc>Used to indicate the first MNC of the first domain, mcc <servingmcc>Used to indicate the first MCC of the first domain.

[0037] According to the embodiment of the present disclosure, the NAI includes relevant information of the PLMN where the certificate holder is deployed, namely, the MNC and MCC, thereby identifying the second domain where the certificate holder is located, namely, the PLMN.

[0038] In conjunction with some embodiments of the first aspect, in some embodiments, the second domain may be an NPN. The second information may include a second NID, a second MNC, and a second MCC of the second domain.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the second domain may be NPN. The second information may satisfy the following format: 5gc-nswo.nid <chnid>.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org; 5gc-nswo is the NSWO label, nid <chnid>The second NID used to indicate the second domain, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>It is used to indicate the second MCC of the second domain, where 3gppnetwork.org is the domain name.

[0040] In conjunction with some embodiments of the first aspect, in some embodiments, the second domain may be NPN. The first NAI may satisfy the following format: 5gc-nswo.nid <chnid>.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org!<username of SUCI in NAI format>@5gc-nswo.nid <servingnid>.mnc <servingmnc>.mcc <servingmcc>.3gppnetwork.org; 5gc-nswo is the NSWO label, 3gppnetwork.org is the domain name, username is used to indicate the user name in SUCI, nid <chnid>The second NID used to indicate the second domain, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>Used to indicate the second MCC of the second domain, the second NID <servingnid>Used to indicate the first NID of the first domain, mnc <servingmnc>Used to indicate the first MNC of the first domain, mcc <servingmcc>Used to indicate the first MCC of the first domain.

[0041] According to the embodiment of the present disclosure, the NAI includes relevant information of the NPN where the credential holder is deployed, namely, the NID, MNC and MCC, thereby identifying the second domain where the credential holder is located, namely, the NPN.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the second domain may be a domain to which the AAA server belongs. The second information may include indication information of the domain to which the AAA server belongs.

[0043] In conjunction with some embodiments of the first aspect, in some embodiments, the second domain may be an AAA server. The second information may satisfy the following format: 5gc-nswo.AAArealm, where 5gc-nswo is an NSWO tag and AAArealm is information indicating the domain to which the AAA server belongs.

[0044] In conjunction with some embodiments of the first aspect, in some embodiments, the second domain may be an AAA server. The first NAI may satisfy the following format: 5gc-nswo.AAArealm!<username of SUCI in NAI format> @5gc-nswo.nid <nid>.mnc <servingmnc>.mcc <servingmcc>.3gppnetwork.org; where 5gc-nswo is the NSWO label, 3gppnetwork.org is the domain name, username is used to indicate the user name in SUCI, AAArealm is the domain to which the AAA server belongs, and nid <nid>Used to indicate the first NID of the first domain, mnc <servingmnc>Used to indicate the first MNC of the first domain, mcc <servingmcc>Used to indicate the first MCC of the first domain.

[0045] In combination with some embodiments of the first aspect, in some embodiments, the indication information of the domain to which the AAA server belongs may include the FQDN of the AAA server.

[0046] According to the embodiment of the present disclosure, the NAI includes relevant information of the AAA server where the credential holder is deployed, that is, indication information of the domain to which the AAA server belongs, thereby identifying the second domain where the credential holder is located.

[0047] With reference to some embodiments of the first aspect, in some embodiments, the first NAI may be carried in an EAP response message.

[0048] According to the embodiment of the present disclosure, the first NAI can be sent to the network device in an EAP response message during the EAP authentication process. In this way, the network device can obtain the first NAI in a timely manner during the EAP authentication process and complete the authentication.

[0049] In conjunction with some embodiments of the first aspect, in some embodiments, before sending the first NAI to the network device, the method may further include: receiving third information from the network device. The third information is used by the terminal to determine the format of the first NAI.

[0050] With reference to some embodiments of the first aspect, in some embodiments, the third information may be carried in an EAP request message.

[0051] According to an embodiment of the present disclosure, third information can be sent to a terminal in an EAP request message during an EAP authentication process. Based on the third information, the terminal can determine the format of the first NAI. In this way, when the terminal sends an EAP response message, it can determine the NAI format of the first NAI based on the specific situation.

[0052] In conjunction with some embodiments of the first aspect, in some embodiments, the network device may be located in a WLAN-AN.

[0053] In a second aspect, embodiments of the present disclosure provide a communication method. The method is performed by a network device. The method includes receiving a first NAI from a terminal. The first NAI includes first information and second information. The first information indicates a first domain corresponding to the network device. The second information indicates a second domain corresponding to a credential holder of the terminal. The first domain is an NPN.

[0054] In combination with some embodiments of the second aspect, in some embodiments, the second domain may be one of the following types: a PLMN, an NPN, or a domain to which an AAA server belongs.

[0055] In conjunction with some embodiments of the second aspect, in some embodiments, the first NAI may satisfy the following format: CHrealm! username@NPNrealm; wherein CHrealm represents the second information, username represents the user name, and NPNrealm represents the first information, and CHrealm, username, and NPNrealm are separated by ! and @.

[0056] In combination with some embodiments of the second aspect, in some embodiments, the first information may include a first NID, a first MNC, and a first MCC of the first domain.

[0057] In conjunction with some embodiments of the second aspect, in some embodiments, the second domain may be a PLMN. The second information may include a second MNC and a second MCC of the second domain.

[0058] In conjunction with some embodiments of the second aspect, in some embodiments, the second domain may be a PLMN. The second information may satisfy the following format: 5gc-nswo..mnc <chmnc>.mcc <chmcc>.3gppnetwork.org; 5gc-nswo is the NSWO label, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>It is used to indicate the second MCC of the second domain, where 3gppnetwork.org is the domain name.

[0059] In conjunction with some embodiments of the second aspect, in some embodiments, the second domain may be a PLMN. The first NAI may satisfy the following format: 5gc-nswo.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org!<username of SUCI in NAI format>@5gc-nswo.nid <nid>.mnc <servingmnc>.mcc <servingmcc>.3gppnetwork.org; 5gc-nswo is the NSWO label, 3gppnetwork.org is the domain name, username is used to indicate the user name in SUCI, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>Used to indicate the second MCC of the second domain, nid <nid>Used to indicate the first NID of the first domain, mnc <servingmnc>Used to indicate the first MNC of the first domain, mcc <servingmcc>Used to indicate the first MCC of the first domain.

[0060] In conjunction with some embodiments of the second aspect, in some embodiments, the second domain may be an NPN. The second information may include a second NID, a second MNC, and a second MCC of the second domain.

[0061] In conjunction with some embodiments of the second aspect, in some embodiments, the second domain may be NPN. The second information may satisfy the following format: 5gc-nswo.nid <chnid>.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org; 5gc-nswo is the NSWO label, nid <chnid>The second NID used to indicate the second domain, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>It is used to indicate the second MCC of the second domain, where 3gppnetwork.org is the domain name.

[0062] In conjunction with some embodiments of the second aspect, in some embodiments, the second domain may be NPN. The first NAI may satisfy the following format: 5gc-nswo.nid <chnid>.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org!<username of SUCI in NAI format>@5gc-nswo.nid <servingnid>.mnc <servingmnc>.mcc <servingmcc>.3gppnetwork.org; 5gc-nswo is the NSWO label, 3gppnetwork.org is the domain name, username is used to indicate the user name in SUCI, nid <chnid>The second NID used to indicate the second domain, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>Used to indicate the second MCC of the second domain, nid <servingnid>Used to indicate the first NID of the first domain, mnc <servingmnc>Used to indicate the first MNC of the first domain, mcc <servingmcc>Used to indicate the first MCC of the first domain.

[0063] In conjunction with some embodiments of the second aspect, in some embodiments, the second domain may be a domain to which the AAA server belongs. The second information may include indication information of the domain to which the AAA server belongs.

[0064] In conjunction with some embodiments of the second aspect, in some embodiments, the second domain may be an AAA server. The second information may satisfy the following format: 5gc-nswo.AAArealm, where 5gc-nswo is an NSWO tag and AAArealm is information indicating the domain to which the AAA server belongs.

[0065] In conjunction with some embodiments of the second aspect, in some embodiments, the second domain may be an AAA server. The first NAI may satisfy the following format: 5gc-nswo.AAArealm!<username of SUCI in NAI format> @5gc-nswo.nid <nid>.mnc <servingmnc>.mcc <servingmcc>.3gppnetwork.org; where 5gc-nswo is the NSWO label, 3gppnetwork.org is the domain name, username is used to indicate the user name in SUCI, AAArealm is the domain to which the AAA server belongs, and nid <nid>Used to indicate the first NID of the first domain, mnc <servingmnc>Used to indicate the first MNC of the first domain, mcc <servingmcc>Used to indicate the first MCC of the first domain.

[0066] In combination with some embodiments of the second aspect, in some embodiments, the indication information of the domain to which the AAA server belongs may include the FQDN of the AAA server.

[0067] With reference to some embodiments of the second aspect, in some embodiments, the first NAI may be carried in an EAP response message.

[0068] In conjunction with some embodiments of the second aspect, in some embodiments, before receiving the first NAI from the terminal, the method may further include: sending third information to the terminal, where the third information is used by the terminal to determine the format of the first NAI.

[0069] In combination with some embodiments of the second aspect, in some embodiments, the third information may be carried in an EAP request message.

[0070] In conjunction with some embodiments of the second aspect, in some embodiments, after receiving the first NAI from the terminal, the method may further include: generating a second NAI based on the first NAI. The second NAI is generated by removing the first information from the first NAI.

[0071] In conjunction with some embodiments of the second aspect, in some embodiments, the network device may be located in a WLAN-AN.

[0072] In conjunction with some embodiments of the second aspect, in some embodiments, after generating the second NAI based on the first NAI, the method may further include:

[0073] The second NAI is sent to the NSWOF or AAA server corresponding to the credential holder.

[0074] In a third aspect, embodiments of the present disclosure provide a communications device. The device is disposed in a terminal. The device includes a sending module. The sending module is configured to send a first NAI to a network device. The first NAI includes first information and second information. The first information indicates a first domain corresponding to the network device. The second information indicates a second domain corresponding to a credential holder of the terminal. The first domain is an NPN.

[0075] In combination with some embodiments of the third aspect, in some embodiments, the second domain may be one of the following types: a PLMN, an NPN, or a domain to which an AAA server belongs.

[0076] In conjunction with some embodiments of the third aspect, in some embodiments, the first NAI may satisfy the following format: CHrealm! username@NPNrealm; wherein CHrealm represents the second information, username represents the user name, and NPNrealm represents the first information, and CHrealm, username, and NPNrealm are separated by ! and @.

[0077] In combination with some embodiments of the third aspect, in some embodiments, the first information may include a first NID, a first MNC, and a first MCC of the first domain.

[0078] In conjunction with some embodiments of the third aspect, in some embodiments, the second domain may be a PLMN. The second information may include a second MNC and a second MCC of the second domain.

[0079] In conjunction with some embodiments of the third aspect, in some embodiments, the second domain may be a PLMN. The second information may satisfy the following format: 5gc-nswo..mnc <chmnc>.mcc <chmcc>.3gppnetwork.org; 5gc-nswo is the NSWO label, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>It is used to indicate the second MCC of the second domain, where 3gppnetwork.org is the domain name.

[0080] In conjunction with some embodiments of the third aspect, in some embodiments, the second domain may be a PLMN. The first NAI may satisfy the following format: 5gc-nswo.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org!<username of SUCI in NAI format>@5gc-nswo.nid <nid>.mnc <servingmnc>.mcc <servingmcc>.3gppnetwork.org; 5gc-nswo is the NSWO label, 3gppnetwork.org is the domain name, username is used to indicate the user name in SUCI, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>Used to indicate the second MCC of the second domain, nid <nid>Used to indicate the first NID of the first domain, mnc <servingmnc>Used to indicate the first MNC of the first domain, mcc <servingmcc>Used to indicate the first MCC of the first domain.

[0081] In conjunction with some embodiments of the third aspect, in some embodiments, the second domain may be an NPN. The second information may include a second NID, a second MNC, and a second MCC of the second domain.

[0082] In conjunction with some embodiments of the third aspect, in some embodiments, the second domain may be NPN. The second information may satisfy the following format: 5gc-nswo.nid <chnid>.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org; 5gc-nswo is the NSWO label, nid <chnid>The second NID used to indicate the second domain, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>It is used to indicate the second MCC of the second domain, where 3gppnetwork.org is the domain name.

[0083] In conjunction with some embodiments of the third aspect, in some embodiments, the second domain may be NPN. The first NAI may satisfy the following format: 5gc-nswo.nid <chnid>.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org!<username of SUCI in NAI format>@5gc-nswo.nid <servingnid>.mnc <servingmnc>.mcc <servingmcc>.3gppnetwork.org; 5gc-nswo is the NSWO label, 3gppnetwork.org is the domain name, username is used to indicate the user name in SUCI, nid <chnid>The second NID used to indicate the second domain, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>Used to indicate the second MCC of the second domain, nid <servingnid>Used to indicate the first NID of the first domain, mnc <servingmnc>Used to indicate the first MNC of the first domain, mcc <servingmcc>Used to indicate the first MCC of the first domain.

[0084] In conjunction with some embodiments of the third aspect, in some embodiments, the second domain may be a domain to which the AAA server belongs. The second information may include indication information of the domain to which the AAA server belongs.

[0085] In conjunction with some embodiments of the third aspect, in some embodiments, the second domain may be an AAA server. The second information may satisfy the following format: 5gc-nswo.AAArealm, where 5gc-nswo is an NSWO tag and AAArealm is information indicating the domain to which the AAA server belongs.

[0086] In conjunction with some embodiments of the third aspect, in some embodiments, the second domain may be an AAA server. The first NAI may satisfy the following format: 5gc-nswo.AAArealm!<username of SUCI in NAI format> @5gc-nswo.nid <nid>.mnc <servingmnc>.mcc <servingmcc>.3gppnetwork.org; where 5gc-nswo is the NSWO label, 3gppnetwork.org is the domain name, username is used to indicate the user name in SUCI, AAArealm is the domain to which the AAA server belongs, and nid <nid>Used to indicate the first NID of the first domain, mnc <servingmnc>Used to indicate the first MNC of the first domain, mcc <servingmcc>Used to indicate the first MCC of the first domain.

[0087] In combination with some embodiments of the third aspect, in some embodiments, the indication information of the domain to which the AAA server belongs may include the FQDN of the AAA server.

[0088] With reference to some embodiments of the third aspect, in some embodiments, the first NAI may be carried in an EAP response message.

[0089] In conjunction with some embodiments of the third aspect, in some embodiments, the apparatus may further include a receiving module configured to receive third information from a network device, wherein the third information is used by the terminal to determine a format of the first NAI.

[0090] In combination with some embodiments of the third aspect, in some embodiments, the third information may be carried in an EAP request message.

[0091] In combination with some embodiments of the third aspect, in some embodiments, the network device may be located in a WLAN-AN.

[0092] In a fourth aspect, embodiments of the present disclosure provide a communications device. The device is disposed in a network device. The device includes a receiving module. The receiving module is configured to receive a first NAI from a terminal. The first NAI includes first information and second information. The first information indicates a first domain corresponding to the network device. The second information indicates a second domain corresponding to a credential holder of the terminal. The first domain is an NPN.

[0093] In combination with some embodiments of the fourth aspect, in some embodiments, the second domain may be one of the following types: a PLMN, an NPN, or a domain to which an AAA server belongs.

[0094] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first NAI may satisfy the following format: CHrealm! username@NPNrealm; wherein CHrealm represents the second information, username represents the user name, and NPNrealm represents the first information, and CHrealm, username, and NPNrealm are separated by ! and @.

[0095] In combination with some embodiments of the fourth aspect, in some embodiments, the first information may include a first NID, a first MNC, and a first MCC of the first domain.

[0096] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second domain may be a PLMN. The second information may include a second MNC and a second MCC of the second domain.

[0097] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second domain may be a PLMN. The second information may satisfy the following format: 5gc-nswo..mnc <chmnc>.mcc <chmcc>.3gppnetwork.org; 5gc-nswo is the NSWO label, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>It is used to indicate the second MCC of the second domain, where 3gppnetwork.org is the domain name.

[0098] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second domain may be a PLMN. The first NAI may satisfy the following format: 5gc-nswo.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org!<username of SUCI in NAI format>@5gc-nswo.nid <nid>.mnc <servingmnc>.mcc <servingmcc>.3gppnetwork.org; 5gc-nswo is the NSWO label, 3gppnetwork.org is the domain name, username is used to indicate the user name in SUCI, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>Used to indicate the second MCC of the second domain, nid <nid>Used to indicate the first NID of the first domain, mnc <servingmnc>Used to indicate the first MNC of the first domain, mcc <servingmcc>Used to indicate the first MCC of the first domain.

[0099] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second domain may be an NPN. The second information may include a second NID, a second MNC, and a second MCC of the second domain.

[0100] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second domain may be NPN. The second information may satisfy the following format: 5gc-nswo.nid <chnid>.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org; 5gc-nswo is the NSWO label, nid <chnid>The second NID used to indicate the second domain, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>It is used to indicate the second MCC of the second domain, where 3gppnetwork.org is the domain name.

[0101] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second domain may be NPN. The first NAI may satisfy the following format: 5gc-nswo.nid <chnid>.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org!<username of SUCI in NAI format>@5gc-nswo.nid <servingnid>.mnc <servingmnc>.mcc <servingmcc>.3gppnetwork.org; 5gc-nswo is the NSWO label, 3gppnetwork.org is the domain name, username is used to indicate the user name in SUCI, nid <chnid>The second NID used to indicate the second domain, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>Used to indicate the second MCC of the second domain, nid <servingnid>Used to indicate the first NID of the first domain, mnc <servingmnc>Used to indicate the first MNC of the first domain, mcc <servingmcc>Used to indicate the first MCC of the first domain.

[0102] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second domain may be a domain to which the AAA server belongs. The second information may include indication information of the domain to which the AAA server belongs.

[0103] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second domain may be an AAA server. The second information may satisfy the following format: 5gc-nswo.AAArealm, where 5gc-nswo is an NSWO tag and AAArealm is information indicating the domain to which the AAA server belongs.

[0104] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second domain may be an AAA server. The first NAI may satisfy the following format: 5gc-nswo.AAArealm!<username of SUCI in NAI format> @5gc-nswo.nid <nid>.mnc <servingmnc>.mcc <servingmcc>.3gppnetwork.org; where 5gc-nswo is the NSWO label, 3gppnetwork.org is the domain name, username is used to indicate the user name in SUCI, AAArealm is the domain to which the AAA server belongs, and nid <nid>Used to indicate the first NID of the first domain, mnc <servingmnc>Used to indicate the first MNC of the first domain, mcc <servingmcc>Used to indicate the first MCC of the first domain.

[0105] In combination with some embodiments of the fourth aspect, in some embodiments, the indication information of the domain to which the AAA server belongs may include the FQDN of the AAA server.

[0106] With reference to some embodiments of the fourth aspect, in some embodiments, the first NAI may be carried in an EAP response message.

[0107] In conjunction with some embodiments of the fourth aspect, in some embodiments, the apparatus may further include a sending module configured to send third information to a terminal, where the third information is used by the terminal to determine a format of the first NAI.

[0108] In combination with some embodiments of the fourth aspect, in some embodiments, the third information may be carried in an EAP request message.

[0109] In conjunction with some embodiments of the fourth aspect, in some embodiments, the apparatus may further include a processing module configured to generate a second NAI based on the first NAI, wherein the second NAI is generated by removing the first information from the first NAI.

[0110] In combination with some embodiments of the fourth aspect, in some embodiments, the network device may be located in a WLAN-AN.

[0111] In conjunction with some embodiments of the fourth aspect, in some embodiments, the sending module may be further configured to: send the second NAI to the NSWOF or AAA server corresponding to the credential holder.

[0112] In a fifth aspect, an embodiment of the present disclosure provides a communication device. The communication device includes at least one processor. The processor is configured to invoke instructions to execute the communication method as described in any one of the first aspect, the second aspect, and the embodiments thereof.

[0113] In a sixth aspect, embodiments of the present disclosure provide a communication system. The communication system includes a terminal and a network device. The terminal is configured to execute the communication method described in any one of the first aspect and its embodiments. The network device is configured to execute the communication method described in any one of the second aspect and its embodiments.

[0114] In a seventh aspect, an embodiment of the present disclosure provides a storage medium storing instructions that, when executed by a processor, perform the communication method as described in any one of the first aspect, the second aspect, and the embodiments thereof.

[0115] In an eighth aspect, a computer program or computer program product is provided. The computer program or computer program product includes code. When the instructions are executed by a processor, the communication method as described in any one of the first aspect, the second aspect, and the embodiments thereof is performed.

[0116] It is understandable that the above-mentioned communication devices, communication equipment, communication systems, storage media, computer programs, and computer program products are all used to perform the methods provided by the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0117] The present disclosure provides a communication method and apparatus, a communication device, a communication system, and a storage medium. In some embodiments, the terms "communication method" and "information processing method" and "information transmission method" are interchangeable; the terms "communication apparatus" and "information processing apparatus" and "information transmission apparatus" are interchangeable; and the terms "communication system" and "information processing system" are interchangeable.

[0118] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain 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 certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0119] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0120] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0121] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0122] In the embodiments of the present disclosure, "plurality" refers to two or more.

[0123] In some embodiments, the terms "at least one", "one or more", "a plurality of", "multiple" and the like can be used interchangeably.

[0124] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "in one case A, in another case B," and "in one case A, in another case B" may include the following technical solutions depending on the circumstances: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above description applies similarly when there are more branches such as A, B, and C.

[0125] In some embodiments, "A or B" and other expressions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is similar when there are more branches such as A, B, and C.

[0126] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted by the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields", and "first" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking the "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different. For another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0127] In some embodiments, “including A”, “containing A”, “used to indicate A”, and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0128] In some embodiments, terms such as "...", "determine that...", "in the case of...", "at the time of...", "when...", "if...", and "if..." can be used interchangeably.

[0129] In some embodiments, terms such as "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 less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "no more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0130] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0131] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0132] In some embodiments, “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”, “bandwidth part”, “bandwidth carrier”, “bandwidth carrier”, “component carrier”, “bandwidth ... part, BWP)" and other terms can be used interchangeably.

[0133] 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 subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0134] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0135] 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, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0136] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0137] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0138] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0139] FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1 , a communication system 100 includes a terminal 101 , a network device 102 , and a certificate holder 103 .

[0140] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0141] In some embodiments, the network device 102 may include an access network device and / or a core network device. In some embodiments, the network device 102 may be, for example, a node or device that connects a terminal to a wireless network. The access network device may include at least one of an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a NodeB (NB), a home nodeB (HNB), a home evolved nodeB (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.

[0142] In some embodiments, the credential holder 103 may be associated with a public land mobile network (PLMN), NPN, or an authentication, authorization and accounting (AAA) server.

[0143] In some embodiments, network device 102 and credential holder 103 may belong to different domains. For example, network device 102 may belong to a first domain, and credential holder 103 may belong to a second domain.

[0144] In one example, the network device 102 may be located in a wireless local area network access network (WLAN-AN). In one example, the network device 102 may be a WLAN-AN (or WLAN-AN device).

[0145] FIG2 is a schematic diagram of a specific NSWO architecture of a communication system provided according to an embodiment of the present disclosure.

[0146] As shown in FIG2(a), network device 102 may be a WLAN-AN and located in a standalone non-public network (SNPN). Credential holder 103 may be associated with a PLMN (e.g., credential holder 103 is implemented using a PLMN). The PLMN includes an NSWO function (NSWOF), an authentication server function (AUSF), and a user data management (UDM) function. The SNPN corresponds to a first domain. The PLMN corresponds to a second domain.

[0147] As shown in FIG2(b), network device 102 may be a WLAN-AN and located in an SNPN. Credential holder 103 may be associated with an NPN (e.g., credential holder 103 is implemented using an NPN). The NPN includes an NSWOF, an AUSF, and an UDM. The SNPN corresponds to the first domain. The NPN corresponds to the second domain. It is understood that the SNPN corresponding to the first domain is different from the NPN corresponding to the second domain.

[0148] As shown in FIG2(c), network device 102 may be a WLAN-AN and located in an SNPN. Credential holder 103 may be associated with an AAA server (e.g., credential holder 103 is implemented using an AAA server). The SNPN corresponds to a first domain. The domain to which the AAA server of the terminal's credential holder belongs is a second domain.

[0149] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces within the network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0150] In some embodiments, the network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0151] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0152] The following embodiments of the present disclosure may be applied to the communication system 100 shown in Figure 1, or a portion thereof, but are not limited thereto. The entities shown in Figure 1 are illustrative only. The communication system 100 may include all or part of the entities shown in Figure 1, or may include other entities outside of Figure 1. The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0153] The embodiments of the present disclosure 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), 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 (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (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 utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0154] In some embodiments, NSWO is a capability provided by the 5GS and the terminal to connect to the WLAN-AN without registering with the 5GS. Specifically, after mutual authentication between the terminal and the 5G core network, the 5G core network sends the key shared between the UE and the 5G core network to the WLAN-AN. In this way, the UE and the WLAN-AN can achieve mutual authentication based on the shared key. In order to obtain the shared key from the credential holder, the WLAN-AN must be able to support mutual authentication between the UE and the credential holder. To do so, the WLAN-AN needs to route authentication-related messages to the credential holder.

[0155] In some embodiments, in an NPN scenario, the NAI sent by the UE to the WLAN-AN only includes domain information of the NPN.

[0156] In some embodiments, the terminal is in a roaming state. In this case, the NPN and the credential holder may be deployed in different domains. In this case, it is difficult for the WLAN-AN to route authentication-related messages to the credential holder based on the NAI that only contains the domain information of the NPN.

[0157] Figure 3 is a schematic diagram illustrating interactions in a communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method, applicable to communication system 100. In communication system 100, network device 102 is associated with a first domain, and credential holder 103 is associated with a second domain. As shown in Figure 3, the method includes steps S310 to S340.

[0158] In step S310 , the network device 102 sends third information to the terminal 101 .

[0159] In some embodiments, the terminal 101 may receive third information from the network device 102 .

[0160] In some embodiments, the third information may be used by the terminal 101 to determine the format (NAI format) of the first NAI sent to the network device 102 .

[0161] In some embodiments, the third information may be used to indicate the format of the first NAI sent by the terminal 101 to the network device 102 .

[0162] In some embodiments, the third information may include the type of the second domain where the credential holder 103 is located, ie, PLMN, NPN, or AAA server.

[0163] In some embodiments, the name of the third information is not limited. For example, the third information can be indication information, etc.

[0164] In some embodiments, after receiving the third information, the terminal 101 may determine the format of the first NAI based on the third information.

[0165] In some embodiments, the network device 102 may send a broadcast message to the terminal 101. The broadcast message may carry the third information. In other words, the third information may be carried in the broadcast message.

[0166] In some embodiments, the network device 102 may send an Extensible Authentication Protocol (EAP) identity / request message to the terminal 101. The EAP request message may carry the third information. In other words, the third information may be carried in the EAP request message.

[0167] In step S320 , the terminal 101 sends a first NAI to the network device 102 .

[0168] In some embodiments, network device 102 may receive a first NAI.

[0169] In some embodiments, the first NAI may be an identity code of the terminal 101 in NAI format.

[0170] In some embodiments, the first NAI may include first information and second information: the first information is used to indicate a first domain corresponding to the network device 102; and the second information is used to indicate a second domain corresponding to the credential holder 103 of the terminal 101.

[0171] In some embodiments, the first information may be included in a first domain portion of the first NAI.

[0172] In some embodiments, the second information may be included in a second domain portion of the first NAI.

[0173] In some embodiments, the first domain may be an NPN.

[0174] In some embodiments, the first NAI may include a username.

[0175] In some embodiments, the first NAI may use the following NAI format: second information! username@first information. Here, the "!" symbol separates the second information from the username. The "@" symbol separates the username from the first information. It is understood that the order of the first information, second information, and username can be adjusted, and other methods of separation can be used, which is not specifically limited in this embodiment.

[0176] In some embodiments, the first NAI may use the following NAI format: CHrealm! username@NPNrealm. Here, CHrealm represents the second information, that is, it indicates the second domain. In other words, CHrealm is the second domain portion. NPNrealm represents the first information, that is, it indicates the first domain. In other words, NPNrealm is the first domain portion. Username represents the user name. The "!" symbol separates CHrealm and username. The "@" symbol separates username and NPNrealm.

[0177] In some embodiments, the first NAI may use the following NAI format: username@NPNrealm!CHrealm. Here, CHrealm represents the second information, i.e., it indicates the second domain. NPNrealm represents the first information, i.e., it indicates the first domain. Username represents the user name. The "@" symbol is used to separate username and NPNrealm. The "!" symbol is used to separate PNPrealm and CHrealm.

[0178] In some embodiments, the first information includes a first network identifier (NID), a first mobile network code (MNC), and a first mobile country code (MCC) of the first domain. The combination of the first NID, the first MNC, and the first MCC can be used to identify the NPN of the first domain.

[0179] In some embodiments, the second domain may be one of the following: a PLMN, an NPN, or a domain to which an AAA server belongs.

[0180] In some embodiments, the second domain may be a PLMN.

[0181] In some embodiments, the second information may include a second MNC and a second MCC of the second domain. The combination of the second MNC and the second MCC may be used to identify the PLMN of the second domain. It is understood that the combination of the second MNC and the second MCC may constitute an identifier of the PLMN, namely, a PLMN ID.

[0182] In some embodiments, the second information may be in the following format: NSWO tag, second MNC, second MCC, domain name.

[0183] In some embodiments, the second information may be in the following format: 5gc-nswo.nid <nid>.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org. 5gc-nswo is the NSWO label used to indicate the use of NSWO services. <chmnc>Used to indicate the second MNC, chMNC is the value of the second MNC. <chmcc>Used to indicate the second MCC, chMCC is the value of the second MCC, and 3gppnetwork.org is the domain name.

[0184] In some embodiments, the second domain may be an NPN.

[0185] In some embodiments, the second information may include a second NID, a second MNC, and a second MCC of the second domain. It can be understood that the combination of the second NID, the second MNC, and the second MCC can be used to identify the NPN of the second domain.

[0186] In some embodiments, the second information may be in the following format: NSWO tag, second NID, second MNC, second MCC, domain name.

[0187] In some embodiments, the second information may be in the following format: 5gc-nswo.nid <nid>.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org. 5gc-nswo is the NSWO label, used to indicate the use of NSWO services. <nid>Used to indicate the second NID, NID is the value of the second NID. mnc <chmnc>Used to indicate the second MNC, chMNC is the value of the second MNC. <chmcc>Used to indicate the second MCC, chMCC is the value of the second MCC, and 3gppnetwork.org is the domain name.

[0188] In some embodiments, the second domain may be the domain to which the AAA server belongs.

[0189] In some embodiments, the second information may include indication information of the domain to which the AAA server belongs.

[0190] In some embodiments, the second information may include a fully qualified domain name (FQDN) of the AAA server.

[0191] In some embodiments, the second information may be in the following format: NSWO tag, indication information of the domain to which the AAA server belongs.

[0192] In some embodiments, the second information may be in the following format: 5gc-nswo.AAArealm, where 5gc-nswo is the NSWO tag and AAArealm is information indicating the domain to which the AAA server belongs.

[0193] In some embodiments, when the terminal 101 determines to use the NSWO service, the terminal 101 may use a subscription concealed identifier (SUCI) in the NAI format or an anonymous SUCI to construct its own identification code.

[0194] In some embodiments, the second domain may be a PLMN, and the first NAI may include at least one of the following: an NSWO label, a second MNC, a second MCC, a domain name, a user name, a first NID, a first MNC, and a first MCC.

[0195] In some embodiments, the second domain may be a PLMN, and the first NAI may be in the following format: 5gc-nswo.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org!<username of SUCI in NAI format>@5gc-nswo.nid <nid>.mnc <servingmnc>.mcc <servingmcc>.3gppnetwork.org. 5gc-nswo is the NSWO label. 3gppnetwork.org is the domain name. Username is used to indicate the user name in SUCI. mnc <chmnc>Used to indicate the second MNC. mcc <chmcc>Used to indicate the second MCC. <nid>Used to indicate the first NID, NID is the value of the first NID. mnc <servingmnc>Used to indicate the first MNC, servingMNC is the value of the first MNC. mcc <servingmcc>Used to indicate the first MCC, where servingMCC is the value of the first MCC.

[0196] In some embodiments, the second domain may be an NPN, and the first NAI may include at least one of the following: an NSWO label, a second NID, a second MNC, a second MCC, a domain name, a user name, a first NID, a first MNC, and a first MCC.

[0197] In some embodiments, the second domain may be an NPN, and the first NAI may be in the following format: 5gc-nswo.nid <nid>.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org!<username of SUCI in NAI format>@5gc-nswo.nid <nid>.mnc <servingmnc>.mcc <servingmcc>.3gppnetwork.org. 5gc-nswo is the NSWO label. 3gppnetwork.org is the domain name. Username is used to indicate the user name in SUCI. The first nid <nid>Used to indicate the second NID. mnc <chmnc>Used to indicate the second MNC. mcc <chmcc>Used to indicate the second MCC. The second NID <nid>Used to indicate the first NID, NID is the value of the first NID. mnc <servingmnc>Used to indicate the first MNC, servingMNC is the value of the first MNC. mcc <servingmcc>Used to indicate the first MCC, where servingMCC is the value of the first MCC.

[0198] In some embodiments, the second domain may be an AAA server, and the first NAI may include at least one of the following: an NSWO tag, information indicating the domain to which the AAA server belongs, a user name, a first NID, a first MNC, and a first MCC.

[0199] In some embodiments, the second domain may be a domain to which the AAA server belongs, and the first NAI may adopt the following format: 5gc-nswo.AAArealm!<username of SUCI in NAI format> @5gc-nswo.nid <nid>.mnc <servingmnc>.mcc <servingmcc>.3gppnetwork.org. 5gc-nswo is the NSWO label. 3gppnetwork.org is the domain name. username is used to indicate the user name in SUCI. AAArealm is the domain to which the AAA server belongs. nid <nid>Used to indicate the first NID, NID is the value of the first NID. mnc <servingmnc>Used to indicate the first MNC, servingMNC is the value of the first MNC. mcc <servingmcc>Used to indicate the first MCC, where servingMCC is the value of the first MCC.

[0200] In some embodiments, the first NID may also be nid <credentialsholdernid>Indicates that the first MNC can also be mnc <credentialsholdermnc>Indicates that the first MCC can also be mcc <credentialsholdermcc>Of course, it is understandable that the first NID, the first MNC, and the first MCC may also be represented in other ways and formats, and this embodiment of the present application does not specifically limit this.

[0201] In some embodiments, the first NAI in the embodiments of the present disclosure may also be referred to as an extended NAI.

[0202] In some embodiments, the terminal 101 may send an EAP response (EAP response / identity) message to the network device 102. The EAP response message carries the first NAI. In other words, the first NAI may be carried in the EAP response message.

[0203] In step S330 , the network device 102 generates a second NAI.

[0204] In some embodiments, after receiving the first NAI, network device 102 may generate a second NAI based on the first NAI.

[0205] In some embodiments, the network device 102 may strip the first information from the first NAI and retain the second information to obtain a second NAI. In other words, the second NAI may include the second domain portion of the first NAI and exclude the first domain portion of the first NAI.

[0206] In some embodiments, the second NAI may adopt the following format: user name@second information.

[0207] In some embodiments, the second NAI may be in the following format: username@CHrealm.

[0208] In some embodiments, the second NAI may be in the following format: second information!username.

[0209] In some embodiments, the second NAI may be in the following format: CHrealm!username.

[0210] In step S340 , the network device 102 sends a second NAI.

[0211] In some embodiments, network device 102 may send a second NAI to credential holder 103 .

[0212] In some embodiments, credential holder 103 may receive a second NAI from network device 102 .

[0213] In some embodiments, when the voucher holder 103 is deployed in a PLMN, ie, the second domain is a PLMN, the network device 102 may send the second NAI to the NSWOF in the PLMN.

[0214] In some embodiments, the network device 102 may send the second NAI to the NSWOF in the PLMN via the AAA proxy.

[0215] In some embodiments, when the credential holder 103 is deployed in an NPN, ie, the second domain is an NPN, the network device 102 may send the second NAI to the NSWOF in the NPN.

[0216] In some embodiments, the network device 102 may send the second NAI to the NSWOF in the NPN via the AAA proxy.

[0217] In some embodiments, when the credential holder 103 is deployed through an AAA server, that is, the second domain is a domain to which the AAA server belongs, the network device 102 may send the second NAI to the AAA server.

[0218] In some embodiments, network device 102 may send the second NAI to the AAA server via the AAA proxy.

[0219] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0220] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", and "send and / or receive" can be used interchangeably, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher levels, obtaining by self-processing, and autonomous implementation, etc.

[0221] In some embodiments, terms such as "send", "transmit", "report", "send", "transmit", "bidirectional transmission", and "send and / or receive" can be used interchangeably.

[0222] In some embodiments, terms such as "certain", "preset", "default", "setting", "indicated", "certain", "arbitrary", and "first" can be used interchangeably. "Specific A", "preset A", "preset A", "setting A", "indicated A", "certain A", "arbitrary A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, certain A, arbitrary A, or first A, etc., but are not limited to this.

[0223] The communication method involved in the embodiments of the present disclosure may include at least one of steps S310 to S340. For example, step S320 can be implemented as an independent embodiment. For example, the combination of steps S310 and S320 can be implemented as an independent embodiment. For example, the combination of steps S320 and S330 can be implemented as an independent embodiment. For example, the combination of steps S320, S330, and S340 can be implemented as an independent embodiment. For example, the combination of steps 310, S320, S330, and S340 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps in steps S310 to S340 are not limited to this.

[0224] In some embodiments, steps S330 and S340 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0225] In some embodiments, step S310 is optional and may be omitted or replaced in different embodiments.

[0226] Figure 4 is a flow chart of a communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method, which is applied to a terminal 101. As shown in Figure 4, the method includes steps S410 and S420.

[0227] In step S410, third information is received.

[0228] The optional implementation of step S410 can refer to the optional implementation of step S310 in Figure 3 and other related parts in the embodiment involved in Figure 3, which will not be repeated here.

[0229] In some embodiments, the terminal 101 may receive third information from the network device 102 .

[0230] In some embodiments, the network device 102 may send third information to the terminal 101 .

[0231] In some embodiments, the third information may be used by the terminal 101 to determine the format of the first NAI sent to the network device 102 .

[0232] In some embodiments, terminal 101 may obtain third information specified by the protocol.

[0233] In some embodiments, terminal 101 may obtain the third information from a higher layer.

[0234] In some embodiments, terminal 101 may perform processing to obtain the third information.

[0235] In step S420, a first NAI is sent.

[0236] The optional implementation of step S420 can refer to the optional implementation of step S320 in Figure 3 and other related parts in the embodiment involved in Figure 3, which will not be repeated here.

[0237] In some embodiments, terminal 101 may send a first NAI to network device 102 .

[0238] In some embodiments, network device 102 may receive a first NAI from terminal 101 .

[0239] In some embodiments, terminal 101 may send the first NAI according to a format of the first NAI determined based on the third information.

[0240] The communication method involved in the embodiments of the present disclosure may include at least one of step S410 and step S420. For example, step S420 may be implemented as an independent embodiment. For example, the combination of steps S410 and S420 may be implemented as an independent embodiment.

[0241] In some embodiments, step S410 is optional and may be omitted or replaced in different embodiments.

[0242] Figure 5 is a flow chart of a communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method, which is applied to a network device 102. As shown in Figure 5, the method includes steps S510 to S540.

[0243] In step S510, the third information is sent.

[0244] The optional implementation of step S510 can refer to the optional implementation of step S310 in Figure 3 and other related parts in the embodiment involved in Figure 3, which will not be repeated here.

[0245] In some embodiments, the network device 102 may send third information to the terminal 101 .

[0246] In some embodiments, the terminal 101 may receive third information from the network device 102 .

[0247] In some embodiments, the third information may be used by the terminal 101 to determine the format of the first NAI sent to the network device 102 .

[0248] In step S520 , a first NAI is received.

[0249] The optional implementation of step S520 can refer to the optional implementation of step S320 in Figure 3 and other related parts in the embodiment involved in Figure 3, which will not be repeated here.

[0250] In some embodiments, network device 102 may receive a first NAI from terminal 101 .

[0251] In some embodiments, terminal 101 may send a first NAI to network device 102 .

[0252] In some embodiments, the first NAI may be sent in a format determined by terminal 101 according to the third information.

[0253] In some embodiments, network device 102 may obtain a first NAI specified by the protocol.

[0254] In some embodiments, network device 102 may obtain the first NAI from a higher layer.

[0255] In some embodiments, network device 102 may perform processing to obtain a first NAI.

[0256] In step S530 , a second NAI is generated.

[0257] The optional implementation of step S530 can refer to the optional implementation of step S330 in Figure 3 and other related parts in the embodiment involved in Figure 3, which will not be repeated here.

[0258] In some embodiments, the network device 102 may remove the first information from the first NAI and construct the second NAI based on the first NAI after removing the first information.

[0259] In step S540 , a second NAI is sent.

[0260] The optional implementation of step S540 can refer to the optional implementation of step S340 in Figure 3 and other related parts in the embodiment involved in Figure 3, which will not be repeated here.

[0261] In some embodiments, network device 102 may send a second NAI to credential holder 103 .

[0262] In some embodiments, credential holder 103 may receive the NAI from network device 102 .

[0263] The communication method involved in the embodiments of the present disclosure may include at least one of steps S510 to S540. For example, step S520 can be implemented as an independent embodiment. For example, the combination of steps S510 and S520 can be implemented as an independent embodiment. For example, the combination of steps S520, S530, and S540 can be implemented as an independent embodiment. For example, the combination of steps S510 and S520 can be implemented as an independent embodiment. For example, the combination of steps S510, S520, S530, and S540 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps in steps S510 to S540 are not limited to this.

[0264] In some embodiments, steps S510, S530, and S540 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0265] In some embodiments, step S510 is optional and may be omitted or replaced in different embodiments.

[0266] Figure 6 is an interactive diagram of a communication method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a communication method, which is applied to a communication system 100. As shown in Figure 6, the method includes step S610.

[0267] In step S610 , the terminal 101 sends a first NAI to the network device 102 .

[0268] In one embodiment, the network device 102 may receive a first NAI from the terminal 101 .

[0269] Optional implementations of step S610 may refer to step S320 in FIG. 3 , step S420 in FIG. 4 , step S520 in FIG. 5 , and other related parts in the embodiments involved in FIG. 3 , FIG. 4 , and FIG. 5 , which will not be described in detail here.

[0270] In some embodiments, the above method may include the method described in the above terminal side and network device side embodiments, which will not be repeated here.

[0271] Figure 7 is a schematic diagram illustrating interactions with a communication method according to an embodiment of the present disclosure. In this embodiment of the present disclosure, the terminal may be a UE, and the network device may be a network device in a WLAN-AN. Furthermore, the credential holder may be implemented based on a PLMN, an NPN, or an AAA server.

[0272] As shown in FIG. 7 , the method includes steps S710 to S750 .

[0273] In step S710, the UE establishes a WLAN connection. The WLAN connection is a connection between the UE and a WLAN-AN. The WLAN-AN is deployed in a serving NPN.

[0274] In step S720 , the WLAN-AN sends an EAP identity / request message (ie, an EAP-ID-request message) to the UE.

[0275] In step S730 , the UE sends an EAP response / identity message (ie, an EAP-ID-response message) to the WLAN-AN.

[0276] In some embodiments, if the UE determines to use the NSWO service, the UE constructs the identity code using SUCI / anonymous SUCI in NAI format (i.e., the username@realm format specified in TS 23.003, 28.7.3), regardless of whether the subscription permanent identifier (SUPI) configured on the universal subscriber identity module (USIM) is an international mobile subscriber identity (IMSI) or an NAI. If the SUPI type configured on the USIM is IMSI, the UE constructs a SUCI in NAI format, where the username includes an encrypted mobile subscriber identification number (MSIN) and the realm part includes the MCC / MNC.

[0277] In some embodiments, when the WLAN-AN and the credential holder are deployed in different domains, the identification code in the EAP ResponseIdentity message is an extended NAI. The extended NAI is implemented based on the domain portion of the credential holder and the domain portion of the serving NPN. The extended NAI has the form CHrealm!username@NPNrealm. The NPNrealm is a domain established by identifying the serving NPN (NID (or servingNID), servingMCC, and servingMNC) selected by the UE.

[0278] In some embodiments, when the certificate holder is based on PLMN implementation, the CHrealm can be in the form of 5gc-nswo.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org. The extended NAI is in the following format: 5gc-nswo.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org!<username of SUCI in NAI format>@5gc-nswo.nid <nid>.mnc <servingmnc>.mcc <servingmcc>.3gppnetwork.org.

[0279] In some embodiments, when the credential holder deployment is based on NPN implementation, the CHrealm may be in the form of 5gc-nswo.nid <chnid>.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org. The extended NAI is in the following form: 5gc-nswo.nid <nid>.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org!<username of SUCI in NAI format>@5gc-nswo.nid <servingnid>.mnc <servingmnc>.mcc <servingmcc>.3gppnetwork.org.

[0280] In some embodiments, when the credential holder is implemented based on an AAA server, CHrealm should be the domain of the AAA server. The domain of the AAA server can be set to the domain name of the AAA server. The extended NAI is in the following form: 5gc-nswo.AAArealm!<username of SUCI in NAI format> @5gc-nswo.nid <nid>.mnc <servingmnc>.mcc <servingmcc>.3gppnetwork.org.

[0281] In step S740 , the WLAN-AN routes the EAP response / identity message to the NSWOF / AAA server through the SWa interface based on the CHrealm portion of the extended NAI.

[0282] In some embodiments, step S740 may be step S740a. In step S740a, the WLAN-AN may send a SWa protocol message to the NSWOF in the PLMN. The SWa protocol message is a message of the SWa interface. Through the SWa protocol message, the WLAN-AN may send an EAP response / identity message (and SUCI) to the NSWOF in the PLMN.

[0283] In some embodiments, step S740 may be step S740b. In step S740b, the WLAN-AN may send a SWa protocol message to the NSWOF in the NPN. The SWa protocol message is a message of the SWa interface. Through the SWa protocol message, the WLAN-AN may send an EAP response / identity message (and SUCI) to the NSWOF in the NPN.

[0284] In some embodiments, step S740 may be step S740c. In step S740c, the WLAN-AN may send a SWa protocol message to the AAA server. The SWa protocol message is a message of the SWa interface. Through the SWa protocol message, the WLAN-AN may send an EAP response / identity message (and SUCI) to the AAA server.

[0285] In step S750 , a mutual authentication process is performed between the UE and the credential holder.

[0286] In some embodiments, step S750 may be step S750a. In step S750a, the UE and the WLAN-AN may continue to perform a mutual authentication process through the NSWOF in the PLMN.

[0287] In some embodiments, step S750 may be step S750b. In step S750b, the UE and the WLAN-AN may continue to perform a mutual authentication process through the NSWOF in the NPN.

[0288] In some embodiments, step S750 may be step S750c. In step S750c, the UE and the WLAN-AN may continue to perform a mutual authentication process through the AAA server.

[0289] The communication method involved in the embodiments of the present disclosure may include at least one of steps S710 to S750. For example, step S730 may be implemented as an independent embodiment. For example, step S730 combined with step S720 may be implemented as an independent embodiment, step S730 combined with steps S710 and S720 may be implemented as an independent embodiment, and step S930 combined with steps S740 and S750 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0290] In some embodiments, steps S710 and S720 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0291] In some embodiments, steps S740 and S750 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0292] In some embodiments, steps S710 , S720 , S740 , and S750 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0293] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0294] The present disclosure also provides a communication device for implementing any of the above methods. For example, the present disclosure provides a device. The device includes units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another device is provided, including units or modules for implementing each step performed by a network device (e.g., an access network device) in any of the above methods.

[0295] It should be understood that the division of the various units or modules in the above devices is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above devices, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0296] In the embodiments of the present disclosure, a processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution 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 relationship of a hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by 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 to implement the hardware circuit configuration 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. In addition, 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), a deep learning processing unit (DPU), etc.

[0297] FIG8 is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure. The communication device 800 is provided in the terminal 101. As shown in FIG8, the communication device 800 may include at least one of a sending module 801 and a receiving module 802.

[0298] In some embodiments, the sending module 801 may be configured to send the first NAI to the network device 102. Optionally, the sending module 801 may be configured to execute at least one of the sending-related steps (e.g., step S320, step S420, step S610, step S730) executed by the terminal 101 in any of the above methods.

[0299] In some embodiments, the receiving module 802 may be configured to receive third information from the network device 102. Optionally, the receiving module 802 may be configured to execute at least one of the reception-related steps (e.g., step S310, step S410, step S720) executed by the terminal 101 in any of the above methods.

[0300] FIG9 is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure. The communication device 900 is provided in the network device 102. As shown in FIG9, the communication device 900 may include at least one of a sending module 901, a receiving module 902, and a processing module 903.

[0301] In some embodiments, the sending module 901 may be configured to send third information to the terminal 101. In some embodiments, the sending module 901 may be configured to send a second NAI. Alternatively, the sending module 901 may be configured to execute at least one of the sending-related steps (e.g., step S310, step S510, step S720, and step S740) executed by the network device 102 in any of the above methods.

[0302] In some embodiments, the receiving module 902 may be configured to receive a first NAI from the terminal 101. Alternatively, the receiving module 902 may be configured to execute at least one of the reception-related steps (e.g., step S320, step S520, step S610, step S730) executed by the network device 102 in any of the above methods.

[0303] In some embodiments, the processing module 903 may be configured to generate the second NAI. Alternatively, the processing module 903 may be configured to execute at least one of the generation-related steps (eg, step S330, step S530, step S740) executed by the network device 102 in any of the above methods.

[0304] Figure 10 is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. Communication device 1000 can be a network device (e.g., an access network device or a core network device), or a terminal (e.g., a user device), or a chip, chip system, or processor that supports a network device to implement any of the above methods, or a chip, chip system, or processor that supports a terminal to implement any of the above communication methods. Communication device 1000 can be used to implement the communication method described in the above method embodiment. For details, please refer to the description of the above method embodiment.

[0305] As shown in Figure 10, the communication device 1000 includes one or more processors 1001. The processor 1001 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The processor 1001 is used to call instructions to enable the communication device 1000 to execute any of the above communication methods.

[0306] In some embodiments, the communication device 1000 further includes one or more memories 1002 for storing instructions. Optionally, all or part of the memory 1002 may be located outside the communication device 1000.

[0307] In some embodiments, the communication device 1000 further includes one or more transceivers 1003. When the communication device 1000 includes one or more transceivers 1003, the communication steps such as sending and receiving in the above method are performed by the transceiver 1003, and the other steps are performed by the processor 1001.

[0308] In some embodiments, the transceiver 1003 may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0309] Optionally, the communication device 1000 further includes one or more interface circuits 1004, which are connected to the memory 1002. The interface circuits 1004 may be configured to receive signals from the memory 1002 or other devices, and may be configured to send signals to the memory 1002 or other devices. For example, the interface circuits 1004 may read instructions stored in the memory 1002 and send the instructions to the processor 1001.

[0310] The communication device 1000 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 1000 described in the present disclosure is not limited thereto, and the structure of the communication device 1000 may not be limited by FIG. 10 . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: (1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) other devices.

[0311] The present disclosure also provides a storage medium having instructions stored thereon. When the instructions are executed on the communication device 1000, the communication device 1000 executes any of the above communication methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but may also be a transient storage medium.

[0312] The present disclosure further provides a program product, which, when executed by the communication device 1000, enables the communication device 1000 to perform any of the above communication methods. Optionally, the program product may be a computer program product.

[0313] The present disclosure also provides a computer program, which, when executed on a computer, enables the computer to execute any one of the above communication methods.

[0314] Other embodiments of the present invention will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow from the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the invention being indicated by the following claims.

[0315] It should be understood that the present invention is not limited to the exact construction described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.< / servingmcc> < / servingmnc> < / nid> < / servingmcc> < / servingmnc> < / servingnid> < / chmcc> < / chmnc> < / nid> < / chmcc> < / chmnc> < / chnid> < / servingmcc> < / servingmnc> < / nid> < / chmcc> < / chmnc> < / chmcc> < / chmnc> < / credentialsholdermcc> < / credentialsholdermnc> < / credentialsholdernid> < / servingmcc> < / servingmnc> < / nid> < / servingmcc> < / servingmnc> < / nid> < / servingmcc> < / servingmnc> < / nid> < / chmcc> < / chmnc> < / nid> < / servingmcc> < / servingmnc> < / nid> < / chmcc> < / chmnc> < / nid> < / servingmcc> < / servingmnc> < / nid> < / chmcc> < / chmnc> < / servingmcc> < / servingmnc> < / nid> < / chmcc> < / chmnc> < / chmcc> < / chmnc> < / nid> < / chmcc> < / chmnc> < / nid> < / chmcc> < / chmnc> < / chmcc> < / chmnc> < / nid> < / servingmcc> < / servingmnc> < / nid> < / servingmcc> < / servingmnc> < / nid> < / servingmcc> < / servingmnc> < / servingnid> < / chmcc> < / chmnc> < / chnid> < / servingmcc> < / servingmnc> < / servingnid> < / chmcc> < / chmnc> < / chnid> < / chmcc> < / chmnc> < / chnid> < / chmcc> < / chmnc> < / chnid> < / servingmcc> < / servingmnc> < / nid> < / chmcc> < / chmnc> < / servingmcc> < / servingmnc> < / nid> < / chmcc> < / chmnc> < / chmcc> < / chmnc> < / chmcc> < / chmnc> < / servingmcc> < / servingmnc> < / nid> < / servingmcc> < / servingmnc> < / nid> < / servingmcc> < / servingmnc> < / servingnid> < / chmcc> < / chmnc> < / chnid> < / servingmcc> < / servingmnc> < / servingnid> < / chmcc> < / chmnc> < / chnid> < / chmcc> < / chmnc> < / chnid> < / chmcc> < / chmnc> < / chnid> < / servingmcc> < / servingmnc> < / nid> < / chmcc> < / chmnc> < / servingmcc> < / servingmnc> < / nid> < / chmcc> < / chmnc> < / chmcc> < / chmnc> < / chmcc> < / chmnc> < / servingmcc> < / servingmnc> < / nid> < / servingmcc> < / servingmnc> < / nid> < / servingmcc> < / servingmnc> < / servingnid> < / chmcc> < / chmnc> < / chnid> < / servingmcc> < / servingmnc> < / servingnid> < / chmcc> < / chmnc> < / chnid> < / chmcc> < / chmnc> < / chnid> < / chmcc> < / chmnc> < / chnid> < / servingmcc> < / servingmnc> < / nid> < / chmcc> < / chmnc> < / servingmcc> < / servingmnc> < / nid> < / chmcc> < / chmnc> < / chmcc> < / chmnc> < / chmcc> < / chmnc> < / servingmcc> < / servingmnc> < / nid> < / servingmcc> < / servingmnc> < / nid> < / servingmcc> < / servingmnc> < / servingnid> < / chmcc> < / chmnc> < / chnid> < / servingmcc> < / servingmnc> < / servingnid> < / chmcc> < / chmnc> < / chnid> < / chmcc> < / chmnc> < / chnid> < / chmcc> < / chmnc> < / chnid> < / servingmcc> < / servingmnc> < / nid> < / chmcc> < / chmnc> < / servingmcc> < / servingmnc> < / nid> < / chmcc> < / chmnc> < / chmcc> < / chmnc> < / chmcc> < / chmnc>

Claims

1. A communication method, performed by a terminal, and comprising: Sending a first network access identifier NAI to the network device; The first NAI includes first information and second information, the first information is used to indicate a first domain corresponding to the network device, the second information is used to indicate a second domain corresponding to the credential holder of the terminal, and the first domain is a non-public network NPN.

2. The method according to claim 1, wherein: The second domain is one of the following types: Public Land Mobile Network PLMN; NPN; The domain to which the authentication, authorization, and accounting AAA servers belong.

3. The method according to claim 1 or 2, wherein: The first NAI satisfies the following format: CHrealm! username@NPNrealm; Among them, CHrealm represents the second information, username represents the user name, and NPNrealm represents the first information. CHrealm, username, and NPNrealm are separated by ! and @.

4. The method according to any one of claims 1 to 3, wherein: The first information includes a first network identifier NID, a first mobile network code MNC, and a first mobile country code MCC of the first domain.

5. The method according to any one of claims 1 to 4, wherein: The second domain is a PLMN; The second information includes a second MNC and a second MCC of the second domain.

6. The method according to any one of claims 1 to 5, wherein: The second domain is a PLMN; The second information satisfies the following format: 5gc-nswo.mnc <chmnc>.mcc <chmcc> .3gppnetwork.org;< / chmcc> < / chmnc> Among them, 5gc-nswo is the NSWO tag for non-seamless wireless LAN migration, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc> The second MCC of the second domain is used to indicate the second MCC of the second domain, where 3gppnetwork.org is the domain name.< / chmcc> < / chmnc> 7. The method according to any one of claims 1 to 6, wherein: The second domain is a PLMN; The first NAI satisfies the following format: 5gc-nswo.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org!<username of SUCI in NAI format>@5gc-nswo.nid <nid>.mnc <servingmnc>.mcc <servingmcc> .3gppnetwork.org;< / servingmcc> < / servingmnc> < / nid> < / chmcc> < / chmnc> Among them, 5gc-nswo is the NSWO label, 3gppnetwork.org is the domain name, username is used to indicate the user name in the user hidden identifier SUCI, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>Used to indicate the second MCC of the second domain, nid <nid>A first NID, mnc, used to indicate the first domain <servingmnc>Used to indicate the first MNC of the first domain, mcc <servingmcc> Used to indicate a first MCC of the first domain.< / servingmcc> < / servingmnc> < / nid> < / chmcc> < / chmnc> 8. The method according to any one of claims 1 to 4, wherein: The second domain is NPN; The second information includes a second NID, a second MNC, and a second MCC of the second domain.

9. The method according to any one of claims 1 to 4 and 8, wherein: The second domain is NPN; The second information satisfies the following format: 5gc-nswo.nid <chnid>.mnc <chmnc>.mcc <chmcc> .3gppnetwork.org;< / chmcc> < / chmnc> < / chnid> Among them, 5gc-nswo is the NSWO label, nid <nid>A second NID, mnc, used to indicate the second domain <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc> The second MCC of the second domain is used to indicate the second MCC of the second domain, where 3gppnetwork.org is the domain name.< / chmcc> < / chmnc> < / nid> 10. The method according to any one of claims 1-4 and 8-9, wherein: The second domain is NPN; The first NAI satisfies the following format: 5gc-nswo.nid <chnid>.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org!<username of SUCI in NAI format>@5gc-nswo.nid <servingnid>.mnc <servingmnc>.mcc <servingmcc> .3gppnetwork.org;< / servingmcc> < / servingmnc> < / servingnid> < / chmcc> < / chmnc> < / chnid> Among them, 5gc-nswo is the NSWO label, 3gppnetwork.org is the domain name, username is used to indicate the user name in SUCI, and nid <chnid>A second NID, mnc, used to indicate the second domain <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>Used to indicate the second MCC of the second domain, nid <servingnid>A first NID, mnc, used to indicate the first domain <servingmnc>Used to indicate the first MNC of the first domain, mcc <servingmcc> Used to indicate a first MCC of the first domain.< / servingmcc> < / servingmnc> < / servingnid> < / chmcc> < / chmnc> < / chnid> 11. The method according to any one of claims 1 to 4, wherein: The second domain is the domain to which the AAA server belongs; The second information includes indication information of the domain to which the AAA server belongs.

12. The method according to any one of claims 1 to 4 and 11, wherein: The second domain is an AAA server; The second information satisfies the following format: 5gc-nswo.AAArealm; Among them, 5gc-nswo is the NSWO label, and AAArealm is the indication information of the domain to which the AAA server belongs.

13. The method according to any one of claims 1-4 and 11-12, wherein: The second domain is an AAA server; The first NAI satisfies the following format: 5gc-nswo.AAArealm!<username of SUCI in NAI format>@5gc-nswo.nid <nid>.mnc <servingmnc>.mcc <servingmcc> .3gppnetwork.org;< / servingmcc> < / servingmnc> < / nid> Among them, 5gc-nswo is the NSWO label, 3gppnetwork.org is the domain name, username is used to indicate the user name in SUCI, AAArealm is the indication information of the domain to which the AAA server belongs, and nid <nid>A first NID, mnc, used to indicate the first domain <servingmnc>Used to indicate the first MNC of the first domain, mcc <servingmcc> Used to indicate a first MCC of the first domain.< / servingmcc> < / servingmnc> < / nid> 14. The method according to any one of claims 11 to 13, wherein: The indication information of the domain to which the AAA server belongs includes the fully qualified domain name FQDN of the AAA server.

15. The method according to any one of claims 1 to 14, wherein: The first NAI is carried in an Extensible Authentication Protocol EAP response message.

16. The method according to any one of claims 1 to 15, wherein: Before sending the first NAI to the network device, the method further includes: receiving third information from the network device, wherein the third information is used by the terminal to determine a format of the first NAI.

17. The method according to claim 16, wherein: The third information is carried in the EAP request message.

18. The method according to any one of claims 1 to 17, wherein: The network device is located in a wireless local area network access network WLAN-AN.

19. A communication method, performed by a network device, and comprising: Receiving a first network access identifier NAI from a terminal; The first NAI includes first information and second information, the first information is used to indicate a first domain corresponding to the network device, the second information is used to indicate a second domain corresponding to the credential holder of the terminal, and the first domain is a non-public network NPN.

20. The method according to claim 19, wherein: The second domain is one of the following types: Public Land Mobile Network PLMN; NPN; The domain to which the authentication, authorization, and accounting AAA servers belong.

21. The method according to claim 19 or 20, wherein: The first NAI satisfies the following format: CHrealm! username@NPNrealm; Among them, CHrealm represents the second information, username represents the user name, and NPNrealm represents the first information. CHrealm, username, and NPNrealm are separated by ! and @.

22. The method according to any one of claims 19 to 21, wherein: The first information includes a first network identifier NID, a first mobile network code MNC, and a first mobile country code MCC of the first domain.

23. The method according to any one of claims 19 to 22, wherein: The second domain is a PLMN; The second information includes a second MNC and a second MCC of the second domain.

24. The method according to any one of claims 19 to 23, wherein: The second domain is a PLMN; The second information satisfies the following format: 5gc-nswo.mnc <chmnc>.mcc <chmcc> .3gppnetwork.org;< / chmcc> < / chmnc> Among them, 5gc-nswo is the NSWO tag for non-seamless wireless LAN migration, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc> The second MCC of the second domain is used to indicate the second MCC of the second domain, where 3gppnetwork.org is the domain name.< / chmcc> < / chmnc> 25. The method according to any one of claims 19 to 24, wherein: The second domain is a PLMN; The first NAI satisfies the following format: 5gc-nswo.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org!<username of SUCI in NAI format>@5gc-nswo.nid <nid>.mnc <servingmnc>.mcc <servingmcc> .3gppnetwork.org;< / servingmcc> < / servingmnc> < / nid> < / chmcc> < / chmnc> Among them, 5gc-nswo is the NSWO label, 3gppnetwork.org is the domain name, username is used to indicate the user name in the user hidden identifier SUCI, mnc <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>Used to indicate the second MCC of the second domain, nid <nid>A first NID, mnc, used to indicate the first domain <servingmnc> To indicate the< / servingmnc> < / nid> < / chmcc> < / chmnc> The first MNC in a region, MCC <servingmcc> Used to indicate a first MCC of the first domain.< / servingmcc> 26. The method according to any one of claims 19 to 22, wherein: The second domain is NPN; The second information includes a second NID, a second MNC, and a second MCC of the second domain.

27. The method according to any one of claims 19 to 22 and 26, wherein: The second domain is NPN; The second information satisfies the following format: 5gc-nswo.nid <chnid>.mnc <chmnc>.mcc <chmcc> .3gppnetwork.org;< / chmcc> < / chmnc> < / chnid> Among them, 5gc-nswo is the NSWO label, nid <chnid>A second NID, mnc, used to indicate the second domain <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc> The second MCC of the second domain is used to indicate the second MCC of the second domain, where 3gppnetwork.org is the domain name.< / chmcc> < / chmnc> < / chnid> 28. The method according to any one of claims 19-22 and 26-27, wherein The second domain is NPN; The first NAI satisfies the following format: 5gc-nswo.nid <chnid>.mnc <chmnc>.mcc <chmcc>.3gppnetwork.org!<username of SUCI in NAI format>@5gc-nswo.nid <servingnid>.mnc <servingmnc>.mcc <servingmcc> .3gppnetwork.org;< / servingmcc> < / servingmnc> < / servingnid> < / chmcc> < / chmnc> < / chnid> Among them, 5gc-nswo is the NSWO label, 3gppnetwork.org is the domain name, username is used to indicate the user name in SUCI, and nid <chnid>A second NID, mnc, used to indicate the second domain <chmnc>Used to indicate the second MNC of the second domain, mcc <chmcc>Used to indicate the second MCC of the second domain, nid <servingnid>A first NID, mnc, used to indicate the first domain <servingmnc>Used to indicate the first MNC of the first domain, mcc <servingmcc> Used to indicate a first MCC of the first domain.< / servingmcc> < / servingmnc> < / servingnid> < / chmcc> < / chmnc> < / chnid> 29. The method according to any one of claims 19 to 22, wherein: The second domain is the domain to which the AAA server belongs; The second information includes indication information of the domain to which the AAA server belongs.

30. The method according to any one of claims 19 to 22 and 29, wherein: The second domain is an AAA server; The second information satisfies the following format: 5gc-nswo.AAArealm; 5gc-nswo is the NSWO label, and AAArealm is the indication information of the domain to which the AAA server belongs.

31. The method according to any one of claims 19-22 and 29-30, wherein: The second domain is an AAA server; The first NAI satisfies the following format: 5gc-nswo.AAArealm!<username of SUCI in NAI format>@5gc-nswo.nid <nid>.mnc <servingmnc>.mcc <servingmcc> .3gppnetwork.org;< / servingmcc> < / servingmnc> < / nid> Among them, 5gc-nswo is the NSWO label, 3gppnetwork.org is the domain name, username is used to indicate the user name in SUCI, AAArealm is the indication information of the domain to which the AAA server belongs, and nid <nid>A first NID, mnc, used to indicate the first domain <servingmnc>Used to indicate the first MNC of the first domain, mcc <servingmcc> Used to indicate a first MCC of the first domain.< / servingmcc> < / servingmnc> < / nid> 32. The method according to any one of claims 29 to 31, wherein: The indication information of the domain to which the AAA server belongs includes the fully qualified domain name FQDN of the AAA server.

33. A method according to any one of claims 19 to 32, wherein: The first NAI is carried in an Extensible Authentication Protocol (EAP) response message.

34. A method according to any one of claims 19 to 33, wherein: Before receiving the first NAI from the terminal, the method further includes: Sending third information to the terminal, wherein the third information is used by the terminal to determine a format of the first NAI.

35. The method of claim 34, wherein: The third information is carried in the EAP request message.

36. A method according to any one of claims 19 to 35, wherein: After receiving the first NAI from the terminal, the method further includes: Based on the first NAI, a second NAI is generated, wherein the second NAI is generated based on the first NAI after the first information is removed.

37. A method according to any one of claims 19 to 36, wherein: The network device is located in a wireless local area network access network WLAN-AN.

38. The method according to claim 36 or 37, wherein: After generating a second NAI based on the first NAI, the method further includes: The second NAI is sent to a non-seamless wireless LAN migration function NSWOF or an AAA server corresponding to the credential holder.

39. A communication device, arranged in a terminal, comprising: A sending module, configured to send a first network access identifier NAI to the network device; The first NAI includes first information and second information, the first information is used to indicate a first domain corresponding to the network device, the second information is used to indicate a second domain corresponding to the credential holder of the terminal, and the first domain is a non-public network NPN.

40. A communication device, arranged in a network device, comprising: A receiving module configured to receive a first network access identifier NAI from a terminal; The first NAI includes first information and second information, the first information is used to indicate a first domain corresponding to the network device, the second information is used to indicate a second domain corresponding to the credential holder of the terminal, and the first domain is a non-public network NPN.

41. A communication device comprising: at least one processor; The processor is used to call instructions to execute the communication method as described in any one of claims 1 to 38.

42. A communication system, comprising a terminal and a network device, wherein: The terminal is configured to implement the communication method according to any one of claims 1 to 18, and the network device is configured to implement the communication method according to any one of claims 19 to 38.

43. A storage medium, wherein: The storage medium stores instructions, wherein the instructions, when executed by a processor, perform the communication method according to any one of claims 1 to 38.

Images