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

Abstract

The invention discloses a registration method, a packet data gateway, terminal equipment and a storage medium. The registration method is applied to a packet data gateway PDG. The method comprises the following steps: establishing a control plane connection with a terminal device according to a control plane protocol based on a fast user datagram protocol network connection QUIC; receiving a registration request message sent by the terminal device based on the control plane connection, wherein the registration request message comprises 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 parameter of the terminal device; and receiving an authentication and authorization message sent by the core network equipment, and sending a registration response message to the terminal equipment according to the authentication and authorization message.

Description

TECHNICAL FIELD

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

[0002] At present, the design of a terminal device from a non-3GPP access network in the 3rd Generation Partnership Project (3GPP) 5th-generation (5G) standard is relatively complex: in order to take into account the fusion of the second version of the Internet Key Exchange (IKEv2) fixed process and 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 additionally allocate an Internet Protocol (IP) address for the NAS, causing the problems 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 cause a large maintenance overhead of the TCP connection on the N3IWF. Moreover, the user plane protocol also adopts an Internet Protocol Security (IPSec) tunnel mode, which also has similar problems as the control plane. SUMMARY

[0003] Embodiments of the present application provide a registration method applied to a packet data gateway (PDG), comprising:

[0004] establishing a control plane connection with the terminal device based on a control plane protocol based on a Quick User Datagram Protocol Network Connection (QUIC);

[0005] 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;

[0006] sending an authentication request message to a core network device according to the identification information and the registration parameters of the terminal device;

[0007] 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.

[0008] Embodiments of the present application provide a registration method applied to a terminal device, comprising:

[0009] establish a control plane connection with a packet data gateway PDG based on a control plane protocol based on a quick user datagram protocol network connection QUIC;

[0010] 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;

[0011] receiving a registration response message sent by the PDG.

[0012] An embodiment of the present application provides a packet data gateway, comprising: a processor; the processor is configured to implement the registration method of any of the above embodiments when executing a computer program.

[0013] An embodiment of the present application provides a terminal device, comprising: a processor; the processor is configured to implement the registration method of any of the above embodiments when executing a computer program.

[0014] An embodiment of the present application further provides a computer readable storage medium, which stores a computer program, and the computer program is configured to implement the method of any of the above embodiments when executed by a processor.

[0015] More details about the above embodiments and other aspects of the present application and implementation manners thereof are provided in the description of drawings, specific embodiments and claims. DETAILED DESCRIPTION

[0016] Figure 1 is an existing control plane protocol stack;

[0017] Figure 2 is another existing control plane protocol stack;

[0018] Figure 3 is an existing user plane protocol stack;

[0019] Figure 4 is a networking schematic diagram of a wireless communication system provided by an embodiment;

[0020] Figure 5 is a flowchart of a registration method provided by an embodiment;

[0021] Figure 6 is a flowchart of another registration method provided by an embodiment;

[0022] Figure 7 is a control plane protocol stack based on QUIC provided by example 1;

[0023] Figure 8 is a user plane protocol stack based on QUIC provided by example 1;

[0024] Figure 9 is an interaction flowchart of a registration method provided in Example 1;

[0025] Figure 10 is a QUIC-based control plane protocol stack provided in Example 2;

[0026] Figure 11 is a QUIC-based user plane protocol stack provided in Example 2;

[0027] Figure 12 is an interaction flowchart of a registration method provided in Example 2;

[0028] Figure 13 is a schematic diagram of a UE switching from an access network 1 to an access network 2 provided in Example 3;

[0029] Figure 14 is an interaction flowchart of a UE switching from an access network 1 to an access network 2 provided in Example 3;

[0030] Figure 15 is a schematic diagram of a UE switching from an access network 1 to an access network 2 provided in Example 4;

[0031] Figure 16 is an interaction flowchart of a UE switching from an access network 1 to an access network 2 provided in Example 4;

[0032] Figure 17 is a structural schematic diagram of a registration device provided in an embodiment;

[0033] Figure 18 is a structural schematic diagram of another registration device provided in an embodiment;

