Data plane establishment methods and network side device

Abstract

Data plane establishment methods and a network side device, relating to the technical field of communications. A data plane establishment method comprises: a first network element sending a first resource allocation request message to a second network element, the first resource allocation request message being used for requesting to establish a tunnel, and the tunnel being used for transmitting service data; and the first network element receiving a first resource allocation response message sent by the second network element, the first resource allocation response message being used for indicating a resource allocation result.

Description

Data plane establishment method and network side equipment

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202510124632.7, filed on January 26, 2025, entitled “Data Plane Establishment Method and Network Side Device”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, specifically relating to a data plane establishment method and network-side equipment. Background Technology

[0004] In related technologies, terminals and network functions (NFs) can communicate via non-access stratum (NAS). However, when a terminal communicates with other NFs besides the Access and Mobility Management Function (AMF) via NAS, it needs to be forwarded through the AMF.

[0005] Due to network deployment issues, AMF forwarding of NAS may result in path detours. Therefore, related technologies have introduced a distributed NAS network architecture, which allows terminals to communicate with any NF without going through AMF forwarding, thus solving the NAS path detour problem caused by AMF forwarding of NAS.

[0006] In a distributed NAS network architecture, how to achieve the transmission of business data is a technical problem that urgently needs to be solved. Summary of the Invention

[0007] This application provides a data plane establishment method and a network-side device, which can solve the problem of how to transmit business data in a distributed NAS network architecture.

[0008] In a first aspect, a data plane establishment method is provided, comprising: a first network element sending a first resource allocation request message to a second network element, the first resource allocation request message being used to request the establishment of a tunnel, the tunnel being used to transmit service data; the first network element receiving a first resource allocation response message sent by the second network element, the first resource allocation response message being used to indicate the resource allocation result.

[0009] Secondly, a data plane establishment method is provided, comprising: a second network element receiving a first resource allocation request message sent by a first network element, the first resource allocation request message being used to request the establishment of a tunnel, the tunnel being used to transmit service data; the second network element sending a first resource allocation response message to the first network element, the first resource allocation response message being used to indicate the resource allocation result.

[0010] Thirdly, a data plane establishment method is provided, comprising: a third network element receiving a second resource allocation request message sent by a second network element, the second resource allocation request message being used to request the establishment of a tunnel, the tunnel being used to transmit service data; the third network element sending a second resource allocation response message to the second network element, the second resource allocation response message being used to indicate the resource allocation result.

[0011] Fourthly, a data plane establishment method is provided, comprising: a terminal sending a service request message to a first network element, the service request message being used to request the establishment of a tunnel, the tunnel being used to transmit service data.

[0012] Fifthly, a data plane establishment method is provided, comprising: an access network device receiving a first message sent by a first network element; the access network device establishing a bearer based on the first message, the bearer being used to transmit service data. Sixthly, a data plane establishment apparatus is provided, comprising: a sending module, configured to send a first resource allocation request message to a second network element, the first resource allocation request message being used to request the establishment of a tunnel, the tunnel being used to transmit service data; and a receiving module, configured to receive a first resource allocation response message sent by the second network element, the first resource allocation response message being used to indicate a resource allocation result.

[0013] In a seventh aspect, a data plane establishment apparatus is provided, comprising: a receiving module, configured to receive a first resource allocation request message sent by a first network element, the first resource allocation request message being used to request the establishment of a tunnel, the tunnel being used to transmit service data; and a sending module, configured to send a first resource allocation response message to the first network element, the first resource allocation response message being used to indicate a resource allocation result.

[0014] Eighthly, a data plane establishment apparatus is provided, comprising: a receiving module for receiving a second resource allocation request message sent by a second network element, the second resource allocation request message being used to request the establishment of a tunnel for transmitting service data; and a sending module for sending a second resource allocation response message to the second network element, the second resource allocation response message being used to indicate a resource allocation result.

[0015] In a ninth aspect, a data plane establishment apparatus is provided, comprising: a sending module, configured to send a service request message to a first network element, the service request message being used to request the establishment of a tunnel, the tunnel being used to transmit service data.

[0016] In a tenth aspect, a data plane establishment apparatus is provided, comprising: a receiving module for receiving a first message sent by a first network element; and a processing module for establishing a bearer based on the first message, wherein the bearer is used to transmit service data.

[0017] Eleventhly, an apparatus for establishing a data plane is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect, or implement the steps of the method described in the third aspect, or implement the steps of the method described in the fourth aspect, or implement the steps of the method described in the fifth aspect.

[0018] In a twelfth aspect, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the fourth aspect.

[0019] In a thirteenth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to send a service request message to a first network element, the service request message is used to request the establishment of a tunnel, and the tunnel is used to transmit service data.

[0020] In a fourteenth aspect, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect, or the steps of the method as described in the second aspect, or the steps of the method as described in the third aspect, or the steps of the method as described in the fifth aspect.

[0021] In a fifteenth aspect, a network-side device is provided, including a processor and a communication interface. The communication interface is configured to send a first resource allocation request message to a second network element, the first resource allocation request message requesting the establishment of a tunnel for transmitting service data; and to receive a first resource allocation response message sent by the second network element, the first resource allocation response message indicating a resource allocation result. Alternatively, the communication interface is configured to receive a first resource allocation request message sent by a first network element, the first resource allocation request message requesting the establishment of a tunnel for transmitting service data; and to send a first resource allocation response message to the first network element, the first resource allocation response message indicating a resource allocation result. Alternatively, the communication interface is configured to receive a second resource allocation request message sent by a second network element, the second resource allocation request message requesting the establishment of a tunnel for transmitting service data; and to send a second resource allocation response message to the second network element, the second resource allocation response message indicating a resource allocation result. Alternatively, the communication interface is configured to receive a first message sent by a first network element; the access network device establishes a bearer based on the first message, the bearer being used to transmit service data.

[0022] In a sixteenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect, or the steps of the method described in the third aspect, or the steps of the method described in the fourth aspect, or the steps of the method described in the fifth aspect.

[0023] In a seventeenth aspect, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the network-side device is configured to perform the steps of the method described in the first aspect, or the steps of the method described in the second aspect, or the steps of the method described in the third aspect, or implement the steps of the method described in the fourth aspect, or implement the steps of the method described in the fifth aspect.

[0024] In an eighteenth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect, or the steps of the method described in the third aspect.

[0025] In a nineteenth aspect, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the steps of the method as described in the first aspect, or the steps of the method as described in the second aspect, or the steps of the method as described in the third aspect, or the steps of the method as described in the fourth aspect, or the steps of the method as described in the fifth aspect.

[0026] In this embodiment of the application, the message interaction between the first network element and the second network element facilitates the establishment of a tunnel for transmitting service data, thereby enabling the transmission of service data. Attached Figure Description

[0027] Figure 1 is a schematic diagram of a wireless communication system according to an embodiment of this application;

[0028] Figure 2 is a schematic flowchart of a data plane establishment method according to an embodiment of this application;

[0029] Figure 3 is a schematic diagram of a tunnel in a data plane establishment method according to an embodiment of this application;

[0030] Figure 4 is a schematic flowchart of a data plane establishment method according to an embodiment of this application;

[0031] Figure 5 is a schematic flowchart of a data plane establishment method according to an embodiment of this application;

[0032] Figure 6 is a schematic flowchart of a data plane establishment method according to an embodiment of this application;

[0033] Figure 7 is a schematic flowchart of a data plane establishment method according to an embodiment of this application;

[0034] Figure 8 is a schematic flowchart of a data plane establishment method according to an embodiment of this application;

[0035] Figure 9 is a schematic flowchart of a data plane establishment method according to an embodiment of this application;

[0036] Figure 10 is a schematic flowchart of a data plane establishment method according to an embodiment of this application;

[0037] Figure 11 is a schematic flowchart of a data plane establishment method according to an embodiment of this application;

[0038] Figure 12 is a schematic diagram of the data plane establishment device according to an embodiment of this application;

[0039] Figure 13 is a schematic diagram of the data plane establishment device according to an embodiment of this application;

[0040] Figure 14 is a schematic diagram of the data plane establishment device according to an embodiment of this application;

[0041] Figure 15 is a schematic diagram of the data plane establishment device according to an embodiment of this application;

[0042] Figure 16 is a schematic diagram of the data plane establishment device according to an embodiment of this application;

[0043] Figure 17 is a schematic diagram of the structure of a communication device according to an embodiment of this application;

[0044] Figure 18 is a schematic diagram of the structure of a terminal according to an embodiment of this application;

[0045] Figure 19 is a schematic diagram of the structure of a network-side device according to an embodiment of this application;

[0046] Figure 20 is a schematic diagram of the structure of a network-side device according to an embodiment of this application. Detailed Implementation

[0047] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0048] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0049] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as the sender explicitly informing the receiver of specific information, the required operation, or the requested result in the instruction sent. An indirect instruction can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the required operation or requested result based on the judgment result.

[0050] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used in the systems and radio technologies mentioned above, as well as in other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.

[0051] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as User Equipment (UE), and can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.Among them, base stations can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform stations). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to specific technical terms. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0052] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.

[0053] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0054] The data plane establishment method provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0055] As shown in Figure 2, this application embodiment provides a data plane establishment method 200, which can be executed by a first network element. In other words, the method can be executed by software or hardware installed on the first network element. The method includes the following steps.

