A tunnel information sending method and device

Abstract

Embodiments of the present application provide a tunnel information sending method and device, wherein the method applied to a first endpoint of a tunnel comprises: sending a first user plane message to a second endpoint of the tunnel based on an address of the second endpoint, the first user plane message comprising tunnel information corresponding to the first endpoint. The tunnel information sending method and device provided by embodiments of the present application send tunnel information through a user plane message, shorten the time of tunnel establishment or modification, and reduce the processing overhead of a control plane function by reducing the number of session messages executed by a network function entity, thereby improving the efficiency of tunnel message exchange.

Description

Technical Field

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

[0002] The 5G system (5GS) follows the control and user plane separation (CUPS) feature. The 5G core network (5GC) control plane communicates through the Service Interface (SBI), while the 5GC user plane uses the GTP-U protocol.

[0003] GTP-U tunnels are used to forward packets between GTP-U entities. A GTP-U tunnel includes a Tunnel endpoint identifier (TEID), IP address, and UDP port number for each node. The UDP destination port number uses the registered port number 2152. The TEID indicates which GTP-U tunnel a specific T-PDU (raw packet) belongs to. During tunnel establishment, the receiving endpoint of the GTP-U tunnel locally allocates the TEID value and IP address that the sending end must use; this information is called tunnel information. Tunnel information is exchanged between GTP-U entities via control plane messages, such as 5GC SBIs and / or the NG Application Protocol (NGAP).

[0004] Therefore, after the receiving endpoint (access network side or UPF) of the 5GS N3 / N9 interface GTP-U tunnel allocates tunnel information locally, it first sends it to the control plane functional entity, and then sends it to the tunnel peer through the control plane functional entity, resulting in low tunnel information exchange efficiency. Summary of the Invention

[0005] To address the problems existing in the prior art, this application provides a method and apparatus for transmitting tunnel information.

[0006] In a first aspect, embodiments of this application provide a tunnel information transmission method, applied to a first endpoint of a tunnel, the method comprising:

[0007] Based on the address of the second endpoint of the tunnel, a first user plane message is sent to the second endpoint of the tunnel. The first user plane message includes tunnel information corresponding to the first endpoint of the tunnel.

[0008] Optionally, according to a tunnel information transmission method according to an embodiment of this application, the first user plane message includes any one or a combination of the following:

[0009] The first user plane message is a General Packet Radio Service User Plane Tunneling Protocol (GTP-U) signaling message;

[0010] The first user plane message is a user plane function UPF service based on a service-oriented interface;

[0011] The first user plane message is a first message used for tunnel information exchange.

[0012] Optionally, according to a tunnel information transmission method according to an embodiment of this application, the GTP-U signaling message includes any of the following:

[0013] The GTP-U signaling message is a new type of signaling message;

[0014] The GTP-U signaling message is a signaling message with a flag bit added to the message type;

[0015] The GTP-U signaling message is a signaling message with a new GTP-U extended header.

[0016] Optionally, according to one embodiment of the tunnel information transmission method of this application, the UPF service based on the service-oriented interface includes:

[0017] After the first endpoint of the tunnel assigns the tunnel information, it notifies the second endpoint of the tunnel through a Notify operation.

[0018] Optionally, according to a tunnel information sending method according to an embodiment of this application, the step of notifying the second endpoint of the tunnel via a Notify operation includes:

[0019] When a network function entity subscribes to tunnel information via Subscribe, it notifies the second endpoint of the tunnel via a Notify operation.

[0020] Optionally, according to a tunnel information sending method according to an embodiment of this application, the first user plane message further includes a second session identifier, which is used to distinguish the session to which the tunnel information belongs and corresponds to the second endpoint of the tunnel.

[0021] Optionally, according to one embodiment of the tunnel information transmission method of this application, before sending the first user plane message to the second endpoint of the tunnel, the method further includes:

[0022] Receive the address of the second endpoint of the tunnel and / or the second session identifier sent by the network function entity.

[0023] Optionally, according to one embodiment of the tunnel information transmission method of this application, the second session identifier includes:

[0024] Network Function Entity Identifier (NFI) and N4 Session Identifier (N4 Session ID), wherein the N4 Session ID corresponds to the second endpoint of the tunnel; or

[0025] Permanent Identity SUPI and Protocol Data Unit Session ID (PDU).

[0026] Optionally, according to one embodiment of the tunnel information transmission method of this application, the method further includes any one or a combination of the following:

[0027] After allocating the tunnel information corresponding to the second session identifier, the tunnel information is sent to the network function entity;

[0028] The system receives a second user plane message sent by the second endpoint of the tunnel. The second user plane message includes a first session identifier and tunnel information corresponding to the second endpoint of the tunnel. The first session identifier is used to distinguish the session to which the tunnel information belongs and corresponds to the first endpoint of the tunnel.

[0029] Optionally, according to a tunnel information transmission method according to an embodiment of this application, the first session identifier includes:

[0030] Network Function Entity Identifier (NFI) and N4 Session Identifier (N4 Session ID), wherein the N4 Session ID corresponds to the first endpoint of the tunnel; or

[0031] Permanent Identity SUPI and Protocol Data Unit Session ID (PDU).

[0032] Optionally, according to one embodiment of the tunnel information transmission method of this application, when the first endpoint of the tunnel is a newly inserted endpoint of the target tunnel, the method further includes:

[0033] The system receives relevant information sent by a network function entity, including tunnel information corresponding to one or more associated tunnel endpoints related to the target tunnel.

[0034] Optionally, according to one embodiment of the tunnel information transmission method of this application, the relevant information further includes the address and / or session identifier corresponding to the associated tunnel endpoint related to the target tunnel, wherein the session identifier is used to distinguish the session to which the tunnel information belongs;

[0035] The method further includes:

[0036] Based on the address corresponding to each associated tunnel endpoint, a user plane message is sent to each associated tunnel endpoint. The user plane message includes tunnel information corresponding to the first tunnel endpoint and a session identifier corresponding to the associated tunnel endpoint.

[0037] Optionally, according to one embodiment of the tunnel information transmission method of this application, the method is applied to the N3 and / or N9 interfaces.

[0038] Secondly, embodiments of this application also provide a tunnel information transmission method, applied to a network functional entity, the method comprising:

[0039] Send the second session identifier and / or the address of the second endpoint of the tunnel to the first endpoint of the tunnel;

[0040] The address of the second endpoint of the tunnel is used by the first endpoint of the tunnel to send user plane messages to the second endpoint of the tunnel. The user plane messages include tunnel information corresponding to the first endpoint of the tunnel. The second session identifier is used to distinguish the session to which the tunnel information belongs and corresponds to the second endpoint of the tunnel.

[0041] Optionally, according to one embodiment of the tunnel information transmission method of this application, the method further includes any one or a combination of the following:

[0042] Receive the tunnel information sent by the first endpoint of the tunnel;

[0043] Send a first relevant information and a second relevant information to the newly inserted tunnel endpoint; the first relevant information includes tunnel information corresponding to the first tunnel endpoint, and the second relevant information includes tunnel information corresponding to the second tunnel endpoint.

[0044] Optionally, according to one embodiment of the tunnel information transmission method of this application, the first related information further includes an address and / or a first session identifier corresponding to the first endpoint of the tunnel, wherein the first session identifier is used to distinguish the session to which the tunnel information belongs and corresponds to the first endpoint of the tunnel;

[0045] The second relevant information also includes the address corresponding to the second endpoint of the tunnel and / or the second session identifier.

[0046] Optionally, according to one embodiment of the tunnel information transmission method of this application, the second session identifier includes:

[0047] Network Function Entity Identifier (NFI) and N4 Session Identifier (N4 Session ID), wherein the N4 Session ID corresponds to the second endpoint of the tunnel; or

[0048] Permanent Identity Item (SUPI) and Protocol Data Unit (PDU) Session ID;

[0049] The first session identifier includes:

[0050] Network Function Entity Identifier (NFI) and N4 Session Identifier (N4 Session ID), wherein the N4 Session ID corresponds to the first endpoint of the tunnel; or

[0051] Permanent Identity SUPI and Protocol Data Unit Session ID (PDU).

[0052] Thirdly, embodiments of this application also provide a tunnel first endpoint device, including a memory, a transceiver, and a processor.

[0053] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer program from the memory and implementing the steps of the tunnel information transmission method as described in the first aspect above.

[0054] Fourthly, embodiments of this application also provide a network functional entity, including a memory, a transceiver, and a processor:

[0055] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer program from the memory and implementing the steps of the tunnel information transmission method as described in the second aspect above.

[0056] Fifthly, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing the processor to perform the steps of the tunnel information transmission method described in the first aspect above.

[0057] In a sixth aspect, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing the processor to perform the steps of the tunnel information transmission method described in the second aspect above.

[0058] The tunnel information sending method and apparatus provided in this application send tunnel information through user plane messages, which shortens the time for tunnel establishment or modification, and reduces the processing overhead of control plane functions by reducing the number of session messages executed by network function entities, thereby improving the efficiency of tunnel message exchange. Attached Figure Description

[0059] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0060] Figure 1 This is a schematic diagram of the 5GS transmission process of the GTP-U tunnel provided in this application;

[0061] Figure 2 This is a schematic diagram of the N4 session establishment process provided in this application;

[0062] Figure 3 This is a schematic diagram of the GTP-U tunnel establishment process provided in this application;

