Registration method, packet data gateway, terminal device, and storage medium

Abstract

Disclosed in the present application are a registration method, a packet data gateway, a terminal device, and a storage medium. The registration method is applied to a packet data gateway (PDG). The method comprises: establishing a control plane connection with a terminal device on the basis of a Quick User-Datagram-Protocol Internet Connections (QUIC)-based control plane protocol; receiving a registration request message which is sent by the terminal device on the basis of the control plane connection, wherein the registration request message comprises identification information and a registration parameter of the terminal device; sending an authentication request message to a core network device on the basis of the identification information and the registration parameter of the terminal device; and receiving an authentication authorization message sent by the core network device, and sending a registration response message to the terminal device on the basis of the authentication authorization message.

Description

Registration method, packet data gateway, terminal device and storage medium TECHNICAL FIELD

[0001] The present application relates to the field of communication technology, for example to a registration method, a packet data gateway, a terminal device and a storage medium. BACKGROUND

[0002] The 3rd Generation Partnership Project (3GPP) 5th-generation (5G) standard is more complex for the design of terminal devices from non-3GPP access networks: in order to take into account the fusion of the second version of the Internet Key Exchange (IKEv2) fixed process and the 3GPP access Non-Access Stratum (NAS) registration, two sets of control plane protocol stacks are needed and tunnel mode is used to implement, resulting in the Non-3GPP InterWorking Function (N3IWF) needing to allocate an Internet Protocol (IP) address for the NAS in addition, causing the problem of complex implementation and large protocol overhead. In addition, in order to ensure the reliability of transmission, a Transmission Control Protocol (TCP) connection is needed, and each control plane connection needs to allocate a TCP port number, which will result in a large maintenance overhead for the TCP connection on the N3IWF. Moreover, the user plane protocol also adopts Internet Protocol Security (IPSec) tunnel mode, which also has similar problems as the control plane. SUMMARY

[0003] The embodiments of the present application provide a registration method applied to a packet data gateway (PDG), comprising: establishing a control plane connection with a terminal device according to a control plane protocol based on a Quick User Datagram Protocol Network Connection (QUIC); receiving a registration request message sent by the terminal device based on the control plane connection, the registration request message comprising identification information and registration parameters of the terminal device; sending an authentication request message to a core network device according to the identification information and the registration parameters of the terminal device; and receiving an authentication and authorization message sent by the core network device, and sending a registration response message to the terminal device according to the authentication and authorization message.

[0004] The embodiment of the present application provides a registration method, which is applied to a terminal device and includes the following steps: establishing a control plane connection with a packet data gateway (PDG) based on a quick user datagram protocol network connection (QUIC) control plane protocol; sending a registration request message to the PDG based on the control plane connection, wherein the registration request message comprises identification information and registration parameters of the terminal device; and receiving a registration response message sent by the PDG.

[0005] The embodiment of the present application provides a packet data gateway, which includes a processor.

[0006] The embodiment of the present application provides a terminal device, which includes a processor.

[0007] The embodiment of the present application further provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the registration method of any of the above embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0008] Fig. 1 is a control plane protocol stack;

[0009] Fig. 2 is another control plane protocol stack;

[0010] Fig. 3 is a user plane protocol stack;

[0011] Fig. 4 is a networking schematic diagram of a wireless communication system provided by an embodiment;

[0012] Fig. 5 is a flowchart of a registration method provided by an embodiment;

[0013] Fig. 6 is a flowchart of another registration method provided by an embodiment;

[0014] Fig. 7 is a control plane protocol stack based on QUIC provided by Example 1;

[0015] Fig. 8 is a user plane protocol stack based on QUIC provided by Example 1;

[0016] Fig. 9 is an interaction flowchart of a registration method provided by Example 1;

[0017] Fig. 10 is a control plane protocol stack based on QUIC provided by Example 2;

[0018] Fig. 11 is a user plane protocol stack based on QUIC provided by Example 2;

[0019] Fig. 12 is an interaction flowchart of a registration method provided by Example 2;

[0020] FIG. 13 is a schematic diagram of switching of a UE from an access network 1 to an access network 2 according to Example 3;

[0021] FIG. 14 is an interaction flowchart of switching of a UE from an access network 1 to an access network 2 according to Example 3;

[0022] FIG. 15 is a schematic diagram of switching of a UE from an access network 1 to an access network 2 according to Example 4;

[0023] FIG. 16 is an interaction flowchart of switching of a UE from an access network 1 to an access network 2 according to Example 4;

[0024] FIG. 17 is a schematic diagram of a structure of a registration apparatus according to an embodiment;

[0025] FIG. 18 is a schematic diagram of a structure of another registration apparatus according to an embodiment;

[0026] FIG. 19 is a schematic diagram of a structure of a packet data gateway according to an embodiment;

[0027] FIG. 20 is a schematic diagram of a structure of a UE according to an embodiment. DETAILED DESCRIPTION

[0028] In order to take into account the fusion of the IKEv2 fixed flow and the 3GPP access NAS registration, the registration flow of a user equipment (UE) from a non-3GPP access to a network needs to use two sets of control plane protocol stacks and a tunnel mode to implement. FIG. 1 is one control plane protocol stack, and FIG. 2 is another control plane protocol stack, which causes the N3IWF to additionally allocate an IP address for the NAS, resulting in the problems of complex implementation and large protocol overhead. Moreover, the user plane protocol also adopts an IPSec tunnel mode, and FIG. 3 is one user plane protocol stack, which also has similar problems as the control plane.

[0029] The registration method provided in this application can be applied to various wireless communication systems, such as a long term evolution (LTE) system, a 4th-generation (4G) system, a 5G system, a mixed architecture system of LTE and 5G, a new radio (NR) system, and a new communication system to be generated in future communication development, such as a 6th-Generation mobile communication (6G) system. FIG. 4 is a networking schematic diagram of a wireless communication system according to an embodiment. As shown in FIG. 4, the wireless communication system includes a terminal device 110, a packet data gateway (PDG) 120, and a core network device 130.

[0030] The terminal device 110 can be a device with wireless transceiving function, which can be deployed on land, water surface or in the air. Examples of some terminal devices 110 include: a wireless terminal, a UE, a mobile phone, a mobile station, a tablet computer, a notebook computer, an ultra-mobile personal computer (UMPC), a handheld computer, a netbook, a personal digital assistant (PDA) and other network-enabled user equipment, or a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical treatment, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, or an Internet of Things (IoT) node in Internet of Things, or a vehicle communication device in vehicle networking, or an entertainment, game device or system, or a global positioning system device, etc. Embodiments of the present application do not limit the specific technology and specific device form of the terminal device, and in addition, the terminal device can be referred to as a terminal. The PDG 120 is an access device through which the terminal device 110 accesses the wireless communication system wirelessly. The core network device 130 can include an access and mobility management network element and a session management network element. Exemplarily, the terminal device 110 can access the core network through the PDG 120 to realize data transmission.