[0056] S202: The first network element sends a first resource allocation request message to the second network element. The first resource allocation request message is used to request the establishment of a tunnel, and the tunnel is used to transmit service data.

[0057] The various embodiments of this application can be applied to network architectures such as distributed NAS.

[0058] In this embodiment, the first network element may send a first resource allocation request message to the second network element upon receiving a service establishment request from the terminal. In this embodiment, when the terminal decides to initiate a specific service interaction with the first network element, the terminal may send a service establishment request to the first network element through access network equipment and / or devices such as the AMF.

[0059] The first network element can be a core network element used to request and obtain service data. For example, the first network element can be a Session Management Function (SMF), a Policy Control Function (PCF), etc., or it can be other service-related network elements / devices, such as a Sensing Function (SF), etc.

[0060] The first network element can be used to process services. It should be noted that, in this article, "services" can refer to conversation-related services, as well as sensing services, AI services, etc., without specific limitations.

[0061] The second network element and the third network element mentioned later can be data plane related network elements. In some examples, data plane functions can be divided into a second network element and a third network element. The second network element can be a data plane management function or control function (DPF-C), and the third network element can be a data plane data function (DPF-U or DPF-D). The data plane management function (DPF-C) can also be called data plane function-control plane (DPF-CP), which can interact with other network-side devices for control signaling and is responsible for data control, etc. The data plane data function (DPF-U) can also be called data plane function-user plane (DPF-UP) or data plane function-data plane (DPF-DP), etc., which can interact with other network-side devices for data-related interactions and is responsible for data transmission, etc. In other embodiments, the data plane functions may not be separate, that is, the second network element and the third network element can be the same network element.

[0062] In some embodiments, the first resource allocation request message includes at least one of the following:

[0063] 1) First information, used to indicate the type of data production node.

[0064] The data production node in each embodiment of this application can be a service data production node, that is, the data production node can generate service data. The type of the data production node can be UE, RAN, etc. The data production node can also be a node that initiates a service request. It should be noted that the terms "node" and "device" have similar meanings and can be used interchangeably. It can be understood that the first information is used to indicate the device type of the device corresponding to the collected data, such as UE, RAN, etc.

[0065] 2) The second piece of information is the identification information used to indicate the data production node.

[0066] This information is used to indicate the node identification information corresponding to the data production node. For example, when the data production node is a terminal, this identification information can be the International Mobile Subscriber Identification Number (IMSI) or the Subscription Permanent Identifier (SUPI), etc. It can be understood that the second information is used to indicate the identification information of the device corresponding to the collected data; for example, when the target device is a UE, it can be IMSI, SUPI, etc.

[0067] 3) The third type of information is used to indicate the address information of the data production node, such as the IP address or port number of the data production node.

[0068] 4) The fourth piece of information is used to indicate the type or granularity of the tunnel to be established.

[0069] The tunnel type information may include shared tunnels or dedicated tunnels, etc.; the tunnel granularity information may include terminal granularity or RAN granularity, etc. It should be noted that tunnel type information and granularity information can implicitly indicate each other. For example, when the tunnel type is a shared tunnel, the tunnel granularity is RAN granularity, and when the tunnel type is a dedicated tunnel, the tunnel granularity is UE granularity.

[0070] It is understandable that the type of data production node can also indicate the type or granularity of the tunnel to some extent. For example, when the type of data production node is RAN, the type of the tunnel can be a shared tunnel; when the type of data production node is UE, the tunnel type can also be a UE-level tunnel.

[0071] It should be noted that a tunnel can also refer to data flow, business flow, or carrier, etc.

[0072] 5) The fifth piece of information is used to indicate a request for the allocation of transmission or storage resources.

[0073] Requesting the allocation of transmission resources can be understood as reserving or allocating resources (or allocating identifiers, etc.) for subsequent tunnel or bearer establishment, or requesting the establishment of a tunnel, etc.; requesting the allocation of storage resources can be understood as allocating resources for subsequent business data storage, such as storage space, allocating storage addresses, allocating storage identifiers, etc.

[0074] 6) The sixth piece of information is used to indicate a request to obtain the business data.

[0075] This business data could be related data from data production nodes, etc. It can be understood that the sixth piece of information can be used to indicate a request to obtain relevant data from data production nodes. The second network element can use the sixth piece of information to determine whether to establish a connection with the data production node, such as establishing a tunnel or bearer. This sixth piece of information can also be referred to as an indication to request the establishment of a connection.

[0076] 7) The seventh piece of information is used to indicate the request for information about the data collection node.

[0077] For example, a request can be made to obtain the identification information, IP address information, port number information, etc. of a data collection node in order to request the data collection node to help collect business data. The data collection node can be a third network element, such as DPF-U.

[0078] 8) The eighth piece of information is used to indicate the carrier identifier.

[0079] The bearer corresponding to this bearer identifier is used to transmit service data, for example, to realize the transmission of service data from the terminal to the access network equipment. The bearer is a logical service perspective, relying on the tunnel to actually transmit the data stream. Therefore, there is a certain correlation and overlap between the bearer, the tunnel, and the data stream. In a certain scenario, the bearer can refer to a tunnel segment or a data stream, etc.

[0080] When the bearer identifier is assigned by the first network element, in order to ensure the uniqueness of the bearer identifier, the eighth information can also indicate the identifier information of the NF (such as the first network element) itself, and then determine the uniqueness of the bearer through the bearer identifier and the identifier information of the NF.

[0081] The bearer identifier can be assigned by the first network element, the second network element, or the AMF.

[0082] For example, after receiving a service establishment request from a terminal, the first network element can determine that the terminal's service requires the establishment of a tunnel, and then the first network element can allocate a bearer identifier.

[0083] For example, if the second network element can obtain the terminal's subscription information and QoS information, then the second network element can allocate bearer identifiers.

[0084] 9) The ninth piece of information is used to indicate Quality of Service (QoS) information.

[0085] Typically, QoS information needs to be considered when establishing a tunnel or related operations in order to establish a tunnel or bearer that meets the requirements.

[0086] QoS information refers to the set of parameters and related mechanisms that ensure the quality of service for different types of services in network transmission. It is set to meet the performance requirements of different applications on the network and may include bandwidth, latency, jitter, reliability, QoS identifiers (5QI identifiers), etc.

[0087] 10) The tenth piece of information is used to indicate the reporting conditions of the business data.

[0088] The reporting conditions include, for example, real-time reporting, reporting upon receiving business data, scheduled reporting, and periodic reporting.

[0089] 11) Eleventh information, used to indicate the notification address of the business data.

[0090] The reporting address can be an IP address, or it can be the identification information or address information of the NF (such as the first network element).

[0091] The information carried in the first resource allocation request message in this embodiment of the application is beneficial to successfully establishing a tunnel or bearer, so as to achieve effective transmission of business data.

[0092] S204: The first network element receives a first resource allocation response message sent by the second network element, the first resource allocation response message being used to indicate the resource allocation result.

[0093] In some embodiments, the first resource allocation response message includes uplink tunnel information of the tunnel, the uplink tunnel information including at least one of the following:

[0094] 1) Address information of the third network element, such as the address information of DPF-U. This address information includes, for example, IP address and MAC address. The third network element can be a data collection node.

[0095] 2) Port information of the third network element, such as the port information of DPF-U. This port information includes, for example, the Transmission Control Protocol (TCP) port number, the User Datagram Protocol (UDP) port number, and the Quick UDP Internet Connections (QUIC) port number.

[0096] 3) The core network side endpoint identification information of the tunnel, for example, the identification information can be the Tunnel Endpoint Identifier (TEID), which can be assigned by the second network element or by the third network element.

[0097] In this embodiment, after obtaining the uplink tunnel information of the tunnel, the first network element can also send the uplink tunnel information to the access network device to establish a terminal context, which is beneficial to the effective transmission of service data in the future.

[0098] In some embodiments, the tunnel requested to be established in this embodiment is as shown in FIG3, and may include a UE-granular NsDP tunnel between the RAN and a third network element.

[0099] The data plane establishment method provided in this application embodiment involves a first network element sending a first resource allocation request message to a second network element to request the establishment of a tunnel for transmitting service data; the first network element receiving a first resource allocation response message sent by the second network element, the first resource allocation response message indicating the resource allocation result. This application embodiment, through message interaction between the first and second network elements, facilitates the establishment of a tunnel for transmitting service data, thereby enabling the transmission of service data.

[0100] The data plane establishment method provided in this application embodiment allows the access network device to establish a bearer based on a bearer identifier, etc., which is used to transmit service data, for example, to realize the transmission of service data from the terminal to the access network device.

[0101] The bearer identifier can be assigned by either the first network element or the second network element. For example, after receiving a service establishment request from the terminal, the first network element can determine that the terminal's service requires a tunnel, and thus assign the bearer identifier. Alternatively, the second network element can obtain the terminal's subscription information and QoS information, and thus assign the bearer identifier.

[0102] When the bearer identifier is assigned by the first network element, in order to ensure the uniqueness of the bearer identifier, the uniqueness of the bearer can also be determined by the combination of the bearer identifier and the identifier information of the first network element.

[0103] The data plane establishment method provided in this application embodiment enables a terminal to directly send a service establishment request to a first network element in a distributed NAS network architecture such as 6G network. In this way, through the interaction between the first network element and the second network element, the establishment of a tunnel and the bearer identifier can be determined. The first network element can also send the bearer identifier and tunnel information to the terminal / access network device to establish a service connection so as to complete the subsequent service interaction.

