WO2024001566A1 - 网元访问方法、装置、网元及存储介质 - Google Patents

网元访问方法、装置、网元及存储介质 Download PDF

Info

Publication number
WO2024001566A1
WO2024001566A1 PCT/CN2023/093984 CN2023093984W WO2024001566A1 WO 2024001566 A1 WO2024001566 A1 WO 2024001566A1 CN 2023093984 W CN2023093984 W CN 2023093984W WO 2024001566 A1 WO2024001566 A1 WO 2024001566A1
Authority
WO
WIPO (PCT)
Prior art keywords
upf
access
access request
management
request
Prior art date
Application number
PCT/CN2023/093984
Other languages
English (en)
French (fr)
Inventor
周爱东
周晟
黄正刚
徐阳
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2024001566A1 publication Critical patent/WO2024001566A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/30—Routing of multiclass traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation

Definitions

  • the present disclosure relates to the field of communications, and in particular, to a network element access method, device, network element and storage medium.
  • UPF User Plane Function
  • 3GPP 3rd Generation Partnership Project
  • UPF User Plane Function
  • 3GPP 3rd Generation Partnership Project
  • UPF has gradually become the bridgehead for operators to serve vertical industries, and is gradually moving from the "core" to the campus of enterprise users.
  • UPF Since UPF must not only meet the features and functions required by the 3GPP architecture, but also meet the basic requirements of enterprise users for performance, operation and maintenance, networking, etc., the cost and deployment of UPF are relatively heavy, especially in edge campus applications. The demand is even more obvious. Therefore, there is an urgent need for a UPF that is not only low-cost, quick to deploy, and convenient for operation and maintenance, but also has complete functions and carrier-level reliability to meet the unique 5G applications in enterprise campuses.
  • the present disclosure provides a network element access method, device, network element and storage medium to solve the problem of thick UPF in related technologies.
  • the first aspect is to provide a network element access method applied to edge UPF, including:
  • the access response is processed based on the type of the access request.
  • the second aspect provides a network element access method for managing UPF, including:
  • a network element access device including:
  • a first receiving module configured to receive the access response from the management UPF
  • a processing module configured to process the access response based on the type of the access request.
  • a network element access device including:
  • the second receiving module is used to receive access requests from edge UPF;
  • a generation module used to generate an access response corresponding to the access request
  • a sending module configured to send the access response to the edge UPF.
  • a network element access system including:
  • the edge UPF is used to obtain an access request from a campus user; forward the access request to a management UPF that matches the edge UPF, so that the management UPF generates an access response corresponding to the access request; receive the access request from managing the access response of the UPF; processing the access response based on the type of the access request;
  • the management UPF is configured to receive an access request from an edge UPF; generate an access response corresponding to the access request; and send the access response to the edge UPF.
  • a network element including: a processor, a memory and a communication bus, wherein the processor and the memory complete communication with each other through the communication bus;
  • the memory is used to store computer programs
  • the processor is configured to execute the program stored in the memory to implement the network element access method described in the first aspect or the network element access method described in the second aspect.
  • a computer-readable storage medium which stores a computer program.
  • the computer program is executed by a processor, the network element access method described in the first aspect or the network element access method described in the second aspect is implemented.
  • the above technical solution provided by the embodiment of the present disclosure has the following advantages: the method provided by the embodiment of the present disclosure obtains the access request of the campus user; forwards the access request to the management UPF that matches the edge UPF, so that the management The UPF generates an access response corresponding to the access request; receives the access response from the management UPF; and processes the access response based on the type of the access request.
  • This embodiment adopts the collaborative deployment method of edge UPF and management UPF to realize the simplified deployment of campus UPF through edge UPF, and ensures the carrier-level reliability of UPF through management UPF.
  • Figure 1 is a schematic flow chart of a network element access method in an embodiment of the present disclosure
  • Figure 2 is another schematic flowchart of a network element access method in an embodiment of the present disclosure
  • FIG. 3 is a schematic structural diagram of edge UPF and management UPF in an embodiment of the present disclosure
  • Figure 4 is a network architecture diagram of edge UPF and management UPF in an embodiment of the present disclosure
  • Figure 5 is a schematic diagram of the Nx media message interface between edge UPF and management CoUPF in an embodiment of the present disclosure
  • Figure 6 is a signaling diagram of session establishment of edge UPF in an embodiment of the present disclosure.
  • Figure 7 is a signaling diagram of session update of edge UPF in an embodiment of the present disclosure.
  • Figure 8 is a signaling diagram of session deletion of edge UPF in an embodiment of the present disclosure.
  • Figure 9 is a signaling diagram of the ULCL process of edge UPF in an embodiment of the present disclosure.
  • Figure 10 is a signaling diagram for high-performance forwarding of edge UPF without local policy in an embodiment of the present disclosure
  • Figure 11 is a signaling diagram of high-performance forwarding of edge UPF with local policy in an embodiment of the present disclosure
  • Figure 12 is a signaling diagram of traffic reporting for high-performance forwarding of edge UPF in an embodiment of the present disclosure
  • Figure 13 is a signaling diagram for route release of high-performance forwarding by edge UPF in an embodiment of the present disclosure
  • Figure 14 is a signaling diagram of the QoS service of edge UPF in an embodiment of the present disclosure.
  • Figure 15 is a signaling diagram of service packet forwarding by edge UPF in an embodiment of the present disclosure
  • Figure 16(a) is a signaling diagram of an edge UPF alarm in an embodiment of the present disclosure
  • Figure 16(b) is a signaling diagram of edge UPF performance statistics and other services in the embodiment of the present disclosure.
  • Figure 17 is a schematic structural diagram of a network element access device in an embodiment of the present disclosure.
  • Figure 18 is another schematic flow diagram of a network element access device in an embodiment of the present disclosure.
  • Figure 19 is a schematic structural diagram of a network element in an embodiment of the present disclosure.
  • the current UPF needs to be able to achieve the following functions:
  • Anchor point for intra-RAT/inter-RAT mobility session point for external PDU interconnection with the data network; packet routing and forwarding to route traffic flows to instances of the data network, supporting Branching Point UPF to support Multi-homing PDU session; packet inspection; implementation of some user plane policy rules, including: gating, redirection, traffic steering, rate control, etc.); legal interception (UP collection); traffic usage report; user plane QoS processing, such as UL/DL rate enforcement, reflective QoS marking in DL; uplink traffic validation (SDF to QoS traffic mapping); transport-level packet marking in uplink and downlink; downlink packet buffering and downlink data notification triggering; Address allocation, networking and route publishing, and related ACL and other functions.
  • SDF to QoS traffic mapping transport-level packet marking in uplink and downlink
  • downlink packet buffering and downlink data notification triggering Address allocation, networking and route publishing, and related ACL and other functions.
  • the interfaces supported by UPF mainly include:
  • N3 The interface between RAN and I-UPF/UPF, I-UPF (initial UPF, relay UPF), is mainly used to transmit uplink and downlink user plane data between 5G(R)AN and UPF.
  • N4 The interface between SMF and UPF, used to transmit control plane information between SMF and UPF.
  • N6 The interface between DN and UPF. It is used to transmit uplink and downlink user data flows between UPF and DN, and communicates with the DN network based on IP and routing protocols.
  • N9 The interface between UPFs, used to transmit uplink and downlink user data flows between UPFs. For single session, multiple anchors. It is also connected through N9 when roaming.
  • this disclosure sets up a collaborative mode between edge UPF (hereinafter collectively referred to as SmartUPF) and management UPF (hereinafter collectively referred to as CoUPF) to achieve minimalist deployment and convenient operation and maintenance of campus UPF; SmartUPF completes all the features and functions required by the 3GPP specification architecture. It has unified interfaces for the central SMF, management UPF, and other I-UPFs and ULCL main anchor UPFs, and appears as an independent UPF office for the EMS; CoUPF collaborates with SmartUPF for business processing, which can be realized One-to-many management is invisible to network elements in the 3GPP architecture such as SMF and EMS.
  • Figure 1 shows a network element access method provided by an embodiment of the present disclosure. This method can be applied to edge UPF; the method includes the following steps:
  • Step 101 Obtain the access request of the park user.
  • the edge UPF and the management UPF are deployed separately.
  • the edge UPF has already established a connection with the management UPF in advance before receiving the access request from the campus user.
  • connection mode adopted between the edge UPF and the management UPF may be the Nx connection mode supported by the above-mentioned UPF.
  • the edge UPF After the edge UPF establishes an Nx connection with the management UPF, configure the edge UPF's IP address pool, TEIDU and other information on the management UPF and deliver it to the management UPF through the Nx connection; the management UPF delivers the new UPF service configuration to the edge UPF through the Nx connection. .
  • the signaling messages between the management UPF and the edge UPF are communicated using the PFCP protocol; the media messages between the management UPF and the edge UPF are communicated in a tunnel manner.
  • Tunnel types include but are not limited to custom UDP tunnels, GTP tunnels, GRE tunnels, etc. It should be understood that media messages between the management UPF and the edge UPF can also be communicated in a customized manner, which is not limited in this embodiment.
  • access requests from campus users include control packets and service packets.
  • the access request may include one or more of the following: session establishment request; session update request; session deletion request; uplink classification request; traffic information reporting request.
  • session establishment request, session update request and session deletion request belong to the control class message, while the uplink classification request and the traffic information reporting request belong to the service class message.
  • Step 102 Forward the access request to the management UPF that matches the edge UPF, so that the management UPF generates an access response corresponding to the access request.
  • the edge UPF implements mobility management, session management, and data transmission.
  • the management UPF receives the session and message information of the edge UPF, and processes the message information.
  • Step 103 Receive an access response from the management UPF.
  • Step 104 Process the access response based on the type of access request.
  • the edge UPF when the access request type is a control packet, the edge UPF returns the access response to the campus user; when the access request type is a business packet, the access response is a packet forwarding policy, and the edge UPF Forward the access request based on the message forwarding policy.
  • the packet forwarding policy indicates the forwarding path of the access request.
  • the edge UPF when the access response is a packet forwarding policy, after receiving the packet forwarding policy, the edge UPF will store the packet forwarding policy locally so that when there are other services that are the same as the access request request, When an access request occurs, other access requests can be processed directly according to the message forwarding policy.
  • the edge UPF can also obtain the service type of the access request and determine whether the service type is stored.
  • the access request is ignored and the access request is forwarded to the management UPF only when it is determined that the packet forwarding policy corresponding to the service type is not stored.
  • the edge UPF can locally establish the corresponding relationship between the service type and the message forwarding policy. Therefore, when the service type of the access request is obtained, the service type can be used to query the corresponding relationship to determine whether the corresponding message is stored locally. forwarding strategy.
  • the service type of the access request can be indicated by the message characteristics of the access request. Therefore, when it is determined that the edge UPF does not store the message forwarding policy corresponding to the service type, the message characteristics of the access request are obtained, and when it is determined When neither the edge UPF message processing unit (PFU) nor the deep message parsing unit (DPI-D) stores the forwarding policy corresponding to the message characteristics, it is determined that the edge UPF does not store the message forwarding policy corresponding to the business class message. .
  • PFU edge UPF message processing unit
  • DPI-D deep message parsing unit
  • the client proxy unit (Proxy-C) is configured in the edge UPF
  • the server proxy unit (Proxy-S) is configured in the management UPF.
  • the edge UPF is implemented through the connection between Proxy-C and Proxy-S. Interaction with management UPF.
  • the edge UPF receives the packet forwarding policy from the management UPF, it receives the packet forwarding policy from the server proxy unit of the management UPF through the client proxy unit.
  • the campus user before obtaining the access request from the campus user, the campus user will establish a session connection with the edge UPF and the management UPF.
  • the management UPF will allocate address parameters to the campus user so that the campus user can use the address parameters for business access.
  • edge UPF will advertise routes based on this address parameter.
  • a route publishing request is sent to the management UPF; the address parameters of the campus user returned by the management UPF in response to the route publishing request are received; based on the address parameters, routing information of the campus user and the edge UPF is generated. The information indicates that the campus user matches the edge UPF; routing information is published to the switch.
  • the address parameters of campus users include but are not limited to IP addresses.
  • the access request of the campus user is obtained; the access request is forwarded to the management UPF that matches the edge UPF, so that the management UPF generates an access response corresponding to the access request; and the access response from the management UPF is received; The access response is processed based on the type of access request.
  • This embodiment adopts the collaborative deployment method of edge UPF and management UPF to realize the simplified deployment of campus UPF through edge UPF, and ensures the carrier-level reliability of UPF through management UPF.
  • Edge UPF and management UPF are deployed together to achieve simplified deployment and convenient operation and maintenance of campus UPF; edge UPF completes all the features and functions required by the 3GPP specification architecture, and supports central SMF, management UPF, and other I-UPF and ULCL masters.
  • Anchor UPF has unified interfaces and appears as an independent UPF office to EMS; CoUPF cooperates with SmartUPF for business processing, which can realize one-to-many management and is invisible to network elements in the 3GPP architecture such as SMF and EMS.
  • Edge UPF implements mobility management, session management and data transmission, connects SMF, UPF, UE, etc. to N3, N4, N6, and N9 interfaces to realize business offloading of campus UPF, including ULCL upstream offloading, IPv6 multi-homing offloading, and LADN 3GPP standardizes business processes such as local data networks.
  • the edge UPF architecture has an IPU unit (Interface Process Unit) to complete the signaling processing of the N4 interface, including session establishment, deletion, modification and other services issued by SMF, and ULCL process; the PFU unit (Packet Forward Unit) completes the switch CE interconnection realizes user message service processing of N3, N6 and N9; OAM unit ((Operation, Administration, Maintenance) to complete the operation, management and maintenance of SmartUPF network elements.
  • IPU unit Interface Process Unit
  • PFU unit Packet Forward Unit
  • OAM unit (Operation, Administration, Maintenance) to complete the operation, management and maintenance of SmartUPF network elements.
  • Proxy-C in the edge UPF architecture realizes the connection with Proxy-S in CoUPF, transparently transmits N4 signaling session information and control management information in N3/N6/N9 messages, and implements business processes through CoUPF.
  • edge UPF The three types of units of PFU, DPI-D (Deep Packet Inspection Cache) and Flow-D (Session Flow Cache) of edge UPF can be implemented through hardware, including FPGA, DPU and other intelligent network cards.
  • PFU Packet Inspection Cache
  • Flow-D Session Flow Cache
  • the management UPF receives edge UPF session and message information through Proxy-S, through PFU, GSU (General Service Unit), LDU (Local Data Unit), LIG (Lawful Interception Gateway), OMU (Operation Maintain Unit), RMU (Resource Management Unit) is completed, and the relationship between Proxy-S and Proxy-C is completed through the NFF (Network Forwarding Framework) protocol.
  • GSU General Service Unit
  • LDU Local Data Unit
  • LIG Layer
  • OMU Operaation Maintain Unit
  • RMU Resource Management Unit
  • Edge SmartUPF achieves minimalist deployment with the collaboration of CoUPF and hardware acceleration.
  • 2 Cores of computing resources are needed (corresponding to Intel 6230 CPU 20Core), plus an FPGA (Xilinx 7P model). Deployment can be completed.
  • the computing resources are increased to 4Core, and the smart network card does not need to be expanded.
  • the capacity exceeds 100G, the smart network card is added as needed.
  • SmartUPF requires 16 Core computing resources (corresponding to Intel 6230 CPU), and 12 Core resources are added for each additional 20G.
  • Edge UPF and the session management unit, business processing unit, data storage unit, etc. that manage UPF are implemented in a distributed manner to facilitate flexible management of capacity expansion and contraction.
  • Edge UPF is implemented in accordance with 3GPP specifications, fully realizing protocol functions and business capabilities, and connecting SMF, UPF, UE, etc. in a sub-anchor UPF manner; there is no special or non-standard perception of peripheral network elements such as SMF/UPF/EMS.
  • Edge UPF implements localized processing of services, which is safe and reliable; SmartUPF and CoUPF collaborate to achieve carrier-level reliability.
  • edge UPF greatly reduces the deployment cost and deployment requirements of campus UPF, achieving low energy consumption, rapid deployment, and plug-and-play; for example, for the 20G campus UPF deployment scenario, the cost and function of SmartUPF The consumption is only equivalent to 50% of ordinary UPF.
  • Edge UPF realizes service localization, and user traffic information is processed locally to achieve high performance and low latency; in hardware acceleration mode, the packet latency of network elements is less than 100us, and the maximum single user rate can meet 100G.
  • Figure 2 shows a network element access method provided by an embodiment of the present disclosure. This method can be applied to manage UPF; the method includes the following steps:
  • Step 201 Receive the access request from the edge UPF
  • Step 202 Generate an access response corresponding to the access request
  • Step 203 Send an access response to the edge UPF.
  • the edge UPF reports the access request to the management UPF in order to obtain the message forwarding policy of the service corresponding to the access request.
  • the access response When generating the access response, in an optional embodiment, obtain the message characteristics of the access request; determine the message characteristics Matching packet forwarding policy; use the packet forwarding policy as the access response.
  • the management UPF can also send the address parameters allocated to campus users during the session to the edge UPF, so that the edge UPF can generate routing information and publish routes in parallel.
  • the management UPF receives the route publishing request from the edge UPF; in response to the route publishing request, it returns the address parameters of the campus user to the edge UPF.
  • edge UPF and management UPF Based on the above detailed description of edge UPF and management UPF, the interaction between edge UPF and management UPF is described using specific scenario embodiments.
  • Embodiment 1 Implement deployment and communication of SmartUPF and CoUPF.
  • Figure 3 is an internal architecture diagram of SmartUPF and CoUPF provided in this embodiment.
  • Step 1 CoUPF and SmartUPF are deployed separately, as shown in Figure 4;
  • Step 2 CoUPF establishes Nx connection with SmartUPF, as shown in Figure 5;
  • Step 3 Configure SmartUPF’s IP address pool, TEIDU and other information on CoUPF and deliver it to SmartUPF through the Nx connection;
  • Step 4 CoUPF delivers the new UPF service configuration to SmartUPF through the Nx connection
  • Step 5 The signaling messages between CoUPF and SmartUPF are exchanged using the PFCP protocol, as shown in Figure 4;
  • Step 6 Media packets between CoUPF and SmartUPF are communicated through tunnels.
  • Tunnel types include but are not limited to custom UDP tunnels, GTP tunnels, GRE tunnels, etc.
  • the following takes a custom UDP tunnel as an example, and the protocol stack layering is shown in Figure 5.
  • the internal header (InnerHead) in Figure 4 adopts a 16-byte structure, as shown in Figure 2. It should be understood that Table 1 is only used as an example diagram, and specific adjustments can be made.
  • InnerType is used to represent the message type.
  • the message type can be seen in Table 2. It should be understood that Table 3 is only used as an example and the details can be adjusted.
  • Embodiment 2 SmartUPF session establishment, as shown in Figure 6.
  • Step 1 SMF triggers the establishment of N4 session process
  • Step 2 Smart-UPF receives the N4 Session Establishment Request (session establishment request) sent by SMF;
  • Step 3 Smart-UPF sends N4 Session Establishment Request message to CoUPF;
  • Step 4 CoUPF completes operations such as allocating IP addresses and allocating service tunnel resources
  • Step 5 CoUPF sends N4 Session Establishment Response (session establishment response) to SmartUPF;
  • Step 6 SmartUPF creates an N4 session, establishes a service tunnel, and sends an N4 Session Establishment Response message to SMF.
  • Embodiment 3 Session update of edge SmartUPF, as shown in Figure 7.
  • Step 1 SMF triggers the update N4 session process
  • Step 2 SmartUPF receives the N4 Session Modification Request (session change request) sent by SMF;
  • Step 3 SmartUPF sends N4 Session Modification Request message to CoUPF;
  • Step 4 CoUPF completes operations such as updating service tunnel resources
  • Step 5 CoUPF sends N4 Session Modification Response (session change response) to SmartUPF;
  • Step 6 SmartUPF updates the N4 session, creates/updates the service tunnel, and sends the N4 Session Modification Response message to SMF.
  • Embodiment 4 SmartUPF session deletion, as shown in Figure 8.
  • Step 1 SMF triggers the release of N4 session process
  • Step 2 SmartUPF receives the N4 Session Release Request (session release request) sent by SMF;
  • Step 3 SmartUPF sends the N4 Session Release Request message to the management UPF;
  • Step 4 CoUPF releases service tunnel resources and other operations
  • Step 5 CoUPF sends N4 Session Release Response (session release response) to SmartUPF;
  • Step 6 SmartUPF releases the N4 session and sends the N4 Session Release Response message to SMF.
  • Embodiment 5 SmartUPF’s ULCL process, as shown in Figure 9.
  • Step 1 PDU session is established, the anchor point is UPF1;
  • Step 2 SMF performs UPF reselection based on the service routing information.
  • the selection result is: SmartUPF is the Uplink Classifier, UPF2 is the anchor point of the business App2 data, and UPF1 is the anchor point of the business App1 data; SmartUPF receives the N4 Session Establishment sent by SMF. Request message;
  • Step 3. SmartUPF sends N4 Session Establishment Request to the management UPF;
  • Step 4 CoUPF completes operations such as allocating IP addresses and allocating service tunnel resources
  • Step 5 CoUPF sends N4 Session Establishment Response to Smart-UPF;
  • Step 6 SmartUPF establishes an N4 session, creates a service tunnel, and sends an N4 Session Establishment Response message to SMF;
  • Step 7 SMF sends the N4 Session Modification Request message to UPF1 to update the N4 session;
  • Step 8 UPF1 completes the session update and sends the N4 Session Modification Response message to SMF.
  • Embodiment 6 SmartUPF high-performance forwarding process without local policy, as shown in Figure 10.
  • Step 1 According to the route advertisement result, the packet is directed to SmartUPF;
  • Step 2 SmartUPF does not have a fast transfer table and no local policy. It identifies the CoUPF to which the packet belongs based on the packet characteristics, and sends the packet to it by carrying the identifier of the pfu of SmartUPF;
  • Step 3 CoUPF receives the message and performs operations such as session, policy, and in-depth message identification, and sends the required Qos policy to SmartUPF. At the same time, it completes the processing of this message and sends it to SmartUPF for outgoing transmission;
  • Step 4 SmartUPF receives the Qos policy information sent by CoUPF and saves it locally, and generates a fast forwarding policy based on the packet characteristics. Complete the message outgoing according to the fast forwarding table.
  • Embodiment 7 SmartUPF high-performance forwarding has a local policy process, as shown in Figure 11.
  • Step 1 Based on the route advertisement results, the packets are directed to SmartUPF.
  • Step 2 SmartUPF has a fast forwarding table, and the packet hits the fast forwarding table and is forwarded directly.
  • Embodiment 8 Traffic reporting process of SmartUPF high-performance forwarding, as shown in Figure 12.
  • Step 1 If there is a local session, collect traffic information according to the session;
  • Step 2 Report the collected traffic information to CoUPF
  • Step 3 CoUPF reports to SMF.
  • Embodiment 9 SmartUPF high-performance forwarding route release process, as shown in Figure 13.
  • Step 1 After SmartUPF is powered on, it reports the interface to CoUPF. CoUPF finally reports the information to the protocol stack center (Rosng), and the protocol stack center forms an external logical interface;
  • Step 2 Read the configured address pool and business address on CoUPF and generate a routing queue to be published;
  • Step 3 CoUPF packages the routing information and sends it to SmartUPF;
  • Step 4 SmartUPF sends the route through the outgoing port.
  • Embodiment 10 QoS business process of SmartUPF, as shown in Figure 14.
  • Step 1 The first request message of the user service arrives at the PFU module of SmartUPF.
  • the service QoS policy is matched based on the five-tuple characteristics of the message. It is found that no QoS policy is matched;
  • Step 2 The packet is forwarded to the DPI-D module for QoS policy request; the DPI-D module still fails to match the local policy based on the characteristics of the service packet, indicating that there is no local cache of the service characteristic data and QoS policy;
  • Step 3 SmartUPF sends the service request message to CoUPF through the Proxy-C module.
  • CoUPF conducts in-depth packet analysis based on user information, packet quintuple characteristics, service packet characteristics and other data, and comprehensively decides on the QoS policy for the packet;
  • Step 4 CoUPF delivers the service packet QoS policy to SmartUPF through the Proxy-S module
  • Step 5 After receiving the QoS policy, the DPI-D module creates an index cache policy based on the message service characteristics and delivers the policy to the PFU;
  • Step 6 The PFU caches the policy based on the five-tuple information of the message, executes the policy and forwards the message at the same time;
  • Step 7 After the packets of the same service flow arrive at the PFU, the PFU can directly match the QoS policy based on the five-tuple characteristics, execute the policy, and forward the packets;
  • Step 8 When the same service initiates a new service flow and reaches the PFU, the PFU cannot hit the policy based on the five-tuple information;
  • Step 9 The service request message is forwarded to the DPI-D module, and the DPI-D module hits the cached policy information based on the service feature information;
  • Step 10 DPI-D directly delivers the policy information to the PFU.
  • the PFU caches the policy based on the message quintuple information, executes the policy, and forwards the message.
  • Embodiment 11 SmartUPF service packet forwarding process, as shown in Figure 15.
  • the forwarding process of business packets can be mainly divided into the following categories:
  • Step 1 After obtaining the cache policy from DPI-D, direct forwarding can be performed on PFU through message quintuple identification.
  • Step 2 The message processing policy includes value-added services.
  • the service request message needs to be sent to DPI-D for message modification, such as header enhancement, redirection and other services; after the modification is completed, it is sent out through the external interface of the PFU. , non-service request messages can be forwarded directly on the PFU;
  • Step 3 The packets need to be deeply analyzed.
  • the DPI-D cache policy cannot accurately identify the packets, such as fraudulent packets. At this time, all the packets are sent to CoUPF for in-depth identification.
  • the forwarding policy is not issued until the service policy that can be identified by DPI-D can be parsed.
  • Embodiment 12 SmartUPF alarm, performance statistics and other business processes, as shown in Figure 16(a).
  • SmartUPF and CoUPF externally embody a UPF as a whole, and unified alarms can be presented by SmartUPF to the upper-level network management.
  • Step 1 The module on SmartUPF generates an alarm (taking the PFU/DPU module as an example) and reports it to SmartUPF-OAM. SmartUPF-OAM directly reports it to the superior network management and displays the UPF business module alarm externally;
  • Step 2 The module on CoUPF generates an alarm (taking the PFU module as an example) and reports it to CoUPF-OAM, carrying the instance information; CoUPF-OAM queries the corresponding SmartUPF based on the instance information and forwards the alarm to SmartUPF-OAM; SmartUPF-OAM receives The CoUPF alarm information is reported to the superior network management, and the UPF management module report is presented to the outside world. police.
  • Step 1 Create a performance statistics task on the upper-level network management system of SmartUPF, and the upper-level network management system delivers the task to SmartUPF-OAM;
  • Step 2 After receiving the performance statistics task, SmartUPF-OAM forwards the task to CoUPF-OAM at the same time;
  • Step 3 CoUPF-OAM delivers the performance statistics task to CoUPF-PFU;
  • Step 4 The PFU/DPU module on SmartUPF pushes business traffic to the PFU module of CoUPF regularly or quantitatively;
  • Step 5 After receiving the reported traffic, CoUPF-PFU generates original performance statistics based on the user's complete information and reports them to CoUPF-OAM, and CoUPF-OAM generates a performance statistics file;
  • Step 6 CoUPF-OAM transmits the performance statistics generated file to SmartUPF-OAM
  • Step 7 SmartUPF-OAM saves the file for query by the superior network management.
  • the embodiment of the present disclosure provides a network element access device.
  • the device mainly includes:
  • the acquisition module 1701 is used to obtain access requests from park users;
  • the forwarding module 1702 is configured to forward the access request to the management UPF that matches the edge UPF, so that the management UPF generates an access response corresponding to the access request;
  • the first receiving module 1703 is used to receive an access response from the management UPF;
  • the processing module 1704 is used to process the access response based on the type of the access request.
  • This device is also used for:
  • Processing module 1704 is used to:
  • This device is used for:
  • the forwarding module 1702 is used for:
  • This device is used for:
  • the corresponding relationship is stored through the PFU module.
  • This device is also used for:
  • the routing information between the campus user and the edge UPF is generated, and the routing information indicates that the campus user matches the edge UPF;
  • Access requests include one or more of the following:
  • the embodiment of the present disclosure provides a network element access device.
  • the device mainly includes:
  • the second receiving module 1801 is used to receive access requests from edge UPF;
  • Generating module 1802 used to generate an access response corresponding to the access request
  • the sending module 1803 is used to send an access response to the edge UPF.
  • the type of access request indicates that the access request is a business class message
  • This device is also used for:
  • the address parameters of the campus user are returned to the edge UPF.
  • the embodiment of the present disclosure also provides a network element.
  • the network element mainly includes: a processor 1901, a memory 1902 and a communication bus 1903.
  • the processor 1901 and the memory 1902 communicate through Bus 1903 completes mutual communication.
  • the memory 1902 stores programs that can be executed by the processor 1901.
  • the processor 1901 executes the programs stored in the memory 1902 to implement the following steps:
  • the communication bus 1903 mentioned in the above network element can be a peripheral component interconnect standard (Peripheral Component Interconnect, PCI for short) bus or an extended industry standard architecture (Extended Industry Standard Architecture, Referred to as EISA) bus, etc.
  • PCI peripheral component interconnect standard
  • EISA Extended Industry Standard Architecture
  • the communication bus 1903 can be divided into an address bus, a data bus, a control bus, etc. For ease of presentation, only one thick line is used in Figure 19, but it does not mean that there is only one bus or one type of bus.
  • the memory 1902 may include random access memory (Random Access Memory, RAM for short), or may include non-volatile memory (non-volatile memory), such as at least one disk memory.
  • RAM Random Access Memory
  • non-volatile memory such as at least one disk memory.
  • the memory may also be at least one storage device located remotely from the aforementioned processor 1901.
  • the above-mentioned processor 1901 can be a general-purpose processor, including a central processing unit (Central Processing Unit, referred to as CPU), a network processor (Network Processor, referred to as NP), etc., or it can also be a digital signal processor (Digital Signal Processing, referred to as DSP). ), Application Specific Integrated Circuit (ASIC for short), Field-Programmable Gate Array (FPGA for short) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components.
  • CPU Central Processing Unit
  • NP Network Processor
  • DSP Digital Signal Processing
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • a computer-readable storage medium stores a computer program.
  • the computer program When the computer program is run on a computer, it causes the computer to execute the above embodiments.
  • the described network element access method is also provided.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network or other programmable device.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another, e.g., from a website, computer, server, or data center via a wireline (e.g., Coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, microwave, etc.) means to transmit to another website, computer, server or data center.
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the available media may be magnetic media (such as floppy disks, hard disks, magnetic tapes, etc.), optical media (such as DVDs), or semiconductor media (such as solid state drives).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本公开涉及一种网元访问方法、装置、网元及存储介质。该方法包括获取园区用户的访问请求；向与边缘UPF匹配的管理UPF转发访问请求，以使得管理UPF生成与访问请求对应的访问响应；接收来自于管理UPF的访问响应；基于访问请求的类型对访问响应进行处理。本实施例通过采用边缘UPF与管理UPF协同部署的方式，经由边缘UPF实现了园区UPF的极简部署，通过管理UPF保证了UPF电信级的可靠性。