[0063] Figure 4 This is a schematic diagram of the GTP-U tunnel modification process provided in this application;

[0064] Figure 5 This is one of the schematic flowcharts of the tunnel information transmission method provided in the embodiments of this application;

[0065] Figure 6 This is a schematic diagram of the GTP-U tunnel establishment process based on user plane messages provided in an embodiment of this application;

[0066] Figure 7 This is a schematic diagram of the GTP-U tunnel modification process based on user plane messages provided in an embodiment of this application;

[0067] Figure 8 This is the second schematic flowchart of the tunnel information transmission method provided in the embodiments of this application;

[0068] Figure 9 This is the third schematic diagram of the tunnel information transmission method provided in the embodiments of this application;

[0069] Figure 10 This is the fourth schematic flowchart of the tunnel information transmission method provided in the embodiments of this application;

[0070] Figure 11 This is a schematic diagram of the structure of the tunnel first end device provided in the embodiment of this application;

[0071] Figure 12 This is a schematic diagram of the structure of the network functional entity provided in the embodiments of this application;

[0072] Figure 13 This is one of the schematic diagrams of the tunnel information transmission device provided in the embodiments of this application;

[0073] Figure 14 This is the second schematic diagram of the tunnel information transmission device provided in the embodiments of this application. Detailed Implementation

[0074] In the embodiments of this application, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0075] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0076] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0077] The technical solutions provided in this application can be applied to various systems, especially 5G systems. For example, applicable systems include Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Long Term Evolution Advanced (LTE-A), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), and 5G New Radio (NR). All of these systems include terminal equipment and network equipment. The systems may also include a core network component, such as Evolved Packet System (EPS) and 5G system (5GS).

[0078] The terminal device (e.g., UE) involved in the embodiments of this application can be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. The name of the terminal device may differ in different systems; for example, in a 5G system, the terminal device can be called User Equipment (UE). The wireless terminal device can communicate with one or more core networks (CNs) via a Radio Access Network (RAN). The wireless terminal device can be a mobile terminal device, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal device, for example, a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device. They exchange voice and / or data with the radio access network. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user device, but this application does not limit the terminology.

[0079] The network device involved in this application embodiment can be a base station, which may include multiple cells providing services to terminals. Depending on the specific application, a base station may also be called an access point, or a device in an access network that communicates with a wireless terminal device through one or more sectors on the air interface, or other names. The network device can be used to exchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The network device can also coordinate the attribute management of the air interface. For example, the network equipment involved in the embodiments of this application can be a base transceiver station (BTS) in a Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), a NodeB in a wide-band Code Division Multiple Access (WCDMA) system, an evolved Node B (eNB or e-NodeB) in a long term evolution (LTE) system, a 5G base station (gNB) in a next generation system, a Home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in the embodiments of this application. In some network structures, the network equipment may include centralized unit (CU) nodes and distributed unit (DU) nodes, and the centralized unit and distributed unit may be geographically separated.

[0080] Since its inception, mobile communications have used the General Packet Radio Service User Plane Tunneling Protocol (GTP) for data domain communication. GTP-C is the control plane protocol, used for establishing, modifying, and deleting session tunnels; GTP-U is the user plane protocol, used for data plane transmission between the mobile network radio access network and the core network, as well as within the core network.

[0081] With the emergence and development of 5G, the 5G system (5GS) architecture is defined as a service-based architecture (SBA). The 5G core network (5GC) control plane functions no longer use GTP-C, but instead interact through Service-Based Interfaces (SBI). However, the 5G core network data plane remains consistent with 4G, still using the GTP-U protocol, but extending it with a QoS Flow Identifier (QFI) to better meet the needs of 5G data plane forwarding.

[0082] 5GS adheres to the Control and User Plane Separation (CUPS) principle. The Session Management Function (SMF) and User Plane Function (UPF) communicate via the N4 interface. The N4 control plane uses the Packet Forwarding Control Protocol (PFCP) for communication, while the N4 data plane uses the GTP-U protocol. The N3 and N9 interfaces of the user plane also use the GTP-U protocol.

[0083] GTP-U tunnels are used to forward messages between GTP-U entities. A GTP-U tunnel includes a Tunnel Endpoint Identifier (TEID), IP address, and UDP port number for each node. GTP-U messages are sent between GTP user plane tunnels and contain GTP-U signaling messages or G-PDU messages.

[0084] A GTP-encapsulated User Plane Data Unit (G-PDU) is a regular user plane message carrying a raw Transport Protocol Data Unit (T-PDU). The T-PDU may be an IP datagram, Ethernet, or unstructured PDU data frame from the UE or an external DN. GTP-U signaling messages are used for user plane path management or user plane tunnel management. The GTP-U message header format is shown in Table 1.

[0085] Table 1. GTP-U Message Header Format

[0086]

[0087]

[0088] The GTP header is of variable length and contains a fixed 8-byte field, as well as optional fields for sequence number, N-PDU number, and next extension header type. The GTP-U message header fields are shown in Table 2.

[0089] Table 2. GTP-U Message Header Fields

[0090]

[0091]

[0092] The Tunnel Endpoint Identifier (TEID) in the GTP header indicates which GTP-U tunnel a specific T-PDU belongs to. In this way, data packets are multiplexed and demultiplexed by GTP-U between specific pairs of tunnel endpoints. TEID values ​​are exchanged between GTP-U entity pairs using control plane protocols, such as GTPv1-C and RANAP, GTPv2-C and S1-AP, 5GC SBIs, and / or NGAP.

[0093] However, in the following GTP-U signaling messages, TEID is set to all zeros:

[0094] Echo Request / Response;

[0095] Supported Extension Headers notification messages;

[0096] Error Indication message.

[0097] As shown in Table 3, GTP-U messages include G-PDU messages carrying the original data packet T-PDU and GTP-U signaling messages. G-PDUs may include extension headers but should not include any information elements (IEs). GTP-U signaling information is further divided into path management messages and tunnel management messages. Path management messages include: Echo Request messages, Echo Response messages, and Supported Extension Headers Notification messages; tunnel management messages include: Error Indication, End Marker, and Tunnel Status.

[0098] Table 3. GTP-U Messages

[0099]

[0100]

[0101] If GTP-U needs to expand message types in the future, the TS29.060 document describing the GTP protocol shows that the reserved unused message types are 0, 8-15, 24-25, 63-69, 106-111, 122-127, 130-239, and 242-252.

[0102] GTP-U signaling messages may include multiple IEs. GTP information elements should use TLV (Type, Length, Value) or TV (Type, Value) encoding format. Within the signaling message, information elements should be sorted in ascending order by the type field. The Length field contains the length of the information element (Value), excluding the lengths of the Type and Length fields.

[0103] When using the TV format, bit 8 in the type field is set to 0 (i.e., 0-127), and when using the TLV format, it is set to 1 (i.e., 128 and above).

[0104] Since the type field is 8 bits, the default supported IE type range is 0-255. If the IE Type Value is 238, then the supported extended types are 2 bytes (i.e., 236-65535, all of which are currently reserved and unused). Information elements with IE type extended fields are shown in Table 4.

[0105] Table 4. Information Elements with IE Type Extended Fields

[0106]

[0107] The existing protocol describes the GTP-U information elements as shown in Table 5, of which 231-237 are reserved and unused.

[0108] Table 5. Information Elements (IEs) in GTP-U

[0109] 0-13 TV Reserved in 3GPP TS 29.060 14 TV Recovery 15 TV Reserved in 3GPP TS 29.060 16 TV Tunnel Endpoint Identifier Data I 17-132 TV / TLV Reserved in 3GPP TS 29.060 133 TLV GTP-U Peer Address 134-140 TLV Reserved in 3GPP TS 29.060 141 TLV Extension Header Type List 142-229 TLV Reserved in 3GPP TS 29.060 230 TLV GTP-U Tunnel Status Information 231-237 TLV Spare. For future use. 238-254 TLV Reserved in 3GPP TS 29.060 255 TLV Private Extension

[0110] Figure 1 This is a schematic diagram of the 5GS transmission process of the GTP-U tunnel provided in this application, as follows: Figure 1As shown, the 5GS uplink data transmission process is as follows: The UE sends data (internal IP header and payload), which is transmitted to the base station (RAN) via the radio channel. The base station encapsulates the UE data packet into a GTP-U message, setting the TEID in the GTP-U header to the tunnel peer identifier "1", and sends it to the N3 UPF (UPF terminating N3 reference point), i.e., UPF1 in the diagram, through the N3 interface. The N3 UPF decapsulates the GTP-U message, obtains the corresponding TEID and other information, determines the tunnel to which the message belongs, executes Packet Detection Rule (PDR) and Forwarding Action Rule (FAR) behaviors, and recapsulates the GTP-U message, setting the TEID to "2", and forwards it to UPF2 (PSA) through the N9 interface. UPF2 is the PDU Session Anchor (PSA). UPF2 (PSA) decapsulates the GTP-U message to obtain the data sent by the UE, and sends it to the external network DN through the N6 interface according to the routing forwarding rules. The reverse is the downlink data transmission process.

[0111] A GTP-U tunnel includes a TEID, IP address, and UDP port number identifier for each node at the tunnel endpoints. The UDP destination port number is the registered port number 2152. Therefore, during tunnel establishment, the receiving endpoint of the GTP-U tunnel needs to locally allocate the TEID value and IP address required by the sending endpoint and pass them to the sending endpoint. The TEID and IP address identifying the tunnel are called tunnel information.

