A communication method and apparatus

Abstract

The embodiment of the application discloses a communication method and device, which can be applied to a 5G / 4G fusion network, and the method comprises the following steps: a first network element receives a first request from a second network element, the first request is used for requesting to create a session, the first request comprises an identifier of the second network element, and the second network element is used for being responsible for non-3GPP access and user plane data processing; and based on the identifier of the second network element, the second network element is selected to create the session. The second network element fuses the non-3GPP access function and the user plane data processing function to realize session creation, so that when message forwarding processing is performed, the ePDG and the UPF network element (or PGW-U) twice protocol processing, and twice tunnel encapsulation and decapsulation can be avoided, cross-network element forwarding is reduced, and transmission delay is reduced.

Description

Technical Field

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

[0002] In 5G / 4G converged networks, non-3GPP access (such as Wireless Fidelity, fixed broadband, and enterprise campus access) requires access to the core network via an evolved packet data gateway (ePDG). The non-3GPP access process includes: the user equipment (UE) selects the ePDG, and the ePDG selects the public data network gateway (PDN GW). The PDN GW includes a control plane PGW-C and a user plane PGW-U. The PGW-C corresponds to the session management function (SMF) network element, and the PGW-U corresponds to the user plane function (UPF) network element.

[0003] When a UE accesses the network via an ePDG and a PDG GW (PGW-U or UPF network element), it relies on the interaction between the ePDG and the PDN GW to establish a GPRS tunneling protocol-user plane (GTP-U) tunnel between the ePDG and the PGW-U (or UPF network element). During packet forwarding, the packet needs to undergo two protocol processing steps (ePDG and UPF network element or PGW-U), and two tunnel encapsulation and decapsulation steps, resulting in significant transmission delay. Summary of the Invention

[0004] This application provides a communication method and apparatus that can reduce transmission latency.

[0005] Firstly, embodiments of this application provide a communication method that can be applied to the network side, such as a first network element or a communication module within the first network element, or a circuit or chip in the first network element responsible for communication functions (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip), or a logic module or software capable of implementing all or part of the functions of the first network element, or referred to as a network function (NF). Taking the application of this method to a first network element as an example, the method includes: The first network element receives a first request from the second network element, which is used to request the creation of a session. The first request includes the identifier of the second network element. The second network element is responsible for non-3GPP access and user plane data processing, and the first network element is responsible for session management. Based on the identifier of the second network element, the first network element is selected to create a session.

[0006] Among them, the network element responsible for non-3GPP access can be ePDG, and the network element responsible for user plane data processing can be user plane function network element (such as UPF network element and / or PGW-U).

[0007] Because the second network element integrates non-3GPP access functions and user plane data processing functions, the first network element directly selects the second network element to create a session after receiving a session creation request from the second network element, without needing to search for other network elements to create a session, thus reducing signaling interaction between network elements. When forwarding packets through the created session, it can avoid two protocol processing steps (ePDG and UPF network element (or PGW-U)) and two tunnel encapsulation and decapsulation steps, reducing cross-network element forwarding. The second network element processes the packets only once, thereby reducing transmission latency. Furthermore, by integrating the ePDG and user plane function network elements (such as UPF network element and / or PGW-U) into a single second network element, the number of external interfaces (S2b-U, S2b-C) is reduced, improving equipment integration and operational efficiency.

[0008] In one possible design, the non-3GPP access includes at least one of the following: secure tunnel termination, user authentication, encryption / decryption, or secure access control; the user plane data processing includes at least one of the following: user plane data forwarding, quality of service (QoS) execution, or billing statistics.

[0009] In one possible design, the first network element sends a first response to the second network element based on the identifier of the second network element. This first response is used to respond to the first request. Upon receiving the second response, the second network element establishes a session and forwards packets through this established session. Since the second network element integrates the functions of ePDG and user plane function network elements (such as UPF and / or PGW-U), packet forwarding can avoid two protocol processing steps (ePDG and UPF / PGW-U) and two tunnel encapsulation and decapsulation steps, reducing cross-network element forwarding. The second network element processes the packets only once, thereby reducing transmission latency.

[0010] In one possible design, the first request further includes at least one of the following: an identifier of the data network that the terminal device needs to access, a session identifier, or an identifier of the terminal device. A connection to the data network is established using the identifier of the data network that the terminal device needs to access; different service sessions are distinguished using the session identifier; and different terminal devices are distinguished using the identifier of the terminal device.

[0011] In one possible design, the first network element determines the session context information to be updated based on update policy information. This update policy information includes at least one of the following: transmission bandwidth, transmission delay, or QoS parameters. The session context information includes at least one of the following: the identifier of the data network that the terminal device needs to access, the session identifier, the identifier of the terminal device, or the identifier of the second network element. The first network element sends a first message to the second network element, which requests an update to the session. By requesting an update to the session uplink file information, the created session meets the requirements for transmission bandwidth, transmission delay, or QoS parameters, thereby improving communication quality and efficiency when forwarding packets through the created session.

[0012] In one possible design, the first message includes at least one of the following: a session identifier or update policy information. By indicating the session identifier, the second network element updates the session uplink file information corresponding to the session identifier. By indicating the update policy information, the created session meets the requirements of transmission bandwidth, transmission latency, or QoS parameters, thereby improving communication quality and efficiency when forwarding packets through the created session.

[0013] In one possible design, the first network element is either a network element that supports interfacing with the second network element, or a network element that supports the S2b-C interface function. By selecting either the first network element that supports interfacing with the second network element or the first network element that supports the S2b-C interface function for session creation, signaling interaction between the first and second network elements is guaranteed, avoiding session creation failures due to the first network element's inability to interface with the second network element, thereby improving the success rate of session creation. Furthermore, not all first network elements need to be upgraded to support interfacing with the second network element, reducing the impact on the existing network.

[0014] In one possible design, the second network element is a network element that integrates the functions of ePDG and user plane network elements. By integrating the functions of ePDG and user plane network elements, the number of external interfaces (S2b-U, S2b-C) is reduced, the equipment integration is improved, and the operation and maintenance efficiency is increased.

[0015] In one possible design, the communication interface between the second network element and the first network element is a first interface, which is an interface that integrates the functions of the S2b-C interface and the N4 interface. By integrating the functions of the S2b-C interface and the N4 interface, a single interface can be used to manage not only non-3GPP access but also 5G user plane, reducing the number of external interfaces, improving equipment integration, and enhancing operational efficiency.

[0016] Secondly, embodiments of this application provide a communication method that can be applied to the network side, such as a second network element or a communication module within the second network element, or a circuit or chip in the second network element responsible for communication functions (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip), or a logic module or software capable of implementing all or part of the functions of the second network element, or referred to as a network function (NF). Taking the application of this method to a second network element as an example, the method includes: The second network element determines the first network element. The second network element is responsible for non-3GPP access and user plane data processing, while the first network element is responsible for session management. The second network element sends a first request to the first network element. The first request is used to request the creation of a session. The first request includes the identifier of the second network element, which is used to indicate the selection of the second network element to create the session.