[0104] In a distributed NAS network architecture, when a UE establishes a service connection with the first network element, it can be directly forwarded by the RAN without going through the AMF (distributed NAS, avoiding AMF overload and path detours). The data plane establishment method provided in this application embodiment allocates bearer identifiers and establishes tunnel connections by the first network element or data plane equipment, thereby realizing service connections and establishing data / service flows to achieve interconnection and interaction between the UE / RAN and the core network.

[0105] The aforementioned bearer identifier can be assigned by the first network element, the second network element, or the AMF. It should be noted that bearers are unique. Even if the bearer identifier is assigned by the first network element, the uniqueness of the bearer can still be determined by the bearer identifier and the identifier information of the NF (such as the first network element).

[0106] In some embodiments, after S204, the method further includes: the first network element sending a first message to the access network device, the first message including at least one of the following: a context establishment request message and a context modification request message, the first message being used to establish or modify a terminal context. The terminal context may be a terminal context on the interface (such as a RAN-NF interface) from the access network device to the first network element.

[0107] This embodiment facilitates the transmission of terminal-related business data by establishing or modifying the terminal context.

[0108] In some embodiments, the first message includes at least one of the following:

[0109] 1) The terminal’s first identification information includes at least one of the following: a temporary identifier assigned to the UE by the NF (such as the first network element), such as NF ID and NF UE ID, or NF UE NxAP ID; a temporary UE identifier on the AMF-RAN interface, such as RAN UE NgAP ID, or RAN UE NgAP ID and AMF UE NgAP ID.

[0110] 2) Bearer identification.

[0111] The bearer corresponding to this bearer identifier is used to transmit service data, for example, to enable the transmission of service data from the terminal to the access network device.

[0112] The bearer identifier can be assigned by the first network element, the second network element, or the AMF. When the bearer identifier is assigned by the first network element, the uniqueness of the bearer can be determined by the bearer identifier and the identifier information of the NF (such as the first network element).

[0113] 3) Address information of the data production node. The data production node can be a terminal, etc., and the address information can include IP address, port number, etc.

[0114] 4) The identifier or address information of the first network element.

[0115] 5) Identification or address information of the third network element, which may include IP address, port number, etc.

[0116] 6) Filter template information, which indicates the association between the bearer and the IP 5-tuple. This filter template can also be called a packet filter, traffic flow template (TFT), etc. The IP 5-tuple includes, for example, the source IP address, source port, destination IP address, destination port, and transport layer protocol.

[0117] 7) The uplink tunnel information of the tunnel, which can be found in the description of other embodiments.

[0118] 8) QoS information corresponding to the tunnel.

[0119] Typically, QoS information needs to be considered when establishing a tunnel or related operations in order to establish a tunnel or bearer that meets the requirements.

[0120] This embodiment, through the aforementioned first message, facilitates the establishment of a bearer by the access network device, enabling the transmission of terminal-related service data.

[0121] In some embodiments, after the first network element sends a first message to the access network device, the method further includes: the first network element receiving a second message sent by the access network device, the second message being used to indicate whether the terminal context has been successfully established, the second message including at least one of the following: a context establishment response message and a context modification response message.

[0122] This embodiment, through the interaction between the first network element and the access network device, helps the first network element and the access network device to maintain a consistent understanding of the terminal context.

[0123] In some embodiments, the second message includes at least one of the following:

[0124] 1) The second identification information of the terminal includes at least one of the following: a temporary identifier assigned to the UE by the NF (such as the first network element), such as NF ID and NF UE ID, or NF UE NxAP ID (on the RAN-NF interface); a temporary identifier assigned to the UE by the RAN, such as RAN ID and NF UE ID, or RAN UE NxAP ID (on the RAN-NF interface); a temporary UE identifier on the AMF-RAN interface, such as RAN UE NgAP ID, or RAN UE NgAP ID and AMF UE NgAP ID.

[0125] 2) Accept or reject bearer identifier, used to indicate whether a bearer was successfully established.

[0126] 3) Downlink tunnel information of the tunnel, the downlink tunnel information including at least one of the following: address information of the access network device; port number information of the access network device; access network side endpoint identification information of the tunnel.

[0127] This example can indicate the downlink tunnel information corresponding to each tunnel identifier at the granularity of each tunnel identifier.

[0128] This embodiment uses a second message to facilitate confirmation between the first network element and the access network equipment that the bearer and tunnel have been successfully established.

[0129] In some embodiments, after the first network element receives the second message sent by the access network device, the method further includes: the first network element sending a tunnel modification request message to the second network element or the third network element, the tunnel modification request message being used to indicate the downlink tunnel information.

[0130] In this embodiment, the first network element can uniquely determine the bearer of the terminal based on the terminal's second identifier and bearer identifier. For a specific bearer, the first network element can send its downlink data tunnel information to the second network element or the third network element.

[0131] In some embodiments, the method further includes: the first network element allocating the bearer identifier.

[0132] In some embodiments, the bearer identifier is assigned by the second network element, or it may be assigned by the AMF.

[0133] In some embodiments, the method further includes at least one of the following:

[0134] 1) The first network element sends a service request message to the terminal or the third network element, which is beneficial for requesting the terminal's service data.

[0135] 2) The first network element receives service result information or service data from the third network element, wherein the service result information may be generated based on the service data.

[0136] This embodiment facilitates the first network element in obtaining service result information or the service data.

[0137] To illustrate the data plane establishment method provided in this application, several specific embodiments will be described below. These embodiments use SF as the first network element (NF), DPF-C as the second network element, and DPF-U as the third network element. In other embodiments, the data plane function may not be separate; that is, DPF-C and DPF-U may be the same network element, namely DPF.

[0138] Example 1

[0139] In the case of distributed NAS in the 6G network architecture (i.e., the UE can communicate with any NF in NAS without going through the AMF), the UE can directly send a service establishment request to the NF. The core network side needs to allocate service flow identifiers (bearer identifiers and / or tunnel identifiers) and tunnel information to establish service flow connections (bearer connections and / or tunnel connections).

[0140] In this embodiment, the SF determines the bearer identifier; the data plane equipment determines the tunnel information.

[0141] In this embodiment, the first network element (NF) is used as the SF as an example, but the solution can be applied to other distributed service NFs.

[0142] As shown in Figure 4, the corresponding signaling flow includes the following steps:

[0143] Step 0: When the UE decides to initiate a specific service interaction with the 6G network, such as initiating a sensing service or an artificial intelligence service, the service modules within the UE generate service-related information, such as a sensing service establish / modify request and a service session ID, and place them in a service NAS (or NF NAS) message.

[0144] The UE sends a Radio Resource Control (RRC) message to the 6G RAN, which carries the aforementioned service NAS / NF NAS message.

[0145] It should be noted that the target object of the above service NAS / NF NAS message is NF, which is forwarded through RAN and AMF (optional), but RAN or AMF cannot parse it.

[0146] Step 1: The RAN forwards the above service NAS / NF NAS message to the 6G NF (such as SF).

[0147] Two possible implementation methods: 1a, the RAN forwards it to the 6G NF through the AMF; 1b: the RAN forwards it directly to the 6G NF.

[0148] Optionally, in method 1a, after receiving the service NAS / NF NAS forwarded by the RAN, the AMF determines whether the UE is authorized to initiate the service information, i.e., whether it is allowed to conduct this type of service or access this type of NF. Specifically, the AMF can obtain the UE's subscription information from the Unified Data Management (UDM), which includes information such as the UE's subscribed service type, network function type, and non-access stratum type (NAS type). Additionally, in this method, the AMF can also determine the target NF.

[0149] Optionally, in method 1b, the RAN can determine the target object NF before forwarding. One possible implementation is that the AMF determines the NF for a specific service of the UE and feeds the NF information back to the RAN. Other possible implementations include the RAN querying a network element information database (such as UDM, NRF, etc.) for the NF for a specific service, a specific area, and a specific UE.

[0150] Step 2: Optionally, the 6G NF can verify whether the UE is authorized to initiate the service information in the service NAS / NF NAS message.

[0151] Specifically, the 6G NF can interact with the UDM to obtain the UE's subscription information related to the service. The NF provides the UDM with the UE ID and service type / NF type / NAS type information. The NF obtains the subscription information from the UDM, which includes whether the service is allowed, the conditions under which the service is allowed, or the conditions under which the service is restricted.

[0152] Optionally, the 6G NF obtains service-related policy information from policy functions (such as PCF). This policy information includes service-related access policy information, QoS information, etc. The QoS information includes the QoS information of the user plane tunnel corresponding to the service.

[0153] The 6G NF establishes / modifies the corresponding service context for the UE for this service message (service establishment request).

[0154] Optionally, at least one of the following shall also be performed:

[0155] 1) If the UE does not provide a service session ID, the NF can assign the service session ID.

[0156] 2) The NF assigns a temporary identifier to the UE to uniquely identify the UE within the NF. The temporary identifier can be assigned in any of the following ways.

[0157] Method 1: The NF assigns a globally unique identifier to the UE (e.g., NF ID and UE ID within the NF). Under this method, other network elements can use this identifier to globally and uniquely identify a specific UE.