[0031] The registration method, the packet data gateway, the terminal device and the storage medium provided by the present application can simplify the process of the terminal device accessing from the non-3GPP access network, reduce the overhead, and have important significance for improving the network reliability and robustness.

[0032] In the following, the registration method, the packet data gateway, the terminal device and the technical effects thereof are described.

[0033] For ease of description, the explanations of technical terms in the present application are as follows:

[0034] Quick UDP Internet Connections (QUIC) is a new transport layer protocol that implements many TCP features on top of the User Datagram Protocol (UDP). It aims to provide low-latency and high-throughput services to improve the user experience of Hypertext Transfer Protocol (HTTP)-based internet applications and services. QUIC was initially designed to reduce webpage load times and improve security. It uses UDP instead of traditional TCP to reduce overhead and allow for faster retransmissions. The basic QUIC protocol is defined in IETF RFC 9000, and other related protocols can be found in relevant IETF RFCs such as 3GPP TS 23.402, 3GPP TS 23.501, IETF RFC 9000, IETF RFC 9001, IETF RFC 9002, and IETF RFC 9114.

[0035] QUIC has the following technical features:

[0036] (1) Fast connection establishment: QUIC uses session reuse to reduce connection establishment latency, allowing parameters from previous connections to be reused on a new connection, thereby avoiding the waiting time of the Transport Layer Security (TLS) handshake.

[0037] (2) Multiplexing: QUIC supports the parallel transmission of multiple data streams on the same connection without blocking other data streams due to the delay of one data stream, unlike TCP.

[0038] (3) Security: It has built-in encryption similar to TLS, providing end-to-end secure connections and protecting data transmission from eavesdropping and tampering.

[0039] (4) Connection migration: QUIC allows connection migration without interrupting service, such as when a user switches from one network to another.

[0040] (5) Connection ID: Each QUIC connection has a set of connection identifiers, i.e., connection IDs. Each connection ID can identify this connection. The main function of the connection ID is to ensure that when the address changes of the underlying protocol (such as UDP, IP and lower-level protocol stacks), a QUIC connection's data packets will not be transmitted to the wrong terminal.

[0041] (6) Flow control and congestion control: QUIC implements two-level flow control, not only connection-level flow control, but also stream-level flow control, to prevent the sender from overloading the network or the receiver.

[0042] Fig. 5 is a flowchart of a registration method provided in an embodiment. As shown in Fig. 5, the method provided in the embodiment is applicable to a PDG. The method includes S510-S540.

[0043] S510, establishing a control plane connection with a terminal device according to a QUIC-based control plane protocol.

[0044] In the process of accessing a non-3GPP access network, the terminal device usually first establishes a control plane connection with the PDG, and then establishes a user plane connection with the PDG. The PDG in the present application can be a conventional PDG or a new PDG capable of implementing the functions of the present application.

[0045] When establishing the control plane connection with the PDG, the QUIC-based control plane protocol is used. The QUIC-based control plane protocol can be another application layer protocol based on QUIC, or a control plane protocol of the third version of the Hypertext Transfer Protocol (HTTP / 3).

[0046] The terminal device triggers a QUIC handshake process with the PDG according to the QUIC-based control plane protocol. After the terminal device and the PDG verify the QUIC Finished message, the control plane connection is considered to be established, and the terminal device and the PDG can start exchanging control plane signaling (such as control plane protocol messages) securely.

[0047] The PDG establishes a control plane connection with the terminal device based on the QUIC-based control plane protocol. The design of QUIC enables it to provide stronger recovery capability in the face of unstable network or packet loss. The further combination of QUIC and HTTP / 3 enables the application program to load faster, especially in a mobile network environment.

[0048] In an embodiment, when the QUIC-based control plane protocol is a control plane protocol of HTTP / 3,

[0049] During the execution of S510, the PDG can also send a QUIC extension frame to the terminal device. The QUIC extension frame includes Uniform Resource Identifier (URI) information, which is used to indicate the resource location of the related services provided by the network.

[0050] S520, receiving a registration request message sent by the terminal device based on the control plane connection, the registration request message comprising identification information of the terminal device and registration parameters.

[0051] The registration request message is used to indicate that the terminal device requests to register to the core network device. In an embodiment, the registration parameters can comprise a registration type, such as initial registration, registration update, emergency registration, etc.

[0052] S530, sending an authentication request message to the core network device according to the identification information of the terminal device and the registration parameters.

[0053] S540, receiving an authentication authorization message sent by the core network device, and sending a registration response message to the terminal device according to the authentication authorization message.

[0054] The authentication request message indicates that the core network device is requested to authenticate the UE, and the authentication authorization message indicates the completion of the authentication authorization process. After the authentication authorization process is completed, the PDG sends a registration response message to the terminal device.

[0055] In an embodiment, the registration response message comprises at least one of user plane connection identification information and connection indication information, the connection indication information being used to indicate whether the terminal device performs 0-Round Trip Time (0-RTT) fast connection establishment. The registration response message can also comprise user plane Quality of Service (QoS) information.

[0056] The user plane connection identification information comprises at least one of the following: a UDP port number of the PDG, a QUIC connection identification used for the user plane connection, and encapsulation layer identification information used for encapsulating user plane packets.

[0057] After S540 is executed, the PDG can also establish a user plane connection with the terminal device based on the QUIC-based user plane protocol; receive a user plane uplink packet sent by the terminal device based on the user plane connection, and forward the user plane uplink packet to the core network device; or receive a user plane downlink packet sent by the core network device, and forward the user plane downlink packet to the terminal device based on the user plane connection.

[0058] In an embodiment, if the registration response message comprises the connection indication information and the connection indication information indicates that the terminal device performs 0-RTT fast connection establishment, the PDG can also send session recovery parameter information to the terminal device to realize fast recovery of the connection between the PDG and the terminal device. The session recovery parameter information comprises a session ticket.

[0059] Exemplarily, after the user plane connection and / or the control plane connection established by the PDG and the terminal device are released, the PDG receives a session recovery request message sent by the terminal device, the session recovery request message comprising session recovery parameter information; and according to the session recovery request message, the user plane connection and / or the control plane connection with the terminal device are recovered.

[0060] In an embodiment, when the user plane connection is established with the terminal device, the PDG can also receive switching indication information sent by the core network device, and send the switching indication information to the terminal device. The switching indication information is used to indicate whether the core network device allows the terminal device to perform connection migration.