[0112] The N4 session establishment procedure is used by the UPF to create an initial N4 session context for a PDU session. The SMF assigns a new N4 Session ID and provides it to the UPF. The N4 Session ID is stored by both entities and used to identify the N4 session context during their interactions. The SMF also stores the relationship between the UE's N4 Session ID and the PDU session.

[0113] Figure 2 This is a schematic diagram of the N4 session establishment process provided in this application, such as... Figure 2 As shown, the N4 session establishment process includes:

[0114] 1. The SMF receives a trigger requesting the establishment of a new PDU session or the modification of the UPF of an existing PDU session.

[0115] 2. The SMF sends an N4 session establishment request message to the UPF, which contains structured control information defining the behavior required by the UPF, including PDR (Packet Detection Rule) and FAR (Forwarding Action Rule).

[0116] 3. The UPF responds using an N4 session establishment response message, which contains any information that the UPF must provide to the SMF in response to the control information received.

[0117] 4. The SMF interacts with the network function that triggered this process (such as the AMF or PCF).

[0118] The 5G core network interacts through Service Interfaces (SBIs). In Release 15, service interfaces were only for the control plane; user plane network elements, such as UPFs, did not provide service interfaces for other network elements to use. In Release 16, user plane network functions and other entities were further transformed into service interfaces to provide services to the outside world.

[0119] The UPF service interface is described below:

[0120] Within 5GC, UPF provides services to NEF and AF through the Nupf service interface. UPF supports the following functions: notifying QoS monitoring information.

[0121] The content of UPF service-oriented architecture is shown in Table 6:

[0122] Table 6. NF Services Provided by UPF

[0123] Nupf_EventExposure Notify Subscribe / Notify NEF,AF

[0124] The Nupf_EventExposure service can expose UPF-related information to other network functions (NFs). One operation of this service is to notify other NFs of PDU session events.

[0125] The following event can be notified to an NF consumer: QoS Monitoring for URLLC. This notification may include information such as QoS monitoring results, such as the end-to-end latency of a specific QoS flow for a specific PDU session.

[0126] As the standardization of UPF services is still in its early stages, the 3GPP protocol currently provides relatively few UPF services and related operational details, but more UPF services may emerge in the future.

[0127] The basic process of GTP-U tunnel management includes GTP-U tunnel establishment and GTP-U tunnel modification.

[0128] GTP-U tunnel construction:

[0129] Figure 3 This is a schematic diagram of the GTP-U tunnel establishment process provided in this application. It can be understood that there is no strict order of the steps in the diagram, such as steps 1.1 and 1.2.

[0130] like Figure 3 As shown, the GTP-U setup process includes:

[0131] (1) The SMF sends an N4Session EstablishmentRequest message to each of the two UPFs at both ends of a GTP-U tunnel. Before establishing the N4 session, the SMF first assigns an N4 Session ID to the N4 session. The request includes structured control information such as PDR and FAR that define the behavior required by the UPF, and an N4Session ID used to identify the N4 session context.

[0132] (2) Upon receiving the N4 Session Establishment Request, the UPF performs the actions required for the structured control information and assigns the required UL and / or DL ​​CN Tunnel Info, including TEID and IP address, to the N4 session.

[0133] (3) The UPF replies to the SMF with an N4 Session Establishment Response message, which carries TunnelInfo.

[0134] (4) The SMF sends an N4Session ModificationRequest message to each of the two UPFs at both ends of a GTP-U tunnel, carrying the Tunnel Info of the other end of the tunnel.

[0135] (5) The UPF stores the Tunnel Info and replies via N4 Session Establishment / ModificationResponse.

[0136] GTP-U tunnel modification:

[0137] If the UPF at one end of a GTP-U tunnel changes, such as by modifying / inserting / deleting a UPF, then the Tunnel Info of a certain endpoint of that GTP-U tunnel needs to be modified. Figure 4 This is a schematic diagram of the GTP-U tunnel modification process provided in this application, such as... Figure 4 As shown, if in Figure 4 After the tunnel shown is established, a UPF is inserted. The basic process of inserting the UPF involving N9 tunnel modification is as follows:

[0138] (1) The SMF sends an N4 Session Establishment Request message to the inserted UPF. The request includes structured control information such as PDR and FAR that define the behavior required by the UPF, N4Session ID for identifying the N4 session context, and Tunnel Info of the tunnel peer.

[0139] (2) After receiving the message, the inserted UPF stores the Tunnel Info of the tunnel peer and allocates the UL and DL Tunnel Info locally for this session;

[0140] (3) The allocated Tunnel Info is carried to the SMF in the N4 Session Establishment Response;

[0141] (4) The SMF sends N4 SessionModification Request messages to the UPFs at the two tunnel ends involved in the newly inserted UPF.

[0142] (5) UPF responds with N4 Session Modification Response message.

[0143] 5GS introduces the CUPS feature, where the control plane function (SMF) and user plane function (UPF) are separated. Tunnel Info from both ends of a GTP-U tunnel needs to be forwarded to the user plane function at the other end of the tunnel via the control plane function. This presents the following main problems:

[0144] Long tunnel establishment / modification time: Exchanging Tunnel Info via control plane messages results in long tunnel information exchange time and large delays in tunnel establishment / modification.

[0145] High overhead of control plane functions: Tunnel Info needs to exchange information through control plane functions, resulting in a large number of N4 Session Modification Requests / Responses executed by SMF, which increases the processing overhead of control plane functions.

[0146] refer to Figure 5 , Figure 5 This is one of the schematic flowcharts of a tunnel information transmission method provided in this application embodiment. The method can be applied to the first endpoint of a tunnel, including:

[0147] Step 510: Based on the address of the second endpoint of the tunnel, send a first user plane message to the second endpoint of the tunnel. The first user plane message includes tunnel information corresponding to the first endpoint of the tunnel.

[0148] Specifically, the first endpoint of the tunnel refers to the receiving end of the GTP-U tunnel, and the second endpoint of the tunnel refers to the sending end of the GTP-U tunnel. The tunnel information corresponding to the first endpoint includes the tunnel endpoint identifier (TEID) generated by the first endpoint and used by the second endpoint, as well as the address used for data routing. It is understood that the address can be an IP address or other forms of address, such as a UPF domain name. This application embodiment does not limit the specific form of the address.

[0149] The first user plane message is sent to the second endpoint of the tunnel. The destination address of the first user plane message is the address of the second endpoint of the tunnel. The address of the second endpoint of the tunnel may be pre-stored by the first endpoint of the tunnel or pre-obtained from other network functional entities or nodes. For example, if the first endpoint of the tunnel has sent a message to the second endpoint of the tunnel or received a message sent by the second endpoint of the tunnel before the tunnel was established, the first endpoint of the tunnel stores the address of the second endpoint of the tunnel.

[0150] The tunnel information sending method provided in this application involves the first endpoint of the tunnel sending tunnel information to the second endpoint of the tunnel via user plane messages. Compared with the prior art method where tunnel information is first sent to the control plane functional entity and then to the tunnel peer, the tunnel information sending method of this application shortens the tunnel establishment or modification time and reduces the processing overhead of the control plane function by reducing the number of session messages executed by the network functional entity. Taking the Session Management Function Entity (SMF) as an example, it reduces the number of N4 Session Modification Request / Response executed by the SMF, thereby improving the efficiency of tunnel message exchange.

[0151] Optionally, the first user plane message further includes a second session identifier, which is used to distinguish the session to which the tunnel information belongs and corresponds to the second endpoint of the tunnel.

[0152] Specifically, the first user plane message also includes a second session identifier. The second endpoint of the tunnel can determine the PDU session corresponding to the second session identifier based on the second session identifier, thereby determining the session corresponding to the tunnel information carried in the first user plane message.

[0153] Optionally, before sending the first user plane message to the second endpoint of the tunnel, the method further includes:

[0154] Receive the address of the second endpoint of the tunnel and / or the second session identifier sent by the network function entity.

[0155] In one embodiment, an N4 Establish Request message is received from a Session Management Function (SMF) entity. The N4 Establish Request message includes the address of the second tunnel endpoint and the second session identifier. The first tunnel endpoint allocates tunnel information and sends a first user plane message carrying the tunnel information and the second session identifier to the second tunnel endpoint. The destination address of the first user plane message is the address of the second tunnel endpoint sent by the SMF. It is understood that the first tunnel endpoint may have pre-stored the second session identifier, for example, by transmitting this information in a previous N4 Request message.

[0156] Optionally, the second session identifier includes:

[0157] Network Function Entity Identifier (NFI) and N4 Session Identifier (N4 Session ID), wherein the N4 Session ID corresponds to the second endpoint of the tunnel; or

[0158] Permanent Identity SUPI and Protocol Data Unit Session ID (PDU).

[0159] In the case where the second session identifier is a Network Function Entity (NF) identifier and an N4 session identifier (N4Session ID), the NF may include an SMF (Signal Function Entity) or other NFs related to the GTP-U tunnel. An N4 session corresponding to the PDU session is established between the NF and the UPF. The NF assigns an N4 Session ID to the N4 session. Both the NF and the UPF store the N4 Session ID, which is used to identify the N4 session context during interaction between the NF and the UPF. It is understood that the NF and the UPF can use the N4 interface or other interfaces to establish sessions of other interface types. The session types established between the NF and the UPF based on other interfaces and their corresponding session identifiers should also fall within the scope of protection of this application. Based on the NF identifier and the N4 session identifier, the second endpoint of the tunnel can uniquely identify a PDU session or an N4 session, thereby determining the session to which the tunnel information carried in the first user plane message belongs.