[0158] Method 2: To uniquely identify a user between the RAN and NF, the NF assigns an NF-assigned UE ID (which only guarantees unique identification of the UE within that NF), and the corresponding RAN also assigns a RAN-assigned UE ID (which only guarantees unique identification of the UE within that RAN). Only when these two are used together can a UE be globally uniquely identified. This method requires the subsequent RAN to generate a corresponding RAN-assigned UE ID.

[0159] Based on the service NAS / NF message from the UE, if the NF determines that this service of the UE still requires the establishment of a data tunnel (hereinafter referred to as a tunnel), then the NF assigns a data tunnel identifier. It should be noted that this data tunnel can also be understood as a data flow or a service flow, in which case the NF assigns a data flow identifier or a service flow identifier. Alternatively, it can be a data bearer (data service bearer, data plane bearer, etc. used to transmit service-related data), in which case the NF assigns a data bearer identifier, etc. This bearer identifier can be similar to a Quality of Service Flow Identity (QFI).

[0160] The purpose of tunnels is to transmit business data, such as the massive amounts of measurement data that may need to be transmitted in perception services, or the training data or model data that may need to be transmitted in AI services. These tunnels can be user plane tunnels or data plane tunnels.

[0161] Step 3: The 6G NF initiates a tunnel establishment request to the data plane function, such as sending a first resource allocation request message, to establish a tunnel for the UE.

[0162] In a possible 6G architecture, network devices with data plane or data management functions will be introduced. These network functions can perform unified data management within the 6G network. In this embodiment, the device can manage / allocate tunnel establishment or tunnel establishment resources. The 6G NF can send a tunnel establishment request to this device to request the establishment of a tunnel for data transmission, or to request the device to collect data, etc.

[0163] In some embodiments, the first resource allocation request message includes at least one of the following:

[0164] 1) First information, used to indicate the type of data production node.

[0165] The data production node in each embodiment of this application can be the node corresponding to the collected data, or the node to which the collected data is located. The type of the data production node can be a UE, or a RAN, etc. It should be noted that the terms "node" and "device" have similar meanings and can be used interchangeably. It can be understood that the first information is used to indicate the device type of the device corresponding to the collected data, such as UE, RAN, etc.

[0166] 2) The second piece of information is the identification information used to indicate the data production node.

[0167] This information is used to indicate the node identification information corresponding to the data production node. For example, when the data production node is a terminal, this identification information can be the International Mobile Subscriber Identification Number (IMSI) or the Subscription Permanent Identifier (SUPI), etc. It can be understood that the second information is used to indicate the identification information of the device corresponding to the collected data; for example, when the target device is a UE, it can be IMSI, SUPI, etc.

[0168] 3) The third type of information is used to indicate the address information of the data production node, such as the IP address or port number of the data production node.

[0169] 4) The fourth piece of information is used to indicate the type or granularity of the tunnel to be established.

[0170] The tunnel type information may include shared tunnels or dedicated tunnels, etc.; the tunnel granularity information may include terminal granularity or RAN granularity, etc. It should be noted that tunnel type information and granularity information can implicitly indicate each other. For example, when the tunnel type is a shared tunnel, the tunnel granularity is RAN granularity, and when the tunnel type is a dedicated tunnel, the tunnel granularity is UE granularity.

[0171] It is understandable that the type of data production node can also indicate the type or granularity of the tunnel to some extent. For example, when the type of data production node is RAN, the type of the tunnel can be a shared tunnel; when the type of data production node is UE, the tunnel type can also be a UE-level tunnel.

[0172] It should be noted that a tunnel can also refer to data flow, business flow, or carrier, etc.

[0173] 5) The fifth piece of information is used to indicate a request for the allocation of transmission or storage resources.

[0174] A request to allocate transmission resources can be understood as reserving or allocating resources (or allocating identifiers) for subsequent tunnel or bearer establishment, or requesting the establishment of a tunnel, etc.; a request to allocate storage resources can be understood as allocating resources for subsequent business data storage, such as storage space, allocating storage addresses, allocating storage identifiers, etc.

[0175] 6) The sixth piece of information is used to indicate a request to obtain the business data.

[0176] This business data could be related data from data production nodes, etc. It can be understood that the sixth piece of information can be used to indicate a request to obtain relevant data from data production nodes. DPF-C can use the sixth piece of information to determine whether to establish a connection with the data production node, such as establishing a tunnel or bearer. This sixth piece of information can also be referred to as an indication to request the establishment of a connection.

[0177] 7) The seventh piece of information is used to indicate the request for information about the data collection node.

[0178] For example, a request can be made to obtain the identification information, IP address information, port number information, etc. of a data collection node in order to request the data collection node to help collect business data. The data collection node can be a third network element, such as DPF-U.

[0179] 8) The eighth piece of information is used to indicate the carrier identifier.

[0180] The bearer corresponding to this bearer identifier is used to transmit service data, for example, to enable the transmission of service data from the terminal to the access network device.

[0181] When the bearer identifier is assigned by the NF, in order to ensure the uniqueness of the bearer identifier, the eighth information can also indicate the identifier information of the NF (such as the first network element) itself, and then determine the uniqueness of the bearer through the bearer identifier and the identifier information of the NF.

[0182] The bearer identifier can be assigned by the first network element, the second network element, or the AMF.

[0183] 9) The ninth piece of information is used to indicate Quality of Service (QoS) information.

[0184] Typically, QoS information needs to be considered when establishing a tunnel or related operations in order to establish a tunnel or bearer that meets the requirements.

[0185] 10) The tenth piece of information is used to indicate the reporting conditions of the business data.

[0186] The reporting conditions include, for example, real-time reporting, reporting upon receiving business data, scheduled reporting, and periodic reporting.

[0187] 11) Eleventh information, used to indicate the notification address of the business data.

[0188] The reporting address can be an IP address, or it can be the identification information or address information of the NF (such as the first network element).

[0189] Steps 4-5: Optionally, the data plane function can be divided into data plane management function (DPF-C) and data plane data function (DPF-U). The data plane management function can also be called data plane function-control plane (DPF-CP), which can interact with other network devices for control signaling and is responsible for data control, etc. The data plane data function can also be called data plane function-user plane (DPF-UP), etc., which can interact with other network devices for data-related interactions and is responsible for data transmission, etc.

[0190] When a DPF is divided into DPF-C and DPF-U, DPF-C can interact with DPF-U to request resource allocation, etc.

[0191] For example, DPF-C sends a second resource allocation request message to DPF-U, which is used to request the establishment of a tunnel for transmitting the service data; DPF-C receives a second resource allocation response message sent by DPF-U, which is used to indicate the resource allocation result.

[0192] Specifically, the second resource allocation request message may carry at least one of the above information from the first to the eleventh information.

[0193] DPF-U allocates tunnel resources (optionally based on QoS requirements) and returns a second resource allocation response message to DPF-C. The second resource allocation response message may include uplink tunnel information.

[0194] Uplink tunnel information includes at least one of the following:

[0195] 1) Address information of DPF-U, which includes, for example, IP address, MAC address, etc. The third network element can be a data collection node.

[0196] 2) Port information for DPF-U, which may include, for example, the Transmission Control Protocol (TCP) port number, the User Datagram Protocol (UDP) port number, and the Quick UDP Internet Connections (QUIC) port number.

[0197] 3) The core network side endpoint identification information of the tunnel, for example, the identification information can be the Tunnel Endpoint Identifier (TEID), which can be assigned by DPF-C or DPF-U.

[0198] Step 6: DPF-C returns the first resource allocation response message to 6G NF, which may include uplink tunnel information.

[0199] Uplink tunnel information includes at least one of the following:

[0200] 1) Address information of DPF-U, which includes, for example, IP address, MAC address, etc. The third network element can be a data collection node.

[0201] 2) Port information for DPF-U, which may include, for example, the Transmission Control Protocol (TCP) port number, the User Datagram Protocol (UDP) port number, and the Quick UDP Internet Connections (QUIC) port number.

[0202] 3) The core network side endpoint identification information of the tunnel, for example, the identification information can be the Tunnel Endpoint Identifier (TEID), which can be assigned by DPF-C or DPF-U.

[0203] Step 7: The NF sends a Context Establishment / Modification Request message to the RAN to establish the UE context on the RAN-NF interface. The Context Establishment / Modification Request message contains at least one of the following:

[0204] 1) The first identification information of the UE includes at least one of the following: a temporary identifier assigned to the UE by the NF (such as the first network element), see step 5, such as NF ID and NF UE ID, or NF UE NxAP ID; a temporary identifier of the UE on the AMF-RAN interface, such as RAN UE NgAP ID, or RAN UE NgAP ID and AMF UE NgAP ID.

[0205] 2) Bearer identifier, which may be assigned by NF in step 2.

[0206] 3) Address information of the data production node, which can be a terminal, etc.

[0207] 4) The identifier or address information of the first network element.

[0208] 5) The identifier or address information of the DPF-U, which may include the IP address, port number, etc.

[0209] 6) Filter template information, which indicates the association between the bearer and the IP 5-tuple. This filter template can also be called a packet filter, traffic flow template (TFT), etc. The IP 5-tuple includes, for example, the source IP address, source port, destination IP address, destination port, and transport layer protocol.

[0210] 7) The uplink tunnel information of the tunnel, which can be found in the description of step 6.

[0211] 8) QoS information corresponding to the tunnel.

[0212] There are two methods here: 7a: forwarded to RAN via AMF; 7b: forwarded directly to RAN via NF.

