CN114556894A - Method, apparatus and computer program product for packet forwarding control protocol message bundling - Google Patents

Abstract

Methods and apparatus, including computer program products, are provided for Packet Forwarding Control Protocol (PFCP) message bundling. In an example embodiment, an apparatus includes means, such as a processor and memory including computer program code. In some embodiments, the apparatus may be configured to: determining that more than one control protocol message should be sent between a control plane entity and a user plane entity or between the user plane entity and the control plane entity; determining that the control plane entity and the user plane entity support sending and receiving a single datagram carrying more than one control protocol message; extending a header of each control protocol message to indicate that the datagram carries more than one control protocol message; combining one or more message types and corresponding message elements of more than one control protocol message into a single datagram; and causes the single datagram to be sent.

Description

Method, apparatus and computer program product for packet forwarding control protocol message bundling

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the U.S. Patent and Trademark Office entitled "Method, Apparatus, and Computer Program Product for Packet Forwarding Control Protocol Messages Bundling", filed on August 16, 2019 Priority to and benefit from Provisional Patent Application No. 62/888,166, the entire disclosure of which is incorporated herein by reference in its entirety for all purposes.

technical field

The subject matter described herein relates to wireless telecommunications.

Background technique

Users of modern telecommunications networks have adopted the use of such networks to access, move and process large amounts of data. As a result, telecommunications networks have become an indispensable and irreplaceable tool to support people's conduct of business, access to important information and every aspect of their daily lives. While many modern telecommunications networks have proven to provide reliable services to many users, the centrality of network connectivity to processes involving fundamental aspects of users' health, safety, business and lifestyle has led to the need to improve the reliability of current and next-generation telecommunications networks Sex and flexibility.

Telecom networks such as fifth generation mobile networks (5G networks) are expected to be the next major phase of mobile telecom standards and bring many improvements to the mobile network user experience. For example, 5G networks should provide new technological solutions to achieve higher throughput, lower latency, higher reliability, higher connectivity and higher mobile range.

In addition to these improvements in performance, 5G networks are expected to expand the flexibility of network usage and allow for a wider range of use cases and business models for users.

SUMMARY OF THE INVENTION

Methods, apparatus and computer program products are provided for Packet Forwarding Control Protocol (PFCP) message bundling.

In some example embodiments, an apparatus may be provided that includes at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to at least : determine whether more than one control protocol message should be sent from the control plane entity to the user plane entity or from the user plane entity to the control plane entity; determine whether both the control plane entity and the user plane entity support sending and receiving the more than one a single datagram of a control protocol message; extending the header of each of the more than one control protocol message to indicate that a single datagram carries the more than one control protocol message; converting one or more of the more than one control protocol message combining a plurality of message types and corresponding message elements into the single datagram; and causing the control plane entity to send the single datagram carrying the more than one control protocol message to the user plane entity or causing the user plane The entity sends the single datagram carrying the more than one control protocol message to the control plane entity. In some embodiments, the user plane entity includes a user plane function and the control plane entity includes a session management function. In some embodiments, the session management functions may include 5GC session management functions for any suitable Control and User Plane Separation (CUPS) architecture, such as for Gateway GPRS Support Node (GGSN-C), Trusted Radio Ingress Gateway (TWAG-C), Broadband Network Gateway (BNG), N4, Sxa, Sxb, Sxc, Evolved Packet Core (EPC) SWG-C, EPC PGW-C, EPC TDF-C, etc. In some embodiments, the control protocol message comprises a Packet Forwarding Control Protocol (PFCP) message. In some embodiments, at least one memory and computer program code are configured to, with at least one processor, cause the apparatus to at least: extend a header of each of the more than one control protocol messages to include a follow-up flag to indicate A single datagram carries the more than one control protocol message. In some embodiments, the single control protocol message includes being configured to be packetized over an N4 interface in a Fifth Generation Core (5GC) network or over an Sxa, Sxb, or Sxc interface in an Evolved Packet Core (EPC) network , a single UDP/IP packet that is exchanged and processed. In some embodiments, the more than one control protocol message carried in a single control protocol message is a control plane request or response related to the same PFCP session or different PFCP sessions handled by the same peer PFCP entity.

According to another embodiment, a method is provided, the method comprising: determining whether more than one control protocol message should be sent from a control plane entity to a user plane entity or from the user plane entity to the control plane entity; determining whether to control Both the plane entity and the user plane entity support sending and receiving a single datagram carrying the more than one control protocol message; extending the header of each control protocol message in the more than one control protocol message to indicate that a single datagram carries the more than one control protocol message; a control protocol message; combining one or more message types and corresponding message elements of the more than one control protocol message into the single datagram; and causing the control plane entity to send a message to the user plane entity that carries the more than one The single datagram of a control protocol message or cause the user plane entity to send the single datagram carrying the more than one control protocol message to the control plane entity. In some embodiments, the user plane entity includes a user plane function and the control plane entity includes a session management function. In some embodiments, the session management functions may include 5GC session management functions for any suitable Control and User Plane Separation (CUPS) architecture, such as for Gateway GPRS Support Node (GGSN-C), Trusted Radio Ingress Gateway (TWAG-C), Broadband Network Gateway (BNG), N4, Sxa, Sxb, Sxc, Evolved Packet Core (EPC) SWG-C, EPC PGW-C, EPC TDF-C, etc. In some embodiments, the control protocol message comprises a Packet Forwarding Control Protocol (PFCP) message. In some embodiments, the method may further include extending a header of each of the more than one control protocol message to include a follow-up flag to indicate that a single datagram carries the more than one control protocol message. In some embodiments, the single control protocol message includes being configured to be packetized over an N4 interface in a Fifth Generation Core (5GC) network or over an Sxa, Sxb, or Sxc interface in an Evolved Packet Core (EPC) network , a single User Datagram/Internet Protocol (UDP/IP) packet that is exchanged and processed. In some embodiments, the more than one control protocol message carried in a single control protocol message is a control plane request or response related to the same PFCP session or different PFCP sessions handled by the same peer PFCP entity.

According to yet another embodiment, there is provided an apparatus comprising means for determining whether more than one control protocol message should be sent from a control plane entity to a user plane entity or from the user plane entity to the control plane entity, such as The above apparatus comprising one or more processors and one or more memories comprising program code; for determining whether both a control plane entity and a user plane entity support sending and receiving of a single datagram carrying the more than one control protocol message means; means for extending the header of each of the more than one control protocol message to indicate that a single datagram carries the more than one control protocol message; means for converting one or more of the more than one control protocol message means for combining a plurality of message types and corresponding message elements into said single datagram; or means for causing said control plane entity to send said single datagram carrying said more than one control protocol message to said user plane entity , or means for causing the user plane entity to send the single datagram carrying the more than one control protocol message to the control plane entity. In some embodiments, the user plane entity includes a user plane function and the control plane entity includes a session management function. In some embodiments, the session management functions may include 5GC session management functions for any suitable Control and User Plane Separation (CUPS) architecture, such as for Gateway GPRS Support Node (GGSN-C), Trusted Radio Ingress Gateway (TWAG-C), Broadband Network Gateway (BNG), N4, Sxa, Sxb, Sxc, Evolved Packet Core (EPC) SWG-C, EPC PGW-C, EPC TDF-C, etc. In some embodiments, the control protocol message comprises a Packet Forwarding Control Protocol (PFCP) message. In some embodiments, the apparatus may further comprise means for extending a header of each of the more than one control protocol message to include a follow-up flag to indicate that a single datagram carries the more than one control protocol message . In some embodiments, the single control protocol message includes being configured to be packetized over an N4 interface in a Fifth Generation Core (5GC) network or over an Sxa, Sxb, or Sxc interface in an Evolved Packet Core (EPC) network , a single UDP/IP packet that is exchanged and processed. In some embodiments, the more than one control protocol message carried in a single control protocol message is a control plane request or response related to the same PFCP session or different PFCP sessions handled by the same peer PFCP entity.