[0160] In the case where the second session identifier is a Permanent Identity Item (SUPI) and a Protocol Data Unit Session Identifier (PDU SessionID), the SUPI refers to the identity of the User Equipment (UE) initiating the PDU session, and the PDU Session ID is assigned by the UE to the PDU session it initiates, used to uniquely identify the Packet Data Unit session of the User Equipment. Based on the SUPI and PDU Session ID, the second endpoint of the tunnel can uniquely determine a PDU session, thereby determining the session to which the tunnel information carried in the first user plane message belongs.

[0161] It is understandable that, since there is a one-to-one correspondence between PDU sessions and N4 sessions, the session to which the tunnel information belongs can be either a PDU session or an N4 session.

[0162] Optionally, the method further includes any one or a combination of the following:

[0163] After allocating the tunnel information corresponding to the second session identifier, the tunnel information is sent to the network function entity;

[0164] The system receives a second user plane message sent by the second endpoint of the tunnel. The second user plane message includes a first session identifier and tunnel information corresponding to the second endpoint of the tunnel. The first session identifier is used to distinguish the session to which the tunnel information belongs and corresponds to the first endpoint of the tunnel.

[0165] Sending the tunnel information to the network function entity after allocating the tunnel information corresponding to the second session identifier means that after the first endpoint of the tunnel allocates the tunnel information for use by the second endpoint of the tunnel, it sends the tunnel information to the network function entity. After receiving the tunnel information sent by the first endpoint of the tunnel, the network function entity stores the tunnel information and can send the tunnel information to other network elements that need the tunnel information, thereby improving data transmission efficiency.

[0166] Receiving the second user plane message sent by the second endpoint of the tunnel means that the first endpoint of the tunnel receives the second user plane message sent by the second endpoint of the tunnel. The second user plane message includes tunnel information allocated by the second endpoint of the tunnel for use by the first endpoint of the tunnel. The second user plane message also includes a first session identifier corresponding to the first endpoint of the tunnel. The first endpoint of the tunnel can identify the dialogue to which the tunnel information carried in the second user plane message belongs based on the first session identifier.

[0167] Optionally, the first session identifier includes:

[0168] Network Function Entity Identifier (NFI) and N4 Session Identifier (N4 Session ID), wherein the N4 Session ID corresponds to the first endpoint of the tunnel; or

[0169] Permanent Identity SUPI and Protocol Data Unit Session ID (PDU).

[0170] The first session identifier corresponds to the first endpoint of the tunnel and is used by the first endpoint to distinguish the session to which the received tunnel information belongs. For an introduction to Network Function Entity Identifiers (NFIs) and N4 Session IDs, as well as SUPI and PDU Session IDs, please refer to the above descriptions; they will not be repeated here.

[0171] refer to Figure 6 , Figure 6 This is a schematic diagram of the GTP-U tunnel establishment process based on user plane messages provided in an embodiment of this application. The GTP-U tunnel establishment steps are as follows:

[0172] (1) The SMF sends an N4 Session Establishment Request Message to the two UPFs at both ends of a GTP-U tunnel.

[0173] With UPF1 as the first endpoint of the tunnel and UPF2 at the other end as the second endpoint, UPF1 allocates tunnel information including TEID and address for UPF2 to send GTP-U messages to UPF1. The case where UPF2 is the first endpoint of the tunnel will not be described further.

[0174] Before establishing an N4 session, the SMF first assigns an N4 Session ID to the N4 session. It can be understood that the SMF has established a first N4 session with UPF1, and a second N4 session with UPF2. Therefore, the N4 Session ID assigned by the SMF for the first N4 session corresponds to UPF1, and the N4 Session ID assigned by the SMF for the second N4 session corresponds to UPF2. The request message contains structured control information such as PDR and FAR that define the required behavior of the UPF, an N4 Session ID used to identify the N4 session context, and the IP address and session identifier of the other UPF. The session identifier can be the SMF ID and N4Session ID, or it can be the SUPI and PDU Session ID, etc.

[0175] (2) Upon receiving the N4 Session Establishment Request, the UPF performs the actions required for the structured control information and assigns the required UL and / or DL ​​CN Tunnel Info, including TEID and IP address, to the N4 session.

[0176] (3) After the UPF allocates the Tunnel Info, it sends the allocated Tunnel Info to another UPF at the tunnel peer through the user plane message. The destination address of the user plane message is the address of the peer. The notification carries the UL or DL ​​identifier and the session identifier corresponding to the peer, which is used by the UPF at the tunnel peer to identify the tunnel to which the Tunnel Info belongs.

[0177] Optionally, after receiving the Tunnel Info message, the tunnel peer can directly store the Tunnel Info information if a session-related context has already been established. Otherwise, the Tunnel Info can be temporarily stored, and a timer can be set. If no relevant N4 message is received after the timer expires, an abnormal situation can be considered to have occurred. In this case, the UPF should send a relevant abnormal signal to the SMF; the specific method is beyond the scope of this patent.

[0178] (4) After sending Tunnel Info, UPF replies to SMF with N4 Session Establishment Response message, which still carries Tunnel Info.

[0179] Understandably, for Figure 6 The order of steps 1.1 and 1.2 is not limited. Steps 2.1 and 2.2, 3.1 and 3.2, and 4.1 and 4.2 are processed in the same way.

[0180] Optionally, the first user plane message includes any one or a combination of the following:

[0181] The first user plane message is a General Packet Radio Service User Plane Tunneling Protocol (GTP-U) signaling message;

[0182] The first user plane message is a user plane function UPF service based on a service-oriented interface;

[0183] The first user plane message is a first message message used for tunnel information exchange, and the first message message may be a newly defined message message.

[0184] For the first user plane message to be a first message message used for tunnel information exchange, the first message message can be a newly defined message message. A newly defined message message refers to a newly defined message message that is different from existing message types and is used for tunnel information exchange. The first message message can be any message message used for information transmission between UPFs. For example, it can include newly defined IPv6 extension headers, new network layer messages, or new IP-based upper-layer protocols. It should be understood that the above message messages are merely examples for ease of understanding and should not constitute any limitation on this application; other types of message messages that can realize tunnel information transmission and / or exchange functions, whether appearing in the art or appearing in the future, can also be applied here.

[0185] The first user plane message being a General Packet Radio Service User Plane Tunneling Protocol (GTP-U) signaling message means that a GTP-U signaling message carrying tunnel information can be constructed as the first user plane message.

[0186] Optionally, the GTP-U signaling message includes any of the following:

[0187] The GTP-U signaling message is a new type of signaling message;

[0188] The GTP-U signaling message is a signaling message with an added flag bit in the message type.

[0189] The GTP-U signaling message is a signaling message with a new GTP-U extended header.

[0190] For the GTP-U signaling message that is a new message type, according to the TS29.060 document of the GTP protocol, the reserved unused message types are 0, 8-15, 24-25, 63-69, 106-111, 122-127, 130-239 and 242-252. Therefore, a message type can be selected from the reserved unused message types as the GTP-U signaling message that supports tunnel information exchange, which can be called a tunnel information signaling message.

[0191] Referring to Table 7, Table 7 shows the information elements (IEs) of the tunnel information signaling message provided in the embodiments of this application.

[0192] Table 7. Information Elements of Tunnel Information Signalling Messages

[0193] Tunnel Endpoint Identifier Data I Mandatory GTP-U Peer Address Mandatory GTP-U Peer Session Identifier Mandatory Private Extension Optional

[0194] Tunnel Endpoint Identifier Data I is the TEID assigned to the first endpoint of the tunnel, and GTP-U PeerAddress is the address assigned to the first endpoint of the tunnel. The GTP-U Peer SessionIdentifier is a newly defined IE, and its IE type number can be one of the reserved 231-237. This information element is designed as shown, mainly containing the UL or DL ​​identifier of the tunnel to which the tunnel information belongs, and a session identifier to distinguish the session to which the tunnel information belongs. The session identifier can be SMF ID and N4 Session ID, or SUPI and PDU Session ID, etc.

[0195] Table 8. Information Elements of GTP-U Node Session Identifier

[0196]

[0197] For the GTP-U signaling message, which is a signaling message with an added flag bit in the message type, the TEID can be carried in the GTP-U header of the existing message type. The UL / DL flag can also utilize bit 4 of the first byte of the GTP-U header, where 0 indicates that Tunnel Info exchange is not supported, and 1 indicates that Tunnel Info exchange is supported. For example, a flag bit is added to the Tunnel Status message to enable the sending of tunnel information allocated by the first endpoint of the tunnel to the second endpoint of the tunnel.

[0198] For the GTP-U signaling message with the new GTP-U extended header, referring to Tables 1 and 2, it can be seen that GTP-U supports extended headers (also called extended headers, the name is not limited in this application), and the format is shown in Table 9.

[0199] Table 9. GTP-U supports extended headers

[0200] 1 Extend header length 2-m Extend Header Content m+1 Next Extension Header Type

[0201] The extended headers defined in the existing protocols are shown in Table 10:

[0202] Table 10. Extension headers defined in existing protocols

[0203]

[0204] Therefore, a new GTP-U extension header can be defined to support the transmission of tunnel information. For example, "10001010" is used to represent "Tunnel Info Container".