[0034] Figure 19 is a structural schematic diagram of a packet data gateway provided in an embodiment;

[0035] Figure 20 is a structural schematic diagram of a UE provided in an embodiment. DETAILED DESCRIPTION

[0036] It should be understood that the specific embodiments described herein merely exemplify the application and do not limit the application. The embodiments of the application will be described in detail below with reference to the accompanying drawings.

[0037] At present, in order to take into account the fusion of the IKEv2 fixed process and the 3GPP access NAS registration, the registration process of a user equipment (UE) from a non-3GPP access to a network needs two sets of control plane protocol stacks and uses a tunnel mode to implement: Figure 1 is a control plane protocol stack, Figure 2is another existing control plane protocol stack, resulting in N3IWF needing to additionally allocate an IP address for NAS, causing problems of complex implementation and large protocol overhead. Moreover, the user plane protocol also adopts an IPSec tunnel mode, Figure 3 is an existing user plane protocol stack, and similar problems exist as in the control plane.

[0038] The registration method provided by the 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 of 5G, and a new communication system to appear in future communication development, such as a 6th-generation (6G) system. Figure 4 is a networking diagram of a wireless communication system provided by an embodiment. As shown in Figure 4 the wireless communication system includes a terminal device 110, a packet data gateway (PDG) 120, and a core network device 130.

[0039] 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.

[0040] 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 the non-3GPP access network, reduce the overhead, and have important significance for improving the network reliability and robustness.

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

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

[0043] Quick UDP Internet Connections (QUIC): A new transport layer protocol that implements many of the features of the TCP protocol on top of the User Datagram Protocol (UDP), designed 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 originally designed to reduce web page loading time and improve security, it uses UDP instead of traditional TCP to reduce overhead and allow faster retransmission. The QUIC base protocol is defined in Internet Engineering Task Force (IETF) RFC 9000, other related protocols can refer to relevant IETF RFCs such as 3GPP TS 23.402, 3GPP TS 23.501, IETF RFC 9000, IETF RFC 9001, IETF RFC 9002, IETF RFC 9114.

[0044] QUIC has the following technical features:

[0045] (1) Fast connection establishment: QUIC uses session multiplexing to reduce the delay of connection establishment, allowing the parameters of the previous connection to be multiplexed on a new connection, thus avoiding the waiting time of the Transport Layer Security (TLS) handshake.

[0046] (2) Multiplexing: QUIC supports 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.

[0047] (3) Security: Built-in encryption similar to TLS provides end-to-end secure connection, protecting data transmission from eavesdropping and tampering.

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

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

[0050] (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.

[0051] Figure 5 FIG. 1 is a flowchart of a registration method according to an embodiment. As shown in FIG. 1, the method provided by the embodiment is applicable to a PDG. The method includes the following steps. Figure 5

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

[0053] In the process of accessing the 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.

[0054] 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).

[0055] Specifically, 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.

[0056] The control plane connection established by the PDG and the terminal device based on the QUIC-based control plane protocol has stronger recovery capability in the face of unstable network or packet loss due to the design of QUIC. The further combination of QUIC and HTTP / 3 significantly improves the application loading speed, especially in a mobile network environment.

[0057] In an embodiment, when the QUIC-based control plane protocol is the control plane protocol of HTTP / 3, the PDG can also send a QUIC extension frame to the terminal device during the execution of step S510. The QUIC extension frame includes Uniform Resource Identifier (URI) information, which is used to indicate the resource location of the related service provided by the network.

[0058] ​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.

[0059] 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.

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

[0061] 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.

[0062] 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.

[0063] 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. Optionally, the registration response message can further comprise user plane Quality of Service (QoS) information.

[0064] 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.

[0065] Further, after step S540 is performed, the PDG can further 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.

[0066] 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 further 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.

[0067] 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.

[0068] 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.

[0069] If the switching indication information indicates that the core network device allows the terminal device to perform connection migration, the PDG receives a path switching request message sent by the terminal device; according to the path switching request 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 switching response message to the terminal device. Thus, the switching of the access network is realized.