[0061] If the switching indication information indicates that the core network device allows the terminal device to perform connection migration, the PDG receives a path challenge message sent by the terminal device; according to the path challenge message, switches the control plane connection and / or the user plane connection with the terminal device from one access network to another access network; and sends a path response message to the terminal device. Thus, the switching of the access network is realized.

[0062] FIG. 6 is a flowchart of another registration method provided in an embodiment. As shown in FIG. 6, the method provided in the embodiment is applicable to a terminal device. The method comprises S610-S630.

[0063] S610, a control plane connection is established with the PDG according to a QUIC-based control plane protocol.

[0064] In the process of the terminal device from a non-3GPP access network, the terminal device usually first establishes a control plane connection with the PDG, and then establishes a user plane connection with the PDG. When the control plane connection is established with the PDG, the QUIC-based control plane protocol is used. The QUIC-based control plane protocol can be another application layer protocol based on QUIC, or a control plane protocol of HTTP / 3.

[0065] The terminal device triggers a QUIC handshake process with the PDG according to the QUIC-based control plane protocol. When the terminal device and the PDG verify the QUIC Finished message, the control plane connection is considered to be established, and the terminal device and the PDG can start to exchange control plane signaling (such as control plane protocol messages) safely.

[0066] The control plane connection established by the terminal device and the PDG based on the QUIC-based control plane protocol. The design of QUIC enables it to provide stronger recovery capability in the face of unstable network or packet loss. The further combination of QUIC and HTTP / 3 enables the application program to load faster, especially in a mobile network environment.

[0067] In an embodiment, when the control plane protocol based on QUIC is the control plane protocol of HTTP / 3, in the process of S610, the terminal device can further receive a QUIC extension frame sent by the PDG, the QUIC extension frame comprising Uniform Resource Identifier (URI) information, the URI information being used to indicate a resource location of a related service provided by the network; and the terminal device can subsequently generate a registration request message according to the URI information.

[0068] S620, sending, to the PDG, a registration request message based on the control plane connection, the registration request message comprising identification information of the terminal device and registration parameters.

[0069] The registration request message is used to indicate that the terminal device requests to register to the core network device. In an embodiment, the registration parameters can comprise a registration type, such as initial registration, registration update, emergency registration, and the like.

[0070] S630, receiving a registration response message sent by the PDG.

[0071] In an embodiment, the registration response message comprises at least one of user plane connection identification information and connection indication information, the connection indication information being used to indicate whether the terminal device performs 0-RTT fast connection establishment. Optionally, the registration response message can further comprise user plane data QoS information.

[0072] The user plane connection identification information comprises at least one of the following: a UDP port number of the PDG, a QUIC connection identification used for the user plane connection, and encapsulation layer identification information used for encapsulating user plane packets.

[0073] After S630 is performed, the terminal device can further establish a user plane connection with the PDG based on a user plane protocol based on QUIC, send a user plane uplink packet to the PDG based on the user plane connection, or receive a user plane downlink packet sent by the PDG based on the user plane connection.

[0074] In an embodiment, if the registration response message comprises the connection indication information and the connection indication information indicates that the terminal device performs 0-RTT fast connection establishment, the terminal device can further receive session recovery parameter information sent by the PDG, so as to realize fast recovery of the connection between the PDG and the terminal device. The session recovery parameter information comprises a session ticket.

[0075] Exemplarily, after the user plane connection and / or the control plane connection established by the PDG and the terminal device is released, the terminal device sends a session recovery request message to the PDG, the session recovery request message comprising session recovery parameter information, so that the PDG recovers the user plane connection and / or the control plane connection with the terminal device according to the session recovery request message.

[0076] In an embodiment, when establishing the user plane connection with the PDG, the terminal device can also receive the handover indication information sent by the PDG, the handover indication information being used to indicate whether the core network device allows the terminal device to perform connection migration.

[0077] If the handover indication information indicates that the core network device allows the terminal device to perform connection migration, the terminal device sends a path challenge message to the PDG, so that the PDG switches the control plane connection and / or the user plane connection with the terminal device from one access network to another access network according to the path challenge message; and receives a path response message sent by the PDG. Thus, the handover of the access network is realized.

[0078] In the following, some examples are provided for illustrating the registration method provided in the present application. In the following examples, the terminal device is taken as an example of UE.

[0079] Example 1: the control plane protocol based on QUIC is another application layer protocol based on QUIC

[0080] FIG. 7 is a control plane protocol stack based on QUIC provided in Example 1. FIG. 8 is a user plane protocol stack based on QUIC provided in Example 1. FIG. 9 is an interaction flowchart of a registration method provided in Example 1. As shown in FIG. 9, it comprises S910-S952.

[0081] S910, the UE establishes a control plane connection with the PDG based on the control plane protocol based on QUIC.

[0082] When the UE establishes the control plane connection with the PDG, the UE triggers a QUIC handshake process with the PDG based on the other application layer protocol based on QUIC. When the UE and the PDG verify the QUIC Finished message, the control plane connection is considered to be established completely, and the UE and the PDG can start to exchange the control plane signaling (such as control plane protocol messages) safely.

[0083] S912, the UE sends a registration request message to the PDG based on the control plane connection.

[0084] The registration request message comprises the identification information of the UE and registration parameters. In an embodiment, the registration parameters can comprise a registration type, such as initial registration, registration update, emergency registration, etc.

[0085] S914, the PDG receives the registration request message sent by the UE based on the control plane connection.

[0086] S916, the PDG sends an authentication request message to the core network device according to the identification information and the registration parameter of the UE.

[0087] The PDG sends an authentication request message to the core network device, that is, the PDG requests the core network device to authenticate the UE.

[0088] S918, the core network device receives the authentication request message sent by the PDG.

[0089] The core network device initiates an authentication and authorization process to the UE through other application layer protocols based on QUIC.

[0090] S920, after completing the authentication and authorization, the core network device sends an authentication and authorization message to the PDG.

[0091] S922, the PDG receives the authentication and authorization message sent by the core network device.

[0092] S924, the PDG sends a registration response message to the UE according to the authentication and authorization message.

[0093] In an embodiment, the registration response message includes information required for subsequent establishment of a user plane connection, such as at least one of user plane connection identification information and connection indication information, the connection indication information being used to indicate whether the UE performs 0-RTT fast connection establishment. The registration response message can also include user plane data QoS information.

[0094] The user plane connection identification information includes at least one of the following: a UDP port number of the PDG, a QUIC connection ID used for the user plane connection, and encapsulation layer identification information (such as a tunnel identifier, a string, etc.) used for encapsulating user plane packets.