[0205] For the first user plane message being a user plane function UPF service based on a service-oriented interface, for example, the Nupf_EventExposure service can be used as the first user plane message. The Nupf_EventExposure service can expose UPF-related information to other network function entities.

[0206] Specifically, the NF services provided by UPF as shown in Table 6 are extended, and the extended NF services are shown in Table 11. UPF is added as a consumer. The original protocol Nupf_EventExposure notification events include QoS monitoring results. This application extends the extension to include tunnel information exposure.

[0207] Table 11. NF Services Provided by UPF in this Application

[0208] Nupf_EventExposure Notify Subscribe / Notify NEF, AF, UPF

[0209] Optionally, the UPF service based on the service-oriented interface includes:

[0210] After the first endpoint of the tunnel allocates the tunnel information, it notifies the second endpoint of the tunnel through a Notify operation. For example, when an N4 session is established or modified, the SMF carries the UPF information of the tunnel peer. After the first endpoint of the tunnel allocates the tunnel information, it provides the tunnel information to the tunnel peer (the second endpoint of the tunnel) through the Notify operation of Nupf_EventExposure.

[0211] The notification of the second endpoint of the tunnel via the Notify operation includes:

[0212] When a network function entity subscribes to tunnel information via Subscribe, it notifies the second endpoint of the tunnel via a Notify operation.

[0213] Specifically, based on the Namf_EventExposure service, a network function entity can subscribe to and receive event notifications on its own or on behalf of another network function entity. Therefore, a network function entity can subscribe to tunnel information on behalf of the second endpoint of the tunnel. After the tunnel information is allocated at the first endpoint of the tunnel, the tunnel information is provided to the second endpoint of the tunnel through the Notify operation of Nupf_EventExposure.

[0214] Optionally, if the first endpoint of the tunnel is the newly inserted endpoint of the target tunnel, the method further includes:

[0215] The system receives relevant information sent by a network function entity, including tunnel information corresponding to one or more associated tunnel endpoints related to the target tunnel.

[0216] refer to Figure 7 , Figure 7 This is a schematic diagram of the GTP-U tunnel modification process based on user plane messages provided in this application embodiment. The target tunnel refers to the GTP-U tunnel that needs to be modified, such as... Figure 7 As shown, without UPF2, the GTP-U tunnel between UPF3 and UPF1 is the target tunnel; UPF2 is the newly inserted endpoint of the target tunnel, i.e., the first endpoint of the tunnel. The system receives tunnel information corresponding to UPF3 and UPF1 sent by the network function entity. For example, when the network function entity is an SMF, the system receives a session modification request message or session establishment request message sent by the SMF. This message includes tunnel information corresponding to the tunnel endpoints at both ends of the target tunnel. In this case, UPF2 needs to receive the tunnel information of its associated tunnel endpoints, i.e., the tunnel information of the endpoints corresponding to UPF1 and UPF3 and UPF2.

[0217] Optionally, when the tunnel information transmission method provided in this application embodiment is only applied to the N9 interface, the UPF2 can be inserted before UPF3, that is, the connection of multiple UPFs is in the following order: UPF2, UPF3, UPF1; in this case, UPF2 only needs to receive the tunnel information of its corresponding endpoint (UPF3).

[0218] Optionally, the data transmission links are sequentially: UPF1, UPF2, PSA. If UPF2 needs to be replaced with UPF3, the tunnel between UPF1 and UPF2 is used as the target tunnel, and UPF3 only needs to receive the tunnel information corresponding to the associated tunnel endpoint UPF1. Optionally, UPF3 can also receive the tunnel information corresponding to UPF2 and allocate a Tunnel Endpoint for UPF2 as a forwarding tunnel to buffer DL data from UPF2. It is understood that the same processing is applied to the tunnel information transmission between the tunnel endpoints at the other end, PSA; this will not be elaborated further here.

[0219] Optionally, in the embodiment of this application, the tunnel information transmission method is applied to the N3 interface, and the data transmission links are sequentially: RAN, PSA1, DN. If PSA1 needs to be replaced by PSA2, the target tunnel is the tunnel between RAN and PSA1. PSA2 only needs to receive the AN Tunnel Info corresponding to the associated tunnel endpoint RAN. Optionally, PSA2 can also receive the tunnel information corresponding to PSA1 and allocate a Tunnel Endpoint for PSA1 as a forwarding tunnel to buffer DL data from PSA1.

[0220] The above examples are all exemplary regarding the insertion position of UPF. Other insertion positions or methods known to those skilled in the art that can implement this solution can also be applied here, and there is no limitation on them.

[0221] The relevant information also includes the address and / or session identifier of the associated tunnel endpoint related to the target tunnel, wherein the session identifier is used to distinguish the session to which the tunnel information belongs;

[0222] The method further includes:

[0223] Based on the address corresponding to each associated tunnel endpoint, a user plane message is sent to each associated tunnel endpoint. The user plane message includes tunnel information corresponding to the first tunnel endpoint and a session identifier corresponding to the associated tunnel endpoint.

[0224] refer to Figure 7 The steps for modifying a GTP-U tunnel based on user plane messages provided in this application embodiment are as follows:

[0225] 1. SMF sends an N4 SessionEstablishment Request Message to the first endpoint of the inserted tunnel, UPF2. The request message contains structured control information such as PDR and FAR that define the required behavior of UPF2, an N4 Session ID used to identify the N4 session context, tunnel information of the tunnel peer, the address and session identifier of UPF1, and the address and session identifier of UPF3.

[0226] 2. After receiving the message, UPF2 stores the tunnel information of the other end of the tunnel and allocates uplink tunnel information (UL Tunnel Info) and downlink tunnel information (DL Tunnel Info) locally for this session.

[0227] 3. UPF2 sends the allocated uplink tunnel information to the tunnel peer UPF3 and the allocated downlink tunnel information to the tunnel peer UPF1 via user plane messages.

[0228] 4. The inserted UPF sends an N4 Session Establishment Response Message to the SMF.

[0229] Alternatively, the reliability of user plane messages can be guaranteed by setting a timer for timeout retransmission, and by using TCP / IP or other underlying protocols.

[0230] The user plane message used to exchange tunnel information can be a GTP-U signaling message, a UPF service based on a service-oriented interface, or a newly defined message for tunnel information exchange. For related information, please refer to the above description, which will not be repeated here.

[0231] Optionally, the tunnel information transmission method provided in this application embodiment can be applied to the N3 and / or N9 interfaces. For the application to the N9 interface, refer to... Figure 6 and Figure 7 The details described in [the document] will not be repeated here. For applications using the N3 interface, please refer to [the relevant documentation]. Figure 6 and Figure 7 Alternatively, the UPF connected to the N3 interface can be used as the first endpoint of the tunnel, and the RAN or AN as the second endpoint. After the UPF connected to the N3 interface allocates uplink tunnel information, the uplink tunnel information is sent to the RAN or AN at the other end of the tunnel via user plane messages. Or, the RAN or AN connected to the N3 interface can be used as the first endpoint of the tunnel, and the UPF connected to the N3 interface can be used as the second endpoint. After the RAN or AN allocates AN Tunnel Info, the AN Tunnel Info is sent to the UPF at the other end of the tunnel via user plane messages.

[0232] refer to Figure 8 , Figure 8 This is a second schematic flowchart of the tunnel information transmission method provided in this application embodiment. The method can be applied to network functional entities, and the method includes:

[0233] Step 810: Send the second session identifier and / or the address of the second endpoint of the tunnel to the first endpoint of the tunnel;

[0234] The address of the second endpoint of the tunnel is used by the first endpoint of the tunnel to send user plane messages to the second endpoint of the tunnel. The user plane messages include tunnel information corresponding to the first endpoint of the tunnel. The second session identifier is used to distinguish the session to which the tunnel information belongs and corresponds to the second endpoint of the tunnel.

[0235] Specifically, a Network Function Entity (NF) refers to a network function entity associated with a GTP-U tunnel, such as an SMF. The first endpoint of the tunnel refers to the receiving end of the GTP-U tunnel, and the second endpoint refers to the sending end. The second session identifier and the address of the second endpoint can be pre-stored by the network function entity or pre-obtained from other network function entities or nodes. For example, if the network function entity has sent a message to or received a message from the second endpoint before the tunnel was established, the network function entity stores the address of the second endpoint. For an explanation of the second session identifier and the address of the second endpoint, please refer to [link to relevant documentation]. Figure 5 The details described in the text will not be repeated here.

[0236] The tunnel information transmission method provided in this application sends the address of the second tunnel endpoint and / or the second session identifier to the first tunnel endpoint via a network function entity. This enables the first tunnel endpoint to send user plane messages carrying tunnel information to the second tunnel endpoint, and the second tunnel endpoint to distinguish the session to which the tunnel information belongs based on the second session identifier. This achieves the exchange of tunnel information between the two ends of a GTP-U tunnel via user plane messages, shortening the tunnel establishment or modification time. Furthermore, by reducing the number of session messages executed by the network function entity, the processing overhead of the control plane function is reduced, thereby improving the efficiency of tunnel message exchange.

[0237] Optionally, the method further includes any one or a combination of the following:

[0238] Receive the tunnel information sent by the first endpoint of the tunnel;

[0239] Send a first relevant information and a second relevant information to the newly inserted tunnel endpoint; the first relevant information includes tunnel information corresponding to the first tunnel endpoint, and the second relevant information includes tunnel information corresponding to the second tunnel endpoint.