According to yet another embodiment, there is provided a computer-readable medium, such as a non-transitory computer-readable medium including program code that, when executed, causes operations including: the user plane entity still sends more than one control protocol message from the user plane entity to the control plane entity; determining whether both the control plane entity and the user plane entity support sending and receiving a single datagram carrying the more than one control protocol message; extending the header of each of the more than one control protocol message to indicate that a single datagram carries the more than one control protocol message; combining one or more message types of the more than one control protocol message with the corresponding message elements are combined into the single datagram; and cause the control plane entity to send the single datagram carrying the more than one control protocol message to the user plane entity or cause the user plane entity to send the control plane entity to the control plane entity The single datagram carrying the more than one control protocol message is sent. In some embodiments, the user plane entity includes a user plane function and the control plane entity includes a session management function. In some embodiments, the session management functions may include 5GC session management functions for any suitable Control and User Plane Separation (CUPS) architecture, such as for Gateway GPRS Support Node (GGSN-C), Trusted Radio Ingress Gateway (TWAG-C), Broadband Network Gateway (BNG), N4, Sxa, Sxb, Sxc, Evolved Packet Core (EPC) SWG-C, EPC PGW-C, EPC TDF-C, etc. In some embodiments, the control protocol message comprises a Packet Forwarding Control Protocol (PFCP) message. In some embodiments, the program code, when executed, may also cause operations comprising: extending a header of each of the more than one control protocol message to include a follow-up flag to indicate a single datagram bearer The more than one control protocol message. In some embodiments, the single control protocol message includes being configured to be packetized over an N4 interface in a Fifth Generation Core (5GC) network or over an Sxa, Sxb, or Sxc interface in an Evolved Packet Core (EPC) network , a single UDP/IP packet that is exchanged and processed. In some embodiments, the more than one control protocol message carried in a single control protocol message is a control plane request or response related to the same PFCP session or different PFCP sessions handled by the same peer PFCP entity.

The above-described aspects and features may be implemented in systems, apparatus, methods and/or articles according to a desired configuration. The details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the description below. The features and advantages of the subject matter described herein will be apparent from the description and drawings, and from the claims.

Description of drawings

In the attached drawings,

1 depicts an example of a portion of a 5G wireless network in accordance with some example embodiments;

FIG. 2 depicts an example of an apparatus according to some example embodiments;

3 depicts a typical header for a Packet Forwarding Control Protocol (PFCP) message in accordance with some example embodiments;

4 depicts a UDP/IP packet bundling multiple PFCP messages in accordance with some example embodiments;

5 depicts a message header, e.g., for a PFCP message, that includes a subsequent flag indicating that another message is bundled in the same datagram, according to some example embodiments;

Figure 6 depicts a message header, e.g., a PFCP message header for a node-related message, the message header including a subsequent flag indicating that another message is bundled in the same datagram;

7 depicts a message header, e.g., a PFCP message header for a session related message, the message header including a subsequent flag indicating that another message is bundled in the same datagram;

Figure 8 depicts a message indicating user plane functional characteristics in accordance with some example embodiments;

9 depicts a feature support flag indicating a user plane function support bundling message (eg, PFCP message bundling) in accordance with some example embodiments;

Figure 10 depicts a message indicating control plane functional characteristics in accordance with some example embodiments;

Figure 11 depicts a feature support flag indicating a control plane function support bundling message (eg, PFCP message bundling) according to some example embodiments; and

12 depicts a process flow diagram of a method for PFCP message bundling in accordance with some example embodiments.

Like reference numbers are used to refer to the same or similar items in the drawings.

Detailed ways

Some embodiments will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the present disclosure are shown. Indeed, various embodiments of the present disclosure may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. The same reference numbers refer to the same elements throughout. As used herein, the terms "data," "content," "information," and similar terms are used interchangeably to refer to data capable of being transmitted, received, and/or stored in accordance with embodiments of the present disclosure. Therefore, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present disclosure.

Furthermore, as used herein, the term "circuitry" refers to (a) a purely hardware circuit implementation (eg, an implementation using analog circuitry and/or digital circuitry); (b) a combination of a circuit and a computer program product, includes software and/or firmware instructions stored on one or more computer-readable memories that work together to cause an apparatus to perform one or more of the functions described herein; (c) circuitry, such as a microprocessor or microprocessor part of it that requires software or firmware to run, even if the software or firmware doesn't actually exist. This definition of "circuitry" applies to all uses of this term herein, including in any claims. As another example, as used herein, the term "circuitry" also includes implementations that include one or more processors and/or portions thereof and accompanying software and/or firmware. As another example, the term "circuitry" as used herein also includes, for example, baseband integrated circuits or application processor integrated circuits for mobile phones, or servers, cellular network equipment, other network equipment, field programmable gate arrays and/or or similar integrated circuits in other computing devices.

As defined herein, "computer-readable storage medium", which refers to physical storage media (eg, volatile or non-volatile storage devices), may be distinguished from "computer-readable transmission medium", which refers to electromagnetic signals .

Referring now to FIG. 1, it should be understood that example embodiments of the present invention disclosed and/or otherwise described herein occur in the context of telecommunications networks, including but not limited to conforming to and/or otherwise incorporating fifth generation (5G ) architecture of various aspects of telecommunication networks. FIG. 1 is an example networked system 100 in accordance with example embodiments of the present disclosure. FIG. 1 specifically illustrates a user equipment (UE) 102 that may communicate with a radio access network (RAN) 104 and an access and mobility management function (AMF) 108 and a user plane function (UPF) 106 . AMF 108 may in turn communicate with core network services including session management function (SMF) 110 and policy control function (PCF) 114 . Core network services may also communicate with application server/application functions (AS/AF) 112 . Other networking services include Network Slice Selection Function (NSSF) 122 , Authentication Server Function (AUSF) 120 , User Data Management (UDM) 118 and Data Network (DN) 116 . In some example implementations of embodiments of the present disclosure, AMF, SMF, UPF, PCF, AUSF, UDM, AF, and NSSF are all considered NFs. It should be understood that one or more additional network functions (NFs) and network resource functions (NRFs) may be incorporated into the networked system. As shown in FIG. 1, NRF 124 is incorporated into the network and is configured to interface with other network functions, including but not necessarily limited to AMF 108, SMF 110, and PCF 114. The methods, apparatus and computer program products described herein are described in the context of fifth generation (5G) core networks and systems such as those depicted in Figure 1, however, the methods described may be , a standard or a wider context of application within a protocol.