[0213] In method 7b, the NF needs to obtain target RAN information, such as RAN ID, address, and port number, before forwarding. In one implementation, the NF can obtain the target RAN information from the AMF in step 1.

[0214] Step 8: The RAN determines the bearer that needs to be established for the air interface based on the UE identifier, address, and bearer identifier (determined in step 2). This air interface bearer can also be called an air interface tunnel.

[0215] Specifically, the RAN and the target UE interact to determine the bearer establishment rules and establish the bearer. At the same time, the RAN allocates tunnel resources (optionally according to QoS requirements) and determines the downlink tunnel information.

[0216] Downlink tunnel information includes at least one of the following:

[0217] 1) RAN address information, such as RAN IP address, MAC address, etc.

[0218] 2) RAN port information, such as TCP port number, UDP port number, QUIC port number, etc.

[0219] 3) Tunnel RAN side endpoint identification information, such as the TEID assigned to the RAN side.

[0220] Step 9: The RAN sends a context establishment / modification response message to the 6G NF to indicate whether the UE context on the RAN-NF interface was successfully established. The message must contain at least one of the following:

[0221] 1) The second identification information of the UE includes at least one of the following: a temporary identifier assigned to the UE by the NF (such as the first network element), see step 5, such as NF ID and NF UE ID, or NF UE NxAP ID (on the RAN-NF interface); (same as step 8) a temporary identifier assigned to the UE by the RAN, such as RAN ID and NF UE ID, or RAN UE NxAP ID (on the RAN-NF interface); a temporary UE identifier on the AMF-RAN interface, such as RAN UE NgAP ID, or RAN UE NgAP ID and AMF UE NgAP ID.

[0222] 2) Accept or reject bearer identifier, used to indicate whether a bearer was successfully established.

[0223] 3) Downlink tunnel information of the tunnel, the downlink tunnel information including at least one of the following: address information of the access network device; port number information of the access network device; access network side endpoint identification information of the tunnel.

[0224] This example can indicate the downlink tunnel information corresponding to each tunnel identifier at the granularity of each tunnel identifier.

[0225] Context creation / modification response messages can be sent via AMF or directly.

[0226] Step 10: Optionally, the NF sends a tunnel modification request message to the DPF-C or DPF-U to indicate the downlink tunnel information received from the RAN.

[0227] Specifically, the NF can uniquely identify the UE's bearer based on the UE's second identifier and bearer identifier. For a specific bearer, the NF sends its downlink tunnel information to the DPF-U.

[0228] At this point, the service tunnel and bearer have been successfully established, including the air interface tunnel (DPF-U to RAN) and the UE bearer (RAN-UE), which can be used to transmit user plane data or media data of the service.

[0229] Step 12: Optionally, the NF also sends a downlink service NAS / NF NAS message to the UE via the RAN, which contains a service request message.

[0230] This step can be combined with step 8 and sent simultaneously, or it can be sent separately. When sent separately, the order of time is not restricted.

[0231] This step can be performed with or without AMF.

[0232] Step 13: Optionally, after receiving service result information / service data, the DPF-U can send the service result information / service data to the NF according to the reporting conditions.

[0233] Example 2

[0234] The signaling flow corresponding to this embodiment is shown in Figure 5. The difference from Embodiment 1 is that in this embodiment, the bearer identifier is allocated by the data plane device (see step 3). The subscription information and QoS information of the data production node can be obtained by the data plane device or sent in step 2.

[0235] Example 3

[0236] The signaling flow corresponding to this embodiment is shown in Figure 6. The difference from Embodiment 1 is that the bearer identifier is allocated by the AMF in this embodiment.

[0237] For example, before step 3, the SF sends the identification information of the data production node and its own identification information to the AMF, requesting the AMF to allocate a bearer identifier; or, in step 7, when the SF sends a bearer / tunnel establishment request to the RAN / UE through the AMF, the AMF can allocate a bearer identifier after receiving the SF's request and before sending the message to the RAN / UE, and send it to the RAN, UE, etc.; or it can be sent to the SF in step 9.

[0238] Example 4

[0239] The signaling flow corresponding to this embodiment is shown in Figure 7. The difference from Embodiment 2 is that: SF directly sends a service data request to the data plane device, requests the data plane device to allocate a bearer identifier, establish a tunnel, and collect and return service data.

[0240] The data plane equipment directly sends tunnel establishment requests, bearer identifiers, tunnel information, etc. to the RAN and UE (see step 7).

[0241] The data plane establishment method according to embodiments of this application has been described in detail above with reference to Figures 2 to 7. The data plane establishment methods according to several other embodiments of this application will now be described in detail with reference to Figures 8 and 9. It is understood that the descriptions of the second network element, the third network element, the terminal, and the access network device are the same as or correspond to the descriptions of the first network element side in the methods shown in Figures 2 to 7. To avoid repetition, relevant descriptions are appropriately omitted.

[0242] Figure 8 is a schematic flowchart of the data plane establishment method according to an embodiment of this application, which can be applied to a second network element. As shown in Figure 8, the method 800 includes the following steps.

[0243] S802: The second network element receives a first resource allocation request message sent by the first network element. The first resource allocation request message is used to request the establishment of a tunnel, and the tunnel is used to transmit service data.

[0244] S804: The second network element sends a first resource allocation response message to the first network element, the first resource allocation response message being used to indicate the resource allocation result.

[0245] The embodiments of this application facilitate the establishment of a tunnel for transmitting service data through message interaction between the first network element and the second network element, thereby enabling the transmission of service data.

[0246] In some embodiments, the method further includes: the second network element sending a second resource allocation request message to the third network element, the second resource allocation request message being used to request the establishment of a tunnel, the tunnel being used to transmit the service data; the second network element receiving a second resource allocation response message sent by the third network element, the second resource allocation response message being used to indicate a resource allocation result; wherein, the first resource allocation response message is generated based on the second resource allocation response message.

[0247] In some embodiments, the first resource allocation response message or the second resource allocation response message includes uplink tunnel information of the tunnel, the uplink tunnel information including at least one of the following: 1) address information of the third network element; 2) port number information of the third network element; 3) core network side endpoint identification information of the tunnel.

[0248] In some embodiments, the first resource allocation request message or the second resource allocation request message includes at least one of the following: 1) first information, used to indicate the type of data production node; 2) second information, used to indicate the identification information of the data production node; 3) third information, used to indicate the address information of the data production node; 4) fourth information, used to indicate the type information or granularity information of the tunnel; 5) fifth information, used to indicate a request to allocate transmission resources or storage resources; 6) sixth information, used to indicate a request to obtain the service data; 7) seventh information, used to indicate a request to obtain information of the data collection node; 8) eighth information, used to indicate the bearer identifier; 9) ninth information, used to indicate QoS information; 10) tenth information, used to indicate the reporting conditions of the service data; 11) eleventh information, used to indicate the reporting address of the service data.

[0249] In some embodiments, the method further includes: the second network element receiving a tunnel modification request message sent by the first network element, the tunnel modification request message being used to indicate downlink tunnel information of the tunnel; wherein the downlink tunnel information includes at least one of the following: address information of the access network device; port number information of the access network device; and access network side endpoint identification information of the tunnel.

[0250] In some embodiments, the method further includes: allocating a bearer identifier to the second network element.

[0251] Figure 9 is a schematic flowchart of the data plane establishment method according to an embodiment of this application, which can be applied to a third network element. As shown in Figure 9, the method 900 includes the following steps.

[0252] S902: The third network element receives a second resource allocation request message sent by the second network element. The second resource allocation request message is used to request the establishment of a tunnel, which is used to transmit service data.

[0253] S904: The third network element sends a second resource allocation response message to the second network element, the second resource allocation response message being used to indicate the resource allocation result.

[0254] The embodiments of this application facilitate the establishment of a tunnel for transmitting service data through message interaction between the second network element and the third network element, thereby enabling the transmission of service data.

[0255] In some embodiments, the second resource allocation response message includes uplink tunnel information of the tunnel, the uplink tunnel information including at least one of the following: 1) address information of the third network element; 2) port number information of the third network element; 3) core network side endpoint identification information of the tunnel.

[0256] In some embodiments, the second resource allocation request message includes at least one of the following: 1) first information indicating the type of data production node; 2) second information indicating the identification information of the data production node; 3) third information indicating the address information of the data production node; 4) fourth information indicating the type or granularity information of the tunnel; 5) fifth information indicating a request to allocate transmission resources or storage resources; 6) sixth information indicating a request to obtain the service data; 7) seventh information indicating a request to obtain information of the data collection node; 8) eighth information indicating a bearer identifier; 9) ninth information indicating QoS information; 10) tenth information indicating the reporting conditions of the service data; and 11) eleventh information indicating the reporting address of the service data.

[0257] In some embodiments, the method further includes: the third network element sending a third message to the access network device, the third message including at least one of the following: 1) first identification information of the terminal; 2) bearer identification; 3) address information of the data production node; 4) identification or address information of the first network element; 5) identification or address information of the third network element; 6) filtering template information, the filtering template information being used to indicate the association relationship between the bearer and the IP 5-tuple; 7) uplink tunnel information of the tunnel; 8) QoS information corresponding to the tunnel.

[0258] In some embodiments, the third message includes at least one of the following: a context establishment request message and a context modification request message.