[0240] refer to Figure 7 With UPF1 as the first endpoint of the tunnel and UPF3 as the second endpoint, after UPF1 allocates tunnel information for UPF3, it sends the tunnel information to the network function entity, which receives the tunnel information sent by UPF1. The network function entity stores the tunnel information corresponding to UPF1 and the tunnel information corresponding to UPF3. If a tunnel modification occurs in the GTP-U tunnel between UPF1 and UPF3, i.e., a new tunnel endpoint UPF2 is inserted between UPF1 and UPF3, a first related information and a second related information are sent to UPF2. The first related information includes the tunnel information corresponding to UPF1, and the second related information includes the tunnel information corresponding to UPF3. The first and second related information can be used after UPF2 allocates uplink and downlink tunnel information, allowing UPF2 to send downlink tunnel information to UPF1 via user plane messages and uplink tunnel information to UPF3.

[0241] Optionally, the first relevant information may further include an address and / or a first session identifier corresponding to the first endpoint of the tunnel, wherein the first session identifier is used to distinguish the session to which the tunnel information belongs and corresponds to the first endpoint of the tunnel;

[0242] The second relevant information also includes the address corresponding to the second endpoint of the tunnel and / or the second session identifier.

[0243] Optionally, the second session identifier includes:

[0244] Network Function Entity Identifier (NFI) and N4 Session Identifier (N4 Session ID), wherein the N4 Session ID corresponds to the second endpoint of the tunnel; or

[0245] Permanent Identity Item (SUPI) and Protocol Data Unit (PDU) Session ID;

[0246] The first session identifier includes:

[0247] Network Function Entity Identifier (NFI) and N4 Session Identifier (N4 Session ID), wherein the N4 Session ID corresponds to the first endpoint of the tunnel; or

[0248] Permanent Identity SUPI and Protocol Data Unit Session ID (PDU).

[0249] For information on Network Function Entity Identifiers (NFIs) and N4 Session IDs, as well as SUPI and PDU Session IDs, please refer to [link / reference]. Figure 5 The details described herein will not be repeated here. For example, refer to... Figure 7 A first N4 session is established between SMF and UPF1, with SMF assigning an N4 Session ID corresponding to UPF1 to the first N4 session. A second N4 session is established between SMF and UPF3, with SMF assigning an N4 Session ID corresponding to UPF3 to the second N4 session. The identifier for the first session can be the SMF ID and the N4 Session ID corresponding to UPF1, or it can be the SUPI and PDU Session ID, etc. The identifier for the second session can be the SMF ID and the N4 Session ID corresponding to UPF3, or it can be the SUPI and PDU Session ID, etc.

[0250] The tunnel information sending method provided in this application embodiment sends first and second related information to the newly inserted tunnel endpoint through a network function entity, enabling the newly inserted tunnel endpoint to send user plane messages carrying tunnel information to the tunnel peer endpoint. This realizes the exchange of tunnel information between the two ends of the GTP-U tunnel through user plane messages, shortens the tunnel establishment or modification time, and reduces the processing overhead of the control plane function by reducing the number of session messages executed by the network function entity, thereby improving the efficiency of tunnel message exchange.

[0251] refer to Figure 9 , Figure 9 This is the third schematic diagram of the tunnel information sending method provided in this application embodiment, which can be applied to the modification of the GTP-U tunnel in the PDU session establishment process. The tunnel information sending method provided in this application embodiment includes:

[0252] If the PDU session establishment request is an "initial request," the SMF sends an N4Session Establishment Request to each selected UPF; otherwise, it sends an N4 Session Modification Request. Before establishing an N4 session, the SMF first assigns an N4 Session ID to that session. The request includes structured control information such as PDR and FAR defining the required behavior of the UPF, an N4 Session ID to identify the N4 session context, and the IP address and session identifier of the other UPF. The session identifier can be the SMF ID and N4 Session ID, or it can be SUPI and PDU Session ID, etc.

[0253] Each UPF acts as the first endpoint of the tunnel, performing the necessary actions and allocating the required Tunnel Info. Then, the UPF constructs GTP-U signaling, with the message type being the newly defined "Tunnel Info Signal." The IE (Interface) consists of Tunnel EndpointIdentifier Data I, GTP-U Peer Address, and the newly defined GTP-U Peer Session Identifier, representing the allocated TEID, the allocated IP address, and the peer's session identifier (including the UL / DL flag), respectively. The destination IP address of the GTP-U signaling message is the IP address of the tunnel peer (i.e., the second endpoint of the tunnel), and the destination port number is the default port 2152.

[0254] The first endpoint UPF of the tunnel will send out the constructed GTP-U signaling message.

[0255] The first endpoint of the tunnel, UPF, sends an N4 session establishment or modification response message to SMF, which carries CNTunnel Info.

[0256] Optionally, the N3 interface can also exchange tunnel messages based on user plane messages. The UPF sends UL Tunnel Info to (R)AN via user plane messages, and the (R)AN sends AN Tunnel Info to the UPF via user plane messages, which can advance the ULlink data transmission time.

[0257] Optionally, the first endpoint of the tunnel, UPF, provides the Tunnel Info to the second endpoint of the tunnel at the other end of the tunnel through the Notify operation of Nupf_EventExposure.

[0258] refer to Figure 10 , Figure 10 This is the fourth schematic diagram of the tunnel information sending method provided in this application embodiment, which can be applied to the service request process. The tunnel information sending method provided in this application embodiment includes:

[0259] If the CN Tunnel Info of the UPF(PSA) changes, the SMF sends an N4 SessionModification Request message to the UPF(PSA). If the SMF removes the old I-UPF without replacing it with a new one, the request also carries the IP address and session identifier of the old UPF. The SMF requests the UPF(PSA) to allocate a second tunnel endpoint as a forwarding tunnel to buffer DL data from the old UPF.

[0260] After the PSA allocates and forwards the DL Tunnel Info, it constructs a GTP-U signaling message. The message type is the newly defined "Tunnel Info Signal," and the IE is Tunnel Endpoint Identifier Data I, GTP-U Peer Address, and the newly defined GTP-U Peer Session Identifier, representing the allocated TEID, the allocated IP address, and the peer's session identifier (DL flag), respectively. The destination IP address of the GTP-U signaling message is the old UPF IP address, and the destination port number is the default port 2152.

[0261] The UPF(PSA) responds by providing the new CN Tunnel Info to the SMF.

[0262] If the SMF chooses to insert a new UPF as the intermediate UPF (I-UPF) for the PDU session, it sends an N4 Session Establishment Request message to the new I-UPF, requesting the allocation of Tunnel Info, along with the PSA's CN Tunnel Info, and additionally carrying the PSA's address and session identification information. If the SMF selects a new UPF to replace the old I-UPF, the SMF may also request the new UPF to allocate a second tunnel endpoint as a forwarding tunnel for DL ​​data buffered from the old I-UPF. Therefore, the N4 Session Establishment Request also needs to carry the old I-UPF's address and session identification information.

[0263] The new I-UPF allocates Tunnel Info, constructs GTP-U signaling messages for both the PSA and the old I-UPF, and sends the constructed GTP-U signaling messages. The new I-UPF responds to the SMF by providing the Tunnel Info requested by the SMF.

[0264] Optionally, UPF provides Tunnel Info to the tunnel peer via the Notify operation of Nupf_EventExposure.

[0265] Optionally, if a GTP-U entity (UPF) becomes unavailable during GTP-U tunnel establishment, it will return a denial-of-service message to the SMF. The handling of this situation is similar to that for GTP-U tunnel modification.

[0266] When the SMF receives a denial-of-service message from a UPF, it selects a new UPF and sends an N4 SessionEstablishment Request message, which carries the address and session identifier of the relevant tunnel peer UPF.

[0267] Upon receiving the request, the new UPF allocates a local UL / DL Tunnel Info, constructs a user plane message, and sends the TunnelInfo to the other end of the tunnel.

[0268] The new UPF replies to the SMF with an N4 Session Establishment Response message.

[0269] The tunnel information sending method provided in this application shortens the time for tunnel establishment or modification, and reduces the processing overhead of control plane functions by exchanging tunnel information through user plane messages. Taking the Session Management Function (SMF) entity as an example, it reduces the number of N4 Session Modification Requests / Responses executed by the SMF, thereby improving the efficiency of tunnel message exchange.

[0270] refer to Figure 11 , Figure 11 This is a schematic diagram of the structure of a tunnel first end-point device provided in an embodiment of this application. The tunnel first end-point device includes a transceiver 1100, a processor 1110, and a memory 1120, wherein:

[0271] The memory 1120 is used to store computer programs; the transceiver 1100 is used to receive and send data under the control of the processor 1110.

[0272] Among them, Figure 11In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 1110) and memory (memory 1120). The bus architecture can also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 1100 can be multiple elements, including transmitters and receivers, providing units for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor 1110 is responsible for managing the bus architecture and general processing, and the memory 1120 can store data used by the processor 1110 during operation.

[0273] The processor 1110 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0274] The processor 1110 calls the computer program stored in the memory 1120 to execute any of the methods provided in the embodiments of this application according to the obtained executable instructions, for example: sending a first user plane message to the second endpoint of the tunnel based on the address of the second endpoint of the tunnel, wherein the first user plane message includes tunnel information corresponding to the first endpoint of the tunnel.