Turning now to FIG. 2, examples of core network equipment (CNA) (including core network services: UPF 106, AMF 108, SMF 110, PCF 114 and/or another NF and/or NRF) may be implemented as example embodiments in accordance with the present disclosure The core network device 200 is configured instead. As described below in conjunction with the flowcharts of FIGS. 3 and 4 , the CNA 200 of an example embodiment may be configured to perform the functions described herein. In any event, CNA 200 may be implemented more generally as a computing device, such as a server, personal computer, computer workstation, or other type of computing device, including computing devices used as user equipment and/or wireless local area networks. Regardless of the manner in which the CNA 200 is implemented, the apparatus of the example embodiment may be configured as shown in FIG. 2 to include, be associated with, or otherwise communicate with the processing circuitry 208 , the processing circuitry 208 . Including, for example, a processor 202 and a memory device 204 and in some embodiments and/or a communication interface 206 .

In processing circuitry 208 , processor 202 (and/or a co-processor or auxiliary processor or any other circuitry otherwise associated with the processor) may communicate with memory device 204 via a bus to communicate with the components of CNA 200 transfer information between. A memory device may include, for example, one or more volatile and/or nonvolatile memories. In other words, for example, a memory device may be an electronic storage device (eg, a computer-readable storage medium) that includes a gate configured to store data (eg, bits of data) that can be retrieved by a machine (eg, a computing device such as a processor). ). A memory device may be configured to store information, data, content, applications, instructions, etc., to enable an apparatus to perform various functions according to example embodiments of the present invention. For example, the memory device may be configured to buffer input data for processing by the processor. Additionally or alternatively, the memory device may be configured to store instructions for execution by the processor.

In some embodiments, CNA 200 may be implemented in various computing devices as described above. However, in some embodiments, the apparatus may be implemented as a chip or chip set. In other words, the device may include one or more physical packages (eg, chips), including materials, components, and/or wires on a structural assembly (eg, a substrate). Structural components may provide physical strength, dimensional retention, and/or confinement of electrical interaction for component circuitry included thereon. Thus, in some cases, the apparatus may be configured to implement embodiments of the invention on a single chip or as a single "system on a chip." Thus, in some cases, a chip or chipset may constitute means for performing one or more operations to provide the functions described herein.

The processor 202 may be implemented in a number of different ways. For example, a processor may be implemented as various hardware processing devices (such as co-processors, microprocessors, controllers, digital signal processors (DSPs), processing elements with or without accompanying DSPs, or individual components including integrated circuits One or more of a variety of other circuitry (eg, ASIC (application specific integrated circuit), FPGA (field programmable gate array), microcontroller unit (MCU), hardware accelerator, special purpose computer chip, etc.). Thus, in some embodiments, a processor may include one or more processing cores configured to execute independently. A multi-core processor enables multiprocessing within a single physical package. Additionally or alternatively, a processor may include one or more processors configured in series via a bus to enable independent execution of instructions, pipelining, and/or multithreading.

In an example embodiment, the processor 202 may be configured to execute instructions stored in the memory device 204 or accessible to the processor. Alternatively or additionally, the processor may be configured to perform hard-coded functions. Thus, whether configured by hardware or software methods or by a combination thereof, a processor may represent an entity (eg, physically embodied in circuitry) capable of performing operations according to embodiments of the present disclosure when correspondingly configured. Thus, for example, when the processor is implemented as an ASIC, FPGA, or the like, the processor may be specifically configured as hardware for performing the operations described herein. Alternatively, as another example, when a processor is implemented as an executor of instructions, the instructions may specifically configure the processor to perform the algorithms and/or operations described herein when the instructions are executed. However, in some cases, the processor may be a processor of a particular device (eg, an encoder and/or a decoder) that is configured to be further configured by instructions for performing the algorithms and/or operations described herein. A processor is configured to operate embodiments of the present invention. The processor may include, among other things, a clock, an arithmetic logic unit (ALU), and logic gates configured to support the operation of the processor.

In embodiments that include communication interface 206, the communication interface may be any apparatus, such as a device or circuitry implemented in hardware or a combination of hardware and software, configured to communicate from/to a network and/or with CNA 200 Any other device or module (such as NF, NRF, UE, radio access network, core network service, application server/function, database or other storage device, etc.) In this regard, for example, the communication interface may include an antenna (or antennas) and supporting hardware and/or software for enabling communication with the wireless communication network. Additionally or alternatively, the communication interface may include circuitry for interacting with the antenna(s) to cause transmission of signals via the antenna(s) or to process reception of signals received via the antenna(s). In some environments, the communication interface may alternatively or additionally support wired communication. Thus, for example, the communication interface may include a communication modem and/or other hardware/software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB), or other mechanisms. In some embodiments, session management functions may include 5GC session management functions for any suitable CUPS architecture, such as for Gateway GPRS Support Node (GGSN-C), TWAG-C, BNG-CUPS, N4, Sxa, Sxb , Sxc, Evolved Packet Core (EPC) SWG-C, EPC PGW-C, EPC TDF-C, etc.

In some embodiments, core network apparatus 200 may represent user equipment configured to connect to other core network entities or network equipment. In some embodiments, the user equipment may comprise a mobile telephone (cellular telephone) or the like.

As shown, apparatus 200 may include a processor 202 in communication with memory 204 and configured to provide signals to and receive signals from communication interface 206 . In some embodiments, the communication interface 206 may include a transmitter and a receiver. In some embodiments, the processor 202 may be configured to control, at least in part, the functionality of the apparatus 200 . In some embodiments, the processor 202 may be configured to control the functions of the transmitter and receiver through control signaling via electrical leads to the transmitter and receiver. Likewise, processor 202 may be configured to control other elements of apparatus 200 by implementing control signaling via electrical leads connecting processor 202 to other elements, such as display or memory 204 . The processor 202 may be implemented, for example, in a variety of ways, including circuitry, at least one processing core, one or more microprocessors with accompanying digital signal processor(s), one without accompanying digital signal processor(s), or Multiple processors, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuitry, one or more computers, various other processing elements (including integrated circuits (eg, Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA), etc.)), or some combination thereof. Thus, although shown in FIG. 2 as a single processor, in some example embodiments, processor 202 may include multiple processors or processing cores.

The apparatus 200 is capable of operating with one or more air interface standards, communication protocols, modulation types, access types, and the like. The signals sent and received by the processor 202 may include signaling information conforming to the air interface standard of the applicable cellular system and/or any number of different wired or wireless network technologies, including but not limited to Wi-Fi, wireless local access network ( WLAN) technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, 802.3, ADSL, DOCSIS, etc. Additionally, these signals may include speech data, user-generated data, user-requested data, and the like.

For example, apparatus 200 and/or a cellular modem therein can operate according to various first generation (1G) communication protocols, second generation (2G or 2.5G) communication protocols, third generation (3G) communication protocols , Fourth Generation (4G) communication protocols, Fifth Generation (5G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (eg, Session Initiation Protocol (SIP), etc.). For example, device 10 may be capable of operating in accordance with 2G wireless communication protocols IS-136, Time Division Multiple Access TDMA, Global System for Mobile Communications GSM, IS-95, Code Division Multiple Access CDMA, and the like. Furthermore, for example, the device 10 is capable of operating in accordance with the 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), and the like. Furthermore, for example, apparatus 200 is capable of operating in accordance with 3G wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division Synchronous Code Division Multiple Access (TD) -SCDMA) etc. Additionally, apparatus 200 is capable of operating in accordance with 3.9G wireless communication protocols such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and the like. Additionally, for example, apparatus 200 is capable of operating in accordance with 4G wireless communication protocols (such as LTE-Advanced), 5G, etc., and similar wireless communication protocols that may be developed subsequently. In some embodiments, apparatus 200 is capable of being in accordance with or within the framework of any suitable Control and User Plane Separation (CUPS) architecture (such as Gateway GPRS Support Node (GGSN-C), Trusted Wireless Access Gateway (TWAG-C) ), Broadband Network Gateway (BNG), N4, Sxa, Sxb, Sxc, Evolved Packet Core (EPC) SWG-C, EPC PGW-C, EPC TDF-C, etc.).