[0017] Because the second network element integrates non-3GPP access functions and user plane data processing functions, the first network element directly selects the second network element to create a session after receiving a session creation request from the second network element, without needing to search for other network elements to create a session, thus reducing signaling interaction between network elements. When forwarding packets through the created session, it can avoid two protocol processing steps (ePDG and UPF network element (or PGW-U)) and two tunnel encapsulation and decapsulation steps, reducing cross-network element forwarding. The second network element processes the packets only once, thereby reducing transmission latency. Furthermore, by integrating the ePDG and user plane function network elements (such as UPF network element and / or PGW-U) into a single second network element, the number of external interfaces (S2b-U, S2b-C) is reduced, improving equipment integration and operational efficiency.

[0018] In one possible design, the non-3GPP access includes at least one of the following: secure tunnel termination, user authentication, encryption / decryption, or secure access control; the user plane data processing includes at least one of the following: user plane data forwarding, QoS execution, or billing statistics.

[0019] In one possible design, the second network element receives a first response from the first network element, which is used to respond to the first request. This allows the second network element to establish a session after receiving the second response, and then forward packets through this established session. Since the second network element integrates the functions of ePDG and user plane function network elements (such as UPF and / or PGW-U), packet forwarding can avoid two protocol processing steps (ePDG and UPF / PGW-U) and two tunnel encapsulation and decapsulation steps, reducing cross-network element forwarding. The second network element processes the packets only once, thereby reducing transmission latency.

[0020] In one possible design, the first request further includes at least one of the following: an identifier of the data network that the terminal device needs to access, a session identifier, or an identifier of the terminal device. A connection to the data network is established using the identifier of the data network that the terminal device needs to access; different service sessions are distinguished using the session identifier; and different terminal devices are distinguished using the identifier of the terminal device.

[0021] In one possible design, the second network element sends a second request to the third network element. This second request queries for network elements that support interfacing with the second network element or support the S2b-C interface function. The second network element receives a second response from the third network element, which includes the identifier of the first network element. By querying the third network element, it is determined that the first network element supports interfacing with the second network element or supports the S2b-C interface function. The first network element then requests the creation of a session, and packet forwarding is performed through this created session. Since the second network element integrates the functions of ePDG and user plane function network elements (UPF network element and / or PGW-U), packet forwarding avoids two protocol processing steps (ePDG and UPF network element (or PGW-U)) and two tunnel encapsulation and decapsulation steps, reducing cross-network element forwarding. The second network element processes the packet only once, thereby reducing transmission latency.

[0022] In one possible design, the second request includes first indication information, which indicates that the second network element is a network element responsible for non-3GPP access and user plane data processing. By indicating that the second network element is a network element responsible for non-3GPP access and user plane data processing, the third network element can select a network element that supports interfacing with the second network element, ensuring successful session establishment. Furthermore, not all first network elements need to be upgraded to support interfacing with the second network element, reducing the impact on the existing network.

[0023] In one possible design, the second network element determines the first network element based on the identifier and configuration information of the data network that the terminal device needs to access. This configuration information includes a mapping between the data network identifier and the identifier of the session management function network element. The first network element is selected by locally querying the configuration information, ensuring that the selected first network element meets the terminal device's requirements for accessing the data network.

[0024] In one possible design, the second network element receives a third request from the terminal device. This third request requests authentication of the terminal device, and includes at least one of the following: an identifier of the data network the terminal device needs to access, or an identifier of the terminal device itself. By requesting the second network element to authenticate the terminal device, a session is created, and packet forwarding is performed through the created session.

[0025] In one possible design, the first network element is either a network element that supports interfacing with the second network element, or a network element that supports the S2b-C interface function. By selecting a first network element that supports interfacing with the second network element or supports the S2b-C interface function for session creation, signaling interaction between the first and second network elements is ensured, avoiding session creation failure due to the inability of the first network element to interface with the second network element, thus ensuring successful session creation.

[0026] In one possible design, the second network element is a network element that integrates the functions of the evolved packet data gateway (ePDG) and the user plane function network element. By integrating the functions of the ePDG and the user plane function network element, the number of external interfaces (S2b-U, S2b-C) is reduced, the device integration is improved, and the operation and maintenance efficiency is increased.

[0027] In one possible design, the communication interface between the second network element and the first network element is a first interface, which is an interface that integrates the functions of the S2b-C interface and the N4 interface. By integrating the functions of the S2b-C interface and the N4 interface, a single interface can be used to manage not only non-3GPP access but also 5G user plane, reducing the number of external interfaces, improving equipment integration, and enhancing operational efficiency.

[0028] Thirdly, embodiments of this application provide a communication method, including: The terminal device sends a third request to the second network element, which instructs the terminal device to request non-3GPP access. The second network element is responsible for non-3GPP access and user plane data processing. The second network element receives the third request, determines the first network element, and sends a first request to the first network element. The first request requests the creation of a session and includes the identifier of the second network element. The first network element is responsible for session management. The first network element receives the first request and, based on the identifier of the second network element, selects the second network element to create a session.

[0029] In one possible design, the first network element can execute the method in any of the possible designs in the first aspect above, and the second network element can execute the method in any of the possible designs in the second aspect above.

[0030] Fourthly, embodiments of this application provide a communication device, which includes one or more processors. Optionally, it also includes a memory for storing part or all of the computer programs or instructions necessary for implementing the functions involved in the first aspect. The one or more processors can execute the computer programs or instructions, and when the computer programs or instructions are executed, cause the communication device to implement the methods in any possible design or implementation of the first aspect.

[0031] In one possible design, the communication device may further include an interface circuit, through which the processor communicates with other devices or components.

[0032] In one possible design, the communication device may also include the memory.

[0033] The aforementioned communication device may be a first network element, or a communication module in the first network element, or a chip in the first network element responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module.

[0034] Fifthly, embodiments of this application provide a communication device, which includes one or more processors. Optionally, it also includes a memory for storing part or all of the computer programs or instructions necessary for implementing the functions involved in the second aspect above. The one or more processors can execute the computer programs or instructions, and when the computer programs or instructions are executed, cause the communication device to implement the methods in any possible design or implementation of the second aspect above.

[0035] In one possible design, the communication device may further include an interface circuit, wherein the processor is used to communicate with other devices or components through the interface circuit.

[0036] In one possible design, the communication device may also include the memory.

[0037] The aforementioned communication device may be a second network element, or a communication module in a second network element, or a chip in a second network element that is responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module.

