Communication method and related apparatus

Abstract

The present application relates to the technical field of communications, and provides a communication method and a related apparatus. The method comprises: a user equipment sends a first message to a target non-3GPP (non-3rd generation partnership project) access gateway, the first message being used to request establishment or updating of a connection of the user equipment, and the first message comprising a non-3GPP device identifier of a non-3GPP device; and the user equipment receives a second message from the target non-3GPP access gateway, the second message comprising quality of service (QoS) information corresponding to the non-3GPP device identifier. In the embodiments of the present application, a user equipment can directly report a non-3GPP device identifier to a core network via a non-3GPP access gateway. Thus, the user equipment can report the non-3GPP device identifier to the core network in the absence of a SIM card, and acquire QoS information corresponding to the non-3GPP device identifier from the core network, thereby enabling differentiated QoS services to be provided to non-3GPP devices connected to the user equipment.

Description

Communication methods and related devices

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

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

[0003] User equipment (UE) can access the core network through non-3GPP access technologies. Furthermore, UE can connect to one or more non-3GPP devices and report the non-3GPP device identifier to the core network through non-access stratum (NAS) signaling. That is, the non-3GPP device identifier of non-3GPP devices is reported through the access and mobility management function (AMF) network element. This allows the core network to identify non-3GPP devices and provide corresponding quality of service (QoS) information to provide differentiated services for non-3GPP devices.

[0004] In the future, in order to meet the reporting requirements of non-3GPP device identifiers in more scenarios (such as scenarios where user equipment does not support NAS signaling), it is necessary to study more solutions for reporting non-3GPP device identifiers of non-3GPP devices to the core network. Summary of the Invention

[0005] This application discloses a communication method and related apparatus that can enable user equipment to report non-3GPP device identifiers of non-3GPP devices connected to the user equipment to the core network without a SIM card.

[0006] The first aspect discloses a communication method that can be applied to a user equipment (UE), a module within the UE (e.g., a processor or chip), or a logic module or software capable of implementing all or part of the UE's functions. The UE connects to a non-3GPP device. Described below using an application to a UE as an example, the communication method may include: sending a first message to a target non-3GPP access gateway, the first message requesting the establishment or renewal of a connection for the UE, the first message including a non-3GPP device identifier; and receiving a second message from the target non-3GPP access gateway, the second message including quality of service (QoS) information corresponding to the non-3GPP device identifier.

[0007] In this application, a user equipment (UE) can send a first message (carrying a non-3GPP device identifier) ​​to a target non-3GPP access gateway. This allows the UE to report the non-3GPP device identifier to the core network (such as a session management network element) during the UE connection establishment / update process. Furthermore, the UE can receive a second message from the target non-3GPP access gateway (carrying QoS information corresponding to the non-3GPP identifier generated by the core network). Based on this QoS information, differentiated services can be provided to the non-3GPP device. Therefore, this provides a new scheme for reporting non-3GPP device identifiers. For scenarios where the UE does not support NAS signaling, this scheme enables the UE to report the non-3GPP device identifier to the core network (such as a session management network element) and obtain the QoS information corresponding to the non-3GPP identifier generated by the core network, thereby providing services corresponding to the QoS information to the non-3GPP device connected to the UE.

[0008] The user equipment can be an evolved residential gateway (eRG). An eRG can be a gateway device (such as an optical modem) deployed in a user's home, supporting wired access, wireless access (such as WiFi), and other technologies. It should be noted that this application does not limit the form factor of the user equipment; it can be various types of terminals (such as smartphones, laptops, etc.), access points (APs), etc.

[0009] Non-3GPP equipment can be any device that supports data transmission via non-3GPP protocols (such as WiFi, Bluetooth, Ethernet, etc.), including but not limited to IoT sensors, smart home terminals, smartphones, etc. Non-3GPP equipment can also be referred to as end devices.

[0010] For example, the first message could be an Internet Key Exchange (IKE) authentication request message or an IKE informational request message.

[0011] The second message can be an IKE authentication response (IKE_auth response) message or an IKE informational request message.

[0012] In conjunction with the first aspect, in one possible implementation, the method further includes: sending first capability information to the target non-3GPP access gateway, the first capability information being used to indicate that the user equipment supports connection with non-3GPP devices.

[0013] Optionally, the first capability information can be used to indicate that the user equipment has the ability to identify and / or process non-3GPP device identifiers.

[0014] In this application, a user equipment can send first capability information to a target non-3GPP access gateway to indicate that the user equipment has a need to report a non-3GPP device identifier, thereby facilitating the target non-3GPP access gateway to perform corresponding processing (such as selecting a session management network element that supports the capability of non-3GPP device identifiers). This ensures that the core network can successfully identify the non-3GPP device identifier reported by the user equipment and generate QoS information corresponding to the non-3GPP device identifier, i.e., the QoS information of the non-3GPP device.

[0015] In conjunction with the first aspect, in one possible implementation, the method further includes: selecting the target non-3GPP access gateway from among non-3GPP access gateways capable of processing non-3GPP device identifiers.

[0016] Optionally, the non-3GPP access gateway capable of processing non-3GPP device identifiers may be a non-3GPP access gateway that supports processing non-3GPP devices, or a non-3GPP access gateway capable of identifying non-3GPP device identifiers, or a non-3GPP access gateway capable of reporting non-3GPP device identifiers.

[0017] In this application, the user equipment can select a target non-3GPP access gateway from among non-3GPP access gateways capable of processing non-3GPP device identifiers. This ensures that the selected target non-3GPP access gateway can report the non-3GPP device identifier to the core network and receive QoS information corresponding to the non-3GPP device identifier from the core network. In other words, it ensures that the selected target non-3GPP access gateway supports the relevant procedures of the non-3GPP device identifier reporting scheme provided in this application.

[0018] In conjunction with the first aspect, in one possible implementation, selecting the target non-3GPP access gateway from non-3GPP access gateways capable of processing non-3GPP device identifiers includes: selecting the target non-3GPP access gateway from non-3GPP access gateways capable of processing non-3GPP device identifiers and co-located with user plane network elements.

[0019] In this application, the user equipment may also choose to co-locate a non-3GPP access gateway with the user plane network element. This facilitates subsequent interaction between the non-3GPP access gateway and the session management network element through the interface between the user plane network element and the session management network element.

[0020] The second aspect discloses a communication method that can be applied to a non-3GPP access gateway, a module (e.g., a processor or chip) within a non-3GPP access gateway, or a logic module or software capable of implementing all or part of the functions of a non-3GPP access gateway. The following description uses an application to a non-3GPP access gateway as an example. The communication method may include: receiving a first message from a user equipment (UE), the first message being used to request the establishment or renewal of a connection for the UE; the first message including a non-3GPP device identifier of the non-3GPP device to which the UE is connected; sending a third message to a target session management network element, the third message being used to request the establishment or renewal of a connection for the UE, the third message including the non-3GPP device identifier of the non-3GPP device; receiving a fourth message from the target session management network element, the fourth message including Quality of Service (QoS) information corresponding to the non-3GPP device identifier; and sending a second message to the UE, the second message including the QoS information corresponding to the non-3GPP device identifier.

[0021] In this application, the target non-3GPP access gateway can receive a first message (carrying a non-3GPP device identifier) ​​from the user equipment, and can send a third message (carrying a non-3GPP device identifier) ​​to the target session management network element based on the first message, so that the non-3GPP device identifier can be reported to the target session management network element during the user equipment connection establishment / update process. Furthermore, the target non-3GPP access gateway can receive a fourth message (carrying QoS information corresponding to the non-3GPP device identifier) ​​from the target session management network element, and can send a second message (carrying QoS information corresponding to the non-3GPP device identifier) ​​to the user equipment, thereby enabling the network to provide differentiated services to non-3GPP devices based on the QoS information. As can be seen, the above provides a new scheme for reporting non-3GPP device identifiers. For scenarios where user equipment does not support NAS signaling, this scheme enables non-3GPP access gateways to assist user equipment in reporting non-3GPP device identifiers to the core network (such as session management network elements) and obtain the QoS information corresponding to the non-3GPP identifiers generated by the core network. This allows the user equipment to provide the services corresponding to the QoS information for the non-3GPP devices connected to it.

[0022] For example, the first message could be an IKE authentication request message or an IKE notification request message.

[0023] The second message can be an IKE authentication response message or an IKE notification response message.

[0024] The third message can be a session report request message, an N4 session establishment response message, or a session creation request message.

[0025] The fourth message can be a session creation response message or an update bearer request message.

[0026] In conjunction with the second aspect, in one possible implementation, the method further includes: selecting the target session management network element from session management network elements capable of processing non-3GPP device identifiers.

[0027] Optionally, the session management network element capable of processing non-3GPP device identifiers may be a session management network element that supports processing non-3GPP devices, or a session management network element capable of identifying non-3GPP device identifiers, or a session management network element capable of reporting non-3GPP device identifiers.

[0028] In this application, the target non-3GPP access gateway can select a session management network element capable of processing non-3GPP device identifiers, thereby ensuring that the selected session management network element can successfully identify the non-3GPP device identifier reported by the user equipment and generate QoS information corresponding to the non-3GPP device identifier.

[0029] In conjunction with the second aspect, in one possible implementation, the method further includes: receiving first capability information from the user equipment, the first capability information indicating that the user equipment supports connection with non-3GPP devices; the selection of the target session management network element from session management network elements capable of processing non-3GPP device identifiers includes: selecting the target session management network element from session management network elements capable of processing non-3GPP device identifiers based on the first capability information.

[0030] In this application, the target non-3GPP access gateway can receive first capability information from the user equipment and determine based on the first information that the user equipment has a need to report non-3GPP device identifiers. Therefore, the target non-3GPP access gateway can select a session management network element that has the ability to process non-3GPP device identifiers.

[0031] In conjunction with the second aspect, in one possible implementation, the method further includes: obtaining first quantity information, the first quantity information being used to indicate the maximum number of non-3GPP device identifiers that the user equipment is allowed to activate simultaneously; the sending of the third message to the target session management network element includes: if it is determined based on the first message that the number of non-3GPP device identifiers that the user equipment is activating simultaneously does not exceed the maximum number, sending the third message to the target session management network element.

[0032] For example, the maximum number of non-3GPP device identifiers that a user equipment is allowed to activate simultaneously can be the maximum number of non-3GPP devices that a user equipment is allowed to activate simultaneously.

[0033] Specifically, activated non-3GPP equipment can be non-3GPP equipment that provides corresponding QoS information (differentiated QoS) to the core network (such as session management elements), or non-3GPP equipment that provides corresponding QoS information to user equipment. Correspondingly, the activated non-3GPP equipment identifier can be a non-3GPP equipment identifier that provides corresponding QoS information (differentiated QoS) to the core network, or a non-3GPP equipment identifier that provides corresponding QoS information to user equipment. This differentiated QoS can be a non-default QoS, and correspondingly, the QoS information can be the QoS information corresponding to the non-default QoS.

[0034] In this application, the target non-3GPP access gateway can obtain first quantity information. Before sending the third message to the target session management network element, the target non-3GPP access gateway can determine, based on the first message, whether the number of non-3GPP device identifiers simultaneously activated by the user equipment exceeds the maximum number indicated by the first quantity information. If it does not exceed the maximum number, the target non-3GPP access gateway can send the third message to the target session management network element. Therefore, in the above process, the target non-3GPP access gateway can control the number of non-3GPP device identifiers simultaneously activated by the user equipment, preventing the number of such identifiers from exceeding the maximum. This controls the number of simultaneously activated non-3GPP device identifiers within a certain range, avoiding excessive resource consumption (such as address allocation resources, core network internal and external transmission resources, and data storage resources), and enhancing network robustness.

[0035] In conjunction with the second aspect, in one possible implementation, the method further includes: obtaining first quantity information, the first quantity information indicating the maximum number of non-3GPP device identifiers that the user equipment is allowed to activate simultaneously; the sending of the second message to the user equipment includes: if it is determined based on the first message that the number of non-3GPP device identifiers that the user equipment can activate simultaneously does not exceed the maximum number, sending the second message to the user equipment.

[0036] In this application, the target non-3GPP access gateway can obtain first quantity information. Before sending the second message to the user equipment, the target non-3GPP access gateway can determine, based on the first message, whether the number of non-3GPP device identifiers simultaneously activated by the user equipment exceeds the maximum number indicated by the first quantity information. If it does not exceed the maximum number, the target non-3GPP access gateway can then send the second message to the user equipment. Therefore, in the above process, the target non-3GPP access gateway controls the number of non-3GPP device identifiers simultaneously activated by the user equipment, thus preventing the number of non-3GPP device identifiers simultaneously activated by the user equipment from exceeding the maximum number.

[0037] In conjunction with the second aspect, in one possible implementation, the first quantity information is carried on an N4 interface, an SWm interface, or an S2b-C interface.

[0038] In this application, the first quantity information can be carried through the N4 interface, SWm interface or S2b-C interface, which provides high flexibility.

[0039] In conjunction with the second aspect, in one possible implementation, the target user plane network element is co-located with the target non-3GPP access gateway, and the acquisition of the first quantity information includes: receiving a fifth message from the target session management network element, the fifth message being used to request the creation of a connection between the target session management network element and the target user plane network element, the fifth message including the first quantity information.

[0040] For example, the fifth message could be an N4 session establishment request message or an N4 session modification request message.

[0041] In this application, the target user plane network element can be co-located with the target non-3GPP access gateway, and the target non-3GPP access gateway can obtain the first quantity information through the fifth message exchanged between the target user plane network element and the target session management network element.

[0042] In conjunction with the second aspect, in one possible implementation, obtaining the first quantity information includes: sending a sixth message to the authentication network element, the sixth message being used to request authentication; and receiving a seventh message from the authentication network element, the seventh message including an authentication success indication and the first quantity information.

[0043] For example, the sixth message could be an authentication request message. The seventh message could be an authentication and authorization answer (AA-answer) message.