[0275] Optionally, the first user plane message includes any one or a combination of the following:

[0276] The first user plane message is a General Packet Radio Service User Plane Tunneling Protocol (GTP-U) signaling message;

[0277] The first user plane message is a user plane function UPF service based on a service-oriented interface;

[0278] The first user plane message is a first message used for tunnel information exchange.

[0279] Optionally, the GTP-U signaling message includes any of the following:

[0280] The GTP-U signaling message is a new type of signaling message;

[0281] The GTP-U signaling message is a signaling message with a flag bit added to the message type;

[0282] The GTP-U signaling message is a signaling message with a new GTP-U extended header.

[0283] Optionally, the UPF service based on the service-oriented interface includes:

[0284] After the first endpoint of the tunnel assigns the tunnel information, it notifies the second endpoint of the tunnel through a Notify operation.

[0285] Optionally, the notification of the second endpoint of the tunnel via the Notify operation includes:

[0286] When a network function entity subscribes to tunnel information via Subscribe, it notifies the second endpoint of the tunnel via a Notify operation.

[0287] Optionally, the first user plane message further includes a second session identifier, which is used to distinguish the session to which the tunnel information belongs and corresponds to the second endpoint of the tunnel.

[0288] Optionally, before sending the first user plane message to the second endpoint of the tunnel, the operation further includes:

[0289] Receive the address of the second endpoint of the tunnel and / or the second session identifier sent by the network function entity.

[0290] Optionally, the second session identifier includes:

[0291] Network Function Entity Identifier (NFI) and N4 Session Identifier (N4 Session ID), wherein the N4 Session ID corresponds to the second endpoint of the tunnel; or

[0292] Permanent Identity SUPI and Protocol Data Unit Session ID (PDU).

[0293] Optionally, the operation further includes any one or a combination of the following:

[0294] After allocating the tunnel information corresponding to the second session identifier, the tunnel information is sent to the network function entity;

[0295] The system receives a second user plane message sent by the second endpoint of the tunnel. The second user plane message includes a first session identifier and tunnel information corresponding to the second endpoint of the tunnel. The first session identifier is used to distinguish the session to which the tunnel information belongs and corresponds to the first endpoint of the tunnel.

[0296] Optionally, the first session identifier includes:

[0297] Network Function Entity Identifier (NFI) and N4 Session Identifier (N4 Session ID), wherein the N4 Session ID corresponds to the first endpoint of the tunnel; or

[0298] Permanent Identity SUPI and Protocol Data Unit Session ID (PDU).

[0299] Optionally, if the first endpoint of the tunnel is the newly inserted endpoint of the target tunnel, the operation further includes:

[0300] The system receives relevant information sent by a network function entity, including tunnel information corresponding to one or more associated tunnel endpoints related to the target tunnel.

[0301] Optionally, the relevant information also includes the address and / or session identifier corresponding to the associated tunnel endpoint related to the target tunnel, wherein the session identifier is used to distinguish the session to which the tunnel information belongs;

[0302] The method further includes:

[0303] Based on the address corresponding to each associated tunnel endpoint, a user plane message is sent to each associated tunnel endpoint. The user plane message includes tunnel information corresponding to the first tunnel endpoint and a session identifier corresponding to the associated tunnel endpoint. Optionally, this operation is applied to the N3 and / or N9 interfaces.

[0304] It should be noted that the apparatus provided in this application embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0305] refer to Figure 12 , Figure 12 This is a schematic diagram of the structure of a network function entity provided in an embodiment of this application. The network function entity includes a transceiver 1200, a processor 1210, and a memory 1220, wherein:

[0306] The memory 1220 is used to store computer programs; the transceiver 1200 is used to receive and send data under the control of the processor 1210.

[0307] Among them, Figure 12In this context, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 1210) and memory (memory 1220). The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 1200 may be multiple elements, including transmitters and receivers, providing units for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor 1210 is responsible for managing the bus architecture and general processing, and the memory 1220 may store data used by the processor 1210 during operation.

[0308] The processor 1210 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0309] The processor 1210 calls the computer program stored in the memory 1220 to execute any of the methods provided in the embodiments of this application according to the obtained executable instructions, such as sending a second session identifier and / or the address of the second endpoint of the tunnel to the first endpoint of the tunnel;

[0310] The address of the second endpoint of the tunnel is used by the first endpoint of the tunnel to send user plane messages to the second endpoint of the tunnel. The user plane messages include tunnel information corresponding to the first endpoint of the tunnel. The second session identifier is used to distinguish the session to which the tunnel information belongs and corresponds to the second endpoint of the tunnel.

[0311] Optionally, the operation further includes any one or a combination of the following:

[0312] Receive the tunnel information sent by the first endpoint of the tunnel;

[0313] Send a first relevant information and a second relevant information to the newly inserted tunnel endpoint; the first relevant information includes tunnel information corresponding to the first tunnel endpoint, and the second relevant information includes tunnel information corresponding to the second tunnel endpoint.

[0314] Optionally, the first relevant information may further include an address and / or a first session identifier corresponding to the first endpoint of the tunnel, wherein the first session identifier is used to distinguish the session to which the tunnel information belongs and corresponds to the first endpoint of the tunnel;

[0315] The second relevant information also includes the address corresponding to the second endpoint of the tunnel and / or the second session identifier.

[0316] Optionally, the second session identifier includes:

[0317] Network Function Entity Identifier (NFI) and N4 Session Identifier (N4 Session ID), wherein the N4 Session ID corresponds to the second endpoint of the tunnel; or

[0318] Permanent Identity Item (SUPI) and Protocol Data Unit (PDU) Session ID;

[0319] The first session identifier includes:

[0320] Network Function Entity Identifier (NFI) and N4 Session Identifier (N4 Session ID), wherein the N4 Session ID corresponds to the first endpoint of the tunnel; or

[0321] Permanent Identity SUPI and Protocol Data Unit Session ID (PDU).

[0322] It should be noted that the apparatus provided in this application embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0323] refer to Figure 13 , Figure 13 This is one of the schematic diagrams of a tunnel information transmission device provided in the embodiments of this application. The device can be applied to the first end point of a tunnel, and the device includes:

[0324] The first sending unit 1310 is used to send a first user plane message to the second endpoint of the tunnel based on the address of the second endpoint of the tunnel. The first user plane message includes tunnel information corresponding to the first endpoint of the tunnel.

[0325] It should be noted that the apparatus provided in this application embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0326] refer to Figure 14 , Figure 14This is a second schematic diagram of the tunnel information transmission device provided in the embodiments of this application. The device can be applied to network functional entities, and includes:

[0327] The second sending unit 1410 is used to send a second session identifier and / or the address of the second endpoint of the tunnel to the first endpoint of the tunnel;

[0328] The address of the second endpoint of the tunnel is used by the first endpoint of the tunnel to send user plane messages to the second endpoint of the tunnel. The user plane messages include tunnel information corresponding to the first endpoint of the tunnel. The second session identifier is used to distinguish the session to which the tunnel information belongs and corresponds to the second endpoint of the tunnel.

[0329] It should be noted that the apparatus provided in this application embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0330] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0331] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0332] It should be noted that the apparatus provided in this application embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0333] On the other hand, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing the processor to execute the methods provided in the above embodiments, including:

[0334] Based on the address of the second endpoint of the tunnel, a first user plane message is sent to the second endpoint of the tunnel. The first user plane message includes tunnel information corresponding to the first endpoint of the tunnel.

[0335] On the other hand, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing the processor to execute the methods provided in the above embodiments, including:

[0336] Send the second session identifier and / or the address of the second endpoint of the tunnel to the first endpoint of the tunnel;

[0337] The address of the second endpoint of the tunnel is used by the first endpoint of the tunnel to send user plane messages to the second endpoint of the tunnel. The user plane messages include tunnel information corresponding to the first endpoint of the tunnel. The second session identifier is used to distinguish the session to which the tunnel information belongs and corresponds to the second endpoint of the tunnel.

[0338] The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0339] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0340] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0341] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0342] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0343] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for transmitting tunnel information, characterized in that, Applied to the first end of a tunnel, the method includes: Based on the address of the second endpoint of the tunnel, a first user plane message is sent to the second endpoint of the tunnel. The first user plane message includes tunnel information corresponding to the first endpoint of the tunnel. The first user plane message also includes a second session identifier, which is used to distinguish the session to which the tunnel information belongs and corresponds to the second endpoint of the tunnel.

2. The tunnel information transmission method according to claim 1, characterized in that, The first user plane message includes any one or a combination of the following: The first user plane message is a General Packet Radio Service User Plane Tunneling Protocol (GTP-U) signaling message; The first user plane message is a user plane function UPF service based on a service-oriented interface; The first user plane message is a first message used for tunnel information exchange.

3. The tunnel information transmission method according to claim 2, characterized in that, The GTP-U signaling message includes any of the following: The GTP-U signaling message is a new type of signaling message; The GTP-U signaling message is a signaling message with a flag bit added to the message type; The GTP-U signaling message is a signaling message with a new GTP-U extended header.

4. The tunnel information transmission method according to claim 2, characterized in that, The UPF service based on the service-oriented interface includes: After the first endpoint of the tunnel assigns the tunnel information, it notifies the second endpoint of the tunnel through a Notify operation.

