Network functions for coordination of compute PDU sessions
The integration of compute nodes with the mobile network in the 6G mobile compute network architecture addresses the challenge of supporting compute-intensive applications by enabling efficient resource management and deterministic compute networking, ensuring reliable performance for 6G services.
Patent Information
- Application Number
- PCT/EP2023/062650
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-11
- Publication Date
- 2024-11-14
AI Technical Summary
Current network designs fail to reliably support compute-intensive applications like extended reality and AI/ML due to separate and loosely integrated networking and computing approaches, which cannot meet the high computation requirements and low latency demands of 6G services.
A 6G mobile compute network architecture is proposed, integrating distributed compute nodes with the mobile network for tight coordination of computing and communication resources, using new network functions for monitoring and control of compute resources and serial/parallel processing, enabling deterministic compute networking.
This integration allows for efficient management and orchestration of networking and computing resources, supporting complex compute-intensive tasks with required latency and performance, ensuring reliable operation for future 6G applications.
Smart Images

Figure EP2023062650_14112024_PF_FP_ABST
Abstract
Description
[0001] NETWORK FUNCTIONS FOR COORDINATION OF COMPUTE PDU SESSIONS
[0002] TECHNICAL FIELD
[0003] Examples of the invention relate to network functions in a communication system for coordination of compute packet data unit (PDU) sessions. Furthermore, examples of the invention also relate to corresponding methods and a computer program.
[0004] BACKGROUND
[0005] High compute-intensive application will emerge in 6G. Immersive services such as extended reality (XR) and holograms for encoding / decoding / rendering media frames, and digital replicas, as well as complex artificial intelligence (Al) / machine learning (ML)-based application for layered processing are examples that require high computation capabilities. Hence, the ultimate user experience will not be determined by fulfilling networking performance requirements only but also by excellent and reliable computing performance. The current separate or loosely integrated networking and computing design approach will not succeed to support such compute-intensive use cases reliably. For example, the required computation capabilities for XR application can be more than 10 times as big as what is required in the 5G edge application, while the required latency for future 6G application can be less than a few times as small as what is required in the 5G ultra-reliable low latency communication (URLLC) application.
[0006] An objective of examples of the invention is to provide a solution which mitigates or solves the drawbacks and problems of conventional solutions.
[0007] Another objective of examples of the invention is to provide integrated computing and communication capabilities and manage networking and computing resources efficiently.
[0008] The above and further objectives are solved by the subject matter of the independent claims. Further examples of the invention can be found in the dependent claims.
[0009] According to a first aspect of the invention, the above mentioned and other objectives are achieved with a session management function, SMF, for a communication system, the SMF being configured to: receive a packet data unit, PDU, session create request from an access and mobility management function, AMF, the PDU session create request being associated with an establishment of a PDU session for a client device and indicating a requested resource type for the PDU session; select a compute coordination function, CCF, based on the PDU session create request; and transmit a coordination request to the selected CCF, the coordination request indicating the requested resource type.
[0010] An advantage of the SMF according to the first aspect is that a PDU session that requires computing and communication capabilities is allowed to be served through a new user plane function with appropriate compute resource coordination support. Also, an PDU session not requiring computing capabilities can be supported through the existing user plane function. Therefore, technology evolution for both user plane domains can be achieved independently and different types of PDU session can be efficiently managed.
[0011] In an implementation form of a SMF according to the first aspect, the requested resource type indicates a network resource type and / or a computing resource type for the PDU session.
[0012] An advantage with this implementation form is that the SMF can identify what additional network functions are needed to support the PDU session. Based on the identified requested type of resources and capabilities, the SMF can discover and select the needed network functions. In case a computing resource type is indicated, the CCF selection can be performed.
[0013] In an implementation form of a SMF according to the first aspect, the PDU session create request further indicates a slice / service type, SST, for the PDU session.
[0014] An advantage with this implementation form is that the SMF can identify whether the PDU session needs to be established over CF(s) as there may be compute-centric features to be supported.
[0015] In an implementation form of a SMF according to the first aspect, the SMF according is configured to: receive a coordination response from the selected CCF, the coordination response indicating a list of candidate compute functions, CFs, for the PDU session; select one or more CFs among the list of candidate CFs based on the coordination response; and transmit a coordination notification request to the selected CCF, the coordination notification request indicating the one or more selected CFs.
[0016] An advantage with this implementation form is that the traditional and unique role of selecting a user plane function by the SMF can be kept in the selection of a CF which includes user plane functionality with compute service function(s). Therefore, the role of computing-related network functions, i.e., compute capabilities monitoring, coordination, and compute resource reservation, can be clearly distinguished from networking related network functions.
[0017] In an implementation form of a SMF according to the first aspect, the coordination response further indicates a monitored compute performance and / or a predicted compute performance of the candidate CFs.
[0018] An advantage with this implementation form is that the received information can be used to further determine the optimal CF by using the monitored network performance and / or the predicted network performance of the candidate CFs. As a result, one or multiple CFs that fulfill the required networking and computing performance for the PDU session can be determined by the SMF.
[0019] In an implementation form of a SMF according to the first aspect, the coordination response further indicates a compute service function, CSF, of a radio access network, RAN, associated with the PDU session.
[0020] An advantage with this implementation form is that the indicated information can provide a flexibility for the SMF to determine a PDU session path in terms of fulfilling the network performance and resource availability.
[0021] In an implementation form of a SMF according to the first aspect, the coordination notification request further indicates whether to use the CSF of the RAN or not.
[0022] An advantage with this implementation form is that the SMF can clearly identify to the CCF whether the RAN will be included in the PDU session path and compute resource reservation procedure should be performed. In an implementation form of a SMF according to the first aspect, the SMF is configured to: receive a coordination notification response from the selected CCF, the coordination notification response indicating a compute resource reservation for the PDU session; determine a flow handling rule for the PDU session based on the coordination notification response; and transmit a session establishment / modification request to the one or more selected CFs, the session establishment / modification request indicating the flow handling rule for the PDU session.
[0023] An advantage with this implementation form is that the role of network control and compute coordination can be separately managed. Therefore, any mutual intervention or conflict between traditional networking related network function and compute-related network function can be avoided. And with the sent flow handling rule, the SMF can make the CFs understand how to treat a received packet internally in association with CSFs running inside the CFs.
[0024] In an implementation form of a SMF according to the first aspect, the SMF is configured to: receive a session establishment / modification response from the one or more selected CFs, the session establishment / modification response indicating an acknowledgement of the flow handling rule for the PDU session.
[0025] An advantage with this implementation form is that the SMF can clearly confirm whether the flow handling rule information for the PDU session is successfully installed in the one or more selected CFs. Therefore, a more reliable networking operation can be expected.
[0026] In an implementation form of a SMF according to the first aspect, the SMF is configured to: transmit a PDU session request to the RAN, the PDU session request indicating the flow handling rule for the PDU session.
[0027] An advantage with this implementation form is that the SMF can make the RAN understand how to treat a received packet internally in association with CSFs running inside the RAN upon the selection of using CSFs in the RAN.
[0028] In an implementation form of a SMF according to the first aspect, the SMF is configured to: receive a PDU session response from the RAN, the PDU session response indicating an acknowledgement with accepted and / or rejected quality-of-service flow identifier, QFI, for the flow handling rule. An advantage with this implementation form is that the SMF can identify that the RAN can support the required QoS requirement. Therefore, the SMF can confirm that the required QoS can be fulfilled for the PDU session. And the SMF can confirm that the flow handling rule information for the PDU session is successfully installed in the RAN. Therefore, a more reliable networking operation can be expected.
[0029] According to a second aspect of the invention, the above mentioned and other objectives are achieved with a CCF for a communication system, the CCF being configured to: receive a coordination request from a SMF, the coordination request being associated with a PDU session for a client device and indicating a requested resource type for the PDU session; determine a list of candidate CFs for the PDU session based on the coordination request; and transmit a coordination response to the SMF, the coordination response indicating the list of candidate CFs.
[0030] An advantage of the CCF according to the second aspect is that the computing related jobs can be separately managed. Therefore, any mutual intervention or conflict between traditional networking related network functions and compute-related network functions can be avoided.
[0031] In an implementation form of a CCF according to the second aspect, the CCF is configured to: determine the list of candidate CFs for the PDU session further based on a monitored compute performance and / or a predicted compute performance of a set of CFs.
[0032] An advantage with this implementation form is that it can keep the SMF transparent when it comes to obtaining computing-related performance information as it can be handled by the CCF. Therefore, it can make the architecture design and evolution for the integrated computing and communication simple and independent.
[0033] In an implementation form of a CCF according to the second aspect, the coordination response further indicates a monitored compute performance and / or a predicted compute performance of the candidate CFs.
[0034] An advantage with this implementation form is that no functional extension related to computing-related performance collection is required in the SMF, so that the SMF can keep focusing on support of networking related control and the independent evolution of the SMF can also be kept.
[0035] In an implementation form of a CCF according to the second aspect, the requested resource type indicates a network resource type and / or a computing resource type for the PDU session.
[0036] An advantage with this implementation form is that it allows the CCF to check and identify what type of computing resource and capabilities is needed and available. Therefore, it helps the CCF to coordinate the distributed compute resource.
[0037] In an implementation form of a CCF according to the second aspect, the coordination request further indicates an SST for the PDU session.
[0038] An advantage with this implementation form is that the CCF can identify what level of computing performance requirement fulfillment is needed. Therefore, the CCF can check available network slice instance which can support the required features from the indicated SST.
[0039] In an implementation form of a CCF according to the second aspect, the CCF is configured to: receive a coordination notification request from the SMF, the coordination notification request indicating one or more selected CFs for the PDU session; reserve a compute resource for the PDU session based on the coordination notification request; and transmit a coordination notification response to the SMF, the coordination notification response indicating the compute resource reservation for the PDU session.
[0040] An advantage with this implementation form is that it allows the CCF to focus on the compute- related operation such as the reservation of compute service resources. Therefore, independent evolution design of the CCF can be made without any conflict with traditional networking-related network functions such as the SMF.
[0041] In an implementation form of a CCF according to the second aspect, the coordination response further indicates a CF of a RAN associated with the PDU session. An advantage with this implementation form is that it allows the CCF to suggest all available RAN and CFs that have the required CSFs for the PDU session. Therefore, the SMF can have more flexibility to determine the networking path with the required network resource.
[0042] In an implementation form of a CCF according to the second aspect, the coordination notification request further indicates whether to use the CF of the RAN or not.
[0043] An advantage with this implementation form is that the CCF can be clearly informed whether to confirm the assignment of the CSF resource for the PDU session.
[0044] According to a third aspect of the invention, the above mentioned and other objectives are achieved with an AMF or a communication system, the AMF being configured to: receive a PDU session establishment request from a client device, the PDU session establishment request being associated with an establishment of a PDU session for the client device and indicating a requested resource type for the PDU session; select a SMF based on the PDU session establishment request; and transmit a PDU session create request to the selected SMF, the PDU session create request indicating the requested resource type.
[0045] An advantage of the AMF according to the third aspect is that a suitable SMF supporting PDU sessions of the requested resource type can be selected since it cannot be assumed that every SMF has the same capability. Therefore, without a change of SMF during the session, except a usual reason such as mobility or policy change, initially selected SMF can serve the requested PDU session until the PDU session is terminated.
[0046] In an implementation form of an AMF according to the third aspect, the requested resource type indicates a network resource type and / or a computing resource type for the PDU session.
[0047] An advantage with this implementation form is that the AMF can use the information to find a SMF supporting the indicated resource type.
[0048] In an implementation form of an AMF according to the third aspect, the PDU session create request further indicates an SST for the PDU session.
[0049] An advantage with this implementation form is that the AMF can use the information to find a SMF supporting the indicated SST. According to a fourth aspect of the invention, the above mentioned and other objectives are achieved with a CF for a communication system, the CF being configured to: receive a session establishment / modification request from a SMF, the session establishment / modification request indicating a flow handling rule associated with an establishment of a PDU session for a client device; and process received packets for the PDU session based on the session establishment / modification request.
[0050] An advantage of the CF according to the fourth aspect is that CFs can be instructed on how a received packet associated with the PDU session should be processed. Therefore, the packet can be forwarded to and processed in the right CSF(s), determined by the CCF, within the CFs.
[0051] In an implementation form of a CF according to the fourth aspect, the CF is configured to: transmit a session establishment / modification response to the SMF, the session establishment / modification response indicating an acknowledgement of the flow handling rule for the PDU session.
[0052] An advantage with this implementation form is that the CF can clearly identify to the SMF whether the flow handling rule information has been successfully installed or if there was any flow handling rule that couldn’t be applied or installed in the CF. Therefore, the SMF can address if there is any issue in the installation process.
[0053] According to a fifth aspect of the invention, the above mentioned and other objectives are achieved with a method for a SMF, the method comprises: receiving a PDU session create request from an AMF, the PDU session create request being associated with an establishment of a PDU session for a client device and indicating a requested resource type for the PDU session; selecting a CCF based on the PDU session create request; and transmitting a coordination request to the selected CCF, the coordination request indicating the requested resource type.
[0054] The method according to the fifth aspect can be extended into implementation forms corresponding to the implementation forms of the SMF according to the first aspect. Hence, an implementation form of the method comprises the feature(s) of the corresponding implementation form of the SMF. The advantages of the methods according to the fifth aspect are the same as those for the corresponding implementation forms of the SMF according to the first aspect.
[0055] According to a sixth aspect of the invention, the above mentioned and other objectives are achieved with a method for a CCF, the method comprises: receiving a coordination request from a SMF, the coordination request being associated with a PDU session for a client device and indicating a requested resource type for the PDU session; determining a list of candidate CFs for the PDU session based on the coordination request; and transmitting a coordination response to the SMF, the coordination response indicating the list of candidate CFs.
[0056] The method according to the sixth aspect can be extended into implementation forms corresponding to the implementation forms of the CCF according to the second aspect. Hence, an implementation form of the method comprises the feature(s) of the corresponding implementation form of the CCF.
[0057] The advantages of the methods according to the sixth aspect are the same as those for the corresponding implementation forms of the CCF according to the second aspect.
[0058] According to a seventh aspect of the invention, the above mentioned and other objectives are achieved with a method for an AMF, the method comprises: receiving a PDU session establishment request from a client device, the PDU session establishment request being associated with an establishment of a PDU session for the client device and indicating a requested resource type for the PDU session; selecting a SMF based on the PDU session establishment request; and transmitting a PDU session create request to the selected SMF, the PDU session create request indicating the requested resource type.
[0059] The method according to the seventh aspect can be extended into implementation forms corresponding to the implementation forms of the AMF according to the third aspect. Hence, an implementation form of the method comprises the feature(s) of the corresponding implementation form of the AMF. The advantages of the methods according to the seventh aspect are the same as those for the corresponding implementation forms of the AMF according to the third aspect.
[0060] According to an eighth aspect of the invention, the above mentioned and other objectives are achieved with a method for a CF, the method comprises: receiving a session establishment / modification request from a SMF, the session establishment / modification request indicating a flow handling rule associated with an establishment of a PDU session for a client device; and processing received packets for the PDU session based on the session establishment / modification request.
[0061] The method according to the eighth aspect can be extended into implementation forms corresponding to the implementation forms of the CF according to the fourth aspect. Hence, an implementation form of the method comprises the feature(s) of the corresponding implementation form of the CF.
[0062] The advantages of the methods according to the eighth aspect are the same as those for the corresponding implementation forms of the CF according to the fourth aspect.
[0063] Examples of the invention also relate to a computer program, characterized in program code, which when run by at least one processor causes the at least one processor to execute any method according to examples of the invention. Further, examples of the invention also relate to a computer program product comprising a computer readable medium and the mentioned computer program, wherein the computer program is included in the computer readable medium, and may comprises one or more from the group of: read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), flash memory, electrically erasable PROM (EEPROM), hard disk drive, etc.
[0064] Further applications and advantages of examples of the invention will be apparent from the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS
[0065] The appended drawings are intended to clarify and explain different examples of the invention, in which:
[0066] - Fig. 1 shows a SMF according to an example of the invention;
[0067] - Fig. 2 shows a flow chart of a method for a SMF according to an example of the invention;
[0068] - Fig. 3 shows a CCF according to an example of the invention;
[0069] - Fig. 4 shows a flow chart of a method for a CCF according to an example of the invention;
[0070] - Fig. 5 shows an AMF according to an example of the invention;
[0071] - Fig. 6 shows a flow chart of a method for an AMF according to an example of the invention;
[0072] - Fig. 7 shows a CF according to an example of the invention;
[0073] - Fig. 8 shows a flow chart of a method for a CF according to an example of the invention;
[0074] - Fig. 9 shows a communication system according to an example of the invention;
[0075] - Fig. 10 shows a communication system according to an example of the invention;
[0076] - Fig. 11 shows signaling for coordination of compute resources according to an example of the invention;
[0077] - Fig. 12 shows signaling for PDU session establishment / modification according to an example of the invention;
[0078] - Fig. 13 shows signaling for SMF selection by an AMF according to an example of the invention;
[0079] - Fig. 14 shows a procedure for a compute PDU session establishment according to an example of the invention; and
[0080] - Fig. 15 shows a procedure for a compute PDU session establishment according to an example of the invention.
[0081] DETAILED DESCRIPTION
[0082] To address both intensive computation and very low latency requirements for computeintensive application, the computation infrastructure should be tightly integrated with mobile network architecture. Therefore, it is important to manage networking and computing resources natively and orchestrate them flexibly in 6G network architecture so that such challenging applications can be sustainably supported.
[0083] According to examples of the invention a 6G mobile compute network (MCN) architecture is proposed, enabling distributed compute nodes and the mobile network to be tightly integrated for providing integrated computing and communication capabilities, to deal with complex computing tasks in a deterministic manner. New network functions that facilitate monitoring and control of distributed compute resources and coordination of serial / parallel compute processing for a compute application are provided.
[0084] Fig. 1 shows a SMF 100 according to an example of the invention. In the example shown in Fig. 1 , the SMF 100 comprises a processor 101 , a transceiver 103 and a memory 105. The processor 101 is coupled to the transceiver 103 and the memory 105 by communication means known in the art. The SMF 100 may be configured for wired communications in a communication system. The wired communication capability may be provided with a wired communication interface 107, e.g., coupled to the transceiver 103, over which the SMF 100 may communicate with other nodes in a network NW.
[0085] The processor 101 may be referred to as one or more general-purpose central processing units (CPUs), one or more digital signal processors (DSPs), one or more application-specific integrated circuits (ASICs), one or more field programmable gate arrays (FPGAs), one or more programmable logic devices, one or more discrete gates, one or more transistor logic devices, one or more discrete hardware components, or one or more chipsets. The memory 105 may be a read-only memory, a random access memory (RAM), or a non-volatile RAM (NVRAM). The transceiver 103 may be a transceiver circuit, a power controller, or an interface providing capability to communicate with other communication modules or communication devices, such as network nodes and network servers. The transceiver 103, memory 105 and / or processor 101 may be implemented in separate chipsets or may be implemented in a common chipset. That the SMF 100 is configured to perform certain actions can in this disclosure be understood to mean that the SMF 100 comprises suitable means, such as e.g., the processor 101 and the transceiver 103, configured to perform the actions.
[0086] According to examples of the invention the SMF 100 is configured to receive a PDU session create request 102 from an AMF 500, the PDU session create request 102 being associated with an establishment of a PDU session for a client device 810 and indicating a requested resource type for the PDU session. The SMF 100 is further configured to select a CCF 300 based on the PDU session create request 102. The SMF 100 is further configured to transmit a coordination request 104 to the selected CCF 300, the coordination request 104 indicating the requested resource type. Fig. 2 shows a flow chart of a corresponding method 200 which may be executed in a SMF 100, such as the one shown in Fig. 1. The method 200 comprises receiving 202 a PDU session create request 102 from an AMF 500, the PDU session create request 102 being associated with an establishment of a PDU session for a client device 810 and indicating a requested resource type for the PDU session. The method 200 further comprises selecting 204 a CCF 300 based on the PDU session create request 102. The method 200 further comprises transmitting 206 a coordination request 104 to the selected CCF 300, the coordination request 104 indicating the requested resource type.
[0087] Fig. 3 shows a CCF 300 according to an example of the invention. In the example shown in Fig. 3, the CCF 300 comprises a processor 302, a transceiver 304 and a memory 306. The processor 302 is coupled to the transceiver 304 and the memory 306 by communication means known in the art. The CCF 300 may be configured for wired communications in a communication system. The wired communication capability may be provided with a wired communication interface 308 e.g., coupled to the transceiver 304, over which the CCF 300 may communicate with other nodes in a network NW.
[0088] The processor 302 may be referred to as one or more general-purpose CPUs, one or more DSPs, one or more ASICs, one or more FPGAs, one or more programmable logic devices, one or more discrete gates, one or more transistor logic devices, one or more discrete hardware components, one or more chipsets. The memory 306 may be a read-only memory, a RAM, or a NVRAM. The transceiver 304 may be a transceiver circuit, a power controller, or an interface providing capability to communicate with other communication modules or communication devices. The transceiver 304, the memory 306 and / or the processor 302 may be implemented in separate chipsets or may be implemented in a common chipset. That the CCF 300 is configured to perform certain actions can in this disclosure be understood to mean that the CCF 300 comprises suitable means, such as e.g., the processor 302 and the transceiver 304, configured to perform the actions.
[0089] According to examples of the invention the CCF 300 is configured to receive a coordination request 104 from a SMF 100, the coordination request 104 being associated with a PDU session for a client device 810 and indicating a requested resource type for the PDU session. The CCF 300 is further configured to determine a list of candidate CFs 700 for the PDU session based on the coordination request 104. The CCF 300 is further configured to transmit a coordination response 106 to the SMF 100, the coordination response 106 indicating the list of candidate CFs 700. Fig. 4 shows a flow chart of a corresponding method 400 which may be executed in a CCF 300, such as the one shown in Fig. 3. The method 400 comprises receiving 402 a coordination request 104 from a SMF 100, the coordination request 104 being associated with a PDU session for a client device 810 and indicating a requested resource type for the PDU session. The method 400 further comprises determining 404 a list of candidate CFs 700 for the PDU session based on the coordination request 104. The method 400 further comprises transmitting 406 a coordination response 106 to the SMF 100, the coordination response106 indicating the list of candidate CFs 700.
[0090] Fig. 5 shows an AMF 500 according to an example of the invention. In the example shown in Fig. 5, the AMF 500 comprises a processor 502, a transceiver 504 and a memory 506. The processor 502 is coupled to the transceiver 504 and the memory 506 by communication means known in the art. The AMF 500 may be configured for wired communications in a communication system. The wired communication capability may be provided with a wired communication interface 508 e.g., coupled to the transceiver 504, over which the AMF 500 may communicate with other nodes in a network NW.
[0091] The processor 502 may be referred to as one or more general-purpose CPUs, one or more DSPs, one or more ASICs, one or more FPGAs, one or more programmable logic devices, one or more discrete gates, one or more transistor logic devices, one or more discrete hardware components, one or more chipsets. The memory 506 may be a read-only memory, a RAM, or a NVRAM. The transceiver 504 may be a transceiver circuit, a power controller, or an interface providing capability to communicate with other communication modules or communication devices, such as network nodes and network servers. The transceiver 504, the memory 506 and / or the processor 502 may be implemented in separate chipsets or may be implemented in a common chipset. That the AMF 500 is configured to perform certain actions can in this disclosure be understood to mean that the AMF 500 comprises suitable means, such as e.g., the processor 502 and the transceiver 504, configured to perform the actions.
[0092] According to examples of the invention the AMF 500 is configured to receive a PDU session establishment request 120 from a client device 810, the PDU session establishment request 120 being associated with an establishment of a PDU session for the client device 810 and indicating a requested resource type for the PDU session. The AMF 500 is further configured to select a SMF 100 based on the PDU session establishment request 120 and transmit a PDU session create request 102 to the selected SMF 100, the PDU session create request 102 indicating the requested resource type. Fig. 6 shows a flow chart of a corresponding method 600 which may be executed in an AMF 500, such as the one shown in Fig. 5. The method 600 comprises receiving 602 a PDU session establishment request 120 from a client device 810, the PDU session establishment request 120 being associated with an establishment of a PDU session for the client device 810 and indicating a requested resource type for the PDU session. The method 600 further comprises selecting 604 a SMF 100 based on the PDU session establishment request 120 and transmitting 606 a PDU session create request 102 to the selected SMF 100, the PDU session create request 102 indicating the requested resource type.
[0093] Fig. 7 shows a CF 700 according to an example of the invention. In the example shown in Fig. 7, the CF 700 comprises a processor 702, a transceiver 704 and a memory 706. The processor 702 is coupled to the transceiver 704 and the memory 706 by communication means known in the art. The CF 700 may be configured for wired communications in a communication system. The wired communication capability may be provided with a wired communication interface 708 e.g., coupled to the transceiver 704, over which the CF 700 may communicate with other nodes in a network NW.
[0094] The processor 702 may be referred to as one or more general-purpose CPUs, one or more DSPs, one or more ASICs, one or more FPGAs, one or more programmable logic devices, one or more discrete gates, one or more transistor logic devices, one or more discrete hardware components, one or more chipsets. The memory 706 may be a read-only memory, a RAM, or a NVRAM. The transceiver 704 may be a transceiver circuit, a power controller, or an interface providing capability to communicate with other communication modules or communication devices, such as network nodes and network servers. The transceiver 704, the memory 706 and / or the processor 702 may be implemented in separate chipsets or may be implemented in a common chipset. That the CF 700 is configured to perform certain actions can in this disclosure be understood to mean that the CF 700 comprises suitable means, such as e.g., the processor 702 and the transceiver 704, configured to perform the actions.
[0095] According to examples of the invention the CF 700 is configured to receive a session establishment / modification request 112 from a SMF 100, the session establishment / modification request 112 indicating a flow handling rule associated with an establishment of a PDU session for a client device 810. The CF 700 is further configured to process received packets for the PDU session based on the session establishment / modification request 112. Fig. 8 shows a flow chart of a corresponding method 800 which may be executed in a CF 700, such as the one shown in Fig. 7. The method 800 comprises receiving 802 a session establishment / modification request 112 from a SMF 100, the session establishment / modification request 112 indicating a flow handling rule associated with an establishment of a PDU session for a client device 810. The method 800 further comprises processing 804 received packets for the PDU session based on the session establishment / modification request 112.
[0096] The overall framework and vision for the 6G MCN according to examples of the invention enables collaboration among mobile network, edge, and cloud to address future challenging compute-intensive tasks. It allows compute resources over an integrated networking and computing infrastructure to be coordinated based on an application demand and enables deterministic compute networking, so that the required latency can be fulfilled despite the complexity of compute processing.
[0097] Mobile network, edge, and cloud may be working based on a common platform for MCN, where an MCN gateway function and an MCN forwarding function may be implemented for operator- driven compute service chaining control. A forwarding control function and compute management and coordination function may be left to an application provider but it may also be implemented in the MCN infrastructure.
[0098] There are a number of potential compute service scenarios for the MCN framework architecture of which four scenarios are described below. The compute service scenarios may describe how the mobile network, the edge, and the cloud are required to work together in order to address the compute requirement. Compute service capability may be provided at the UE, the mobile network, the edge, the cloud and the provided compute service capabilities can be the same or different.
[0099] Scenario 1 : Serial multi-edge
[0100] In scenario 1 , a compute application is mainly served at multiple edges where there are a main edge and supportive edge node(s). When the main edge does not have sufficient resources available to complete the requested compute task in time, the main edge may request sub processing from one or more supportive edge nodes. Scenario 2: Parallel multi-edge
[0101] In scenario 2, a compute task is serviced at two different edge nodes at the same time and each edge may be dedicated to a certain work processing. For example, one edge may be dedicated to image processing while the other edge may be dedicated to audio processing. In that case, the divide-and-conquer approach may be used. The network may then have the capability to split and merge the compute application session for parallel compute processing in time.
[0102] Scenario 3: Serial multi-edge-cloud
[0103] In scenario 3, a sequential compute processing may be performed for a given compute task, with some tasks being performed by the edge and some by the cloud. In case of a XR application with very low latency requirement, compute processing for quick response may be provided by the edge to display information with lightweight processing, while processing of complicated compute task may be provided by the cloud.
[0104] Scenario 4: Hybrid multi-edge-cloud
[0105] Scenario 4 is a multi-edge-cloud scenario where the mobile network, the edge, and the cloud are involved in the overall compute processing. In scenario 4, a compute task may be split into multiple edges for intermediate processing, and then the output of each processing may be sent to the cloud for final processing. This scenario may be suitable e.g., for AI / ML-based layered processing.
[0106] A short description of compute services to be expected in MCN is provided below. This indicates the type of compute processing to be expected for collaborative and deterministic compute processing. The described compute processing may be suitable to be deployed in the network and / or the edge and / or the cloud, depending on compute application requirements.
[0107] Pre-processing: a huge amount of raw data for AI / ML may be pre-processed in the network, in order to reduce a lot of network bandwidth. The pre-processing may be beneficial for AI / ML applications to improve the prediction accuracy by filtering out highly deviating data.
[0108] Packet replication / elimination / ordering function (PREOF): PREOF may be important to make the network deterministic so that data packets can be reliably delivered. PREOF may be natively supported for deterministic compute networking. Network coding: Network coding allows packet manipulation such as encoding, recoding, decoding for reliable, robust and low-latency data delivery. Network coding may assist to support reliable and low networking capabilities.
[0109] Intermediate processing: Part of the layered processing for AI / ML applications may be implemented not only in the edge or cloud but also inside the mobile network.
[0110] Application-specific processing: The edge and cloud usually provide application-specific processing but some of the processing may also be designed inside the mobile network. For example, whole application-specific processing or part of processing to support simultaneous localization and mapping (SLAM), XR-specific compute processing may also be implemented in the mobile network.
[0111] Fig. 9 shows a communication system 900 according to an example of the invention in which the communication system 900 is a 6G MCN architecture underlay model. The 6G MCN architecture underlay model may be based on the 5G reference architecture for collaborative and deterministic compute processing. With reference to Fig. 9, the new network functions introduced for the proposed MCN architecture may include the CCF 300, the CF 700, a compute data analytics function (CDAF) and a compute mobile data network (CMDN). In addition, the functionality of existing network functions such as the network exposure function (NEF), the session management function (SMF), the network resource function (NRF), the application function (AF) and / or the radio access network (RAN) may be extended to support compute-centric application sessions.
[0112] The basic philosophy behind the proposed MCN architecture as underlay model may be as follows:
[0113] 1) A compute PDU session, i.e. , a PDU session using compute resources, may be treated separately from the existing PDU session treatment. A compute PDU session may be established through a new different user plane function (UPF) which is instructed by new compute-related control plane functionality, while the existing PDU session may still be served through the traditional network functions such as the RAN and the UPF.
[0114] 2) Compute service functions (CSFs) may be distributed across the mobile network, the edge, the cloud but may be managed and coordinated by the CCF 300.
[0115] 3) A CSF may also be provided in the RAN 750. So, the functionality of the traditional RAN may be extended to include CSF(s). 4) Exposing compute capabilities as well as network capabilities may be treated in the 6G core network.
[0116] This separate session treatment may minimize the impact on the current 5G architecture and allow an independent network evolution for compute-centric application sessions.
[0117] The CCF 300 may handle compute resource management, e.g., type of compute-related resource, total amount of compute resource, and reservation of specific compute resource. The CCF 300 may deal with compute coordination at the CFs 700, and the edges for compute sessions. The CCF 300 may e.g., select target nodes, i.e., CF(s) 700, CF(s) 700 and edge node(s), or edges node(s), and role for compute services. With reference to Fig. 9, the CCF 300 may instruct the RAN 750 and the CF 700 to perform specific computation through Na / Nb interfaces, based on a compute service graph provided by an AF+. The CCF 300 may also instruct the CF 700 and the CMDN on how to treat / forward data packets. For scalability, the CCF 300 may be further decomposed with same / different sub functions. For structured CCFs 300, the same interface, i.e., the Nb interface may be used.
[0118] The CF 700 may provide user plane forwarding functionality to treat a compute application session. In addition, compute plane part, e.g., pre-processing, packet replication / elimination / (re-)ordering, packet manipulation for network coding, intermediate processing for AI / ML sessions may be provided. With reference to Fig. 9, the CF 700 may be instructed by the SMF 100 via the Nc interface for session management and control, as well as by the CCF 300 via the Nb interface for compute resource management and coordination, and compute resource reservation. Traffic steering policy for compute service path and compute service steering policy for compute service coordination may be provided from the SMF 100 and the CCF 300, respectively, enabling flexible and coordinated compute session treatment. A Nran interface may allow service based architecture (SBA)-based communication among necessary network functions, so overall compute resource / service coordination can be easier. The Nran interface has been proposed in the 5G IA White Paper “The 6G Architecture Landscape - European Perspective” v1.0, December 2022.
[0119] The CDAF may interact with edge analytics and cloud analytics functions or collects compute performance related data which can be obtained directly from the CF 700, the CMDN, the CCF 300, and the AF+ through the NEF+. The CDAF can provide the compute performance related analytics to the CCF 300. The CCF 300 may obtain the network performance analytics from network intelligence function such as network data analytics function (NWDAF). Based on the obtained analytics information from the CDAF and the NWDAF, the CCF 300 may select appropriate compute nodes and coordinate them for an application task. The CDAF is here described by focusing on its logical functionality for compute performance related data analytics. This functionality can also be implemented in other relevant network intelligence function such as the NWDAF.
[0120] The CMDN basically refers to an edge and cloud. However, user plane forwarding functionality may be provided in the CMDN. This forwarding functionality may be programmable. With reference to Fig. 9, the compute resource of the CMDN may be managed by the CCF 300 via the Nf interface.
[0121] The SMF 100 provides extended functionality compared to the 5G SMF. The SMF 100 may instruct a PDU session requiring CSF(s) running over CFs 700. Basic session management functionality may be provided. With reference to Fig. 9, the CSF(s) may be instructed by the CCF 300 via the Nb interface.
[0122] The NEF+ may provide extended functionality compared to the 5G NEF. The NEF+ may support compute resource monitoring application programming interface (API) and compute capabilities exposure. The NEF+ may receive a request from internal and / or external AF+ to check compute resource availability within the mobile network. A request for compute resource coordination for a specific compute task may also be received.
[0123] The NRF+ may provide extended functionality compared to the 5G NRF. The NRF+ may support service discovery for compute-related functions. The NRF+ may accommodate the compute- related network functions to be managed so that any network function discovery for 6G MCN is feasible.
[0124] The AF+ may provide extended functionality compared to the 5G AF. The AF+ may provide compute- related service request. The request may include a level of compute-related performance to be fulfilled in addition to the request for fulfilling the existing QoS requirement. Requesting the compute-related performance fulfillment may be made by a separate request or a new request that accommodates network requirements and compute requirements in an integrated manner. The scope of the request extension may be considered over all the service requests initiated by the AF, described in TS 23.501 and TS 23.502. The RAN 750 provides extended functionality compared to the 5G RAN. The RAN 750 may provide compute service with a CSF. It needs to interact with other compute relevant network functions. To forward a data packet for a compute application session, a tunnel or forwarding path may be to establish between the RAN 750 and the CF 700. Therefore, the RAN 750 may be instructed by the SMF 100 and / or the CCF 300.
[0125] Fig. 10 shows a communication system 900 according to an example of the invention in which the communication system 900 is a 6G MCN architecture overlay model. The 6G MCN architecture overlay model may be based on the 5G reference architecture for collaborative and deterministic compute processing. The basic philosophy behind the proposed MCN architecture as overlay model may be as follows:
[0126] 1) A compute service platform may exist as overlay network. In an UPF perspective, the compute PDU session may be directed to a new data network (DN). Therefore, a much lower impact for compute service support on the existing 5G network architecture can be expected.
[0127] 2) The collaboration among compute nodes, i.e. , the CF 700 and the CMDN, may be limited as the compute service network is provided on top of the existing 5G network.
[0128] 3) A benefit is that, without a big impact on the existing network, more specific functions and interfaces can be created towards an independent evolution of the compute service platform.
[0129] In the overlay model, the CCF 300, the CF 700, the CDAF, and the CMDN are proposed to be deployed and may provide similar functionality to the functionality described for the underlay model. However, the CF 700 may not be connected directly to the RAN. With reference to Fig. 10, the PDU session that requires computing service may be forwarded to the CF 700 by the UPF. The NRF+, the NEF+, the AF+ may be considered in the overlay model, but the SMF and the RAN may be unaware of the compute service.
[0130] Standardized slice / service type (SST) values provide a way for establishing global interoperability for compute-centric or compute-related application sessions so that public land mobile networks (PLMNs) can support the roaming use case more efficiently for the most commonly used SSTs. In-network computing processing can be provided through the CF 700 independently or together with a local DN. When in-network computing capability is required for a PDU session, a new type of SST is proposed to be defined so that the network slice that accommodates the relevant networking and computing capabilities can be initiated, based on their requirements. The proposed new SST values may also be used to distinguish whether to forward a traffic session to e.g., the UPF or the CF 700. For generic compute-related service, a new SST value 6 is proposed to be introduced as an SST which is suitable for handling of generic in-network computing communications. For highly compute-centric communication with low latency (HCLLC), a new SST value 7 is proposed to be defined as an SST which is suitable for handling of HCLLC communications.
[0131] Table 1 below shows the existing SST values 1 to 5 and the new SST values 6 and 7 proposed according to examples of the invention.
[0132] Alternatively, with the SST values defined in TS 23.501 , features that can handle in-network computing communication could be defined using slice differentiator (SD), which is optional information that complements the SST(s) to differentiate amongst multiple network slices of the same SST.
[0133] Fig. 11 shows signaling between the SMF 100 and the CCF 300 for coordination of compute resources according to an example of the invention.
[0134] In step 1 in Fig. 11 , the SMF 100 receive a PDU session create request 102 from an AMF 500. The PDU session create request 102 is associated with an establishment of a PDU session for a client device 810, as further described below with reference to Fig. 13. The PDU session create request 102 indicates a requested resource type for the PDU session. The requested resource type may indicate a network resource type and / or a computing resource type for the PDU session and hence indicate to the SMF 100 whetherthe PDU session requests computing resources or not. The requested resource type may be indicated e.g., with index numbers.
[0135] The PDU session create request 102 may further indicates an SST for the PDU session. As described above the SST may indicate the slice and / or service type of the requested PDU session, e.g., if the PDU session is associated with a compute-related service and if so whether the compute-related service is generic or highly compute-centric. The SST may e.g., be indicated as single network slice selection assistance information (S-NSSAI) according to the 3GPP standard.
[0136] In step 2 in Fig. 11 , the SMF 100 selects a CCF 300 based on the PDU session create request 102. The SMF 100 may select a CCF 300 suitable to support the requested PDU session. The SMF 100 may e.g., select a CCF 300 which has corresponding capability to the requested resource type and / or the SST indicated in the PDU session create request 102, through a CCF 300 discovery procedure from the NRF+ that can manage the compute-related network functions.
[0137] In step 3 in Fig. 11 , the SMF 100 transmits a coordination request 104 to the selected CCF 300. The coordination request 104 indicates the requested resource type. The coordination request 104 may further indicates the SST for the PDU session. The information about the requested PDU session which the SMF 100 received in the PDU session create request 102 from the AMF 500 may hence be forwarded to the CCF 300.
[0138] The CCF 300 receives the coordination request 104 from the SMF 100. As described, the coordination request 104 is associated with the PDU session for the client device 810 and indicates the requested resource type for the PDU session and may further indicate the SST for the PDU session. From the received coordination request 104, the CCF 300 may hence obtain the requested resource type for the PDU session which may indicate the network resource type and / or the computing resource type for the PDU session, as well as the SST for the PDU session if indicated.
[0139] Based on the coordination request 104, the CCF 300 determines a list of candidate CFs 700 for the PDU session in step 4 in Fig. 11. Candidate CFs 700 may be CFs 700 which have capability and / or resources to support the requested PDU session. In examples of the invention, the CCF 300 may determine the list of candidate CFs 700 for the PDU session further based on a monitored compute performance and / or a predicted compute performance of a set of CFs 700. Thus, the CCF 300 may evaluate the monitored and / or predicted compute performance of the set of CFs 700 and include CFs 700 which have required compute resources and capabilities to support the requested PDU session in the list of candidate CFs 700.
[0140] In step 5 in Fig. 11 , the CCF 300 transmits a coordination response 106 to the SMF 100, the coordination response 106 indicating the list of candidate CFs 700. The coordination response 106 may further indicate the monitored compute performance and / or the predicted compute performance of the candidate CFs 700. For example, the CCF 300 may indicate the monitored compute performance and / or the predicted compute performance of the candidate CFs 700 which may be used by the SMF 100 to select the CFs 700.
[0141] In examples, the coordination response 106 may further indicate a CSF of a RAN 750 associated with the PDU session, i.e. , the CCF 300 may determine that a CSF of a RAN 750 may be used to provide compute resources for the PDU session. The CCF 300 may indicate the CSF of the RAN 750 if the CSF of the RAN 750 is suitable and capable to support the requested resource type and optionally SST based on monitored compute performance and / or predicted compute performance. For example, if the CSF of the RAN 750 has enough compute resources and the PDU session is associated with a low-latency service, since using compute resources in the RAN 750 can reduce latency.
[0142] The SMF 100 receives the coordination response 106 from the selected CCF 300 and hence obtains the list of candidate CFs 700 for the PDU session indicated in the coordination response 106. As described, the coordination response 106 may further indicate the monitored compute performance and / or the predicted compute performance of the candidate CFs 700 and / or a CSF 700 of a RAN 750 associated with the PDU session.
[0143] Based on the coordination response 106, the SMF 100 may select one or more CFs 700 among the list of candidate CFs 700 in step 6 in Fig. 11. In examples, the SMF 100 may select one or more CFs 700 among the list of candidate CFs 700 based on the monitored networking and computing performance and / or the predicted networking and computing performance for the candidate CFs 700. The SMF 100 can get the networking and computing performance information from the same or different network functions. In this way, the SMF 100 may select CFs 700 suitable and with capacity to support the PDU session, e.g., CFs 700 with compute resources and network resources that can support the PDU session.
[0144] The SMF 100 may further determine whether to use the CSF of the RAN 750 or not, based on the network performance prediction with and / or without the CSF of the RAN 750. Since using the RAN 750 for compute processing can reduce latency but be a little bit expensive as the RAN may have limited computing capacity. Whether to use the CSF of the RAN 750 or not may also be related to the user subscription, e.g., whether the client device 810 has priority for high computing with low latency or not.
[0145] In step 7 in Fig. 11 , the SMF 100 transmits a coordination notification request 108 to the selected CCF 300. The coordination notification request 108 indicates the one or more selected CFs 700. The coordination notification request 108 may further indicate whether to use the CSF of the RAN 750 or not.
[0146] The CCF 300 receives the coordination notification request 108 from the SMF 100 and obtains the one or more selected CFs 700 for the PDU session indicated in the coordination notification request 108. From the coordination notification request 108, the CCF 300 may further obtain the indication whether to use the CSF of the RAN 750 or not.
[0147] Based on the coordination notification request 108, the CCF 300 may reserve a compute resource for the PDU session in step 8 in Fig. 11. The CCF 300 may reserve a compute resource of coordinated CSFs in the one or more selected CFs 700 for the PDU session. The CCF 300 may further reserve a compute resource in the CSF of the RAN 750 if the coordination notification request 108 indicates that the CSF of the RAN 750 can be used.
[0148] In step 9 in Fig. 11 , the CCF 300 transmits a coordination notification response 110 to the SMF 100, the coordination notification response 110 indicating the compute resource reservation for the PDU session.
[0149] The SMF 100 receive the coordination notification response 110 from the selected CCF 300 and obtains the compute resource reservation for the PDU session indicated in the coordination notification response 110. Thus, the SMF 100 are made aware about the reserved compute resources and may proceed with the PDU session establishment / modification, as described with reference to Fig. 12. Fig. 12 shows signaling between the SMF 100 and the one or more selected CFs 700 for PDU session establishment / modification according to an example of the invention. In step 1 in Fig. 12, the SMF 100 receives a coordination notification response 110 from the CCF 300, as described with reference to Fig. 11. The coordination notification response 110 indicates the compute resource reservation for the PDU session.
[0150] Based on the coordination notification response 110, the SMF 100 determines a flow handling rule for the PDU session in step 2 in Fig. 12. The flow handling rule may provide information, e.g., in addition to forwarding action rule (FAR), on how a particular packet should be handled by considering CSFs running on the CF 700 and the RAN 750, for a compute service chaining.
[0151] In step 3 in Fig. 12, the SMF 100 transmits a session establishment / modification request 112 to the one or more selected CFs 700. The session establishment / modification request 112 indicating the flow handling rule for the PDU session.
[0152] Each CF 700 receives the session establishment / modification request 112 from the SMF 100 and hence obtains the flow handling rule for the PDU session indicated in the session establishment / modification request 112. Based on the session establishment / modification request 112, the CF 700 process received packets for the PDU session in step 4 in Fig. 12. Thus, each CF 700 starts to process received packets for the PDU session based on the flow handling rule received from the SMF 100.
[0153] As shown in step 5 in Fig. 12, the CF 700 may further transmit a session establishment / modification response 114 to the SMF 100, in response to the received session establishment / modification request 112. The session establishment / modification response 114 indicating an acknowledgement of the flow handling rule for the PDU session. The SMF 100 receives the session establishment / modification response 114 from the one or more selected CFs 700 and hence obtains the acknowledgement of the flow handling rule for the PDU session indicated in the session establishment / modification response 114.
[0154] With reference to step 6 in Fig. 12, the SMF 100 may further indicate the flow handling rule for the PDU session to the RAN 750 using a PDU session request 116. In examples, the SMF 100 may hence transmit a PDU session request 116 to the RAN 750. The PDU session request 116 indicating the flow handling rule for the PDU session. In response to the PDU session request 116, the SMF 100 may receive a PDU session response 118 from the RAN 750, as shown in step 7 in Fig. 12. The PDU session response 118 indicate an acknowledgement with accepted and / or rejected quality-of-service flow identifier (QFI) for the flow handling rule. By the PDU session response 118, the SMF 100 is hence informed and can clearly identify whether the RAN 750 can support the flow handling rule or not. In this way, the SMF can address any uninstalled or unapplied flow handling rules based on the response.
[0155] Fig. 13 shows signaling for SMF selection by the AMF 500 according to an example of the invention. In step I in Fig. 13, the AMF 500 receives a PDU session establishment request 120 from a client device 810. The PDU session establishment request 120 is associated with an establishment of a PDU session for the client device 810 and indicating a requested resource type for the PDU session. The requested resource type may indicate a network resource type and / or a computing resource type for the PDU session, i.e., whether the PDU session is a compute PDU session or not. The PDU session establishment request 120 may further indicate an SST for the PDU session.
[0156] Based on the received PDU session establishment request 120, the AMF 500 selects a SMF 100 in step 2 in Fig. 13. Thus, the AMF 500 may use the information indicated in PDU session establishment request 120 to select a SMF 100 which is suitable to support the PDU session. For example, based on the requested resource type and / or SST, the AMF 500 may select a SMF 100 which supports a compute-centric PDU session and can interact with compute- related network functions such as the CCF 300.
[0157] In step 3 in Fig. 13, the AMF 500 transmit a PDU session create request 102 to the selected SMF 100, the PDU session create request 102 indicating the requested resource type. As previously described, the requested resource type may indicate the network resource type and / or the computing resource type for the PDU session. The PDU session create request 102 may further indicate the SST for the PDU session.
[0158] Further details related to examples of the invention will now be described in a 3GPP context with reference to Figs. 14 and 15. Thus, 3GPP terminology, definitions, expressions and system architecture will be used.
[0159] In Figs. 14 and 15, the procedure for a compute PDU session establishment according to an example the invention is described. The procedure may follow the PDU session establishment procedure in general, specified in clause of 4.3.2.2 of TS 23.502. Additional description of new functionality and new messages according to examples of the invention is provided.
[0160] In step 1 in Fig. 14, the client device 810, such as a UE, initiates a UE requested compute PDU session establishment procedure by the transmission of the PDU session establishment request 120 to the AMF 500. In addition to the information elements included in the PDU session establishment request according to the 3GPP standard, the PDU session establishment request 120 indicates requested resource type. The requested resource type is further defined and added to indicate what type of resource is requested by the client device 810. For example, it may be network resource only or network resource and compute resource for MCN. If compute resources are requested, the type of requested S-NSSAI with specific SST may be indicated to help the AMF 500 to select an appropriate SMF 100 for serving a compute PDU session. To assist the CCF 300 in the compute resource coordination, the CMDN may be indicated in the UE requested data network name (DNN).
[0161] In the shown example, it is assumed that the PDU session establishment request 120 sent in step 1 in Fig. 14 indicate that the request type is initial request, the requested resource type is MCN and the SST contained in the S-NSSAI is "7" for HCLLC and / or the UE requested DNN is CMDN. The PDU session establishment request 120 hence indicates the appropriate SST for S-NSSAI for a compute PDU session establishment and the compute coordination according to the invention is therefore performed. A request not indicating a request for a compute PDU session may be treated as a normal PDU session establishment.
[0162] In step 2 in Fig. 14, the AMF 500 determines that the received PDU session establishment request 120 corresponds to a request for a new compute PDU session based on that the indicated request type is initial request, the requested resource type is MCN and SST contained in the S-NSSAI is "7” for HCLLC. Based on the indicated S-NSSAI, the AMF 500 selects an appropriate SMF 100, i.e., a SMF 100 with capabilities to interact with CCFs 300 and instruct CFs 700 for packet forwarding. The SMF 100 may instruct the CF 700 and / or the CMDN how to treat packet handling, based on the interaction with the CCF 300 which coordinates the compute services to be distributed and running over CFs 700 and / or the CMDN for the compute PDU session.
[0163] In step 3 in Fig. 14, the AMF 500 sends a Nsmf_PDUSession_CreateSM Context Request 102 to the selected SMF 100. The Nsmf_PDUSession_CreateSM Context Request 102 may include the listed information elements and parameters in clause 4.3.2.2 of TS 23.502. The Nsmf_PDUSession_CreateSM Context Request 102 may further include the requested resource type, S-NSSAI and UE requested DNN received from the client device 810, i.e., requested resource type MCN, S-NSSAI HCLLC, and UE requested DNN CMDN. This information enables the SMF 100 to distinguish the needed requirements and capabilities for the requested compute PDU session.
[0164] In step 4 to 7 in Fig. 14, subscription, policy and authentication procedures are performed according to step 4 to 7 in clause 4.3.2.2 of TS 23.502.
[0165] In step 8 in Fig. 14, the SMF 100 selects a CCF 300 with capability to accommodate the request type, requested resource type, and S-NSSAI information for the requested compute PDU session.
[0166] In step 9 in Fig. 14, the SMF 100 sends a Nsmf_Coordination Request 104 to the selected CCF 300 to request that the CCF 300 checks the necessary compute resource availability and coordinate the relevant CSFs, based on the requested S-NSSAI and UE requested DNN information.
[0167] In step 10 in Fig. 14, the CCF 300 coordinates the required compute resources and capabilities among the RAN 750, the CF 700, and the CMDN to ensure that the computing performance for the compute PDU session will be reliably provided. Therefore, the CCF 300 may periodically monitor compute resource availability and capabilities among RAN 750, CF 700, and the CMDN. In addition to the compute performance monitoring, the CCF 300 may get compute data analytics from the CDAF or integrated network / compute data analytics from the CDAF and the NWDAF. As a result of the coordination, candidate CFs 700 are selected. Based on the monitoring and / or analytics information, the CCF 300 can coordinate the required compute resources with the selected CFs 700 and / or the CMDN for the compute PDU session based on the received S-NSSAI and UE requested DNN information.
[0168] In step 11 in Fig. 14, the CCF 300 sends a Nsmf_RSCoordination Response 106 to the SMF 100 with the candidate CFs 700 selected in step 10 based on the coordination.
[0169] The procedure continues in Fig. 15 and in step 12 in Fig. 15, the SMF 100 selects CFs 700 among the candidate list of CFs 700 and determines the forwarding path for compute service chaining. The SMF 100 may select one or more CFs 700 that fulfill the required computing and network capabilities for the compute service chaining, based on the compute service coordination provided by the CCF 300. If there are multiple candidate CFs 700 that fulfill the required computing and networking capabilities for the compute PDU session, the selection may depend on a user subscription or other network policy related to reliable network operation. Following the existing communication methods at step 8 in clause 4.3.2.2 of TS 23.502, IPv4 / IPv6 / IPv4v6 / MAC address may be allocated to the client device 810 based on the PDU session type.
[0170] In step 13 in Fig. 15, the SMF 100 sends an Nsmf_RSCoordination Notification Request 108 to notify the CCF 300 about the determined CFs 700.
[0171] In step 14 in Fig. 15, the CCF 300 reserves all the compute service resources in the determined compute nodes including CF 700 and RAN 750 and the CMDN.
[0172] In step 15 in Fig. 15, the CCF 300 sends an Nsmf_RSCoordination Notification Response 110 to acknowledge the Nsmf_RSCoordination Notification Request 108 and provide status information. The response message may include target CSFs running on the CF 700 for internal packet handling between forwarding layer and compute service layer within the CF 700.
[0173] In step 16 in Fig. 15, the SMF 100 sends an Nc Session Establishment / Modification Request 112 to the CF 700 and provides flow handling rule to be installed in the CF 700 for the PDU session, in addition to packet detection, enforcement and reporting rules specified at step 10a in clause 4.3.2.2 of TS 23.502. The flow handling rule provides an additional rule or method describing how to handle a received packet internally in association with CSFs running within the CF 700. That is, the CF 700 can know which CSF the received packet should be forwarded to and processed by within the CF 700.
[0174] In step 17 in Fig. 15, the CF 700 acknowledges by sending an Nc Session Establishment / Modification Response 114 to the SMF 100.
[0175] In step 18 in Fig. 15, the SMF 100 sends an Nh_PDU_Session Request 116 to the RAN 750. The message includes a flow handling rule to be installed in the RAN 750. The flow handling rule provides an additional rule or method describing how to handle a received packet internally in association with CSFs running within the RAN 750. That is, the RAN 750 can know which CSF the received packet should be forwarded to and processed by within the RAN 750. In 5G network architecture, the session management information may be transferred to the RAN 750 through the AMF 500 since there is no direct interface between the SMF 100 and the RAN 750. In this disclosure, a Nh interface being directly connected between the SMF 100 and the RAN 750 is assumed to be used for quick message transfer. However, the method for transferring the message is not limited to using Nh interface. An indirect message transfer through the AMF 500 may also be used by adding the flow handling rule information in the relevant messages from the SMF 100 to the AMF 500 and from the AMF 500 to the RAN 750.
[0176] In step 19 in Fig. 15, access node (AN)-specific resource setup is performed between the RAN 750 and the client device 810 according to step 13 in clause 4.3.2.2 of TS 23.502.
[0177] In step 20 in Fig. 15, the RAN 750 sends an Nh_PDU_Session Response 118 to the SMF 100. The message contains the accepted or rejected QFI associated with the received flow handling rule.
[0178] Continued handling of the PDU session may be performed by following the steps in clause 4.3.2.2 of TS 23.502.
[0179] The SMF 100, the CCF 300, the AMF 500 and the CF 700 herein may be functions configured for communication in 3GPP related LTE and LTE-Advanced, in WiMAX and its evolution, in 5G wireless technologies, such as new radio (NR), and 6G wireless technologies.
[0180] A client device herein may be denoted as a user device, a user equipment (UE), a mobile station, an internet of things (loT) device, a sensor device, a wireless terminal and / or a mobile terminal, and is enabled to communicate wirelessly in a wireless communication system, sometimes also referred to as a cellular radio system. The UEs may further be referred to as mobile telephones, cellular telephones, computer tablets or laptops with wireless capability. The UEs in this context may be, for example, portable, pocket-storable, hand-held, computer- comprised, or vehicle-mounted mobile devices, enabled to communicate voice and / or data, via a radio access network (RAN), with another communication entity, such as another receiver or a server. The UE may further be a station, which is any device that contains an IEEE 802.11- conformant MAC and PHY interface to the WM. The UE may be configured for communication in 3GPP related LTE, LTE-advanced, 5G wireless systems, such as NR, and their evolutions, as well as in IEEE related Wi-Fi, WiMAX and their evolutions.
[0181] Furthermore, any method according to examples of the invention may be implemented in a computer program, having code means, which when run by processing means causes the processing means to execute the steps of the method. The computer program is included in a computer readable medium of a computer program product. The computer readable medium may comprise essentially any memory, such as previously mentioned a ROM, a PROM, an EPROM, a flash memory, an EEPROM, or a hard disk drive.
[0182] Moreover, it should be realized that the SMF 100, the CCF 300, the AMF 500 and the OF 700 comprise the necessary communication capabilities in the form of e.g., functions, means, units, elements, etc., for performing or implementing examples of the invention. Examples of other such means, units, elements and functions are: processors, memory, buffers, control logic, encoders, decoders, rate matchers, de-rate matchers, mapping units, multipliers, decision units, selecting units, switches, interleavers, de-interleavers, modulators, demodulators, inputs, outputs, antennas, amplifiers, receiver units, transmitter units, DSPs, TCM encoder, TCM decoder, power supply units, power feeders, communication interfaces, communication protocols, etc. which are suitably arranged together for performing the solution.
[0183] Therefore, the processor(s) of the SMF 100, the CCF 300, the AMF 500 and the CF 700 may comprise, e.g., one or more instances of a CPU, a processing unit, a processing circuit, a processor, an ASIC, a microprocessor, or other processing logic that may interpret and execute instructions. The expression “processor” may thus represent a processing circuitry comprising a plurality of processing circuits, such as e.g., any, some or all of the ones mentioned above. The processing circuitry may further perform data processing functions for inputting, outputting, and processing of data comprising data buffering and device control functions, such as call processing control, user interface control, or the like.
[0184] Finally, it should be understood that the invention is not limited to the examples described above, but also relates to and incorporates all examples within the scope of the appended independent claims.
Claims
CLAIMS1. A session management function, SMF, (100) for a communication system (900), the SMF (100) being configured to: receive a packet data unit, PDU, session create request (102) from an access and mobility management function, AMF, (500), the PDU session create request (102) being associated with an establishment of a PDU session for a client device (810) and indicating a requested resource type for the PDU session; select a compute coordination function, CCF, (300) based on the PDU session create request (102); and transmit a coordination request (104) to the selected CCF (300), the coordination request (104) indicating the requested resource type.
2. The SMF (100) according to claim 1 , wherein the requested resource type indicates a network resource type and / or a computing resource type for the PDU session.
3. The SMF (100) according to claim 1 or 2, wherein the PDU session create request (102) further indicates a slice / service type, SST, for the PDU session.
4. The SMF (100) according to any one of the preceding claims, configured to: receive a coordination response (106) from the selected CCF (300), the coordination response (106) indicating a list of candidate compute functions, CFs, (700) for the PDU session; select one or more CFs (700) among the list of candidate CFs (700) based on the coordination response (106); and transmit a coordination notification request (108) to the selected CCF (300), the coordination notification request (108) indicating the one or more selected CFs.
5. The SMF (100) according to claim 4, wherein the coordination response (106) further indicates a monitored compute performance and / or a predicted compute performance of the candidate CFs (700).
6. The SMF (100) according to claim 4 or 5, wherein the coordination response (106) further indicates a compute service function, CSF, of a radio access network, RAN, (750) associated with the PDU session.
7. The SMF (100) according to claim 6, wherein the coordination notification request (108) further indicates whether to use the CSF of the RAN (750) or not.
8. The SMF (100) according to any one of claims 4 to 7, configured to: receive a coordination notification response (110) from the selected CCF (300), the coordination notification response (110) indicating a compute resource reservation for the PDU session; determine a flow handling rule for the PDU session based on the coordination notification response (110); and transmit a session establishment / modification request (112) to the one or more selected CFs (700), the session establishment / modification request (112) indicating the flow handling rule for the PDU session.
9. The SMF (100) according to claim 8, configured to: receive a session establishment / modification response (114) from the one or more selected CFs (700), the session establishment / modification response (114) indicating an acknowledgement of the flow handling rule for the PDU session.
10. The SMF (100) according to claim 8 or 9, configured to: transmit a PDU session request (116) to the RAN (750), the PDU session request (116) indicating the flow handling rule for the PDU session.
11. The SMF (100) according to claim 10, configured to: receive a PDU session response (118) from the RAN (750), the PDU session response (118) indicating an acknowledgement with accepted and / or rejected quality-of-service flow identifier, QFI, for the flow handling rule.
12. A CCF (300) for a communication system (900), the CCF (300) being configured to: receive a coordination request (104) from a SMF (100), the coordination request (104) being associated with a PDU session for a client device (810) and indicating a requested resource type for the PDU session; determine a list of candidate CFs (700) for the PDU session based on the coordination request (104); and transmit a coordination response (106) to the SMF (100), the coordination response (106) indicating the list of candidate CFs (700).
13. The CCF (300) according to claim 12, configured to: determine the list of candidate CFs (700) for the PDU session further based on a monitored compute performance and / or a predicted compute performance of a set of CFs (700).
14. The CCF (300) according to claim 12 or 13, wherein the coordination response (106) further indicates a monitored compute performance and / or a predicted compute performance of the candidate CFs (700).
15. The CCF (300) according to any one of claims 12 to 14, wherein the requested resource type indicates a network resource type and / or a computing resource type for the PDU session.
16. The CCF (300) according to any one of claims 12 to 15, wherein the coordination request (104) further indicates an SST for the PDU session.
17. The CCF (300) according to any one of claims 12 to 16, configured to: receive a coordination notification request (108) from the SMF (100), the coordination notification request (108) indicating one or more selected CFs (700) for the PDU session; reserve a compute resource for the PDU session based on the coordination notification request (108); and transmit a coordination notification response (110) to the SMF (100), the coordination notification response (110) indicating the compute resource reservation for the PDU session.
18. The CCF (300) according to any one of claims 12 to 17, wherein the coordination response (106) further indicates a CSF of a RAN (750) associated with the PDU session.
19. The CCF (300) according to any one of claims 12 to 18, wherein the coordination notification request (108) further indicates whether to use the CSF of the RAN (750) or not.
20. An AMF (500) for a communication system (900), the AMF (500) being configured to: receive a PDU session establishment request (120) from a client device (810), the PDU session establishment request (120) being associated with an establishment of a PDU session for the client device (810) and indicating a requested resource type for the PDU session; select a SMF (100) based on the PDU session establishment request (120); andtransmit s PDU session create request (102) to the selected SMF (100), the PDU session create request (102) indicating the requested resource type.
21. The AMF (500) according to claim 20, wherein the requested resource type indicates a network resource type and / or a computing resource type for the PDU session.
22. The AMF (500) according to claim 20 or 21 , wherein the PDU session establishment request (120) and / or the PDU session create request (102) further indicates an SST for the PDU session.
23. A CF (700) for a communication system (900), the CF (700) being configured to: receive a session establishment / modification request (112) from a SMF (100), the session establishment / modification request (112) indicating a flow handling rule associated with an establishment of a PDU session for a client device (810); and process received packets for the PDU session based on the session establishment / modification request (112).
24. The CF (700) according to claim 23, configured to: transmit a session establishment / modification response (114) to the SMF (100), the session establishment / modification response (114) indicating an acknowledgement of the flow handling rule for the PDU session.
25. A method (200) for a SMF (100), the method (200) comprising: receiving (202) a PDU session create request (102) from an access and AMF (500), the PDU session create request (102) being associated with an establishment of a PDU session for a client device (810) and indicating a requested resource type for the PDU session; selecting (204) a CCF (300) based on the PDU session create request (102); and transmitting (206) a coordination request (104) to the selected CCF (300), the coordination request (104) indicating the requested resource type.
26. A method (400) for a CCF (300), the method (400) comprising: receiving (402) a coordination request (104) from a SMF (100), the coordination request (104) being associated with a PDU session for a client device (810) and indicating a requested resource type for the PDU session;determining (404) a list of candidate CFs (700) for the PDU session based on the coordination request (104); and transmitting (406) a coordination response (106) to the SMF (100), the coordination response (106) indicating the list of candidate CFs (700).
27. A method (600) for an AMF (500), the method (600) comprising: receiving (602) a PDU session establishment request (120) from a client device (810), the PDU session establishment request (120) being associated with an establishment of a PDU session for the client device (810) and indicating a requested resource type for the PDU session; selecting (604) a SMF (100) based on the PDU session establishment request (120); and transmitting (606) a PDU session create request (102) to the selected SMF (100), the PDU session create request (102) indicating the requested resource type.
28. A method (800) for a CF (700), the method (800) comprising: receiving (802) a session establishment / modification request (112) from a SMF (100), the session establishment / modification request (112) indicating a flow handling rule associated with an establishment of a PDU session for a client device (810); and processing (804) received packets for the PDU session based on the session establishment / modification request (112).
29. A computer program with a program code for performing a method according to any one of claim 25 to 28 when the computer program runs on a computer.
Citation Information
Patent Citations
Computing service enablement for next generation cellular networks
WO2022031556A1