[0044] In this application, the target non-3GPP access gateway can receive a seventh message (carrying first quantity information) from the authentication network element during the user equipment authentication process, and can obtain the first quantity information through the authentication network element. This approach allows the non-3GPP access gateway to obtain the first quantity information more quickly. In some cases (such as when the user equipment reports non-3GPP device identifiers to the core network during connection establishment), it can determine earlier, based on the first message, whether the number of non-3GPP device identifiers simultaneously activated by the user equipment exceeds the maximum number indicated by the first quantity information. This avoids reporting the corresponding non-3GPP device identifiers to the session management network element even when the maximum number is exceeded, saving transmission resources and avoiding unnecessary subsequent processing of non-3GPP device identifiers, such as the session management network element generating QoS information corresponding to the non-3GPP device identifier.

[0045] In conjunction with the second aspect, in one possible implementation, the third message is carried on the N4 interface or the S2b-C interface.

[0046] In this application, third messages can be carried through the N4 interface or the S2b-C interface, which provides high flexibility.

[0047] The third aspect discloses a communication method that can be applied to a session management network element, a module (e.g., a processor or chip) within the session management network element, or a logic module or software capable of implementing all or part of the session management network element's functions. The following description uses an application to a session management network element as an example. This communication method may include: receiving a third message from a target non-3GPP access gateway, the third message being used to request the establishment or renewal of a connection for a user equipment; the third message including a non-3GPP device identifier of the non-3GPP device to which the user equipment is connected; and sending a fourth message to the target non-3GPP access gateway, the fourth message including Quality of Service (QoS) information corresponding to the non-3GPP device identifier.

[0048] In this application, the session management network element can receive a third message (carrying a non-3GPP device identifier) ​​from a non-3GPP access gateway. Based on this third message, it can obtain the QoS information corresponding to the non-3GPP device identifier. Subsequently, it can send a fourth message (carrying the QoS information corresponding to the non-3GPP device identifier) ​​to the non-3GPP access gateway to provide differentiated QoS services for the corresponding non-3GPP devices. Therefore, this provides a new scheme for reporting non-3GPP device identifiers. For scenarios where user equipment does not support NAS signaling, this scheme enables the non-3GPP access gateway to assist the user equipment in reporting the non-3GPP device identifier to the core network (such as the session management network element) and obtaining the QoS information corresponding to the non-3GPP identifier generated by the core network. This allows the user equipment to provide services corresponding to the QoS information for the non-3GPP devices connected to it.

[0049] In conjunction with the third aspect, in one possible implementation, the method further includes: selecting a target user plane network element co-located with the target non-3GPP access gateway; and sending a fifth message to the target user plane network element, the fifth message being used to request the creation of a connection between the session management network element and the target user plane network element.

[0050] For example, the fifth message could be an N4 session establishment request message or an N4 session update request message.

[0051] In this application, the session management network element can be selected as a user plane network element co-located with a non-3GPP access gateway. This facilitates subsequent interaction between the session management network element and the non-3GPP access gateway through the interface between the user plane network element and the session management network element.

[0052] In conjunction with the third aspect, in one possible implementation, the method further includes: obtaining first quantity information, the first quantity information indicating the maximum number of non-3GPP device identifiers that the user equipment is allowed to activate simultaneously; and sending the first quantity information to the target non-3GPP access gateway.

[0053] In this application, the session management network element can obtain first quantity information and send the first quantity information to the target non-3GPP access gateway so that the target non-3GPP access gateway can control the number of non-3GPP device identifiers that are simultaneously activated by the user equipment.

[0054] In conjunction with the third aspect, in one possible implementation, obtaining the first quantity information includes: sending an eighth message to the policy control network element, the eighth message being used to request the establishment of a session management policy association; and receiving a ninth message from the policy control network element, the ninth message including the first quantity information and policy information.

[0055] For example, the eighth message could be a Session Management Policy Control Create Request (SMpolicy control create request), and the ninth message could be an SM policy control create response.

[0056] In this application, the session management network element can obtain the first quantity information from the policy control network element when requesting policy information of the user equipment from the policy control network element, which can reduce signaling interaction.

[0057] In conjunction with the third aspect, in one possible implementation, sending the first quantity information to the target non-3GPP access gateway includes sending the first quantity information to the target non-3GPP access gateway via an N4 interface or an S2b-C interface.

[0058] In conjunction with the third aspect, in one possible implementation, the target user plane network element is co-located with the target non-3GPP access gateway, and sending the first quantity information to the target non-3GPP access gateway includes: sending a fifth message to the target user plane network element, the fifth message being used to request the creation of a connection between the session management network element and the target user plane network element, the fifth message including the first quantity information.

[0059] In conjunction with the third aspect, in one possible implementation, the third message is carried on the N4 interface or the S2b-C interface.

[0060] The fourth aspect discloses a communication method that can be applied to an authentication network element, a module within the authentication network element (e.g., a processor or chip), or a logic module or software capable of implementing all or part of the authentication network element's functions. The following description uses an application to an authentication network element as an example. This communication method may include: receiving a sixth message from a non-3GPP access gateway, the sixth message being used to request authentication; and sending a seventh message to the non-3GPP access gateway, the seventh message including an authentication success indication and first quantity information, the first quantity information being used to indicate the maximum number of non-3GPP device identifiers that the user equipment is allowed to activate simultaneously.

[0061] In this application, after the user equipment is successfully authenticated, the authentication network element can send the first quantity information corresponding to the user equipment to the non-3GPP access gateway, so that the non-3GPP access gateway can control the number of non-3GPP device identifiers that are simultaneously activated by the user equipment based on the first quantity information.

[0062] It should be noted that the technical solutions of the first to fourth aspects of this application correspond to each other, and the relevant beneficial effects can be referred to each other.

[0063] The fifth aspect discloses a communication device that has the functions of the first aspect described above. For example, the communication device includes a module or unit that performs the methods of the first aspect or any possible implementation of the first aspect. The module or unit can be implemented by software, hardware, or a combination of software and hardware.

[0064] For example, the communication device disclosed in the fifth aspect above may be a user equipment or a chip in a user equipment.

[0065] The sixth aspect discloses a communication device that has the functions of the second aspect described above. For example, the communication device includes a module or unit that performs the methods of the second aspect or any possible implementation of the second aspect. The module or unit can be implemented by software, hardware, or a combination of software and hardware.

[0066] For example, the communication device disclosed in the fifth aspect above may be a non-3GPP access gateway or a chip in a non-3GPP access gateway, etc.

[0067] The seventh aspect discloses a communication device that has the functions of the third aspect described above. For example, the communication device includes a module or unit that performs the methods of the third aspect or any possible implementation of the third aspect. The module or unit can be implemented by software, hardware, or a combination of software and hardware.

[0068] For example, the communication device disclosed in the fifth aspect above may be a session management network element or a chip in a session management network element.

[0069] The eighth aspect discloses a communication device that has the functions of the fourth aspect described above. For example, the communication device includes a module or unit that performs the methods of the fourth aspect or any possible implementation of the fourth aspect. The module or unit can be implemented by software, hardware, or a combination of software and hardware.

[0070] For example, the communication device disclosed in the fifth aspect above may be an authentication network element or a chip in the authentication network element.

[0071] A ninth aspect discloses a communication system comprising at least one of a user equipment, a non-3GPP access gateway, a session management network element, and an authentication network element. The user equipment is configured to implement the methods provided in the first aspect and any possible embodiments thereof. The non-3GPP access gateway is configured to implement the methods provided in the second aspect and any possible embodiments thereof. The session management network element is configured to implement the methods provided in the third aspect and any possible embodiments thereof. The authentication network element is configured to implement the methods provided in the fourth aspect and any possible embodiments thereof.

[0072] The tenth aspect discloses a communication device, including a processor and a communication interface; the communication interface is used to receive and / or transmit data; the processor invokes a computer program or computer instructions stored in a memory to implement the method provided in the first aspect and any possible implementation of the first aspect, or to implement the method provided in the second aspect and any possible implementation of the second aspect, or to implement the method provided in the third aspect and any possible implementation of the third aspect, or to implement the method provided in the fourth aspect and any possible implementation of the fourth aspect.

[0073] As one possible implementation, the communication device disclosed in the tenth aspect above may include one or more processors.

[0074] Optionally, the communication device disclosed in the tenth aspect above further includes one or more memories.

[0075] The eleventh aspect discloses a computer-readable storage medium storing a computer program or computer instructions that, when executed, implement the methods provided in the first aspect and any possible embodiments thereof, or implement the methods provided in the second aspect and any possible embodiments thereof, or implement the methods provided in the third aspect and any possible embodiments thereof, or implement the methods provided in the fourth aspect and any possible embodiments thereof.

[0076] The twelfth aspect discloses a chip including a processor for executing a program stored in a memory, wherein when the program is executed, the chip performs the methods provided in the first aspect and any possible embodiments thereof, or performs the methods provided in the second aspect and any possible embodiments thereof, or performs the methods provided in the third aspect and any possible embodiments thereof, or performs the methods provided in the fourth aspect and any possible embodiments thereof.

[0077] As one possible implementation, the memory is located outside the chip.

[0078] The thirteenth aspect discloses a computer program product comprising computer program code that, when executed, causes the methods provided in the first aspect and any possible embodiments thereof to be performed, or causes the methods provided in the second aspect and any possible embodiments thereof to be performed, or causes the methods provided in the third aspect and any possible embodiments thereof to be performed, or causes the methods provided in the fourth aspect and any possible embodiments thereof to be performed.

[0079] It should be understood that the implementation and beneficial effects of the above-mentioned aspects or any possible implementation methods of this application can be referred to each other. Attached Figure Description

[0080] Figure 1 is a schematic diagram of a network architecture disclosed in an embodiment of this application;

[0081] Figure 2 is a schematic diagram of another network architecture disclosed in an embodiment of this application;

[0082] Figure 3 is a schematic diagram of another network architecture disclosed in an embodiment of this application;

[0083] Figure 4 is a flowchart illustrating a communication method disclosed in an embodiment of this application;

[0084] Figure 5 is a flowchart illustrating another communication method disclosed in an embodiment of this application;

[0085] Figure 6 is a flowchart illustrating another communication method disclosed in an embodiment of this application;

[0086] Figure 7 is a flowchart illustrating another communication method disclosed in an embodiment of this application;

[0087] Figure 8 is a flowchart illustrating another communication method disclosed in an embodiment of this application;

[0088] Figure 9 is a schematic diagram of the structure of a communication device disclosed in an embodiment of this application;

[0089] Figure 10 is a schematic diagram of the hardware structure of a communication device disclosed in an embodiment of this application. Detailed Implementation

[0090] This application discloses a communication method and related apparatus that enables user equipment to report non-3GPP device identifiers of non-3GPP devices connected to the user equipment to the core network without a SIM card. The technical solutions in this application will be clearly and completely described below with reference to the accompanying drawings.

[0091] To better understand the embodiments of this application, the relevant content, terms or nouns involved in this application will be briefly introduced below.

[0092] Currently, the 5G network architecture supports radio access technologies defined by the 3rd generation partnership project (3GPP) to access the core network (CN), such as the Long Term Evolution (LTE) radio access network (RAN) and 5G RAN. The 5G network architecture also supports non-3GPP access technologies to access the core network through the Non-3GPP interworking function (N3IWF) or the trusted Non-3GPP gateway function (TNGF).

[0093] For example, please refer to Figure 1, which is a schematic diagram of a network architecture disclosed in an embodiment of this application. In the network architecture shown in Figure 1, the 5G core network supports untrusted Non-3GPP (N3G) access. Here, N3IWF can be an untrusted Non-3GPP access gateway, and the untrusted Non-3GPP access network (Non-3GPP network) can include an untrusted wireless local area network (WLAN) access network.

[0094] Furthermore, the 5G core network can also support trusted Non-3GPP access and / or wired network access. Trusted Non-3GPP access networks can include trusted WLAN networks, and wired networks include fixed home networks. When the 5G core network supports trusted Non-3GPP access, the network-side architecture is similar to the untrusted Non-3GPP access architecture (Figure 1), where the untrusted Non-3GPP access gateway (N3IWF) can be replaced with a trusted non-3GPP gateway function (TNGF). When the 5G core network supports wired network access, the network-side architecture is also similar to the untrusted Non-3GPP access architecture (Figure 1), where the untrusted Non-3GPP access gateway (N3IWF) can be replaced with a wired network access gateway function (W-AGF). Access network devices between user equipment (UE) and the access gateway can include WLAN access points (APs), fixed access network (FAN) devices, switches, routers, etc. The 3GPP standard also defines the fixed network residential gateway (FN-RG) and the 5G residential gateway (5G-RG).

[0095] Based on the above, it can be seen that N3G access technologies include trusted WLAN access, untrusted WLAN access, and wired access. For these access technologies, the core network can adopt the point-to-point interface protocol shown in Figure 1, or a service-oriented interface.

[0096] The 3GPP standard also defines a network architecture that integrates the evolved packet core (EPC) and the 5G core network (5GC), as shown in Figure 2. For detailed specifications of the interface between user equipment and the evolved packet data gateway (ePDG), as well as the interfaces between various nodes in the core network (such as SWm, SWx, S2b, etc.), please refer to the descriptions in relevant standards (such as 3GPP TS23.402).

[0097] Currently, user equipment (such as 5G-RG) can access the 5G core network through the 3GPP network or through the N3IWF / TNGF defined in 5GC. Furthermore, user equipment can connect to one or more non-3GPP devices. User equipment can report relevant information about non-3GPP devices to the 5G core network via non-access stratum (NAS) signaling, specifically through access and mobility management function (AMF) network elements. This information includes the non-3GPP device identifier, indicating the addition of non-3GPP devices to the 5G core network, enabling the 5G core network to identify these devices and provide differentiated services. The prerequisite for user equipment to access the 5G core network and communicate via NAS signaling is that the user equipment has a universal subscriber identity module (USIM).