[0038] In a sixth aspect, this application provides a computer-readable storage medium for storing a computer program that, when executed, causes the method described in any one of the first to second aspects to be implemented.

[0039] In a seventh aspect, this application provides a computer program product including a computer program that, when executed, causes the method described in any one of the first to second aspects to be implemented.

[0040] Eighthly, embodiments of this application provide a communication system, which includes a first network element and a second network element. The first network element is used to perform the steps in the first aspect described above, and the second network element is used to perform the steps in the second aspect described above.

[0041] In a ninth aspect, a chip or chip system is provided, the chip or chip system including at least one processor and a communication interface for communicating with external or internal devices, the processor for implementing the methods of the above aspects.

[0042] In one possible design, the chip may further include a memory storing computer programs or instructions, which the processor executes, either from the stored computer programs or instructions or derived from other programs or instructions. When the computer program or instructions are executed, the processor implements the methods described above.

[0043] In one possible design, the chip can be integrated onto the first network element or the second network element. Attached Figure Description

[0044] Figure 1 This is a schematic diagram of the architecture of a communication system; Figure 2 This is a schematic diagram of a 5G / 4G converged network system. Figure 3 This is a schematic diagram of a non-3GPP access process; Figure 4 This is a schematic diagram of another 5G / 4G converged network system provided in the embodiments of this application; Figure 5This is a flowchart illustrating a communication method provided in an embodiment of this application; Figure 6 This is a schematic diagram of a non-3GPP access process provided in an embodiment of this application; Figure 7 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application; Figure 8 This is a schematic diagram of the structure of a network device provided in an embodiment of this application. Detailed Implementation

[0045] like Figure 1 As shown, Figure 1 This is a schematic diagram of a communication system architecture. This communication system is based on the current 5G 3rd Generation Partnership Project (3GPP) system architecture. The network functions and entities included in this communication system mainly include: terminal equipment (e.g., user equipment (UE)), radio access network ((R)AN) equipment, user plane function (UPF) network elements, data network (DN) network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, policy control function (PCF) network elements, application function (AF) network elements, authentication server function (AUSF) network elements, unified data management (UDM) network elements, and network slice selection function (NSSF) network elements (not shown). The diagram illustrates the interaction relationships between network functions and entities, as well as their corresponding interfaces. For example, the UE and AMF network elements can interact through the N1 interface, and the interaction messages are called N1 Messages. Some interfaces are implemented using a service-oriented approach.

[0046] The UE, (R)AN device, UPF network element, and DN network element are generally referred to as data plane network functions and entities. User data traffic can be transmitted through the protocol data unit session (PDU) established between the UE and the DN network element, and the transmission passes through the (R)AN and UPF network function entities. The remaining parts are referred to as control plane network functions and entities, which are mainly responsible for authentication and authorization, registration management, session management, mobility management, and policy control, thereby achieving reliable and stable transmission of user layer traffic. The user plane is used to carry service data, while the control plane is used to carry signaling messages.

[0047] The following describes the functions of the main entities or network elements included in the communication system: Terminal devices can be UEs (User Equipment), handheld terminals, laptops, cellular phones, smartphones, tablets, augmented reality (AR) devices, virtual reality (VR) devices, machine-type communication terminals, or other devices capable of accessing the network. Terminal devices communicate with access network devices using some air interface technology (such as New Radio (NR) or Long Term Evolution (LTE)). Terminal devices can also communicate with each other using some air interface technology (such as NR or LTE). In vehicle-to-everything (V2X) communication, the communication terminal mounted on the vehicle is a type of terminal device, and the roadside unit (RSU) can also be considered a terminal device. Unmanned aerial vehicles (UAVs) carrying communication terminals can also be considered a type of terminal device.

[0048] RAN equipment: Primarily responsible for functions such as radio resource management, quality of service management, data compression, and encryption on the air interface side. The access network equipment can include various types of base stations, such as macro base stations, micro base stations, relay stations, and access points. In systems employing different radio access technologies, the names of equipment with base station functions may differ; for example, in 5G systems, it is called a next-generation node B (gNB).

[0049] AMF network elements are core network elements primarily responsible for signaling processing, such as access control, mobility management, attach and detach, and gateway selection. When an AMF network element provides services to a session in a terminal device, it provides control plane storage resources for that session to store the session identifier and the SMF network element identifier associated with the session identifier.

[0050] SMF network elements are responsible for user plane network element selection, user plane network element redirection, Internet Protocol (IP) address allocation, bearer establishment, modification and release, and quality of service (QoS) control.

[0051] UPF network elements are responsible for forwarding and receiving user data in terminal devices. They can receive user data from the data network and transmit it to the terminal device through the access network equipment; UPF network elements can also receive user data from the terminal device through the access network equipment and forward it to the data network. The transmission resources and scheduling functions that provide services to the terminal device in the UPF network element are managed and controlled by the SMF network element.

[0052] NEF network elements primarily support secure interaction between 3GPP networks and third-party applications.

[0053] AF network element: mainly supports interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing some third-party services to the network side.

[0054] PCF network element: Responsible for policy control decisions, providing policy rules for control plane functions, and traffic-based billing control functions.

[0055] NSSF network element: mainly responsible for network slice selection, determining the network slice instance that the UE is allowed to access based on the UE's slice selection auxiliary information, subscription information, etc.

[0056] UDM network element: mainly responsible for the management of UE subscription data, including the storage and management of UE identifiers, UE access authorization, etc.

[0057] AUSF network element: Supports 3GPP and non-3GPP access authentication.

[0058] Network repository function (NRF) network element: supports the registration and discovery of network functions.

[0059] User data records (UDR) network element: Stores and retrieves subscription data used by UDM and PCF.

[0060] Network data analytics function (NWDAF) network element: supports collecting data from other network functions and AFs; supports collecting data from operation administration and maintenance (OAM); supports providing analytical information to other network functions and AFs.

[0061] The communication system described in this application may include, but is not limited to, communication systems using various radio access technologies (RATs), such as: General Packet Radio Service (GPRS), Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, 5G systems, 5G / 4G converged network systems, or New Radio (NR), or future communication systems or other similar communication systems, or Ultra Wide Band (UWB) systems, or Wireless Fidelity (WiFi) systems, etc. The network architecture and service scenarios described in this application are for the purpose of more clearly illustrating the technical solutions of this application and do not constitute a limitation on the technical solutions provided in this application. Those skilled in the art will understand that, with the evolution of communication network architectures and the emergence of new service scenarios, the technical solutions provided in this application are equally applicable to similar technical problems.