[0095] S926, the UE receives the registration response message sent by the PDG.

[0096] S928, the UE establishes a user plane connection with the PDG based on the user plane protocol of QUIC.

[0097] After the control plane signaling process is completed, the UE also needs to establish a user plane connection with the PDG. As shown in FIG. 8, user plane packets can be encapsulated by an encapsulation layer and then transmitted on the user plane connection based on QUIC between the UE and the PDG, or can be directly transmitted on the user plane connection based on QUIC between the UE and the PDG.

[0098] In an embodiment, the UE triggers a QUIC handshake process with the PDG based on other application layer protocols of QUIC to establish a user plane connection between the UE and the PDG.

[0099] If the registration response message includes the user plane connection identifier information, and the user plane connection identifier information is: 1) the UDP port number of the PDG, then the UDP port number of the PDG is the destination UDP port number for the QUIC connection; 2) the QUIC connection ID for the user plane connection, then the QUIC connection ID is the QUIC connection ID on the PDG side for the connection; 3) the encapsulation layer identifier information (such as tunnel identifier, string, etc.) for encapsulating the user plane message, then the encapsulation layer identifier information is the encapsulation layer identifier for the subsequent user plane message, which can be associated with the user plane QoS information.

[0100] In an embodiment, if the registration response message includes the connection indication information, and the connection indication information indicates that the UE performs 0-RTT fast connection establishment, in the process performed in S928, the PDG can send session recovery parameter information to the UE, and the session recovery parameter information includes a session ticket for fast recovery of the QUIC connection. The definition of the session ticket can refer to the related description of IETF RFC 9000, and will not be described here for brevity.

[0101] S930, the UE sends a user plane uplink message to the PDG based on the user plane connection.

[0102] S932, the PDG receives the user plane uplink message sent by the UE.

[0103] S934, the PDG forwards the user plane uplink message to the core network device.

[0104] S936, the core network device receives the user plane uplink message forwarded by the PDG.

[0105] The user plane uplink message can be a normal data message, or a user plane connection modification request message, a user plane connection release request message, etc. The user plane connection modification request message includes a user plane identifier to be modified; the user plane connection release request message includes a user plane identifier to be released.

[0106] The user plane connection modification request message and the user plane connection release request message can also be initiated by the PDG. That is, the user plane connection modification request process and the user plane connection release request process can be initiated by the UE, initiated by the PDG, or initiated by the core network device.

[0107] S940, the core network device sends a user plane downlink message to the PDG.

[0108] S942, the PDG receives the user plane downlink message sent by the core network device.

[0109] S944, the PDG forwards the user plane downlink message to the UE based on the user plane connection.

[0110] S946, the UE receives the user plane downlink message forwarded by the PDG based on the user plane connection.

[0111] The user plane downlink message can be a normal data message, or a user plane connection modification request message, a user plane connection release request message, etc. The user plane connection modification request message includes a user plane identifier to be modified; the user plane connection release request message includes a user plane identifier to be released.

[0112] The user plane connection modification request message and the user plane connection release request message can also be initiated by the PDG. That is, the user plane connection modification request process and the user plane connection release request process can be initiated by the UE, initiated by the PDG, or initiated by the core network device.

[0113] In an embodiment, if the registration response message includes connection indication information, and the connection indication information indicates that the terminal device performs 0-RTT fast connection establishment, S950-S952 can also be performed.

[0114] S950, the UE sends a session recovery request message to the PDG.

[0115] The session recovery request message includes session recovery parameter information. The session recovery parameter information includes a session ticket. Optionally, the session recovery request message can also carry user plane data, which is encrypted and protected by the key derived from the session ticket.

[0116] S952, the PDG receives the session recovery request message sent by the UE, and recovers the user plane connection and / or the control plane connection with the UE according to the session recovery request message.

[0117] Example 2: the control plane protocol based on QUIC is the control plane protocol of HTTP / 3

[0118] FIG. 10 is a control plane protocol stack based on QUIC provided by example 2. FIG. 11 is a user plane protocol stack based on QUIC provided by example 2. FIG. 12 is an interaction flowchart of a registration method provided by example 2. As shown in FIG. 12, it includes S1210-S1252.

[0119] S1210, based on the control plane protocol of HTTP / 3, the UE establishes a control plane connection with the PDG.

[0120] When the UE establishes the control plane connection with the PDG, the UE triggers a QUIC handshake procedure with the PDG based on the HTTP / 3 control plane protocol, and the control plane connection is considered to be established only after the UE and the PDG verify the QUIC Finished message, and the UE and the PDG can start to exchange control plane signaling (such as control plane protocol messages) safely.

[0121] In an embodiment, in the process of performing S1210, the PDG can also send a QUIC extension frame to the UE, and the QUIC extension frame includes a URI, and the URI information is used to indicate the resource location of the related service provided by the network.

[0122] S1212, the UE generates a registration request message according to the URI information, and sends the registration request message to the PDG based on the control plane connection.

[0123] The registration request message includes the identification information of the UE and the registration parameter. In an embodiment, the registration parameter can include a registration type, such as initial registration, registration update, emergency registration, etc.

[0124] S1214, the PDG receives the registration request message sent by the UE based on the control plane connection.

[0125] S1216, the PDG sends an authentication request message to the core network device according to the identification information of the UE and the registration parameter.

[0126] The PDG sends the authentication request message to the core network device, that is, the PDG requests the core network device to authenticate the UE.

[0127] S1218, the core network device receives the authentication request message sent by the PDG.

[0128] The core network device initiates an authentication and authorization procedure to the UE through other application layer protocols based on QUIC.

[0129] S1220, after completing the authentication and authorization, the core network device sends an authentication and authorization message to the PDG.

[0130] S1222, the PDG receives the authentication and authorization message sent by the core network device.

[0131] S1224, the PDG sends a registration response message to the UE according to the authentication and authorization message.

[0132] In an embodiment, the registration response message includes at least one of user plane connection identification information and connection indication information required for subsequent establishment of a user plane connection, and the connection indication information is used to indicate whether the UE performs 0-RTT fast connection establishment. The registration response message can also include user plane data QoS information.

[0133] The user plane connection identification information includes at least one of the following: a UDP port number of the PDG, and a QUIC connection ID for the user plane connection.

[0134] S1226, the UE receives the registration response message sent by the PDG.

[0135] S1228, the UE establishes a user plane connection with the PDG based on the HTTP / 3-based user plane protocol.

[0136] In an embodiment, the UE triggers a QUIC handshake process with the PDG based on the HTTP / 3-based user plane protocol to establish the user plane connection between the UE and the PDG.