[0098] For example, among the non-3GPP devices connected to a user equipment (UE), for those requiring differentiated QoS from the core network, the UE needs to report the corresponding non-3GPP device identifiers to the core network. This allows the core network to identify these non-3GPP devices and provide them with differentiated QoS information. For non-3GPP devices that do not require differentiated QoS from the core network, these devices can use the default QoS, and the UE does not need to report their non-3GPP device identifiers. Furthermore, as described above, without a USIM, the UE cannot use the above scheme to access the core network and report the non-3GPP device identifiers to the core network, thus preventing the core network from providing differentiated QoS information and consequently, preventing the provision of differentiated QoS services to the non-3GPP devices. Based on this, in order to improve the flexibility of non-3GPP device identifier reporting and meet the reporting requirements of non-3GPP device identifiers in more scenarios (such as scenarios where user equipment does not support NAS signaling), this application provides a related network architecture and related processes for user equipment registration and reporting of non-3GPP device identifiers of non-3GPP devices. These processes are applicable to the case where user equipment does not have a USIM, and can be referred to the description in the following method embodiments for details.

[0099] To better understand the embodiments of this application, the network architecture of the embodiments of this application will be described below.

[0100] Please refer to Figure 3, which is a schematic diagram of a network architecture (Non-3GPP access architecture) disclosed in an embodiment of this application. The core network in the network architecture shown in Figure 3 can be a converged core network of 5GC and EPC, and can be referred to as a 5GC / EPC converged network. As shown in Figure 3, this network architecture may include user equipment (UEs), which can be connected to one or more non-3GPP devices (such as non-3GPP devices #1 to #3 in Figure 3). UEs can connect to the core network through a non-3GPP access gateway, and the core network can identify the non-3GPP devices connected to the UEs.

[0101] Among them, non-3GPP devices can be devices that support data transmission via non-3GPP protocols (such as WiFi, Bluetooth, Ethernet, etc.), including but not limited to IoT sensors, smart home terminals, smartphones, etc. In this embodiment, non-3GPP devices can also be referred to as end devices.

[0102] Non-3GPP access gateways can be ePDGs. The interface between a non-3GPP access gateway and user plane network elements can be an S2b-user plane (S2b-U) interface. The user plane network element can be a converged network element combining user plane function (UPF) and packet data network gateway-user plane (PGW-U) (denoted as UPF / PGW-U). The interface between a non-3GPP access gateway and session management network elements can be an S2b-control plane (S2b-C) interface. The session management network element can be a converged network element combining session management function (SMF) and packet data network gateway-control plane (PGW-C) (denoted as SMF / PGW-C). The interface between a non-3GPP access gateway and the authentication, authorization, and accounting server (AAA server) can be an SWm interface. It should be understood that ePDG has a high deployment rate and has little or no impact on fixed network edge nodes. Therefore, using ePDG as a non-3GPP access gateway in this application embodiment can reduce deployment and maintenance costs.

[0103] In this embodiment, the user equipment can support access to the core network (such as a 5G core network) without a USIM, and can report the non-3GPP device identifiers of one or more non-3GPP devices connected via ePDG. For example, the user equipment can be an evolved residential gateway (eRG). The eRG can be a gateway device (such as an optical modem) deployed in the user's home, supporting wired access, wireless access (such as WiFi), etc. It should be noted that this embodiment does not limit the form of the user equipment; it can be various types of terminals (such as smartphones, laptops, etc.), access points (APs), etc.

[0104] In this application embodiment, the non-3GPP access gateway can include multiple deployment methods, two of which are exemplified below. One deployment method is the independent deployment of the non-3GPP access gateway and user plane network element as shown in Figure 3 (separate deployment). In another possible deployment method, the non-3GPP access gateway and user plane network element can be co-deployed. In this case, the non-3GPP access gateway and session management network element can interact through the interface between the user plane network element and session management network element. For example, when the non-3GPP access gateway is an ePDG, the ePDG can be co-deployed with UPF / PGW-U (denoted as ePDG / UPF / PGW-U). The ePDG can interact with the session management network element (SMF / PGW-C) through the N4 interface or the S2b-C interface. When the non-3GPP access gateway and user plane network element are co-deployed, there is no need to deploy the non-3GPP access gateway (such as ePDG) independently, which can reduce the deployment and maintenance costs of network elements. In cases where non-3GPP access gateways and user plane network elements are separated, the existing network element architecture can be used to reduce the impact on the existing network element architecture.

[0105] It should be understood that core network elements can include user plane network elements and control plane network elements. User plane network elements are mainly responsible for packet forwarding, quality of service (QoS) control, and billing information statistics. Control plane network elements are mainly responsible for user registration and authentication, mobility management, and issuing packet forwarding policies and QoS control policies to user plane network elements. Control plane network elements can include session management network elements, authentication network elements, data management network elements, policy control network elements, and so on.

[0106] The session management network element is responsible for establishing corresponding session connections when a user initiates a service, and providing specific services to the user, such as issuing packet forwarding policies and QoS policies to the UPF based on the N4 interface between the SMF and UPF. For example, the session management network element can be an SMF, PGW-C, or SMF / PGW-C.

[0107] The authentication and authorization network element can obtain subscription data from the data management network element and can be responsible for authenticating user equipment. For example, the authentication and authorization network element can be an AAA server. In this embodiment, the authentication and authorization network element can also be referred to as an authentication network element.

[0108] The data management network element is primarily responsible for storing and managing the subscription data of user equipment, such as providing subscription data to authentication and authorization network elements and policy control network elements. For example, the data management network element can be a unified data management (UDM) network element, a unified data repository (UDR) network element, a home subscriber server (HSS), or a converged UDM and HSS network element.

[0109] Policy control network elements are primarily used to issue service-related policies, such as providing relevant policies to session management network elements. For example, a policy control network element can be a policy control function (PCF) network element.

[0110] User plane network elements can connect to the data network (DN), which can provide services to user equipment, such as mobile operator services, Internet services, or third-party services.

[0111] It should be understood that although the above description uses a 5GC / EPC converged network as an example, the embodiments of this application are not limited thereto. For example, the core network can also be 5GC, the user plane network element can be UPF, and the session management network element can be SMF, etc.

[0112] It should be understood that the architecture shown in Figure 3 is merely an illustrative example, and other devices / network elements may also be included in the architecture shown in Figure 3. This application embodiment does not limit this. For example, the architecture shown in Figure 2 above may also be referred to.

[0113] It is understood that the aforementioned network elements and user equipment can be implemented in the form of hardware, computer software, or a combination of hardware and computer software. For example, the aforementioned network elements and user equipment can be implemented by a single device, multiple devices working together, or a functional module within a single device; this application does not specifically limit this.

[0114] It should be understood that the technical solutions provided in the embodiments of this application can be applied to various communication systems, such as fifth-generation (5G) communication systems, networks integrating multiple systems (such as 5GC / EPC converged networks), multi-band communication systems, and future communication systems.

[0115] It should be noted that the system architecture, network architecture, and business scenarios (or application scenarios) described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Those skilled in the art will understand that with the evolution of communication network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems. Furthermore, the names of the messages described in the embodiments of this application do not limit the messages themselves; for example, in a service-oriented architecture, a message can also be called a service.

[0116] In this embodiment, the timing of the user equipment reporting the non-non-3GPP device identifier to the core network can be divided into two cases: one is during the connection establishment phase of the user equipment, and the other is during the connection update phase of the user equipment. Furthermore, in these two cases, the process for reporting the non-non-3GPP device identifier can also differ depending on whether the non-3GPP access gateway and user plane network element are co-located or separately deployed.

[0117] For example, in a co-located deployment of the non-3GPP access gateway and user plane network elements, after receiving a non-non-3GPP device identifier from the user equipment, the non-3GPP access gateway can send the non-non-3GPP device identifier to the session management network element via the N4 interface. In a separate deployment of the non-3GPP access gateway and user plane network elements, after receiving the non-non-3GPP device identifier from the user equipment, the non-3GPP access gateway can send the non-non-3GPP device identifier to the session management network element via the S2b-C interface. It should be understood that the method of sending the non-non-3GPP device identifier to the session management network element via the S2b-C interface also applies to the co-located deployment of the non-3GPP access gateway and user plane network elements.

[0118] Furthermore, in this embodiment, the non-3GPP access gateway can also obtain first quantity information by interacting with authentication network elements or session management network elements. The first quantity information indicates the maximum number of non-3GPP device identifiers that a user equipment can simultaneously activate. After obtaining the first quantity information, the non-3GPP access gateway can control the number of non-3GPP device identifiers that a user equipment can simultaneously activate based on the first quantity information.

[0119] The overall scheme of the embodiments of this application will be described below.

[0120] Please refer to Figure 4, which is a flowchart illustrating a communication method disclosed in an embodiment of this application. As shown in Figure 4, the method may include, but is not limited to, the following steps:

[0121] 401. The user equipment sends a first message to the target non-3GPP access gateway.

[0122] The first message is used to request the establishment or renewal of a connection for a user equipment (UE). The first message includes the non-3GPP device identifier of the non-3GPP device to which the UE is connecting. For example, the first message may be an Internet Key Exchange (IKE) authentication request message or an IKE informational request message. Accordingly, the target non-3GPP access gateway can receive the first message from the UE. For example, the target non-3GPP access gateway may refer to the non-3GPP access gateway selected by the UE. The target non-3GPP access gateway may be an ePDG.

[0123] In this embodiment of the application, the user equipment can connect to non-3GPP devices, and the connected non-3GPP devices can be one or more. The non-3GPP device identifier of the non-3GPP device can be information used to identify the non-3GPP device. This embodiment of the application does not limit this, but it should be understood that the core network (such as SMF) can recognize the non-3GPP device identifier.

[0124] For example, the connection of the user equipment can be a protocol data unit (PDU) session or a packet data network (PDN) connection, or it can be other connections associated with the user equipment during the establishment / update of a PDU session or PDN connection, such as the connection between the session management network element associated with the user equipment and the user plane network element (such as an N4 session connection).

[0125] It should be noted that for non-3GPP access gateways in the network, some may support the non-3GPP device identifier capability, while others may not. The non-3GPP device identifier capability can refer to the ability to process non-3GPP device identifiers. For example, this capability may include the ability to identify non-3GPP device identifiers, report non-3GPP device identifiers, provide services to non-3GPP devices, process non-3GPP devices, or other capabilities related to reporting non-3GPP device identifiers (such as supporting a processing flow for reporting non-3GPP device identifiers), or a combination of these capabilities. For non-3GPP access gateways that support the non-3GPP device identifier capability, user equipment can report non-3GPP device identifiers through these gateways. For non-3GPP access gateways that do not support this capability, user equipment cannot report non-3GPP device identifiers through them. In this embodiment, the target non-3GPP access gateway can be a non-3GPP access gateway that supports non-3GPP device identifier capabilities. In some possible implementations, the user equipment can select the target non-3GPP access gateway from among non-3GPP access gateways that support non-3GPP device identifier capabilities (e.g., the ability to process non-3GPP device identifiers). For example, the user equipment can obtain information on multiple non-3GPP access gateways, each including information indicating whether it supports non-3GPP device identifier capabilities. Based on this information, the user equipment can determine which of the multiple non-3GPP access gateways supports non-3GPP device identifier capabilities, and then select one from these gateways. This selected non-3GPP access gateway is the target non-3GPP access gateway.

[0126] Furthermore, in some possible implementations, the non-3GPP access gateway can be co-located with the user plane network element. In this case, the target non-3GPP access gateway can be a non-3GPP access gateway that supports non-3GPP device identifier capability and is co-located with the user plane network element. In one possible implementation, the user equipment can select the target non-3GPP access gateway from among those that support non-3GPP device identifier capability and are co-located with the user plane network element, so that the target non-3GPP access gateway can subsequently send the non-3GPP device identifier to the session management network element through the interface between the user plane network element co-located with it (denoted as the target user plane network element) and the session management network element. For example, a user equipment can obtain information (such as capability information / selection information) of multiple non-3GPP access gateways. The information of each non-3GPP access gateway includes information indicating whether the non-3GPP access gateway supports the non-3GPP device identifier capability, and information indicating whether the non-3GPP access gateway is co-located with user plane network elements. The user equipment can determine the non-3GPP access gateway that supports the non-3GPP device identifier capability and is co-located with user plane network elements based on the information of multiple non-3GPP access gateways. Then, it can select one of these non-3GPP access gateways, and the selected non-3GPP access gateway is the target non-3GPP access gateway.

[0127] It is understood that the above descriptions regarding the selection of non-3GPP access gateways are merely illustrative and do not constitute a limitation. In other possible embodiments of this application, user equipment may refer to further information when selecting a non-3GPP access gateway. For example, user equipment may select a non-3GPP access gateway co-located with user plane network elements that support a specific access point name (APN) or data network name (DNN).

[0128] In some possible implementations, the user equipment (UE) may send first capability information to the target non-3GPP access gateway. This first capability information indicates that the UE supports connection with non-3GPP devices. This notifies the target non-3GPP access gateway that the UE has a need to report non-3GPP device identifiers, allowing the target non-3GPP access gateway to process the request accordingly, such as selecting a session management network element that supports non-3GPP device identifier capabilities. It should be noted that in some embodiments, the first capability information may be used to indicate that the UE supports non-3GPP device identifier capabilities. Optionally, the first capability information may be included in a first message or may be a separate message.

[0129] For example, an Internet Protocol Security (IPSec) channel can be established between a user equipment and a target non-3GPP access gateway. Communication can be carried out through the IPSec channel, such as the user equipment sending a first message to the target non-3GPP access gateway through the IPSec channel.

[0130] 402. The target non-3GPP access gateway sends a third message to the target session management network element. The third message is used to request the establishment or renewal of the user equipment connection. The third message includes the non-3GPP device identifier of the non-3GPP device.

[0131] For example, the third message could be a session report request message, an N4 session establishment response message, or a create session request message.

[0132] After receiving the first message from the user equipment, the target non-3GPP access gateway can send a third message to the target session management network element. This third message includes the non-3GPP device identifier of the non-3GPP device, which is the same non-3GPP device identifier of the non-3GPP device to which the user equipment is connected, carried in the first message. Correspondingly, the target session management network element can receive the third message from the target non-3GPP access gateway.

[0133] It should be noted that for session management network elements in the network, some may support non-3GPP device identifier capabilities, while others may not. For session management network elements that support non-3GPP device identifier capabilities, the target non-3GPP access gateway can report non-3GPP device identifiers through these network elements. For session management network elements that do not support non-3GPP device identifier capabilities, the target non-3GPP access gateway cannot report non-3GPP device identifiers through these network elements. In this embodiment, the target session management network element can be a session management network element that supports non-3GPP device identifier capabilities. In some possible implementations, the target non-3GPP access gateway can select the target session management network element from those that support non-3GPP device identifier capabilities (such as having the ability to process non-3GPP device identifiers). For example, the target non-3GPP access gateway can obtain information about multiple session management network elements. The information of each session management network element includes information indicating whether the session management network element supports non-3GPP device identifier capabilities. The target non-3GPP access gateway can determine the session management network element that supports non-3GPP device identifier capabilities among the multiple session management network elements based on the information of the multiple session management network elements, and then select one of these session management network elements that supports non-3GPP device identifier capabilities. The selected session management network element is the target session management network element.

[0134] In some possible implementations, the target non-3GPP access gateway can receive first capability information from the user equipment (UE), and then select a target session management network element (SMU) from among the SMUs capable of processing non-3GPP device identifiers based on the first capability information. For example, after receiving the first capability information from the UE, the target non-3GPP access gateway can determine based on the first capability information that the UE has a need to report a non-3GPP device identifier, and then select a target SMU from among the SMUs capable of processing non-3GPP device identifiers to support the subsequent reporting of non-3GPP device identifiers by the UE.

[0135] Optionally, the third message can be carried on the N4 interface or the S2b-C interface. For example, in the case where the target non-3GPP access gateway and the target user plane network element are co-located, the third message can be carried on the N4 interface, that is, the third message can be sent through the N4 interface.

[0136] In some possible implementations, the target non-3GPP access gateway can obtain first quantity information. This first quantity information can be used to indicate the maximum number of non-3GPP device identifiers that the user equipment (UE) is allowed to activate simultaneously (e.g., 10), that is, the maximum number of non-3GPP device identifiers that are allowed to be activated simultaneously by non-3GPP devices. For example, the maximum number of non-3GPP device identifiers that the UE is allowed to activate simultaneously can be understood as the maximum number of non-3GPP devices that the UE is allowed to activate simultaneously. For the UE, the activated non-3GPP devices are those that can provide differentiated QoS to the core network. In some possible cases, for non-3GPP devices that require differentiated QoS from the core network, the UE can report the non-3GPP device identifiers of these non-3GPP devices, so that the core network can identify these non-3GPP devices and provide differentiated QoS information. For non-3GPP devices that do not require differentiated QoS from the core network, these devices can use the default QoS. In this case, the user equipment does not need to report the non-3GPP device identifiers of these devices, and these non-3GPP devices can be disregarded as active non-3GPP devices. After obtaining the first quantity information, the target non-3GPP access gateway can perform relevant processing based on the first quantity information.

[0137] In one possible implementation, if the target non-3GPP access gateway obtains the first quantity information before sending the third message to the target session management network element, the target non-3GPP access gateway can determine, based on the first message, whether the number of non-3GPP device identifiers simultaneously activated by the user equipment exceeds the maximum number. If, based on the first message, the number of non-3GPP device identifiers simultaneously activated by the user equipment does not exceed the maximum number, the target non-3GPP access gateway sends the third message to the target session management network element. Conversely, if, based on the first message, the number of non-3GPP device identifiers simultaneously activated by the user equipment exceeds the maximum number, the target non-3GPP access gateway does not send the third message to the target session management network element. For example, the target non-3GPP access gateway can determine the number of non-3GPP device identifiers to be activated this time based on the number of non-3GPP device identifiers carried in the first message, or it can obtain the number of non-3GPP device identifiers currently activated by the user equipment. Then it can determine whether the sum of the two exceeds the maximum number. If it exceeds the maximum number, it means that if the non-3GPP device identifiers in the first message are activated, the number of non-3GPP device identifiers activated by the user equipment at the same time will exceed the maximum number. Therefore, the user equipment may not send a third message to the target session management network element. If it does not exceed the maximum number, it means that even if the non-3GPP device identifiers in the first message are activated, the number of non-3GPP device identifiers activated by the user equipment at the same time will not exceed the maximum number. Therefore, the user equipment may send a third message to the target session management network element.

[0138] Optionally, the first quantity information is carried on the N4 interface, SWm interface, or S2b-C interface.

[0139] In some possible implementations, the target non-3GPP access gateway can send a sixth message to the authentication network element, which requests authentication. Accordingly, the authentication network element can receive the sixth message from the target non-3GPP access gateway and then authenticate the user equipment based on the sixth message. If authentication is successful (or authentication passes), the authentication network element can send a seventh message to the target non-3GPP access gateway, which includes an authentication success indication and first quantity information. Accordingly, the target non-3GPP access gateway can receive the seventh message from the authentication network element. For example, the sixth message can be an authentication request message. The seventh message can be an authentication and authorization answer (AA-answer) message.

[0140] In other possible implementations, the target session management network element can obtain the first quantity information and send it to the target non-3GPP access gateway. Correspondingly, the target non-3GPP access gateway can receive the first quantity information from the target session management network element. Optionally, the target session management network element can send the first quantity information to the target non-3GPP access gateway via the N4 interface or the S2b-C interface.

[0141] For example, a non-3GPP access gateway can be co-located with a user plane network element. In this case, the target session management network element can select a target user plane network element co-located with the target non-3GPP access gateway so that the target non-3GPP access gateway and the target session management network element can interact through the interface between the target session management network element and the target user plane network element (such as the N4 interface). For example, the target session management network element can send a fifth message to the target user plane network element. The fifth message is used to request the creation / update of a connection (such as an N4 session connection) between the target session management network element and the target user plane network element. The fifth message may include first quantity information. Accordingly, the target non-3GPP access gateway can receive the fifth message from the target session management network element. It should be understood that in the above case, the fifth message can be carried on the N4 interface, that is, the first quantity information can be carried on the N4 interface. For example, the fifth message can be an N4 session establishment request message or an N4 session modification request message.

[0142] The following exemplifies a method by which a target session management network element obtains first quantity information. The target session management network element can send an eighth message to a policy control network element, the eighth message being used to request the establishment of a session management policy association. Correspondingly, the policy control network element can receive the eighth message from the target session management network element, and then can send a ninth message to the target session management network element based on the eighth message, the ninth message including the first quantity information and policy information. Correspondingly, the target session management network element can receive the ninth message from the policy control network element. For example, the eighth message can be a session management policy control create request (SMpolicy control create request), and the ninth message can be an SM policy control create response (SMpolicy control create response).

[0143] It should be noted that in some possible implementations, the third message may also be other messages, and this application embodiment does not limit this. For example, the third message may be a message used to establish or update the connection between the target session management network element and the target user plane network element, such as an N4 session establishment response.

[0144] 403. The target session management network element sends a fourth message to the target non-3GPP access gateway. The fourth message includes QoS information corresponding to the non-3GPP device identifier.

[0145] After receiving the third message from the target non-3GPP access gateway, the target session management network element can send a fourth message to the target non-3GPP access gateway based on the third message. Correspondingly, the target non-3GPP access gateway can receive the fourth message from the target session management network element. For example, the fourth message can be a create session response message or an update bearer request message.

[0146] For example, the target session management network element can generate QoS information for a non-3GPP device based on the non-3GPP device identifier included in the third message. The QoS information may include QoS flow identifiers, bandwidth information, etc.

[0147] 404. The target non-3GPP access gateway sends a second message to the user equipment, the second message including QoS information corresponding to the non-3GPP device identifier.

[0148] Accordingly, the user equipment can receive a second message from the target non-3GPP access gateway. For example, the second message may be an IKE authentication response message or an IKE informational request message.

[0149] In one possible implementation, if the target non-3GPP access gateway obtains the first quantity information before sending the second message to the user equipment, the target non-3GPP access gateway can determine, based on the first message, whether the number of non-3GPP device identifiers simultaneously activated by the user equipment exceeds the maximum number. If, based on the first message, the number of non-3GPP device identifiers simultaneously activated by the user equipment does not exceed the maximum number, the target non-3GPP access gateway sends the second message to the user equipment. Conversely, if, based on the first message, the number of non-3GPP device identifiers simultaneously activated by the user equipment exceeds the maximum number, the target non-3GPP access gateway does not send the second message to the user equipment.

[0150] In the above process, the user equipment can report non-3GPP device identifiers through the non-3GPP access gateway during the connection establishment or connection update phase, so that the core network (such as the session management network element) can identify the non-3GPP devices connected to the user equipment and provide differentiated services for these non-3GPP devices.

[0151] Figure 5 illustrates a possible implementation example of the method shown in Figure 4. Figure 5 demonstrates the process of a user equipment (UE) reporting non-3GPP device identifiers during the connection establishment phase and the connection update phase, when the user plane network element and the non-3GPP access gateway are co-located. Specifically, during the connection establishment phase, if the UE requires reporting non-3GPP device identifiers, it can report one or more non-3GPP device identifiers to the core network (such as a session management network element) through the non-3GPP access gateway to obtain the QoS information corresponding to those identifiers from the core network. Subsequently, if the UE still requires reporting non-3GPP device identifiers, it can initiate a connection update. During the connection update phase, the UE can again report one or more non-3GPP device identifiers to the core network through the non-3GPP access gateway to obtain the QoS information corresponding to those identifiers from the core network. The connection establishment phase can also be called the attach phase, which is the phase where the UE attaches to the network (such as the core network). As shown in Figure 5, this process may include, but is not limited to, the following steps:

[0152] 501. User equipment selects a non-3GPP access gateway.

[0153] For example, when a user equipment is in a deregistered state, it can initiate an initial attach procedure (or initial connection establishment procedure) to the core network for registration. Since the user equipment communicates with the core network through a non-3GPP access gateway, the user equipment can choose a non-3GPP access gateway.

[0154] In this embodiment, the user equipment can connect to one or more non-3GPP devices, thus requiring the reporting of non-3GPP device identifiers. Furthermore, the non-3GPP access gateway can be co-located with user plane network elements. In this case, to facilitate subsequent interaction between the non-3GPP access gateway and the session management network element through the interface between the user plane network element and the session management network element, the user equipment can choose to support non-3GPP device identifier capabilities and a non-3GPP access gateway co-located with user plane network elements.

[0155] For example, a user equipment (UE) can obtain information (such as capability information / selection information) about multiple non-3GPP access gateways. Based on the information of each non-3GPP access gateway, the UE can determine whether the non-3GPP access gateway supports the non-3GPP device identifier capability and whether it is co-located with user plane network elements. Therefore, the UE can select from these multiple non-3GPP access gateways that support the non-3GPP device identifier capability and are co-located with user plane network elements. For instance, the UE can determine the network selection strategy for non-3GPP access gateways through non-3GPP access gateway selection information. Based on the network selection strategy, the UE can select non-3GPP access gateways that support the non-3GPP device identifier capability and are co-located with user plane network elements, and can construct a fully qualified domain name (FQDN) for selecting non-3GPP access gateways.

[0156] Optionally, the user equipment may request the address information (such as the Internet Protocol (IP) address) of the selected non-3GPP access gateway from the domain name server (DNS) in order to communicate with the selected non-3GPP access gateway.

[0157] 502. The user equipment negotiates security parameters with the non-3GPP access gateway.

[0158] For example, a user equipment can initiate an Internet Key Exchange (IKE) Security Association (SA) initialization process (IKE_SA_INIT) to a selected non-3GPP access gateway. The user equipment and the non-3GPP access gateway can negotiate encryption algorithms, exchange random numbers (nonces), and perform Diffie-Hellman (DH value) exchange.

[0159] Optionally, after the user equipment negotiates security parameters with the non-3GPP access gateway, an Internet Protocol Security (IPSec) channel can be established between the user equipment and the target non-3GPP access gateway. Subsequently, the user equipment and the non-3GPP access gateway can communicate based on the IPSec channel.

[0160] In this embodiment of the application, when the user plane network element and the non-3GPP access gateway are co-located, the entire entity can be referred to as a co-located network element, that is, a network element where the user plane network element and the non-3GPP access gateway are co-located. In this case, communication between other devices (such as user equipment, session management network elements, etc.) and the user plane network element or the non-3GPP access gateway can be regarded as communication between other devices and the co-located network element. Therefore, the co-located user plane network element and the non-3GPP access gateway can share the interface with other network elements.

[0161] 503. The user equipment sends a first request to a non-3GPP access gateway.

[0162] To enable the core network to identify non-3GPP devices connected to a user equipment (UE), the UE can report the non-3GPP device identifier of a non-3GPP device connected to it to the core network. For example, the UE can send a first request to a non-3GPP access gateway, the first request including the non-3GPP device identifier of a non-3GPP device connected to the UE, hereinafter referred to as the target non-3GPP device.

[0163] The first request may also include a header, user equipment identification information (such as eRG ID), first capability information, APN / DNN information, etc. In this embodiment, the user equipment subscription data stored in the data management network element may include the user equipment identification information.

[0164] For example, the first request can be an IKE authentication request (IKE_auth request). The first request can be the first message in the method embodiment of Figure 4 above.

[0165] 504. Authentication process between non-3GPP access gateways and authentication network elements.

[0166] For example, after receiving the first request from a user equipment (UE), a non-3GPP access gateway can initiate an authentication process with the authentication network element to authenticate the UE. For instance, the non-3GPP access gateway can send an authentication request (sixth message) to the authentication network element, which may include the UE's identification information. Upon receiving the authentication request, the authentication network element can authenticate the UE based on the relevant information to determine the UE's identity and legitimacy.

[0167] 505. The authentication network element requests the user equipment's subscription data from the data management network element.

[0168] The user equipment subscription data requested by the authentication network element from the data management network element may include the first quantity information.

[0169] For example, after the user equipment is authenticated, the authentication network element can obtain the user equipment's subscription data from the data management network element.

[0170] 506. The authentication network element sends an authentication response message to the non-3GPP access gateway.

[0171] For example, after successful authentication of the user equipment, the authentication network element can send an authentication response message to the non-3GPP access gateway. The authentication response message may include an authentication success indication (such as a result code indicating successful authentication), service authorization information, Extensible Authentication Protocol (EAP) success information, key materials, etc. Optionally, the authentication response message may include the user equipment's subscription data, such as first quantity information.

[0172] For example, the authentication response message can be an authentication and authorization answer (AA-answer). The authentication response message can be the seventh message in the method embodiment of Figure 4 above.

[0173] 507. Non-3GPP access gateways select session management network elements.

[0174] In this embodiment, to facilitate the reporting of non-3GPP device identifiers, the non-3GPP access gateway can select a session management network element that supports non-3GPP device identifier capabilities. Optionally, the non-3GPP access gateway can select a session management network element that supports non-3GPP device identifier capabilities based on PDN GW selection information / parameters. It should be understood that when selecting a session management network element, the non-3GPP access gateway can also refer to more information, such as the APN / DNN information carried in the first request.

[0175] For example, the PDN GW selection function embedded in a non-3GPP access gateway (such as an ePDG) can perform PGW selection using PGW selection parameters provided by a data management network element (such as an HSS) to an authentication network element (such as an AAA server), or the non-3GPP access gateway can perform PGW selection based on the PDN GW information (including information indicating whether the PGW supports non-3GPP device identifier capabilities) contained in the static configuration at the time of network access. The PGW selection parameters may include user equipment subscription data, one or more PDN subscription contexts (including a pair of PDN gateway identifiers (PGW IDs) and APNs), information indicating whether the PGW supports non-3GPP device identifier capabilities, etc.

[0176] 508. A non-3GPP access gateway sends a request to the session management network element to create a user connection.

[0177] After a non-3GPP access gateway selects a session management network element, it can send a "Create User Connection" request to the selected session management network element to establish a connection for the user equipment. For example, the user equipment connection can be a PDU session or a PDN connection. Establishing a user equipment connection can be understood as creating a transmission channel between the user equipment and the core network.

[0178] For example, a user connection creation request may include APN information, radio access technology (RAT) type, non-3GPP access gateway control plane tunnel endpoint identifier (TEID), PDN type, PDN address, evolved packet system (EPS) bearer identifier, default EPS bearer QoS, non-3GPP access gateway user plane address, non-3GPP access gateway user plane TEID, APN-aggregate maximum bit rate (AMBR), selection mode, dual address bearer flag, monitoring information, billing ID, additional parameters, international mobile equipment identity (IMEI), and user location information.

[0179] For example, creating a user connection request can be a create session request.

[0180] 509. Session management network elements perform policy control network element selection.

[0181] Step 509 is optional.

[0182] 510. Establish policy associations between session management network elements and policy control network elements.

[0183] For example, a session management network element can establish a session management policy association with a policy control network element to obtain policy information of user equipment, such as policy and charging control rules (PCC). For instance, the session management network element can send a session management policy control create request (SM policy control create request) to the policy control network element. After receiving the SM policy control create request, the policy control network element can make policy decisions, generate policy information for the user equipment, and then send an SM policy control create response to the session management network element. The SM policy control create response may include the policy information of the user equipment.

[0184] In some possible implementations, the session management network element can assign addresses (such as IP addresses) to user equipment. During the SM policy association establishment process, the session management network element can send the user equipment's address to the policy control network element, such as by including it in the SM policy control creation request.

[0185] Optionally, during the SM policy association establishment process (e.g., after the policy control network element receives the SM policy control creation request), the policy control network element can also obtain the first quantity information corresponding to the user equipment from the data management network element (e.g., UDR), and then send the first quantity information corresponding to the user equipment to the session management network element. For example, the first quantity information can be carried in the SM policy control creation response, or it can be part of the user equipment's policy information. It should be understood that if the first quantity information is carried in step 506 above, the policy control network element does not need to send the first quantity information to the session management network element in step 510. Accordingly, in subsequent steps (e.g., in step 513), the session management network element does not need to send the first quantity information to the non-3GPP access gateway / user plane network element.

[0186] For example, the SM policy control creation request can be the eighth message in the method embodiment of Figure 4 above, and the SM policy control creation response can be the ninth message in the method embodiment of Figure 4 above.

[0187] It is understandable that for information regarding SM policy association creation, SM policy control creation request, and SM policy control creation response, you can refer to the descriptions in relevant standards, such as the relevant descriptions in 3GPP TS23.502.

[0188] 511. The session management network element selects user plane network elements.

[0189] For example, in order to facilitate subsequent data transmission between the non-3GPP access gateway and the APN / DNN, the session management network element can select a user plane network element. In this embodiment, the session management network element can select a user plane network element co-located with the non-3GPP access gateway, such as the user plane network element co-located with the non-3GPP access gateway that sent the user connection creation request in step 508.

[0190] In some possible implementations, the session management network element can obtain information about user plane network elements (such as capability information) and then select user plane network elements based on the obtained information. For example, the session management network element can obtain the capability information of user plane network elements during the N4 association setup / update process, or through the network repository function (NRF) network element.

[0191] It should be understood that when selecting user plane network elements, the session management network element can also refer to more information, such as APN / DNN information.

[0192] Step 511 is optional.

[0193] 512. Modify the policy association between the session management network element and the policy control network element.

[0194] For example, the session management network element can modify the session management policy association with the policy control network element, sending addresses assigned to non-3GPP access gateways to the policy control network element. For instance, the session management network element can send a session management policy control update request (SM policy control update request) to the policy control network element. The SM policy control update request may include addresses assigned to non-3GPP access gateways. After receiving the SM policy control update request, the policy control network element can perform relevant processing and send an SM policy control update response to the session management network element. The SM policy control update response may include information indicating whether the SM policy association update was successful or failed. If the update is successful, it may also include updated user equipment policy information.

[0195] Step 512 is optional. For example, if the session management network element has already sent the address of the non-3GPP access gateway to the policy control network element in step 512, then step 512 does not need to be executed.

[0196] Understandably, for information regarding SM policy association modification, SM policy control update requests, and SM policy control update responses, you can refer to the descriptions in relevant standards, such as the relevant descriptions in 3GPP TS23.502.

[0197] 513. The session management network element sends a connection establishment request to the user plane network element.

[0198] For example, a session management network element can send a connection establishment request to a user plane network element. The connection establishment request can be used to establish a connection between the session management network element and the user plane network element, such as an N4 session connection. The connection establishment request may include packet detection rules (PDR).

[0199] Optionally, the connection establishment request may include first quantity information. In this case, the session management network element can send the first quantity information to the user plane network element through the N4 interface, that is, it can send the first quantity information to the non-3GPP access gateway co-located with the user plane network element through the N4 interface.

[0200] For example, the connection establishment request can be an N4 session establishment request. The connection establishment request can be the fifth message in the method embodiment of Figure 4 above.

[0201] 514. The user plane network element sends a connection establishment response to the session management network element.

[0202] For example, after receiving a connection establishment request from a session management network element, the user plane network element can allocate tunnel information, such as its own address (e.g., IP address) and TEID, and then send a connection establishment response to the session management network element. The connection establishment response may include its own address and TEID allocated by the user plane network element.

[0203] In this embodiment of the application, if the first request in step 503 carries the non-3GPP device identifier of the target non-3GPP device, the user plane network element may carry the non-3GPP device identifier of the target non-3GPP device in the connection establishment response.

[0204] For example, the connection establishment response can be an N4 session establishment response. The connection establishment response can be the third message in the method embodiment of Figure 4 above.

[0205] 515. Modify the policy association between the session management network element and the policy control network element.

[0206] After receiving the non-3GPP device identifier of the target non-3GPP device carried in the connection establishment response, the session management network element can modify the policy association with the policy control network element to obtain the policy information corresponding to the non-3GPP device identifier of the target non-3GPP device. For example, the session management network element can send an SM policy control update request to the policy control network element. The SM policy control update request may include the non-3GPP device identifier of the target non-3GPP device. After receiving the SM policy control update request, the policy control network element can perform relevant processing and send an SM policy control update response to the session management network element. The SM policy control update response may include the policy information (such as PCC rules) corresponding to the non-3GPP device identifier of the target non-3GPP device.

[0207] Among them, the session management network element can generate information such as packet detection rules corresponding to the non-3GPP device identifier based on the policy information corresponding to the non-3GPP device identifier of the target non-3GPP device.

[0208] 516. The session management network element sends a connection update request to the user plane network element.

[0209] For example, a session management network element can send a connection update request to a user plane network element. This connection update request can be used to update the connection between the session management network element and the user plane network element, such as an N4 session connection. The connection update request may include updated packet detection rules (PDRs). These PDRs may include service data flow filters (SDF filters) and QoS flow identifiers (QFIs) related to non-3GPP device identifiers, such as service data flow filters and QoS flow identifiers related to the non-3GPP device identifier of the target non-3GPP device.

[0210] Optionally, the session management network element may include a first quantity information in the connection update request sent to the user plane network element.

[0211] For example, a connection update request can be an N4 session modification request. A connection update request can be the fifth message in the method embodiment shown in Figure 4 above.

[0212] 517. The user plane network element sends a connection update response to the session management network element.

[0213] For example, after receiving a connection update request from the session management network element, the user plane network element can update the packet detection rules (such as updating the service data flow filter and QoS flow identifier related to the non-3GPP device identifier of the target non-3GPP device), and then send a connection update response to the session management network element.

[0214] For example, a connection update response can be an N4 session modification response.

[0215] 518. The session management network element sends a create user connection response to the non-3GPP access gateway.

[0216] If, in step 514, the connection establishment response sent by the user plane network element to the session management network element includes a non-3GPP device identifier for the target non-3GPP device, the session management network element can include the QoS information corresponding to that non-3GPP device identifier, i.e., the QoS information corresponding to the target non-3GPP device, in the user plane network element's connection creation response sent to the non-3GPP access gateway. The session management network element can obtain the QoS information corresponding to the non-3GPP device identifier based on the policy information corresponding to the non-3GPP device identifier of the target non-3GPP device.

[0217] For example, the user connection creation response may also include the PGW user plane address, PGW user plane TEID, PGW control plane TEID, PDN type, PDN address, EPS bearer identifier, EPS bearer QoS, APN-AMBR, billing ID, reason, and the address assigned to a non-3GPP access gateway.

[0218] Optionally, the session management network element may carry first quantity information in the create user connection response sent to a non-3GPP access gateway.

[0219] For example, the user connection creation response can be a session creation response. The user connection creation response can be the fourth message in the method embodiment shown in Figure 4 above.

[0220] 519. The non-3GPP access gateway sends a first response to the user equipment.

[0221] If the non-3GPP access gateway receives the QoS information corresponding to the target non-3GPP device in the user connection creation response sent in step 518, the non-3GPP access gateway may carry the QoS information corresponding to the target non-3GPP device in the first response sent to the user equipment.

[0222] For example, the first response may also include an authentication success indication, an address assigned to the user equipment, and an associated PDN identifier. It is understood that the address assigned to the user equipment can be associated with the non-3GPP device identifier of the target non-3GPP device, i.e., associated with the target non-3GPP device. In this way, the target non-3GPP device can use the address assigned to the user equipment by the network side (such as a session management element) for user plane transmission.

[0223] It should be noted that, although the above process is illustrated by taking the first request in step 503 carrying a non-3GPP device identifier as an example, this application embodiment does not limit this. In some possible cases, the first request in step 503 may also carry multiple non-3GPP device identifiers. In subsequent processes, the core network may also generate QoS information for the multiple non-3GPP device identifiers and return it to the user equipment, and may also return information indicating the non-3GPP device identifier / non-3GPP device associated with each QoS information.

[0224] In some possible implementations, if the non-3GPP access gateway obtains the first quantity information, the non-3GPP device identifier carried in the first request, and the QoS information corresponding to the non-3GPP device identifier carried in the first request in the user connection creation response before sending the first response, then the non-3GPP access gateway can determine whether the number of non-3GPP device identifiers simultaneously activated by the user equipment exceeds the maximum number indicated by the first quantity information based on the number of non-3GPP device identifiers carried in the first request. If it does not exceed the maximum number, the non-3GPP access gateway carries the QoS information corresponding to the non-3GPP device identifier in the first response. For example, if it exceeds the maximum number, the non-3GPP access gateway may not carry the QoS information corresponding to the non-3GPP device identifier in the first response, or may perform other related processing, such as choosing to discard some QoS information.

[0225] Understandably, for a user equipment, it will typically only access a single non-3GPP access gateway. The user equipment can use this non-3GPP access gateway to report the non-3GPP device identifiers of the non-3GPP devices connected to it to the core network. Therefore, the non-3GPP access gateway can identify the non-3GPP devices that are simultaneously active behind the user equipment, thereby facilitating the management of the number of non-3GPP device identifiers that are simultaneously active behind the user equipment.

[0226] For example, the first response can be an IKE authentication response (IKE_auth response). The first response can be the second message in the method embodiment of Figure 4 above.

[0227] Steps 501-519 can be the connection establishment phase for the user equipment.

[0228] Optionally, the user equipment may also report a non-3GPP device identifier during the connection update phase, such as steps 520-527 below.

[0229] 520. The user equipment sends a second request to a non-3GPP access gateway.

[0230] The user equipment (UE) can send a second request to a non-3GPP access gateway. The second request may include non-3GPP device identifiers of non-3GPP devices connected to the UE. For example, the second request may include one or more non-3GPP device identifiers, i.e., the non-3GPP device identifiers of one or more non-3GPP devices connected to the UE. The second request may also include address information (such as a user plane address) corresponding to the one or more non-3GPP device identifiers, i.e., the address information of the one or more non-3GPP devices. The address information of the one or more non-3GPP devices can be assigned by the UE. For example, the UE can assign addresses to the one or more non-3GPP devices based on the addresses obtained in step 519, such as assigning different port numbers to different non-3GPP devices. In this embodiment, address information and addresses can be interchanged.

[0231] It is understandable that if the address of the user equipment is used as the address of the target non-3GPP device, the user equipment can reallocate the address of the target non-3GPP device and carry the non-3GPP device identifier and the corresponding address of the target non-3GPP device in the second request.

[0232] For example, the second request can be an IKE informational request. The second request can be the first message in the method embodiment of Figure 4 above. The IKE informational request can be used to trigger an IKE information exchange, including the non-3GPP device identifier of the non-3GPP device connected to the user equipment, and the address information corresponding to the non-3GPP device.

[0233] 521. A non-3GPP access gateway sends a modify bearer request to the session management network element.

[0234] For example, after receiving a second request from a user equipment, a non-3GPP access gateway can send a modify bearer request to the session management network element through the S2b-C interface.

[0235] Modify bearer requests may include EPS bearer identifier, EPS bearer QoS, and APN-AMBR.

[0236] For example, a modify bearer request can be a modify bearer command.

[0237] 522. A non-3GPP access gateway sends a user connection modification request to the session management network element.

[0238] For example, after receiving a second request from a user equipment, a non-3GPP access gateway can send a user connection modification request to the session management network element through the N4 interface.

[0239] The user connection modification request may include one or more non-3GPP device identifiers carried in the second request, as well as the corresponding address information.

[0240] For example, a user connection modification request can be a session report request, such as a Packet Forwarding Control Protocol (PFCP) session report request. A user connection modification request can also be the third message in the method embodiment shown in Figure 4 above.

[0241] In some possible implementations, if the non-3GPP access gateway obtains the first quantity information before sending the Modify Bearer Request and User Connection Modification Request to the User Equipment (UE), the non-3GPP access gateway can determine whether the number of non-3GPP device identifiers simultaneously activated by the UE exceeds the maximum number indicated by the first quantity information based on the number of non-3GPP device identifiers carried in the second request. If it does not exceed the maximum number, the non-3GPP access gateway sends the Modify Bearer Request and User Connection Modification Request to the Session Management Network (SMN). For example, if it exceeds the maximum number, the non-3GPP access gateway may not send the Modify Bearer Request and User Connection Modification Request to the SMN, or it may perform other related processing, such as choosing to discard some of the non-3GPP device identifiers and corresponding address information carried in the second request, that is, the User Connection Modification Request in step 522 carries some of the non-3GPP device identifiers and corresponding address information reported by the UE.

[0242] 523. Modify the connection between the session management network element and the policy control network element.

[0243] For example, a session management network element can modify the connection with a policy control network element, such as through IP-CAN session modification, to obtain policy information for user equipment (UE). For instance, the session management network element can send a session modification request to the policy control network element. This request may include one or more non-3GPP device identifiers and their corresponding address information received by the session management network element in a user connection modification request. Upon receiving the session modification request, the policy control network element can determine the UE's policy information (such as QoS information) based on the non-3GPP device identifier information retrieved from a data management network element (such as a UDR) and / or operator policies. Then, it can send a session modification response to the session management network element. This response may include updated UE policy information. The updated UE policy information may include the policy information corresponding to the one or more non-3GPP device identifiers.

[0244] Step 523 is optional.

[0245] 524. The session management network element sends a connection update request to the non-3GPP access gateway.

[0246] Session management network elements can modify user connections, such as modifying the default bearer of the PDN connection corresponding to a changed QoS. Furthermore, session management network elements can send connection update requests to non-3GPP access gateways. Connection update requests can include QoS information corresponding to one or more non-3GPP device identifiers, as well as the corresponding address information. For example, connection update requests can also include EPS bearer identifiers, traffic flow templates (TFTs), APN-AMBRs, and other information.

[0247] In some possible implementations, the session management network element can obtain the QoS information corresponding to the one or more non-3GPP device identifiers based on the policy information corresponding to the one or more non-3GPP device identifiers.

[0248] For example, a connection update request can be an update bearer request. A connection update request can be the fourth message in the method embodiment shown in Figure 4 above.

[0249] 525. Non-3GPP access gateways send connection update responses to session management network elements.

[0250] For example, after receiving a connection update request from a session management network element, a non-3GPP access gateway can process the request and send a connection update response to the session management network element. For example, the connection update response may include an EPS bearer identifier to confirm the bearer modification. If the connection update (bearer modification) fails, the session management network element can delete the relevant S2b bearer.

[0251] For example, a connection update response can be an update bearer response.

[0252] 526. The session management network element sends an acknowledgment message to the policy control network element.

[0253] After receiving an update response from a non-3GPP access gateway, the session management network element can send an acknowledgment message to the policy control network element to indicate whether the requested policy decision should be executed, such as whether the policy obtained in step 523 should be executed.

[0254] For example, the acknowledgment message could be a provision Ack message.

[0255] Step 526 is optional.

[0256] 527. A non-3GPP access gateway sends a second response to the user equipment.

[0257] If the non-3GPP access gateway receives QoS information corresponding to one or more non-3GPP device identifiers and corresponding address information in the connection update request sent in step 524, the non-3GPP access gateway may carry the QoS information corresponding to the one or more non-3GPP device identifiers and corresponding address information in the second response sent to the user equipment.

[0258] For example, the second response can be an IKE notification response (IKE informational request). The second response can be the second message in the method embodiment of Figure 4 above.

[0259] Steps 520-527 can be the connection update phase for the user device.

[0260] It should be noted that steps 520-527 can be executed independently and do not depend on steps 501-519.

[0261] In the above example process, it is supported that user equipment (UE) can report non-3GPP device identifiers from UE to the core network through a non-3GPP access gateway in scenarios without a SIM card (such as a USIM card). For example, the non-3GPP access gateway can report non-3GPP device identifiers from UE to the session management network element through the extended N4 interface, as in steps 514 and 522. This allows the session management network element to identify non-3GPP devices connected to the UE, thereby providing differentiated services for the non-3GPP devices connected to the UE. Furthermore, in the above process, the number of non-3GPP device identifiers that UE can activate simultaneously can also be limited through the non-3GPP access gateway.

[0262] Figure 6 illustrates another possible implementation example of the method shown in Figure 4. Figure 6 demonstrates the connection establishment process for a user equipment (UE) when a user plane network element and a non-3GPP access gateway are co-located, and the related process for the UE to report non-3GPP device identifiers during the connection update phase. Specifically, the UE can establish a connection through the non-3GPP access gateway. After the connection is established, if the UE needs to report non-3GPP device identifiers, it can initiate a connection update. During the connection update phase, the UE can report one or more non-3GPP device identifiers to the core network (such as a session management network element) through the non-3GPP access gateway to obtain QoS information corresponding to these identifiers from the core network. The main difference between the process in Figure 6 and that in Figure 5 is that during the connection establishment phase, the UE does not report non-3GPP device identifiers to the core network through the non-3GPP access gateway. As shown in Figure 6, this process may include, but is not limited to, the following steps:

[0263] Steps 601-614 are similar to steps 501-514, and you can refer to the relevant descriptions of steps 501-514 above. The main difference is that the relevant steps of steps 601-614 do not involve the reporting of non-3GPP device identifiers, etc.

[0264] Steps 615-616 are similar to steps 518-519, and you can refer to the relevant descriptions of steps 518-519 above. The main difference is that steps 615-616 do not involve the transmission of QoS information corresponding to non-3GPP device identifiers.

[0265] Steps 617-624 are similar to steps 520-527, and you can refer to the relevant descriptions of steps 520-527 above.

[0266] It should be noted that steps 617-624 can be executed independently and do not depend on steps 601-616.

[0267] Figure 7 illustrates another possible implementation example of the method shown in Figure 4. Figure 7 demonstrates the process of a user equipment (UE) reporting non-3GPP device identifiers during the connection establishment phase and the connection update phase, when the user plane network element and the non-3GPP access gateway are separate. Specifically, during the connection establishment phase, if the UE requires reporting non-3GPP device identifiers, it can report one or more non-3GPP device identifiers to the core network (such as a session management network element) through the non-3GPP access gateway to obtain the QoS information corresponding to those identifiers provided by the core network. Subsequently, if the UE still requires reporting non-3GPP device identifiers, it can initiate a connection update. During the connection update phase, the UE can again report one or more non-3GPP device identifiers to the core network through the non-3GPP access gateway to obtain the QoS information corresponding to those identifiers. As shown in Figure 7, this process may include, but is not limited to, the following steps:

[0268] 701. User equipment selects a non-3GPP access gateway.

[0269] In this embodiment, the user equipment can connect to one or more non-3GPP devices, and there is a need to report non-3GPP device identifiers. Therefore, the user equipment can select a non-3GPP access gateway that supports non-3GPP device identifier capabilities, so that the non-3GPP device identifier can be reported through the selected non-3GPP access gateway.

[0270] For example, a user equipment (UE) can obtain information (such as capability information / selection information) about multiple non-3GPP access gateways. Based on the information of each non-3GPP access gateway, it can determine whether the gateway supports the non-3GPP device identifier capability, and thus select a non-3GPP access gateway that supports this capability from among the multiple gateways. For instance, the UE can determine the network selection strategy for non-3GPP access gateways using the selection information, select a non-3GPP access gateway that supports the non-3GPP device identifier capability based on the selection strategy, and construct a fully qualified domain name (FQDN) for selecting the non-3GPP access gateway.

[0271] Optionally, the user equipment may request the address information of the selected non-3GPP access gateway from the Domain Name Server (DNS) in order to communicate with the selected non-3GPP access gateway.

[0272] 702. User equipment negotiates security parameters with non-3GPP access gateways.

[0273] 703. The user equipment sends a first request to a non-3GPP access gateway.

[0274] 704. Authentication process between non-3GPP access gateways and authentication network elements.

[0275] 705. The authentication network element requests the user equipment's subscription data from the data management network element.

[0276] 706. The authentication network element sends an authentication response message to the non-3GPP access gateway.

[0277] 707. Non-3GPP access gateways select session management network elements.

[0278] Steps 702-707 are similar to steps 502-507, and you can refer to the relevant descriptions of steps 502-507 above.

[0279] 708. A non-3GPP access gateway sends a request to the session management network element to create a user connection.

[0280] After selecting a session management network element, the non-3GPP access gateway can send a "Create User Connection Request" to the selected session management network element to establish a connection for the user equipment. If the non-3GPP access gateway receives the non-3GPP device identifier of the target non-3GPP device in the first request sent in step 703, the non-3GPP access gateway can include the non-3GPP device identifier of the target non-3GPP device in the "Create User Connection Request" sent to the session management network element.

[0281] In some possible implementations, if the non-3GPP access gateway obtains the first quantity information and the non-3GPP device identifier carried in the first request before sending the user connection creation request to the session management network element, the non-3GPP access gateway can determine whether the number of non-3GPP device identifiers simultaneously activated by the user equipment exceeds the maximum number indicated by the first quantity information based on the number of non-3GPP device identifiers carried in the first request. If it does not exceed the maximum number, the non-3GPP access gateway carries the non-3GPP device identifier in the user connection creation request. For example, if it exceeds the maximum number, the non-3GPP access gateway may not carry the non-3GPP device identifier in the user connection request, or may perform other related processing.

[0282] For example, a user connection creation request may also include APN information, RAT type, non-3GPP access gateway control plane TEID, PDN type, PDN address, evolved packet system (EPS) bearer identifier, default EPS bearer QoS, non-3GPP access gateway user plane address, non-3GPP access gateway user plane TEID, APN-AMBR, selection mode, dual address bearer flag, monitoring information, billing ID, additional parameters, IMEI (SV), and user location information.

[0283] For example, a user connection creation request can be a session creation request. A user connection creation request can be the third message in the method embodiment shown in Figure 4 above.

[0284] 709. Session management network elements perform policy control network element selection.

[0285] Step 709 is optional.

[0286] 710. Establish policy associations between session management network elements and policy control network elements.

[0287] Session management network elements can establish session management policy associations with policy control network elements to obtain policy information of user equipment (such as policy information corresponding to the non-3GPP device identifier of the target non-3GPP device), such as PCC rules. For example, the session management network element can send a session management policy control create request (SM policy control create request) to the policy control network element. After receiving the SM policy control create request, the policy control network element can make policy decisions, generate policy information for the user equipment, and then send an SM policy control create response to the session management network element. The SM policy control create response may include the policy information of the user equipment. For example, the SM policy control create request may include the non-3GPP device identifier of the target non-3GPP device, and the SM policy control create response may include the policy information (such as PCC rules) corresponding to the non-3GPP device identifier of the target non-3GPP device.

[0288] In some possible implementations, the session management network element can assign addresses (such as IP addresses) to user equipment. During the SM policy association establishment process, the session management network element can send the user equipment's address to the policy control network element, such as by including it in the SM policy control creation request.

[0289] Optionally, during the SM policy association establishment process (e.g., after the policy control network element receives the SM policy control creation request), the policy control network element can also obtain the first quantity information corresponding to the user equipment from the data management network element (e.g., UDR), and then send the first quantity information corresponding to the user equipment to the session management network element. For example, the first quantity information can be carried in the SM policy control creation response, or it can be part of the user equipment's policy information. It should be understood that if the first quantity information is carried in step 706 above, the policy control network element does not need to send the first quantity information to the session management network element in step 710. Accordingly, in subsequent steps (e.g., in step 715), the session management network element does not need to send the first quantity information to the non-3GPP access gateway.

[0290] For example, the SM policy control creation request can be the eighth message in the method embodiment of Figure 4 above, and the SM policy control creation response can be the ninth message in the method embodiment of Figure 4 above.

[0291] 711. Session management network element selects user plane network elements.

[0292] For example, in order to transmit data between the non-3GPP access gateway and the APN / DNN, the session management network element can select a user plane network element.

[0293] Step 711 is optional.

[0294] 712. Modify the policy association between the session management network element and the policy control network element.

[0295] Step 712 is optional. For example, if the session management network element has already sent the address of the non-3GPP access gateway to the policy control network element in step 712, then step 712 does not need to be executed.

[0296] 713. The session management network element sends a connection establishment request to the user plane network element.

[0297] For example, a session management network element can send a connection establishment request to a user plane network element. The connection establishment request can be used to establish a connection between the session management network element and the user plane network element, such as an N4 session connection. The connection establishment request may include packet detection rules (PDR).

[0298] For example, a connection establishment request can be an N4 session establishment request.

[0299] 714. The user plane network element sends a connection establishment response to the session management network element.

[0300] For example, after receiving a connection establishment request from a session management network element, the user plane network element can allocate tunnel information, such as its own address (e.g., IP address) and TEID, and then send a connection establishment response to the session management network element. The connection establishment response may include its own address and TEID allocated by the user plane network element.

[0301] For example, the connection establishment response can be an N4 session establishment response.

[0302] 715. The session management network element sends a create user connection response to the non-3GPP access gateway.

[0303] If, in step 708, the non-3GPP access gateway sends a request to the session management network element to create a user connection that includes a non-3GPP device identifier for the target non-3GPP device, the session management network element may include the QoS information corresponding to the non-3GPP device identifier, i.e., the QoS information corresponding to the target non-3GPP device, in the request to create a user connection sent to the non-3GPP access gateway.

[0304] For example, the user connection creation response may also include the PGW user plane address, PGW user plane TEID, PGW control plane TEID, PDN type, PDN address, EPS bearer identifier, EPS bearer QoS, APN-AMBR, billing ID, reason, and the address assigned to a non-3GPP access gateway.

[0305] Optionally, the session management network element may carry first quantity information in the create user connection response sent to a non-3GPP access gateway.

[0306] For example, the user connection creation response can be a session creation response. The user connection creation response can be the fourth message in the method embodiment shown in Figure 4 above.

[0307] 716. The non-3GPP access gateway sends a first response to the user equipment.

[0308] Step 716 is similar to step 519, and you can refer to the relevant description in step 519 above.

[0309] Steps 701-716 can be the connection establishment phase for the user equipment.

[0310] Optionally, the user equipment may also report a non-3GPP device identifier during the connection update phase, such as steps 717-724 below.

[0311] 717. The user equipment sends a second request to a non-3GPP access gateway.

[0312] Step 717 is similar to step 518, and you can refer to the relevant description in step 518 above.

[0313] 718. A non-3GPP access gateway sends a modify bearer request to the session management network element.

[0314] For example, after receiving a second request from a user equipment, a non-3GPP access gateway can send a modify bearer request to the session management network element through the S2b-C interface.

[0315] A modify bearer request may include one or more non-3GPP device identifiers carried in the second request, along with their corresponding address information. The modify bearer request may also include the EPS bearer identifier, EPS bearer QoS, and APN-AMBR.

[0316] For example, a modify bearer request can be a modify bearer command.

[0317] 719. Modify the connection between the session management network element and the policy control network element.

[0318] 720. The session management network element sends a connection update request to a non-3GPP access gateway.

[0319] 721. Non-3GPP access gateways send connection update responses to session management network elements.

[0320] 722. The session management network element sends an acknowledgment message to the policy control network element.

[0321] 723. The non-3GPP access gateway sends a second response to the user equipment.

[0322] Steps 719-723 are similar to steps 523-527, and you can refer to the relevant descriptions of steps 523-527 above.

[0323] Steps 717-723 can be the connection update phase for the user device.

[0324] It should be noted that steps 717-723 can be executed independently and do not depend on steps 701-716.

[0325] In the above example process, it is supported that user equipment (UE) can report non-3GPP device identifiers from UE to the core network through a non-3GPP access gateway in scenarios without a SIM card (such as a USIM card). For example, the non-3GPP access gateway can report the non-3GPP device identifiers from UE to the session management network element through an extended S2b-C interface, as in step 708. This allows the session management network element to identify the non-3GPP devices connected to the UE, thereby providing differentiated services for the non-3GPP devices connected to the UE. Furthermore, in the above process, the number of non-3GPP device identifiers that UE can activate simultaneously can also be limited through the non-3GPP access gateway.

[0326] Figure 8 illustrates another possible implementation example of the method shown in Figure 4. Figure 8 demonstrates the connection establishment process for a user equipment (UE) when the user plane network element and the non-3GPP access gateway are separate, as well as the related process for the UE to report non-3GPP device identifiers during the connection update phase. Specifically, the UE can establish a connection through the non-3GPP access gateway. After the connection is established, if the UE needs to report non-3GPP device identifiers, it can initiate a connection update. During the connection update phase, the UE can report one or more non-3GPP device identifiers to the core network (such as a session management network element) through the non-3GPP access gateway to obtain the QoS information corresponding to these identifiers from the core network. The main difference between the process in Figure 8 and that in Figure 7 is that during the connection establishment phase, the UE does not report non-3GPP device identifiers to the core network through the non-3GPP access gateway. As shown in Figure 8, this process may include, but is not limited to, the following steps:

[0327] Steps 801-816 are similar to steps 701-716, and you can refer to the relevant descriptions of steps 701-716 above. The main difference is that the relevant steps of steps 801-816 do not involve the reporting of non-3GPP device identifiers or the transmission of QoS information corresponding to non-3GPP device identifiers.

[0328] Steps 817-823 are similar to steps 717-723, and you can refer to the relevant descriptions of steps 717-723 above.

[0329] It should be noted that steps 817-823 can be executed independently and do not depend on steps 801-816.

[0330] It should be noted that the relevant information and descriptions in the different embodiments described above can be referenced interchangeably. Furthermore, technical features in different method embodiments can be combined to form new embodiments based on their inherent logical relationships. For example, the various methods of reporting non-3GPP device identifiers illustrated in the above method embodiments can be combined. In addition, different implementations or examples within the same method embodiment can also be referenced or consulted with each other.

[0331] It should be understood that Figures 4-8 above primarily illustrate the above processing flow using user equipment, non-3GPP access gateways, session management network elements, and authentication network elements as examples of the execution entities in the interaction illustrations. However, this application does not limit the execution entities in these interaction illustrations. For example, the user equipment in Figures 4-8 could also be a chip, chip system, or processor that supports the user equipment in implementing this method, or it could be a logic module or software capable of implementing all or part of the user equipment's functions. Similarly, the non-3GPP access gateway in Figures 4-8 could also be a chip, chip system, or processor that supports the non-3GPP access gateway in implementing this method, or it could be a logic module or software capable of implementing all or part of the non-3GPP access gateway's functions.

[0332] The foregoing mainly describes the communication method provided in the embodiments of this application. It is understood that the aforementioned user equipment, non-3GPP access gateway, session management network element, authentication network element, etc., may include hardware structures and / or software modules corresponding to each function in order to achieve the corresponding functions. Based on the units and steps of the various examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this application.

[0333] This application embodiment can divide user equipment, non-3GPP access gateway, session management network element, authentication network element, etc., into functional modules according to the above method examples. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0334] Figure 9 shows a possible structural diagram of a communication device 900, where each functional module is divided according to its corresponding function. The communication device 900 may include a communication unit 901. The communication device 900 may also include a processing unit 902. Optionally, the communication unit 901 may also be referred to as a transceiver unit, an output unit, or an interface unit, etc. In one possible implementation, the communication unit 901 includes at least one of a transmitting unit or a receiving unit. The transmitting unit and the receiving unit may be integrated together, or they may be two independent units, etc. In one possible design, the communication device 900 may be the aforementioned user equipment, or it may be a component within the user equipment (e.g., a processor, chip, chip system, circuit, or functional module), or it may be a processing system within the user equipment, etc. The user equipment connects to non-3GPP equipment.