[0062] like Figure 2 As shown, Figure 2 This is a schematic diagram of a 5G / 4G converged network system. The system includes a UE, ePDG, authentication, authorization and accounting (AAA) server, home subscriber server (HSS) / unified data management (UDM), SMF / PGW-C, and UPF / PGW-U. In 4G, PGW-C and PGW-U are collectively referred to as the PDG GW. In 5G, the control plane and user plane functions are separated, with PGW-C corresponding to SMF and PGW-U corresponding to UPF. The interface between ePDG and SMF / PGW-C is an S2b-C interface, the interface between ePDG and UPF / PGW-U is an S2b-U interface, and the interface between SMF / PGW-C and UPF / PGW-U is an N4 interface.

[0063] In 5G / 4G converged networks, non-3GPP access (such as Wi-Fi, fixed broadband, and enterprise campus access) needs to access the core network through ePDG. ePDG primarily performs functions such as IP layer security protocol (IPSec) / datagram transport layer security (DTLS) tunnel termination, user authentication, encryption / decryption, and secure access control. After user plane packets are processed by ePDG, they need to be forwarded to UPF network elements for user plane forwarding, quality of service (QoS) enforcement, and billing statistics.

[0064] like Figure 3 As shown, Figure 3 This is a schematic diagram of a non-3GPP access process. In a scenario where the ePDG and PDG GW are separated, the UE selects the ePDG, and the ePDG selects the PDN GW. The path for non-3GPP access to the data network is UE-ePDG-PDG GW, which mainly includes: Step A: Authorization and Authentication. The UE configures the ePDG's Internet Protocol (IP) address and establishes an Internet Key Exchange (IKE) connection with the ePDG to negotiate encryption algorithms, authentication algorithms, key exchange parameters, etc. Step B: Create Session Request. The ePDG selects the PDN GW (PGW-C). Since PGW-C and PGW-U are merged into the PDN GW, the step of selecting PGW-U from PGW-C is omitted. In the 5G network architecture, the corresponding ePDG selects the SMF network element, and the SMF network element selects the UPF network element. Step E: Establish IPSec and GTP-U Tunnels. This includes: establishing an IPSec tunnel between the UE and the ePDG, and establishing a GTP-U tunnel between the ePDG and the UPF network element (or PGW-U). Steps C and D will not be described in detail.

[0065] It can be seen that the ePDG and the UPF network element (or PGW-U) are independently deployed network elements. When the UE accesses the network through the ePDG and the PDG GW (PGW-U or UPF network element), it relies on the ePDG to interact with the PDN GW. The two interact through an external interface to establish a GTP-U tunnel between the ePDG and the UPF network element (or PGW-U).

[0066] However, this solution has the following problems: First, the independent ePDG and UPF network element (or PGW-U) require two sets of hardware and virtualization resources, resulting in low equipment utilization and difficulty in lightweight deployment to edge nodes such as campuses. Second, there are many external interfaces between the ePDG and UPF network element (or PGW-U), leading to complex configuration, significant compatibility issues, difficulty in fault location, and the need for collaborative operations for upgrades and expansions, resulting in low operation and maintenance efficiency. Third, when forwarding packets, the packets need to undergo two protocol processing steps and two tunnel encapsulation and decapsulation steps between the ePDG and UPF network element (or PGW-U), introducing additional latency through cross-network element forwarding.

[0067] To address the aforementioned technical problems, the embodiments of this application provide the following solutions.

[0068] like Figure 4 As shown, Figure 4 This is a schematic diagram of another 5G / 4G converged network system provided in an embodiment of this application. The system includes a UE, an AAA server, an HSS / UDM, an SMF / PGW-C, and a converged network element. This converged network element is a network element that integrates the functions of ePDG and user plane function network elements (such as UPF network elements and / or PGW-U). It can be seen that, relative to... Figure 2 In the 5G / 4G converged network system shown, the S2b-U interface between the ePDG and the UPF network element (or PGW-U) is eliminated, and the S2b-C interface between the ePDG and the SMF network element (or PGW-C) is merged with the N4 interface. That is, there is a first interface between the ePDG and the SMF network element (or PGW-C), which is an interface that integrates the functions of the S2b-C interface and the N4 interface.

[0069] like Figure 5 As shown, Figure 5 This is a flowchart illustrating a communication method provided in an embodiment of this application. The second network element is responsible for non-3GPP access and user plane data processing. For example, the second network element can be a network element that integrates ePDG functionality and user plane function network elements (such as UPF network elements and / or PGW-U). The first network element is responsible for session management. For example, the first network element can be an SMF network element (or PGW-C). Non-3GPP access includes at least one of the following: secure tunnel termination, user authentication, encryption / decryption, or secure access control; user plane data processing includes at least one of the following: user plane data forwarding, Quality of Service (QoS) execution, or billing statistics. The method mainly includes the following steps: S501, the terminal device sends a third request to the second network element. The third request is used to request authentication of the terminal device, or the third request is used to instruct the terminal device to request non-3GPP access.

[0070] The third request can be an IKE authentication request message. This third request, used to request authentication of the terminal device, can also be understood as: the third request is used to request IKE authentication of the terminal device's identity.

[0071] The third request includes at least one of the following: an identifier of the data network that the terminal device needs to access, or an identifier of the terminal device. For example, the identifier of the data network that the terminal device needs to access can be an access point name (APN) or a data network name (DNN), and the identifier of the terminal device can be an identity identifier of the terminal device, which is used to identify the identity of the terminal device.

[0072] Optionally, after receiving the third request, the second network element can send a fourth request to the AAA server. This fourth request requests the AAA server to authenticate the terminal device. For example, the fourth request can be a Diameter Extensible Authentication Protocol Request (DER) message, which includes at least one of the following: the identifier of the terminal device (e.g., data identity), or the identifier of the data network the terminal device needs to access (e.g., the APN subscribed to by the terminal device). After receiving the fourth request, the AAA server authenticates the terminal device based on its identifier and returns a third response to the second network element. This third response can indicate whether the authentication of the terminal device was successful. For example, the third response can be a Diameter EAPanswer (DER) message.

[0073] For example, the third response can be an authentication success message. In this case, the third response may include at least one of the following: the identifier of the terminal device, or the identifier of the data network that the terminal device needs to access. The identifier of the data network that the terminal device needs to access carried in the third response is the APN that the terminal device has subscribed to, which may be the same as the identifier of the data network that the terminal device needs to access carried in the fourth request. Alternatively, the identifier of the data network that the terminal device needs to access carried in the third response is an APN that allows the terminal device to access, which may be different from the identifier of the data network that the terminal device needs to access carried in the fourth request. Alternatively, the third response may also be an authentication failure message. In this case, the result-code attribute-value pair (result-code AVP) in the third response may carry an error code indicating that the terminal device's authentication has failed. After receiving the third response, the second network element can re-instruct the terminal device to perform authentication.

[0074] S502: If the terminal device's identity authentication is successful, the second network element determines the first network element.

