Apparatus, method and computer program for user plane function control by a group of controllers
By using flags and identifiers that can be controlled by different SMF instances in the SMF group of 5G system, the problem of complexity and inefficiency of protocol session control between SMF and UPF is solved, and efficient load balancing within the SMF group is achieved and service stability.
Patent Information
- Application Number
- CN201980096001.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-05-02
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2039-05-02
AI Technical Summary
In existing 5G systems, there are complexity and inefficiency problems in protocol session control between session management function (SMF) and user plane function (UPF), especially when PFCP session management and load balancing in SMF groups. Causes increased signaling and risk of service interruption.
By introducing flags and identifiers that can be controlled by different SMF instances in the SMF group, any SMF instance in the SMF group allows to manage PFCP sessions, and use IPv4 or IPv6 addresses to indicate preferred or alternate SMF instances to achieve session association, modification and Released requests and responses ensure that there is no service interruption in the event of SMF instance failure or load changes.
Simplifies PFCP session management within SMF groups, reduces signaling complexity and service interruption risks, improves system scalability and load balancing capabilities, and reduces the possibility of service interruption.
Smart Images

Figure CN113785553B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to a method, an apparatus, a system and a computer program, and particularly but not exclusively to user plane function (UPF) control performed by a session management function (SMF) group. Background Art
[0002] A communication system can be viewed as a facility that enables communication sessions between two or more entities such as user terminals, base stations and / or other nodes by providing carriers between the various entities involved in the communication path. For example, a communication system can be provided by means of a communication network and one or more compatible communication devices (also referred to as stations or user equipment) and / or application servers. For example, a communication session may include data communications for carrying communications, such as voice, video, electronic mail (email), text messages, multimedia, content data, time-sensitive network (TSN) streams and / or data in industrial applications, such as critical system messages between actuators and controllers, critical sensor data (such as measurements, video feeds, etc.) toward control systems, etc. Non-limiting examples of the services provided include two-way or multi-way calls, data communications or multimedia services, and access to data network systems such as the Internet.
[0003] In a wireless communication system, at least a portion of a communication session, for example between at least two stations or between at least one station and at least one application server (e.g., for video), occurs over a wireless link. Examples of wireless systems include public land mobile networks (PLMNs) operating based on 3GPP radio standards, such as E-UTRA, New Radio, satellite-based communication systems, and different wireless local networks, such as wireless local area networks (WLANs). Wireless systems can typically be divided into cells and are therefore often referred to as cellular systems.
[0004] A user may access a communication system by means of a suitable communication device or terminal. The user's communication device may be referred to as a user equipment (UE) or user device. The communication device is provided with suitable signal receiving and sending means to enable communication, for example, to enable access to a communication network or to communicate directly with other users. The communication device may access one or more carriers provided by a network (e.g., a base station of a cell) and send and / or receive communications on the one or more carriers.
[0005] The communication system and associated equipment usually operate according to a given standard or specification that sets out what the various entities associated with the system are allowed to do and how it should be achieved. The communication protocols and / or parameters that will be used for the connection are usually also defined. An example of a communication system is UTRAN (3G radio). Other examples of communication systems are the Long Term Evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) based on the E-UTRAN radio access technology, and the so-called 5G system (5GS) including 5G or Next Generation Core (NGC) and 5G access networks based on New Radio (NR) radio access technology. The 5GS including NR is being standardized by the Third Generation Partnership Project (3GPP). Summary of the invention
[0006] In a first aspect, a device is provided, comprising components for performing the following operations: providing first information from a first function instance in a group of first function instances to a second function, the first information comprising an indication that a protocol session between the first function and the second function can be controlled by different instances in the group of first function instances; and receiving a protocol session-related message from the second function at a first function instance in the group of first function instances based on the first information.
[0007] The first function may be a session management function. The second function may be a user plane function. The protocol session may be a packet forwarding control protocol session.
[0008] The apparatus may include means for providing first information during a protocol association process.
[0009] The first information may include at least one of: a fully qualified domain name or identifier associated with the group of first function instances, a flag indicating that the protocol session can be controlled by different instances in the group of first function instances, and an identifier or Internet Protocol address of another first function instance in the group of first function instances.
[0010] The other first function instance may be a backup first function instance.
[0011] The apparatus may include means for providing a request to update or release a protocol session association to any one of the group of first function instances.
[0012] The apparatus may include means for providing the first information in a protocol session establishment or modification request.
[0013] The first information may be included in a control plane fully qualified session identifier.
[0014] The first information may include at least one of: a fully qualified domain name or identifier associated with the group of first function instances, a flag indicating that the protocol session can be controlled by different instances in the group of first function instances, a unique session identifier associated with the group of first function instances, and an identifier or Internet Protocol address of another first function instance in the group of first function instances.
[0015] The another first function instance may be a backup first function instance or a preferred first function instance.
[0016] When the another first functional instance is the preferred first functional instance, the identifier of the another first functional instance may include an IPv4 or IPv6 address.
[0017] The first information may include a null IPv4 or IPv6 address indicating that there is no preferred first function instance.
[0018] The apparatus may include means for providing a request to modify or delete a protocol session to any one of the set of first functional instances.
[0019] The apparatus may include means for providing a request denial to the second function by any one of the set of first function instances, the request denial including an indication of the first function instance in the set of first function instances.
[0020] The apparatus may include means for providing a protocol session-related message to a first functional instance of the set of first functional instances.
[0021] The apparatus may include means for establishing a single protocol association with a second function for any one first function instance in the set of first function instances.
[0022] In a second aspect, a device is provided, comprising components for performing the following operations: receiving first information at a second function from a first function instance in a group of first function instances, the first information comprising an indication that a protocol session between the first function and the second function can be controlled by different instances in the group of first function instances; and providing a protocol session-related message from the second function to a first function instance in the group of first function instances based on the first information.
[0023] The first function may be a session management function. The second function may be a user plane function. The protocol session may be a packet forwarding control protocol session.
[0024] The apparatus may include means for receiving first information in a protocol association procedure, or a protocol session establishment or modification request.
[0025] When the first information is received in a protocol session establishment or modification request, the first information may be included in a control plane fully qualified session identifier.
[0026] The first information may include at least one of: a fully qualified domain name or identifier associated with the group of first function instances, a flag indicating that the protocol session can be controlled by different instances in the group of first function instances, and an identifier or Internet Protocol address of a backup first function instance in the group of first function instances.
[0027] When the first information is received in a protocol session establishment or modification request, the first information may include an IPv4 or IPv6 address, which indicates a preferred first function instance if the IPv4 or IPv6 address is non-empty, and which indicates no preferred first function instance if the IPv4 or IPv6 address is empty.
[0028] The device may include a component for performing the following operations: if the IPv4 or IPv6 address is non-null, providing a protocol session-related message from the second function to the IPv4 or IPv6 address, and if the IPv4 or IPv6 address is null or unresponsive, sending a protocol session-related message to any one of the first function instances in the group of first instances.
[0029] The apparatus may include means for receiving a request to modify a protocol session, or a request to delete a protocol session, or a request to update or release a protocol session association from any one of the set of first function instances.
[0030] The apparatus may include means for triggering a recovery procedure by the second function if a heartbeat procedure with all instances in the set of first function instances fails.
[0031] In a third aspect, a method is provided, comprising: providing first information from a first function instance in a group of first function instances to a second function, the first information comprising an indication that a protocol session between the first function and the second function can be controlled by different instances in the group of first function instances; and based on the first information, receiving a protocol session-related message from the second function at a first function instance in the group of first function instances.
[0032] The first function may be a session management function. The second function may be a user plane function. The protocol session may be a packet forwarding control protocol session.
[0033] The method may include providing first information during a protocol association process.
[0034] The first information may include at least one of: a fully qualified domain name or identifier associated with the group of first function instances, a flag indicating that the protocol session can be controlled by different instances in the group of first function instances, and an identifier or Internet Protocol address of another first function instance in the group of first function instances.
[0035] The other first function instance may be a backup first function instance.
[0036] The method may include: any one of the group of first function instances providing a request to update or release a protocol session association.
[0037] The method may include providing first information in a protocol session establishment or modification request.
[0038] The first information may be included in a control plane fully qualified session identifier.
[0039] The first information may include at least one of: a fully qualified domain name or identifier associated with the group of first function instances, a flag indicating that the protocol session can be controlled by different instances in the group of first function instances, a unique session identifier associated with the group of first function instances, and an identifier or Internet Protocol address of another first function instance in the group of first function instances.
[0040] The another first function instance may be a backup first function instance or a preferred first function instance.
[0041] When the another first functional instance is the preferred first functional instance, the identifier of the another first functional instance may include an IPv4 or IPv6 address.
[0042] The first information may include a null IPv4 or IPv6 address indicating that there is no preferred first function instance.
[0043] The method may include: any one of the group of first function instances providing a request to modify or delete the protocol session.
[0044] The method may include: any one of the group of first function instances providing a request rejection to the second function, the request rejection including an indication of the first function instance in the group of first function instances.
[0045] The method may include providing a protocol session-related message to a first function instance in the group of first function instances.
[0046] The method may include: any one of the group of first function instances establishing a single protocol association with the second function.
[0047] In a fourth aspect, a method is provided, comprising: receiving first information at a second function from a first function instance in a group of first function instances, the first information comprising an indication that a protocol session between the first function and the second function can be controlled by different instances in the group of first function instances; and providing a protocol session-related message from the second function to a first function instance in the group of first function instances based on the first information.
[0048] The first function may be a session management function. The second function may be a user plane function. The protocol session may be a packet forwarding control protocol session.
[0049] The method may include receiving first information in a protocol association procedure, or a protocol session establishment or modification request.
[0050] When the first information is received in a protocol session establishment or modification request, the first information may be included in a control plane fully qualified session identifier.
[0051] The first information may include at least one of: a fully qualified domain name or identifier associated with the group of first function instances, a flag indicating that the protocol session can be controlled by different instances in the group of first function instances, and an identifier or Internet Protocol address of a backup first function instance in the group of first function instances.
[0052] When the first information is received in a protocol session establishment or modification request, the first information may include an IPv4 or IPv6 address, which indicates a preferred first function instance if the IPv4 or IPv6 address is non-empty, and which indicates no preferred first function instance if the IPv4 or IPv6 address is empty.
[0053] The method may include: if the IPv4 or IPv6 address is non-empty, providing a protocol session related message to the IPv4 or IPv6 address from the second function, and if the IPv4 or IPv6 address is empty or unresponsive, sending a protocol session related message to any one of the first function instances in the group of first instances.
[0054] The method may include receiving a request to modify a protocol session, or a request to delete a protocol session, or a request to update or release a protocol session association from any one of the group of first function instances.
[0055] The method may include triggering a recovery process by the second function if a heartbeat process with all instances in the set of first function instances fails.
[0056] In a fifth aspect, a device is provided, comprising at least one processor and at least one memory comprising computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, enable the device to at least: provide first information from a first function instance in a group of first function instances to a second function, the first information comprising an indication that a protocol session between the first function and the second function can be controlled by different instances in the group of first function instances; and based on the first information, receive a protocol session-related message from the second function at a first function instance in the group of first function instances.
[0057] The first function may be a session management function. The second function may be a user plane function. The protocol session may be a packet forwarding control protocol session.
[0058] The apparatus may be configured to provide first information during a protocol association process.
[0059] The first information may include at least one of: a fully qualified domain name or identifier associated with the group of first function instances, a flag indicating that the protocol session can be controlled by different instances in the group of first function instances, and an identifier or Internet Protocol address of another first function instance in the group of first function instances.
[0060] The other first function instance may be a backup first function instance.
[0061] The apparatus may be configured to provide a request to update or release a protocol session association to any one of the group of first function instances.
[0062] The apparatus may be configured to provide the first information in a protocol session establishment or modification request.
[0063] The first information may be included in a control plane fully qualified session identifier.
[0064] The first information may include at least one of: a fully qualified domain name or identifier associated with the group of first function instances, a flag indicating that the protocol session can be controlled by different instances in the group of first function instances, a unique session identifier associated with the group of first function instances, and an identifier or Internet Protocol address of another first function instance in the group of first function instances.
[0065] The another first function instance may be a backup first function instance or a preferred first function instance.
[0066] When the another first functional instance is the preferred first functional instance, the identifier of the another first functional instance may include an IPv4 or IPv6 address.
[0067] The first information may include a null IPv4 or IPv6 address indicating that there is no preferred first function instance.
[0068] The apparatus may be configured to provide a request to modify or delete a protocol session to any one of the group of first functional instances.
[0069] The apparatus may be configured for any one of the group of first function instances to provide a request rejection to the second function, the request rejection comprising an indication of the first function instance in the group of first function instances.
[0070] The apparatus may be configured to provide a protocol session related message to a first function instance in the group of first function instances.
[0071] The apparatus may be configured for any one first function instance in the group of first function instances to establish a single protocol association with a second function.
[0072] In a sixth aspect, a device is provided, comprising at least one processor and at least one memory comprising computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, enable the device to at least: receive first information from a first function instance in a group of first function instances at a second function, the first information comprising an indication that a protocol session between the first function and the second function can be controlled by different instances in the group of first function instances; and based on the first information, provide a protocol session-related message from the second function to one of the first function instances in the group of first function instances.
[0073] The first function may be a session management function. The second function may be a user plane function. The protocol session may be a packet forwarding control protocol session.
[0074] The apparatus may be configured to receive the first information in a protocol association process, or a protocol session establishment or modification request.
[0075] When the first information is received in a protocol session establishment or modification request, the first information may be included in a control plane fully qualified session identifier.
[0076] The first information may include at least one of: a fully qualified domain name or identifier associated with the group of first function instances, a flag indicating that the protocol session can be controlled by different instances in the group of first function instances, and an identifier or Internet Protocol address of a backup first function instance in the group of first function instances.
[0077] When the first information is received in a protocol session establishment or modification request, the first information may include an IPv4 or IPv6 address, which indicates a preferred first function instance if the IPv4 or IPv6 address is non-empty, and which indicates no preferred first function instance if the IPv4 or IPv6 address is empty.
[0078] The device can be configured to: if the IPv4 or IPv6 address is non-empty, provide a protocol session related message from the second function to the IPv4 or IPv6 address, and if the IPv4 or IPv6 address is empty or unresponsive, send a protocol session related message to any one of the first function instances in the group of first instances.
[0079] The apparatus may be configured to receive, from any one of the group of first function instances, a request to modify a protocol session, or a request to delete a protocol session, or a request to update or release a protocol session association.
[0080] If the heartbeat process with all instances in the set of first function instances fails, the device may be configured for the second function to trigger a recovery process.
[0081] In a seventh aspect, a computer-readable medium is provided, comprising program instructions for causing an apparatus to at least perform the following operations: provide first information to a second function from a first function instance in a group of first function instances, the first information comprising an indication that a protocol session between the first function and the second function can be controlled by different instances in the group of first function instances; and based on the first information, receive a protocol session-related message from the second function at a first function instance in the group of first function instances.
[0082] The first function may be a session management function. The second function may be a user plane function. The protocol session may be a packet forwarding control protocol session.
[0083] The apparatus may be configured to provide first information during a protocol association process.
[0084] The first information may include at least one of: a fully qualified domain name or identifier associated with the group of first function instances, a flag indicating that the protocol session can be controlled by different instances in the group of first function instances, and an identifier or Internet Protocol address of another first function instance in the group of first function instances.
[0085] The other first function instance may be a backup first function instance.
[0086] The apparatus may enable any first function instance in the group of first function instances to provide a request to update or release a protocol session association.
[0087] The apparatus may be caused to provide the first information in a protocol session establishment or modification request.
[0088] The first information may be included in a control plane fully qualified session identifier.
[0089] The first information may include at least one of: a fully qualified domain name or identifier associated with the group of first function instances, a flag indicating that the protocol session can be controlled by different instances in the group of first function instances, a unique session identifier associated with the group of first function instances, and an identifier or Internet Protocol address of another first function instance in the group of first function instances.
[0090] The another first function instance may be a backup first function instance or a preferred first function instance.
[0091] When the another first functional instance is the preferred first functional instance, the identifier of the another first functional instance may include an IPv4 or IPv6 address.
[0092] The first information may include a null IPv4 or IPv6 address indicating that there is no preferred first function instance.
[0093] The apparatus may enable any first function instance in the group of first function instances to provide a request to modify or delete a protocol session.
[0094] The apparatus may cause any one of the group of first function instances to provide a request rejection to the second function, the request rejection comprising an indication of the first function instance in the group of first function instances.
[0095] The apparatus may be caused to provide a protocol session-related message to a first function instance in the group of first function instances.
[0096] The apparatus may enable any first function instance in the group of first function instances to establish a single protocol association with a second function.
[0097] In an eighth aspect, a computer-readable medium is provided, comprising program instructions for causing a device to at least perform the following operations: receiving first information at a second function from a first function instance in a group of first function instances, the first information comprising an indication that a protocol session between the first function and the second function can be controlled by different instances in the group of first function instances; and providing a protocol session-related message from the second function to a first function instance in the group of first function instances based on the first information.
[0098] The first function may be a session management function. The second function may be a user plane function. The protocol session may be a packet forwarding control protocol session.
[0099] The apparatus may be caused to receive the first information in a protocol association procedure, or a protocol session establishment or modification request.
[0100] When the first information is received in a protocol session establishment or modification request, the first information may be included in a control plane fully qualified session identifier.
[0101] The first information may include at least one of: a fully qualified domain name or identifier associated with the group of first function instances, a flag indicating that the protocol session can be controlled by different instances in the group of first function instances, and an identifier or Internet Protocol address of a backup first function instance in the group of first function instances.
[0102] When the first information is received in a protocol session establishment or modification request, the first information may include an IPv4 or IPv6 address, which indicates a preferred first function instance if the IPv4 or IPv6 address is non-empty, and which indicates no preferred first function instance if the IPv4 or IPv6 address is empty.
[0103] The device can be configured to: provide a protocol session-related message from the second function to the IPv4 or IPv6 address if the IPv4 or IPv6 address is non-empty, and to send a protocol session-related message to any one of the first function instances in the group of first instances if the IPv4 or IPv6 address is empty or unresponsive.
[0104] The apparatus may be configured to receive, from any one of the group of first functional instances, a request to modify a protocol session, or a request to delete a protocol session, or a request to update or release a protocol session association.
[0105] If the heartbeat process with all instances in the group of first function instances fails, the device can cause the second function to trigger a recovery process.
[0106] In a ninth aspect, a non-transitory computer-readable medium is provided, comprising program instructions for causing an apparatus to at least perform the method according to the third or fourth aspect.
[0107] In the above, many different embodiments have been described. It should be understood that further embodiments can be provided by combining any two or more of the above embodiments. BRIEF DESCRIPTION OF THE DRAWINGS
[0108] Embodiments will now be described, by way of example only, with reference to the accompanying drawings, in which:
[0109] Figure 1 A schematic diagram showing an example communication system including a base station and a plurality of communication devices;
[0110] Figure 2 A schematic diagram illustrating an example mobile communication device;
[0111] Figure 3 A schematic diagram showing an example control device;
[0112] Figure 4 A schematic diagram illustrating an example 5G core network;
[0113] Figure 5 A flowchart illustrating a method according to an example embodiment;
[0114] Figure 6 A flowchart illustrating a method according to an example embodiment;
[0115] Figure 7 shows a signaling flow between an SMF instance and a UPF according to an example embodiment;
[0116] Figure 8 shows the signaling flow between an SMF instance and a UPF according to an example embodiment;
[0117] Fig. 9 shows example information elements;
[0118] Fig.10 illustrating information elements according to example embodiments;
[0119] Fig.11 illustrating information elements according to example embodiments;
[0120] Fig.12 shows example information elements;
[0121] Fig.13 Shows a table of node ID types;
[0122] Fig.14 The signaling flow between an SMF instance and a UPF according to an example embodiment is shown. DETAILED DESCRIPTION
[0123] Before explaining the examples in detail, refer to Figures 1 to 3 Certain general principles of wireless communication systems and mobile communication devices are briefly explained to facilitate understanding of the technology upon which the described examples are based.
[0124] In such Figure 1In the wireless communication system 100 shown, mobile communication devices or user equipment (UE) 102, 104, 105 are provided with wireless access via at least one base station (e.g., next generation NB (gNB)) or similar wireless transmission and / or reception node or point. The base station can be controlled or assisted by at least one suitable controller device to enable its operation and management of communication between the mobile communication device and the base station. The controller device can be located in a radio access network (e.g., wireless communication system 100) or a core network (CN) (not shown) and can be implemented as a central device or its functions can be distributed over several devices. The controller device can be part of the base station and / or provided by a separate entity such as a radio network controller. In Figure 1 1 and 2. The control means 108 and 109 for controlling the respective macro-level base stations 106 and 107 are shown. The control means of the base stations may be interconnected with other control entities. The control means are typically equipped with storage capacity and at least one data processor. The control means and functions may be distributed among a plurality of control units. In some systems, the control means may additionally or alternatively be provided in a radio network controller.
[0125] exist Figure 1 In FIG. 1 , base stations or nodes 106 and 107 are shown as being connected to a wider communications network 113 via a gateway 112. A further gateway function may be provided to connect to another network.
[0126] Smaller base stations 116, 118, and 120 may also be connected to the network 113, for example, through a separate gateway function and / or via a controller of a macro-level station. Base stations 116, 118, and 120 may be pico or femto-level base stations, etc. In this example, stations 116 and 118 are connected via gateway 111, while station 120 is connected via controller device 108. In some embodiments, smaller stations may not be provided. Smaller base stations 116, 118, and 120 may be part of a second network (e.g., WLAN) and may be WLAN APs.
[0127] The communication devices 102, 104, 105 may access the communication system based on various access technologies such as code division multiple access (CDMA) or wideband code division multiple access (WCDMA). Other non-limiting examples include time division multiple access (TDMA), frequency division multiple access (FDMA) and its various schemes such as interleaved frequency division multiple access (IFDMA), single carrier frequency division multiple access (SC-FDMA) and orthogonal frequency division multiple access (OFDMA), space division multiple access (SDMA), etc.
[0128] An example of a wireless communication system is an architecture standardized by the Third Generation Partnership Project (3GPP). A development based on 3GPP is generally referred to as the Long Term Evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio access technology. The various development stages of the 3GPP specification are referred to as releases. The latest development of LTE is generally referred to as Advanced LTE (LTE-A). LTE (LTE-A) uses a radio mobile architecture called Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and a core network called Evolved Packet Core (EPC). The base station of such a system is referred to as an evolved or enhanced Node B (eNB) and provides E-UTRAN features such as user plane packet data convergence / radio link control / media access control / physical layer protocol (PDCP / RLC / MAC / PHY) and control plane radio resource control (RRC) protocol termination in communication devices. Other examples of radio access systems include those provided by base stations of systems based on technologies such as wireless local area networks (WLAN) and / or WiMax (Worldwide Interoperability for Microwave Access). The base station can provide coverage for an entire cell or similar radio service area. The core network elements include a Mobility Management Entity (MME), a Serving Gateway (S-GW), and a Packet Gateway (P-GW).
[0129] An example of a suitable communication system is the 5G or NR concept. The network architecture in NR may be similar to that in Advanced LTE. The base station of the NR system may be referred to as the next generation Node B (gNB). Changes to the network architecture may depend on the need to support various radio technologies and more refined QoS support, as well as some on-demand requirements for QoS levels that support QoE from the user's perspective, for example. New functions are defined in the 5G system architecture, including access management function (AMF), session management function (SMF), user plane function (UPF), and other network functions in the 5G core network (5GC). The 5G system supports new capabilities including network slicing, which can better customize the network for application requirements and provide a virtual network to tenants. It also uses a service-based architecture that provides greater flexibility for introducing new services and features compared to the EPC that relies on a fixed peer reference point. NR can use multiple input multiple output (MIMO) antennas, many more base stations or nodes than LTE (the so-called small cell concept), including macro sites, which operate in collaboration with smaller base stations and may also use various radio technologies to achieve better coverage and enhanced data rates. NR can also support lower latency for air interface transmissions due to revisions to the physical and MAC layer protocols.
[0130] Future networks may use network function virtualization (NFV), which is a network architecture concept that proposes to virtualize network node functions into "building blocks" or entities that are operably connected or linked together to provide services. Virtualized network functions (VNFs) may include one or more virtual machines that use standard or general-purpose servers rather than custom hardware to run computer program codes. Cloud computing or data storage may also be used. In radio communications, this may mean that node operations will be performed by a centralized unit (CU) at least in part in a server, host, or node that is operably coupled to a distributed unit (DU), which may be connected to a remote radio head (RRH). Node operations will also be distributed between multiple servers, nodes, or hosts. It should also be understood that the workload distribution between core network operations and base station operations may be different from LTE, or even non-existent.
[0131] Now refer to Figure 2 describing in more detail possible mobile communication devices, Figure 2 A schematic partial cross-sectional view of a communication device 200 is shown. Such a communication device is generally referred to as a user equipment (UE) or terminal. Suitable mobile communication devices can be provided by any device capable of sending and receiving radio signals. Non-limiting examples include a mobile station (MS) or a mobile device such as a mobile phone or a so-called "smart phone", a computer equipped with a wireless interface card or other wireless interface facilities (e.g., a USB adapter), a personal data assistant (PDA) or a tablet computer provided with wireless communication capabilities, or any combination thereof. Mobile communication devices can, for example, provide data communications for carrying communications such as voice, e-mail (email), text messages, multimedia, etc. Therefore, users can be given and provided with various services via their communication devices. Non-limiting examples of these services include two-way or multi-way calls, data communications or multimedia services, or only access to data communication network systems such as the Internet. . Broadcast or multicast data can also be provided to users. Non-limiting examples of content include downloads, television and radio programs, videos, advertisements, various alarms, and other information.
[0132] In industrial applications, the communication device can be a modem integrated into an industrial actuator (e.g., a robotic arm) and / or a modem acting as an Ethernet hub, which will act as a connection point for one or several connected Ethernet devices (the connection can be wired or wireless).
[0133] The mobile device is typically equipped with at least one data processing entity 201, at least one memory 202, and possibly other components 203, for software and hardware-assisted execution of the tasks it is designed to perform, including controlling access to access systems and other communication devices and controlling communications with access systems and other communication devices. Data processing, storage and other related control devices may be provided on a suitable circuit board and / or in a chipset. This feature is indicated by reference numeral 204. The user may control the operation of the mobile device by means of a suitable user interface such as a keypad 205, voice commands, a touch-sensitive screen or pad, or a combination thereof. A display 208, a speaker and a microphone may also be provided. In addition, the mobile communication device may include suitable connectors (wired or wireless) to other devices and / or for connecting external accessories (e.g., a hands-free device).
[0134] The mobile device 200 may receive signals over the air or radio interface 207 via suitable means for receiving, and may transmit signals via suitable means for transmitting radio signals. Figure 2 In the embodiment of the present invention, the transceiver arrangement is schematically designated by block 206. The transceiver arrangement 206 may be provided, for example, by means of a radio part and associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.
[0135] Figure 3 An example embodiment of a control device for a communication system is shown, for example, a station to be coupled to and / or used to control an access system, such as a RAN node, for example, a base station, an eNB or a gNB, a relay node or a core network node such as an MME or an S-GW or a P-GW, or a core network function such as an AMF or an SMF, or a server or a host. The method may be implanted in a single control device or implanted between more than one control device. The control device may be integrated with a node or module of a core network or a RAN or external to it. In some embodiments, the base station includes a separate control device unit or module. In other embodiments, the control device may be other network units such as a radio network controller or a spectrum controller. In some embodiments, each base station may have such a control device (such as a CU control plane (CU-CP)) and a control device provided in a radio network controller. The control device 300 may be arranged to provide control of communications in a service area of the system. The control device 300 includes at least one memory 301, at least one data processing unit 302, 303 and an input / output interface 304. Via the interface, the control device may be coupled to a receiver and a transmitter of the base station. The receiver and transmitter may be implemented as a radio front end or a remote radio head.
[0136] Figure 4A schematic diagram of an example 5G core network (CN) is shown. An example 5G core network (CN) includes functional entities. The CN is connected to the UE via a radio access network (RAN). The UPF (User Plane Function) can be an intermediate UPF or PSA (PDU Session Anchor) that provides an anchor point for user IP, Ethernet, or unstructured user data sessions. The UPF can be responsible for forwarding PDUs (e.g., IP packets or Ethernet frames) back and forth between
[0137] DN (data network) and 5G access network (e.g. gNB in case of 3GPP access, or N3IWF / TNGF / W-AGF in case of non-3GPP access)
[0138] DN (data network) with another UPF that supports PDU sessions
[0139] 5G access network (e.g., gNB in case of 3GPP access, or N3IWF / TNGF / W-AGF in case of non-3GPP access).
[0140] The UPF is controlled by the SMF (Session Management Function) which can receive policies from the PCF (Policy Control Function). The CN may also include an AMF (Access and Mobility Function) which terminates the control plane interface with the 5G access network and manages UE registration and mobility.
[0141] 3GPP Rel-16 (Enhancements to Service-Based Architecture work item) supports the concept of SMF Groups, which include functionally equivalent SMF instances that can access the Session Management (SM) context handled by the SMF Group and invoke all service SM requests targeted to the SMF Group. 3GPP Rel-16 generalizes the concept of NF Groups in the 5GC control plane (limited to AMF Groups in Rel-15) to achieve enhanced scalability (e.g., when shrinking or expanding operations), dynamic load rebalancing, elasticity, and enable support for stateless NFs. See 3GPP TS 23.501.
[0142] According to the existing system architecture, SMF uses the Packet Forwarding Control Protocol (PFCP) to control the user plane functions in the UPF through the N4 interface (see 3GPP TS29.244). The N4 interface is currently defined as a point-to-point interface between an SMF instance and a UPF; PFCP sessions established in the UPF (e.g., to support PDU sessions) are bound to the SMF instances that created them.
[0143] Before establishing any PFCP session (e.g., during PDU session establishment), the SMF will establish a PFCP association with the UPF. The PFCP association establishment process is a node-dependent process during which the UPF signals the SMF about its node capabilities (e.g., the features it supports) and configuration (e.g., IP addressing information).
[0144] When establishing a PFCP session, the SMF signals a "CP node ID" (control plane node ID) and a CP F-SEID (control plane fully qualified session identifier) to the UPF in the PFCP session establishment request message, where the CP node ID identifies the SMF instance and can be in the form of an IP address or a fully qualified domain name (FQDN), and the CP F-SEID identifies the PFCP session in the CP node, i.e., IP address + session identifier (SEID).
[0145] The UPF sends subsequent session-related request messages to the SMF for this PFCP session (e.g., for a PDU session with no active user plane connection, a session report message is sent when a DL data packet arrives) to the IP address assigned by the SMF received in the CP F-SEID. This may be a problem in deployments with SMF groups.
[0146] It may be useful to adjust the N4 protocol (PFCP) to enable any SMF instance from the SMF group to control any PFCP session created by any other SMF instance in the SMF group, and / or to control the UPF to initiate signaling to any SMF instance in the SMF group.
[0147] For example, the SMF instance that created the PFCP session may no longer be available due to an SMF instance failure, a planned maintenance or shrink operation of the SMF instance, or a new SMF instance may have been deployed in the SMF group (scaling operation).
[0148] 3GPP CT4 has not yet discussed the impact of the SMF group concept on the N4 / PFCP protocol.
[0149] Using the current PFCP protocol, a SMF group can establish a single PFCP association with the UPF and the CP node ID in the form of a fully qualified domain name (FQDN), assuming that the SMFs within the SMF group self-coordinate the establishment / update / publication of the PFCP association (vendor specific implementation). The protocol allows the SMFs to change the F-SEID assigned to an existing PFCP session, so that when an SMF instance takes over a PFCP session created by a different SMF instance (for example, when the latter SMF instance fails or is removed), the SMF instance can change the F-SEID assigned to the relevant PFCP session to its own IP address.
[0150] This may result in increased signaling to update the F-SEID for hundreds of thousands of PFCP sessions, and / or may result in the UPF being unable to initiate session-related signaling to the SMF until the PFCP session is updated with the new F-SEID. If the UPF detects a communication or heartbeat failure with the IP address of the F-SEID, the UPF may release the PFCP session.
[0151] A possible alternative solution may be to move the IP addresses allocated in the CP F-SEID between the SMF instances in the SMF group to hide the addition / removal of SMF instances within the SMF group from the UPF. This solution may lead to implementation complexity and operational limitations, for example, because the SMF instances may be deployed in different locations / subnets.
[0152] Figure 5 A flow chart of a method according to an example embodiment is shown. Figure 5 The method shown in can be performed at at least one SMF in the SMF group.
[0153] In a first step S1 , the method comprises providing first information from a first function instance of a set of first function instances to a second function, the first information comprising an indication that a protocol session between the first function and the second function may be controlled by different instances of the set of first function instances.
[0154] In a second step S2, the method comprises: receiving, at a first function instance in the group of first function instances, a protocol session related message from a second function based on the first information.
[0155] Figure 6 A flow chart of a method according to an example embodiment is shown. Figure 6 The method shown in can be performed at the UPF.
[0156] In a first step T1, the method comprises receiving, at a second function, first information from a first function instance in a group of first function instances, the first information comprising an indication that a protocol session between the first function and the second function can be controlled by different instances in the group of first function instances.
[0157] In a second step T2, the method comprises providing, based on the first information, a protocol session related message from the second function to a first function instance of the group of first function instances.
[0158] The first function may be a session management function (SMF). The second function may be a user plane function (UPF). The protocol session may be a PFCP session.
[0159] The first information may include at least one of the following: a flag indicating that the protocol session can be controlled by different instances in the group of first function instances, a fully qualified domain name or identifier of the group of first function instances, and an identifier or IP address of another first function instance in the group of first function instances. The group of first function instances may be identified by an SMF identifier or a FQDN.
[0160] The other first function instance may be a backup first function instance.
[0161] The first information may be provided in a protocol association establishment procedure, or a protocol session establishment or modification request.
[0162] The method may include: any one of the group of first function instances establishing a single protocol association with the second function.
[0163] If the first information is provided in a protocol session establishment or modification request, the first information may be included in a CP F-SEID (control plane fully qualified session identifier). If the binding with the first function instance is preferred, the other first function instance may be the preferred first function instance. In this case, the identifier of the other first function instance may include an Internet Protocol address (e.g., an IPv4 or IPv6 address), or a preferred first function instance.
[0164] The method may include: if the IPv4 or IPv6 address is non-empty, providing a protocol session related message to the IPv4 or IPv6 address from the second function, and if the IPv4 or IPv6 address is empty or unresponsive, sending a protocol session related message to any one of the first function instances in the group of first instances.
[0165] Alternatively, if the IP address or identifier of the backup instance is provided and the IP address signaled in the existing IPv4 or IPv6 address field does not respond, the second function may provide a session-related request message to the backup first function instance.
[0166] If the first information is provided in a protocol session establishment or modification request, the first information may include a unique session identifier (SEID).
[0167] A protocol session between a first function and a second function that can be controlled by different function instances in the first group of function instances can be defined as a PFCP session that is not bound to a unique PFCP entity (i.e., a unique IP address of an SMF instance). Instead, the protocol session can be bound to any one PFCP entity within a group of first functions (e.g., within a group of SMFs, where the SMF group can be identified by an SMF group identifier or FQDN).
[0168] The protocol-related session message initiated by UPF may be a PFCP session report request.
[0169] That is, during the PFCP association establishment process or during the PFCP session establishment process, the SMF in the SMF group can signal to the UPF the SMF group identifier or FQDN, at least one of the backup SMF instance ID or IP address, and signal that the PFCP session is not bound to a unique PFCP entity (i.e., the unique IP address of the SMF instance).
[0170] A single PFCP association may be established between a SMF group and a UPF. In this case, the management of PFCP associations across SMF groups (i.e., between SMFs within an SMF group) is implementation specific, but a standard requirement may be that PFCP associations with UPFs are managed and unique at the SMF group level. Node related processes (e.g., PFCP association establishment, load / overload control) may be coordinated between SMFs within an SMF group. There is no assumption that there is a front-end function that coordinates the SMF group to avoid a single point of failure architecture. PFCP association establishment is also used to enable the SMF to understand whether the UPF supports being controlled by a SMF group (rather than a single SMF).
[0171] During PFCP session establishment, the SMF may additionally signal a preferred binding to a specific SMF instance by optionally including a non-empty IPv4 or IPv6 address in the CP F-SEID; the SMF may also additionally signal an SMF group identifier or FQDN, or a backup SMF instance ID or IP address.
[0172] Signaling preferred binding can, for example, avoid that, for a given PFCP session, the UPF reselects a different SMF instance for each newly initiated session-related request message for the SMF group.
[0173] If a preferred binding exists, i.e., if the existing IPv4 or IPv6 address field is signaled with a non-empty IP address, the UPF can initiate a session-related request message to the IPv4 or IPv6 address of a specific SMF instance.
[0174] If there is no preferred binding for a specific SMF instance, or if a preferred binding for a specific SMF instance exists but the corresponding IP address does not respond, the UPF can initiate a session-related request message to any SMF instance in the SMF group.
[0175] If a backup SMF IP address or a backup SMF instance ID is sent by SMF signaling and there is no response to the IP address signaled in the existing IPv4 or IPv6 address field, the UPF can initiate a session-related request message to the backup SMF instance.
[0176] For example, by querying DNS or by performing a discovery request to NRF, UPF can use the SMF group identifier or FQDN to discover the SMF instance within the SMF group. For the latter, each SMF instance can register the SMF group identifier or FQDN in its NF profile in NRF. By querying DNS or initiating a discovery request to NRF, UPF also uses the backup SMF instance ID to discover the IP address of the SMF.
[0177] Any first function instance in the group of first function instances can send a request to modify the protocol session, or a request to delete the protocol session, or a request to update or release the protocol session association to the second function. In other words, any SMF in the SMF group can send a request to modify or delete the PFCP session, or a request to update or release the PFCP association to the UPF.
[0178] If the heartbeat process with all instances in the group of first function instances fails, the second function can trigger a recovery process. For a PFCP session that is not bound to a unique CP PFCP entity, if a heartbeat failure with the preferred bound IP address is detected, the UPF may not trigger error handling, i.e., the recovery process specified in TS 23.527 (e.g., local release of the PFCP session). The recovery process can only be triggered if the heartbeat fails with all IP addresses of all SMF instances in the SMF group.
[0179] Figure 7 An example signaling diagram for a PFCP association establishment procedure between an SMF instance in an SMF group and a UPF controlled by the SMF group is shown.
[0180] exist Figure 7In the example shown in , before establishing the first PFCP session in the UPF, an SMF instance in the SMF group establishes a PFCP association with the UPF. Node-related processes (e.g., PFCP association establishment, load / overload control) are coordinated between the SMF instances in the SMF group (implementation specific, e.g., relying on UPF state information stored in the UDSF).
[0181] The SMF may signal the UPF with a new SMF group identifier, FQDN, or a new backup SMF instance ID or IP address during the PFCP association process.
[0182] In an example embodiment, one SMF in the SMF group will establish a single PFCP association with the UPF for the SMF group; the node ID in the PFCP association establishment request will be set to represent the FQDN of the SMF group.
[0183] Table 1 shows the information elements in the PFCP association establishment request, including the SMF group identifier or FQDN and the backup SMF in the bottom two rows.
[0184]
[0185] The addition of an SMF Group Identifier or FQDN and a backup SMF corresponds to one possible implementation. Figure 8 The described alternative implementations may not require these parameters.
[0186] Figure 8 An example signaling diagram for a PFCP session establishment procedure between an SMF instance in an SMF group and a UPF controlled by the SMF group is shown.
[0187] In this example embodiment, the SMF provides the UPF with a control plane (CP) SEID (session identifier), and at least one of the following: an IPv4 or IPv6 address (if binding to a specific SMF instance is preferred), an SMF group identifier or FQDN (if not provided during PFCP association establishment), a backup SMF instance identifier or IP address (if not provided during PFCP association establishment), and an indication that the PFCP session is not bound to a unique PFCP entity (i.e., if an IPv4 or IPv6 address is provided, the PFCP session is not bound only to the IP address provided in the CP-F-SEID). The SMFs within an SMF group ensure unique allocation of SEIDs within the group.
[0188] If no existing IPv4 and IPv6 addresses are allocated, an IPv4 (or IPv6) null address may be signaled, since PFCP requires at least one of an IPv4 address or an IPv6 address to be included.
[0189] In an example embodiment, when establishing a PFCP session, the SMF allocates a unique SEID within the SMF group in the CP F-SEID of the PFCP session establishment request by including the SSET flag in the CP F-SEID, indicating to the UPF that the PFCP session can be continuously controlled by different SMFs in the SMF group, and that the preferred binding with a specific SMF can be additionally signaled by including the IPv4 or IPv6 address of the SMF in the CP F-SEID. If a preferred binding with a specific SMF is not desired, the CP F-SEID will contain a null IPv4 or IPv6 address.
[0190] Table 2 shows the information elements in the PFCP session establishment request.
[0191]
[0192]
[0193]
[0194] Table 2
[0195] Fig. 9 An example encoded F-SEID is shown. The following flags are encoded within octet 5.
[0196] - Bit 1 - V6: If this bit is set to "1", then the IPv6 address field will be present in the F-SEID, otherwise there will be no IPv6 address field at all.
[0197] - Bit 2 - V4: If this bit is set to "1", the IPv4 address field shall be present in the F-SEID, otherwise the IPv4 address field shall not be present at all.
[0198] - Bits 3 to 8 are spare and are reserved for future use.
[0199] At least one of V4 and V6 will be set to "1", and both of them may be set to "1".
[0200] If present, octets "m to (m+3)" and / or "p to (p+15)" (IPv4 Address / IPv6 Address field) contain the corresponding address values.
[0201] Since the F-SEID IE is an extensible IE (see subclause 8.1.2 of 3GPP TS29.244), in one possible implementation, it can be extended, for example, as Fig.10 As shown in Fig.10In the SMF group identifier or FQDN field, if the corresponding flag is set to 1, there are fields: SMF group identifier or FQDN; Backup SMF instance ID or IP address.
[0202] In an alternative embodiment, if Fig.11 As shown in , a flag is included in the F-SEID to indicate to the UPF that the PFCP session is not bound to a unique CP PFCP entity (i.e., IP address). When this flag is set, it indicates that the UPF will consider that any IP address that it can derive from the CP Node ID IE (through a DNS query or NRF discovery process) can take over control of the PFCP session. In this case, when establishing a PFCP session or at a subsequent PFCP session modification, the UPF should use the IP address that has been provided in the F-SEID (if any), but another IP address can be used if there is a problem.
[0203] The Node ID is defined in 3GPP TS 29.244. In this alternative implementation, it may be specified that the Node ID is encoded as a FQDN representing the SMF group.
[0204] The Node ID IE will contain either the FQDN or the IPv4 / IPv6 address. It will be Fig.13 is encoded as shown in .
[0205] The Node ID Type indicates the type of the Node ID value. The Node ID value is encoded as a 4-bit binary integer as specified in Table 13. If the Node ID is an IPv4 address, the Node ID value length will be 4 octets. If the Node ID is an IPv6 address, the Node ID value length will be 16 octets. If the Node ID is an FQDN, the Node ID value encoding will be the same as the encoding of the FQDN in the DNS message of Section 3.1 of IETF RFC1035
[27] , but excluding the trailing zero byte.
[0206] Fig.14 An example signaling diagram for PFCP session report request and response between an SMF instance for an SMF group and the UPF controlled by the SMF group is shown.
[0207] If the existing IPv4 or IPv6 address field is signaled with a non-empty IP address or any SMF instance in the SMF group, if there is no preferred binding for a specific SMF instance, or if a preferred binding for a specific SMF instance exists but the corresponding IP@ does not respond, the UPF initiates a session-related request message (e.g., PFCP session report request, see subclauses 6.3.5 and 7.6.8 of TS 29.244) to the IPv4 or IPv6 address of the specific SMF instance (for which a preferred binding exists).
[0208] The UPF uses the SMF group identifier or FQDN (or the FQDN in the CP node IE in the alternative implementation of step 2) to discover the SMF instances within the SMF group, for example, by querying the DNS or by performing a discovery request to the NRF. For the latter, each SMF instance registers the SMF group identifier or FQDN in its NF profile in the NRF.
[0209] Alternatively, if the backup SMF IP address or backup SMF instance ID is sent by SMF signaling and there is no response to the IP address signaled in the existing IPv4 or IPv6 address field, the UPF can initiate a session-related request message to the backup SMF instance. This alternative solution is mutually exclusive with the solution of the previous paragraph, that is, the SMF indicates an SMF group or a backup SMF for the PFCP session. This allows the UPF implementation to support different SMF resilience schemes (one-to-one if a backup SMF instance is used, and one-to-many if an SMF group is used).
[0210] A PFCP session corresponds to a PDU session. The following may happen: when the first SMF instance used to serve a PDU session (and the corresponding PFCP session) has failed or has decided not to serve the PDU session anymore, the 5G control plane process selects a second SMF instance to serve the PDU session (and the corresponding PFCP session), but then selects a third SMF instance on the UPF (because it is unaware of the change in the SMF instance serving the PFCP session).
[0211] The method may include providing a request rejection to the second function, the request rejection including an indication of the first function instance in the group of first function instances. The SMF may redirect the UPF initiated PFCP session related request to a different SMF in the group of SMFs by rejecting the UPF initiated PFCP session related request with a cause "redirect request" and with a CP F-SEID IE including an IP address of a new SMF to contact (i.e., a new preferred SMF binding).
[0212] For example, by rejecting a UPF-initiated PFCP session-related request with a cause of "redirect request" and with a CP F-SEID IE including the IP address of a new SMF to be contacted (i.e., a new preferred SMF binding), the SMF instance (determining that it is not a suitable SMF to serve the PFCP session, about which it received a message from the UPF) may redirect the UPF-initiated PFCP session-related request to a different SMF in the SMF group. Alternatively, the SMF may forward the UPF request to another SMF in the SMF group; the new SMF responds to the UPF, optionally including a CP F-SEID IE with the IPv4 or IPv6 address of the new preferred SMF.
[0213] Alternatively, the SMF may forward the UPF request to another SMF in the SMF group; the new SMF responds to the UPF, optionally including a CP F-SEID IE with the IPv4 or IPv6 address of the new preferred SMF. That is, the method may include: providing a protocol session related message to a first function instance in the group of first function instances.
[0214] For example, to avoid the need for coordination between SMF instances to achieve unique SEID allocation, when the UPF reselects an alternative SMF instance in the group, it sets a null SEID in the header of the PFCP session-related request message sent to the new SMF instance, and it includes the old F-SEID in the message. The new SMF instance uses the old F-SEID to obtain the session context and allocates a new F-SEID in the response.
[0215] The above method can also be applied to distributed SMF implementations (without considering the concept of SMF groups introduced in Rel-16) when other PFCP entities (i.e., IP addresses) of the SMF can take over control of the PFCP session when the PFCP entity that created the PFCP session fails or is removed from the SMF. The above method can also be applied to SMF service groups, for example, to allow the UPF to reselect an SMF service instance from a specific SMF service group for a network slicing scenario.
[0216] This approach can allow any one SMF instance within the SMF group to control the UPF association and the PFCP session established in the UPF without any additional N4 signaling and without any failure or loss of messages or PFCP session context in the UPF.
[0217] This method can be found in reference Figure 3 The control device described is implemented in the
[0218] A device may include a component for performing the following operations: providing first information from a first function instance in a group of first function instances to a second function, the first information including an indication that a protocol session between the first function and the second function can be controlled by different instances in the group of first function instances; and based on the first information, receiving a protocol session-related message from the second function at a first function instance in the group of first function instances.
[0219] Alternatively or additionally, a device may include a component for performing the following operations: receiving first information at a second function from a first function instance in a group of first function instances, the first information including an indication that a protocol session between the first function and the second function can be controlled by different instances in the group of first function instances; and based on the first information, providing a protocol session-related message from the second function to a first function instance in the group of first function instances.
[0220] It should be understood that these devices may include or be coupled to other units or modules, etc., such as radio components or radio terminals used in or for sending and / or receiving. Although these devices have been described as one entity, different modules and memories may be implemented in one or more physical or logical entities.
[0221] Note that while embodiments have been described with respect to LTE and 5G NR, similar principles may also be applied with respect to other networks and communication systems. Thus, while certain embodiments are described above by way of example with reference to certain example architectures for wireless networks, technologies and standards, these embodiments may be applied to any other suitable form of communication system in addition to the communication system illustrated and described herein.
[0222] It is also noted herein that while in the above exemplary embodiments are described, there are several variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention.
[0223] In general, various example embodiments may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects of the invention may be implemented in hardware, while other aspects may be implemented in firmware or software that may be 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, flow charts, or using some other graphical representation, it should be well understood that, as non-limiting examples, the boxes, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.
[0224] Exemplary embodiments of the present invention may be implemented by computer software executable by a data processor of a mobile device, such as in a processor entity, or by hardware, or by a combination of hardware and software. Computer software or programs are also referred to as program products, including software routines, applets and / or macros, which may be stored in any device-readable data storage medium and which include program instructions for performing specific tasks. A computer program product may include one or more computer executable components configured to execute an embodiment when the program is running. One or more computer executable components may be at least one software code or a portion thereof.
[0225] Further in this regard, it should be noted that any box of the logic flow as in the accompanying drawings may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on physical media such as memory chips, or storage blocks implemented within a processor, magnetic media such as hard disks or floppy disks, and optical media such as, for example, DVDs and data variants thereof, CDs, etc. Physical media are non-transitory media.
[0226] The memory may be of any type suitable for 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, as non-limiting examples, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an FPGA, a gate-level circuit based on a multi-core processor architecture, and a processor.
[0227] Example embodiments of the present invention may be practiced in various components such as integrated circuit modules. The design of integrated circuits is generally a highly automated process. Complex and powerful software tools are available to convert logic level designs into semiconductor circuit designs ready to be etched and formed on semiconductor substrates.
[0228] The foregoing description has provided a complete and detailed description of exemplary embodiments of the present invention by way of non-limiting examples. However, various modifications and changes will become apparent to those skilled in the art in view of the foregoing description when read in conjunction with the accompanying drawings and the appended claims. However, the teachings of all such or similar modifications of the present invention will still fall within the scope of protection of the present invention as defined by the appended claims. Further embodiments do exist including combinations of one or more embodiments with any of the other previously discussed embodiments.
[0229] Any reference to Table 13 should be deemed not to exist.
Claims
1. A device for a communication network, the device comprising: a first instance of a session management function among a set of instances of the session management function, the first instance of the session management function being configured to: providing first information to a user plane function, the first information being used by the user plane function to send a protocol session related message, the first information comprising an indication that a protocol session between the first instance of the session management function and the user plane function may be controlled by any instance of the set of instances of the session management function, and the first information comprising at least one of: a fully qualified domain name or identifier associated with the set of instances of the session management function, or an identifier or Internet Protocol address of a second instance of the session management function in the set of instances of the session management function; as well as A protocol session related message is received from the user plane function.
2. The device according to claim 1, wherein: The protocol session is a packet forwarding control protocol session.
3. The device according to any one of claims 1 to 2, wherein: The providing to the user plane function comprises providing the first information in a protocol association procedure.
4. The device according to claim 3, wherein: The indication includes a logo.
5. The device according to claim 4, wherein: The second instance of the session management function is a backup of the first instance of the session management function.
6. The device according to any one of claims 3 to 5, wherein: The first instance of the session management function is further configured to provide a request to update or release a protocol session association.
7. The device according to any one of claims 1 to 4, wherein: Providing the first information to the user plane function comprises providing the first information in a protocol session establishment or modification request.
8. The device according to claim 7, wherein: The first information is included in a control plane fully qualified session identifier.
9. The device according to claim 7 or claim 8, wherein: The first information includes a unique session identifier associated with the set of instances of the session management function.
10. The device according to claim 9, wherein: The second instance of the session management function is a backup of the first instance of the session management function or a preferred instance of the session management function.
11. The device according to claim 10, wherein: The second instance of the session management function is a preferred instance of the session management function, and the identifier of the second instance of the session management function comprises an IPv4 or IPv6 address.
12. The device according to any one of claims 7 to 11, wherein: The first information includes a null IPv4 or IPv6 address indicating that there is no preferred instance of the session management function.
13. The device according to any one of claims 7 to 12, wherein: The first instance of the session management function is further configured to provide a request to modify or delete a protocol session.
14. The device according to any one of claims 1 to 13, wherein: The first instance of the session management function is further configured to provide a request rejection to the second instance of the session management function, the request rejection comprising an indication of the first instance of the session management function.
15. The apparatus according to any one of claims 1 to 13, comprising the user plane function, wherein: The user plane function is configured to provide the protocol session related messages to the first instance of the session management function.
16. The device according to any one of claims 1 to 15, wherein: The first instance of the session management function is further configured to establish a single protocol association with the user plane function.
17. An apparatus for a communication network, the apparatus comprising a user plane function, the user plane function being configured to: receiving first information from a first instance of a session management function in a set of instances of the session management function, the first information being used by the user plane function to send a protocol session related message, the first information comprising an indication that a protocol session between the first instance of the session management function and the user plane function may be controlled by any instance in the set of instances of the session management function, and the first information comprising at least one of: a fully qualified domain name or identifier associated with the set of instances of the session management function, or an identifier or an Internet Protocol address of a second instance of the session management function in the set of instances of the session management function; and Based on the first information, a protocol session-related message is provided to one of the set of instances of the session management function.
18. The device according to claim 17, wherein: The protocol session is a packet forwarding control protocol session.
19. The device according to any one of claims 17 to 18, wherein: The receiving includes: receiving the first information in a protocol association process, or a protocol session establishment or modification request.
20. The device according to claim 19, wherein The first information is received in a protocol session establishment or modification request, and wherein the first information is included in a control plane fully qualified session identifier.
21. The apparatus of claim 19 or claim 20, wherein: The indication includes a logo.
22. The device according to any one of claims 19 to 21, wherein: The first information is received in a protocol session establishment or modification request, and wherein the first information includes an IPv4 or IPv6 address, and if the IPv4 or IPv6 address is non-empty, it indicates a preferred instance of the session management function in the set of instances of the session management function, and if the IPv4 or IPv6 address is empty, it indicates that there is no preferred instance in the set of instances of the session management function.
23. The device according to claim 22, wherein: The user plane function is configured to: provide the protocol session related message to the IPv4 or IPv6 address if the IPv4 or IPv6 address is non-null, and send the protocol session related message to any instance in the set of instances of the session management function if the IPv4 or IPv6 address is null or unresponsive.
24. The device according to any one of claims 18 to 23, wherein: The user plane function is configured to receive, from any instance of the set of instances, a request to modify a protocol session, or a request to delete a protocol session, or a request to update or release a protocol session association.
25. The device according to any one of claims 18 to 24, wherein: The user plane function is configured to trigger a recovery procedure if a heartbeat procedure with all instances of the set of instances of the session management function fails.
26. A method of communication, the method comprising: providing first information from a first instance of a session management function among a set of instances of the session management function to a user plane function, the first information being used by the user plane function to send a protocol session related message, the first information comprising an indication that a protocol session between the first instance of the session management function and the user plane function may be controlled by any of the set of instances of the session management function, and the first information comprising at least one of: a fully qualified domain name or identifier associated with the set of instances of the session management function, or an identifier or Internet Protocol address of a second instance of the session management function among the set of instances of the session management function; as well as A protocol session-related message is received from the user plane function at the first instance of the session management function.
27. A method of communication, the method comprising: receiving, at a user plane function, first information from a first instance of a session management function among a set of instances of the session management function, the first information being used by the user plane function to send a protocol session related message, the first information comprising an indication that a protocol session between the first instance of the session management function and the user plane function may be controlled by any of the set of instances of the session management function, and the first information comprising at least one of: a fully qualified domain name or identifier associated with the set of instances of the session management function, or an identifier or Internet Protocol address of a second instance of the session management function among the set of instances of the session management function; as well as Based on the first information, a protocol session-related message is provided from the user plane function to one of the set of instances of the session management function.
28. An apparatus for a communications network, the apparatus comprising at least one processor and at least one memory including computer program code of a first instance of a session management function, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to at least: providing first information to a user plane function, the first information being used by the user plane function to send a protocol session related message, the first information comprising an indication that a protocol session between the first instance of the session management function and the user plane function may be controlled by any instance of a set of instances of the session management function, and the first information comprising at least one of: a fully qualified domain name or identifier associated with the set of instances of the session management function, or an identifier or Internet Protocol address of a second instance of the session management function in the set of instances of the session management function; and A protocol session-related message is received from the user plane function at the first instance of the session management function.
29. An apparatus for a communications network, the apparatus comprising at least one processor and at least one memory including computer program code for user plane functionality, the at least one memory and the computer program code being configured to, together with the at least one processor, cause the apparatus to at least: receiving first information from a first instance of a session management function in a set of instances of the session management function, the first information being used by the user plane function to send a protocol session related message, the first information comprising an indication that a protocol session between the first instance of the session management function and the user plane function may be controlled by any instance in the set of instances of the session management function, and the first information comprising at least one of: a fully qualified domain name or identifier associated with the set of instances of the session management function, or an identifier or an Internet Protocol address of a second instance of the session management function in the set of instances of the session management function; and Based on the first information, a protocol session related message is provided to an instance of the session management function in the set of instances.
30. A computer-readable medium comprising program instructions of a first instance of a session management function, the program instructions being configured to cause an apparatus to at least: providing first information to a user plane function, the first information being used by the user plane function to send a protocol session related message, the first information comprising an indication that a protocol session between the first instance of the session management function and the user plane function may be controlled by any instance of a set of instances of the session management function, and the first information comprising at least one of: a fully qualified domain name or identifier associated with the set of instances of the session management function, or an identifier or Internet Protocol address of a second instance of the session management function in the set of instances of the session management function; and A protocol session-related message is received from the user plane function at the first instance of the session management function.
31. A computer-readable medium comprising program instructions for user plane functions, the program instructions being configured to cause an apparatus to at least perform the following operations: receiving first information from a first instance of a session management function in a set of instances of the session management function, the first information being used by the user plane function to send a protocol session related message, the first information comprising an indication that a protocol session between the first instance of the session management function and the user plane function may be controlled by any instance in the set of instances of the session management function, and the first information comprising at least one of: a fully qualified domain name or identifier associated with the set of instances of the session management function, or an identifier or an Internet Protocol address of a second instance of the session management function in the set of instances of the session management function; and Based on the first information, a protocol session-related message is provided to one of the set of instances of the session management function.
Citation Information
Patent Citations
PFCP connection processing method, device, network element, system and storage medium
CN109167670A