[0335] When the communication device 900 is used for the functions of the user equipment in the embodiments shown in Figures 4-8 above, for example:

[0336] Communication unit 901 is used to send a first message to a target non-3GPP access gateway, the first message being used to request the establishment or update of the connection of the user equipment, the first message including the non-3GPP device identifier of the non-3GPP device.

[0337] The communication unit 901 is further configured to receive a second message from the target non-3GPP access gateway, the second message including the Quality of Service (QoS) information corresponding to the non-3GPP device identifier.

[0338] In one possible implementation, the communication unit 901 is further configured to send first capability information to the target non-3GPP access gateway, the first capability information being used to indicate that the user equipment supports connection with non-3GPP devices.

[0339] In one possible implementation, the processing unit 902 is configured to select the target non-3GPP access gateway from among non-3GPP access gateways capable of processing non-3GPP device identifiers.

[0340] In one possible implementation, the processing unit 902 selects the target non-3GPP access gateway from non-3GPP access gateways capable of processing non-3GPP device identifiers, including: selecting the target non-3GPP access gateway from non-3GPP access gateways capable of processing non-3GPP device identifiers and co-located with user plane network elements.

[0341] The specific operation of each unit in the above-mentioned communication device 900 can be found in the description of the user equipment in the embodiments shown in Figures 4-8 above, and will not be repeated here.