[0075] In one implementation, the second network element sends a second request to the third network element. This second request queries which network elements support interfacing with the second network element or support the S2b-C interface function. Upon receiving the second request, the third network element selects a first network element that supports interfacing with the second network element or the S2b-C interface function, and then sends a second response to the second network element. Correspondingly, the second network element receives the second response from the third network element, which includes the identifier of the first network element. This implementation is suitable for large-scale network scenarios.

[0076] Among them, the third network element can be a network repository function (NRF) network element, which supports the registration, discovery and service management of network functions.

[0077] Optionally, the second request includes first indication information, which indicates that the second network element is a network element responsible for non-3GPP access and user plane data processing. The third network element can select a first network element that supports interfacing with the second network element or using the S2b-C interface, based on the first indication information.

[0078] In another implementation, the second network element determines the first network element based on the identifier and configuration information of the data network that the terminal device needs to access. The configuration information includes a mapping between the data network identifier and the identifier of the session management function network element; this configuration information can be pre-configured locally or agreed upon by a protocol. The identifier of the session management function network element can be its IP address.

[0079] Furthermore, the second network element can search the configuration information for the identifier of the session management function network element corresponding to the identifier of the data network that the terminal device needs to access. If multiple session management function network elements are found, one of them that supports interfacing with the second network element or the S2b-C interface function can be selected as the first network element. This implementation method is suitable for recessed box solutions, such as user equipment gateways (UEGs).

[0080] S503, the second network element sends a first request to the first network element. The first request is used to request the creation of a session and includes the identifier of the second network element.

[0081] Optionally, the first request may also include at least one of the following: an identifier of the data network the terminal device needs to access, a session identifier (e.g., session ID), or an identifier of the terminal device. The identifier of the data network the terminal device needs to access is used to establish a connection with the data network. The session identifier is used to distinguish different service sessions. The identifier of the terminal device can be used to distinguish different terminal devices.

[0082] Optionally, the second network element creates session context information, which includes session identifiers and data forwarding rules, etc.

[0083] S504: The first network element selects the second network element to create a session based on the identifier of the second network element.

[0084] The session can be a non-3GPP session.

[0085] In one implementation, the second network element first creates session context information locally, and then sends a first request to the first network element. This first request carries some session context information (such as a session identifier). Correspondingly, after receiving the first request, the first network element saves the session context information and sends a first response to the second network element. This first response is used to respond to the first request, and the first response can create a response message for the session.

[0086] The session context information includes at least one of the following: the identifier of the data network that the terminal device needs to access, the session identifier, the identifier of the terminal device, or the identifier of the second network element.

[0087] In another implementation, the first request in S503 does not carry session context information. After receiving the first request from the second network element, the first network element creates session context information and sends a first response to the second network element. This first response may include the session context information. Correspondingly, after receiving the first response, the second network element retains the session context information. This session context information includes a session identifier and data forwarding rules, etc. The first response can be a session creation response message or a session creation request message. It should be understood that if the first response is a session creation request message, the second network element may also need to send a session creation response message to the first network element, as not shown in the attached diagram.

[0088] Optionally, the first network element may send a first response to the second network element based on the second network element's identifier. This first response may include a session identifier. Correspondingly, the second network element receives the first response and creates a non-3GPP session corresponding to the session identifier, then forwards packets through the created non-3GPP session.

[0089] Optionally, the first network element determines the session context information to be updated based on the update policy information, which includes at least one of the following: transmission bandwidth, transmission delay, or QoS parameters; then, based on the identifier of the second network element, it sends a first message to the second network element, which requests a session update. The first message includes at least one of the following: session identifier or update policy information. Correspondingly, the second network element receives the first message, updates the session context information, and then sends a fourth response to the second network element. The fourth response is used to respond to the first message and can indicate that the session context information update was successful. For example, the fourth response can be a session update response message.

[0090] In this embodiment, since the second network element integrates non-3GPP access functions and user plane data processing functions, the first network element directly selects the second network element to create a session after receiving the session creation request from the second network element, without needing to search for other network elements to create a session, thus reducing signaling interaction between network elements. When forwarding packets through the created session, it can avoid two protocol processing steps (ePDG and UPF network element (or PGW-U)) and two tunnel encapsulation and decapsulation steps, reducing cross-network element forwarding. The second network element processes the packets only once, thereby reducing transmission latency. Furthermore, by integrating the ePDG and user plane function network elements (such as UPF network element and / or PGW-U) into a single second network element, the number of external interfaces (S2b-U, S2b-C) is reduced, improving equipment integration and operational efficiency.

[0091] The following uses the terminal device as UE, the first network element as SMF network element, and the second network element as converged network element. This converged network element is a network element that integrates the functions of ePDG and user plane functions (such as UPF network element and / or PGW-U). Figure 5 The content shown will be described in detail.

[0092] like Figure 6 As shown, Figure 6 This is a schematic diagram of a non-3GPP access process provided in an embodiment of this application. The non-3GPP access mainly includes the following steps: S601, UE configures the address or fully qualified domain name (FQDN) of the converged network element.

[0093] Optionally, the UE obtains the address of the converged network element, where the address of the converged network element can be its IP address. One implementation is that the UE can directly obtain the configured address of the converged network element. Another implementation is that the UE can obtain the configured FQDN and then query the Domain Name System (DNS) server for the corresponding converged network element address based on the configured FQDN.

[0094] S602, the UE sends an IKE initialization request to the converged network element.

[0095] Specifically, the UE can send an IKE initialization request to the converged network element based on the IP address of the converged network element. This IKE initialization request is used to request the establishment of an IKE connection with the converged network element.

[0096] S603, the converged network element sends an IKE initialization response to the UE.

[0097] The IKE initialization response can be used to respond to the IKE initialization request.

[0098] Optionally, after receiving the IKE initialization request, the converged network element establishes an IKE connection with the UE. After establishing the IKE connection, the converged network element can negotiate encryption algorithms, authentication algorithms, key exchange parameters, etc. with the UE.

[0099] It should be noted that the signaling interaction between the UE and the converged network element in S602 and S603 is transmitted in plaintext. After the IKE connection is established, a secure channel is established between the UE and the converged network element. The subsequent signaling interaction between the UE and the converged network element is completed through this secure channel. That is, the subsequent signaling between the UE and the converged network element is encrypted using negotiated encryption algorithms, authentication algorithms, or key exchange parameters.

[0100] S604, the UE sends an IKE authentication request message to the converged network element.

[0101] The IKE authentication request message is used to request IKE authentication of the UE's identity, or to instruct the terminal device to request non-3GPP access. The IKE authentication request message includes at least one of the following: the identifier of the data network the UE needs to access, or the UE's identifier. For example, the identifier of the data network the UE needs to access can be an APN or a DNN, and the UE's identifier can be the UE's identity identifier, which is used to identify the UE's identity.