[0070] Figure 6 is a flowchart of another registration method provided in an embodiment, as shown in Figure 6 The method provided in the embodiment is applicable to a terminal device. The method comprises the following steps.

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

[0072] In the process of the terminal device from the 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, a QUIC-based control plane protocol is adopted. The QUIC-based control plane protocol can be another application layer protocol based on QUIC, or a control plane protocol of HTTP / 3.

[0073] Specifically, 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.

[0074] 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 loading speed to be significantly improved, especially in a mobile network environment.

[0075] In an embodiment, when the control plane protocol based on the QUIC is the control plane protocol of HTTP / 3, in the process of performing the step 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.

[0076] 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.

[0077] 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, for example, initial registration, registration update, emergency registration, and the like.

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

[0079] 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.

[0080] 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.

[0081] Further, after performing the step S630, the terminal device can further establish a user plane connection with the PDG according to the user plane protocol based on the 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.

[0082] 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.

[0083] 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.

[0084] 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.

[0085] 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 switching request 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 switching request message; and receives a path switching response message sent by the PDG. Thus, the handover of the access network is realized.

[0086] Next, some examples are provided to illustrate the registration method provided in the present application. In the following examples, the terminal device is taken as an example of UE.

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

[0088] Figure 7 is a control plane protocol stack based on QUIC provided in Example 1. Figure 8 is a user plane protocol stack based on QUIC provided in Example 1. Figure 9 is an interaction flowchart of a registration method provided in Example 1. As shown in Figure 9 , the following steps are included.

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

[0090] When the UE establishes the control plane connection with the PDG, the UE triggers a QUIC handshake process with the PDG based on another 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, and the UE and the PDG can start to exchange control plane signaling (such as control plane protocol messages) safely.

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

[0092] The registration request message comprises 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.

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

[0094] 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.

[0095] 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.

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

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

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

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

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

[0101] 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. Optionally, the registration response message can also include user plane data QoS information.

[0102] 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 messages.

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

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

[0105] After the control plane signaling process is completed, the UE also needs to establish a user plane connection with the PDG. As shown in the figure, the user plane message can be transmitted on the QUIC-based user plane connection between the UE and the PDG after being encapsulated by the encapsulation layer, or can be directly transmitted on the QUIC-based user plane connection between the UE and the PDG. Figure 8

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

[0107] If the registration response message in the above step includes the 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; 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; 3) encapsulation layer identification information (such as tunnel identification, string, etc.) for encapsulating user plane messages, then the encapsulation layer identification information is the encapsulation layer identification for subsequent user plane messages, which can be associated with the user plane QoS information.

[0108] In an embodiment, if the registration response message in the above step includes connection indication information, and the connection indication information indicates that the UE performs 0-RTT fast connection establishment, in the process performed in step 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.

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

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

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

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

[0113] 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 identification to be modified; the user plane connection release request message includes a user plane identification to be released.

[0114] Optionally, 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 procedure and the user plane connection release request procedure can be initiated by the UE, or by the PDG, or by the core network device.

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

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

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

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

[0119] 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.

[0120] Optionally, 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.

[0121] In an embodiment, if the registration response message in the above steps includes connection indication information, and the connection indication information indicates that the terminal device performs 0-RTT fast connection establishment, the following steps can also be performed.

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

[0123] 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 a key derived from the session ticket.

[0124] 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.

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

[0126] Figure 10 is a control plane protocol stack based on QUIC provided by example 2. Figure 11 is a user plane protocol stack based on QUIC provided by example 2. Figure 12 is an interaction flowchart of a registration method provided by example 2. As shown in Figure 12 , the following steps are included.

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

[0128] When the UE establishes a control plane connection with the PDG, the UE triggers a QUIC handshake process with the PDG based on the HTTP / 3-based control plane protocol. After the UE and the PDG verify the QUICFinished message, the control plane connection is considered to be established, and the UE and the PDG can start exchanging control plane signaling (such as control plane protocol messages) securely.

[0129] In an embodiment, during the execution of step S1210, the PDG can also send a QUIC extension frame to the UE. 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.

[0130] 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.

[0131] 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.

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

[0133] 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.