[0342] In another possible design, the communication device 900 may be the aforementioned non-3GPP access gateway, or it may be a component (e.g., processor, chip, chip system, circuit or functional module) in the non-3GPP access gateway, or it may be a processing system in the non-3GPP access gateway, etc.

[0343] When the communication device 900 is used for the function of a non-3GPP access gateway in the embodiments shown in Figures 4-8 above, for example:

[0344] Communication unit 901 is configured to receive a first message from user equipment, the first message being used to request the establishment or renewal of the connection of the user equipment; the first message includes a non-3GPP device identifier of a non-3GPP device to which the user equipment is connected.

[0345] The communication unit 901 is also used to send a third message to the target session management network element, the third message being used to request the establishment or update of the connection of the user equipment, the third message including the non-3GPP device identifier of the non-3GPP device;

[0346] The communication unit 901 is also configured to receive a fourth message from the target session management network element, the fourth message including the quality of service (QoS) information corresponding to the non-3GPP device identifier;

[0347] The communication unit 901 is also configured to send a second message to the user equipment, the second message including QoS information corresponding to the non-3GPP device identifier.

[0348] In one possible implementation, the processing unit 902 is configured to select the target session management network element from session management network elements capable of processing non-3GPP device identifiers.

[0349] In one possible implementation, the communication unit 901 is further configured to receive first capability information from the user equipment, the first capability information being used to indicate that the user equipment supports connection with non-3GPP equipment; the processing unit 902 selects the target session management network element from session management network elements capable of processing non-3GPP equipment identifiers by: selecting the target session management network element from session management network elements capable of processing non-3GPP equipment identifiers based on the first capability information.