[0137] If the registration response message includes user plane connection identification information, and the user plane connection identification information is: 1) a UDP port number of the PDG, then the UDP port number of the PDG is the destination UDP port number for the QUIC connection; or 2) a QUIC connection ID for the user plane connection, then the QUIC connection ID is the QUIC connection ID on the PDG side for the connection.

[0138] In an embodiment, if the registration response message includes connection indication information and the connection indication information indicates that the UE performs 0-RTT fast connection establishment, during the process performed in S1228, the PDG can send session recovery parameter information to the UE, the session recovery parameter information including a session ticket for fast recovery of the QUIC connection. The definition of the session ticket can refer to the related description of IETF RFC 9000, and will not be described here for brevity.

[0139] The PDG can initiate a UE user plane channel establishment request to the core network device, the core network decides the related transmission strategy and feeds back the strategy to the PDG and the core network gateway in a response message, and the user plane establishment between the PDG and the core network for the UE is completed.

[0140] S1230, the UE sends a user plane uplink message to the PDG based on the user plane connection.

[0141] S1232, the PDG receives the user plane uplink message sent by the UE.

[0142] S1234, the PDG forwards the user plane uplink message to the core network device.

[0143] S1236, the core network device receives the user plane uplink message forwarded by the PDG.

[0144] The user plane uplink message can be a normal HTTP / 3 data message, or a user plane connection modification request message, a user plane connection release request message, etc. The user plane connection modification request message includes a user plane identifier to be modified; and the user plane connection release request message includes a user plane identifier to be released.

[0145] The user plane connection modification request message and the user plane connection release request message can also be initiated by the PDG. That is, the user plane connection modification request process and the user plane connection release request process can be initiated by the UE, initiated by the PDG, or initiated by the core network device. The user plane connection modification request process and the user plane connection release request process are implemented through HTTP / 3 request and HTTP / 3 response.

[0146] In S1240, the core network device sends a user plane downlink message to the PDG.

[0147] In S1242, the PDG receives the user plane downlink message sent by the core network device.

[0148] In S1244, the PDG forwards the user plane downlink message to the UE based on the user plane connection.

[0149] In S1246, the UE receives the user plane downlink message forwarded by the PDG based on the user plane connection.

[0150] The user plane downlink message can be a normal HTTP / 3 data message, or a user plane connection modification request message, a user plane connection release request message, etc. The user plane connection modification request message includes a user plane identifier to be modified; and the user plane connection release request message includes a user plane identifier to be released.

[0151] The user plane connection modification request message and the user plane connection release request message can also be initiated by the PDG. That is, the user plane connection modification request process and the user plane connection release request process can be initiated by the UE, initiated by the PDG, or initiated by the core network device. The user plane connection modification request process and the user plane connection release request process are implemented through HTTP / 3 request and HTTP / 3 response.

[0152] In an embodiment, if the registration response message includes connection indication information, and the connection indication information indicates that the terminal device performs 0-RTT fast connection establishment, S1250-S1252 can also be performed.

[0153] In S1250, the UE sends a session recovery request message to the PDG.

[0154] The session resume request message includes session resume parameter information. The session resume parameter information includes a session ticket. The session resume request message can also carry user plane data, which is encrypted and protected by a key derived from the session ticket.

[0155] S1252, the PDG receives the session resume request message sent by the UE, and resumes the user plane connection and / or the control plane connection with the UE according to the session resume request message.

[0156] Example 3

[0157] FIG. 13 is a schematic diagram of a UE switching from an access network 1 to an access network 2 according to example 3. As shown in FIG. 13, the access network 1 and the access network 2 are connected to the same PDG, and the connection control management is based on the QUIC protocol. FIG. 14 is an interaction flow diagram of a UE switching from an access network 1 to an access network 2 according to example 3. As shown in FIG. 14, the following processes are included.

[0158] 1. The UE connects to the core network from the access network 1. In this process, the network can instruct the UE to allow connection migration when the UE address information changes, which can be used to indicate at least one of migration of the control plane connection and migration of the user plane connection.

[0159] 2. The UE moves to the access network 2 due to movement or the like, and the local address of the UE changes. At this time, the UE sends a PATH_CHALLENGE message to the PDG, which is directly sent using the control plane QUIC connection parameter in the access network 1, for the purpose of migrating the control plane connection to the access network 2 path.

[0160] 3. The PDG verifies through the PATH_CHALLENGE message, and sends a PATH_RESPONSE message to the UE. The UE completes the migration of the control plane connection with the PDG from the access network 1 to the access network 2.

[0161] 4. The UE sends a PATH_CHALLENGE message to the PDG, which is directly sent using the user plane QUIC connection parameter in the access network 1, for the purpose of migrating the user plane connection to the access network 2 path.

[0162] 5. The PDG verifies through the PATH_CHALLENGE message, and sends a PATH_RESPONSE message to the UE. The UE completes the migration of the user plane connection with the PDG from the access network 1 to the access network 2.

[0163] The user plane data can be transmitted between the UE and the core network through the access network 2.

[0164] Example 4

[0165] Figure 15 is a schematic diagram of a UE switching from an access network 1 to an access network 2 according to example 4. As shown in Figure 15, the access network 1 connects to a PDG 1, the access network 2 connects to a PDG 2, and the connection control management is based on the QUIC protocol. Figure 16 is an interaction flow diagram of a UE switching from an access network 1 to an access network 2 according to example 4. As shown in Figure 16, the following processes are included.

[0166] 1. The UE connects to a core network from an access network 1. In this process, the network can indicate that the UE is allowed to perform connection migration when the UE address information changes, and the indication can be used to indicate at least one of migration of a control plane connection and migration of a user plane connection.

[0167] 2. The UE moves to an access network 2 due to movement or the like, the local address of the UE changes, the UE updates the connection state to the PDG 1, and the connection is migrated from the access network 1 to the access network 2. According to the change of the connection, the PDG 1 decides to migrate the connection of the UE to the PDG 2 based on a local policy or interaction information with the core network. The PDG 1 notifies the UE of the migration result and includes address information (IP address, port number, URI / URL, etc.) of the PDG 2 to migrate the connection to the PDG 2; the PDG 1 triggers the push of the connection context information of the UE to the PDG 2 through the core network.

[0168] 3. The UE sends a PATH_CHALLENGE message to the PDG 2, which is directly sent using the control plane QUIC connection parameter of the UE connecting to the PDG 1 from the access network 1, and the purpose is to migrate the control plane connection to the PDG 2.

[0169] 4. The PDG 2 verifies through the PATH_CHALLENGE message and sends a PATH_RESPONSE message to the UE. The UE completes the control plane connection migration to the PDG 2 through the access network 2.