[0259] In some embodiments, the method further includes: the third network element receiving a tunnel modification request message sent by the first network element, the tunnel modification request message being used to indicate downlink tunnel information of the tunnel; wherein the downlink tunnel information includes at least one of the following: address information of the access network device; port number information of the access network device; and access network side endpoint identification information of the tunnel.

[0260] In some embodiments, the method further includes at least one of the following: 1) the third network element receives a service request message sent by the first network element; 2) the third network element sends service result information or the service data to the first network element.

[0261] Figure 10 is a schematic diagram of the implementation flow of the data plane establishment method according to an embodiment of this application, which can be applied to a terminal. As shown in Figure 10, the method 1000 includes the following steps.

[0262] S1002: The terminal sends a service request message to the first network element. The service request message is used to request the establishment of a tunnel, and the tunnel is used to transmit service data.

[0263] The embodiments of this application facilitate the establishment of a tunnel for transmitting service data through message interaction between the terminal and the first network element, thereby enabling the transmission of service data.

[0264] In some embodiments, the method further includes: the terminal sending the service data to a third network element.

[0265] Figure 11 is a schematic diagram of the implementation flow of the data plane establishment method according to an embodiment of this application, which can be applied to access network devices. As shown in Figure 11, the method 1100 includes the following steps.

[0266] S1102: The access network device receives the first message sent by the first network element.

[0267] S1104: The access network device establishes a bearer based on the first message, and the bearer is used to transmit service data.

[0268] The embodiments of this application facilitate the establishment of a bearer for transmitting service data through message interaction between the access network device and the first network element, thereby enabling the transmission of service data.

[0269] In some embodiments, the method further includes: the access network device sending a second message to the first network element; wherein the first message includes at least one of the following: 1) first identification information of the terminal; 2) bearer identification; 3) address information of the data production node; 4) identification or address information of the first network element; 5) identification or address information of the third network element; 6) filtering template information, the filtering template information being used to indicate the association relationship between the bearer and the IP 5-tuple; 7) uplink tunnel information of the tunnel; 8) QoS information corresponding to the tunnel; and / or, the second message includes at least one of the following: 1) second identification information of the terminal; 2) bearer identification of acceptance or rejection; 3) downlink tunnel information of the tunnel, the downlink tunnel information including at least one of the following: address information of the access network device; port number information of the access network device; access network side endpoint identification information of the tunnel; wherein, the tunnel is used to transmit the service data.

[0270] The data plane establishment method provided in this application can be executed by a data plane establishment device. This application uses an example of a data plane establishment device executing the data plane establishment method to illustrate the data plane establishment device provided in this application.

[0271] This application provides a data plane establishment apparatus. As an example, the data plane establishment apparatus can be a communication device or a component within a communication device, such as a chip. The communication device can be a network-side device or a server, etc. Exemplarily, the network-side device can include, but is not limited to, the types of network-side devices 12 listed above; this application does not specifically limit the types.

[0272] The data plane establishment device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, etc., such as central processing units (CPUs), microprocessors, digital signal processors (DSPs), artificial intelligence (AI) processors, graphics processing units (GPUs), application-specific integrated circuits (ASICs), network processors (NPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceivers, pins, circuits, buses, radio frequency units, etc.

[0273] Specifically, referring to Figure 12, when the data plane establishment device is a first network element or a component within the first network element, the data plane establishment device 1200 includes:

[0274] The sending module 1202 is used to send a first resource allocation request message to the second network element. The first resource allocation request message is used to request the establishment of a tunnel, and the tunnel is used to transmit service data.

[0275] The receiving module 1204 is used to receive a first resource allocation response message sent by the second network element, wherein the first resource allocation response message is used to indicate the resource allocation result.

[0276] The embodiments of this application facilitate the establishment of a tunnel for transmitting service data through message interaction between the first network element and the second network element, thereby enabling the transmission of service data.

[0277] In some embodiments, the sending module 1202 is further configured to send a first message to the access network device, the first message including at least one of the following: 1) first identification information of the terminal; 2) bearer identification; 3) address information of the data production node; 4) identification or address information of the first network element; 5) identification or address information of the third network element; 6) filtering template information, the filtering template information being used to indicate the association relationship between the bearer and the IP 5-tuple; 7) uplink tunnel information of the tunnel; 8) QoS information corresponding to the tunnel.

[0278] In some embodiments, the receiving module 1204 is further configured to receive a second message sent by the access network device, the second message including at least one of the following: 1) second identification information of the terminal; 2) bearer identifier for acceptance or rejection; 3) downlink tunnel information of the tunnel, the downlink tunnel information including at least one of the following: address information of the access network device; port number information of the access network device; access network side endpoint identifier information of the tunnel.

[0279] In some embodiments, the sending module 1202 is further configured to send a tunnel modification request message to the second network element or the third network element. The tunnel modification request message is used to indicate downlink tunnel information, and the downlink tunnel information includes at least one of the following: address information of the access network device; port number information of the access network device; and access network side endpoint identification information of the tunnel.

[0280] In some embodiments, the sending module 1202 is further configured to send a service request message to a terminal or a third network element; or, the receiving module 1204 is further configured to receive service result information or the service data from the third network element.

[0281] Specifically, referring to Figure 13, when the data plane establishment device is a second network element or a component within a second network element, the data plane establishment device 1300 includes:

[0282] The receiving module 1302 is used to receive a first resource allocation request message sent by a first network element. The first resource allocation request message is used to request the establishment of a tunnel, and the tunnel is used to transmit service data.

[0283] The sending module 1304 is used to send a first resource allocation response message to the first network element, the first resource allocation response message being used to indicate the resource allocation result.

[0284] The embodiments of this application facilitate the establishment of a tunnel for transmitting service data through message interaction between the first network element and the second network element, thereby enabling the transmission of service data.

[0285] In some embodiments, the sending module 1304 is further configured to send a second resource allocation request message to a third network element, the second resource allocation request message being used to request the establishment of a tunnel, the tunnel being used to transmit the service data; the receiving module 1302 is further configured to receive a second resource allocation response message sent by the third network element, the second resource allocation response message being used to indicate the resource allocation result; wherein, the first resource allocation response message is generated based on the second resource allocation response message.

[0286] In some embodiments, the receiving module 1302 is further configured to receive a tunnel modification request message sent by a first network element, the tunnel modification request message being used to indicate downlink tunnel information of the tunnel; wherein, the downlink tunnel information includes at least one of the following: address information of the access network device; port number information of the access network device; and access network side endpoint identification information of the tunnel.

[0287] Specifically, referring to Figure 14, when the data plane establishment device is a third network element or a component within a third network element, the data plane establishment device 1400 includes:

[0288] The receiving module 1402 is used to receive a second resource allocation request message sent by a second network element. The second resource allocation request message is used to request the establishment of a tunnel, and the tunnel is used to transmit service data.

[0289] The sending module 1404 is used to send a second resource allocation response message to the second network element, the second resource allocation response message being used to indicate the resource allocation result.

[0290] The embodiments of this application facilitate the establishment of a tunnel for transmitting service data through message interaction between the second network element and the third network element, thereby enabling the transmission of service data.

[0291] In some embodiments, the sending module 1404 is further configured to send a third message to the access network device, the third message including at least one of the following: 1) first identification information of the terminal; 2) bearer identification; 3) address information of the data production node; 4) identification or address information of the first network element; 5) identification or address information of the third network element; 6) filtering template information, the filtering template information being used to indicate the association relationship between the bearer and the IP 5-tuple; 7) uplink tunnel information of the tunnel; 8) QoS information corresponding to the tunnel.

[0292] In some embodiments, the receiving module 1402 is further configured to receive a tunnel modification request message sent by a first network element, the tunnel modification request message being used to indicate downlink tunnel information of the tunnel; wherein, the downlink tunnel information includes at least one of the following: address information of the access network device; port number information of the access network device; access network side endpoint identification information of the tunnel.

[0293] The data plane establishment apparatus provided in this application embodiment can implement the various processes implemented in the method embodiments of Figures 2 to 9 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0294] Specifically, referring to Figure 15, when the data plane establishment device is a terminal or a component in a terminal, the data plane establishment device 1500 includes:

[0295] The sending module 1502 is used to send a service request message to the first network element. The service request message is used to request the establishment of a tunnel, and the tunnel is used to transmit service data.

[0296] The embodiments of this application facilitate the establishment of a tunnel for transmitting service data through message interaction between the terminal and the first network element, thereby enabling the transmission of service data.

[0297] In some embodiments, the sending module 1502 is further configured to send the service data by the third network element.

[0298] Specifically, referring to Figure 16, when the data plane establishment device is an access network device or a component within an access network device, the data plane establishment device 1600 includes:

[0299] The receiving module 1602 is used to receive the first message sent by the first network element.

[0300] The processing module 1604 is used to establish a bearer based on the first message, the bearer being used to transmit service data.

[0301] The embodiments of this application facilitate the establishment of a bearer for transmitting service data through message interaction between the access network device and the first network element, thereby enabling the transmission of service data.