[0350] In one possible implementation, the processing unit 902 is further configured to acquire first quantity information, which indicates the maximum number of non-3GPP device identifiers that the user equipment is allowed to activate simultaneously; the communication unit 901 sends a third message to the target session management network element including: if it is determined based on the first message that the number of non-3GPP device identifiers that the user equipment is allowed to activate simultaneously does not exceed the maximum number, sending a third message to the target session management network element.

[0351] In one possible implementation, the processing unit 902 is further configured to acquire first quantity information, which indicates the maximum number of non-3GPP device identifiers that the user equipment is allowed to activate simultaneously; the communication unit 901 sends a second message to the user equipment by: if it is determined based on the first message that the number of non-3GPP device identifiers that the user equipment can activate simultaneously does not exceed the maximum number, sending a second message to the user equipment.

[0352] In one possible implementation, the first quantity information is carried on the N4 interface, SWm interface, or S2b-C interface.

[0353] In one possible implementation, the target user plane network element is co-located with the target non-3GPP access gateway. The processing unit 902 obtains the first quantity information by receiving a fifth message from the target session management network element through the communication unit 901. The fifth message is used to request the creation of a connection between the target session management network element and the target user plane network element. The fifth message includes the first quantity information.

[0354] In one possible implementation, the processing unit 902 obtains the first quantity information by: sending a sixth message to the authentication network element through the communication unit 901, the sixth message being used to request authentication; and receiving a seventh message from the authentication network element through the communication unit 901, the seventh message including an authentication success indication and the first quantity information.