[0102] S605, the converged network element sends a fourth request to the AAA server.

[0103] The fourth request is used to request the AAA server to authenticate the UE. For example, the fourth request can be a Diameter Extensible Authentication Protocol Request (DER) message, which includes at least one of the following: the UE's identifier (e.g., data identity) or the identifier of the data network that the UE needs to access (e.g., the APN that the UE has signed up for).

[0104] S606, the AAA server verifies user information from the UDM network element.

[0105] Specifically, UDM network elements can authenticate the UE based on the UE's identifier. This further includes determining whether the UE's identity is legitimate and whether the UE has access permissions, among other things.

[0106] S607, the AAA server sends a third response to the converged network element.

[0107] The third response can be used to indicate whether the UE's authentication was successful. For example, the third response can be a Diameter EAP Answer (DER) message.

[0108] The specific implementation methods of S604-S607 are the same as those of S501 in the above embodiments. The specific implementation methods of S604-S607 can refer to the steps of S501 in the above embodiments, and will not be repeated here.

[0109] S608, the converged network element sends a second request to the NRF network element.

[0110] The second request is used to query network elements that support interfacing with converged network elements or SMF network elements that support the S2b-C interface function.

[0111] Optionally, the second request includes first indication information, which indicates that the converged network element is a network element responsible for non-3GPP access and user plane data processing. The NRF network element can select an SMF network element that supports interfacing with the converged network element or an S2b-C interface based on the first indication information.

[0112] S609, the NRF network element sends a second response to the converged network element.

[0113] The second response includes the identifier of the SMF network element. The identifier of the SMF network element can be its IP address. This SMF network element is an SMF network element that the NRF network element finds that supports interfacing with the converged network element, or an SMF network element that supports the S2b-C interface function.

[0114] S610, the converged network element sends the first request to the SMF network element.

[0115] The first request is used to request the creation of a session, and the first request includes the identifier of the converged network element.

[0116] Optionally, the first request may also include at least one of the following: the identifier of the data network that the UE needs to access, the session identifier (e.g., session ID), or the UE's identifier.

[0117] S611, SMF network elements select a converged network element to create a session based on the identifier of the converged network element.

[0118] The session can be a non-3GPP session.

[0119] Optionally, the SMF network element stores session context information, which includes at least one of the following: the identifier of the data network that the UE needs to access, the session identifier, the UE's identifier, or the identifier of the converged network element.

[0120] S612, the SMF network element sends the first response to the converged network element.

[0121] Specifically, the SMF network element can send a first response to the converged network element based on the identifier of the converged network element. This first response is used to respond to the first request. For example, the first response can be a session creation response, which may include a session identifier. Accordingly, the converged network element receives the first response, creates a non-3GPP session, and forwards packets through the created non-3GPP session.

[0122] The specific implementation methods of S610-S612 can be referred to the specific implementation methods of S503 and S504 mentioned above, and will not be repeated here.

[0123] S613, the SMF network element sends the first message to the converged network element.

[0124] The first message is used to request a session update. This first message may include at least one of the following: a session identifier or update policy information.

[0125] Specifically, the SMF network element can determine the update session context information based on update policy information, which includes at least one of the following: transmission bandwidth, transmission delay, or QoS parameters; then, the SMF network element sends a first message to the converged network element based on the identifier of the converged network element. Correspondingly, the converged network element receives the first message and updates the session context information.

[0126] S614, the converged network element sends the fourth response to the SMF network element.

[0127] The fourth response is used in response to the first message, and can be used to indicate that the session context information has been successfully updated. For example, the fourth response can be an update session response message.

[0128] S615, the converged network element sends an IKE authentication response message to the UE.

[0129] Specifically, after the converged network element completes the session creation, it sends an IKE authentication response (IKE_AUTH answer) message to the UE, which indicates that IKE authentication has passed.

[0130] It should be noted that in all the above embodiments, the first network element (e.g., SMF network element) and the second network element (e.g., converged network element) can perform some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application can also perform other operations or variations of various operations. Furthermore, the steps can be performed in different orders as presented in each embodiment, and it is not necessary to perform all the operations in the embodiments of this application. Moreover, the sequence number of each step does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0131] It is understood that in the above-described method embodiments, the methods and operations implemented by the first network element can also be implemented by components (such as chips or circuits) that can be used in the first network element, and the methods and operations implemented by the second network element can also be implemented by components (such as chips or circuits) that can be used in the second network element.

[0132] This application embodiment can divide the first network element or the second network element into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or software functional modules. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The following description uses the division of functional modules according to each function as an example.

[0133] The above, combined with Figures 5-6 The methods provided in the embodiments of this application are described in detail below. Figure 7 This application provides a detailed description of the communication device provided in its embodiments. It should be understood that the descriptions of the device embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail here will be referred to the method embodiments above, and for the sake of brevity, will not be repeated here.

[0134] Please see Figure 7 , Figure 7 This is a schematic diagram of a communication device provided in an embodiment of this application. The communication device can implement the steps or processes executed by the first network element or the second network element corresponding to the method embodiment described above. In one possible design, the communication device may include a receiving module 701, a processing module 702, and a transmitting module 703. Optionally, the communication device may further include a storage module for storing device program code and / or data.

[0135] The communication device can be a network-side device as described in the above embodiments, such as a first network element or a communication module within the first network element, or a circuit or chip within the first network element responsible for communication functions. Alternatively, it can be a second network element or a communication module within the second network element, or a circuit or chip within the second network element responsible for communication functions.

[0136] In one embodiment: The receiving module 701 is used to receive a first request from a second network element. The first request is used to request the creation of a session. The first request includes the identifier of the second network element. The second network element is used to be responsible for non-3GPP access and user plane data processing, and the first network element is used to be responsible for session management. Processing module 702 is used to select the second network element to create a session based on the identifier of the second network element.

[0137] Optionally, the non-3GPP access includes at least one of the following: secure tunnel termination, user authentication, encryption / decryption, or secure access control; the user plane data processing includes at least one of the following: user plane data forwarding, QoS execution, or billing statistics.

[0138] Optionally, the sending module 703 is used to send a first response to the second network element based on the identifier of the second network element, wherein the first response is used to respond to the first request.

[0139] Optionally, the processing module 702 is used to determine update session context information based on update policy information, wherein the update policy information includes at least one of the following: transmission bandwidth, transmission delay, or QoS parameters, and the session context information includes at least one of the following: the identifier of the data network that the terminal device needs to access, the session identifier, the identifier of the terminal device, or the identifier of the second network element; the sending module 703 is used to send a first message to the second network element, wherein the first message is used to request an update session.

[0140] Optionally, the first message includes at least one of the following: the session identifier, or the update policy information.