[0134] 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.

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

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

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

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

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

[0140] In an embodiment, the registration response message comprises information required for subsequent establishment of the user plane connection, such as at least one of user plane connection identification information and connection indication information used to indicate whether the UE performs 0-RTT fast connection establishment. Optionally, the registration response message can further comprise user plane data QoS information.

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

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

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

[0144] 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.

[0145] If the registration response message in the above step comprises 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 used for the QUIC connection; or 2) a QUIC connection ID used for the user plane connection, then the QUIC connection ID is the QUIC connection ID on the PDG side for the connection.

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

[0147] 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.

[0148] S1230, the UE sends user plane uplink messages to the PDG based on the user plane connection.

[0149] S1232, the PDG receives the user plane uplink messages sent by the UE.

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

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

[0152] 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.

[0153] Optionally, 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.

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

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

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

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

[0158] 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.

[0159] Optionally, 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.

[0160] In an embodiment, if the registration response message in the above steps includes connection indication information, and the connection indication information indicates that the terminal device performs 0-RTT fast connection establishment, the following steps can also be performed.

[0161] S1250, the UE sends a session resume request message to the PDG.

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

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

[0164] Example 3

[0165] Figure 13 is a schematic diagram of a UE switching from an access network 1 to an access network 2 provided by example 3. As shown, 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. Figure 13 Figure 14 is an interactive flowchart of a UE switching from an access network 1 to an access network 2 provided by example 3. As shown, it includes the following steps. Figure 14

[0166] 1, the UE is connected 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 the migration of the control plane connection and the migration of the user plane connection.

[0167] 2, the UE moves to the access network 2 due to movement or other reasons, and the local address of the UE has changed. At this time, the UE sends a PATH_CHALLENGE message to the PDG, which is directly sent using the control plane QUIC connection parameters in the access network 1, the purpose of which is to migrate the control plane connection to the access network 2 path.

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

[0169] 4, the UE sends a PATH_CHALLENGE message to the PDG, which is directly sent using the user plane QUIC connection parameters in the access network 1, the purpose of which is to migrate the user plane connection to the access network 2 path.

[0170] ​​5. The PDG sends a PATH_RESPONSE message to the UE through PATH_CHALLENGE message verification. The UE completes the user plane connection migration from access network 1 to access network 2 to the PDG.

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

[0172] Example 4

[0173] Figure 15 is a schematic diagram of a UE switching from an access network 1 to an access network 2 provided by Example 4. As shown, the access network 1 is connected to the PDG 1, the access network 2 is connected to the PDG 2, and the connection control management is based on the QUIC protocol. Figure 15 Figure 16 is an interaction flowchart of a UE switching from an access network 1 to an access network 2 provided by Example 4. As shown, it includes the following steps. Figure 16

[0174] 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.

[0175] 2. The UE moves to the access network 2 due to movement or other reasons, the local address of the UE has changed, the UE updates the connection state to the PDG 1, and migrates the connection 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 the local policy or interaction information with the core network. The PDG 1 informs the UE of the migration result and includes the 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.

[0176] 3. The UE sends a PATH_CHALLENGE message to the PDG 2, which is directly sent using the control plane QUIC connection parameters between the PDG 1, the purpose of which is to migrate the control plane connection to the PDG 2.

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

[0178] ​​5. The UE sends a PATH_CHALLENGE message to the PDG 2, which is sent directly using the user plane QUIC connection parameters between the UE and the PDG 1, with the purpose of migrating the user plane connection to the PDG 2.

[0179] 6. The PDG 2 verifies 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.

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

[0181] Figure 17 Figure 1 is a structural schematic diagram of a registration device provided in an embodiment, which can be configured in a PDG, as shown in the figure, the device comprises a processing module 100, a receiving module 101 and a sending module 102. Figure 17

[0182] 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 QUIC (Quick User Datagram Protocol Network Connection).

[0183] 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.

[0184] 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.

[0185] The receiving module 101 is configured to receive an authentication authorization message sent by the core network device.

[0186] The sending module 102 is configured to send a registration response message to the terminal device according to the authentication authorization message.