[0355] In one possible implementation, the third message is carried on the N4 interface or the S2b-C interface.

[0356] The specific operation of each unit in the above-mentioned communication device 900 can be found in the description of the non-3GPP access gateway in the embodiments shown in Figures 4-8 above, and will not be repeated here.

[0357] In another possible design, the communication device 900 may be the aforementioned session management network element, or a component within the session management network element (e.g., a processor, chip, chip system, circuit, or functional module), or a processing system within the session management network element, etc.

[0358] When the communication device 900 is used for the function of the session management network element in the embodiments shown in Figures 4-8 above, for example:

[0359] Communication unit 901 is configured to receive a third message from a target non-3GPP access gateway, the third message being used to request the establishment or renewal of a connection for a user equipment; the third message includes a non-3GPP device identifier of the non-3GPP device to which the user equipment is connected.

[0360] The communication unit 901 is also configured to send a fourth message to the target non-3GPP access gateway, the fourth message including the Quality of Service (QoS) information corresponding to the non-3GPP device identifier.

[0361] In one possible implementation, the processing unit 902 is used to select a target user plane network element co-located with the target non-3GPP access gateway; the communication unit 901 is further used to send a fifth message to the target user plane network element, the fifth message being used to request the creation of a connection between the session management network element and the target user plane network element.

[0362] In one possible implementation, the processing unit 902 is further configured to acquire first quantity information, which indicates the maximum number of non-3GPP device identifiers that the user equipment is allowed to activate simultaneously; the communication unit 901 is further configured to send the first quantity information to the target non-3GPP access gateway.

[0363] In one possible implementation, the processing unit 902 obtains the first quantity information by: sending an eighth message to the policy control network element through the communication unit 901, the eighth message being used to request the establishment of a session management policy association; and receiving a ninth message from the policy control network element through the communication unit 901, the ninth message including the first quantity information and policy information.