[0141] Optionally, the first network element is a network element that supports interfacing with the second network element, or the first network element is a network element that supports the S2b-C interface function.

[0142] Optionally, the second network element is a network element that integrates the functions of the evolved packet data gateway (ePDG) and the user plane function network element.

[0143] Optionally, the communication interface between the second network element and the first network element is a first interface, which is an interface that integrates the S2b-C interface function and the N4 interface function.

[0144] In one possible design, when the communication device is a first network element or a communication module within a first network element, the functions of the receiving module 701 and the transmitting module 703 can be implemented by a transceiver circuit. The function of the processing module 702 can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) chip or a SIP chip containing a modem core.

[0145] In one possible design, when the communication device is a circuit or chip responsible for communication functions in the first network element, such as a modem chip or a system-on-a-chip (SoC) or SIP chip containing a modem core, the functions of the receiving module 701 and the transmitting module 703 can be implemented by the interface circuit or data transceiver circuit on the aforementioned chip. The function of the processing module 702 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores.

[0146] In another embodiment: Processing module 702 is used to determine the first network element, the second network element is used to be responsible for non-3GPP access and user plane data processing, and the first network element is used to be responsible for session management; The sending module 703 is used to send a first request to the first network element. The first request is used to request the creation of a session. The first request includes the identifier of the second network element, which is used to indicate the selection of the second network element to create a session.

[0147] Optionally, the non-3GPP access includes at least one of the following: secure tunnel termination, user authentication, encryption / decryption, or secure access control; the user plane data processing includes at least one of the following: user plane data forwarding, QoS execution, or billing statistics.

[0148] Optionally, the receiving module 701 is configured to receive a first response from the first network element, the first response being used to respond to the first request.

[0149] Optionally, the first request may further include at least one of the following: an identifier of the data network that the terminal device needs to access, a session identifier, or an identifier of the terminal device.

[0150] Optionally, the sending module 703 is used to send a second request to the third network element, the second request being used to request a query for a network element that supports interfacing with the second network element or a network element that supports the S2b-C interface function; the receiving module 701 is used to receive a second response from the third network element, the second response including the identifier of the first network element.

[0151] Optionally, the second request includes first indication information, which indicates that the second network element is a network element responsible for non-3GPP access and user plane data processing.

[0152] Optionally, the processing module 702 is used to determine the first network element based on the identifier and configuration information of the data network that the terminal device needs to access, wherein the configuration information includes the mapping relationship between the identifier of the data network and the identifier of the session management function network element.

[0153] Optionally, the receiving module 701 is configured to receive a third request from the terminal device, the third request being used to request authentication of the terminal device, wherein the third request includes at least one of the following: the identifier of the data network that the terminal device needs to access, or the identifier of the terminal device.

[0154] Optionally, the first network element is a network element that supports interfacing with the second network element, or the first network element is a network element that supports the S2b-C interface function.

[0155] Optionally, the second network element is a network element that integrates the functions of the evolved packet data gateway (ePDG) and the user plane function network element.

[0156] Optionally, the communication interface between the second network element and the first network element is a first interface, which is an interface that integrates the S2b-C interface function and the N4 interface function.

[0157] In one possible design, when the communication device is a second network element or a communication module within a second network element, the functions of the receiving module 701 and the transmitting module 703 can be implemented by a transceiver circuit. The function of the processing module 702 can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) chip or a SIP chip containing a modem core.

[0158] In one possible design, when the communication device is a circuit or chip responsible for communication functions in a second network element, such as a modem chip or a system-on-a-chip (SoC) or SIP chip containing a modem core, the functions of the receiving module 701 and the transmitting module 703 can be implemented by the interface circuit or data transceiver circuit on the aforementioned chip. The function of the processing module 702 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores.

[0159] It should be noted that the implementation of each module can also be referenced accordingly. Figures 5-6 The corresponding description of the method embodiment shown above executes the methods and functions performed by the first network element or the second network element in the above embodiments.

[0160] Figure 8 This is a schematic diagram of the structure of a network device provided in an embodiment of this application. This network device can be applied to, for example... Figure 1 or Figure 4 In the system shown, the functions of the first network element or the second network element in the above method embodiments are executed, or the steps or processes executed by the first network element or the second network element in the above method embodiments are implemented.

[0161] like Figure 8As shown, the network device includes a processor 801 and a transceiver 802. The transceiver 802 includes a transmitter 821, a receiver 822, and an antenna 823. The receiver 822 can be used to receive transmission control information through the antenna 823, and the transmitter 821 can be used to send transmission feedback information to a second network element through the antenna 823. Optionally, the network device also includes a memory 803. The processor 801, transceiver 802, and memory 803 can communicate with each other through internal connection paths to transmit control and / or data signals. The memory 803 stores computer programs, and the processor 801 calls and runs the computer programs from the memory 803 to control the transceiver 802 to transmit and receive signals. Optionally, the network device may also include an antenna for transmitting uplink data or uplink control signaling output by the transceiver 802 via wireless signals.

[0162] The aforementioned processor 801 can be with Figure 7 Corresponding to the processing module, the processor 801 and the memory 803 can be integrated into a single processing device. The processor 801 executes the program code stored in the memory 803 to achieve the aforementioned functions. In specific implementations, the memory 803 can be integrated into the processor 801 or independent of the processor 801.

[0163] The transceiver 802 described above can be used with Figure 7 The receiving module and transmitting module in the transceiver unit correspond to each other and can also be called a transceiver unit or transceiver module. The transceiver 802 may include a receiver (or receiver circuit) and a transmitter (or transmitter circuit). The receiver is used to receive signals, and the transmitter is used to transmit signals.

[0164] It should be understood that Figure 8 The network device shown can achieve Figures 5-6 The methods illustrated in the embodiments involve various processes related to the first or second network element. The operations and / or functions of each module in the network device are respectively for implementing the corresponding processes in the above method embodiments. For details, please refer to the descriptions in the above method embodiments; to avoid repetition, detailed descriptions are appropriately omitted here.

[0165] The processor 801 described above can be used to execute the actions implemented internally by the first network element or the second network element as described in the preceding method embodiments, while the transceiver 802 can be used to execute the transmission or reception actions of the first network element or the second network element as described in the preceding method embodiments. Please refer to the descriptions in the preceding method embodiments for details, which will not be repeated here.