[0170] 5. The UE sends a PATH_CHALLENGE message to the PDG 2, which is directly sent using the user plane QUIC connection parameter of the UE connecting to the PDG 1 from the access network 1, and the purpose is to migrate the user plane connection to the PDG 2.

[0171] 6. The PDG 2 verifies through the PATH_CHALLENGE message and sends a PATH_RESPONSE message to the UE. The UE completes the user plane connection migration to the PDG 2 through the access network 2.

[0172] User plane data can be transmitted between the UE and the core network through the access network 2 and the PDG 2.

[0173] Fig. 17 is a structural schematic diagram of a registration device provided in an embodiment, which can be arranged in a PDG. As shown in Fig. 17, the device comprises a processing module 100, a receiving module 101 and a sending module 102.

[0174] The processing module 100 is configured to establish a control plane connection with a terminal device according to a control plane protocol based on a Quick User Datagram Protocol network connection (QUIC); the receiving module 101 is configured to receive a registration request message sent by the terminal device based on the control plane connection, the registration request message comprising identification information and registration parameters of the terminal device; the sending module 102 is configured to send an authentication request message to a core network device according to the identification information and the registration parameters of the terminal device; the receiving module 101 is configured to receive an authentication and authorization message sent by the core network device; and the sending module 102 is configured to send a registration response message to the terminal device according to the authentication and authorization message.

[0175] The registration device provided in the embodiment is used to implement the registration method shown in Fig. 5, and the implementation principle and technical effects of the registration device provided in the embodiment are similar to those of the above-mentioned embodiments, which will not be described herein.

[0176] In an embodiment, the control plane protocol based on QUIC is another application layer protocol based on QUIC or a control plane protocol of a third version of the Hypertext Transfer Protocol (HTTP / 3).

[0177] In an embodiment, when the control plane protocol based on QUIC is the control plane protocol of HTTP / 3, the sending module 102 is further configured to send a QUIC extension frame to the terminal device when the control plane connection is established with the terminal device, the QUIC extension frame comprising uniform resource identifier (URI) information, the URI information being used to indicate a resource location of a related service provided by the network.

[0178] In an embodiment, the registration response message comprises at least one of user plane connection identification information and connection indication information, the connection indication information being used to indicate whether the terminal device performs a 0-RTT (0-Round Trip Time) fast connection establishment.

[0179] In an embodiment, the user plane connection identification information comprises at least one of the following: a UDP port number of the PDG, a QUIC connection identification used for the user plane connection, and encapsulation layer identification information used for encapsulating a user plane message.

[0180] In an embodiment, the processing module 100 is further configured to establish a user plane connection with the terminal device according to the QUIC-based user plane protocol; the receiving module 101 is further configured to receive a user plane uplink message sent by the terminal device based on the user plane connection, and the sending module 102 is further configured to forward the user plane uplink message to the core network device; or, the receiving module 101 is further configured to receive a user plane downlink message sent by the core network device, and the sending module 102 is further configured to forward the user plane downlink message to the terminal device based on the user plane connection.

[0181] In an embodiment, if the registration response message includes connection indication information, and the connection indication information indicates that the terminal device performs 0-RTT fast connection establishment, the sending module 102 is further configured to send session resumption parameter information to the terminal device; the receiving module 101 is further configured to receive a session resumption request message sent by the terminal device after the user plane connection and / or the control plane connection established with the terminal device are released, the session resumption request message including the session resumption parameter information; and the processing module 100 is further configured to resume the user plane connection and / or the control plane connection with the terminal device according to the session resumption request message.

[0182] In an embodiment, the session resumption parameter information includes a session ticket.

[0183] In an embodiment, the receiving module 101 is further configured to receive switching indication information sent by the core network device, the switching indication information being used to indicate whether the core network device allows the terminal device to perform connection migration; and the sending module 102 is further configured to send the switching indication information to the terminal device.

[0184] In an embodiment, if the switching indication information indicates that the core network device allows the terminal device to perform connection migration, the receiving module 101 is further configured to receive a path challenge message sent by the terminal device; the processing module 100 is further configured to switch the control plane connection and / or the user plane connection with the terminal device from one access network to another access network according to the path challenge message; and the sending module 102 is further configured to send a path response message to the terminal device.

[0185] FIG. 18 is a structural schematic diagram of another registration apparatus provided by an embodiment, which can be configured in a terminal device, as shown in FIG. 18, the apparatus includes a processing module 200, a sending module 201 and a receiving module 202.

[0186] The processing module 200 is configured to establish a control plane connection with a packet data gateway (PDG) according to a control plane protocol based on a quick user datagram protocol network connection (QUIC); the sending module 201 is configured to send a registration request message to the PDG based on the control plane connection, the registration request message including identification information and registration parameters of the terminal device; and the receiving module 202 is configured to receive a registration response message sent by the PDG.

[0187] The registration device provided in this embodiment is used to implement the registration method shown in FIG. 6, and the implementation principle and technical effects of the registration device provided in this embodiment are similar to those of the above-described embodiments, which will not be described herein again.

[0188] In an embodiment, the control plane protocol based on QUIC is another application layer protocol based on QUIC or a control plane protocol of a third version of a hypertext transfer protocol (HTTP / 3).

[0189] In an embodiment, when the control plane protocol based on QUIC is the control plane protocol of HTTP / 3, the receiving module 202 is further configured to receive a QUIC extension frame sent by the PDG when the control plane connection is established, the QUIC extension frame including uniform resource identifier (URI) information, the URI information being used to indicate a resource location of a related service provided by a network; and the sending module 201 is further configured to generate the registration request message according to the URI information.

[0190] In an embodiment, the registration response message includes at least one of user plane connection identification information and connection indication information, the connection indication information being used to indicate whether the terminal device performs 0-RTT fast connection establishment.

[0191] In an embodiment, the user plane connection identification information includes at least one of a UDP port number of the PDG, a QUIC connection identifier used for the user plane connection, and encapsulation layer identification information used for encapsulating a user plane message.

[0192] In an embodiment, the processing module 200 is further configured to establish a user plane connection with the PDG according to a user plane protocol based on QUIC; the sending module 201 is further configured to send a user plane uplink message to the PDG based on the user plane connection; or the receiving module 202 is further configured to receive a user plane downlink message sent by the PDG based on the user plane connection.

[0193] In an embodiment, if the registration response message comprises the connection indication information, and the connection indication information indicates that the terminal device performs 0-RTT fast connection establishment, the receiving module 202 is further configured to receive session resumption parameter information sent by the PDG; and the sending module 201 is further configured to send, to the PDG, a session resumption request message after releasing the user plane connection and / or the control plane connection established with the PDG, the session resumption request message comprising the session resumption parameter information.