Description

网元访问方法、装置、网元及存储介质
相关申请的交叉引用
本公开要求享有2022年6月29日提交的名称为“网元访问方法、装置、网元及存储介质”的中国专利申请CN202210758875.2的优先权，其全部内容通过引用并入本公开中。
技术领域
本公开涉及通信领域，尤其涉及一种网元访问方法、装置、网元及存储介质。
背景技术
UPF(User Plane Function，用户面功能)是3GPP(3rd Generation Partnership Project，第三代合作伙伴计划)核心网***架构的重要组成部分，主要负责5G核心网用户面数据包的路由和转发，数据和业务识别，以及动作和策略执行。UPF作为5G数据处理和转发的核心功能，已经逐步成为运营商服务垂直行业的桥头堡，正逐步从“核心”走到企业用户的园区。
由于UPF既要满足3GPP架构要求的特性功能，同时也要满足企业用户对性能、运维、组网等的基本要求，UPF的成本、部署等就较为厚重，尤其在边缘园区应用中，这一需求体现的就更为明显。因此迫切需要一种既能成本低廉、快速部署、运维便利的UPF，又要功能齐备、电信级可靠性，满足企业园区的5G特色应用。
发明内容
本公开提供了一种网元访问方法、装置、网元及存储介质，用以解决相关技术中的UPF比较厚重的问题。
第一方面，提供一种网元访问方法，应用于边缘UPF，包括：
获取园区用户的访问请求；
向与所述边缘UPF匹配的管理UPF转发所述访问请求，以使得所述管理UPF生成与所述访问请求对应的访问响应；
接收来自于所述管理UPF的所述访问响应；
基于所述访问请求的类型对所述访问响应进行处理。
第二方面，提供一种网元访问方法，应用于管理UPF，包括：
接收来自于边缘UPF的访问请求；
生成与所述访问请求对应的访问响应；
向所述边缘UPF发送所述访问响应。
第三方面，提供一种网元访问装置，包括：
获取模块，用于获取园区用户的访问请求；
转发模块，用于向与所述边缘UPF匹配的管理UPF转发所述访问请求，以使得所述管 理UPF生成与所述访问请求对应的访问响应；
第一接收模块，用于接收来自于所述管理UPF的所述访问响应；
处理模块，用于基于所述访问请求的类型对所述访问响应进行处理。
第四方面，提供一种网元访问装置，包括：
第二接收模块，用于接收来自于边缘UPF的访问请求；
生成模块，用于生成与所述访问请求对应的访问响应；
发送模块，用于向所述边缘UPF发送所述访问响应。
第五方面，提供一种网元访问***，包括：
管理UPF和边缘UPF；
所述边缘UPF用于，获取园区用户的访问请求；向与所述边缘UPF匹配的管理UPF转发所述访问请求，以使得所述管理UPF生成与所述访问请求对应的访问响应；接收来自于所述管理UPF的所述访问响应；基于所述访问请求的类型对所述访问响应进行处理；
所述管理UPF用于，接收来自于边缘UPF的访问请求；生成与所述访问请求对应的访问响应；向所述边缘UPF发送所述访问响应。
第六方面，提供一种网元，包括：处理器、存储器和通信总线，其中，处理器和存储器通过通信总线完成相互间的通信；
所述存储器，用于存储计算机程序；
所述处理器，用于执行所述存储器中所存储的程序，实现第一方面所述的网元访问方法或第二方面所述的网元访问方法。
第七方面，提供一种计算机可读存储介质，存储有计算机程序，所述计算机程序被处理器执行时实现第一方面所述的网元访问方法或第二方面所述的网元访问方法。
本公开实施例提供的上述技术方案与现有技术相比具有如下优点：本公开实施例提供的该方法，获取园区用户的访问请求；向与边缘UPF匹配的管理UPF转发访问请求，以使得管理UPF生成与访问请求对应的访问响应；接收来自于管理UPF的访问响应；基于访问请求的类型对访问响应进行处理。本实施例通过采用边缘UPF与管理UPF协同部署的方式，经由边缘UPF实现了园区UPF的极简部署，通过管理UPF保证了UPF电信级的可靠性。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本发明的实施例，并与说明书一起用于解释本发明的原理。
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，对于本领域普通技术人员而言，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本公开实施例中网元访问方法的一种流程示意图；
图2为本公开实施例中网元访问方法的又一种流程示意图；
图3为本公开实施例中边缘UPF和管理UPF的结构示意图；
图4为本公开实施例中边缘UPF和管理UPF的网络架构图；
图5为本公开实施例中边缘UPF与管理CoUPF的Nx媒体报文接口的示意图；
图6为本公开实施例中边缘UPF的会话建立的信令图；
图7为本公开实施例中边缘UPF的会话更新的信令图；
图8为本公开实施例中边缘UPF的会话删除的信令图；
图9为本公开实施例中边缘UPF的ULCL流程的信令图；
图10为本公开实施例中边缘UPF的高性能转发之无本地策略的信令图；
图11为本公开实施例中边缘UPF的高性能转发之有本地策略的信令图；
图12为本公开实施例中边缘UPF的高性能转发之流量上报的信令图；
图13为本公开实施例中边缘UPF的高性能转发之路由发布的信令图；
图14为本公开实施例中边缘UPF的QoS业务的信令图；
图15为本公开实施例中边缘UPF的业务报文转发的信令图；
图16(a)为本公开实施例中边缘UPF的告警的信令图；
图16(b)为本公开实施例中边缘UPF的性能统计等业务的信令图；
图17为本公开实施例中网元访问装置的一种结构示意图；
图18为本公开实施例中网元访问装置的又一种流程示意图；
图19为本公开实施例中网元的结构示意图。
具体实施方式
为使本公开实施例的目的、技术方案和优点更加清楚，下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本公开的一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有做出创造性劳动的前提下所获得的所有其他实施例，都属于本公开保护的范围。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本公开的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、***、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
为了方便阅读，以下先通过表一对本公开方案涉及到的技术术语进行简单介绍。
表一