It should be appreciated that the processor 202 may include circuitry for implementing the audio/video and logic functions of the apparatus 200 . For example, the processor 202 may include a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, and the like. The control and signal processing functions of the apparatus 200 may be distributed among these devices according to their respective capabilities. The processor 202 may also include an internal voice coder (VC), an internal data modem (DM), and the like. Additionally, the processor 202 may include functionality to operate one or more software programs, which may be stored in the memory 204 . Generally, the processor 202 and software instructions stored in the memory 206 may be configured to cause the apparatus 200 to perform actions. For example, the processor 202 can operate a connectivity program, such as a web browser. The connectivity program may allow the device 200 to send and receive network content, such as location-based content, according to protocols such as Wireless Application Protocol, WAP, Hypertext Transfer Protocol, HTTP, and the like.

The apparatus 200 may also include a user interface including, for example, a headset or speaker, a ringer, a microphone, a display, a user input interface, etc., which may be operatively coupled to the processor 202 . As described above, the display may include a touch-sensitive display, where a user may touch and/or make gestures to make selections, enter values, and the like. The processor 202 may also include user interface circuitry configured to control at least some functions of one or more elements of the user interface, such as speakers, ringers, microphones, displays, and the like. The processor 202 and/or user interface circuitry that includes the processor 202 may be configured to store data in a memory 204 (eg, volatile memory, non-volatile memory, devices including them, etc.) that are accessible by the processor 202. ) on computer program instructions (eg, software and/or firmware) to control one or more functions of one or more elements of the user interface. The apparatus 200 may include a battery for powering various circuits associated with the mobile terminal, eg, circuits for providing mechanical vibration as a detectable output. The user input interface may include a device that allows the apparatus 200 to receive data, such as a keypad (eg, a virtual keyboard presented on a display or a keyboard coupled to the outside), or the like.

As shown in FIG. 2 , apparatus 200 may also include one or more mechanisms for sharing and/or obtaining data, as shown by communication interface 206 . For example, the communication interface 206 of the apparatus 200 may include a short-range radio frequency (RF) transceiver and/or an interrogator, and thus may share data with and/or obtain data from the electronic device in accordance with RF techniques. Device 200 may include other short-range transceivers, such as infrared (IR) transceivers, Bluetooth ^™ (BT) transceivers operating using Bluetooth ^™ wireless technology, wireless Universal Serial Bus (USB) transceivers, Bluetooth ^™ low energy transceivers, ZigBee transceivers, ANT transceivers, cellular device-to-device transceivers, wireless local area network link transceivers, and/or any other short-range radio technology. The apparatus 200, particularly the short-range transceiver, is capable of transmitting data to and/or receiving data from electronic devices in the vicinity of the apparatus, such as within about 10 meters. The device 200 including a Wi-Fi or wireless local area network modem may also be configured according to various wireless network technologies (including 6LoWpan, Wi-Fi, Wi-Fi low power, WLAN technologies (such as IEEE 802.11 technology, IEEE 802.15 technology, IEEE 802.16 technology), etc. ) transmit and/or receive data from an electronic device.

The apparatus 200 may include other memory, such as Subscriber Identity Module (SIM), Removable User Identity Module (R-UIM), eUICC, UICC, etc., which may store information elements related to mobile subscribers. In addition to the SIM, the device 200 may include other removable and/or fixed memory. Device 200 may include volatile memory and/or non-volatile memory, which may form part or all of memory 204 , or may be separate memory within or connected to device 200 . For example, volatile memory may include random access memory (RAM), including dynamic and/or static RAM, on-chip or off-chip cache memory, and the like. Non-volatile memory that may be embedded and/or removable may include, for example, read-only memory, flash memory, magnetic storage devices such as hard disks, floppy disk drives, magnetic tape, optical disk drives and/or media, non-volatile random access memory (NVRAM), etc. Like volatile memory, non-volatile memory may include a cache area for temporarily storing data. At least a portion of volatile and/or nonvolatile memory may be embedded in processor 202 . The memory may store one or more software programs, instructions, information, data, etc. that may be used by the apparatus to perform the operations disclosed herein. Alternatively or additionally, apparatus 200 may be configured to cause the operations disclosed herein with respect to base stations, WLAN access points, network nodes including UEs, and the like.

The memory may include an identifier capable of uniquely identifying the apparatus 200, such as an International Mobile Equipment Identity (IMEI) code. The memory may include an identifier capable of uniquely identifying the apparatus 200, such as an International Mobile Equipment Identity (IMEI) code. In example embodiments, the processor 202 may be configured using computer code stored in memory, and/or configured to provide the operations disclosed herein with respect to base stations, WLAN access points, network nodes including UEs, and the like. Likewise, the apparatus 200 may be configured as any other component or network device from the core network.

Some of the embodiments disclosed herein may be implemented in software, hardware, application logic or a combination of software, hardware and application logic. For example, software, application logic, and/or hardware may reside on memory 204, control device 202, or electronic components. In some example embodiments, application logic, software, or a set of instructions is maintained on any of a variety of conventional computer-readable media. In the context of this document, a "computer-readable medium" can be one that can contain, store, communicate, propagate, or transmit instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer or data processor circuitry Any non-transitory medium, an example of which is depicted in FIG. 2, a computer-readable medium may include a non-transitory computer-readable storage medium, which may be a system, apparatus, or device that may contain or store instructions for execution of the instructions (such as computer) used in or in conjunction with any medium.

Without limiting in any way the scope, interpretation, or application of the claims presented below, a technical effect of one or more of the example embodiments disclosed herein may be an improved user equipment or network equipment configuration. Accordingly, any embodiment of a method, system, method, apparatus, apparatus, or computer program described or illustrated herein is understood to include any or all components, functions, elements, or steps of any other embodiment such that any method can be implemented by the apparatus 200 or by any other suitable system or device, and as such, may be executed in accordance with computer program code contemplated within the scope of this disclosure.

In some embodiments, it may be helpful for either or both of the control plane entity or the user plane entity to bundle messages (such as PCFP messages) between them. Such bundling may be supported by control plane functions and/or user plane functions. Such bundling may be used if both the control plane function and the user plane function support it, e.g. if both the control plane function and the user plane function indicate support for bundling of PCFP messages into a single datagram, as in Aug 16, 2019 as described in clauses 8.2.25 and 8.2.58 of the 3GPP CT WG4 Change Request filed on , the entire contents of which are incorporated herein by reference for all purposes. For example, in some embodiments, if both the control plane function and the user plane function indicate support for bundling PCFP messages into a single datagram during PFCP association setup or update procedures, such PFCP messages may be implemented into a single datagram The use of bundles of datagrams.