[0302] In some embodiments, the system further includes a sending module for sending a second message to the first network element; wherein the first message includes at least one of the following: 1) first identification information of the terminal; 2) bearer identification; 3) address information of the data production node; 4) identification or address information of the first network element; 5) identification or address information of the third network element; 6) filtering template information, the filtering template information being used to indicate the association relationship between the bearer and the IP 5-tuple; 7) uplink tunnel information of the tunnel; 8) QoS information corresponding to the tunnel; and / or, the second message includes at least one of the following: 1) second identification information of the terminal; 2) bearer identification of acceptance or rejection; 3) downlink tunnel information of the tunnel, the downlink tunnel information including at least one of the following: address information of the access network device; port number information of the access network device; access network side endpoint identification information of the tunnel; wherein the tunnel is used to transmit the service data.

[0303] As shown in Figure 17, this application embodiment also provides a communication device 1700, including a processor 1701 and a memory 1702. The memory 1702 stores a program or instructions that can run on the processor 1701. For example, when the communication device 1700 is a terminal, the program or instructions executed by the processor 1701 implement the various steps of the above-described data plane establishment method embodiment and achieve the same technical effect. When the communication device 1700 is a network-side device, the program or instructions executed by the processor 1701 implement the various steps of the above-described data plane establishment method embodiment and achieve the same technical effect. To avoid repetition, this will not be described again here.

[0304] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG10. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal may be the data plane establishment device shown in FIG15. Specifically, FIG18 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0305] The terminal 1800 includes, but is not limited to, at least some of the following components: radio frequency unit 1801, network module 1802, audio output unit 1803, input unit 1804, sensor 1805, display unit 1806, user input unit 1807, interface unit 1808, memory 1809, and processor 1810.

[0306] Those skilled in the art will understand that the terminal 1800 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the processor 1810 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 18 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0307] It should be understood that, in this embodiment, the input unit 1804 may include a graphics processor 18041 and a microphone 18042. The graphics processor 18041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1806 may include a display panel 18061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1807 includes at least one of a touch panel 18071 and other input devices 18072. The touch panel 18071 is also called a touch screen. The touch panel 18071 may include a touch detection device and a touch controller. Other input devices 18072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0308] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 1801 can transmit it to the processor 1810 for processing; in addition, the radio frequency unit 1801 can send uplink data to the network-side device. Typically, the radio frequency unit 1801 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0309] The memory 1809 can be used to store software programs or instructions, as well as various data. The memory 1809 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1809 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 1809 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0310] Processor 1810 may include one or more processing units; optionally, processor 1810 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1810.

[0311] The radio frequency unit 1801 is used to send a service request message to the first network element. The service request message is used to request the establishment of a tunnel, and the tunnel is used to transmit service data.

[0312] The embodiments of this application facilitate the establishment of a tunnel for transmitting service data through message interaction between the terminal and the first network element, thereby enabling the transmission of service data.

[0313] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be described again here.

[0314] Specifically, this application embodiment also provides a network-side device, which can be the data plane establishment device shown in FIG16. As shown in FIG19, the network-side device 1900 includes: an antenna 191, a radio frequency device 192, a baseband device 193, a processor 194, and a memory 195. The antenna 191 is connected to the radio frequency device 192. In the uplink direction, the radio frequency device 192 receives information through the antenna 191 and sends the received information to the baseband device 193 for processing. In the downlink direction, the baseband device 193 processes the information to be transmitted and sends it to the radio frequency device 192. The radio frequency device 192 processes the received information and transmits it through the antenna 191.

[0315] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 193, which includes a baseband processor.

[0316] The baseband device 193 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG19. One of the chips is, for example, a baseband processor, which is connected to the memory 195 via a bus interface to call the program or instructions in the memory 195 to execute the network-side device operation shown in the above method embodiment.

[0317] The network-side device may also include a network interface 196, such as a Common Public Radio Interface (CPRI).

[0318] The radio frequency device 192 is used to receive a first message sent by a first network element. The processor 194 is used to establish a bearer based on the first message, the bearer being used to transmit service data.

[0319] In addition, the network-side device 1900 of this application embodiment also includes: a program or instructions stored in memory 195 and executable on processor 194. The processor 194 calls the program or instructions in memory 195 to execute the methods executed by each module shown in FIG16 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0320] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiments shown in FIG2, FIG8, or FIG9. This network-side device embodiment corresponds to the above-described network-side device method embodiments. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effects.

[0321] Specifically, this application also provides a network-side device. As shown in FIG20, the network-side device 2000 includes a processor 2001, a network interface 2002, and a memory 2003. The network-side device may be the data plane establishment apparatus shown in FIG12, FIG13, or FIG14. The network interface 2002 is, for example, a Common Public Radio Interface (CPRI).

[0322] Specifically, network interface 2002 is used to send a first resource allocation request message to the second network element, the first resource allocation request message being used to request the establishment of a tunnel for transmitting service data; and to receive a first resource allocation response message sent by the second network element, the first resource allocation response message being used to indicate a resource allocation result. Alternatively, network interface 2002 is used to receive a first resource allocation request message sent by the first network element, the first resource allocation request message being used to request the establishment of a tunnel for transmitting service data; and to send a first resource allocation response message to the first network element, the first resource allocation response message being used to indicate a resource allocation result. Alternatively, network interface 2002 is used to receive a second resource allocation request message sent by the second network element, the second resource allocation request message being used to request the establishment of a tunnel for transmitting service data; and to send a second resource allocation response message to the second network element, the second resource allocation response message being used to indicate a resource allocation result.

[0323] In addition, the network-side device 2000 of this application embodiment also includes: a program or instructions stored in the memory 2003 and executable on the processor 2001. The processor 2001 calls the program or instructions in the memory 2003 to execute the methods executed by the modules shown in FIG12, FIG13 or FIG14 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0324] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described data plane establishment method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0325] The processor mentioned above is either the processor in the terminal described in the above embodiments or the processor in the network-side device. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0326] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described data plane establishment method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0327] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0328] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described data plane establishment method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0329] This application also provides a data plane establishment system, including: a terminal and a network-side device, wherein the network-side device can be used to execute the steps of the data plane establishment method described above.

[0330] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0331] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.), and the computer software product includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0332] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A method for establishing a data surface, comprising: The first network element sends a first resource allocation request message to the second network element. The first resource allocation request message is used to request the establishment of a tunnel, and the tunnel is used to transmit service data. The first network element receives a first resource allocation response message sent by the second network element, the first resource allocation response message being used to indicate the resource allocation result.

2. The method according to claim 1, wherein, The first resource allocation response message includes uplink tunnel information of the tunnel, and the uplink tunnel information includes at least one of the following: Address information of the third network element; Port number information of the third network element; The core network side endpoint identification information of the tunnel.

3. The method according to claim 1 or 2, wherein, The first resource allocation request message includes at least one of the following: The first piece of information is used to indicate the type of data production node; The second piece of information is the identification information used to indicate the data production node; The third piece of information is used to indicate the address information of the data production node; The fourth piece of information is used to indicate the type or granularity of the tunnel. The fifth piece of information is used to indicate a request for the allocation of transmission or storage resources; The sixth piece of information is used to indicate a request to obtain the business data; The seventh piece of information is used to indicate the request for information about the data collection node; The eighth piece of information is used to indicate the carrier identifier; The ninth piece of information is used to indicate Quality of Service (QoS) information; The tenth piece of information is used to indicate the reporting conditions for the business data; The eleventh piece of information is used to indicate the reporting address of the business data.

4. The method according to any one of claims 1 to 3, wherein, The method further includes: the first network element sending a first message to the access network device, the first message including at least one of the following: The terminal's first identification information; Carrying identification; Address information of data production nodes; The identifier or address information of the first network element; The identifier or address information of the third network element; Filter template information, which is used to indicate the association between bearer and IP 5-tuple; The upstream tunnel information of the tunnel; The QoS information corresponding to the tunnel.

5. The method according to claim 4, wherein, The first message includes at least one of the following: a context establishment request message and a context modification request message.

6. The method according to claim 4 or 5, wherein, The method further includes: the first network element receiving a second message sent by the access network device, the second message including at least one of the following: The terminal's second identification information; Acceptance or rejection identifier; The downlink tunnel information of the tunnel includes at least one of the following: address information of the access network device; port number information of the access network device; and access network side endpoint identification information of the tunnel.

7. The method according to claim 6, wherein, The second message includes at least one of the following: a context establishment response message and a context modification response message.

8. The method according to claim 7, wherein, The method further includes: The first network element sends a tunnel modification request message to the second or third network element, the tunnel modification request message being used to indicate the downlink tunnel information.

9. The method according to claim 3, 4 or 6, wherein, The method further includes: The first network element assigns the bearer identifier.

10. The method according to claim 3, 4 or 6, wherein, The bearer identifier is assigned by the second network element.

11. The method according to any one of claims 1 to 10, wherein, The method further includes at least one of the following: The first network element sends a service request message to the terminal or the third network element; The first network element receives service result information or service data from the third network element.

12. A method for establishing a data surface, comprising: The second network element receives a first resource allocation request message sent by the first network element. The first resource allocation request message is used to request the establishment of a tunnel, and the tunnel is used to transmit service data. The second network element sends a first resource allocation response message to the first network element, the first resource allocation response message being used to indicate the resource allocation result.

13. The method according to claim 12, wherein, The method further includes: The second network element sends a second resource allocation request message to the third network element. The second resource allocation request message is used to request the establishment of a tunnel, and the tunnel is used to transmit the service data. The second network element receives a second resource allocation response message sent by the third network element, the second resource allocation response message being used to indicate the resource allocation result; The first resource allocation response message is generated based on the second resource allocation response message.