[0187] The registration device provided in the embodiment is used for implementing the registration method of the embodiment, 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. Figure 5

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

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

[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 (0-Round Trip Time) fast connection establishment.

[0191] In an embodiment, the user plane connection identification information includes at least one of the following: 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 the user plane message.

[0192] In an embodiment, the processing module 100 is further configured to establish the user plane connection with the terminal device according to the user plane protocol based on the QUIC.

[0193] 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.

[0194] In an embodiment, if the registration response message includes the 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 recovery parameter information to the terminal device.

[0195] The receiving module 101 is further configured to receive a session recovery request message sent by the terminal device after the user plane connection and / or the control plane connection established with the terminal device is released, the session recovery request message including session recovery parameter information.

[0196] The processing module 100 is further configured to recover the user plane connection and / or the control plane connection with the terminal device according to the session recovery request message.

[0197] In an embodiment, the session recovery parameter information includes a session ticket.

[0198] 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.

[0199] The sending module 102 is further configured to send the switching indication information to the terminal device.

[0200] 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 switching request message sent by the terminal device.

[0201] 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 switching request message.

[0202] The sending module 102 is further configured to send a path switching response message to the terminal device.

[0203] Figure 18 FIG. 2 is a structural schematic diagram of another registration device provided in an embodiment, which can be configured in a terminal device, as shown in the figure, the device comprises a processing module 200, a sending module 201 and a receiving module 202. Figure 18

[0204] The processing module 200 is configured to establish a control plane connection with a packet data gateway (PDG) based on a quick user datagram protocol (QUIC) based control plane protocol.

[0205] 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 comprising identification information and registration parameters of the terminal device.

[0206] The receiving module 202 is configured to receive a registration response message sent by the PDG.

[0207] The registration device provided in the embodiment is used to implement the registration method of the embodiment shown in FIG. 1, and the registration device provided in the embodiment has similar implementation principles and technical effects to the above-mentioned embodiments, and thus will not be described herein. Figure 6

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

[0209] ​​In an embodiment, when the control plane protocol based on the 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 with the PDG, 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 the network.

[0210] The sending module 201 is further configured to generate a registration request message according to the URI information.

[0211] 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 (0-Round Trip Time) fast connection establishment.

[0212] In an embodiment, the user plane connection identification information includes 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 the user plane message.

[0213] In an embodiment, the processing module 200 is further configured to establish a user plane connection with the PDG according to the user plane protocol based on the QUIC.

[0214] 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.

[0215] In an embodiment, if the registration response message includes the connection indication information and the connection indication information indicates that the terminal device performs the 0-RTT fast connection establishment, the receiving module 202 is further configured to receive session recovery parameter information sent by the PDG.

[0216] The sending module 201 is further configured to send a session recovery request message to the PDG after the user plane connection and / or the control plane connection established with the PDG is released, the session recovery request message including the session recovery parameter information.

[0217] In an embodiment, the session recovery parameter information includes a session ticket.

[0218] 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.

[0219] In one 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 a path switching request message to the PDG;

[0220] The receiving module 202 is further configured to receive a path switching response message sent by the PDG.

[0221] An embodiment of the present application further provides a packet data gateway, comprising: a processor, the processor being configured to implement the method provided in any embodiment of the present application when executing a computer program.

[0222] Figure 19 This is a schematic diagram of the structure of a packet data gateway provided by an embodiment. Figure 19 As shown, the packet data gateway includes a processor 60, a memory 61 and a communication interface 62; the number of the processor 60 in the packet data gateway can be one or more. Figure 19 The processor 60, the memory 61, and the communication interface 62 in the packet data gateway may be connected by a bus or other means. Figure 19 The term "bus" refers to one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures.

[0223] The memory 61, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the methods in the embodiments of the present application. The processor 60 executes the software programs, instructions, and modules stored in the memory 61 to execute at least one functional application and data processing of the packet data gateway, thereby implementing the above-mentioned method.

[0224] Memory 61 may include a program storage area and a data storage area. The program storage area may store an operating system and at least one application required for a function; the data storage area may store data generated based on the use of the terminal. Furthermore, memory 61 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state memory device. In some instances, memory 61 may include memory remotely located relative to processor 60, and such remote memory may be connected to a packet data gateway via a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a network, a mobile communication network, and combinations thereof.

[0225] The communication interface 62 can be configured to receive and send data.

[0226] The embodiment of the present application further provides a terminal device, comprising: a processor, the processor being configured to implement the method provided in any embodiment of the present application when executing a computer program.

[0227] Figure 20 This is a structural diagram of a UE provided in one embodiment. The UE can be implemented in various forms. The UE in this application may include but is not limited to mobile terminal devices such as mobile phones, smart phones, laptops, digital broadcast receivers, personal digital assistants (PDAs), tablet computers (PADs), portable multimedia players (PMPs), navigation devices, vehicle-mounted terminal devices, vehicle-mounted display terminals, vehicle-mounted electronic rearview mirrors, etc., as well as fixed terminal devices such as digital televisions (TVs) and desktop computers.

[0228] like Figure 20 As shown, UE 50 may 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, a power supply unit 59, and the like. Figure 20 A UE is shown including various components, but it should be understood that implementing all of the components shown is not a requirement. Greater or fewer components may alternatively be implemented.

[0229] 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.

[0230] 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.

[0231] 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.

[0232] 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 (EPROM), 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.

[0233] The computer readable signal medium can include a data signal propagating in baseband or propagating as a carrier wave in a propagated signal, bearing computer readable program code. Such propagated signal can take through various 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 storage medium, which can be used to carry or transmit a program for use by or in connection with an instruction execution system, apparatus or device.

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

[0235] 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).