[0194] In an embodiment, the session resumption parameter information comprises a session ticket.

[0195] In an embodiment, the receiving module 202 is further configured to receive switching indication information sent by the PDG, the switching indication information being used to indicate whether the core network device allows the terminal device to perform connection migration.

[0196] In an embodiment, if the switching indication information indicates that the core network device allows the terminal device to perform connection migration, the sending module 201 is further configured to send, to the PDG, a path challenge message; and the receiving module 202 is further configured to receive a path response message sent by the PDG.

[0197] Embodiments of the present application further provide a packet data gateway, comprising a processor, the processor being used to implement the method provided in any of the embodiments of the present application when executing a computer program.

[0198] FIG. 19 is a structural schematic diagram of a packet data gateway according to an embodiment of the present application. As shown in FIG. 19, the packet data gateway comprises a processor 60, a memory 61 and a communication interface 62; the number of processors 60 in the packet data gateway can be one or more, and one processor 60 is taken as an example in FIG. 19; the processor 60, the memory 61 and the communication interface 62 in the packet data gateway can be connected through a bus or other means, and the connection through a bus is taken as an example in FIG. 19. The bus represents one or more of several bus structures, including a memory bus or a memory controller, a peripheral bus, a graphics acceleration port, a processor or a local bus using any of the bus structures.

[0199] The memory 61, as a kind of computer readable storage medium, can be configured to store software programs, computer executable programs and modules, such as program instructions / modules corresponding to the method in the embodiments of the present application. The processor 60 performs at least one function application and data processing of the packet data gateway by running the software programs, instructions and modules stored in the memory 61, that is, implements the above method.

[0200] The memory 61 can include a program region and a data region, where the program region can store an operating system, an application required for at least one function, and the like, and the data region can store data created according to use of the terminal, and the like. In addition, the memory 61 can include a high-speed random access memory, and can further include a non-volatile memory such as at least one of a magnetic disk storage device, a flash memory device, or other non-volatile solid state storage device. In some examples, the memory 61 can include a memory disposed remotely from the processor 60, and these remote memories can be connected to a packet data gateway through a network. Examples of the network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0201] The communication interface 62 can be configured to receive and transmit data.

[0202] The embodiments of the present application also provide a terminal device, including: a processor, the processor is used for implementing the method provided by any of the embodiments of the present application when executing a computer program. For example, the following embodiments provide a structural schematic diagram of a terminal device, which is a UE.

[0203] FIG. 20 is a structural schematic diagram of a UE according to an embodiment, and the UE can be implemented in various forms. The UE in the present application can include, but is not limited to, a mobile terminal device such as a mobile phone, a smart phone, a notebook computer, a digital broadcast receiver, a personal digital assistant (PDA), a tablet computer (PAD), a portable media player (PMP), a navigation device, a vehicle-mounted terminal device, a vehicle-mounted display terminal, a vehicle-mounted electronic rearview mirror, and the like, and a fixed terminal device such as a digital television (TV), a desktop computer, and the like.

[0204] As shown in FIG. 20, the UE 50 can include a wireless communication unit 51, an audio / video (A / V) input unit 52, a user input unit 53, a sensing unit 54, an output unit 55, a memory 56, an interface unit 57, a processor 58, and a power supply unit 59, and the like. FIG. 20 shows a UE including various components, but it is understood that implementation of all of the illustrated components is not required. More or fewer components can alternatively be implemented.

[0205] In the present embodiment, the wireless communication unit 51 allows radio communication between the UE 50 and a base station or a network. The A / V input unit 52 is configured to receive audio or video signals. The user input unit 53 can generate key input data to control various operations of the UE 50 according to a user's input command. The sensing unit 54 detects a current state of the UE 50, a location of the UE 50, a presence or absence of a user's touch input with respect to the UE 50, an orientation of the UE 50, acceleration or deceleration movement and direction of the UE 50, and the like, and generates a command or signal for controlling the operation of the UE 50. The interface unit 57 serves as an interface through which at least one external device can be connected to the UE 50. The output unit 55 is configured to provide an output signal in a form of visual, audio, and / or tactile. The memory 56 can store software programs and the like for processing and control operations performed by the processor 58, or can temporarily store data that has been output or is to be output. The memory 56 can include at least one type of storage medium. Also, the UE 50 can cooperate with a network storage device that performs a storage function of the memory 56 through a network connection. The processor 58 generally controls the overall operation of the UE 50. The power supply unit 59 receives external power or internal power under the control of the processor 58 and provides appropriate power required for operating various elements and components.

[0206] The processor 58 performs at least one functional application and data processing by running a program stored in the memory 56, for example, a method provided by the present embodiment.

[0207] The present embodiment also provides a computer readable storage medium, and the computer readable storage medium stores a computer program. The computer program is executed by a processor to implement a method provided by any of the embodiments of the present application.

[0208] The computer storage medium of the embodiments of the present application can adopt any combination of one or more computer readable media. The computer readable medium can be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium may, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination thereof. The computer readable storage medium includes, but is not limited to, a non-exhaustive list: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present application, the computer readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device or apparatus.

[0209] The computer readable signal medium can include a data signal propagating in a baseband or as part of a carrier wave propagating through a transmission medium, and bearing computer readable program code. Such a propagating data signal can take many forms, including but not limited to electro-magnetic, optical, or any suitable combination thereof. The computer readable signal medium can also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate or transport program for use by or in connection with an instruction execution system, apparatus or device.

[0210] The program code contained on the computer readable medium can be transmitted by any suitable medium, including but not limited to wireless, wire, cable, radio frequency (RF), or any suitable combination thereof.

[0211] Computer program code for carrying out operations of the present disclosure can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++, Ruby, Go, or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0212] The embodiments of the present application further provide a computer program product, comprising a computer program which, when executed by a processor, implements the method provided by any of the embodiments of the present application.

[0213] The computer program code for carrying out operations of the present application can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++, Ruby, Go, or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0214] Those skilled in the art will appreciate that the term user terminal encompasses any appropriate type of wireless user equipment, such as a mobile phone, a portable data processing apparatus, a portable web browser, or a vehicle mounted mobile station.

[0215] In general, the various embodiments of the application can be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects can be implemented in hardware, while other aspects can be implemented in

[0216] Embodiments of the application can be implemented by computer program instructions on a mobile device's data processor, for example in the processor entity, or by hardware, or by a combination of software and hardware. Computer program instructions can be in assemblies, Instruction Set Architecture (ISA), machine, machine-related, microcode, firmware, state setting data, or source code or object code written in any combination of one or more programming languages to be ultimately mapped to machine language.