[0364] In one possible implementation, sending the first quantity information to the target non-3GPP access gateway includes: sending the first quantity information to the target non-3GPP access gateway via the communication unit 901 on the N4 interface or the S2b-C interface.

[0365] In one possible implementation, the target user plane network element is co-located with the target non-3GPP access gateway. The communication unit 901 sends the first quantity information to the target non-3GPP access gateway by sending a fifth message to the target user plane network element. The fifth message is used to request the creation of a connection between the session management network element and the target user plane network element. The fifth message includes the first quantity information.

[0366] In one possible implementation, the third message is carried on the N4 interface or the S2b-C interface.

[0367] The specific operation of each unit in the above-mentioned communication device 900 can be found in the description of the session management network element in the embodiments shown in Figures 4-8 above, and will not be repeated here.

[0368] Figure 10 shows a possible hardware structure diagram of the communication device 1000 provided in an embodiment of this application. The communication device 1000 may include a communication interface 1004 and at least one processor 1002. Optionally, it may also include a bus 1003. Further optionally, it may also include at least one memory 1001, wherein the memory 1001, the processor 1002 and the communication interface 1004 can be connected through the bus 1003.

[0369] The memory 1001 provides storage space, which can store data such as the operating system and computer programs. The memory 1001 can be one or a combination of several of the following: random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM).

[0370] Processor 1002 is a module that performs arithmetic and / or logical operations. Specifically, it can be one or a combination of processing modules such as a central processing unit (CPU), graphics processing unit (GPU), microprocessor unit (MPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), complex programmable logic device (CPLD), coprocessor (assisting the CPU in completing corresponding processing and applications), and microcontroller unit (MCU). For example, processor 1002 can be used to process communication protocols and communication data.

[0371] The communication interface 1004 is used to receive and / or transmit data to external sources. Optionally, the communication interface 1004 may also include a transmitter (such as an RF transmitter, antenna, etc.) and / or a receiver coupled to the interface. For example, the communication interface 1004 may include a control circuit and an antenna. The control circuit is mainly used for converting baseband signals to RF signals and processing RF signals. The antenna is mainly used for transmitting and receiving RF signals in the form of electromagnetic waves. When data needs to be transmitted wirelessly, the processor 1002 performs baseband processing on the data to be transmitted and outputs a baseband signal to the control circuit. The control circuit then performs RF processing on the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the control circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 1002. The processor 1002 converts the baseband signal back into data and processes the data.

[0372] In one possible implementation, the control circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the control circuitry and antenna can be arranged in a remote manner, independent of the communication device.

[0373] In one design, the communication device 1000 can be used to perform the functions of the user equipment in the embodiments shown in Figures 4-8. For details, please refer to the relevant descriptions of the user equipment in Figures 4-8, which will not be repeated here.

[0374] In another design, the communication device 1000 can be used to perform the functions of a non-3GPP access gateway in the embodiments shown in Figures 4-8. For details, please refer to the relevant descriptions of the non-3GPP access gateways in Figures 4-8 above; further details will not be elaborated here.

[0375] In another design, the communication device 1000 can be used to perform the functions of the session management network element in the embodiments shown in Figures 4-8. For details, please refer to the relevant descriptions of the session management network element in Figures 4-8 above; further details will not be elaborated here.

[0376] In another design, the communication device 1000 can be used to perform the functions of the authentication network element in the embodiments shown in Figures 4-8. For details, please refer to the relevant descriptions of the authentication network element in Figures 4-8 above; further details will not be elaborated here.

[0377] In one possible design, the memory 1001 may store instructions, which may be computer programs that run on the processor 1002 and cause the communication device 1000 to perform operations performed by the user equipment in any of the above method embodiments, or operations performed by a non-3GPP access gateway, or operations performed by a session management network element, or operations performed by an authentication network element. For details, please refer to the relevant descriptions in Figures 4-8 above, which will not be elaborated here.

[0378] It should be noted that the communication device 1000 shown in Figure 10 is only one implementation of the embodiment of this application. In actual applications, the communication device 1000 may include more or fewer components, which is not limited here.

[0379] This application also discloses a communication system, which includes at least one of a user equipment, a non-3GPP access gateway, a session management network element, and an authentication network element. The user equipment is used to perform the operations performed by the user equipment in any of the above method embodiments. The non-3GPP access gateway is used to perform the operations performed by the non-3GPP access gateway in any of the above method embodiments. The session management network element is used to perform the operations performed by the session management network element in any of the above method embodiments. The authentication network element is used to perform the operations performed by the authentication network element in any of the above method embodiments.

[0380] This application also discloses a chip, which includes a processor, wherein the processor is configured to execute a computer program or computer instructions stored in a memory, causing the chip to perform operations performed by the user equipment in the above method embodiments, or to perform operations performed by a non-3GPP access gateway in the above method embodiments, or to perform operations performed by a session management network element in the above method embodiments, or to perform operations performed by an authentication network element in the above method embodiments.

[0381] As one possible implementation, the memory is located outside the chip.

[0382] This application also discloses a computer-readable storage medium storing instructions that, when executed, perform operations performed by the user equipment in the above method embodiments, or operations performed by a non-3GPP access gateway in the above method embodiments, or operations performed by a session management network element in the above method embodiments, or operations performed by an authentication network element in the above method embodiments.

[0383] This application also discloses a computer program product including instructions, which, when executed, perform operations performed by the user equipment in the above method embodiments, or operations performed by the non-3GPP access gateway in the above method embodiments, or operations performed by the session management network element in the above method embodiments, or operations performed by the authentication network element in the above method embodiments.

[0384] It should be understood that the transmission in the embodiments of this application can be direct or indirect. Direct transmission means that one device or module directly sends information / data to the corresponding device or module, while indirect transmission means that one device or module sends information / data to the corresponding device or module through other devices or modules.

[0385] Obviously, the embodiments described above are only some embodiments of this application, and not all embodiments. The term "embodiment" as used herein means that a specific feature, structure, or characteristic described in connection with an embodiment can be included in at least one embodiment of this application. The appearance of this phrase in various places in the specification does not necessarily indicate the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art will understand, explicitly and implicitly, that the embodiments described herein can be combined with other embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without inventive effort are within the scope of protection of this application. The terms "first," "second," "third," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects and are not used to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, it may include a series of steps or units, or optionally, steps or units not listed, or optionally other steps or units inherent to these processes, methods, products, or devices. It is also understandable that, for an architecture with multiple devices or modules, if one device or module generates a piece of information and another device or module uses that information, there are multiple ways for the other device to obtain that information. For example, the device or module that generated the information may send the information directly to the device or module that used the information (equivalent to direct sending), or the device or module that generated the information may send the information to the device or module that used the information through other devices or modules (equivalent to indirect sending).

[0386] It is understood that the accompanying drawings show only the parts relevant to this application and not all of them. It should be understood that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe operations (or steps) as sequential processes, many of these operations can be performed in parallel, concurrently, or simultaneously. Furthermore, the order of the operations can be rearranged. The process can be terminated when its operation is completed, but may also have additional steps not included in the drawings. The process can correspond to a method, function, procedure, subroutine, subroutine, etc.

[0387] The terms “component,” “module,” “system,” “unit,” etc., used in this specification are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a unit can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, a thread of execution, a program, and / or distributed between two or more computers. Furthermore, these units can be executed from various computer-readable media on which various data structures are stored. For example, a unit can communicate via local and / or remote processes based on signals having one or more data packets (e.g., data from a second unit interacting with another unit between a local system, a distributed system, and / or a network; for example, the Internet interacting with other systems via signals).

[0388] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above description is only a specific embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of this application should be included within the scope of protection of this application.

Claims

1. A communication method characterized by comprising: Applied to user equipment connected to non-3GPP (3rd Generation Partnership Project) equipment, the method includes: Send a first message to the target non-3GPP access gateway. The first message is used to request the establishment or update of the connection of the user equipment. The first message includes the non-3GPP device identifier of the non-3GPP device. Receive a second message from the target non-3GPP access gateway, the second message including the Quality of Service (QoS) information corresponding to the non-3GPP device identifier.

2. The method of claim 1, wherein, The method further includes: Send first capability information to the target non-3GPP access gateway, the first capability information being used to indicate that the user equipment supports connection with non-3GPP devices.

3. The method according to claim 1 or 2, characterized in that, The method further includes: The target non-3GPP access gateway is selected from the non-3GPP access gateways that have the ability to process non-3GPP device identifiers.

4. The method of claim 3, wherein, Selecting the target non-3GPP access gateway from among non-3GPP access gateways capable of processing non-3GPP device identifiers includes: The target non-3GPP access gateway is selected from non-3GPP access gateways that have the ability to process non-3GPP device identifiers and are co-located with user plane network elements.

5. A communication method characterized by comprising: Applied to non-3GPP access gateways, the method includes: A first message is received from a user equipment, the first message being used to request the establishment or renewal of a connection of the user equipment; the first message includes a non-3GPP device identifier of a non-3GPP device to which the user equipment is connected. A third message is sent to the target session management network element. The third message is used to request the establishment or update of the connection of the user equipment. The third message includes the non-3GPP device identifier of the non-3GPP device. Receive a fourth message from the target session management network element, the fourth message including the Quality of Service (QoS) information corresponding to the non-3GPP device identifier; A second message is sent to the user equipment, the second message including QoS information corresponding to the non-3GPP device identifier.

6. The method of claim 5, wherein, The method further includes: The target session management network element is selected from the session management network elements that are capable of processing non-3GPP device identifiers.

7. The method of claim 6, wherein, The method further includes: Receive first capability information from the user equipment, the first capability information being used to indicate that the user equipment supports connection with non-3GPP equipment; Selecting the target session management network element from session management network elements capable of processing non-3GPP device identifiers includes: Based on the first capability information, the target session management network element is selected from session management network elements that have the ability to process non-3GPP device identifiers.

8. The method according to any one of claims 5-7, characterized in that, The method further includes: Obtain first quantity information, which indicates the maximum number of non-3GPP device identifiers that the user equipment is allowed to activate simultaneously. The sending of the third message to the target session management network element includes: If, based on the first message, it is determined that the number of non-3GPP device identifiers simultaneously activated by the user equipment does not exceed the maximum number, a third message is sent to the target session management network element.

9. The method according to any one of claims 5-7, characterized in that, The method further includes: Obtain first quantity information, which indicates the maximum number of non-3GPP device identifiers that the user equipment is allowed to activate simultaneously. Sending the second message to the user equipment includes: If, based on the first message, it is determined that the number of non-3GPP device identifiers simultaneously activated by the user equipment does not exceed the maximum number, a second message is sent to the user equipment.

10. The method according to claim 8 or 9, characterized in that, The first quantity information is carried on the N4 interface, SWm interface, or S2b-C interface.

11. The method according to any one of claims 8-10, characterized in that, The target user plane network element is co-located with the target non-3GPP access gateway, and obtaining the first quantity information includes: A fifth message is received from the target session management network element, the fifth message being used to request the creation of a connection between the target session management network element and the target user plane network element, the fifth message including the first quantity information.

12. The method according to any one of claims 8-10, characterized in that, The acquisition of the first quantity information includes: Send a sixth message to the authentication network element, the sixth message being used to request authentication; A seventh message is received from the authentication network element, the seventh message including an authentication success indication and the first quantity information.

13. The method according to any one of claims 5-12, characterized in that, The third message is carried on the N4 interface or the S2b-C interface.

14. A communication method, characterized in that, Applied to a session management network element, the method includes: Receive a third message from a target non-3GPP access gateway, the third message being used to request the establishment or renewal of a connection for a user equipment; the third message includes a non-3GPP device identifier of the non-3GPP device to which the user equipment is connected. A fourth message is sent to the target non-3GPP access gateway, the fourth message including the Quality of Service (QoS) information corresponding to the non-3GPP device identifier.

15. The method according to claim 14, characterized in that, The method further includes: Select the target user plane network element that is co-located with the target non-3GPP access gateway; A fifth message is sent to the target user plane network element, the fifth message being used to request the creation of a connection between the session management network element and the target user plane network element.

16. The method according to claim 14, characterized in that, The method further includes: Obtain first quantity information, which indicates the maximum number of non-3GPP device identifiers that the user equipment is allowed to activate simultaneously. The first quantity information is sent to the target non-3GPP access gateway.

17. The method according to claim 16, characterized in that, The acquisition of the first quantity information includes: Send an eighth message to the policy control network element, the eighth message being used to request the establishment of a session management policy association; The system receives a ninth message from the policy control network element, the ninth message including first quantity information and policy information.

18. The method according to claim 16 or 17, characterized in that, Sending the first quantity information to the target non-3GPP access gateway includes: The first quantity information is sent to the target non-3GPP access gateway via the N4 interface or the S2b-C interface.

19. The method according to any one of claims 16-18, characterized in that, The target user plane network element is co-located with the target non-3GPP access gateway, and sending the first quantity information to the target non-3GPP access gateway includes: A fifth message is sent to the target user plane network element. The fifth message is used to request the creation of a connection between the session management network element and the target user plane network element. The fifth message includes the first quantity information.

20. The method according to any one of claims 14-19, characterized in that, The third message is carried on the N4 interface or the S2b-C interface.

21. A communication system, characterized in that, The device includes at least one of a user equipment, a non-3GPP access gateway, and a session management network element, wherein the user equipment is used to implement the method of any one of claims 1-4, the non-3GPP access gateway is used to implement the method of any one of claims 5-13, and the session management network element is used to implement the method of any one of claims 14-20.

22. A communication device, characterized in that, Includes modules for implementing the method as described in any one of claims 1-20.

23. A communication device, characterized in that, The device includes a processor and a transceiver, the transceiver being used to send and receive information, and the processor being used to enable the communication device to implement the method as described in any one of claims 1-20.

24. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or computer instructions that are executed by a processor to implement the method as described in any one of claims 1-20.

25. A computer program product, characterized in that, The computer program product includes computer program code or computer instructions, which, when executed, implement the method described in any one of claims 1-20.

Images