5. The tunnel information transmission method according to claim 4, characterized in that, The notification of the second endpoint of the tunnel via the Notify operation includes: When a network function entity subscribes to tunnel information via Subscribe, it notifies the second endpoint of the tunnel via a Notify operation.

6. The tunnel information transmission method according to claim 1, characterized in that, Before sending the first user plane message to the second endpoint of the tunnel, the method further includes: Receive the address of the second endpoint of the tunnel and / or the second session identifier sent by the network function entity.

7. The tunnel information transmission method according to claim 1, characterized in that, The second session identifier includes: Network Function Entity Identifier (NFI) and N4 Session Identifier (N4 Session ID), wherein the N4 Session ID corresponds to the second endpoint of the tunnel; or Permanent Identity SUPI and Protocol Data Unit Session ID (PDU).

8. The tunnel information transmission method according to claim 1, characterized in that, When the first endpoint of the tunnel is the newly inserted endpoint of the target tunnel, the method further includes: The system receives relevant information sent by a network function entity, including tunnel information corresponding to one or more associated tunnel endpoints related to the target tunnel.

9. The tunnel information transmission method according to claim 8, characterized in that, The relevant information also includes the address and / or session identifier of the associated tunnel endpoint related to the target tunnel, wherein the session identifier is used to distinguish the session to which the tunnel information belongs; The method further includes: Based on the address corresponding to each associated tunnel endpoint, a user plane message is sent to each associated tunnel endpoint. The user plane message includes tunnel information corresponding to the first tunnel endpoint and a session identifier corresponding to the associated tunnel endpoint.

10. The tunnel information transmission method according to any one of claims 1 to 5, characterized in that, The method is applied to the N3 and / or N9 interfaces.

11. A method for transmitting tunnel information, characterized in that, Applied to network functional entities, the method includes: Send the second session identifier and / or the address of the second endpoint of the tunnel to the first endpoint of the tunnel; The address of the second endpoint of the tunnel is used by the first endpoint of the tunnel to send user plane messages to the second endpoint of the tunnel. The user plane messages include tunnel information corresponding to the first endpoint of the tunnel. The second session identifier is used to distinguish the session to which the tunnel information belongs and corresponds to the second endpoint of the tunnel.

12. The tunnel information transmission method according to claim 11, characterized in that, The method further includes any one or a combination of the following: Receive the tunnel information sent by the first endpoint of the tunnel; Send a first relevant information and a second relevant information to the newly inserted tunnel endpoint; the first relevant information includes tunnel information corresponding to the first tunnel endpoint, and the second relevant information includes tunnel information corresponding to the second tunnel endpoint.

13. The tunnel information transmission method according to claim 12, characterized in that, The first related information also includes an address and / or a first session identifier corresponding to the first endpoint of the tunnel, wherein the first session identifier is used to distinguish the session to which the tunnel information belongs and corresponds to the first endpoint of the tunnel; The second relevant information also includes the address corresponding to the second endpoint of the tunnel and / or the second session identifier.

14. The tunnel information transmission method according to claim 13, characterized in that, The second session identifier includes: Network Function Entity Identifier (NFI) and N4 Session Identifier (N4 Session ID), wherein the N4 Session ID corresponds to the second endpoint of the tunnel; or Permanent Identity Item (SUPI) and Protocol Data Unit (PDU) Session ID; The first session identifier includes: Network Function Entity Identifier (NFI) and N4 Session Identifier (N4 Session ID), wherein the N4 Session ID corresponds to the first endpoint of the tunnel; or Permanent Identity SUPI and Protocol Data Unit Session ID (PDU).

15. A tunnel first-endpoint device, comprising a memory, a transceiver, and a processor; characterized in that: Memory, used to store computer programs; The transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: Based on the address of the second endpoint of the tunnel, a first user plane message is sent to the second endpoint of the tunnel. The first user plane message includes tunnel information corresponding to the first endpoint of the tunnel. The first user plane message also includes a second session identifier, which is used to distinguish the session to which the tunnel information belongs and corresponds to the second endpoint of the tunnel.

16. The tunnel first end device according to claim 15, characterized in that, The first user plane message includes any one or a combination of the following: The first user plane message is a General Packet Radio Service User Plane Tunneling Protocol (GTP-U) signaling message; The first user plane message is a user plane function UPF service based on a service-oriented interface; The first user plane message is a first message used for tunnel information exchange.

17. The tunnel first end device according to claim 16, characterized in that, The GTP-U signaling message includes any of the following: The GTP-U signaling message is a new type of signaling message; The GTP-U signaling message is a signaling message with a flag bit added to the message type; The GTP-U signaling message is a signaling message with a new GTP-U extended header.

18. The tunnel first end-point device according to claim 16, characterized in that, The UPF service based on the service-oriented interface includes: After the first endpoint of the tunnel assigns the tunnel information, it notifies the second endpoint of the tunnel through a Notify operation.

19. The tunnel first end device according to claim 18, characterized in that, The notification of the second endpoint of the tunnel via the Notify operation includes: When a network function entity subscribes to tunnel information via Subscribe, it notifies the second endpoint of the tunnel via a Notify operation.

20. The tunnel first end device according to claim 15, characterized in that, Before sending the first user plane message to the second endpoint of the tunnel, the operation further includes: Receive the address of the second endpoint of the tunnel and / or the second session identifier sent by the network function entity.

21. The tunnel first end device according to claim 15, characterized in that, The second session identifier includes: Network Function Entity Identifier (NFI) and N4 Session Identifier (N4 Session ID), wherein the N4 Session ID corresponds to the second endpoint of the tunnel; or Permanent Identity SUPI and Protocol Data Unit Session ID (PDU).

22. The tunnel first end device according to claim 15, characterized in that, When the first endpoint of the tunnel is the newly inserted endpoint of the target tunnel, the operation further includes: The system receives relevant information sent by a network function entity, including tunnel information corresponding to one or more associated tunnel endpoints related to the target tunnel.

23. The tunnel first end device according to claim 22, characterized in that, The relevant information also includes the address and / or session identifier of the associated tunnel endpoint related to the target tunnel, wherein the session identifier is used to distinguish the session to which the tunnel information belongs; The operation also includes: Based on the address corresponding to each associated tunnel endpoint, a user plane message is sent to each associated tunnel endpoint. The user plane message includes tunnel information corresponding to the first tunnel endpoint and a session identifier corresponding to the associated tunnel endpoint.

24. The tunnel first end device according to any one of claims 15 to 19, characterized in that, The operation is applied to the N3 and / or N9 interfaces.

25. A network functional entity, comprising a memory, a transceiver, and a processor; characterized in that: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: Send the second session identifier and / or the address of the second endpoint of the tunnel to the first endpoint of the tunnel; The address of the second endpoint of the tunnel is used by the first endpoint of the tunnel to send user plane messages to the second endpoint of the tunnel, and the user plane messages include tunnel information corresponding to the first endpoint of the tunnel; The second session identifier is used to distinguish the session to which the tunnel information belongs, and corresponds to the second endpoint of the tunnel.

26. The network functional entity according to claim 25, characterized in that, The operation also includes any one or a combination of the following: Receive the tunnel information sent by the first endpoint of the tunnel; Send a first relevant information and a second relevant information to the newly inserted tunnel endpoint; the first relevant information includes tunnel information corresponding to the first tunnel endpoint, and the second relevant information includes tunnel information corresponding to the second tunnel endpoint.

27. The network functional entity according to claim 26, characterized in that, The first related information also includes an address and / or a first session identifier corresponding to the first endpoint of the tunnel, wherein the first session identifier is used to distinguish the session to which the tunnel information belongs and corresponds to the first endpoint of the tunnel; The second relevant information also includes the address corresponding to the second endpoint of the tunnel and / or the second session identifier.

28. The network functional entity according to claim 27, characterized in that, The second session identifier includes: Network Function Entity Identifier (NFI) and N4 Session Identifier (N4 Session ID), wherein the N4 Session ID corresponds to the second endpoint of the tunnel; or Permanent Identity Item (SUPI) and Protocol Data Unit (PDU) Session ID; The first session identifier includes: Network Function Entity Identifier (NFI) and N4 Session Identifier (N4 Session ID), wherein the N4 Session ID corresponds to the first endpoint of the tunnel; or Permanent Identity SUPI and Protocol Data Unit Session ID (PDU).

29. A tunnel information transmission device, characterized in that, The device, applied to the first end of a tunnel, includes: The first sending unit is configured to send a first user plane message to the second endpoint of the tunnel based on the address of the second endpoint of the tunnel. The first user plane message includes tunnel information corresponding to the first endpoint of the tunnel. The first user plane message also includes a second session identifier, which is used to distinguish the session to which the tunnel information belongs and corresponds to the second endpoint of the tunnel.

30. A tunnel information transmission device, characterized in that, Applied to network functional entities, the device includes: The second sending unit is used to send the second session identifier and / or the address of the second endpoint of the tunnel to the first endpoint of the tunnel; The address of the second endpoint of the tunnel is used by the first endpoint of the tunnel to send user plane messages to the second endpoint of the tunnel. The user plane messages include tunnel information corresponding to the first endpoint of the tunnel. The second session identifier is used to distinguish the session to which the tunnel information belongs and corresponds to the second endpoint of the tunnel.

31. A processor-readable storage medium, characterized in that, The processor-readable storage medium stores a computer program that causes the processor to execute the tunnel information transmission method according to any one of claims 1 to 10, or the tunnel information transmission method according to any one of claims 11 to 14.

Images