[0166] The processor 801 can be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor 801 can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, etc. The network device may also include a communication bus, which can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. The communication bus is used to realize the connection and communication between these components. In this embodiment, the transceiver 802 is used for signaling or data communication with other node devices. The memory 803 may include volatile memory, such as nonvolatile random access memory (NVRAM), phase change RAM (PRAM), magnetoresistive RAM (MRAM), etc., and may also include non-volatile memory, such as at least one disk storage device, electrically erasable programmable read-only memory (EEPROM), flash memory devices, such as NOR flash memory or NAND flash memory, semiconductor devices, such as solid-state disks (SSDs), etc. Optionally, the memory 803 may also be at least one storage device located remotely from the aforementioned processor 801. Optionally, the memory 803 may also store a set of computer program code or configuration information. Optionally, the processor 801 may also execute the program stored in the memory 803. The processor can cooperate with the memory and transceiver to execute any of the methods and functions of the network device in the above-described embodiments.

[0167] This application also provides a chip system including a processor for supporting a first network element or a second network element to implement the functions involved in any of the above embodiments, such as generating or processing the first request involved in the above methods.

[0168] In one possible design, the chip system may further include a memory for storing necessary computer programs and data for the first or second network element. The chip system may be composed of chips or may include chips and other discrete devices. The inputs and outputs of the chip system correspond to the receiving and transmitting operations of the first or second network element in the method embodiment, respectively.

[0169] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: a computer program that, when run on a computer, causes the computer to perform... Figures 5-6 The method of any one of the embodiments shown.

[0170] According to the method provided in the embodiments of this application, this application also provides a computer-readable medium storing a computer program, which, when run on a computer, causes the computer to perform... Figures 5-6 The method of any one of the embodiments shown.

[0171] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

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

Claims

1. A communication method, characterized in that, The method includes: The first network element receives a first request from the second network element. The first request is used to request the creation of a session. The first request includes the identifier of the second network element. The second network element is responsible for non-3GPP access and user plane data processing. The first network element is responsible for session management. The first network element selects the second network element to create a session based on the identifier of the second network element.

2. The method as described in claim 1, characterized in that, The non-3GPP access includes at least one of the following: secure tunnel termination, user authentication, encryption / decryption, or secure access control; the user plane data processing includes at least one of the following: user plane data forwarding, QoS execution, or billing statistics.

3. The method as described in claim 1, characterized in that, The method further includes: The first network element sends a first response to the second network element based on the identifier of the second network element. The first response is used to respond to the first request.

4. The method as described in claim 1, characterized in that, The first request also includes at least one of the following: an identifier of the data network that the terminal device needs to access, a session identifier, or an identifier of the terminal device.

5. The method as described in claim 4, characterized in that, The method further includes: The first network element determines the update session context information based on the update policy information. The update policy information includes at least one of the following: transmission bandwidth, transmission delay, or QoS parameters. The session context information includes at least one of the following: the identifier of the data network that the terminal device needs to access, the session identifier, the identifier of the terminal device, or the identifier of the second network element. The first network element sends a first message to the second network element, the first message being used to request an update of the session.

6. The method as described in claim 5, characterized in that, The first message includes at least one of the following: the session identifier, or the update policy information.

7. The method according to any one of claims 1-6, characterized in that, The first network element is a network element that supports interfacing with the second network element, or the first network element is a network element that supports the S2b-C interface function.

8. The method according to any one of claims 1-6, characterized in that, The second network element is a network element that integrates the functions of the evolved packet data gateway (ePDG) and the user plane function network element.

9. The method according to any one of claims 1-6, characterized in that, The communication interface between the second network element and the first network element is the first interface, which is an interface that integrates the functions of the S2b-C interface and the N4 interface.

10. A communication method, characterized in that, The method includes: The second network element determines the first network element. The second network element is responsible for non-3GPP access and user plane data processing, while the first network element is responsible for session management. The second network element sends a first request to the first network element. The first request is used to request the creation of a session. The first request includes the identifier of the second network element, which is used to indicate the selection of the second network element to create the session.

11. The method as described in claim 10, characterized in that, The non-3GPP access includes at least one of the following: secure tunnel termination, user authentication, encryption / decryption, or secure access control; the user plane data processing includes at least one of the following: user plane data forwarding, QoS execution, or billing statistics.

12. The method as described in claim 10, characterized in that, The method further includes: The second network element receives a first response from the first network element, and the first response is used to respond to the first request.

13. The method as described in claim 10, characterized in that, The first request also includes at least one of the following: an identifier of the data network that the terminal device needs to access, a session identifier, or an identifier of the terminal device.

14. The method as described in claim 10, characterized in that, The second network element determines the first network element including: The second network element sends a second request to the third network element. The second request is used to query network elements that support interfacing with the second network element or network elements that support the S2b-C interface function. The second network element receives a second response from the third network element, the second response including the identifier of the first network element.

15. The method as described in claim 14, characterized in that, The second request includes first indication information, which indicates that the second network element is a network element responsible for non-3GPP access and user plane data processing.

16. The method as described in claim 10, characterized in that, The second network element determines the first network element including: The second network element determines the first network element based on the identifier and configuration information of the data network that the terminal device needs to access, wherein the configuration information includes the mapping relationship between the identifier of the data network and the identifier of the session management function network element.

17. The method as described in claim 10, characterized in that, Before the second network element determines the first network element, the method further includes: The second network element receives a third request from the terminal device, the third request being used to request authentication of the terminal device, wherein the third request includes at least one of the following: the identifier of the data network that the terminal device needs to access, or the identifier of the terminal device.

18. The method according to any one of claims 10-17, characterized in that, The first network element is a network element that supports interfacing with the second network element, or the first network element is a network element that supports the S2b-C interface function.

19. The method according to any one of claims 10-17, characterized in that, The second network element is a network element that integrates the functions of the evolved packet data gateway (ePDG) and the user plane function network element.

20. The method according to any one of claims 10-17, characterized in that, The communication interface between the second network element and the first network element is the first interface, which is an interface that integrates the functions of the S2b-C interface and the N4 interface.

21. A communication method, characterized in that, The method includes: The terminal device sends a third request to the second network element. The third request is used to instruct the terminal device to request non-3GPP access. The second network element is responsible for non-3GPP access and user plane data processing. The second network element receives the third request, determines the first network element, and sends a first request to the first network element. The first request is used to request the creation of a session. The first request includes the identifier of the second network element. The first network element is responsible for session management. The first network element receives the first request and selects the second network element to create a session based on the identifier of the second network element.

22. A communication device, characterized in that, It includes a memory and a processor, the memory being used to store a computer program, and the processor running the computer program to cause the communication device to perform the method of any one of claims 1-9 or any one of claims 10-20.

23. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program that, when executed by a processor, causes the method of any one of claims 1-9 or any one of claims 10-20 to be implemented.

24. A chip, characterized in that, The chip includes a processor and a communication interface, the communication interface being used to communicate with external or internal devices, and the processor being used to implement the method as claimed in any one of claims 1-9 or any one of claims 10-20.

25. A computer program product comprising a computer program, characterized in that, When the computer program is executed, it causes the computer to perform the method of any one of claims 1-9 or any one of claims 10-20.

Images