为了方便理解，以下对UPF所支持的功能和接口进行简要描述。
当前UPF需要能够实现以下功能：
用于RAT内/RAT间移动性的锚点；外部PDU与数据网络互连的会话点；分组路由和转发，以将业务流路由到数据网络的实例，支持分支点(Branching Point UPF)以支持多宿主PDU会话；数据包检查；用户平面部分策略规则实施，包括：门控，重定向，流量转向，速率控制等)；合法拦截(UP收集)；流量使用报告；用户平面的QoS处理，如UL/DL速率实施，DL中的反射QoS标记；上行链路流量验证(SDF到QoS流量映射)；上行链路和下行链路中的传输级分组标记；下行数据包缓冲和下行数据通知触发；地址分配、组网和路由发布、及与此相关的ACL等功能。
为了实现上述功能，UPF所支持的接口主要有：
N3：RAN和I-UPF/UPF之间的接口，I-UPF(initial UPF，中继UPF)，主要用于传递5G(R)AN与UPF间的上下行用户面数据。N4：SMF和UPF之间的接口，用于传输SMF和UPF间的控制面信息。N6：DN和UPF之间的接口，用于传递UPF与DN之间的上下行用户数据流，基于IP和路由协议与DN网络通信。N9：UPF之间的接口，用于传递UPF之间的上下行用户数据流。用于单会话，多锚点。漫游的时候也通过N9连接。
为了解决相关技术中存在的问题，本公开设置边缘UPF(以下统一称为SmartUPF)和管理UPF(以下统一称为CoUPF)协同方式，实现园区UPF的极简部署和便捷运维； SmartUPF完成3GPP规范架构要求的所有特性功能，对中心SMF、管理UPF，及其它I-UPF、ULCL主锚点UPF，接口统一，对EMS呈现为独立UPF局；CoUPF协同SmartUPF做业务处理，可实现一对多管理，对SMF、EMS等3GPP架构内网元不可见。
以下分别从边缘UPF和管理UPF的角度对本公开的方案展开说明。
请参见图1，图1为本公开实施例提供的一种网元访问方法，该方法可应用于边缘UPF；该方法包括以下步骤：
步骤101、获取园区用户的访问请求。
本实施例中，边缘UPF与管理UPF分开部署，边缘UPF在接收园区用户的访问请求之前，已经预先与管理UPF建立了连接。
应理解，边缘UPF与管理UPF之间采用的连接方式可以为上述UPF所支持的Nx连接方式。边缘UPF与管理UPF建立Nx连接后，管理UPF上配置边缘UPF的IP地址池，TEIDU等信息，通过Nx连接下发给管理UPF；管理UPF把新增UPF业务配置通过Nx连接下发给边缘UPF。
本实施例中，管理UPF和边缘UPF之间的信令报文采用PFCP协议进行交互；管理UPF和边缘UPF之间的媒体报文采用隧道方式通信。隧道类型包括但不限于自定义udp隧道、GTP隧道、GRE隧道等。应理解，管理UPF和边缘UPF之间的媒体报文还可以采用自定义方式通信，本实施例不对此进行限定。
本实施例中，园区用户的访问请求包括控制类报文和业务类报文两类。具体应用中，该访问请求可以包括以下一种或多种：会话建立请求；会话更新请求；会话删除请求；上行分类请求；流量信息上报请求。
应理解，在这里，会话建立请求、会话更新请求和会话删除请求属于控制类报文，而上行分类请求和流量信息上报请求则属于业务类报文。
步骤102、向与边缘UPF匹配的管理UPF转发访问请求，以使得管理UPF生成与访问请求对应的访问响应。
本实施例中，边缘UPF实现移动管理、会话管理和数据传输，管理UPF接收边缘UPF的会话及报文信息，并对报文信息进行处理。
步骤103、接收来自于管理UPF的访问响应。
步骤104、基于访问请求的类型对访问响应进行处理。
本实施例中，当访问请求的类型为控制类报文时，边缘UPF向园区用户返回该访问响应；当访问请求的类型为业务类报文时，该访问响应为报文转发策略，边缘UPF基于该报文转发策略转发访问请求。报文转发策略指示访问请求的转发路径。
应用中，当访问响应为报文转发策略时，边缘UPF收到报文转发策略后，会在本地存储该报文转发策略，以便当后续再有与该访问请求请求的业务为同一业务的其它访问请求出现时，可以按照该报文转发策略直接对该其它访问请求进行处理。相应地，针对于业务类报文的访问请求，边缘UPF在获取到园区用户的访问请求后，向管理UPF转发访问请求之前，还可以获取访问请求的业务类型，判断是否存储有与该业务类型对应的报文转发策 略，并在确定未存储该业务类型对应的报文转发策略时，才向管理UPF转发该访问请求。
应理解，边缘UPF可以在本地建立业务类型与报文转发策略的对应关系，因此当获取到访问请求的业务类型时，可以采用该业务类型查询对应关系，以确定本地是否存储有对应的报文转发策略。
本实施例中，访问请求的业务类型可以用访问请求的报文特征进行指示，因此在确定边缘UPF未存储有业务类型对应的报文转发策略时，获取访问请求的报文特征，并当确定边缘UPF报文处理单元(PFU)和深度报文解析单元(DPI-D)均未存储有该报文特征对应的转发策略时，确定边缘UPF未存储有业务类报文对应的报文转发策略。
本实施例中，在边缘UPF中配置客户端代理单元(Proxy-C)，同时在管理UPF中配置服务端代理单元(Proxy-S)，通过Proxy-C与Proxy-S的连接，实现边缘UPF和管理UPF的交互。相应地，边缘UPF接收来自于管理UPF的报文转发策略时，通过客户端代理单元接收来自于管理UPF的服务端代理单元的报文转发策略。
本实施例中，在获取园区用户的访问请求之前，园区用户会与边缘UPF和管理UPF建立会话连接，在会话连接建立的过程中，管理UPF会为园区用户分配地址参数，以便园区用户采用地址参数进行业务访问。为了实现园区用户能够基于该地址参数进行业务访问，边缘UPF会基于该地址参数进行路由发布。
具体实现时，一个可选实施例中，向管理UPF发送路由发布请求；接收管理UPF响应于路由发布请求返回的园区用户的地址参数；基于地址参数，生成园区用户与边缘UPF的路由信息，路由信息指示园区用户与边缘UPF相匹配；向交换机发布路由信息。
应用中，园区用户的地址参数包括但不限于IP地址。
本实施例提供的技术方案中，获取园区用户的访问请求；向与边缘UPF匹配的管理UPF转发访问请求，以使得管理UPF生成与访问请求对应的访问响应；接收来自于管理UPF的访问响应；基于访问请求的类型对访问响应进行处理。本实施例通过采用边缘UPF与管理UPF协同部署的方式，经由边缘UPF实现了园区UPF的极简部署，通过管理UPF保证了UPF电信级的可靠性。
基于以上描述，简要对本公开中的边缘UPF进行描述。
(1)边缘UPF和管理UPF协同部署，实现园区UPF的极简部署和便捷运维；边缘UPF完成3GPP规范架构要求的所有特性功能，对中心SMF、管理UPF，及其它I-UPF、ULCL主锚点UPF，接口统一，对EMS呈现为独立UPF局；CoUPF协同SmartUPF做业务处理，可实现一对多管理，对SMF、EMS等3GPP架构内网元不可见。
(2)边缘UPF实现移动管理、会话管理和数据传输，对SMF、UPF、UE等对接N3、N4、N6、N9接口，实现园区UPF的业务分流，包括ULCL上行分流、IPv6多归属分流、LADN本地数据网络等3GPP规范业务流程。
(3)边缘UPF架构具备IPU单元(Interface Process Unit)，完成N4接口的信令处理，包括SMF下发的会话建立、删除、修改等业务，和ULCL流程；PFU单元(Packet Forward Unit)完成交换机CE对接，实现N3、N6、N9的用户报文业务处理；OAM单元((Operation、 Administration、Maintenance)完成SmartUPF网元的操作、管理和维护。
(4)边缘UPF架构中Proxy-C，实现与CoUPF中Proxy-S(的连接，透明传输N4信令会话信息，及N3/N6/N9报文中的控制管理信息，通过CoUPF实现业务流程。
(5)边缘UPF的PFU、DPI-D(Deep Packet Inspection Cache)、Flow-D(Session Flow Cache)三类单元，可以通过硬件实现，包括FPGA、DPU等智能网卡方式实现。
(6)管理UPF通过Proxy-S接收边缘UPF的会话及报文信息，通过PFU、GSU(General Service Unit)、LDU(Local Data Unit)、LIG(Lawful Interception Gateway)、OMU(Operation Maintain Unit)、RMU(Resource Management Unit)完成，Proxy-S与Proxy-C之间通过NFF(Network Forwarding Framework网络转发框架)协议完成。
(7)边缘SmartUPF在CoUPF及硬件加速的协同下，实现极简部署，在园区20G以下场景下，仅需计算资源2 Core(对应Intel 6230 CPU 20Core)，加一张FPGA(Xilinx 7P型号)即可完成部署。当园区要求在100G场景时，计算资源增加到4Core，智能网卡不需扩展，当容量超过100G时，智能网卡按需增加。在没有智能网卡硬件协同的场景下，20G性能容量，SmartUPF需计算资源16 Core(对应Intel 6230 CPU)，每增加20G则增加12Core资源。
(8)边缘UPF和管理UPF的会话管理单元、业务处理单元、数据存储单元等以分布式方式实现，便于缩扩容弹性管理。
基于边缘UPF具有的上述功能，本公开具有如下有益效果：
(1)边缘UPF按3GPP规范实现，完整实现协议功能和业务能力，对SMF、UPF、UE等以分锚点UPF方式对接；SMF/UPF/EMS等周边网元无特殊或非标准的感知。
(2)边缘UPF实现业务的本地化处理，安全可靠；SmartUPF和CoUPF协同，实现电信级可靠性。
(3)边缘UPF相比普通UPF，极大的降低了园区UPF的部署成本和部署要求，实现低能耗和快速部署、即插即用；如针对20G的园区UPF部署场景，SmartUPF的成本和功耗仅相当于普通UPF的50％。
(4)边缘UPF实现业务本地化，用户流量信息在本地处理，实现高性能、低时延；硬件加速方式下，网元的报文时延在100us以下，且单用户速率最大可满足100G。
(5)边缘UPF业务能力全面、实现其能力开放。
请参见图2，图2为本公开实施例提供的一种网元访问方法，该方法可应用于管理UPF；该方法包括以下步骤：
步骤201、接收来自于边缘UPF的访问请求；
步骤202、生成与访问请求对应的访问响应；
步骤203、向边缘UPF发送访问响应。
当访问请求为的类型指示访问请求为业务类报文时，边缘UPF向管理UPF上报该访问请求就是为了获得访问请求对应的业务的报文转发策略。
在生成访问响应时，一个可选实施例中，获取访问请求的报文特征；确定与报文特征 匹配的报文转发策略；将报文转发策略作为访问响应。
本实施例中，管理UPF还可以将在会话过程中为园区用户分配的地址参数发送给边缘UPF，以便边缘UPF生成路由信息，并并行路由发布。
具体实现时，管理UPF接收来自于边缘UPF的路由发布请求；响应于路由发布请求，向边缘UPF返回园区用户的地址参数。
基于以上对边缘UPF和管理UPF的具体描述，以具体的场景实施例对边缘UPF和管理UPF的交互进行展开描述。
实施例1：实现SmartUPF和CoUPF的部署和通信，图3为本实施例提供的SmartUPF和CoUPF的内部架构图。
步骤1，CoUPF与SmartUPF分开部署，如图4所示；
步骤2，CoUPF与SmartUPF建立Nx连接，如图5所示；
步骤3，CoUPF上配置SmartUPF的IP地址池，TEIDU等信息，通过Nx连接下发给SmartUPF；
步骤4，CoUPF把新增UPF业务配置通过Nx连接下发给SmartUPF；
步骤5，CoUPF和SmartUPF之间的信令报文采用PFCP协议进行交互，如图4所示；
步骤6，CoUPF和SmartUPF之间的媒体报文采用隧道方式通信。隧道类型包括但不限于自定义udp隧道、GTP隧道、GRE隧道等。下面以自定义udp隧道为例，给出协议栈分层如图5所示。
其中图4中的内部头(InnerHead)采用16字节结构，如图表二所示，应理解，表一仅用作举例示意图，具体可做调整。
表二
InnerType用来表征消息类型，消息类型可参见表二所示，应理解，表三仅用作举例，具体可做调整。
表三

实施例二：SmartUPF的会话建立，如图6所示。
步骤1，SMF触发建立N4会话流程；
步骤2，Smart-UPF收到SMF发送的N4 Session Establishment Request(会话建立请求)；
步骤3，Smart-UPF发送N4 Session Establishment Request消息给CoUPF；
步骤4，CoUPF完成分配IP地址，分配业务隧道资源等操作；
步骤5，CoUPF发送N4 Session Establishment Response(会话建立响应)给SmartUPF；
步骤6，SmartUPF创建N4会话，建立业务隧道，发送N4 Session Establishment Response消息给SMF。
实施例三：边缘SmartUPF的会话更新，如图7所示。
步骤1，SMF触发更新N4会话流程；
步骤2，SmartUPF收到SMF发送的N4 Session Modification Request(会话更改请求)；
步骤3，SmartUPF发送N4 Session Modification Request消息送给CoUPF；
步骤4，CoUPF完成更新业务隧道资源等操作；
步骤5，CoUPF发送N4 Session Modification Response(会话更改响应)给SmartUPF；
步骤6，SmartUPF更新N4会话，创建/更新业务隧道，发送N4 Session Modification Response消息给SMF。
实施例四：SmartUPF的会话删除，如图8所示。
步骤1，SMF触发释放N4会话流程；
步骤2，SmartUPF收到SMF发送的N4 Session Release Request(会话释放请求)；
步骤3，SmartUPF将N4 Session Release Request消息发送给管理UPF；
步骤4，CoUPF释放业务隧道资源等操作；
步骤5，CoUPF发送N4 Session Release Response(会话释放响应)给SmartUPF；
步骤6，SmartUPF释放N4会话，发送N4 Session Release Response消息给SMF。
实施例五：SmartUPF的ULCL流程，如图9所示。
步骤1，PDU会话建立，锚点是UPF1；
步骤2，SMF根据业务路由信息进行UPF重选，选择的结果为：SmartUPF为Uplink Classifier，UPF2为业务App2数据的锚点，UPF1为业务App1数据的锚点；SmartUPF收到SMF发送的N4 Session Establishment Request消息；
步骤3，SmartUPF按发送N4 Session Establishment Request给管理UPF；
步骤4，CoUPF完成分配IP地址，分配业务隧道资源等操作；
步骤5，CoUPF发送N4 Session Establishment Response给Smart-UPF；
步骤6，SmartUPF建立N4会话，创建业务隧道，发送N4 Session Establishment Response消息给SMF；
步骤7，SMF向UPF1发送N4 Session Modification Request消息，更新N4会话；
步骤8，UPF1完成会话更新，发送N4 Session Modification Response消息给SMF。
实施例六：SmartUPF高性能转发之无本地策略流程，如图10所示。
步骤1，根据路由发布的结果，报文被引流到SmartUPF；
步骤2，SmartUPF不存在快转表，无本地策略，根据报文特征识别出报文归属的CoUPF，通过携带SmartUPF的pfu的标识，将报文送过去；
步骤3，CoUPF收到报文进行会话、策略、深度报文识别等操作，将需要的Qos策略下发给SmartUPF，同时完成本报文的处理，送SmartUPF外发；
步骤4，SmartUPF收到CoUPF发来的Qos策略信息后保存到本地，并根据报文特征生成快转策略。根据快转表完成报文外发。
实施例七：SmartUPF高性能转发之有本地策略流程，如图11所示。
步骤1，根据路由发布的结果，报文被引流到SmartUPF。
步骤2，SmartUPF存在快转表，报文命中快转表，直接转发。
实施例八：SmartUPF高性能转发之流量上报流程，如图12所示。
步骤1，有本地会话的，按照会话收集流量信息；
步骤2，将收集的流量信息上报给CoUPF；
步骤3，CoUPF上报给SMF。
实施例九：SmartUPF高性能转发之路由发布流程，如图13所示。
步骤1，SmartUPF上电后，上报接口给CoUPF，CoUPF最终将信息上报到协议栈中心(Rosng)，协议栈中心形成对外逻辑接口；
步骤2，CoUPF上读取配置的地址池和业务地址，生成待发布路由队列；
步骤3，CoUPF将路由信息打包发给SmartUPF；
步骤4，SmartUPF通过外发口，将路由发送出去。
实施例十：SmartUPF的QoS业务流程，如图14所示。
步骤1，用户业务首个请求报文到达SmartUPF的PFU模块，根据报文五元组特征进行业务QoS策略匹配，发现没有命中任何QoS策略；
步骤2，报文转发至DPI-D模块进行QoS策略请求；DPI-D模块根据业务报文特征进行本地策略匹配仍然没有命中，说明本地没有该业务特征数据及QoS策略缓存；
步骤3，SmartUPF将业务请求报文通过Proxy-C模块上送CoUPF。CoUPF根据用户信息、报文五元组特征、业务报文特征等数据进行报文深度分析，综合决策出该报文QoS策略；
步骤4，CoUPF将该业务报文QoS策略通过Proxy-S模块下发给SmartUPF；
步骤5，DPI-D模块收到QoS策略后根据报文业务特征创建索引缓存策略，并将策略下发给PFU；
步骤6，PFU上根据报文五元组信息缓存策略，同时执行策略并对该报文进行转发；
步骤7，该业务相同业务流的报文到达PFU后，PFU可以直接根据五元组特征进行匹配命中QoS策略，执行策略并对报文进行转发；
步骤8，当相同业务又发起了新的业务流到达PFU后，PFU根据五元组信息无法命中策略；
步骤9，业务请求报文转发至DPI-D模块，DPI-D模块根据业务特征信息命中了缓存的策略信息；
步骤10，DPI-D直接将策略信息下发给PFU，PFU收到策略后根据报文五元组信息缓存策略，同时执行策略并对该报文进行转发。
应理解，在图14中，两个SmartUPF实际为同一个UPF，为了更清楚描述信号流的走向，分为两个模块对同一个SmartUPF进行描述。并且，图14中的数字代表本实施例中的各步骤。
实施例十一：SmartUPF的业务报文转发流程，如图15所示。
业务报文的转发流程可以主要分为以下几类：
步骤1，从DPI-D上获取了缓存策略后，在PFU上可通过报文五元组识别进行直接转发
步骤2，报文处理策略中包含增值业务，业务请求报文需要上送DPI-D进行报文修改，例如：头增强、重定向等业务；报完修改完成后再通过PFU的外部接口发送出去，非业务请求报文可以在PFU直接进行转发；
步骤3，报文需要进行深度解析，DPI-D缓存的策略无法对报文进行精确识别，例如：欺诈报文等，此时报文全部上送CoUPF进行深度识别。直到可以解析出可供DPI-D识别的业务策略后才下发转发策略。
应理解，在图15中，三个SmartUPF实际为同一个UPF，为了更清楚描述信号流的走向，分为三个模块对同一个SmartUPF进行描述。并且，图15中的数字代表本实施例中的各步骤。
实施例十二：SmartUPF的告警、性能统计等业务流程，如图16(a)所示。
运维上SmartUPF和CoUPF对应实例对外体现一个UPF整体，告警统一可以由SmartUPF对上级网管呈现。
步骤1，SmartUPF上的模块产生告警(以PFU/DPU模块为例)上报SmartUPF-OAM,SmartUPF-OAM直接上报上级网管，对外呈现UPF业务模块告警；
步骤2，CoUPF上的模块产生告警(以PFU模块为例)上报CoUPF-OAM，并携带实例信息；CoUPF-OAM根据实例信息查询到对应的SmartUPF，向SmartUPF-OAM转发告警；SmartUPF-OAM收到CoUPF的告警信息后上报上级网管，对外呈现UPF管理模块告 警。
如图16(b)所示，性能统计机制：
步骤1，在SmartUPF的上级网管上创建性能统计任务，上级网管将任务下发给SmartUPF-OAM；
步骤2，SmartUPF-OAM收到性能统计任务后同时向CoUPF-OAM转发任务；
步骤3，CoUPF-OAM向CoUPF-PFU下发性能统计任务；
步骤4，SmartUPF上PFU/DPU模块定时或者定量推送业务流量到CoUPF的PFU模块；
步骤5，CoUPF-PFU收到上报流量后根据用户完整的信息产生原始性能统计数据上报CoUPF-OAM，CoUPF-OAM生成性能统计数据文件；
步骤6，CoUPF-OAM将性能统计数据生成文件传输给SmartUPF-OAM；
步骤7，SmartUPF-OAM保存文件供上级网管查询使用。
基于同一构思，本公开实施例中提供了一种网元访问装置，该装置的具体实施可参见方法实施例部分的描述，重复之处不再赘述，如图17所示，该装置主要包括：
获取模块1701，用于获取园区用户的访问请求；
转发模块1702，用于向与边缘UPF匹配的管理UPF转发访问请求，以使得管理UPF生成与访问请求对应的访问响应；
第一接收模块1703，用于接收来自于管理UPF的访问响应；
处理模块1704，用于基于访问请求的类型对访问响应进行处理。
该装置还用于：
向管理UPF转发访问请求之前，当确定访问请求的类型指示访问请求为业务类报文，获取访问请求的业务类型；
确定未存储有与业务类型对应的报文转发策略；
向管理UPF转发访问请求之后，接收并存储来自于管理UPF的报文转发策略；
处理模块1704用于：
按照报文转发策略对业务类报文进行转发。
该装置用于：
获取访问请求的报文特征；
当确定PFU模块和DPI-D模块中均未存储有与报文特征匹配的报文转发策略时，确定未存储有与业务类型对应的报文转发策略；
转发模块1702用于：
通过客户端代理单元向管理UPF发送访问请求；
该装置用于：
接收来自于管理UPF的服务端代理单元的报文转发策略；
通过DPI-D模块创建报文业务特征与报文转发策略的对应关系；
通过PFU模块存储对应关系。
该装置还用于：
获取园区用户的访问请求之前，向管理UPF发送路由发布请求；
接收管理UPF响应于路由发布请求返回的园区用户的地址参数；
基于地址参数，生成园区用户与边缘UPF的路由信息，路由信息指示园区用户与边缘UPF相匹配；
向交换机发布路由信息。
访问请求包括以下一种或多种：
会话建立请求；
会话更新请求；
会话删除请求；
上行分类请求；
流量信息上报请求。
基于同一构思，本公开实施例中提供了一种网元访问装置，该装置的具体实施可参见方法实施例部分的描述，重复之处不再赘述，如图18所示，该装置主要包括：
第二接收模块1801，用于接收来自于边缘UPF的访问请求；
生成模块1802，用于生成与访问请求对应的访问响应；
发送模块1803，用于向边缘UPF发送访问响应。
访问请求的类型指示访问请求为业务类报文；
生成模块1802用于：
获取访问请求的报文特征；
确定与报文特征匹配的报文转发策略；
将报文转发策略作为访问响应。
该装置还用于：
接收来自于边缘UPF的访问请求之前，接收来自于边缘UPF的路由发布请求；
响应于路由发布请求，向边缘UPF返回园区用户的地址参数。
基于同一构思，本公开实施例中还提供了一种网元，如图19所示，该网元主要包括：处理器1901、存储器1902和通信总线1903，其中，处理器1901和存储器1902通过通信总线1903完成相互间的通信。其中，存储器1902中存储有可被处理器1901执行的程序，处理器1901执行存储器1902中存储的程序，实现如下步骤：
获取园区用户的访问请求；向与边缘UPF匹配的管理UPF转发访问请求，以使得管理UPF生成与访问请求对应的访问响应；接收来自于管理UPF的访问响应；基于访问请求的类型对访问响应进行处理；
或，
接收来自于边缘UPF的访问请求；生成与访问请求对应的访问响应；向边缘UPF发送访问响应。
上述网元中提到的通信总线1903可以是外设部件互连标准(Peripheral Component Interconnect，简称PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture， 简称EISA)总线等。该通信总线1903可以分为地址总线、数据总线、控制总线等。为便于表示，图19中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
存储器1902可以包括随机存取存储器(Random Access Memory，简称RAM)，也可以包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。可选地，存储器还可以是至少一个位于远离前述处理器1901的存储装置。
上述的处理器1901可以是通用处理器，包括中央处理器(Central Processing Unit，简称CPU)、网络处理器(Network Processor，简称NP)等，还可以是数字信号处理器(Digital Signal Processing，简称DSP)、专用集成电路(Application Specific Integrated Circuit，简称ASIC)、现场可编程门阵列(Field-Programmable Gate Array，简称FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。
在本公开的又一实施例中，还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序，当该计算机程序在计算机上运行时，使得计算机执行上述实施例中所描述网元访问方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行该计算机指令时，全部或部分地产生按照本公开实施例所述的流程或功能。该计算机可以时通用计算机、专用计算机、计算机网络或者其他可编程装置。该计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、微波等)方式向另外一个网站站点、计算机、服务器或数据中心进行传输。该计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。该可用介质可以是磁性介质(例如软盘、硬盘、磁带等)、光介质(例如DVD)或者半导体介质(例如固态硬盘)等。
需要说明的是，在本文中，诸如“第一”和“第二”等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
以上所述仅是本发明的具体实施方式，使本领域技术人员能够理解或实现本发明。对这些实施例的多种修改对本领域的技术人员来说将是显而易见的，本文中所定义的一般原理可以在不脱离本发明的范围的情况下，在其它实施例中实现。因此，本发明将不会被限制于本文所示的这些实施例，而是要符合与本文所申请的原理和新颖特点相一致的最宽的范围。

Claims (13)

  1. 一种网元访问方法，应用于边缘UPF，包括：
    获取园区用户的访问请求；
    向与所述边缘UPF匹配的管理UPF转发所述访问请求，以使得所述管理UPF生成与所述访问请求对应的访问响应；
    接收来自于所述管理UPF的所述访问响应；以及
    基于所述访问请求的类型对所述访问响应进行处理。
  2. 根据权利要求1所述的方法，其中，向管理UPF转发所述访问请求之前，还包括：
    当确定所述访问请求的类型指示所述访问请求为业务类报文，获取所述访问请求的业务类型；以及
    确定未存储有与所述业务类型对应的报文转发策略；
    向管理UPF转发所述访问请求之后，还包括：
    接收并存储来自于所述管理UPF的所述报文转发策略；
    基于所述访问请求的类型对所述访问响应进行处理，包括：
    按照所述报文转发策略对所述业务类报文进行转发。
  3. 根据权利要求2所述的方法，其中，确定未存储有与所述业务类型对应的报文转发策略，包括：
    获取所述访问请求的报文特征；以及
    当确定PFU模块和DPI-D模块中均未存储有与所述报文特征匹配的报文转发策略时，确定未存储有与所述业务类型对应的报文转发策略；
    向管理UPF转发所述访问请求，包括：
    通过客户端代理单元向所述管理UPF发送所述访问请求；
    接收并存储来自于所述管理UPF的所述报文转发策略，包括：
    接收来自于所述管理UPF的服务端代理单元的所述报文转发策略；
    通过所述DPI-D模块创建所述报文业务特征与所述报文转发策略的对应关系；以及
    通过所述PFU模块存储所述对应关系。
  4. 根据权利要求1所述的方法，其中，获取园区用户的访问请求之前，还包括：
    向所述管理UPF发送所述路由发布请求；
    接收所述管理UPF响应于所述路由发布请求返回的所述园区用户的地址参数；
    基于所述地址参数，生成所述园区用户与所述边缘UPF的路由信息，所述路由信息指示所述园区用户与所述边缘UPF相匹配；以及
    向交换机发布所述路由信息。
  5. 根据权利要求1所述的方法，其中，所述访问请求包括以下一种或多种：
    会话建立请求；
    会话更新请求；
    会话删除请求；
    上行分类请求；以及
    流量信息上报请求。
  6. 一种网元访问方法，应用于管理UPF，包括：
    接收来自于边缘UPF的访问请求；
    生成与所述访问请求对应的访问响应；以及
    向所述边缘UPF发送所述访问响应。
  7. 根据权利要求6所述的方法，其中，所述访问请求的类型指示所述访问请求为业务类报文；
    生成与所述访问请求对应的访问响应，包括：
    获取所述访问请求的报文特征；
    确定与所述报文特征匹配的报文转发策略；以及
    将所述报文转发策略作为所述访问响应。
  8. 根据权利要求6所述的方法，其中，接收来自于边缘UPF的访问请求之前，还包括：
    接收来自于所述边缘UPF的路由发布请求；
    响应于所述路由发布请求，向所述边缘UPF返回所述园区用户的地址参数。
  9. 一种网元访问装置，包括：
    获取模块，用于获取园区用户的访问请求；
    转发模块，用于向与所述边缘UPF匹配的管理UPF转发所述访问请求，以使得所述管理UPF生成与所述访问请求对应的访问响应；
    第一接收模块，用于接收来自于所述管理UPF的所述访问响应；以及
    处理模块，用于基于所述访问请求的类型对所述访问响应进行处理。
  10. 一种网元访问装置，包括：
    第二接收模块，用于接收来自于边缘UPF的访问请求；
    生成模块，用于生成与所述访问请求对应的访问响应；以及
    发送模块，用于向所述边缘UPF发送所述访问响应。
  11. 一种网元访问***，包括：
    管理UPF和边缘UPF；
    所述边缘UPF用于，获取园区用户的访问请求；向与所述边缘UPF匹配的管理UPF转发所述访问请求，以使得所述管理UPF生成与所述访问请求对应的访问响应；接收来自于所述管理UPF的所述访问响应；基于所述访问请求的类型对所述访问响应进行处理；
    所述管理UPF用于，接收来自于边缘UPF的访问请求；生成与所述访问请求对应的访问响应；向所述边缘UPF发送所述访问响应。
  12. 一种网元，包括：处理器、存储器和通信总线，其中，处理器和存储器通过通信总线完成相互间的通信；
    所述存储器，用于存储计算机程序；
    所述处理器，用于执行所述存储器中所存储的程序，实现权利要求1-5中任一项所述的网元访问方法或权利要求6-8任一项所述的网元访问方法。
  13. 一种计算机可读存储介质，存储有计算机程序，其中，所述计算机程序被处理器执行时实现根据权利要求1-5中任一项所述的网元访问方法或根据权利要求6-8中任一项所述的网元访问方法。
PCT/CN2023/093984 2022-06-29 2023-05-12 网元访问方法、装置、网元及存储介质 WO2024001566A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210758875.2 2022-06-29
CN202210758875.2A CN117354372A (zh) 2022-06-29 2022-06-29 网元访问方法、装置、网元及存储介质

Publications (1)

Publication Number Publication Date
WO2024001566A1 true WO2024001566A1 (zh) 2024-01-04

Family

ID=89354550

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/093984 WO2024001566A1 (zh) 2022-06-29 2023-05-12 网元访问方法、装置、网元及存储介质

Country Status (2)

Country Link
CN (1) CN117354372A (zh)
WO (1) WO2024001566A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120224481A1 (en) * 2011-03-02 2012-09-06 3Inova Networks Inc. Traffic management in distributed wireless networks
US20140169269A1 (en) * 2012-12-19 2014-06-19 Cisco Technology, Inc. SYSTEMS, METHODS AND MEDIA FOR MOBILE MANAGEMENT ENTITY (MME) SELECTION BY EVOLVED NODE B (eNodeB)
CN108811011A (zh) * 2017-05-05 2018-11-13 华为技术有限公司 一种会话管理方法、网络设备和通信***
CN112087390A (zh) * 2019-06-14 2020-12-15 华为技术有限公司 一种网络路由方法及装置
CN113225697A (zh) * 2021-07-07 2021-08-06 中兴通讯股份有限公司 群组用户通信方法、装置、网络设备和存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120224481A1 (en) * 2011-03-02 2012-09-06 3Inova Networks Inc. Traffic management in distributed wireless networks
US20140169269A1 (en) * 2012-12-19 2014-06-19 Cisco Technology, Inc. SYSTEMS, METHODS AND MEDIA FOR MOBILE MANAGEMENT ENTITY (MME) SELECTION BY EVOLVED NODE B (eNodeB)
CN108811011A (zh) * 2017-05-05 2018-11-13 华为技术有限公司 一种会话管理方法、网络设备和通信***
CN112087390A (zh) * 2019-06-14 2020-12-15 华为技术有限公司 一种网络路由方法及装置
CN113225697A (zh) * 2021-07-07 2021-08-06 中兴通讯股份有限公司 群组用户通信方法、装置、网络设备和存储介质

Also Published As

Publication number Publication date
CN117354372A (zh) 2024-01-05

Similar Documents

Publication Publication Date Title
WO2020207490A1 (en) System, apparatus and method to support data server selection
WO2018145654A1 (zh) 实现多接入管理的方法、装置及计算机存储介质
US9173244B2 (en) Methods for establishing and using public path, M2M communication method, and systems thereof
WO2019052376A1 (zh) 一种业务处理方法、移动边缘计算设备及网络设备
WO2020019764A1 (zh) 信息传输方法、设备及计算机可读存储介质
CN111629450B (zh) 一种数据传输方法、相关设备以及存储介质
US10945180B2 (en) Mobility management method, apparatus, and system
WO2011060673A1 (zh) 公用承载建立的方法、数据传输方法和核心网络侧设备
EP4044685A1 (en) Network access method and communication apparatus
US11102116B2 (en) Method and device for hosting application by access node
JP7192140B2 (ja) ポリシー管理方法及び装置
US20200229037A1 (en) Implementing edge network services at access elements for mobile edge computing
US11412564B2 (en) Method and apparatus for providing next generation network service in heterogeneous network environment
WO2018082070A1 (zh) 一种数据报文处理方法及控制面网元、用户面网元
WO2024001566A1 (zh) 网元访问方法、装置、网元及存储介质
KR20230157194A (ko) 스위치를 이용하는 트래픽 처리를 위한 장치 및 방법
CN109150752B (zh) 缓存控制方法、网元及控制器
EP4395267A1 (en) Method and apparatus for traffic processing using traffic classification in wireless communication system
CN113938349B (zh) 无线工业总线通信方法及***
US20220294739A1 (en) Method and apparatus for improved packet detection rule provision
WO2023015973A1 (zh) 一种网络切片准入控制方法和装置
KR20220118273A (ko) 에지 어플리케이션 서버 디스커버리 방법 및 장치
JP2015061155A (ja) 通信装置、通信システムおよび通信制御方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23829752

Country of ref document: EP

Kind code of ref document: A1