[0236] The embodiments of the present application also 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.

[0237] The computer program product, in its implementation, can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++, 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).

[0238] 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.

[0239] 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

[0240] 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 the form of 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 name a few.

[0241] Any flowchart of the figures herein can represent program steps, or can represent interconnected logic circuits, modules, and functions, or can represent a combination of program steps and logic circuits, modules, and functions. The computer program can be stored on a memory. The memory can be of any type suitable to the local technical environment and can be implemented using any suitable data storage technology, such as, but not limited to, random access memory (RAM), read only memory (ROM), optical storage devices, and systems such as digital versatile disc (DVD) or CD-ROM, and the like. The computer readable media can include non-transitory storage media. The data processor can be of any type suitable to the local technical environment, and can include, but is not limited to, a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and a processor based on multi-core processor architecture, to name a few.

Claims

1. A registration method, characterized in that: Applicable to packet data gateway (PDG), including: Establishing a control plane connection with the terminal device according to a control plane protocol based on a Fast User Datagram Protocol network connection QUIC; receiving a registration request message sent by the terminal device based on the control plane connection, where the registration request message includes identification information and registration parameters of the terminal device; Sending an authentication request message to a core network device according to the identification information of the terminal device and the registration parameters; Receive the authentication and authorization message sent by the core network device, and send a registration response message to the terminal device based on the authentication and authorization message.

2. The registration method according to claim 1, characterized in that: The QUIC-based control plane protocol is other application layer protocols based on QUIC, or the control plane protocol of the third version of the Hypertext Transfer Protocol HTTP / 3.

3. The registration method according to claim 2, characterized in that: When the QUIC-based control plane protocol is an HTTP / 3 control plane protocol, when establishing a control plane connection with a terminal device, the method further includes: A QUIC extension frame is sent to the terminal device, where the QUIC extension frame includes uniform resource identifier (URI) information, where the URI information is used to indicate a resource location of related services provided by the network.

4. The registration method according to claim 1, wherein: The registration response message includes at least one of user plane connection identification information and connection indication information, and the connection indication information is used to indicate whether the terminal device performs zero round-trip time 0-RTT fast connection establishment.

5. The registration method according to claim 4, characterized in that: The user plane connection identification information includes at least one of the following: the UDP port number of the PDG, the QUIC connection identifier used for the user plane connection, and the encapsulation layer identification information used to encapsulate the user plane message.