[0217] Any block diagrams of logical flows of the application can represent program operations, or a logical flow of operations, or a combination of program operations and logical flows of operations. Computer program instructions can be stored on a memory. The memory can be of any suitable type and can be implemented using any suitable data storage technology, such as, but not limited to, read only memory (ROM), random access memory (RAM), optical storage devices, and systems, digital versatile disc (DVD) or CD discs, and the like. The computer readable media can include non-transitory storage media. The data processor can be of any suitable type and can be implemented using any suitable combination of hardware and software.

Claims

1. A registration method applied to a packet data gateway (PDG), comprising: establishing a control plane connection with a terminal device according to a control plane protocol based on a quick user datagram protocol (UDP) internet connection (QUIC); receiving a registration request message sent by the terminal device based on the control plane connection, the registration request message comprising identification information of the terminal device and registration parameters; sending an authentication request message to a core network device according to the identification information of the terminal device and the registration parameters; and receiving an authentication and authorization message sent by the core network device, and sending a registration response message to the terminal device according to the authentication and authorization message. The control plane protocol based on QUIC is a control plane protocol of a third version of a hypertext transfer protocol (HTTP) 3 or another application layer protocol based on QUIC. When the control plane protocol based on QUIC is a control plane protocol of HTTP / 3, the method further comprises, when the control plane connection is established with the terminal device: sending a QUIC extension frame to the terminal device, the QUIC extension frame comprising uniform resource identifier (URI) information, the URI information being used to indicate a resource location of a related service provided by a network. The registration response message comprises at least one of user plane connection identification information and connection indication information, the connection indication information being used to indicate whether the terminal device performs 0-RTT fast connection establishment.

2. The registration method of claim 1, wherein, The user plane connection identification information comprises at least one of a user datagram protocol (UDP) port number of the PDG, a QUIC connection identifier used for a user plane connection, and encapsulation layer identification information used for encapsulating a user plane message.

3. The registration method of claim 2, wherein, 6. The registration method of claim 4, after the registration response message is sent to the terminal device, further comprising: establishing a user plane connection with the terminal device according to a user plane protocol based on QUIC; 4. The registration method of claim 1, wherein, receiving a user plane uplink message sent by the terminal device based on the user plane connection, and forwarding the user plane uplink message to the core network device; or receiving a user plane downlink message sent by the core network device, and forwarding the user plane downlink message to the terminal device based on the user plane connection.

5. The registration method of claim 4, wherein, If the registration response message comprises the connection indication information, and the connection indication information indicates that the terminal device performs 0-RTT fast connection establishment, the method further comprises: sending session recovery parameter information to the terminal device; after at least one of the user plane connection and the control plane connection established with the terminal device is released, receiving a session recovery request message sent by the terminal device, the session recovery request message comprising the session recovery parameter information; and reestablishing at least one of the user plane connection and the control plane connection with the terminal device according to the session recovery request message. The session recovery parameter information comprises a session ticket.

7. The registration method of claim 6, wherein, When the user plane connection is established with the terminal device, the method further comprises: receiving switching indication information sent by the core network device, the switching indication information being used to indicate whether the core network device allows the terminal device to perform connection migration; ​ ​ 8. The registration method of claim 7, wherein, ​ 9. The registration method of claim 6, wherein, ​ ​ sending the terminal device the handover indication information.

10. The registration method of claim 9, wherein, If the handover indication information indicates that the core network device allows the terminal device to perform connection migration, the method further includes: receiving a path challenge message sent by the terminal device; switching at least one of the control plane connection and the user plane connection of the terminal device from one access network to another access network according to the path challenge message; sending a path response message to the terminal device.

11. A registration method applied to a terminal device, comprising: establishing a control plane connection with a packet data gateway (PDG) based on a quick user datagram protocol (UDP) internet connection (QUIC)-based control plane protocol; sending a registration request message to the PDG based on the control plane connection, the registration request message comprising identification information and registration parameters of the terminal device; receiving a registration response message sent by the PDG.

12. The registration method of claim 11, wherein, The QUIC-based control plane protocol is a QUIC-based other application layer protocol or a control plane protocol of a third version of hypertext transfer protocol (HTTP) / 3.

13. The registration method of claim 12, wherein, When the QUIC-based control plane protocol is the control plane protocol of HTTP / 3, when the control plane connection is established with the PDG, the method further includes: receiving a QUIC extension frame sent by the PDG, the QUIC extension frame comprising uniform resource identifier (URI) information, the URI information being used to indicate a resource location of a related service provided by a network; generating the registration request message according to the URI information.

14. The registration method of claim 11, wherein, The registration response message comprises at least one of user plane connection identification information and connection indication information, the connection indication information being used to indicate whether the terminal device performs 0-RTT (zero round trip time) fast connection establishment.

15. The registration method of claim 14, wherein, The user plane connection identification information comprises at least one of a user datagram protocol (UDP) port number of the PDG, a QUIC connection identification used for a user plane connection, and encapsulation layer identification information used for encapsulating a user plane message.

16. The registration method according to claim 14, after receiving the registration response message sent by the PDG, the method further includes: establishing a user plane connection with the PDG based on a QUIC-based user plane protocol; sending a user plane uplink message to the PDG based on the user plane connection; or receiving a user plane downlink message sent by the PDG based on the user plane connection. If the registration response message comprises the connection indication information and the connection indication information indicates that the terminal device performs 0-RTT fast connection establishment, the method further includes:

17. The registration method of claim 16, wherein, receiving session recovery parameter information sent by the PDG; after releasing at least one of the user plane connection and the control plane connection established with the PDG, sending a session recovery request message to the PDG, the session recovery request message comprising the session recovery parameter information. The session recovery parameter information comprises a session ticket.

18. The registration method of claim 17, wherein, When the user plane connection is established with the PDG, the method further includes:

19. The registration method of claim 16, wherein, receiving handover indication information sent by the PDG, the handover indication information being used to indicate whether a core network device allows the terminal device to perform connection migration. ​ 20. The registration method of claim 19, wherein, if the handover indication information indicates that the core network device allows the terminal device to perform connection migration; further comprising: sending a path challenge message to the PDG; receiving a path response message sent by the PDG.

21. A packet data gateway, comprising: a processor; the processor is configured to implement the registration method of any one of claims 1-10 when executing the computer program.

22. A terminal device comprising: a processor; the processor is configured to implement the registration method of any one of claims 11-20 when executing the computer program.

23. A computer readable storage medium storing a computer program, the computer program being executed by a processor to implement the registration method of any one of claims 1-20.

Images