For example, such bundling of PFCP messages can reduce computational complexity and bandwidth requirements since current approaches are to process each PFCP message individually, even if all PFCP messages are intended for a single recipient, such as a single control plane entity or a single user plane entity. According to the methods disclosed herein, there are efficiencies associated with bundling requests, but there is currently no mechanism according to current 3GPP or other standards for performing such bundling while also indicating to intended recipients of such datagrams carrying bundled PFCP messages Include multiple PFCP messages. Under the current method, even if multiple PFCP messages are bundled and sent to one of the control plane entity or the user plane entity, the receiver will not understand that the received datagram carries multiple PFCP messages.

However, in some embodiments, requirements may apply to how bundling is performed. For example, in some embodiments, several PFCP session related request and/or response messages related to the same PFCP session or different PFCP sessions handled by the same peer PFCP entity (eg, the peer's F-SEID has the same IP address) , or the IP address of a PFCP session establishment request with the same peer) when sent to that peer PFCP entity, may be bundled together as specified in clause 7.2.1A of the 8/16/2019 Change Request above in a single UDP/IP packet. In some embodiments, the PFCP messages may be independently bundled to the PFCP entity of the user plane function or the control plane function.

By bundling multiple PFCP session related messages (for the same peer IP address) in one UDP/IP packet, significant performance improvements and enhanced scalability can be achieved (e.g. due to reduced packetization on N4 , number of packets exchanged and processed, CPU and memory costs are reduced).

In some embodiments, example use cases may include (1) bundling PFCP session related messages for the same UE: For UEs with multiple PDN connections/PDU sessions, the communication between (E)CM-IDLE and (E)CM-CONNECTED The transition results in sending many PFCP Session Modification Request messages to request the UPF to forward or buffer DL traffic. (2) Binding PFCP session related messages from different UEs handled by the same peer PFCP entity. In some embodiments, the bundling of PFCP session related messages has no impact on existing PFCP procedures, eg, each PFCP session related message is sent with its normal header and processed as currently specified by the PFCP protocol. Binding independently applies to PFCP session related messages sent from the CP function to the UP function and vice versa.

In some embodiments, the PFCP message binding process (which may be optional, but typically results in significant performance improvements and enhanced scalability) is defined to be able to bind multiple PFCP session related messages in a single in UDP/IP packets.

PFCP message binding

PFCP message bundling is an optional process that can be supported by the CP function and the UP function. PFCP message bundling can be used if both the CP function and the UP function indicate that the corresponding feature is supported during PFCP association establishment or update (see 3GPP TSG-CT WG4 meeting in Wroclaw, Poland, 26-30 August 2019 Items 8.2.25 and 8.2.58 of 29.244 CR 0285 of #93, the entire disclosures of which are incorporated herein by reference). If so, the following requirements shall apply.

Several PFCP session related request and/or response messages related to the same PFCP session or different PFCP sessions handled by the same peer PFCP entity (i.e., the peer's F-SEID has the same IP address, or has the same peer's F-SEID The IP address of the PFCP session establishment request), when sent to the peer PFCP entity, may be bundled together in a single UDP/IP packet as specified in Section 7.2.1A. PFCP messages can be independently bound to UP-function or CP-function PFCP entities.

If the CP function bundles a small number of PFCP session related requests in one UDP/IP packet sent to the UP function, the UP function may return responses in separate UDP/IP packets, or it may bundle some responses with other PFCP session related messages together.

Bundling PFCP messages in a single UDP/IP packet can improve performance and scalability (reduced CPU and memory costs due to reduced number of packets to be packetized, switched and processed on N4).

PFCP session related messages handled by different peer PFCP entities (ie, peers' F-SEIDs with different IP addresses) should not be bundled together. PFCP node related messages should also not be bundled.

The procedures specified in the rest of this specification shall apply to each PFCP message bundled in a UDP/IP packet as if the PFCP message were sent in its own individual UDP/IP packet, i.e., PFCP message bundling shall not apply to PFCP The agreement produces any changes other than those described in this section.

Each PFCP message bundled in a single UDP/IP packet has its own sequence number. In addition, if the UDP/IP packet carrying the bundled PFCP message is lost, the retransmitted PFCP message does not need to be bundled in the way it was originally sent.

message format

A typical format of a PFCP message is depicted in Figure 3.

In some embodiments, the PFCP message shall contain a PFCP message header and may contain subsequent information element(s) depending on the message type.

PFCP messages bundled in a UDP/IP packet

When applying PFCP message binding (see Section 6.x), PFCP messages shall be bound in a UDP/IP packet, as shown in Figure 4.

Each bundled PFCP message shall contain its PFCP message header and may contain subsequent information element(s) depending on the message type.

The "FO" (following) flag in the PFCP message header of each PFCP message (except the last PFCP message) bundled in a UDP/IP packet shall be set to "1" to indicate that another A PFCP message.

message header

PFCP messages use variable length headers. The message header length shall be a multiple of 4 octets. Figure 5 shows the format of a PFCP header according to one embodiment.

In some embodiments,

i. If S=0, the SEID field is not present, k=0, m=0 and n=5;

ii. If S=1, the SEID field is present, k=1, m=5 and n=13.

The use of the PFCP header is defined in clause 7.2.2.4 of 29.244CR 0285

1 bit in an octet shall be encoded as follows:

i. Bit 1 represents the SEID flag (T).

ii. Bit 2 represents the "MP" flag (see clause 7.2.2.4.1 of 29.244CR 0285).

iii. Bit 3 represents the "FO" flag (see clause 7.2.2.4.1 of 29.244CR 0285).

iv. Bits 3, 4 to 5 are spare, the sender should set them to "0" and the receiving entity should ignore them.

v. Bits 6-8 represent the version field.

PFCP header for node related messages

The PFCP message header for Node Related Messages SHOULD NOT contain the SEID field, but SHOULD contain the Sequence Number field followed by a spare octet, as shown in Figure 6, the spare bits SHOULD be set to zero by the sender, and SHOULD be ignored by the receiver. For Version Not Supported Response messages, the sequence number can be set to any number and SHOULD be ignored by the receiver.

PFCP header for session related messages

PFCP message headers for Session Related Messages SHOULD contain SEID and Sequence Number fields followed by a spare octet. The PFCP header is depicted in Figure 7. Spare bits shall be set to zero by the sender and shall be ignored by the receiver.

Use of PFCP headers

The format of the PFCP header is specified in section 7.2.2 of 29.244CR 0285.

The use of the PFCP header shall be defined as follows.

The first octet of the header is used as follows:

i. Bit 1 represents the "S" flag, which indicates whether the SEID field is present in the PFCP header. If the "S" flag is set to 0, the SEID field shall not be present in the PFCP header. If the "S" flag is set to 1, the SEID field shall follow the length field, in octets 5 through 12. The value of the "S" flag shall be set to "1" in all PFCP messages except node related messages.

ii. Bit 2 represents the "MP" flag. If the "MP" flag is set to "1", then bits 8 to 5 of octet 16 shall indicate the message priority.

iii. Bit 3 represents the "FO" (following) flag. If the "FO" flag is set to "1", another PFCP message will be followed in the UDP/IP packet (see Sections 6.x and 7.2.1A of 29.244CR 0285).

iv. Bit 4 is a spare bit. The sending entity SHOULD set it to '0' and the receiving entity SHOULD ignore it.

v. Bit 5 is a spare bit. The sending entity SHOULD set it to '0' and the receiving entity SHOULD ignore it.

vi. Bits 6 to 8 representing the PFCP version shall be set to decimal 1 ("001"). The use of fields in octets 2-n of the header shall be specified as follows.

i. Octet 2 represents the message type field, which should be set to a unique value for each type of control plane message. The message type values are specified in Table 7.3-1, "Message Types".

ii. Octets 3 to 4 represent the message length field. This field shall represent the length of the message in octets, excluding the mandatory part of the PFCP header (first 4 octets). SEID (if present) and sequence number shall be included in the length count. The format of the length field of the information element is specified in Section 8.2 "Information element format".

iii. When S=1, octets 5 to 12 represent the Session Endpoint Identifier (SEID) field. This field shall unambiguously identify the session endpoint in the receiving Packet Forward Control entity. The session endpoint identifier is set by the sending entity in the PFCP header of all control plane messages to the SEID value provided by the corresponding receiving entity (CP or UP function). If the peer's SEID is not available, the SEID field shall be present in the PFCP header, but its value shall be set to "0", "Condition for sending SEID=0 in PFCP header".

Regardless of whether the source IP address of the request message and the IP destination address provided by the receiving entity for subsequent request messages are the same, the SEID in the PFCP header of the message is set to the SEID value provided by the corresponding receiving entity.

i. Octets 13 to 15 represent the PFCP sequence number field.

UP features

The UP Function Features IE indicates the features supported by the UP function. Its encoding is shown in Figure 8 and Figure 9.

The UP Functional Feature IE takes the form of a bitmask, where each bit set indicates support for the corresponding feature. The receiver should ignore the spare bits. The same bitmask is defined for all PFCP interfaces.

Table 1 details the characteristics defined on the PFCP interface and the interface to which it is applied.

Table 1

Control Plane Features

The CP Function Features IE indicates the features supported by the CP function. Only features that have an impact on the (system-wide) UP functional behavior are signaled in this IE. Its encoding is shown in Figure 10 and Figure 11.

The CP Capability Feature IE takes the form of a bitmask, where each bitset indicates support for the corresponding feature. The receiver should ignore the spare bits. The same bitmask is defined for all PFCP interfaces.

Table 2 details the characteristics defined on the PFCP interface and the interface to which it is applied.

Table 2

In some embodiments, if the control plane function bundles multiple PFCP session related requests in one UDP/IP packet, as shown in Figure 4, it may send the UDP/IP packet bundle to the user plane function, the user plane function The responses may be returned in one or more separate UDP/IP packets, or it may bundle some responses with other PFCP session related responses or other messages. In some embodiments, bundling PFCP messages into a single UDP/IP packet can enhance performance and scalability (eg, CPU and memory costs due to reduced number of packets to be packetized, switched, and processed on N4) reduce). Figure 5 shows the header of a PFCP message in which bit 3 of octet 1 (usually "spare") is now occupied by the follow-up (FO) flag to indicate to the recipient of the datagram that the datagram includes more than A control message (eg, PFCP message).

Furthermore, as shown in Figure 8, the user plane function may be configured to support certain features or mechanisms, such as bundling messages in datagrams, which may be indicated in the header of the message between the user plane function and the control plane function. Similar messages may be communicated between the control plane function and the user plane function to indicate the capabilities and configuration of the control plane function in order to bundle control messages in a single datagram. For example, as shown in FIG. 9, certain messages during an association establishment or update procedure may include a "BUNDL" flag indicating support for PFCP message bundling, eg, for Sxa, Sxb, Sxc or N4 interfaces. Similar messages for control plane functions may be generated and sent, as shown in Figures 10 and 11, to indicate to the recipient of the message (eg, user plane function) that the control plane function is capable of receiving datagrams carrying bundled PFCP messages and the like. For example, in the 5G network shown in Figure 1, the apparatus of Figure 2 can be used to exchange capabilities between the SMF and UPF, knowing that both nodes support the capability so that any of the various entities can use the capability mechanism.

In some embodiments, PFCP session related messages handled by different peer PFCP entities (eg, peers with F-SEIDs with different IP addresses) cannot or should not be bundled together. In some embodiments, PFCP node related messages should also not be bundled.

In some embodiments, the procedures specified in the remainder of the 3GPP Release 16 specification shall apply to each PFCP message bundled in a UDP/IP packet as if the PFCP message were sent in its own individual UDP/IP packet, For example, PFCP message binding should not cause any changes to the PFCP protocol (other than what is described in this disclosure).

In some embodiments, each PFCP message bundled in a single UDP/IP packet may have its own sequence number in the bundle. In some embodiments, if the UDP/IP packet carrying the bundled PFCP message is lost, the retransmission of the PFCP message need not be bundled in the same way as originally sent.

Referring now to FIG. 11, method 10 may be performed by an apparatus, such as apparatus 200 shown in FIG. 2, or the like. For example, an apparatus may be provided that includes at least one processor and at least one memory including computer program code configured to perform the method 10 . In some embodiments, the method may include, at 11, determining whether more than one control protocol message should be sent from a control plane entity to a user plane entity or from the user plane entity to the control plane entity. In some embodiments, the method 10 may further include, at 12, determining whether both the control plane entity and the user plane entity support sending and receiving a single datagram carrying the more than one control protocol message. In some embodiments, method 10 may further include, at 13, extending a header of each of the more than one control protocol message to indicate that a single datagram carries the more than one control protocol message. In some embodiments, method 10 may further include, at 14, combining one or more message types and corresponding message elements of the more than one control protocol message into the single datagram. In some embodiments, method 10 may further include, at 15, causing the control plane entity to send the single datagram carrying the more than one control protocol message to the user plane entity or causing the user plane entity to send the single datagram carrying the more than one control protocol message to the user plane entity. The control plane entity sends the single datagram carrying the more than one control protocol message.

In some embodiments, the user plane entity includes a user plane function and the control plane entity includes a session management function. In some embodiments, the session management functions may include 5GC session management functions and/or Evolved Packet Core (EPC) (SWG-C), (PGW-C), (TDF-C), and the like. In some embodiments, the control protocol message comprises a Packet Forwarding Control Protocol (PFCP) message. In some embodiments, the method may further include extending a header of each of the more than one control protocol message to include a follow-up flag to indicate that a single datagram carries the more than one control protocol message. In some embodiments, the single control protocol message includes being configured to be packetized over an N4 interface in a Fifth Generation Core (5GC) network or over an Sxa, Sxb, or Sxc interface in an Evolved Packet Core (EPC) network , a single User Datagram/Internet Protocol (UDP/IP) packet that is exchanged and processed. In some embodiments, the more than one control protocol message carried in a single control protocol message is a control plane request or response related to the same PFCP session or different PFCP sessions handled by the same peer PFCP entity.

The above-described aspects and features may be implemented in systems, apparatus, methods and/or articles according to a desired configuration. The details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the detailed description. The features and advantages of the subject matter described herein will be apparent from the description and drawings, and from the claims.

The subject matter described herein can be implemented in systems, apparatus, methods and/or articles according to the desired configuration. For example, the control plane and user plane entities (or one or more components thereof or one or more components associated therewith) and/or the processes described herein may be implemented using one or more of the following: Executing a program Code processors, application specific integrated circuits (ASICs), digital signal processors (DSPs), embedded processors, field programmable gate arrays (FPGAs), and/or combinations thereof. These various implementations may include implementations in one or more computer programs executable and/or interpretable on a programmable system including at least one programmable processor, which may be a special purpose Or generally, coupled to receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device. These computer programs (also referred to as programs, software, software applications, applications, components, program code, or code) may include machine instructions for programmable processors, and may be written in high-level procedural and/or object-oriented programming languages, and / or assembly/machine language implementation. As used herein, the term "computer-readable medium" refers to any computer program product, machine-readable medium, computer-readable storage medium, apparatus and/or device for providing machine instructions and/or data to a programmable processor A device (eg, a magnetic disk, an optical disk, a memory, a programmable logic device (PLD)), including a machine-readable medium that receives machine instructions. Similarly, systems are also described herein that can include a processor and a memory coupled to the processor. The memory may include one or more programs that cause the processor to perform one or more operations described herein.

While some variations have been described in detail above, other modifications or additions are possible. In particular, other features and/or variations may be provided in addition to those set forth herein. Furthermore, the above-described implementations may be directed to various combinations and sub-combinations of the disclosed features and/or combinations and sub-combinations of several other features disclosed above. Other embodiments may be within the scope of the following claims.

If desired, the various functions discussed herein may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the above-described functions may be optional or may be combined. Although aspects of some embodiments are set forth in the independent claims, other aspects of some embodiments include other combinations of features from the described embodiments and/or the dependent claims and features of the independent claims, and not only is a combination expressly listed in the claims. It should also be noted here that while example embodiments have been described above, these descriptions should not be considered limiting. Rather, several changes and modifications may be made without departing from the scope of some embodiments as defined in the appended claims. Other embodiments may be within the scope of the following claims. The word "based on" includes "based on at least". Use of the phrase "such as" means "for example" unless stated otherwise.

It should be understood that the terms "user entity" and "user equipment" are intended to encompass any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device or a portable web browser. It should also be understood that the terms "user entity" and "user equipment" are intended to encompass any suitable type of non-portable user equipment, such as television receivers, desktop data processing equipment or set-top boxes.

In general, the various embodiments of the present invention may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software executed by a controller, microprocessor or other computing device, although the invention is not limited thereto. Although various aspects of the invention may be illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it is well understood that, by way of non-limiting example, the blocks, apparatus, systems, techniques or methods described herein may Implemented in hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controllers or other computing devices, or some combination thereof.

Embodiments of the present invention may be implemented by computer software, such as in a processor entity, executable by a data processor of a mobile device, or by hardware, or by a combination of software and hardware. Furthermore, in this regard, it should be noted that any block of the logic flow in the figures may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. Software may be stored on physical media such as memory chips or memory blocks implemented within a processor, magnetic media such as hard disks or floppy disks, optical media such as DVD and its data variant CD, and the like. The memory may be of any type appropriate to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor may be of any type suitable for the local technical environment and may include one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture, As a non-limiting example.

For example, examples of embodiments provided herein include methods, apparatus, and computer program products provided for Packet Forwarding Control Protocol (PFCP) message bundling.

In some example embodiments, an apparatus may be provided that includes at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to at least : determine whether more than one control protocol message should be sent from the control plane entity to the user plane entity or from the user plane entity to the control plane entity; determine whether both the control plane entity and the user plane entity support sending and receiving the more than one a single datagram of a control protocol message; extending the header of each of the more than one control protocol message to indicate that a single datagram carries the more than one control protocol message; converting one or more of the more than one control protocol message combining a plurality of message types and corresponding message elements into the single datagram; and causing the control plane entity to send the single datagram carrying the more than one control protocol message to the user plane entity or causing the user plane The entity sends the single datagram carrying the more than one control protocol message to the control plane entity. In some embodiments, the user plane entity includes a user plane function and the control plane entity includes a session management function. In some embodiments, the session management functions may include 5GC session management functions and/or Evolved Packet Core (EPC) (SWG-C), (PGW-C), (TDF-C), and the like. In some embodiments, the control protocol message comprises a Packet Forwarding Control Protocol (PFCP) message. In some embodiments, at least one memory and computer program code are configured to, with at least one processor, cause the apparatus to at least: extend a header of each of the more than one control protocol messages to include a follow-up flag to indicate A single datagram carries the more than one control protocol message. In some embodiments, the single control protocol message includes being configured to be packetized over an N4 interface in a Fifth Generation Core (5GC) network or over an Sxa, Sxb, or Sxc interface in an Evolved Packet Core (EPC) network , exchange and process a single UDP/IP packet. In some embodiments, the more than one control protocol message carried in a single control protocol message is a control plane request or response related to the same PFCP session or different PFCP sessions handled by the same peer PFCP entity.

According to another embodiment, a method is provided, the method comprising determining whether more than one control protocol message should be sent from a control plane entity to a user plane entity or from the user plane entity to the control plane entity; determining whether the control plane Both the entity and the user plane entity support sending and receiving a single datagram carrying the more than one control protocol message; extending the header of each control protocol message in the more than one control protocol message to indicate that a single datagram carries the more than one a control protocol message; combining one or more message types and corresponding message elements of the more than one control protocol message into the single datagram; and causing the control plane entity to send a transmission to the user plane entity that carries the more than one The single datagram of a control protocol message or causing the user plane entity to send the single datagram carrying the more than one control protocol message to the control plane entity. In some embodiments, the user plane entity includes a user plane function and the control plane entity includes a session management function. In some embodiments, the session management functions may include 5GC session management functions and/or Evolved Packet Core (EPC) (SWG-C), (PGW-C), (TDF-C), and the like. In some embodiments, the control protocol message comprises a Packet Forwarding Control Protocol (PFCP) message. In some embodiments, the method may further include extending a header of each of the more than one control protocol message to include a follow-up flag to indicate that a single datagram carries the more than one control protocol message. In some embodiments, the single control protocol message includes being configured to be packetized over an N4 interface in a Fifth Generation Core (5GC) network or over an Sxa, Sxb, or Sxc interface in an Evolved Packet Core (EPC) network , a single User Datagram/Internet Protocol (UDP/IP) packet that is exchanged and processed. In some embodiments, the more than one control protocol message carried in a single control protocol message is a control plane request or response related to the same PFCP session or different PFCP sessions handled by the same peer PFCP entity.

According to yet another embodiment, there is provided an apparatus comprising means for determining whether more than one control protocol message should be sent from a control plane entity to a user plane entity or from the user plane entity to the control plane entity, such as the apparatus comprising one or more processors and one or more memories comprising program code; for determining whether both a control plane entity and a user plane entity support sending and receiving a single datagram carrying the more than one control protocol message A component for extending the header of each control protocol message in the more than one control protocol message to indicate that a single datagram carries the more than one control protocol message; for converting the more than one control protocol message means for combining one or more message types and corresponding message elements into said single datagram; or for causing said control plane entity to send said single datagram carrying said more than one control protocol message to said user plane entity or means for causing the user plane entity to send the single datagram carrying the more than one control protocol message to the control plane entity. In some embodiments, the user plane entity includes a user plane function and the control plane entity includes a session management function. In some embodiments, the session management functions may include 5GC session management functions and/or Evolved Packet Core (EPC) (SWG-C), (PGW-C), (TDF-C), and the like. In some embodiments, the control protocol message comprises a Packet Forwarding Control Protocol (PFCP) message. In some embodiments, the apparatus may further comprise means for extending a header of each of the more than one control protocol message to include a follow-up flag to indicate that a single datagram carries the more than one control protocol message . In some embodiments, the single control protocol message includes being configured to be packetized over an N4 interface in a Fifth Generation Core (5GC) network or over an Sxa, Sxb, or Sxc interface in an Evolved Packet Core (EPC) network , exchange and process a single UDP/IP packet. In some embodiments, the more than one control protocol message carried in a single control protocol message is a control plane request or response related to the same PFCP session or different PFCP sessions handled by the same peer PFCP entity.

According to yet another embodiment, there is provided a computer-readable medium, such as a non-transitory computer-readable medium including program code that, when executed, causes operations including: the user plane entity still sends more than one control protocol message from the user plane entity to the control plane entity; determining whether both the control plane entity and the user plane entity support sending and receiving a single datagram carrying the more than one control protocol message; extending the header of each of the more than one control protocol message to indicate that a single datagram carries the more than one control protocol message; combining one or more message types and corresponding message elements of the more than one control protocol message combining into said single datagram; and causing said control plane entity to send said single datagram carrying said more than one control protocol message to said user plane entity or causing said user plane entity to send said control plane entity carrying the single datagram of the more than one control protocol message. In some embodiments, the user plane entity includes a user plane function and the control plane entity includes a session management function. In some embodiments, the session management functions may include 5GC session management functions and/or Evolved Packet Core (EPC) (SWG-C), (PGW-C), (TDF-C), and the like. In some embodiments, the control protocol message comprises a Packet Forwarding Control Protocol (PFCP) message. In some embodiments, the program code, when executed, may also cause operations comprising: extending a header of each of the more than one control protocol message to include a follow-up flag to indicate a single datagram bearer The more than one control protocol message. In some embodiments, the single control protocol message includes being configured to be packetized over an N4 interface in a Fifth Generation Core (5GC) network or over an Sxa, Sxb, or Sxc interface in an Evolved Packet Core (EPC) network , exchange and process a single UDP/IP packet. In some embodiments, the more than one control protocol message carried in a single control protocol message is a control plane request or response related to the same PFCP session or different PFCP sessions handled by the same peer PFCP entity.

The above-described aspects and features may be implemented in systems, apparatus, methods and/or articles according to a desired configuration. The details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the description below. The features and advantages of the subject matter described herein will be apparent from the description and drawings, and from the claims. The foregoing description has provided, by way of illustration and non-limiting example, a complete and informative description of the exemplary embodiments of the present invention. However, various modifications and adjustments will become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings of this invention will still fall within the scope of this invention.

Claims (18)

1. A device comprising: means for determining whether more than one control protocol message should be sent from a control plane entity to a user plane entity or from the user plane entity to the control plane entity; means for determining whether both the control plane entity and the user plane entity support sending and receiving a single datagram carrying the more than one control protocol message; means for extending a header of each of the more than one control protocol message to indicate that another control protocol message is followed in the single datagram; means for combining one or more message types and corresponding message elements of the more than one control protocol message into the single datagram; and for causing the control plane entity to send the single datagram carrying the more than one control protocol message to the user plane entity or causing the user plane entity to send the control plane entity to the control plane entity carrying the more than one control protocol message The component of the single datagram of the message. 2. The apparatus of claim 1, wherein the user plane entity includes a user plane function and the control plane entity includes a session management function. 3. The apparatus of any of claims 1 or 2, wherein the control protocol message comprises a Packet Forwarding Control Protocol (PFCP) message. 4. The apparatus of any one of claims 1 to 3, further comprising: means for extending the header of each of the more than one control protocol message to include a follow-up flag to indicate that another control protocol message is followed in the single datagram. 5. The apparatus of any one of claims 1 to 4, wherein the single datagram comprises a single User Datagram/Internet Protocol (UDP/IP) packet, the single User Datagram/Internet Protocol (UDP/ IP) packets are configured to be packetized, switched and processed over the N4 interface in Fifth Generation Core (5GC) networks or over the Sxa interface, Sxb interface or Sxc interface in Evolved Packet Core (EPC) networks. 6. The apparatus of claim 3, wherein the more than one control protocol message carried in a single datagram is a control plane request or response related to the same PFCP session or different PFCP sessions handled by the same peer PFCP entity . 7. A method comprising: determining whether more than one control protocol message should be sent from a control plane entity to a user plane entity or from the user plane entity to the control plane entity; determining whether both the control plane entity and the user plane entity support sending and receiving a single datagram carrying the more than one control protocol message; extending a header of each of the more than one control protocol message to indicate that the single datagram is followed by another control protocol message; combining one or more message types and corresponding message elements of the more than one control protocol message into the single datagram; and causing the control plane entity to send the single datagram carrying the more than one control protocol message to the user plane entity or causing the user plane entity to send to the control plane entity the single datagram carrying the more than one control protocol message the single datagram. 8. The method of claim 7, wherein the user plane entity includes a user plane function and the control plane entity includes a session management function. 9. The method of one of claims 7 or 8, wherein the control protocol message comprises a Packet Forwarding Control Protocol (PFCP) message. 10. The method of any one of claims 7 to 9, further comprising: The header of each of the more than one control protocol message is extended to include a follow-up flag to indicate that another control protocol message is followed in the single datagram. 11. The method of any one of claims 7 to 10, wherein the single datagram comprises a single User Datagram/Internet Protocol (UDP/IP) packet, the single User Datagram/Internet Protocol (UDP/ IP) packets are configured to be packetized, switched and processed over the N4 interface in Fifth Generation Core (5GC) networks or over the Sxa interface, Sxb interface or Sxc interface in Evolved Packet Core (EPC) networks. 12. The method of claim 9, wherein the more than one control protocol message carried in a single datagram is a control plane request or response related to the same PFCP session or different PFCP sessions handled by the same peer PFCP entity . 13. A non-transitory computer-readable medium comprising program code that, when executed, causes operations comprising: determining whether more than one control protocol message should be sent from a control plane entity to a user plane entity or from the user plane entity to the control plane entity; determining whether both the control plane entity and the user plane entity support sending and receiving a single datagram carrying the more than one control protocol message; extending a header of each of the more than one control protocol message to indicate that the single datagram is followed by another control protocol message; combining one or more message types and corresponding message elements of the more than one control protocol message into the single datagram; and causing the control plane entity to send the single datagram carrying the more than one control protocol message to the user plane entity or causing the user plane entity to send to the control plane entity the single datagram carrying the more than one control protocol message the single datagram. 14. The computer-readable medium of claim 13, wherein the user plane entity includes a user plane function and the control plane entity includes a session management function. 15. The computer-readable medium of one of claims 13 or 14, wherein the control protocol message comprises a Packet Forwarding Control Protocol (PFCP) message. 16. The computer-readable medium of any one of claims 13 to 15, wherein the program code, when executed, further causes operations comprising: The header of each of the more than one control protocol message is extended to include a follow-up flag to indicate that another control protocol message is followed in the single datagram. 17. The computer-readable medium of any one of claims 13 to 16, wherein the single datagram comprises a single User Datagram/Internet Protocol (UDP/IP) packet, the single User Datagram/Internet Protocol (UDP/IP) packets are configured to be packetized, switched, and processed over the N4 interface in Fifth Generation Core (5GC) networks or over the Sxa interface, Sxb interface, or Sxc interface in Evolved Packet Core (EPC) networks. 18. The computer-readable medium of claim 15, wherein the more than one control protocol message carried in a single datagram is a control related to the same PFCP session or to different PFCP sessions handled by the same peer PFCP entity Flat request or response.

Images