6. The registration method according to claim 4, characterized in that: After sending the registration response message to the terminal device, the method further includes: Establishing a user plane connection with the terminal device according to a QUIC-based user plane protocol; Receive the user plane uplink message sent by the terminal device based on the user plane connection, and forward the user plane uplink message to the core network device; or receive the user plane downlink message sent by the core network device, and forward the user plane downlink message to the terminal device based on the user plane connection.

7. The registration method according to claim 6, characterized in that: If the registration response message includes connection indication information, and the connection indication information instructs the terminal device to perform 0-RTT fast connection establishment; further comprising: Sending session resumption parameter information to the terminal device; After the user plane connection and / or the control plane connection established with the terminal device is released, receiving a session resumption request message sent by the terminal device, where the session resumption request message includes the session resumption parameter information; Restore the user plane connection and / or the control plane connection with the terminal device according to the session resumption request message.

8. The registration method according to claim 7, characterized in that: The session resumption parameter information includes a session ticket.

9. The registration method according to claim 6, characterized in that: When establishing a user plane connection with a terminal device, it also includes: Receiving handover indication information sent by the core network device, where the handover indication information is used to indicate whether the core network device allows the terminal device to perform connection migration; Send the switching indication information to the terminal device.

10. The registration method according to claim 9, characterized in that: If the switching indication information indicates that the core network device allows the terminal device to perform connection migration; the method further includes: receiving a path switching request message sent by the terminal device; Switching 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 switch request message; Send a path switching response message to the terminal device.

11. A registration method, characterized in that: Applied to terminal equipment, including: Establishing a control plane connection with the packet data gateway PDG according to a control plane protocol based on a fast user datagram protocol network connection QUIC; Sending a registration request message to the PDG based on the control plane connection, where the registration request message includes identification information and registration parameters of the terminal device; Receive a registration response message sent by the PDG.

12. The registration method according to claim 11, characterized in that: The QUIC-based control plane protocol is other application layer protocols based on QUIC, or the control plane protocol of the third version of the Hypertext Transfer Protocol HTTP / 3.

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

14. The registration method according to claim 11, characterized in that: The registration response message includes at least one of user plane connection identification information and connection indication information, and the connection indication information is used to indicate whether the terminal device performs zero round-trip time 0-RTT fast connection establishment.

15. The registration method according to claim 14, characterized in that: The user plane connection identification information includes at least one of the following: the UDP port number of the PDG, the QUIC connection identifier used for the user plane connection, and the encapsulation layer identification information used to encapsulate the user plane message.

16. The registration method according to claim 14, characterized in that: After receiving the registration response message sent by the PDG, the method further includes: Establishing a user plane connection with the PDG according to a QUIC-based user plane protocol; Send a user plane uplink message to the PDG based on the user plane connection; or receive a user plane downlink message sent by the PDG based on the user plane connection.

17. The registration method according to claim 16, characterized in that: If the registration response message includes connection indication information, and the connection indication information instructs the terminal device to perform 0-RTT fast connection establishment; further comprising: Receiving session recovery parameter information sent by the PDG; After the user plane connection and / or the control plane connection established with the PDG is released, a session resumption request message is sent to the PDG, where the session resumption request message includes the session resumption parameter information.

18. The registration method according to claim 17, characterized in that: The session resumption parameter information includes a session ticket.

19. The registration method according to claim 16, wherein: When establishing a user plane connection with the PDG, the method further includes: Receive the switching indication information sent by the PDG, where the switching indication information is used to indicate whether the core network device allows the terminal device to perform connection migration.

20. The registration method according to claim 19, characterized in that: If the switching indication information indicates that the core network device allows the terminal device to perform connection migration; the method further includes: Sending a path switch request message to the PDG; Receive a path switching response message sent by the PDG.

21. A packet data gateway, characterized in that: include: processor; The processor is configured to implement the registration method according to any one of claims 1 to 10 when executing the computer program.

22. A terminal device, characterized in that: include: processor; The processor is configured to implement the registration method according to any one of claims 11 to 20 when executing the computer program.

23. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the registration method according to any one of claims 1 to 20 is implemented.

Images