14. The method according to claim 13, wherein, The first resource allocation response message or the second resource allocation response message includes uplink tunnel information of the tunnel, and the uplink tunnel information includes at least one of the following: The address information of the third network element; The port number information of the third network element; The core network side endpoint identification information of the tunnel.

15. The method according to claim 13, wherein, The first resource allocation request message or the second resource allocation request message includes at least one of the following: The first piece of information is used to indicate the type of data production node; The second piece of information is the identification information used to indicate the data production node; The third piece of information is used to indicate the address information of the data production node; The fourth piece of information is used to indicate the type or granularity of the tunnel. The fifth piece of information is used to indicate a request for the allocation of transmission or storage resources; The sixth piece of information is used to indicate a request to obtain the business data; The seventh piece of information is used to indicate the request for information about the data collection node; The eighth piece of information is used to indicate the carrier identifier; The ninth piece of information is used to indicate QoS information; The tenth piece of information is used to indicate the reporting conditions for the business data; The eleventh piece of information is used to indicate the reporting address of the business data.

16. The method according to any one of claims 12 to 15, wherein, The method further includes: The second network element receives a tunnel modification request message sent by the first network element, the tunnel modification request message being used to indicate the downlink tunnel information of the tunnel; The downlink tunnel information includes at least one of the following: the address information of the access network device; the port number information of the access network device; and the access network side endpoint identification information of the tunnel.

17. The method according to any one of claims 12 to 16, wherein, The method further includes: The second network element is assigned a bearer identifier.

18. A method for establishing a data surface, comprising: The third network element receives a second resource allocation request message sent by the second network element. The second resource allocation request message is used to request the establishment of a tunnel, and the tunnel is used to transmit service data. The third network element sends a second resource allocation response message to the second network element, the second resource allocation response message being used to indicate the resource allocation result.

19. The method according to claim 18, wherein, The second resource allocation response message includes uplink tunnel information of the tunnel, and the uplink tunnel information includes at least one of the following: The address information of the third network element; The port number information of the third network element; The core network side endpoint identification information of the tunnel.

20. The method according to claim 18 or 19, wherein, The second resource allocation request message includes at least one of the following: The first piece of information is used to indicate the type of data production node; The second piece of information is the identification information used to indicate the data production node; The third piece of information is used to indicate the address information of the data production node; The fourth piece of information is used to indicate the type or granularity of the tunnel. The fifth piece of information is used to indicate a request for the allocation of transmission or storage resources; The sixth piece of information is used to indicate a request to obtain the business data; The seventh piece of information is used to indicate the request for information about the data collection node; The eighth piece of information is used to indicate the carrier identifier; The ninth piece of information is used to indicate QoS information; The tenth piece of information is used to indicate the reporting conditions for the business data; The eleventh piece of information is used to indicate the reporting address of the business data.

21. The method according to any one of claims 18 to 20, wherein, The method further includes: The third network element sends a third message to the access network device, the third message including at least one of the following: The terminal's first identification information; Carrying identification; Address information of data production nodes; The identifier or address information of the first network element; The identifier or address information of the third network element; Filter template information, which is used to indicate the association between bearer and IP 5-tuple; The upstream tunnel information of the tunnel; The QoS information corresponding to the tunnel.

22. The method according to claim 21, wherein, The third message includes at least one of the following: a context establishment request message and a context modification request message.

23. The method according to any one of claims 18 to 20, wherein, The method further includes: The third network element receives a tunnel modification request message sent by the first network element, the tunnel modification request message being used to indicate the downlink tunnel information of the tunnel; The downlink tunnel information includes at least one of the following: the address information of the access network device; the port number information of the access network device; and the access network side endpoint identification information of the tunnel.

24. The method according to any one of claims 18 to 23, wherein, The method further includes at least one of the following: The third network element receives the transmission service request message sent by the first network element; The third network element sends service result information or service data to the first network element.

25. A method for establishing a data surface, comprising: The terminal sends a service request message to the first network element. The service request message is used to request the establishment of a tunnel, and the tunnel is used to transmit service data.

26. The method of claim 25, wherein, The method further includes: The terminal sends the service data to the third network element.

27. A method for establishing a data surface, comprising: The access network device receives the first message sent by the first network element; The access network device establishes a bearer based on the first message, and the bearer is used to transmit service data.

28. The method according to claim 27, wherein, The method further includes: the access network device sending a second message to the first network element; The first message includes at least one of the following: The terminal's first identification information; Carrying identification; Address information of data production nodes; The identifier or address information of the first network element; The identifier or address information of the third network element; Filter template information, which is used to indicate the association between bearer and IP 5-tuple; Information on the tunnel's upstream passage; QoS information corresponding to the tunnel; and / or The second message includes at least one of the following: The terminal's second identification information; Acceptance or rejection identifier; The downlink tunnel information includes at least one of the following: address information of the access network device; port number information of the access network device; and access network side endpoint identification information of the tunnel. The tunnel is used to transmit the service data.

29. A data plane establishment apparatus, comprising: The sending module is used to send a first resource allocation request message to the second network element. The first resource allocation request message is used to request the establishment of a tunnel, and the tunnel is used to transmit service data. The receiving module is configured to receive a first resource allocation response message sent by the second network element, wherein the first resource allocation response message is used to indicate the resource allocation result.

30. The apparatus according to claim 29, wherein, The sending module is further configured to send a first message to the access network device, the first message including at least one of the following: The terminal's first identification information; Carrying identification; Address information of data production nodes; The identifier or address information of the first network element; The identifier or address information of the third network element; Filter template information, which is used to indicate the association between bearer and IP 5-tuple; The upstream tunnel information of the tunnel; The QoS information corresponding to the tunnel.

31. The apparatus according to claim 30, wherein, The receiving module is further configured to receive a second message sent by the access network device, the second message including at least one of the following: The terminal's second identification information; Acceptance or rejection identifier; The downlink tunnel information of the tunnel includes at least one of the following: address information of the access network device; port number information of the access network device; The access network side endpoint identification information of the tunnel.

32. The apparatus according to claim 31, wherein, The sending module is further configured to send a tunnel modification request message to the second network element or the third network element. The tunnel modification request message is used to indicate downlink tunnel information, and the downlink tunnel information includes at least one of the following: address information of the access network device; port number information of the access network device. The access network side endpoint identification information of the tunnel.

33. The apparatus according to any one of claims 29 to 32, wherein, The sending module is also used to send service request messages to the terminal or a third network element; or, The receiving module is also used to receive service result information or service data from a third network element.

34. A data plane establishment apparatus, comprising: The receiving module is configured to receive a first resource allocation request message sent by a first network element, wherein the first resource allocation request message is used to request the establishment of a tunnel, and the tunnel is used to transmit service data. The sending module is used to send a first resource allocation response message to the first network element, wherein the first resource allocation response message is used to indicate the resource allocation result.

35. The apparatus according to claim 34, wherein, The sending module is further configured to send a second resource allocation request message to the third network element, the second resource allocation request message being used to request the establishment of a tunnel, the tunnel being used to transmit the service data; The receiving module is further configured to receive a second resource allocation response message sent by the third network element, wherein the second resource allocation response message is used to indicate the resource allocation result; The first resource allocation response message is generated based on the second resource allocation response message.

36. The apparatus according to claim 34 or 35, wherein, The receiving module is further configured to receive a tunnel modification request message sent by the first network element, the tunnel modification request message being used to indicate the downlink tunnel information of the tunnel; The downlink tunnel information includes at least one of the following: the address information of the access network device; the port number information of the access network device; and the access network side endpoint identification information of the tunnel.

37. A data plane establishment apparatus, comprising: The receiving module is used to receive a second resource allocation request message sent by a second network element. The second resource allocation request message is used to request the establishment of a tunnel, and the tunnel is used to transmit service data. The sending module is used to send a second resource allocation response message to the second network element, the second resource allocation response message being used to indicate the resource allocation result.

38. The apparatus according to claim 37, wherein, The sending module is further configured to send a third message to the access network device, the third message including at least one of the following: The terminal's first identification information; Carrying identification; Address information of data production nodes; The identifier or address information of the first network element; The identifier or address information of the third network element; Filter template information, which is used to indicate the association between bearer and IP 5-tuple; The upstream tunnel information of the tunnel; The QoS information corresponding to the tunnel.

39. The apparatus according to claim 37 or 38, wherein, The receiving module is further configured to receive a tunnel modification request message sent by the first network element, the tunnel modification request message being used to indicate the downlink tunnel information of the tunnel; The downlink tunnel information includes at least one of the following: the address information of the access network device; the port number information of the access network device; and the access network side endpoint identification information of the tunnel.

40. A data plane establishment apparatus, comprising: The sending module is used to send a service request message to the first network element. The service request message is used to request the establishment of a tunnel, and the tunnel is used to transmit service data.

41. A data plane establishment apparatus, comprising: The receiving module is used to receive the first message sent by the first network element; The processing module is used to establish a bearer based on the first message, the bearer being used to transmit service data.

42. A terminal comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as claimed in claim 25 or 26.

43. A network-side device, comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as claimed in any one of claims 1 to 24, or implementing the steps of the method as claimed in claim 27 or 28.

44. A readable storage medium on which a program or instructions are stored, wherein the program or instructions, when executed by a processor, implement the steps of the method as claimed in any one of claims 1 to 28.

Images