A session management method and device for a cross-domain computing power-aware network

Abstract

The application discloses a session management method and device of a cross-domain computing power-aware network, wherein the method comprises the following steps: a first session management function network element of a first domain can establish a first session between the first domain and a second domain by interacting with a second session management function network element of the second domain, one end of the first session is connected with a first boundary computing power-aware user plane function network element of the first domain, and the other end of the first session is connected with a second boundary computing power-aware user plane function network element of the second domain. In this way, the first domain and the second domain can create a complete cross-domain computing power-aware network based on the first session between the domains, thereby realizing cross-domain expansion of computing power routing and solving the problem that the edge application coverage range and the user group of a single-domain computing power-aware network are limited.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a session management method and apparatus for a cross-domain computing power sensing network. Background Technology

[0002] Current computing power-aware networks are primarily designed for large-scale, intensive deployments of multi-access edge computing (MEC) by a single operator. However, in scenarios where a single operator independently deploys a computing power-aware network, each operator provides its own mobile computing power service, which to some extent limits the coverage and user base of edge applications. This is because edge application developers either have to target only the customer base of a specific operator or develop versions of the same application compatible with multiple operators, resulting in additional development costs and impacting their business interests.

[0003] To address the challenges of deploying compute-aware networks across different operators, the Global System for Mobile Communications Association (GSMA) proposed the Operator Platform (OP) architecture. The OP architecture is a set of functional modules that allow operators to deploy enterprise user solutions or applications to locations closest to their customers, aggregate the infrastructure capabilities of multiple operators, and provide application providers with a unified, open interface. However, the OP architecture only defines the collaboration interfaces at the management plane and does not address the definitions of the control plane and user plane. Considering that compute-aware networks possess compute awareness capabilities and dynamic routing, cross-operator compute collaboration still relies on user plane integration and the establishment of routing relationships, which cannot be directly accomplished through the management plane of the OP architecture.

[0004] Therefore, how to implement cross-carrier computing power routing and packet forwarding at the user plane is an urgent problem to be solved. Summary of the Invention

[0005] This application provides a session management method and apparatus for cross-domain computing power sensing networks, which enables cross-domain deployment and session management of computing power sensing networks in multiple operator environments, and solves the problem of limited edge application coverage and user base of computing power sensing networks of a single operator.

[0006] In a first aspect, embodiments of this application provide a session management method for a cross-domain computing power awareness network. This method can be executed by a first session management function network element of a first domain, or by a component (e.g., a chip or circuit) configured in the first session management function network element.

[0007] The method includes: a first session management function network element in a first domain receiving a first request message from a second session management function network element in a second domain, the first request message being used to request the establishment of a first session between the first domain and the second domain of a cross-domain computing power awareness network; the first session management function network element sending a second request message to a first boundary computing power awareness user plane function network element in the first domain, the second request message being used to request the establishment of the first session, one end of the first session being connected to the first boundary computing power awareness user plane function network element in the first domain, and the other end being connected to the second boundary computing power awareness user plane function network element in the second domain; the first session management function network element receiving a second response message from the first boundary computing power awareness user plane function network element, the second response message being used to indicate that the first session has been established on the first boundary computing power awareness user plane function network element side; and the first session management function network element sending a first response message to the second session management function network element, the first response message being used to indicate that the first session has been established on the first domain side.

[0008] In the above technical solution, the first session management function network element of the first domain can interact with the second session management function network element of the second domain to establish a first session between the first domain and the second domain. This enables the first domain and the second domain to create a cross-domain computing power awareness network based on the first session between the domains, realize the cross-domain extension of computing power routing, and solve the problem of limited edge application coverage and user group of the computing power awareness network of a single domain.

[0009] In one possible design of the first aspect, the first request message includes first inter-domain tunnel information, and the second request message includes first inter-domain tunnel information; the first inter-domain tunnel information is used to establish a tunnel for the first boundary computing power-aware user plane function element to send messages to the second boundary computing power-aware user plane function element.

[0010] In one possible design of the first aspect, the first request message includes identification information of the second boundary computing power sensing user plane functional network element, and the second request message includes identification information of the second boundary computing power sensing user plane functional network element.

[0011] In one possible design of the first aspect, the first response message includes second inter-domain tunnel information, which is used to establish a tunnel for the second boundary computing power-aware user plane function element to send messages to the first boundary computing power-aware user plane function element.

[0012] In one possible design of the first aspect, the method further includes: a first session management function network element generating second inter-domain tunnel information; or, the second response message including the second inter-domain tunnel information.

[0013] In one possible design of the first aspect, the method further includes: a first session management function network element receiving a third request message from a first computing management function network element of a first domain, the third request message being used to request the establishment of a second session of the cross-domain computing power awareness network within the first domain; the first session management function network element sending a fourth request message to a first boundary computing power awareness user plane function network element, the fourth request message being used to request the second session; the first session management function network element receiving a fourth response message from the first boundary computing power awareness user plane function network element, the fourth response message being used to indicate that the second session has been established on the side of the first boundary computing power awareness user plane function network element; and the first session management function network element sending a third response message to the first computing management function network element, the third response message being used to indicate that the second session has been established. Thus, the first session management function network element of the first domain can also establish a second session within the first domain according to the request of the first computing management function network element of the first domain, thereby enabling the first domain to create or update the intra-domain portion of the cross-domain computing power awareness network based on the second session within the domain.

[0014] Secondly, embodiments of this application provide a session management method for a cross-domain computing power awareness network. This method can be executed by a second session management function network element in the second domain, or by a component (e.g., a chip or circuit) configured in the second session management function network element.

[0015] The method includes: a second session management function network element of a second domain sending a first request message to a first session management function network element of a first domain, the first request message being used to request the establishment of a first session between the first domain and the second domain in a cross-domain computing power awareness network; the second session management function network element receiving a first response message from the first session management function network element, the first response message being used to indicate that the first session has been established on the first domain side; the second session management function network element sending a fifth request message to a second boundary computing power awareness user plane function network element of the second domain, the fifth request message being used to request the establishment of the first session, one end of the first session being connected to the second boundary computing power awareness user plane function network element of the second domain, and the other end being connected to the first boundary computing power awareness user plane function network element of the first domain; the second session management function network element receiving a fifth response message from the second boundary computing power awareness user plane function network element, the fifth response message being used to indicate that the first session has been established on the second boundary computing power awareness user plane function network element side.

[0016] In the above technical solution, the second session management function network element of the second domain can interact with the first session management function network element of the first domain to establish a first session between the first domain and the second domain. This enables the first domain and the second domain to create a cross-domain computing power awareness network based on the first session between the domains, realize the cross-domain extension of computing power routing, and solve the problem of limited edge application coverage and user group of a single domain computing power awareness network.

[0017] In one possible design of the second aspect, the first request message includes first inter-domain tunnel information, which is used to establish a tunnel for the first boundary computing power-aware user plane function element to send messages to the second boundary computing power-aware user plane function element.

[0018] In one possible design of the second aspect, the method further includes: the second session management function network element generating first inter-domain tunnel information; or, the second session management function network element receiving first inter-domain tunnel information from the second boundary computing power awareness user plane function network element.

[0019] In one possible design of the second aspect, the first request message includes the identification information of the second boundary computing power sensing user plane functional network element.

[0020] In one possible design of the second aspect, the first response message includes second inter-domain tunnel information, and the fifth request message includes second inter-domain tunnel information; the second inter-domain tunnel information is used to establish a tunnel for the second boundary computing power sensing user plane function network element to send messages to the first boundary computing power sensing user plane function network element.

[0021] In one possible design of the second aspect, the fifth request message includes the identification information of the first boundary computing power-aware user plane functional network element.

[0022] In one possible design of the second aspect, the method further includes: a second session management function network element receiving a sixth request message from a second computing management function network element of a second domain, the sixth request message being used to request the establishment of a first session; and the second session management function network element sending a sixth response message to the second computing management function network element, the sixth response message being used to indicate that the establishment of the first session is complete.

[0023] In the above technical solution, the second session management function network element of the second domain can interact with the first session management function network element of the first domain according to the request of the second computing management function network element of the second domain, thereby establishing a first session between the first domain and the second domain.

[0024] In one possible design of the second aspect, the sixth request message includes one or more of the following information: identification information of the first session management function network element, identification information of the first boundary computing power sensing user plane function network element, identification information of the second boundary computing power sensing user plane function network element, and identification information of the cross-domain computing power sensing network.

[0025] In one possible design of the second aspect, the method further includes: a second session management function network element receiving a seventh request message from a second computing management function network element of a second domain, the seventh request message being used to request the establishment of a third session of the cross-domain computing power awareness network within the second domain; the second session management function network element sending an eighth request message to a second boundary computing power awareness user plane function network element, the eighth request message being used to request the establishment of the third session; the second session management function network element receiving an eighth response message from the second boundary computing power awareness user plane function network element, the eighth response message being used to indicate that the third session has been established on the side of the second boundary computing power awareness user plane function network element; and the second session management function network element sending a seventh response message to the second computing management function network element, the seventh response message being used to indicate that the third session has been established. Thus, the second session management function network element of the second domain can also establish a third session within the second domain according to the request of the second computing management function network element of the second domain, thereby enabling the second domain to create or update the intra-domain portion of the cross-domain computing power awareness network based on the third session within the domain.

[0026] Thirdly, embodiments of this application provide a session management method for a cross-domain computing power awareness network. This method can be executed by a first computing management function network element of a first domain, or by a component (e.g., a chip or circuit) configured in the first computing management function network element.

[0027] The method includes: a first computing management function network element of a first domain sending a ninth request message to a second computing management function network element of a second domain, the ninth request message being used to request the creation of a cross-domain computing power awareness network, the cross-domain computing power awareness network including the first domain and the second domain; the first computing management function network element receiving a ninth response message from the second computing management function network element, the ninth response message being used to indicate that the cross-domain computing power awareness network has been created on the second domain side.

[0028] In the above technical solution, to create a cross-domain computing power awareness network, a first computing management function network element in the first domain can send a request to a second computing management function network element in the second domain. Thus, after the second computing management function network element completes the creation of the cross-domain computing power awareness network on the second domain side, it can return a response to the first computing management function network element, allowing the first computing management function network element to continue creating the cross-domain computing power awareness network on the first domain side, thereby completing the creation of the cross-domain computing power awareness network.

[0029] In one possible design of the third aspect, the ninth request message includes one or more of the following information: identification information of the first session management function network element of the first domain, identification information of the first boundary computing power awareness user plane function network element of the first domain, and identification information of the cross-domain computing power awareness network.

[0030] In one possible design of the third aspect, the method further includes: a first computing management function network element sending a third request message to a first session management function network element of the first domain, the third request message being used to request the establishment of a second session of the cross-domain computing power awareness network within the first domain; the first computing management function network element receiving a third response message from the first session management function network element, the third response message being used to indicate that the establishment of the second session is complete.

[0031] Fourthly, embodiments of this application provide a session management method for a cross-domain computing power awareness network. This method can be executed by a second computing management function network element of a second domain, or by a component (e.g., a chip or circuit) configured in the second computing management function network element.

[0032] The method includes: a second computing management function network element of a second domain receiving a ninth request message from a first computing management function network element of a first domain, the ninth request message being used to request the creation of a cross-domain computing power awareness network, the cross-domain computing power awareness network including the first domain and the second domain; the second computing management function network element sending a sixth request message to a second session management function network element of the second domain, the sixth request message being used to request the establishment of a first session between the first domain and the second domain in the cross-domain computing power awareness network, one end of the first session being connected to a second boundary computing power awareness user plane function network element of the second domain, and the other end being connected to a first boundary computing power awareness user plane function network element of the first domain; the second computing management function network element receiving a sixth response message from a second session management function network element, the sixth response message being used to indicate that the first session has been established; and the second computing management function network element sending a ninth response message to the first computing management function network element, the ninth response message being used to indicate that the cross-domain computing power awareness network has been created on the second domain side.

[0033] In the above technical solution, the second computing management function network element of the second domain can receive a request from the first computing management function network element of the first domain to request the creation of a cross-domain computing power awareness network. Then, through interaction with the second session management function of the second domain, a first session is established between the first and second domains, and a response is returned to the first computing management function network element. Thus, the first computing management function network element can subsequently continue to create the cross-domain computing power awareness network on the first domain side, thereby completing the creation of the cross-domain computing power awareness network.

[0034] In one possible design of the fourth aspect, the ninth request message includes one or more of the following information: identification information of the first session management function network element of the first domain, identification information of the first boundary computing power awareness user plane function network element of the first domain, and identification information of the cross-domain computing power awareness network.

[0035] In one possible design of the fourth aspect, the sixth request message includes one or more of the following information: identification information of the first session management function network element of the first domain, identification information of the first boundary computing power awareness user plane function network element of the first domain, identification information of the second boundary computing power awareness user plane function network element, and identification information of the cross-domain computing power awareness network.

[0036] In one possible design of the fourth aspect, the method further includes: a second computing management function network element sending a seventh request message to a second session management function network element, the seventh request message being used to request the establishment of a third session of the cross-domain computing power awareness network within the second domain; and the second computing management function network element receiving a seventh response message from the second session management function network element, the seventh response message being used to indicate that the establishment of the third session is complete.

[0037] Fifthly, embodiments of this application provide a session management method for a cross-domain computing power awareness network. This method can be executed by a first boundary computing power awareness user plane functional network element of a first domain, or by a component (e.g., a chip or circuit) configured in the first boundary computing power awareness user plane functional network element.

[0038] The method includes: a first boundary computing power-aware user plane function network element of a first domain receiving a second request message from a first session management function network element of the first domain. The second request message is used to request the establishment of a first session between the first domain and the second domain in a cross-domain computing power-aware network. One end of the first session is connected to the first boundary computing power-aware user plane function network element of the first domain, and the other end is connected to the second boundary computing power-aware user plane function network element of the second domain. The second request message includes inter-domain tunnel information. The first boundary computing power-aware user plane function network element establishes a tunnel for sending messages from the first boundary computing power-aware user plane function network element to the second boundary computing power-aware user plane function network element based on the inter-domain tunnel information. The first boundary computing power-aware user plane function network element sends a second response message to the first session management function network element. The second response message is used to indicate that the first session has been established on the side of the first boundary computing power-aware user plane function network element.

[0039] In one possible design of the fifth aspect, the method further includes: the first boundary computing power-aware user plane function network element establishing an inter-domain forwarding neighbor relationship with the second boundary computing power-aware user plane function network element, the inter-domain forwarding neighbor relationship being used by the first boundary computing power-aware user plane network element to send a service request message to the second boundary computing power-aware user plane function network element.

[0040] In the above technical solution, the first boundary computing power awareness user plane function network element of the first domain can determine the inter-domain forwarding neighbor relationship with the second boundary computing power awareness user plane function network element of the second domain according to the request of the first session management function network element of the first domain, establish a tunnel for sending messages to the second boundary computing power awareness user plane function network element, thereby completing the establishment of the first session between the first domain and the second domain on the side of the first boundary computing power awareness user plane function network element, and return a response to the first session management function network element.

[0041] By introducing a first boundary computing power sensing user plane functional network element in the first domain, and establishing a first session between the first boundary computing power sensing user plane functional network element and the second boundary computing power sensing user plane functional network element in the second domain, the computing power sensing network in the first domain and the computing power sensing network in the second domain can be interconnected to form a cross-domain computing power sensing network, realize the cross-domain extension of computing power routing, and solve the problem of limited edge application coverage and user group of computing power sensing network in a single domain.

[0042] In one possible design of the fifth aspect, the second request message includes identification information of the second boundary computing power-aware user plane functional network element.

[0043] In one possible design of the fifth aspect, the method further includes: a first boundary computing power-aware user plane function network element generating second inter-domain tunnel information, the second inter-domain tunnel information being used to establish a tunnel for the second boundary computing power-aware user plane function network element to send messages to the first boundary computing power-aware user plane function network element, and the second response message including the second inter-domain tunnel information.

[0044] In one possible design of the fifth aspect, the method further includes: a first boundary computing power-aware user plane function network element receiving a fourth request message from a first session management function network element, the fourth request message being used to request the establishment of a second session within a first domain of the cross-domain computing power-aware network; and the first boundary computing power-aware user plane function network element sending a fourth response message to the first session management function network element, the fourth response message being used to indicate that the second session has been established on the side of the first boundary computing power-aware user plane function network element.

[0045] In a sixth aspect, embodiments of this application provide a session management method for a cross-domain computing power awareness network. This method can be executed by a second boundary computing power awareness user plane functional network element of the second domain, or by a component (e.g., a chip or circuit) configured in the second boundary computing power awareness user plane functional network element.

[0046] The method includes: a second boundary computing power-aware user plane function network element of a second domain receiving a fifth request message from a second session management function network element of the second domain. This fifth request message requests the establishment of a first session between the first and second domains in a cross-domain computing power-aware network. One end of the first session is connected to the second boundary computing power-aware user plane function network element of the second domain, and the other end is connected to the first boundary computing power-aware user plane function network element of the first domain. The fifth request message includes inter-domain tunnel information. The second boundary computing power-aware user plane function network element establishes a tunnel for sending messages from the second boundary computing power-aware user plane function network element to the first boundary computing power-aware user plane function network element based on the inter-domain tunnel information. The second boundary computing power-aware user plane function network element sends a fifth response message to the second session management function network element, indicating that the first session has been successfully established on the second boundary computing power-aware user plane function network element side.

[0047] In one possible design of the sixth aspect, the method further includes: the second boundary computing power-aware user plane function network element establishing an inter-domain announcement neighbor relationship with the first boundary computing power-aware user plane function network element, the inter-domain announcement neighbor relationship being used by the second boundary computing power-aware user plane function network element to announce the domain-level service capability information of the second domain to the first boundary computing power-aware user plane function network element.

[0048] In the above technical solution, the second boundary computing power awareness user plane function network element of the second domain can determine the inter-domain announcement neighbor relationship with the first boundary computing power awareness user plane function network element of the first domain according to the request of the second session management function network element of the second domain, establish a tunnel for sending messages to the first boundary computing power awareness user plane function network element, thereby completing the establishment of the first session between the first domain and the second domain on the side of the second boundary computing power awareness user plane function network element, and return a response to the second session management function network element.

[0049] By introducing a second boundary computing power sensing user plane functional network element in the second domain, and establishing a first session between the second boundary computing power sensing user plane functional network element and the first boundary computing power sensing user plane functional network element in the first domain, the computing power sensing network in the first domain and the computing power sensing network in the second domain can be interconnected to form a cross-domain computing power sensing network. This enables cross-domain expansion of computing power routing and solves the problem of limited edge application coverage and user groups in a single-domain computing power sensing network.

[0050] In one possible design of the sixth aspect, the fifth request message includes the identification information of the first boundary computing power-aware user plane functional network element.

[0051] In one possible design of the sixth aspect, the method further includes: the second boundary computing power-aware user plane function network element generating first inter-domain tunnel information, the first inter-domain tunnel information being used to establish a tunnel for the first boundary computing power-aware user plane function network element to send messages to the second boundary computing power-aware user plane function network element; the second boundary computing power-aware user plane function network element sending the first inter-domain tunnel information to the second session management function network element.

[0052] In one possible design of the sixth aspect, the method further includes: a second boundary computing power-aware user plane function network element receiving an eighth request message from a second session management function network element, the eighth request message being used to request the establishment of a third session within a second domain of the cross-domain computing power-aware network; and the second boundary computing power-aware user plane function network element sending an eighth response message to the second session management function network element, the eighth response message being used to indicate that the third session has been established on the side of the second boundary computing power-aware user plane function network element.

[0053] In a seventh aspect, embodiments of this application provide a session management method for a cross-domain computing power sensing network. This method can be executed by a first boundary computing power sensing user plane functional network element of a first domain, or by a component (e.g., a chip or circuit) configured in the first boundary computing power sensing user plane functional network element.

[0054] The method includes: a first boundary computing power-aware user plane function network element of a first domain receiving a first announcement message from a second boundary computing power-aware user plane function network element of a second domain, the first announcement message including domain-level service capability information, the domain-level service capability information indicating the ability of the second domain to provide a first computing service to the outside world; the first boundary computing power-aware user plane function network element sending a second announcement message to a computing power-aware user plane function network element within the first domain of the first domain, the second announcement message including domain-level service capability information.

[0055] In the above technical solution, the first boundary computing power-aware user plane function network element of the first domain can receive domain-level service capability information announced by the second boundary computing power-aware user plane function network element of the second domain, and announce the domain-level service capability information to the computing power-aware user plane function network elements within the first domain. This allows users accessing the computing power-aware user plane function network elements within the first domain to also access the first computing service provided by the second domain, thereby expanding the service scope of the computing service in the second domain and effectively improving the user experience.

[0056] In one possible design of the seventh aspect, the first announcement message includes the identification information of the second boundary computing power-aware user plane functional network element; the method further includes: the first boundary computing power-aware user plane functional network element generates or updates the computing power routing information of the first computing service in the first boundary computing power-aware user plane functional network element based on the domain-level service capability information and the identification information of the second boundary computing power-aware user plane functional network element.

[0057] In one possible design of the seventh aspect, the second announcement message includes the identification information of the first boundary computing power-aware user plane functional network element.

[0058] In one possible design of the seventh aspect, the domain-level service capability information includes: computing service information of the first computing service corresponding to the second domain and / or load information of the second domain.

[0059] In one possible design of the seventh aspect, the method further includes: a first boundary computing power-aware user plane function network element receiving a service request message from a first domain computing power-aware user plane function network element, the service request message being used to request a first computing service, the service request message including a service identifier of the first computing service; and the first boundary computing power-aware user plane function network element sending a service request message to a second boundary computing power-aware user plane function network element according to the computing power routing information of the first computing service.

[0060] Eighthly, embodiments of this application provide a session management method for a cross-domain computing power awareness network. This method can be executed by a second boundary computing power awareness user plane functional network element of the second domain, or by a component (e.g., a chip or circuit) configured in the second boundary computing power awareness user plane functional network element.

[0061] The method includes: a second boundary computing power-aware user plane function network element of a second domain receiving a third announcement message from a computing power-aware user plane function network element within the second domain, the third announcement message including service capability information of an edge computing node associated with the computing power-aware user plane function network element within the second domain, the service capability information indicating the edge computing node's ability to provide a first computing service externally; the second boundary computing power-aware user plane function network element generating domain-level service capability information based on the edge computing node's service capability information, the domain-level service capability information indicating the second domain's ability to provide the first computing service externally; and the second boundary computing power-aware user plane function network element sending a first announcement message to a first boundary computing power-aware user plane function network element of the first domain, the first announcement message including the domain-level service capability information.

[0062] In the above technical solution, the second boundary computing power-aware user plane function network element of the second domain can receive service capability information announced by the computing power-aware user plane function network elements within the second domain, generate domain-level service capability information based on this information, and announce it to the computing power-aware user plane function network elements within the first domain. This allows users in the first domain to also access the first computing services provided by the second domain, thereby expanding the service scope of the computing services deployed in the second domain and effectively improving the user experience.

[0063] Furthermore, the second boundary computing power-aware user plane functional network element constructs domain-level service capability information based on the service capability information provided by the computing power-aware user plane functional network element within a single domain. This effectively shields the specific details of the computing services provided within the second domain, thereby protecting the information security of the second domain.

[0064] In one possible design of the eighth aspect, the third announcement message includes the identification information of the computing power-aware user plane functional network element in the second domain; the method further includes: the second boundary computing power-aware user plane functional network element generates or updates the computing power routing information of the first computing service in the second boundary computing power-aware user plane functional network element based on the service capability information of the edge computing node and the identification information of the computing power-aware user plane functional network element in the second domain.

[0065] In one possible design of the eighth aspect, the first announcement message includes the identification information of the second boundary computing power sensing user plane functional network element.

[0066] In one possible design of the eighth aspect, the service capability information of the edge computing node includes: computing service information of the first computing service corresponding to the edge computing node and / or load information of the edge computing node; the domain-level service capability information includes: computing service information of the first computing service corresponding to the second domain and / or load information of the second domain.

[0067] In one possible design of the eighth aspect, the method further includes: a second boundary computing power-aware user plane function network element receiving a service request message from a first boundary computing power-aware user plane function network element, the service request message being used to request a first computing service, the service request message including a service identifier of the first computing service; and the second boundary computing power-aware user plane function network element sending a service request message to a computing power-aware user plane function network element within the second domain according to the computing power routing information of the first computing service.

[0068] Ninthly, embodiments of this application provide a communication device that may have the function of a first session management network element implementing any of the above-described aspects or possible designs, or the function of a first computing management network element implementing any of the above-described aspects or possible designs, or the function of a second computing management network element implementing any of the above-described aspects or possible designs, or the function of a first boundary computing power awareness user plane network element implementing any of the above-described aspects or possible designs, or the function of a second boundary computing power awareness user plane network element implementing any of the above-described aspects or possible designs. This device may be a network device or a chip included in a network device.

[0069] The functions of the aforementioned communication device can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules, units, or means corresponding to the aforementioned functions.

[0070] In one possible design, the communication device includes a processing module and a transceiver module. The processing module is configured to support the communication device in performing the functions corresponding to the first session management function network element in any of the above-described aspects or designs, or performing the functions corresponding to the second session management function network element in any of the above-described aspects or designs, or performing the functions corresponding to the first computing management function network element in any of the above-described aspects or designs, or performing the functions corresponding to the second computing management function network element in any of the above-described aspects or designs, or performing the functions corresponding to the first computing power sensing user plane function network element in any of the above-described aspects or designs, or performing the functions corresponding to the second computing power sensing user plane function network element in any of the above-described aspects or designs. The transceiver module supports communication between the communication device and other communication devices. For example, when the communication device is a first session management function network element, it can receive a first request message from a second session management function network element. The communication device may also include a storage module coupled to the processing module, which stores the necessary program instructions and data of the device. As an example, the processing module can be a processor, the communication module can be a transceiver, and the storage module can be a memory. The memory can be integrated with the processor or set up separately from the processor.

[0071] In another possible design, the communication device includes a processor and may also include a memory. The processor is coupled to the memory and can be used to execute computer program instructions stored in the memory to cause the device to perform the methods in any of the above-described aspects or aspects of the possible design. Optionally, the communication device also includes a communication interface, to which the processor is coupled. When the communication device is a network device, the communication interface may be a transceiver or an input / output interface; when the device is a chip included in a network device, the communication interface may be the chip's input / output interface. Optionally, the transceiver may be a transceiver circuit, and the input / output interface may be an input / output circuit.

[0072] In a tenth aspect, embodiments of this application provide a chip system comprising: a processor coupled to a memory for storing programs or instructions, wherein when the programs or instructions are executed by the processor, the chip system implements any of the above-mentioned aspects or any possible design methods in each aspect.

[0073] Optionally, the chip system also includes an interface circuit for exchanging code instructions with the processor.

[0074] Optionally, the chip system may include one or more processors, which can be implemented in hardware or software. When implemented in hardware, the processor may be a logic circuit, integrated circuit, etc. When implemented in software, the processor may be a general-purpose processor that reads software code stored in memory.

[0075] Optionally, the chip system may contain one or more memories. These memories may be integrated with the processor or disposed separately. For example, the memory may be a non-transitory processor, such as a read-only memory, which may be integrated with the processor on the same chip or disposed on separate chips.

[0076] Eleventhly, embodiments of this application provide a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed, causes a computer to perform any of the methods in the above-described aspects or any possible design.

[0077] In a twelfth aspect, embodiments of this application provide a computer program product that, when read and executed by a computer, causes the computer to perform any of the methods in the above-described aspects or any possible design of the aspects.

[0078] In a thirteenth aspect, embodiments of this application provide a communication system, which includes one or more of the following communication devices: a first session management function network element of a first domain, a first computing management function network element of a first domain, a first boundary computing power sensing user plane function network element of a first domain, a second session management function network element of a second domain, a second computing management function network element of a second domain, or a second boundary computing power sensing user plane function network element of a second domain.

[0079] Specifically, the first session management function network element is used to implement the method in the first aspect or any possible design of the first aspect; the second session management function network element is used to implement the method in the second aspect or any possible design of the second aspect; the first computing management function network element is used to implement the method in the third aspect or any possible design of the third aspect; the second computing management function network element is used to implement the method in the fourth aspect or any possible design of the fourth aspect; the first boundary computing power awareness user plane function network element is used to implement the method in the fifth aspect or any possible design of the fifth aspect; and the second boundary computing power awareness user plane function network element is used to implement the method in the sixth aspect or any possible design of the sixth aspect.

[0080] Optionally, the communication system also includes a computing power-aware user plane function network element within the first domain of the first domain and a computing power-aware user plane function network element within the second domain of the second domain.

[0081] Optionally, the communication system further includes a terminal device and one or more edge computing nodes associated with the computing power sensing user plane function among the aforementioned first boundary computing power sensing user plane function network element, second boundary computing power sensing user plane function network element, first domain computing power sensing user plane function network element, and second domain computing power sensing user plane function network element.

[0082] In a fourteenth aspect, embodiments of this application provide a communication system, which includes a first boundary computing power sensing user plane functional network element of a first domain and a second boundary computing power sensing user plane functional network element of a second domain.

[0083] The first boundary computing power sensing user plane functional network element can also be used to implement the methods in the seventh aspect or any possible design of the seventh aspect, and the second boundary computing power sensing user plane functional network element can also be used to implement the methods in the eighth aspect or any possible design of the eighth aspect.

[0084] Optionally, the communication system also includes a computing power-aware user plane function network element within the first domain of the first domain and a computing power-aware user plane function network element within the second domain of the second domain.

[0085] Optionally, the communication system further includes a terminal device and one or more edge computing nodes associated with the computing power sensing user plane function among the aforementioned first boundary computing power sensing user plane function network element, second boundary computing power sensing user plane function network element, first domain computing power sensing user plane function network element, and second domain computing power sensing user plane function network element. Attached Figure Description

[0086] Figure 1 A network architecture for a communication system supporting a computing power-aware network is provided in the embodiments of this application;

[0087] Figure 2 This is a specific example of a cross-domain computing power sensing network provided in the embodiments of this application;

[0088] Figure 3 This application provides a network architecture for a communication system that supports cross-domain computing power sensing networks.

[0089] Figure 4a and Figure 4b This is another specific example of the cross-domain computing power sensing network provided in the embodiments of this application;

[0090] Figure 5 A flowchart illustrating a session management method for a cross-domain computing power sensing network provided in Embodiment 1 of this application;

[0091] Figure 6 Implementation method one of the inter-domain session creation process provided in Embodiment 1 of this application;

[0092] Figure 7 A second implementation of the inter-domain session creation process provided in Embodiment 1 of this application;

[0093] Figure 8 This is a schematic diagram of the session creation or update process of the cross-domain computing power sensing network in the second domain in Embodiment 1 of this application;

[0094] Figure 9 This is a schematic diagram illustrating the process by which the second SMF establishes or updates a third session on the second boundary CA-UPF side in Embodiment 1 of this application;

[0095] Figure 10 This is a schematic diagram illustrating the process by which the second SMF establishes or updates a third session on the CA-UPF side within the second domain in Embodiment 1 of this application.

[0096] Figure 11 This is a schematic diagram of the session establishment or update process of the cross-domain computing power sensing network in the first domain in Embodiment 1 of this application;

[0097] Figure 12 This is a schematic diagram illustrating the process by which the first SMF establishes or updates the second session on the first boundary CA-UPF side in Embodiment 1 of this application;

[0098] Figure 13 This is a schematic diagram illustrating the process by which the first SMF establishes or updates the second session on the CA-UPF side within the first domain in Embodiment 1 of this application.

[0099] Figure 14 A flowchart illustrating a session management method for a cross-domain computing power sensing network provided in Embodiment 2 of this application;

[0100] Figure 15 Implementation method three of the inter-domain session creation process provided in Embodiment 2 of this application;

[0101] Figure 16 Implementation method four of the inter-domain session creation process provided in Embodiment 2 of this application;

[0102] Figure 17 A flowchart illustrating a session management method for a cross-domain computing power sensing network provided in Embodiment 3 of this application;

[0103] Figure 18 This is a schematic diagram of the interaction process between CA-UPF and associated edge computing nodes in the second domain in Embodiment 3 of this application;

[0104] Figure 19 A flowchart illustrating a session management method for a cross-domain computing power-aware network provided in Embodiment 4 of this application;

[0105] Figure 20 and Figure 21 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0106] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings.

[0107] The technical solutions of this application can be applied to various communication systems, such as long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, 5th generation (5G) mobile communication systems, or new radio (NR) systems, or to future communication systems or other similar communication systems.

[0108] The following explanations of some terms used in this application are provided to facilitate understanding by those skilled in the art.

[0109] 1) A terminal device is a device with wireless transceiver capabilities. A terminal device can communicate with the core network or the Internet via a wireless access network (such as a radio access network, RAN) and exchange voice and / or data with the RAN.

[0110] Terminal equipment can include user equipment (UE), wireless terminal equipment, mobile terminal equipment, D2D terminal equipment, vehicle-to-everything (V2X) terminal equipment, machine-to-machine / machine-type communications (M2M / MTC) terminal equipment, internet of things (IoT) terminal equipment, subscriber unit, subscriber station, mobile station, remote station, access point (AP), remote terminal, access terminal, user terminal, user agent, or user device, etc. For example, terminal equipment can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, portable, pocket-sized, handheld, or computer-embedded mobile devices, etc. For example, terminal devices can also be virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, terminal devices in future public land mobile networks (PLMNs), or vehicle equipment in V2X, customer premises equipment (CPE), and so on.For example, the terminal device can also be a personal communication service (PCS) telephone, a cordless telephone, a session initiation protocol (SIP) telephone, a wireless local loop (WLL) station, a personal digital assistant (PDA), or other similar devices. This application does not limit the specific technology or form of the terminal device.

[0111] As an example, and not a limitation, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices or smart wearable devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets, smart helmets, and smart jewelry for vital sign monitoring. All the terminal devices described above, if located in a vehicle (e.g., placed inside or installed in a vehicle), can be considered in-vehicle terminal devices, also known as on-board units (OBUs).

[0112] 2) Wireless access network (RAN) equipment is used in a communication system to connect terminal devices to a wireless network. RAN equipment is typically connected to the core network via a wired link (e.g., fiber optic cable). RAN equipment can be a node in the RAN, also known as a base station, or RAN node (or device).

[0113] Wireless access network equipment may include base stations, evolved NodeBs (eNodeBs) in LTE systems or evolved LTE-Advanced (LTE-A) systems, next-generation NodeBs (gNBs) in 5G communication systems, transmission reception points (TRPs), base band units (BBUs), access points (APs) in wireless local area networks (WLANs), integrated access and backhaul (IAB) nodes, base stations in future mobile communication systems, or access nodes in WiFi systems. Wireless access network equipment may also be modules or units that perform some of the functions of a base station, such as centralized units (CUs) or distributed units (DUs). This application does not limit the specific technologies or equipment forms used in the wireless access network equipment.

[0114] For example, in one network architecture, the radio access network equipment can be a CU node, a DU node, or a radio access network equipment including both CU and DU nodes. The CU node supports protocols such as radio resource control (RRC), packet data convergence protocol (PDCP), and service data adaptation protocol (SDAP); the DU node supports radio link control (RLC) layer protocols, medium access control (MAC) layer protocols, and physical layer protocols.

[0115] Wireless access network equipment and terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on aircraft, balloons, and satellites. This application does not limit the application scenarios of the wireless access network equipment and terminal equipment. In this application, the wireless access network equipment can be simply referred to as access network equipment; unless otherwise specified, the access network equipment mentioned below refers to wireless access network equipment.

[0116] 3) Core network equipment refers to the equipment in the core network (CN) that provides service support for terminal equipment. Core network equipment may include network elements or functional entities such as access and mobility management function (AMF), session management function (SMF), user plane function (UPF), network exposure function (NEF), unified data management (UDM), and application function (AF).

[0117] Among them, AMF is mainly used for access management and mobility management of terminal equipment, such as user location updates, network registration, and cell handover; SMF is mainly used for session management, such as user session establishment, modification, and release; UPF is the user plane functional entity, mainly responsible for connecting to external networks and processing user packets, such as forwarding, billing, and lawful interception; NEF is used to expose some network functions to applications in a controlled manner; UDM is used to manage the subscription information of terminal equipment; AF is used to provide various application service data to the control plane network elements of the operator's communication network, or to obtain network data and control information from the control plane network elements of the communication network.

[0118] The core network equipment may also include other network elements or functional entities related to multi-access edge computing (MEC), which will be described in detail below.

[0119] It should be noted that the aforementioned network elements or functional entities can be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform). Optionally, the aforementioned network elements or functional entities can be implemented by one device, multiple devices working together, or different functional modules within a single device; this application embodiment does not specifically limit these possibilities.

[0120] 4) The terms "system" and "network" in the embodiments of this application can be used interchangeably. "Multiple" refers to two or more. Therefore, in the embodiments of this application, "multiple" can also be understood as "at least two". "At least one" can be understood as one or more, such as one, two or more. For example, including at least one means including one, two or more, and is not limited to which ones are included. For example, including at least one of A, B and C, then it can include A, B, C, A and B, A and C, B and C, or A and B and C. Similarly, the understanding of descriptions such as "at least one" is similar. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single items or multiple items. For example, "at least one of A, B and C" includes A, B, C, AB, AC, BC or ABC. "And / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent: A alone, A and B at the same time, and B alone. In addition, the character " / ", unless otherwise specified, generally indicates that the objects before and after it are in an "or" relationship.

[0121] Unless otherwise specified, the ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects, and are not used to limit the order, sequence, priority or importance of multiple objects, and the description of "first" and "second" does not limit the objects to necessarily being different.

[0122] The network architecture and related technical features applicable to the embodiments of this application will be described in detail below.

[0123] I. Computing Power Awareness Network

[0124] To enable 3GPP networks to adapt to dense MEC deployments and highly dynamic scheduling of edge microservices / functions, improve addressing efficiency for edge service discovery and access, and achieve unified end-to-end session and mobility management for connectivity and computing, compute-aware networks have emerged.

[0125] The computing-aware network, also known as the computing-aware-virtual network (CA-VN) or mobile computing network, introduces computing management function (CMF) and computing-aware-userplane function (CA-UPF) on the basis of the existing 3GPP network architecture. It realizes computing awareness and dynamic computing routing and packet forwarding based on service identifiers through information announcements between CA-UPFs.

[0126] Please refer to Figure 1 This application provides a network architecture for a communication system supporting a computing power-aware network. The network architecture includes terminal devices, access network devices, AMF, SMF, CMF, NEF, MEC platform manager, computing power-aware network, and edge data network. The computing power-aware network may include at least one CA-UPF, and the edge data network may include at least one edge computing node, which may also be referred to as an MEC node (or site).

[0127] The main characteristics of the aforementioned computing power awareness network can be summarized as follows:

[0128] 1) The functional roles of CA-UPF are divided into ingress CA-UPF and egress CA-UPF. Ingress CA-UPF refers to CA-UPF that can serve as an access anchor point for terminal devices to access the computing power sensing network, while egress CA-UPF refers to CA-UPF that is associated with edge computing nodes in the edge data network.

[0129] Since each CA-UPF in the computing power awareness network may be selected by terminal devices as an access anchor point, and each CA-UPF in the computing power awareness network may also establish or disassociate with edge computing nodes in the edge data network according to the dynamic changes in network deployment, the functional role of CA-UPF can be relative and dynamic. A CA-UPF can exist only as an ingress CA-UPF, or only as an egress CA-UPF, or simultaneously as both an ingress CA-UPF and an egress CA-UPF, without limitation.

[0130] 2) The egress CA-UPF can establish a relationship with edge computing nodes in the edge data network, receive service binding information reported by edge computing nodes, record the mapping relationship between the service ID of computing services and the server IP address according to the service binding information, receive computing service information and load information reported by edge computing nodes, and announce the computing service information and load information to the corresponding ingress CA-UPF according to the neighbor announcement list.

[0131] In a computing power-aware network, one egress CA-UPF can correspond to one or more ingress CA-UPFs. The neighbor relationship between an egress CA-UPF and its corresponding one or more ingress CA-UPFs is called an announcement neighbor relationship. This means that the egress CA-UPF needs to announce information such as computing service information and load information—which characterize the computing service capabilities of its associated edge computing nodes—to its corresponding ingress CA-UPFs so that the ingress CA-UPFs can construct computing power routing information accordingly. Accordingly, the egress CA-UPF is configured with an announcement neighbor list, which includes the identification information of the one or more ingress CA-UPFs corresponding to the egress CA-UPF.

[0132] Understandably, in the embodiments of this application, the computing service information and load information of the edge computing nodes associated with the egress CA-UPF can be collectively referred to as service capability information, and one or more ingress CA-UPFs corresponding to the egress CA-UPF can be considered as the announcement objects of the egress CA-UPF in announcing the above-mentioned service capability information.

[0133] 3) The ingress CA-UPF can aggregate computing service information and load information received from its corresponding egress CA-UPF. Based on the forwarding neighbor list and the aforementioned computing service information and load information, it constructs corresponding computing power routing information for each computing service. Based on the computing power routing information, it forwards the service request packets of the terminal device to one of the corresponding egress CA-UPFs.

[0134] In a computing power-aware network, one ingress CA-UPF can correspond to one or more egress CA-UPFs. The neighbor relationship between an ingress CA-UPF and its corresponding one or more egress CA-UPFs is called a forwarding neighbor relationship. This indicates that the ingress CA-UPF needs to forward service request packets from terminal devices to one of its corresponding egress CA-UPFs so that the terminal device's service request packets can be dynamically forwarded to the appropriate edge computing nodes for processing. Accordingly, the ingress CA-UPF is configured with a forwarding neighbor list, which includes the identification information of the one or more egress CA-UPFs corresponding to the ingress CA-UPF.

[0135] Understandably, in the embodiments of this application, one or more outgoing CA-UPFs corresponding to the ingress CA-UPF can be considered as multiple optional forwarding objects for the ingress CA-UPF to forward the aforementioned service request message. The service request message can also be called a business request message or have other names, and is not limited thereto.

[0136] 4) CA-UPF adds a computing power awareness processing unit, a regional dynamic session processing unit, and a network address translation unit to the existing UPF protocol data unit (PDU) session processing.

[0137] Specifically, the computing power awareness processing unit located in the exit CA-UPF is responsible for obtaining service capability information from edge computing nodes, storing the mapping relationship between the service ID of computing services and the server IP address, and announcing the service capability information of edge computing nodes to the entry CA-UPF in the announcement neighbor list. The service capability information of the edge computing nodes may include computing service information and / or load information. The computing service information indicates which computing services the edge computing node supports, and may include one or more of the following: service ID, service attributes, running status, or computing resource information for each computing service. The load information characterizes the current load status of the edge computing node.

[0138] The computing power awareness processing unit located in the ingress CA-UPF is responsible for receiving service capability information from the egress CA-UPF and generating or updating the computing power routing information database in the ingress CA-UPF. The computing power routing information database includes computing power routing information for one or more computing services. Specifically, the computing power routing information for a computing service includes one or more of the following: the service identifier of the computing service; the identifier information of one or more egress CA-UPFs capable of providing the computing service; the service capability information corresponding to each egress CA-UPF (including computing service information and / or load information of associated edge computing nodes); and network cost information (such as latency, bandwidth, and jitter between the ingress CA-UPF and the egress CA-UPF). Based on the computing power routing information of the computing services in the computing power routing information database, the computing power awareness processing unit can select appropriate forwarding tunnels for service request packets received by the regional dynamic session processing unit and generate corresponding packet matching and forwarding rules.

[0139] The main function of the regional dynamic session processing unit is to establish a forwarding tunnel between the ingress CA-UPF and the egress CA-UPF according to the forwarding tunnel information issued by the SMF, and to achieve real-time packet forwarding based on the packet matching and forwarding rules generated by the computing power awareness processing unit. When the regional dynamic session processing unit within the ingress CA-UPF receives a service request packet from a terminal device, if there is no corresponding packet matching and forwarding rule to match the packet to the appropriate forwarding tunnel, the computing power awareness processing unit can select an egress CA-UPF for the packet based on the computing power routing information database and generate the corresponding packet matching and forwarding rules.

[0140] The Network Address Translation (NAT) unit's main function is to replace the service identifier of the computing service with the server IP address in a message, based on the mapping relationship between the service identifier of the computing service and the server IP address provided by the computing power awareness processing unit. Specifically, the NAT unit can replace the destination IP address in uplink messages sent to edge computing nodes with the service identifier of the computing service, and replace the source IP address in downlink messages returned to terminal devices with the service identifier of the computing service.

[0141] 5) CMF is used to create and manage compute-aware network instances, specifically including: managing which CA-UPF members are included in the compute-aware network, determining the functional role of each CA-UPF member (i.e., whether it is an ingress CA-UPF, an egress CA-UPF, or both), and establishing and updating forwarding neighbor relationships and / or announcement neighbor relationships between CA-UPF members. Furthermore, CMF can also be used to record information such as the service identifier and service status of computing services deployed in the edge data network, so that terminal devices can query this information before initiating service request messages.

[0142] The computational power-aware network exists as an internal virtual interface within CA-UPF and can have multiple instances. Each computational power-aware network corresponds to a different network slice instance (NSI) and / or data network name (DNN). The CA-UPF members included in different computational power-aware networks can be completely different, partially overlapping, or completely identical; this application does not limit this.

[0143] CMF can create the aforementioned compute-aware network among CA-UPFs by sending a request to SMF to establish a compute-aware network. It can also establish neighbor relationships between adjacent CA-UPFs within the compute-aware network and perform dynamic session management for these neighboring CA-UPFs based on compute awareness. This forms a regional compute cluster among the edge computing nodes associated with these adjacent CA-UPFs, enabling dynamic deployment of computing services within the cluster. Service capability information of edge computing nodes can be quickly announced among CA-UPFs to ensure rapid response to service requests from terminal devices. Furthermore, it allows for forwarding of requests to the optimal edge computing node based on dynamic compute routing information, achieving system resource load balancing and improving user experience.

[0144] Understandably, in the embodiments of this application, the forwarding neighbor list and / or announcement neighbor list of each CA-UPF can be added, modified and deleted as needed. Since the forwarding neighbor relationship and the announcement neighbor relationship are relative, the CMF can confirm that each exit CA-UPF in the forwarding neighbor list of the ingress CA-UPF includes the ingress CA-UPF in its announcement neighbor list.

[0145] 6) The SMF can receive requests from the CMF to create a computing power-aware network, establish virtual network-level forwarding tunnels between CA-UPFs based on the forwarding neighbor relationships and announcement neighbor relationships between each CA-UPF, and issue corresponding forwarding neighbor lists and / or announcement neighbor lists to each CA-UPF.

[0146] 7) Each type of computing service corresponds to a unique service identifier (serviceID) within the operator's network management domain. The computing power awareness network dynamically routes and forwards messages requesting computing services from terminal devices based on the service identifier.

[0147] For example, each type of computing service has a service name that identifies what kind of computing service it is. There is a one-to-one correspondence between the service name and the service identifier. The service name can be described using a Uniform Resource Identifier (URI) or a Uniform Resource Locator (URL).

[0148] A computing service can be deployed on different edge computing nodes in an edge data network, which is equivalent to distributing multiple copies of the computing service across the edge data network. These multiple copies correspond to different server IP addresses, but still have the same service identifier. For example, these multiple copies can be multiple service instances of the same computing service running on edge application servers (EAS) on different edge computing nodes.

[0149] Correspondingly, the computing power awareness network realizes the computing power routing information of computing services based on service identifiers. It maps the server IP addresses of multiple replicas of the same computing service deployed on different edge computing nodes to the same service identifier, indicating that these multiple edge computing nodes can provide the same computing service, thereby achieving routing consistency.

[0150] To maximize the reuse of the existing IP protocol stack, the service identifier for the computing service can be an anycast IP address. Terminal devices can use this service identifier to initiate service requests without needing to know the specific EAS on which the service instance runs or the server IP address of that EAS. Specifically, the terminal device can translate the service name in the service request into a service identifier and use this identifier as the destination IP address to construct the corresponding IP packet (i.e., the service request packet). CA-UPF can route and forward service request packets based on the service identifier and perform the substitution between the service identifier and the server IP address when sending and receiving packets to and from EAS nodes in the edge computing nodes.

[0151] The computing services mentioned in this application embodiment, also known as edge computing services or edge applications, are not monolithic applications in the traditional client-server model, but rather lightweight services, such as microservices or function instances. These lightweight computing services are deployed and run on EAS in edge computing nodes. Optionally, the computing service can be a stateless, short-lifecycle microservice or function instance.

[0152] 8) Each edge computing node in the edge data network can be associated with a CA-UPF in the computing power awareness network, serving as the last hop before the service request message from the terminal device is forwarded to the edge computing node, ensuring that the end-to-end data forwarding path is controlled by the mobile network. The interface between the edge computing node and the CA-UPF is the N6 interface defined by 3GPP, and the interface between CA-UPFs is the N19 interface defined by 3GPP.

[0153] In an edge data network, a group of multiple adjacent edge computing nodes is called a regional computing power group. The CA-UPFs associated with each edge computing node in a regional computing power group are neighbors. By forming regional computing power groups from multiple adjacent edge computing nodes, the edge data network can use load balancing technology to overcome the resource bottlenecks of a single site, thereby increasing the scale of applications that edge computing can serve. It should be noted that the terms "region" and "adjacent" here are based on the network latency between edge computing nodes. This application can form regional computing power groups from edge computing nodes with interaction latency within a specified range, thereby improving the response efficiency of edge services.

[0154] Edge computing nodes may include MEC platforms and EAS (Enterprise Application Servers). The MEC platform is responsible for scheduling local computing, storage, and network resources. EAS is used to deploy or run computing services; a specific computing service running within an EAS can be referred to as a service instance of that service. An edge computing node may include one or more EAS, each EAS being assigned a different server IP address. The physical form of the EAS can be physical bare metal, a virtual machine, a container, etc., and this application is not limited to these.

[0155] The MEC Platform Manager is used to manage the MEC platform and EAS resources in edge computing nodes. By interacting with the MEC platform in the edge computing nodes, it enables the dynamic deployment, orchestration, and lifecycle management of computing services of different granularities, such as virtual machines, microservices, and function instances, on EAS in multiple edge computing nodes.

[0156] It should be noted that the above network architecture is designed for a large-scale, dense deployment scenario of MEC implemented by a single operator. In other words, the aforementioned computing power awareness network is deployed and managed independently by a single operator, and can be understood as a single-domain computing power awareness network implemented within the management scope of a single operator. The CA-UPF in this computing power awareness network, as well as the access network equipment and various types of core network equipment (such as AMF, SMF, CMF, etc.) in the communication system supporting this computing power awareness network, are all controlled and managed by the same operator.

[0157] II. Cross-Domain Computing Power Sensing Network

[0158] To address the limitations of edge application coverage and user base in single-operator computing power-aware networks, this application... Figure 1Based on the computing power awareness network shown in the network architecture, a border computing aware-user plane function (border CA-UPF) is further introduced. Computing power awareness networks of different operators with alliance relationships establish computing power routing and forwarding tunnels between each other through the border CA-UPF, thereby creating a cross-domain computing power awareness network.

[0159] By introducing the boundary CA-UPF, edge computing services can be flexibly deployed on edge computing nodes connected to multiple carrier networks with alliance relationships. This allows a user of a carrier to access edge computing services in the carrier network of their local domain, as well as edge computing services in the carrier network of their alliance domain through the boundary CA-UPF.

[0160] Please refer to Figure 2 This is a specific example of a cross-domain computing power awareness network provided in the embodiments of this application. This application uses this example to illustrate the concepts of local domain and federation domain in a cross-domain computing power awareness network.

[0161] Within a consortium, each operator's compute awareness network can be considered its local domain relative to itself. The compute awareness network directly connected to by terminal devices, whether it's the home network or the visited network, belongs to the local domain. The compute awareness networks of other operators interconnected by local domains via boundary CA-UPFs can be called consortium domains. Consortium domains can be further divided into direct consortium domains and indirect consortium domains. A direct consortium domain refers to a consortium domain directly connected to a local domain via a boundary CA-UPF, while an indirect consortium domain refers to a consortium domain reachable from a local domain via a multi-hop boundary CA-UPF. For example, such as... Figure 2 As shown, the cross-domain computing power awareness network consists of four interconnected computing power awareness networks of operators with alliance relationships. From the perspective of operator 1, operator 1's computing power awareness network is the local domain, and the computing power awareness networks of operators 2, 3, and 4 are direct alliance domains of operator 1's computing power awareness network. From the perspective of operator 4, operator 4's computing power awareness network is the local domain, operator 1's computing power awareness network is a direct alliance domain of operator 4's computing power awareness network, while the computing power awareness networks of operators 2 and 3 are indirect alliance domains of operator 4's computing power awareness network.

[0162] Optionally, to ensure latency, end users can be restricted to accessing edge computing services within their local domain and directly affiliated domain. This introduces a maximum of two hops of latency compared to the computing power-aware network within the local domain. For example, end users of Operator 4 can only access edge computing services provided by Operator 4 and Operator 1. If they access edge computing services provided by Operator 2 and Operator 3, it will introduce excessive latency, resulting in a deterioration in service experience.

[0163] Please refer to Figure 3 This is a network architecture diagram of a communication system supporting cross-domain computing power awareness networks, provided in an embodiment of this application. The network architecture shows the connection relationship between the computing power awareness network of the local domain and the computing power awareness network of the alliance domain.

[0164] On the user plane, the boundary CA-UPF of the local domain and the boundary CA-UPF of the federation domain are directly connected to enable message forwarding of service request and response messages between the two domains, as well as the announcement of service capability information. For example, such as... Figure 3 As shown, the boundary CA-UPF of the local domain and the boundary CA-UPF of the alliance domain can be directly connected through the N19 interface defined by 3GPP.

[0165] In the control plane, the local domain's CMF and the federated domain's CMF are configured with connections, enabling them to interact and create a cross-domain computing power awareness network. Similarly, the local domain's SMF and the federated domain's SMF are also configured with connections, allowing them to interact and establish inter-domain forwarding neighbor relationships and inter-domain announcement neighbor relationships between boundary CA-UPFs, as well as establish forwarding tunnels.

[0166] It's important to note that the boundary CA-UPF is a special type of CA-UPF. Within the local domain, the boundary CA-UPF acts as an exit CA-UPF to the entry CA-UPF within the domain; however, the messages received by the boundary CA-UPF are not directly sent to the associated edge computing nodes, but rather to the boundary CA-UPF of the computing power awareness network in the peer consortium domain. Between boundary CA-UPFs, the local boundary CA-UPF acts as an entry CA-UPF, and the consortium boundary CA-UPF acts as an exit CA-UPF. Within the consortium domain, the boundary CA-UPF acts as an entry CA-UPF to the exit CA-UPF within the domain.

[0167] In this embodiment of the application, each CA-UPF (including the boundary CA-UPF of the local domain) in the cross-domain computing power awareness network can be used as an ingress CA-UPF, and the CA-UPF associated with the edge computing node and the boundary CA-UPF of the local domain can be used as an egress CA-UPF.

[0168] Furthermore, it should be understood that Figure 3 The network architecture shown is for illustrative purposes only. In actual deployment scenarios, there can be one or more boundary CA-UPFs in the local domain and one or more boundary CA-UPFs in the federated domain. Furthermore, the local domain can create cross-domain computing power awareness networks with one or more federated domains, without limitation.

[0169] Please refer to Figure 4a and Figure 4b This is another specific example of the cross-domain computing power awareness network provided in the embodiments of this application. This example illustrates the connection and forwarding relationship between the local domain and the federation domain in the user plane. In this example, operator 1, operator 2, and operator 3 have a federation relationship. The cross-domain computing power awareness network is created with operator 1 as the local domain and operator 2 and operator 3 as the federation domains. The edge computing services are distributed and deployed on the edge computing nodes of the three operator networks.

[0170] Figure 4a This illustrates cross-domain packet forwarding paths. The local domain's ingress CA-UPF establishes intra-domain forwarding neighbor relationships and intra-domain forwarding tunnels with its neighboring egress CA-UPF and boundary CA-UPF. The local domain's boundary CA-UPF establishes inter-domain forwarding neighbor relationships and inter-domain forwarding tunnels with the boundary CA-UPF of its directly allied domain. The allied domain's boundary CA-UPF establishes intra-domain forwarding neighbor relationships and intra-domain forwarding tunnels with its neighboring egress CA-UPF.

[0171] Figure 4b This illustrates cross-domain announced neighbor relationships. Within a federation domain, the egress CA-UPF, based on the intra-domain announced neighbor list, announces the service capability information of associated edge computing nodes to the boundary CA-UPF within the federation domain. The boundary CA-UPF then generates or updates its intra-domain computing power routing information database. The boundary CA-UPF of the federation domain aggregates and merges service capability information for the same computing service from different egress CA-UPFs within the domain into a single domain-level service capability information entry. Then, based on the inter-domain announced neighbor list, it announces this domain-level service capability information of the federation domain to the boundary CA-UPF of the local domain. The boundary CA-UPF of the local domain then generates or updates its inter-domain computing power routing information database. Finally, the boundary CA-UPF of the local domain, based on the intra-domain announced neighbor list, further announces the service capability information to the ingress CA-UPF within the local domain. The ingress CA-UPF of the local domain then generates or updates its intra-domain computing power routing information database.

[0172] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of communication network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0173] For simplicity, the following embodiments use CMF, SMF, boundary CA-UPF, and intra-domain CA-UPF as examples. It should be understood that in the following embodiments, CMF can be replaced by a computing management function network element, SMF can be replaced by a session management function network element, boundary CA-UPF can be replaced by a boundary computing power awareness user plane function network element, and intra-domain CA-UPF can be replaced by an intra-domain computing power awareness user plane function network element.

[0174] Based on the network architecture and related technical features described above, this application provides a method for creating a cross-domain computing power awareness network among multiple operators with an alliance relationship and for performing session management in the cross-domain computing power awareness network.

[0175] Understandably, since local domain and alliance domain are relative concepts, when creating a cross-domain computing power awareness network among multiple operators with an alliance relationship, each operator can initiate a request to create a cross-domain computing power awareness network with itself as its local domain, and establish a cross-domain computing power awareness network with its direct alliance domain.

[0176] However, it should be noted that before creating a cross-domain computing power awareness network, it is necessary to first confirm that each operator in the alliance has deployed a boundary CA-UPF within its domain, and that boundary CA-UPFs with forwarding relationships have physical network connections and IP reachability. Additionally, each operator's CMF can be configured with the CA-UPF members and connections within its local domain, as well as the connections between its local boundary CA-UPF and CA-UPFs in other domains, the connections between its local boundary CA-UPF and the boundary CA-UPF of the peer alliance domain, and the CMF ID and SMF ID of the alliance domain, so that the CMF and SMF of the local domain can interact with the CMF and SMF of the peer alliance domain.

[0177] Furthermore, depending on the different ways of establishing inter-domain sessions between the local domain and the federated domain, the method for creating a cross-domain computing power awareness network provided in this application may include two possible technical solutions in its specific implementation, which will be referred to as Solution 1 and Solution 2 for ease of description.

[0178] 1) Option 1: The CMF of the local domain requests the CMF of the consortium domain to trigger the SMF of the consortium domain to initiate the inter-domain session creation process of the cross-domain computing power awareness network to the SMF of the local domain. This completes the creation of inter-domain forwarding neighbor relationships and inter-domain announcement neighbor relationships between the boundary CA-UPF of the local domain and the consortium domain, as well as the creation of inter-domain forwarding tunnels. Then, the local domain and the consortium domain respectively complete the creation of their respective computing power awareness networks.

[0179] 2) Option 2: The CMF of the local domain requests the SMF of the local domain to initiate the inter-domain session creation process of the cross-domain computing power awareness network to the SMF of the federation domain. This process completes the creation of inter-domain forwarding neighbor relationships and inter-domain announcement neighbor relationships between the boundary CA-UPFs of the local domain and the federation domain, as well as the creation of inter-domain forwarding tunnels. Then, the local domain and the federation domain complete the creation of their respective computing power awareness networks.

[0180] It should be noted that if each operator in the alliance initiates the creation of its own cross-domain computing power awareness network, then end users within each operator's domain can access that network and access edge computing services in the peer domain. The computing power awareness networks of different operators complement and extend each other's computing power. However, if an operator does not actively initiate the creation of a cross-domain computing power awareness network but passively accepts requests to establish inter-domain sessions from a peer domain, then the computing power awareness network within that operator's domain can only provide computing power extensions for the peer domain. End users in that domain cannot access the cross-domain network and cannot access edge computing services in the peer domain.

[0181] For ease of understanding, in the following embodiments, the first domain is taken as the local domain and the second domain as the alliance domain, and the first domain initiates a request to create a cross-domain computing power awareness network between the first domain and the second domain, as an example for illustration.

[0182] Furthermore, the relevant terms and concepts appearing in the following embodiments are explained as follows:

[0183] The first domain is the local domain, and the second domain is the alliance domain, which is the direct alliance domain of the first domain. The network elements or functional entities in the first and second domains (such as access network equipment and core network equipment such as AMF, SMF, CMF, and CA-UPF) are controlled and managed by different operators.

[0184] The first CMF, the first SMF, the CA-UPF within the first domain, and the first boundary CA-UPF belong to the first domain. The second CMF, the second SMF, the CA-UPF within the second domain, and the second boundary CA-UPF belong to the second domain. Furthermore, the CA-UPF within the first domain, the first boundary CA-UPF, the CA-UPF within the second domain, and the second boundary CA-UPF are all members of the cross-domain computing power awareness network to be created between the first and second domains.

[0185] Among them, the CA-UPF within the first domain refers to the CA-UPF (i.e., non-boundary CA-UPF) in the first domain included in the cross-domain computing power sensing network. The CA-UPF within the first domain can be an entry CA-UPF, an exit CA-UPF, or both an entry CA-UPF and an exit CA-UPF, without limitation.

[0186] The second domain CA-UPF refers to the intra-domain CA-UPF (i.e., non-boundary CA-UPF) in the second domain included in the cross-domain computing power sensing network. This second domain CA-UPF can be an ingress CA-UPF, an egress CA-UPF, or both an ingress CA-UPF and an egress CA-UPF, without limitation.

[0187] The first boundary CA-UPF refers to the boundary CA-UPF within the first domain included in the cross-domain computing power awareness network, and the second boundary CA-UPF refers to the boundary CA-UPF within the second domain included in the cross-domain computing power awareness network. Both are used together to achieve interconnection between the first and second domains. The first boundary CA-UPF corresponds to the second boundary CA-UPF, or in other words, there is an association between them. This correspondence or association can be pre-configured after negotiation between the first and second CMFs. Thus, by establishing forwarding neighbor relationships and forwarding tunnels between the first and second boundary CA-UPFs, and creating corresponding virtual network-level sessions, the first and second domains can be interconnected, realizing the cross-domain expansion of the computing power awareness network.

[0188] From the perspective of a cross-domain computing power awareness network, this network can include N intra-domain CA-UPFs and a first boundary CA-UPF in a first domain, and M intra-domain CA-UPFs and a second boundary CA-UPF in a second domain, where N and M are both positive integers. Specifically, the N intra-domain CA-UPFs refer to the N intra-domain CA-UPFs (i.e., non-boundary CA-UPFs) in the first domain, and each first intra-domain CA-UPF is one of the N intra-domain CA-UPFs included in the first domain by the cross-domain computing power awareness network. Similarly, the M intra-domain CA-UPFs refer to the M intra-domain CA-UPFs (i.e., non-boundary CA-UPFs) in the second domain, and each second intra-domain CA-UPF is one of the M intra-domain CA-UPFs included in the second domain by the cross-domain computing power awareness network.

[0189] Understandably, the first domain can have one or more boundary CA-UPFs, and different boundary CA-UPFs can be used to interconnect the first domain with different federated domains. Optionally, multiple boundary CA-UPFs in the first domain can be logically independent but physically deployed together. The boundary CA-UPFs in the second domain are similar.

[0190] In addition, the first domain may also include network elements or functional entities such as the first management plane (operation, administration and management, OAM) of the management plane and the first UDM of the control plane, and the second domain may also include network elements or functional entities such as the second OAM of the management plane and the second UDM of the control plane, without limitation.

[0191] The two schemes for creating cross-domain computing power sensing networks will be described in detail below through Example 1 and Example 2, respectively.

[0192] Example 1

[0193] Embodiment 1 of this application provides a session management method for a cross-domain computing power awareness network. Specifically, this method is a method for creating a cross-domain computing power awareness network between a first domain and a second domain, corresponding to Scheme 1 mentioned above.

[0194] Please refer to Figure 5 The above is a flowchart illustrating a session management method for a cross-domain computing power-aware network provided in Embodiment 1 of this application. The method includes:

[0195] Step S501: The first CMF sends a ninth request message to the second CMF. The ninth request message is used to request the creation of a cross-domain computing power awareness network, which includes the first domain and the second domain.

[0196] Correspondingly, the second CMF receives the ninth request message from the first CMF.

[0197] The cross-domain computing power sensing network, including the first domain and the second domain, means that: the cross-domain computing power sensing network is a computing power sensing network created between the first domain and the second domain, or the cross-domain computing power sensing network is composed of interconnected computing power sensing networks in the first domain and computing power sensing networks in the second domain, or the cross-domain computing power sensing network covers the first domain and the second domain.

[0198] The ninth request message includes one or more of the following information: identification information of the cross-domain computing power awareness network, identification information of the first boundary CA-UPF of the first domain, or identification information of the first SMF. The identification information of the cross-domain computing power awareness network may include one or more of the following: the cross-domain computing power awareness network's identity (ID), the corresponding DNN, network slice information, or application descriptor. Different cross-domain computing power awareness networks may correspond to different DNNs, different network slice information, or different application descriptors; this is not limited.

[0199] The ninth request message may be called a cross-domain computing power sensing network creation request message, or may have other names, which are not limited in this application.

[0200] In one embodiment of this application, the first CMF can receive a request message from the first OAM or the first UDM of the first domain to create a cross-domain computing power awareness network. Based on the request message, it determines that a cross-domain computing power awareness network needs to be created, and determines the CA-UPF members included in the first domain of the cross-domain computing power awareness network, such as including N intra-domain CA-UPFs and a first boundary CA-UPF.

[0201] The request message may include identification information of the cross-domain computing power awareness network to be created, a list of intra-domain members of the local domain, and a list of boundary members of the local domain. The list of members of the local domain includes identification information of N intra-domain CA-UPFs included in the first domain, indicating which intra-domain CA-UPF members the cross-domain computing power awareness network to be created includes in the first domain. The list of boundary members of the local domain includes identification information of the first boundary CA-UPF in the first domain, indicating which boundary CA-UPF members the cross-domain computing power awareness network to be created includes in the first domain.

[0202] Understandably, the boundary member list of the local domain can also include the identification information of one or more other boundary CA-UPFs, indicating that in addition to the second domain, a cross-domain computing power awareness network needs to be created between the first domain and other consortium domains. In this case, the first CMF can send a request message to the CMF in the consortium domain corresponding to each boundary CA-UPF to request the creation of a cross-domain computing power awareness network, and repeat the process. Figure 5 The method steps shown herein complete the creation of a cross-domain computing power awareness network with each alliance domain.

[0203] For example, if the boundary member list of the local domain also includes the identification information of the third boundary CA-UPF, which corresponds to the fourth boundary CA-UPF of the third domain, and the third domain is also a federated domain of the first domain, then it means that the first CMF also needs to create a cross-domain computing power awareness network between the first domain and the third domain. This interconnection between the computing power awareness network in the first domain and the computing power awareness network in the third domain is achieved through the third boundary CA-UPF and the fourth boundary CA-UPF. The process by which the first CMF creates a cross-domain computing power awareness network between the first domain and the third domain can be referred to the method described in this document for creating a cross-domain computing power awareness network between the first domain and the second domain, and will not be repeated here.

[0204] Furthermore, regarding the inter-domain creation part, the first CMF can generate an inter-domain forwarding neighbor list for the first boundary CA-UPF, which includes the identification information of the second boundary CA-UPF. Understandably, during the process of the first CMF generating the corresponding inter-domain forwarding neighbor list for the first boundary CA-UPF, the first CMF can determine that an inter-domain forwarding neighbor relationship exists between the first boundary CA-UPF and the second boundary CA-UPF in the second domain that corresponds to the first boundary CA-UPF.

[0205] The first CMF can also determine the identification information of the second CMF in the alliance domain (i.e., the second domain) connected by the first boundary CA-UPF, so as to send the aforementioned ninth request message to the second CMF, requesting the second CMF to create a cross-domain computing power awareness network, including creating the inter-domain part of the cross-domain computing power awareness network between the first domain and the second domain, and the intra-domain part of the cross-domain computing power awareness network in the second domain.

[0206] Step S502: The second CMF sends a sixth request message to the second SMF. The sixth request message is used to request the establishment of a first session between the first domain and the second domain of the cross-domain computing power awareness network. One end of the first session is connected to the first boundary CA-UPF of the first domain, and the other end is connected to the second boundary CA-UPF of the second domain.

[0207] Correspondingly, the second SMF receives the sixth request message from the second CMF.

[0208] The sixth request message includes one or more of the following information: the identification information of the cross-domain computing power sensing network, the identification information of the first boundary CA-UPF, the identification information of the second boundary CA-UPF, or the identification information of the first SMF.

[0209] The sixth request message can be understood as a request to establish an inter-domain session or inter-domain forwarding path for a cross-domain computing power awareness network. Therefore, the sixth request message can be called a cross-domain computing power awareness network inter-domain session establishment request message, or may have other names, which are not limited in this application.

[0210] Optionally, the first session (i.e., inter-domain session) is a virtual network-level session. The virtual network-level session refers to a shared session for communication between CA-UPFs, used to forward session messages from terminal devices accessing the computing power sensing network. This virtual network-level session differs from existing terminal device-level sessions, which can only be used for message forwarding within that terminal device.

[0211] In Embodiment 1 of this application, after the second CMF receives the ninth request message from the first CMF, the second CMF can determine the second boundary CA-UPF in the second domain corresponding to the first boundary CA-UPF based on the identification information of the first boundary CA-UPF provided by the first CMF, and generate an inter-domain advertised neighbor list for the second boundary CA-UPF, which includes the identification information of the first boundary CA-UPF. It can be understood that during the process of the second CMF generating the inter-domain advertised neighbor list for the second boundary CA-UPF, the second CMF can determine, based on the identification information of the first boundary CA-UPF in the first request message, that there is an inter-domain advertised neighbor relationship between the second boundary CA-UPF and the first boundary CA-UPF in the first domain.

[0212] Furthermore, the second CMF can carry one or more of the following information: the identification information of the cross-domain computing power awareness network to be created, the identification information of the second boundary CA-UPF, the inter-domain announcement neighbor list, and the identification information of the first SMF. It then sends a sixth request message to the second SMF to request the second SMF to establish a first session of the cross-domain computing power awareness network between the first and second domains, thereby triggering the inter-domain session creation process of the cross-domain computing power awareness network. Understandably, the aforementioned information is used for interaction between the second and first SMFs to complete the establishment of the first session on the first boundary CA-UPF side and the first session on the second boundary CA-UPF side, respectively.

[0213] Step S503: The second SMF sends a first request message to the first SMF, which is used to request the establishment of a first session.

[0214] Correspondingly, the first SMF receives the first request message from the second SMF.

[0215] In Embodiment 1 of this application, after receiving the sixth request message from the second CMF, the second SMF can determine, based on the identification information of the cross-domain computing power sensing network, the identification information of the second boundary CA-UPF, and the inter-domain announcement neighbor list, that it is necessary to establish a first session between the second boundary CA-UPF of the second domain and the first boundary CA-UPF of the first domain. Then, based on the identification information of the first SMF, the first SMF is determined, and a first request message is sent to the first SMF.

[0216] The first request message includes one or more of the following information: identification information of the cross-domain computing power sensing network, identification information of the first boundary CA-UPF, identification information of the second boundary CA-UPF, or first inter-domain tunnel information.

[0217] Specifically, the first inter-domain tunnel information is used to establish a tunnel between the first boundary CA-UPF and the second boundary CA-UPF. Considering that there are two-way forwarding tunnels between the first and second boundary CA-UPFs, this first inter-domain tunnel information is specifically used to establish a tunnel for sending messages from the first boundary CA-UPF to the second boundary CA-UPF, or in other words, a forwarding tunnel from the first boundary CA-UPF to the second boundary CA-UPF. For clarity, this tunnel will be referred to as the first inter-domain forwarding tunnel.

[0218] Understandably, since the first boundary CA-UPF and the second boundary CA-UPF are inter-domain forwarding neighbors and advertising neighbors, the inter-domain forwarding neighbor list of the first boundary CA-UPF includes the identification information of the second boundary CA-UPF, and the inter-domain advertising neighbor list of the second boundary CA-UPF includes the identification information of the first boundary CA-UPF. Therefore, it can also be considered that the first request message includes the identification information of the first boundary CA-UPF and its inter-domain forwarding neighbor list, and / or, the identification information of the second boundary CA-UPF and its inter-domain advertising neighbor list.

[0219] The first request message can also be understood as a request to establish a cross-domain virtual network level session. Therefore, the first request message can be called a cross-domain virtual network level session establishment request message, or it may have other names, which are not limited.

[0220] Step S504: The first SMF sends a second request message to the first boundary CA-UPF, which is used to request the establishment of a first session.

[0221] Correspondingly, the first boundary CA-UPF receives a second request message from the first SMF.

[0222] In Embodiment 1 of this application, after receiving a first request message from a second SMF, the first SMF can determine, based on the identification information of the cross-domain computing power sensing network, the identification information of the first boundary CA-UPF, and the identification information of the second boundary CA-UPF, that it is necessary to establish a first session between the first boundary CA-UPF of the first domain and the second boundary CA-UPF of the second domain. Then, based on the identification information of the first boundary CA-UPF, the first boundary CA-UPF is determined, and a second request message is sent to the first boundary CA-UPF.

[0223] The second request message can also be understood as a request to establish an inter-domain virtual network level session on the first boundary CA-UPF side. Therefore, the second request message can be called an inter-domain virtual network level session establishment request message, or it may have other names, which are not limited.

[0224] Step S505: The first boundary CA-UPF establishes a first inter-domain forwarding tunnel with the second boundary CA-UPF.

[0225] In Embodiment 1 of this application, both the first request message and the second request message include the aforementioned first inter-domain tunnel information. Thus, after the first boundary CA-UPF receives the second request message from the first SMF, it can establish a first inter-domain forwarding tunnel based on the first inter-domain tunnel information.

[0226] Furthermore, both the first and second request messages include the identification information of the second boundary CA-UPF, i.e., the inter-domain forwarding neighbor list of the first boundary CA-UPF. Thus, after receiving the second request message from the first SMF, the first boundary CA-UPF can establish an inter-domain forwarding neighbor relationship with the second boundary CA-UPF based on its corresponding inter-domain forwarding neighbor list. This inter-domain forwarding neighbor relationship is used by the first boundary CA-UPF to send inter-domain service request messages to the second boundary CA-UPF. In other words, the first boundary CA-UPF can determine that the second boundary CA-UPF is its corresponding inter-domain forwarding neighbor based on the identification information of the second boundary CA-UPF included in the inter-domain forwarding neighbor list.

[0227] Optionally, the second request message may also include identification information of the cross-domain computing power awareness network.

[0228] Step S506: The first boundary CA-UPF sends a second response message to the first SMF. The second response message is used to indicate that the first session has been established on the first boundary CA-UPF side.

[0229] Correspondingly, the first SMF receives a second response message from the first boundary CA-UPF.

[0230] Optionally, the second response message may include identification information of the cross-domain computing power awareness network.

[0231] The second response message can also be understood as indicating that the inter-domain virtual network level session establishment on the first boundary CA-UPF side is complete. Therefore, the second response message can be called an inter-domain virtual network level session establishment response message, or have other names, without limitation.

[0232] Understandably, the completion of the first session establishment on the first boundary CA-UPF side signifies the completion of the first session establishment on the first domain side. Therefore, the second response message can also be used to indicate that the first session has been established on the first domain side.

[0233] Step S507: The first SMF sends a first response message to the second SMF, which is used to indicate that the first session has been established on the first domain side.

[0234] Correspondingly, the second SMF receives the first response message from the first SMF.

[0235] The first response message includes one or more of the following: identification information of the cross-domain computing power awareness network or second-domain tunnel information. The second-domain tunnel information is used to establish a tunnel between the first boundary CA-UPF and the second boundary CA-UPF. Considering that there are two-way forwarding tunnels between the first and second boundary CA-UPFs, the second-domain tunnel information here is specifically used to establish a tunnel for sending messages from the second boundary CA-UPF to the first boundary CA-UPF, or in other words, a forwarding tunnel from the second boundary CA-UPF to the first boundary CA-UPF. For clarity, this tunnel will be referred to as the second-domain forwarding tunnel.

[0236] The first response message can also be understood as indicating that the cross-domain virtual network level session has been established on the first domain side. Therefore, the first response message can be called a cross-domain virtual network level session establishment response message, or it can have other names, which are not limited.

[0237] Step S508: The second SMF sends a fifth request message to the second boundary CA-UPF, which is used to request the establishment of the first session.

[0238] Correspondingly, the second boundary CA-UPF receives the fifth request message from the second SMF.

[0239] The fifth request message can also be understood as a request to establish an inter-domain virtual network level session on the second boundary CA-UPF side. Therefore, the fifth request message can be called an inter-domain virtual network level session establishment request message, or it may have other names, which are not limited.

[0240] Step S509: The second boundary CA-UPF establishes a second inter-domain forwarding tunnel with the first boundary CA-UPF.

[0241] In Embodiment 1 of this application, both the first response message and the fifth request message include the aforementioned second inter-domain tunnel information. Thus, after the second boundary CA-UPF receives the fifth request message from the second SMF, it can establish a second inter-domain forwarding tunnel based on this second inter-domain tunnel information.

[0242] Furthermore, the fifth request message includes the identification information of the first boundary CA-UPF, i.e., the inter-domain advertised neighbor list of the second boundary CA-UPF. Thus, after receiving the fifth request message from the second SMF, the second boundary CA-UPF can establish an inter-domain advertised neighbor relationship with the first boundary CA-UPF based on its corresponding inter-domain advertised neighbor list. This inter-domain advertised neighbor relationship is used by the second boundary CA-UPF to advertise the domain-level service capability information of the second domain to the first boundary CA-UPF. That is, the second boundary CA-UPF can determine that the first boundary CA-UPF is its corresponding inter-domain advertised neighbor based on the identification information of the first boundary CA-UPF included in the inter-domain advertised neighbor list.

[0243] Optionally, the fifth request message may also include identification information of the cross-domain computing power awareness network.

[0244] Step S510: The second boundary CA-UPF sends a fifth response message to the second SMF, which is used to indicate that the first session has been established on the second boundary CA-UPF side.

[0245] Correspondingly, the second SMF receives the fifth response message from the second boundary CA-UPF.

[0246] Optionally, the fifth response message may include identification information of the cross-domain computing power awareness network.

[0247] The fifth response message can also be understood as indicating that the inter-domain virtual network level session establishment on the second boundary CA-UPF side is complete. Therefore, the fifth response message can be called the inter-domain virtual network level session establishment response message, or it may have other names, which are not limited.

[0248] Understandably, the completion of the first session establishment on the second boundary CA-UPF side signifies the completion of the first session establishment on the second domain side. Therefore, the fifth response message can also be used to indicate that the first session has been established on the second domain side.

[0249] Therefore, in Embodiment 1 of this application, after the second SMF receives the second request message from the second CMF, the second SMF can complete the inter-domain session creation process by interacting with the first SMF (as shown in steps S506 to S510 above), thereby establishing an inter-domain forwarding tunnel between the first boundary CA-UPF and the second boundary CA-UPF, as well as inter-domain forwarding neighbor relationships and inter-domain announcement neighbor relationships.

[0250] It should be noted that in the process of creating an inter-domain session, the inter-domain tunnel information used to establish the inter-domain forwarding tunnel between the first boundary CA-UPF and the second boundary CA-UPF can be generated by the SMF or by the boundary CA-UPF. Depending on whether the inter-domain tunnel information is generated by the SMF or the boundary CA-UPF, and considering that both the establishment of the first and second inter-domain forwarding tunnels requires the corresponding inter-domain tunnel information, the inter-domain session creation process in Embodiment 1 can have two possible implementations, which will be referred to as Implementation 1 and Implementation 2 below.

[0251] like Figure 6 As shown, the inter-domain session creation process corresponding to Implementation Method 1 may include:

[0252] In step S601, the second SMF generates first inter-domain tunnel information based on the identification information of the first boundary CA-UPF. This first inter-domain tunnel information is used to establish a first inter-domain forwarding tunnel. For example, the first inter-domain tunnel information includes the identification information of the first inter-domain forwarding tunnel and the device IP address of the second boundary CA-UPF.

[0253] In step S602, the second SMF sends a first request message to the first SMF. The first request message is used to request the establishment of a first session, that is, a cross-domain virtual network level session.

[0254] Correspondingly, the first SMF receives the first request message from the second SMF.

[0255] The first request message includes the identification information of the cross-domain computing power sensing network, the identification information of the first boundary CA-UPF, the identification information of the second boundary CA-UPF, and the first inter-domain tunnel information.

[0256] In step S603, the first SMF sends a second request message to the first boundary CA-UPF. The second request message is used to request the establishment of a first session, that is, to request the establishment of an inter-domain virtual network level session on the first boundary CA-UPF side.

[0257] Correspondingly, the first boundary CA-UPF receives a second request message from the first SMF.

[0258] The second request message includes the identification information of the cross-domain computing power awareness network, the inter-domain forwarding neighbor list of the first boundary CA-UPF, and the first inter-domain tunnel information. The inter-domain forwarding neighbor list includes the identification information of the second boundary CA-UPF. Optionally, the second request message also includes the identification information of the first boundary CA-UPF.

[0259] Step S604: The first boundary CA-UPF establishes an inter-domain forwarding neighbor relationship and a first inter-domain forwarding tunnel between the first boundary CA-UPF and the second boundary CA-UPF based on the inter-domain forwarding neighbor list and the first inter-domain tunnel information.

[0260] Specifically, after receiving the second request message from the first SMF, the first boundary CA-UPF can create a corresponding internal interface for the cross-domain computing power sensing network based on the identification information of the cross-domain computing power sensing network. Then, it records or updates the inter-domain forwarding neighbor relationship between the first boundary CA-UPF and the second boundary CA-UPF based on the inter-domain forwarding neighbor list. Based on the first inter-domain tunnel information, it determines the connection relationship and corresponding tunnel forwarding rules between the internal interface of the cross-domain computing power sensing network and the external interface of the first boundary CA-UPF.

[0261] In step S605, the first boundary CA-UPF sends a second response message to the first SMF. The second response message is used to indicate that the first session has been established on the first boundary CA-UPF side, that is, to indicate that the inter-domain virtual network level session on the first boundary CA-UPF side has been established.

[0262] Correspondingly, the first SMF receives a second response message from the first boundary CA-UPF.

[0263] The second response message includes the identification information of the cross-domain computing power awareness network.

[0264] In step S606, the first SMF generates second inter-domain tunnel information based on the identification information of the second boundary CA-UPF. This second inter-domain tunnel information is used to establish a second inter-domain forwarding tunnel. For example, the second inter-domain tunnel information includes the identification information of the second inter-domain forwarding tunnel and the device IP address of the first boundary CA-UPF.

[0265] In step S607, the first SMF sends a first response message to the second SMF, which indicates that the first session has been established on the first domain side.

[0266] Correspondingly, the second SMF receives the first response message from the first SMF.

[0267] The first response message includes the identification information of the cross-domain computing power perception network and the inter-domain tunnel information.

[0268] In step S608, the second SMF sends a fifth request message to the second boundary CA-UPF. This fifth request message is used to request the establishment of a first session, that is, to request the establishment of an inter-domain virtual network level session on the second boundary CA-UPF side.

[0269] Correspondingly, the second boundary CA-UPF receives the fifth request message from the second SMF.

[0270] The fifth request message includes the identification information of the cross-domain computing power awareness network, the inter-domain announcement neighbor list of the second boundary CA-UPF, and the second-domain tunnel information. Optionally, the fifth request message may also include the identification information of the second boundary CA-UPF.

[0271] Step S609: The second boundary CA-UPF establishes an inter-domain announcement neighbor relationship and an inter-domain forwarding tunnel between the second boundary CA-UPF and the first boundary CA-UPF based on the inter-domain announcement neighbor list and the second inter-domain tunnel information.

[0272] Specifically, after receiving the fifth request message from the second SMF, the second boundary CA-UPF can create a corresponding internal interface for the cross-domain computing power sensing network based on the identification information of the cross-domain computing power sensing network, record or update the inter-domain announcement neighbor relationship between the second boundary CA-UPF and the first boundary CA-UPF according to the inter-domain announcement neighbor list, and establish the connection relationship and corresponding tunnel forwarding rules between the internal interface of the cross-domain computing power sensing network and the external interface of the second boundary CA-UPF according to the second inter-domain tunnel information.

[0273] In step S610, the second boundary CA-UPF sends a fifth response message to the second SMF. This fifth response message is used to indicate that the first session has been established at the second boundary CA-UPF, that is, to indicate that the inter-domain virtual network level session on the second boundary CA-UPF side has been established.

[0274] Correspondingly, the second SMF receives the fifth response message from the second boundary CA-UPF.

[0275] The fifth response message includes the identification information of the cross-domain computing power perception network.

[0276] In the above-described implementation method one, the first inter-domain tunnel information is generated by the second SMF and is used by the first SMF to establish a virtual network-level session of the first boundary CA-UPF; the second inter-domain tunnel information is generated by the first SMF and is used by the second SMF to establish a virtual network-level session of the second boundary CA-UPF.

[0277] Steps S603 to S605 describe the process by which the first SMF establishes a first session (i.e., an inter-domain virtual network level session on the first boundary CA-UPF side) by interacting with the first boundary CA-UPF. Steps S608 to S610 describe the process by which the second SMF establishes a first session (i.e., an inter-domain virtual network level session on the second boundary CA-UPF side) by interacting with the second boundary CA-UPF. Understandably, the execution of steps S603 to S605 depends on the first inter-domain tunnel information provided by the second SMF, and the execution of steps S608 to S610 depends on the second inter-domain tunnel information provided by the first SMF. Therefore, steps S603 to S605 are executed after step S602, and steps S608 to S610 are executed after step S607. However, it should be noted that this application does not specifically limit the execution order between steps S603 to S605 and step S606.

[0278] like Figure 7 As shown, the inter-domain session creation process corresponding to Implementation Method 2 includes:

[0279] Step S701: The second SMF sends a tenth request message to the second boundary CA-UPF. The tenth request message is used to request the establishment of a first session, that is, to request the establishment of an inter-domain virtual network level session on the second boundary CA-UPF side.

[0280] Correspondingly, the second boundary CA-UPF receives the tenth request message from the second SMF.

[0281] The tenth request message includes the identification information of the cross-domain computing power awareness network and the inter-domain announcement neighbor list of the second boundary CA-UPF, which includes the identification information of the first boundary CA-UPF. Optionally, the tenth request message also includes the identification information of the second boundary CA-UPF.

[0282] In step S702, the second boundary CA-UPF generates first inter-domain tunnel information based on the identification information of the first boundary CA-UPF. This first inter-domain tunnel information is used to establish a first inter-domain forwarding tunnel. For example, the first inter-domain tunnel information includes the identification information of the first inter-domain forwarding tunnel and the device IP address of the second boundary CA-UPF.

[0283] In step S703, the second boundary CA-UPF sends a tenth response message to the second SMF. This tenth response message is used to indicate that the first session has been established on the second boundary CA-UPF side, that is, to indicate that the inter-domain virtual network level session on the second boundary CA-UPF side has been established.

[0284] Correspondingly, the second SMF receives the tenth response message from the second boundary CA-UPF.

[0285] The tenth response message includes the identification information of the cross-domain computing power perception network and the first-domain tunnel information.

[0286] In step S704, the second SMF sends a first request message to the first SMF. The first request message is used to request the establishment of a first session, that is, to request the establishment of a cross-domain virtual network level session.

[0287] Correspondingly, the first SMF receives the first request message from the second SMF.

[0288] The first request message includes the identification information of the cross-domain computing power sensing network, the identification information of the first boundary CA-UPF, the identification information of the second boundary CA-UPF, and the first inter-domain tunnel information.

[0289] In step S705, the first SMF sends a second request message to the first boundary CA-UPF. The second request message is used to request the establishment of a first session, that is, to request the establishment of an inter-domain virtual network level session on the first boundary CA-UPF side.

[0290] Correspondingly, the first boundary CA-UPF receives a second request message from the first SMF.

[0291] The second request message includes the identification information of the cross-domain computing power awareness network, the inter-domain forwarding neighbor list of the first boundary CA-UPF, and the first inter-domain tunnel information. The inter-domain forwarding neighbor list includes the identification information of the second boundary CA-UPF. The second request message also includes the identification information of the first boundary CA-UPF.

[0292] Step S706: The first boundary CA-UPF establishes an inter-domain forwarding neighbor relationship and a first inter-domain forwarding tunnel between the first boundary CA-UPF and the second boundary CA-UPF based on the inter-domain forwarding neighbor list and the first inter-domain tunnel information.

[0293] Specifically, after receiving the second request message from the first SMF, the first boundary CA-UPF can create a corresponding internal interface for the cross-domain computing power sensing network based on the identification information of the cross-domain computing power sensing network. Then, it records or updates the inter-domain forwarding neighbor relationship between the first boundary CA-UPF and the second boundary CA-UPF according to the inter-domain forwarding neighbor list. Based on the first inter-domain tunnel information, it determines the connection relationship and corresponding tunnel forwarding rules between the internal interface of the cross-domain computing power sensing network and the external interface of the first boundary CA-UPF.

[0294] In step S707, the first boundary CA-UPF generates second inter-domain tunnel information based on the identification information of the second boundary CA-UPF. This second inter-domain tunnel information is used to establish a second inter-domain forwarding tunnel. For example, the second inter-domain tunnel information includes the identification information of the second inter-domain forwarding tunnel and the device IP address of the first boundary CA-UPF.

[0295] In step S708, the first boundary CA-UPF sends a second response message to the first SMF. The second response message is used to indicate that the first session has been established on the first boundary CA-UPF side, that is, to indicate that the inter-domain virtual network level session on the first boundary CA-UPF side has been established.

[0296] Correspondingly, the first SMF receives a second response message from the first boundary CA-UPF.

[0297] The second response message includes the identification information of the cross-domain computing power perception network and the inter-domain tunnel information.

[0298] In step S709, the first SMF sends a first response message to the second SMF, which indicates that the first session has been established on the first domain side.

[0299] Correspondingly, the second SMF receives the first response message from the first SMF.

[0300] The first response message includes the identification information of the cross-domain computing power perception network and the inter-domain tunnel information.

[0301] In step S710, the second SMF sends a fifth request message to the second boundary CA-UPF. This fifth request message is used to request an update to the first session, that is, to request an update to the inter-domain virtual network level session of the second boundary CA-UPF.

[0302] Correspondingly, the second boundary CA-UPF receives the fifth request message from the second SMF.

[0303] The fifth request message includes the identification information of the cross-domain computing power awareness network, the inter-domain forwarding neighbor list of the first boundary CA-UPF, and the first inter-domain tunnel information. The inter-domain forwarding neighbor list includes the identification information of the second boundary computing power awareness user plane function. Optionally, the fifth request message also includes the identification information of the first boundary CA-UPF.

[0304] Step S711: The second boundary CA-UPF establishes an inter-domain announcement neighbor relationship and an inter-domain forwarding tunnel between the second boundary CA-UPF and the first boundary CA-UPF based on the inter-domain announcement neighbor list and the second inter-domain tunnel information.

[0305] Specifically, after receiving the fifth request message from the second SMF, the second boundary CA-UPF can create a corresponding internal interface for the cross-domain computing power sensing network based on the identification information of the cross-domain computing power sensing network, record or update the announcement neighbor relationship between the second boundary CA-UPF and the first boundary CA-UPF according to the inter-domain announcement neighbor list, and determine the connection relationship and corresponding tunnel forwarding rules between the internal interface of the cross-domain computing power sensing network and the external interface of the second boundary CA-UPF according to the second inter-domain tunnel information.

[0306] In step S712, the second boundary CA-UPF sends a fifth response message to the second SMF. This fifth response message is used to indicate that the first session update is complete, that is, to indicate that the inter-domain virtual network level session update on the second boundary CA-UPF side is complete.

[0307] Correspondingly, the second SMF receives the fifth response message from the second boundary CA-UPF.

[0308] The fifth response message includes the identification information of the cross-domain computing power perception network.

[0309] In the above-described second implementation method, the first inter-domain tunnel information is generated by the second boundary CA-UPF and is used by the first SMF to establish a virtual network-level session of the first boundary CA-UPF; the second inter-domain tunnel information is generated by the first boundary CA-UPF and is used by the second SMF to establish a virtual network-level session of the second boundary CA-UPF.

[0310] To obtain the first inter-domain tunnel information, the second SMF can send a tenth request message to the second boundary CA-UPF. Upon receiving this tenth request message, the second boundary CA-UPF generates the first inter-domain tunnel information and returns it to the second SMF via a tenth response message. During this process, because the tenth request message does not include the second inter-domain tunnel information, the second boundary CA-UPF cannot establish a second inter-domain forwarding tunnel. Therefore, the first session on the second boundary CA-UPF side (i.e., the virtual network-level session on the second boundary CA-UPF side) is not truly established successfully. Subsequently, when the second SMF receives the first response message from the first SMF, it can carry the second inter-domain tunnel information and send a fifth request message to the second boundary CA-UPF, updating the first session through further interaction with the second boundary CA-UPF.

[0311] Understandably, steps S705 to S708 are executed after step S704, and steps S710 to S712 are executed after step S709. However, it should be noted that this application does not specifically limit the execution order between steps S706 and S707.

[0312] Step S511: The second SMF sends a sixth response message to the second CMF, which is used to indicate that the first session has been established.

[0313] Correspondingly, the second CMF receives the sixth response message from the second SMF.

[0314] The sixth response message includes the identification information of the cross-domain computing power perception network.

[0315] The sixth response message can be understood as indicating that the inter-domain session or inter-domain forwarding path of the cross-domain computing power awareness network has been established. Therefore, the sixth response message can be called the cross-domain computing power awareness network inter-domain session establishment response message, or it may have other names, which are not limited in this application.

[0316] Understandably, the sixth response message signifies the completion of the inter-domain session between the first boundary CA-UPF in the first domain and the second boundary CA-UPF in the second domain. Thus, after receiving the sixth response message from the second SMF, the second CMF can continue creating or updating the intra-domain portion of the cross-domain computing power awareness network in the second domain.

[0317] Step S512: The second CMF creates or updates the cross-domain computing power awareness network within the second domain.

[0318] For the creation portion within the domain, the second CMF can determine which intra-domain CA-UPF members are included in the second domain (i.e., determine the M intra-domain CA-UPFs), use the second boundary CA-UPF as the inter-domain entry CA-UPF, determine the intra-domain forwarding neighbor relationship and / or intra-domain advertising neighbor relationship between the second boundary CA-UPF and the M intra-domain CA-UPFs, and determine the intra-domain forwarding neighbor relationship and / or intra-domain advertising neighbor relationship among the M intra-domain CA-UPFs, thereby establishing or updating intra-domain virtual network level sessions.

[0319] like Figure 8 As shown, the session establishment or update process of the cross-domain computing power awareness network in the second domain may include:

[0320] In step S801, the second CMF sends a seventh request message to the second SMF. This seventh request message is used to request the establishment or update of the third session of the cross-domain computing power awareness network in the second domain.

[0321] Correspondingly, the second SMF receives the seventh request message from the second CMF.

[0322] Optionally, the third session is a virtual network level session.

[0323] The seventh request message includes the identification information of the cross-domain computing power awareness network, the identification information of the second boundary CA-UPF, and the intra-domain forwarding neighbor list.

[0324] The seventh request message can be understood as a request to establish / update an intra-domain session within the cross-domain computing power awareness network or a forwarding path within the second domain. Therefore, the seventh request message can be called a cross-domain computing power awareness network intra-domain session establishment / update request message, or may have other names, which are not limited in this application.

[0325] In Embodiment 1 of this application, before the second CMF sends the seventh request message to the second SMF, the second CMF can generate an intra-domain forwarding neighbor list for the second boundary CA-UPF. This intra-domain forwarding neighbor list includes the identification information of P intra-domain CA-UPFs out of the M intra-domain CA-UPFs included in the second domain by the cross-domain computing power awareness network, where P is a positive integer less than or equal to M. Optionally, the second CMF can also generate an intra-domain announcement neighbor list for the second boundary CA-UPF. This intra-domain announcement neighbor list includes the identification information of Q intra-domain CA-UPFs out of the M intra-domain CA-UPFs, where Q is a positive integer less than or equal to M.

[0326] The second CMF can also generate a corresponding intra-domain forwarding neighbor list and / or intra-domain advertising neighbor list for each of the M intra-domain CA-UPFs. For example, taking a second intra-domain CA-UPF as an example, where this second intra-domain CA-UPF is one of the M intra-domain CA-UPFs, the second CMF can generate an intra-domain forwarding neighbor list and / or intra-domain advertising neighbor list for the second intra-domain CA-UPF. It can be understood that if the second intra-domain CA-UPF is an ingress CA-UPF, then the second intra-domain CA-UPF has a corresponding intra-domain forwarding neighbor list; if the second intra-domain CA-UPF is an egress CA-UPF, then the second intra-domain CA-UPF has a corresponding intra-domain advertising neighbor list.

[0327] Therefore, the seventh request message includes the identification information of the cross-domain computing power awareness network, the identification information of the second boundary CA-UPF and its intra-domain forwarding neighbor list, the identification information of the M intra-domain CA-UPFs, and the intra-domain forwarding neighbor list and / or intra-domain announcement neighbor list corresponding to each of the M intra-domain CA-UPFs. For example, the intra-domain forwarding neighbor list and / or intra-domain announcement neighbor list corresponding to the second intra-domain CA-UPF.

[0328] Optionally, the seventh request message may also include an intra-domain announcement neighbor list of the second boundary CA-UPF.

[0329] Understandably, if no intra-domain computing power awareness network exists within the second domain before the creation of the cross-domain computing power awareness network, the seventh request message can be used to request the establishment of a third session of the cross-domain computing power awareness network within the second domain. If the second CMF has already created an intra-domain computing power awareness network through the second SMF before the creation of the cross-domain computing power awareness network, the seventh request message can be used to request the update of the third session of the cross-domain computing power awareness network within the second domain. In this case, the intra-domain forwarding neighbor list and intra-domain advertising neighbor list carried in the seventh request message can be the updated intra-domain forwarding neighbor list and intra-domain advertising neighbor list.

[0330] Step S802: The second SMF establishes or updates the third session of the cross-domain computing power awareness network within the second domain.

[0331] like Figure 9 As shown, the process of establishing or updating a third session by the second SMF may include, on the second boundary CA-UPF side:

[0332] Step S901: The second SMF sends an eighth request message to the second boundary CA-UPF. This eighth request message is used to request the establishment or update of a third session, that is, to request the establishment or update of a session at the intra-domain virtual network level on the second boundary CA-UPF side. The eighth request message includes the identification information of the cross-domain computing power awareness network and the intra-domain forwarding neighbor list of the second boundary CA-UPF. Optionally, the eighth request message also includes the intra-domain advertised neighbor list of the second boundary CA-UPF. Step S902: The second boundary CA-UPF establishes or updates intra-domain forwarding neighbor relationships and intra-domain forwarding tunnels with the P intra-domain CA-UPFs according to its corresponding intra-domain forwarding neighbor list. The P intra-domain CA-UPFs are the exit CA-UPFs corresponding to the second boundary CA-UPF in the second domain, and their identification information is included in the intra-domain forwarding neighbor list of the second boundary CA-UPF. Optionally, the second boundary CA-UPF can also establish intra-domain advertised neighbor relationships with the Q intra-domain CA-UPFs according to its corresponding intra-domain advertised neighbor list. The Q intra-domain CA-UPFs are the entry CA-UPFs corresponding to the second boundary CA-UPF within the second domain, and their identification information is included in the intra-domain announced neighbor list of the second boundary CA-UPF. In step S903, the second boundary CA-UPF sends an eighth response message to the second SMF. This eighth response message indicates that the third session establishment or update is complete, that is, it indicates that the intra-domain virtual network level session establishment or update of the second boundary CA-UPF is complete. The eighth response message includes the identification information of the cross-domain computing power awareness network.

[0333] It should be noted that the process of establishing or updating the third session by the second SMF may also include the establishment or updating of the CA-UPF side in each of the M domain CA-UPFs, that is, establishing or updating the intra-domain virtual network level session in each of the M domain CA-UPFs.

[0334] For example, taking the CA-UPF within the second domain as an example, the process of the second SMF establishing or updating the third session may include on the CA-UPF side within the second domain:

[0335] In step S1001, the second SMF sends an eleventh request message to the CA-UPF in the second domain. This eleventh request message is used to request the establishment or update of a third session, that is, to request the establishment or update of a virtual network-level session within the domain on the second CA-UPF side. The eleventh request message includes the identification information of the cross-domain computing power awareness network, the intra-domain forwarding neighbor list of the CA-UPF in the second domain, and / or the intra-domain announcement neighbor list.

[0336] In step S1002, the second intra-domain CA-UPF establishes an intra-domain forwarding neighbor relationship and an intra-domain forwarding tunnel with its corresponding egress CA-UPF based on its corresponding intra-domain forwarding neighbor list. Optionally, the second intra-domain CA-UPF may also establish an intra-domain announcement neighbor relationship with its corresponding ingress CA-UPF based on its corresponding intra-domain announcement neighbor list.

[0337] In step S1003, the CA-UPF in the second domain sends an eleventh response message to the second SMF. The eleventh response message is used to indicate that the third session has been established or updated on the CA-UPF side in the second domain. That is, it is used to indicate that the session at the virtual network level within the domain of the second CA-UPF has been established or updated. The eleventh response message includes the identification information of the cross-domain computing power awareness network.

[0338] In step S803, the second SMF sends a seventh response message to the second CMF, which is used to indicate that the third session has been established or updated.

[0339] Correspondingly, the second CMF receives the seventh response message from the second SMF.

[0340] The seventh response message includes the identification information of the cross-domain computing power perception network.

[0341] In Embodiment 1 of this application, after the second SMF completes the establishment or update of the intra-domain virtual network level session of the second boundary CA-UPF and the intra-domain virtual network level session of each of the M CA-UPFs, it sends a seventh response message to the second CMF, indicating that the establishment or update of the forwarding path of the cross-domain computing power awareness network in the second domain is complete.

[0342] The seventh response message can be understood as indicating the completion of the establishment / update of an intra-domain session or a forwarding path within the second domain of the cross-domain computing power awareness network. Therefore, the seventh response message can be called the cross-domain computing power awareness network intra-domain session establishment / update response message, or may have other names, which are not limited in this application.

[0343] Step S513: The second CMF sends a ninth response message to the first CMF. The ninth response message is used to indicate that the cross-domain computing power awareness network has been created on the second domain side.

[0344] Correspondingly, the first CMF receives the ninth response message from the second CMF.

[0345] The ninth response message includes the identification information of the cross-domain computing power perception network.

[0346] The ninth response message may be called the cross-domain computing power sensing network creation response message, or may have other names, which are not limited in this application.

[0347] In Embodiment 1 of this application, the second CMF can send a ninth response message to the first CMF after completing the creation or update of the intra-domain portion of the cross-domain computing power sensing network in the second domain.

[0348] The ninth response message signifies the completion of the creation of the inter-domain portion of the cross-domain computing power awareness network (CMF), as well as the completion of the creation (or update) of the intra-domain portion of the CMF in the second domain. Alternatively, it can be understood as signifying the completion of the establishment or update of the inter-domain virtual network level session between the first boundary CA-UPF of the first domain and the second boundary CA-UPF of the second domain, and the completion of the establishment or update of the intra-domain virtual network level session between the second boundary CA-UPF and its corresponding exit CA-UPF in the second domain. Thus, after receiving the ninth response message from the second CMF, the first CMF can continue creating or updating the intra-domain portion of the CMF in the first domain.

[0349] Step S514: The first CMF creates or updates the cross-domain computing power awareness network within the first domain.

[0350] For the creation portion within the domain, the first CMF can determine which CA-UPFs are ingress CA-UPFs and which are egress CA-UPFs among the N intra-domain CA-UPFs and the first boundary CA-UPF included in the first domain. Then, for each CA-UPF (including intra-domain CA-UPFs and the first boundary CA-UPF, where the first boundary CA-UPF serves as the egress CA-UPF within the domain), a corresponding intra-domain forwarding neighbor list and / or intra-domain advertising neighbor list are generated, thereby establishing or updating intra-domain virtual network level sessions.

[0351] like Figure 11 As shown, the session creation or update process of the cross-domain computing power awareness network within the first domain may include:

[0352] In step S1101, the first CMF sends a third request message to the first SMF. The third request message is used to request the establishment or update of the second session of the cross-domain computing power awareness network in the first domain.

[0353] Correspondingly, the first SMF receives the third request message from the first CMF.

[0354] Optionally, the second session is a virtual network level session.

[0355] The third request message includes the identification information of the cross-domain computing power awareness network, the identification information of the first boundary CA-UPF, and the list of announced neighbors within the domain.

[0356] The third request message can be understood as a request to establish / update an intra-domain session within the cross-domain computing power awareness network or a forwarding path within the first domain. Therefore, the third request message can be called a cross-domain computing power awareness network intra-domain session establishment / update request message, or may have other names, which are not limited in this application.

[0357] In Embodiment 1 of this application, before the first CMF sends the third request message to the first SMF, the first CMF can generate an intra-domain announcement neighbor list for the first boundary CA-UPF. This intra-domain announcement neighbor list includes the identification information of L intra-domain CA-UPFs among the N intra-domain CA-UPFs included in the first domain by the cross-domain computing power awareness network, where L is a positive integer less than or equal to N. Optionally, the first CMF can also generate an intra-domain forwarding neighbor list for the first boundary CA-UPF. This intra-domain forwarding neighbor list includes the identification information of K intra-domain CA-UPFs among the N intra-domain CA-UPFs, where K is a positive integer less than or equal to N.

[0358] The first CMF can also generate a corresponding intra-domain forwarding neighbor list and / or intra-domain advertising neighbor list for each of the N intra-domain CA-UPFs. For example, taking a first intra-domain CA-UPF as an example, where the first intra-domain CA-UPF is one of the N CA-UPFs, the first CMF can generate an intra-domain forwarding neighbor list and / or intra-domain advertising neighbor list for the first intra-domain CA-UPF. It can be understood that if the first intra-domain CA-UPF is an ingress CA-UPF, then the first intra-domain CA-UPF has a corresponding intra-domain forwarding neighbor list; if the first intra-domain CA-UPF is an egress CA-UPF, then the first intra-domain CA-UPF has a corresponding intra-domain advertising neighbor list.

[0359] Therefore, the third request message includes the identification information of the cross-domain computing power awareness network, the identification information and intra-domain announcement neighbor list of the first boundary CA-UPF, the identification information of the N intra-domain CA-UPFs, and the intra-domain forwarding neighbor list and / or intra-domain announcement neighbor list corresponding to each of the N intra-domain CA-UPFs. For example, the intra-domain forwarding neighbor list and / or intra-domain announcement neighbor list corresponding to the first intra-domain CA-UPF.

[0360] Optionally, the third request message may also include a list of intra-domain forwarding neighbors for the first boundary CA-UPF.

[0361] Understandably, if no intra-domain computing power awareness network exists within the first domain before the creation of the cross-domain computing power awareness network, the third request message can be used to request the establishment of a second session of the cross-domain computing power awareness network within the first domain. If the first CMF has already created an intra-domain computing power awareness network through the first SMF before the creation of the cross-domain computing power awareness network, the third request message can be used to request the update of the second session of the cross-domain computing power awareness network within the first domain. In this case, the intra-domain forwarding neighbor list and intra-domain advertising neighbor list carried in the third request message can be the updated intra-domain forwarding neighbor list and intra-domain advertising neighbor list.

[0362] Step S1102: The first SMF establishes or updates the second session of the cross-domain computing power awareness network within the first domain.

[0363] like Figure 12 As shown, the process of establishing or updating a second session using the first SMF may include, on the first boundary CA-UPF side:

[0364] Step S1201: The first SMF sends a fourth request message to the first boundary CA-UPF. This fourth request message is used to request the establishment or update of a second session, that is, to request the establishment or update of a session at the intra-domain virtual network level on the first boundary CA-UPF side. The fourth request message includes the identification information of the cross-domain computing power awareness network and the intra-domain advertised neighbor list of the first boundary CA-UPF. Optionally, the fourth request message may also include the intra-domain forwarding neighbor list of the first boundary CA-UPF. Step S1202: The first boundary CA-UPF establishes or updates intra-domain advertised neighbor relationships with the L intra-domain CA-UPFs according to its corresponding intra-domain advertised neighbor list. The L intra-domain CA-UPFs are the entry CA-UPFs corresponding to the first boundary CA-UPF in the first domain, and their identification information is included in the intra-domain advertised neighbor list of the first boundary CA-UPF. Optionally, the first boundary CA-UPF may also establish intra-domain forwarding neighbor relationships and intra-domain forwarding tunnels with the K intra-domain CA-UPFs according to its corresponding intra-domain forwarding neighbor list. The K intra-domain CA-UPFs are the egress CA-UPFs corresponding to the first boundary CA-UPF within the first domain, and their identification information is included in the intra-domain forwarding neighbor list of the first boundary CA-UPF. In step S1203, the first boundary CA-UPF sends a fourth response message to the first SMF. This fourth response message indicates that the second session has been established or updated on the first boundary CA-UPF side, that is, it indicates that the intra-domain virtual network level session on the first boundary CA-UPF side has been established or updated. This fourth response message includes the identification information of the cross-domain computing power awareness network.

[0365] It should be noted that the process of establishing or updating the second session by the first SMF may also include the establishment or updating of the CA-UPF side in each of the N domain CA-UPFs, that is, establishing or updating the intra-domain virtual network level session in each of the N domain CA-UPFs.

[0366] For example, taking a CA-UPF within a first domain as an example, the process of the first SMF establishing or updating a second session may include the following steps on the CA-UPF side: Step S1301, the first SMF sends a twelfth request message to the first CA-UPF. This twelfth request message is used to request the establishment or updating of the second session, that is, to request the establishment or updating of a session at the intra-domain virtual network level on the CA-UPF side of the first domain. The twelfth request message includes the identification information of the cross-domain computing power awareness network, the intra-domain forwarding neighbor list of the first CA-UPF, and / or the intra-domain advertised neighbor list. Step S1302, the first CA-UPF establishes an intra-domain forwarding neighbor relationship and an intra-domain forwarding tunnel with its corresponding egress CA-UPF based on its corresponding intra-domain forwarding neighbor list. Optionally, the first CA-UPF may also establish an intra-domain advertised neighbor relationship with its corresponding ingress CA-UPF based on its corresponding intra-domain advertised neighbor list. In step S1303, the CA-UPF in the first domain sends a twelfth response message to the first SMF. The twelfth response message is used to indicate that the second session has been established or updated on the CA-UPF side in the first domain. That is, it is used to indicate that the session at the intra-domain virtual network level on the CA-UPF side in the first domain has been established. The twelfth response message includes the identification information of the cross-domain computing power awareness network.

[0367] In step S1103, the first SMF sends a third response message to the first CMF. This third response message is used to indicate that the second session of the cross-domain computing power awareness network in the first domain has been established or updated.

[0368] Correspondingly, the first CMF receives the tenth response message from the first SMF.

[0369] The third response message includes the identification information of the cross-domain computing power perception network.

[0370] The third response message can be understood as indicating that the establishment / update of an intra-domain session within the cross-domain computing power awareness network or a forwarding path within the first domain is complete. Therefore, the third response message can be called a cross-domain computing power awareness network intra-domain session establishment / update response message, or may have other names, which are not limited in this application.

[0371] It should be noted that, as mentioned above, the first domain, as a local domain, can create cross-domain computing power awareness networks with one or more federation domains. Therefore, after the first CMF has determined that the inter-domain session with each federation domain has been created or updated, it can execute the method shown in steps S1101 to S1103 above to create or update the intra-domain computing power awareness network.

[0372] Optionally, after the first CMF completes the creation or update of the intra-domain portion of the cross-domain computing power awareness network in the first domain, it may also send a response message to the first OAM or the first UDM of the first domain to indicate that the cross-domain computing power awareness network has been successfully created.

[0373] As can be seen from the above, this application introduces boundary CA-UPF into the infrastructure of the computing power-aware network to realize computing power routing between multiple operator networks, thereby enabling the sharing of edge computing power among operators. This solves the problem of limited edge application coverage and user base faced by a single operator's computing power network, and is conducive to aggregating the infrastructure capabilities of multiple operators, providing application providers and enterprise users with a unified capability open interface, and realizing a consistent and seamless edge service experience across operators.

[0374] Example 2

[0375] Embodiment 2 of this application provides a session management method for a cross-domain computing power awareness network. Specifically, this method is a method for creating a cross-domain computing power awareness network between a first domain and a second domain, corresponding to Scheme 2 mentioned above.

[0376] Please refer to Figure 14 The above is a flowchart illustrating a session management method for a cross-domain computing power-aware network provided in Embodiment 2 of this application. The method includes:

[0377] Step S1401: The first CMF sends a thirteenth request message to the first SMF. The thirteenth request message is used to request the establishment of a first session between the first domain and the second domain of the cross-domain computing power awareness network. One end of the first session is connected to the first boundary CA-UPF of the first domain, and the other end is connected to the second boundary CA-UPF of the second domain.

[0378] Correspondingly, the first SMF receives the thirteenth request message from the first CMF.

[0379] The thirteenth request message includes one or more of the following information: the identification information of the cross-domain computing power sensing network, the identification information of the first boundary CA-UPF, the identification information of the second boundary CA-UPF, or the identification information of the second SMF.

[0380] The thirteenth request message can be understood as a request to establish an inter-domain session or inter-domain forwarding path for a cross-domain computing power awareness network. Therefore, the thirteenth request message can be called a cross-domain computing power awareness network inter-domain session establishment request message, or may have other names, which are not limited in this application.

[0381] Optionally, the first session (i.e., the inter-domain session) is a virtual network level session.

[0382] In Embodiment 2 of this application, the first CMF can receive a request message from the first OAM or the first UDM of the first domain to create a cross-domain computing power awareness network. Based on the request message, it determines that a cross-domain computing power awareness network needs to be created, and determines the CA-UPF members included in the first domain, such as N intra-domain CA-UPFs and a first boundary CA-UPF. The request message may include identification information of the cross-domain computing power awareness network to be created, a list of intra-domain members of the local domain, and a list of boundary members of the local domain. For a description of the identification information of the cross-domain computing power awareness network, the list of intra-domain members of the local domain, and the list of boundary members of the local domain, please refer to the relevant description in Embodiment 1; it will not be repeated here.

[0383] It should be noted that if the local domain's boundary member list includes identification information for one or more other boundary CA-UPFs, then in this case, the first CMF can send a request message to the first SMF for establishing an inter-domain session between the first domain and the corresponding federation domain for each boundary CA-UPF, and repeat the process. Figure 14 The method steps shown herein complete the creation of a cross-domain computing power awareness network with each alliance domain.

[0384] Furthermore, regarding the inter-domain creation part, the first CMF can generate an inter-domain forwarding neighbor list for the first boundary CA-UPF, which includes the identification information of the second boundary CA-UPF. Understandably, during the process of the first CMF generating the corresponding inter-domain forwarding neighbor list for the first boundary CA-UPF, the first CMF can determine that an inter-domain forwarding neighbor relationship exists between the first boundary CA-UPF and the second boundary CA-UPF in the corresponding second domain.

[0385] The first CMF can also determine the identification information of the second CMF, the second SMF, and the second boundary CA-UPF of the alliance domain (i.e., the second domain) connected by the first boundary CA-UPF, so as to send the aforementioned thirteenth request message to the first SMF, requesting the first SMF to initiate the inter-domain session creation process of the cross-domain computing power awareness network.

[0386] Optionally, the first CMF may also determine the inter-domain announcement neighbor list of the second boundary CA-UPF, which includes the identification information of the first boundary CA-UPF.

[0387] Thus, the thirteenth request message may include the identification information of the cross-domain computing power awareness network, the identification information of the first boundary CA-UPF and the inter-domain forwarding neighbor list, the identification information of the second boundary CA-UPF and the inter-domain announcement neighbor list, and the identification information of the second SMF.

[0388] Understandably, if the first domain, as a local domain, has direct connections with multiple federation domains (i.e., there are multiple boundary CA-UPFs in the first domain), then the first CMF can determine the identification information of the CMF, SMF, and boundary CA-UPF in the peer federation domain connected to each boundary CA-UPF in the first domain. Accordingly, the thirteenth request message may include the identification information of multiple boundary CA-UPFs in the first domain and the inter-domain forwarding neighbor list, as well as the identification information of the boundary CA-UPF of the federation domain corresponding to each boundary CA-UPF and the inter-domain announcement neighbor list.

[0389] Step S1402: The first SMF sends a fourteenth request message to the second SMF, which is used to request the establishment of a first session.

[0390] Correspondingly, the second SMF receives the fourteenth request message from the first SMF.

[0391] In Embodiment 2 of this application, after receiving the thirteenth request message from the first CMF, the first SMF can determine, based on the identification information of the cross-domain computing power sensing network, the identification information of the first boundary CA-UPF, and the identification information of the second boundary CA-UPF, that it is necessary to establish a first session between the first boundary CA-UPF of the first domain and the second boundary CA-UPF of the second domain. Then, based on the identification information of the second SMF, the first SMF is determined, and the fourteenth request message is sent to the second SMF.

[0392] The fourteenth request message includes one or more of the following information: the identification information of the cross-domain computing power sensing network, the identification information of the first boundary CA-UPF, the identification information of the second boundary CA-UPF, or the second inter-domain tunnel information.

[0393] Specifically, the second inter-domain tunnel information is used to establish a second inter-domain forwarding tunnel between the first boundary CA-UPF and the second boundary CA-UPF. Considering that there are forwarding tunnels in two directions between the first and second boundary CA-UPFs, this second inter-domain tunnel information is specifically used to establish a tunnel for sending messages from the second boundary CA-UPF to the first boundary CA-UPF, or in other words, a forwarding tunnel from the second boundary CA-UPF to the first boundary CA-UPF. For clarity, this tunnel will be referred to as the second inter-domain forwarding tunnel.

[0394] Understandably, since the first boundary CA-UPF and the second boundary CA-UPF are inter-domain forwarding neighbors and advertising neighbors, the inter-domain forwarding neighbor list of the first boundary CA-UPF includes the identification information of the second boundary CA-UPF, and the inter-domain advertising neighbor list of the second boundary CA-UPF includes the identification information of the first boundary CA-UPF. Therefore, it can also be considered that the fourteenth request message includes the identification information of the first boundary CA-UPF and its inter-domain forwarding neighbor list, and / or, the identification information of the second boundary CA-UPF and its inter-domain advertising neighbor list.

[0395] The fourteenth request message can also be understood as a request to establish a cross-domain virtual network level session. Therefore, the fourteenth request message can be called a cross-domain virtual network level session establishment request message, or it may have other names, which are not limited.

[0396] Step S1403: The second SMF sends a fifteenth request message to the second boundary CA-UPF, which is used to request the establishment of the first session.

[0397] Correspondingly, the second boundary CA-UPF receives the fifteenth request message from the second SMF.

[0398] In the second embodiment of this application, after receiving the fourteenth request message from the second SMF, the second SMF can determine, based on the identification information of the cross-domain computing power sensing network, the identification information of the first boundary CA-UPF, and the identification information of the second boundary CA-UPF, that it is necessary to establish a first session between the first boundary CA-UPF of the first domain and the second boundary CA-UPF of the second domain. Then, based on the identification information of the second boundary CA-UPF, the second boundary CA-UPF is determined, and the fifteenth request message is sent to the second boundary CA-UPF.

[0399] The fifteenth request message can also be understood as a request to establish an inter-domain virtual network level session on the second boundary CA-UPF side. Therefore, the fifteenth request message can be called an inter-domain virtual network level session establishment request message, or it may have other names, which are not limited.

[0400] Step S1404: The second boundary CA-UPF establishes a second inter-domain forwarding tunnel with the first boundary CA-UPF.

[0401] In Embodiment 2 of this application, both the fourteenth and fifteenth request messages include the aforementioned second inter-domain tunnel information. Thus, after the second boundary CA-UPF receives the fifteenth request message from the second SMF, it can establish a second inter-domain forwarding tunnel based on this second inter-domain tunnel information.

[0402] Furthermore, both the fourteenth and fifteenth request messages include the identification information of the first boundary CA-UPF, i.e., the inter-domain advertised neighbor list of the second boundary CA-UPF. Thus, after receiving the fifteenth request message from the second SMF, the second boundary CA-UPF can establish an inter-domain advertised neighbor relationship with the first boundary CA-UPF based on its corresponding inter-domain advertised neighbor list. This inter-domain advertised neighbor relationship is used by the second boundary CA-UPF to advertise the domain-level service capability information of the second domain to the first boundary CA-UPF. In other words, the second boundary CA-UPF can determine that the first boundary CA-UPF is its corresponding inter-domain advertised neighbor based on the identification information of the first boundary CA-UPF included in the inter-domain advertised neighbor list.

[0403] Optionally, the fifteenth request message may also include identification information of the cross-domain computing power awareness network.

[0404] Step S1405: The second boundary CA-UPF sends a fifteenth response message to the second SMF. This fifteenth response message is used to indicate that the first session has been established on the second boundary CA-UPF side.

[0405] Correspondingly, the second SMF receives the fifteenth response message from the second boundary CA-UPF.

[0406] Optionally, the fifteenth response message may include identification information of the cross-domain computing power awareness network.

[0407] The fifteenth response message can also be understood as indicating that the inter-domain virtual network level session establishment on the second boundary CA-UPF side is complete. Therefore, the fifteenth response message can be called an inter-domain virtual network level session establishment response message, or have other names, without limitation.

[0408] Understandably, the completion of the first session establishment on the second boundary CA-UPF side signifies the completion of the first session establishment on the second domain side. Therefore, the fifteenth response message can also be used to indicate the completion of the first session establishment on the second domain side.

[0409] Step S1406: The second SMF sends a fourteenth response message to the first SMF, which indicates that the first session has been established on the second domain side.

[0410] Correspondingly, the first SMF receives the fourteenth response message from the second SMF.

[0411] The fourteenth response message includes one or more of the following information: identification information of the cross-domain computing power awareness network or first-domain tunnel information. The first-domain tunnel information is used to establish a tunnel between the first boundary CA-UPF and the second boundary CA-UPF. Considering that there are two-way forwarding tunnels between the first boundary CA-UPF and the second boundary CA-UPF, the first-domain tunnel information here is specifically used to establish a tunnel for sending messages from the first boundary CA-UPF to the second boundary CA-UPF, or in other words, a forwarding tunnel from the first boundary CA-UPF to the second boundary CA-UPF. For clarity, this tunnel will be referred to as the first-domain forwarding tunnel.

[0412] The fourteenth response message can also be understood as indicating that the cross-domain virtual network level session has been successfully established on the second domain side. Therefore, the fourteenth response message can be called a cross-domain virtual network level session establishment response message, or it can have other names, which are not limited.

[0413] Step S1407: The first SMF sends a sixteenth request message to the first boundary CA-UPF, which is used to request the establishment of the first session.

[0414] Accordingly, the first boundary CA-UPF receives the sixteenth request message from the first SMF.

[0415] The sixteenth request message can also be understood as a request to establish an inter-domain virtual network level session on the first boundary CA-UPF side. Therefore, the sixteenth request message can be called an inter-domain virtual network level session establishment request message, or it may have other names, which are not limited.

[0416] Step S1408: The first boundary CA-UPF establishes a first inter-domain forwarding tunnel with the second boundary CA-UPF.

[0417] In Embodiment 2 of this application, both the fourteenth response message and the sixteenth request message include the aforementioned first inter-domain tunnel information. Thus, after the first boundary CA-UPF receives the sixteenth request message from the first SMF, it can establish a first inter-domain forwarding tunnel based on the first inter-domain tunnel information.

[0418] Furthermore, the sixteenth request message includes the identification information of the second boundary CA-UPF, which is the inter-domain forwarding neighbor list of the first boundary CA-UPF. Thus, after receiving the sixteenth request message from the first SMF, the first boundary CA-UPF can establish an inter-domain forwarding neighbor relationship with the second boundary CA-UPF based on its corresponding inter-domain forwarding neighbor list. This inter-domain forwarding neighbor relationship is used by the first boundary CA-UPF to send inter-domain service request messages to the second boundary CA-UPF. In other words, the first boundary CA-UPF can determine that the second boundary CA-UPF is its corresponding inter-domain forwarding neighbor based on the identification information of the second boundary CA-UPF included in the inter-domain forwarding neighbor list.

[0419] Optionally, the sixteenth request message may also include identification information for the cross-domain computing power awareness network.

[0420] Step S1409: The first boundary CA-UPF sends a sixteenth response message to the first SMF. The sixteenth response message is used to indicate that the first session has been established on the first boundary CA-UPF side.

[0421] Accordingly, the first SMF receives the sixteenth response message from the first boundary CA-UPF.

[0422] Optionally, the sixteenth response message may include identification information of the cross-domain computing power awareness network.

[0423] The sixteenth response message can also be understood as indicating that the inter-domain virtual network level session establishment on the first boundary CA-UPF side is complete. Therefore, the sixteenth response message can be called an inter-domain virtual network level session establishment response message, or have other names, without limitation.

[0424] Understandably, the completion of the first session establishment on the first boundary CA-UPF side signifies the completion of the first session establishment on the first domain side. Therefore, the sixteenth response message can also be used to indicate that the first session has been established on the first domain side.

[0425] Therefore, in Embodiment 2 of this application, after the first SMF receives the thirteenth request message from the first CMF, it can complete the inter-domain session creation process by interacting with the second SMF (as shown in steps S1403 to S1407 above), thereby establishing an inter-domain forwarding tunnel between the first boundary CA-UPF and the second boundary CA-UPF, as well as inter-domain forwarding neighbor relationships and inter-domain announcement neighbor relationships.

[0426] It should be noted that, depending on whether the inter-domain tunnel information is generated by SMF or by the boundary CA-UPF, and considering that the establishment of the first and second inter-domain forwarding tunnels both require corresponding inter-domain tunnel information, the inter-domain session creation process in Embodiment 2 can also have two possible implementation methods, which will be referred to as Embodiment 3 and Embodiment 4 below.

[0427] like Figure 15 As shown, the inter-domain session creation process corresponding to Implementation Method 3 may include:

[0428] In step S1501, the first SMF generates second inter-domain tunnel information based on the identification information of the second boundary CA-UPF. This second inter-domain tunnel information is used to establish a second inter-domain forwarding tunnel. For example, the second inter-domain tunnel information includes the identification information of the second inter-domain forwarding tunnel and the device IP address of the first boundary CA-UPF.

[0429] In step S1502, the first SMF sends a fourteenth request message to the second SMF. This fourteenth request message is used to request the establishment of a first session, that is, to request the establishment of a cross-domain virtual network level session.

[0430] Correspondingly, the second SMF receives the fourteenth request message from the first SMF.

[0431] The fourteenth request message includes the identification information of the cross-domain computing power sensing network, the identification information of the first boundary CA-UPF, the identification information of the second boundary CA-UPF, and the second inter-domain tunnel information.

[0432] In step S1503, the second SMF sends a fifteenth request message to the second boundary CA-UPF. The fifteenth request message is used to request the establishment of a first session, that is, to request the establishment of an inter-domain virtual network level session on the second boundary CA-UPF side.

[0433] Correspondingly, the second boundary CA-UPF receives the fifteenth request message from the second SMF.

[0434] The fifteenth request message includes the identification information of the cross-domain computing power awareness network, the inter-domain announcement member list of the second boundary CA-UPF, and the second inter-domain tunnel information. The inter-domain announcement neighbor list includes the identification information of the first boundary CA-UPF. Optionally, the fifteenth request message also includes the identification information of the second boundary CA-UPF.

[0435] Step S1504: The second boundary CA-UPF establishes an inter-domain announcement neighbor relationship and an inter-domain forwarding tunnel between the second boundary CA-UPF and the first boundary CA-UPF based on the inter-domain announcement neighbor list and the second inter-domain tunnel information.

[0436] In step S1505, the second boundary CA-UPF sends a fifteenth response message to the second SMF. This fifteenth response message is used to indicate that the first session has been established on the second boundary CA-UPF side, that is, to indicate that the inter-domain virtual network level session on the second boundary CA-UPF side has been established.

[0437] Correspondingly, the second SMF receives the fifteenth response message from the second boundary CA-UPF.

[0438] The fifteenth response message includes the identification information of the cross-domain computing power awareness network.

[0439] In step S1506, the second SMF generates first inter-domain tunnel information based on the identification information of the first boundary CA-UPF. This first inter-domain tunnel information is used to establish a first inter-domain forwarding tunnel. For example, the first inter-domain tunnel information includes the identification information of the first inter-domain forwarding tunnel and the device IP address of the second boundary CA-UPF.

[0440] In step S1507, the second SMF sends a fourteenth response message to the first SMF, which indicates that the first session has been established on the first domain side.

[0441] Correspondingly, the first SMF receives the fourteenth response message from the second SMF.

[0442] The fourteenth response message includes the identification information of the cross-domain computing power perception network and the first-domain tunnel information.

[0443] In step S1508, the first SMF sends a sixteenth request message to the first boundary CA-UPF. The sixteenth request message is used to request the establishment of a first session, that is, to request the establishment of an inter-domain virtual network level session on the first boundary CA-UPF side.

[0444] Accordingly, the first boundary CA-UPF receives the sixteenth request message from the first SMF.

[0445] The sixteenth request message includes the identification information of the cross-domain computing power awareness network, the inter-domain forwarding member list of the first boundary CA-UPF, and the first inter-domain tunnel information.

[0446] Step S1509: The first boundary CA-UPF establishes an inter-domain forwarding neighbor relationship and a first inter-domain forwarding tunnel between the first boundary CA-UPF and the second boundary CA-UPF based on the inter-domain forwarding neighbor list and the first inter-domain tunnel information.

[0447] In step S1510, the first boundary CA-UPF sends a sixteenth response message to the first SMF. This sixteenth response message is used to indicate that the first session has been established, that is, to indicate that the inter-domain virtual network level session on the first boundary CA-UPF side has been established.

[0448] Accordingly, the first SMF receives the sixteenth response message from the first boundary CA-UPF.

[0449] The sixteenth response message includes the identification information of the cross-domain computing power awareness network.

[0450] In the above-described third implementation method, the first inter-domain tunnel information is generated by the second SMF and is used by the first SMF to establish a virtual network-level session of the first boundary CA-UPF; the second inter-domain tunnel information is generated by the first SMF and is used by the second SMF to establish a virtual network-level session of the second boundary CA-UPF.

[0451] Steps S1503 to S1505 describe the process by which the second SMF establishes a first session (i.e., an inter-domain virtual network level session on the second boundary CA-UPF side) through interaction with the second boundary CA-UPF. Steps S1508 to S1510 describe the process by which the first SMF establishes a first session (i.e., an inter-domain virtual network level session on the first boundary CA-UPF side) through interaction with the first boundary CA-UPF. Understandably, the execution of steps S1503 to S1505 depends on the second inter-domain tunnel information provided by the first SMF, and the execution of steps S1508 to S1510 depends on the first inter-domain tunnel information provided by the second SMF. Therefore, steps S1503 to S1505 are executed after step S1502, while steps S1508 to S1510 are executed after step S1507. However, it should be noted that this application does not specify the execution order of steps S1503 to S1505 and step S1506.

[0452] like Figure 16 As shown, the inter-domain session creation process corresponding to Implementation Method 4 may include:

[0453] Step S1601: The first SMF sends a seventeenth request message to the first boundary CA-UPF. The seventeenth request message is used to request the establishment of a first session, that is, to request the establishment of an inter-domain virtual network level session on the first boundary CA-UPF side.

[0454] Accordingly, the first boundary CA-UPF receives the seventeenth request message from the first SMF.

[0455] The seventeenth request message includes the identification information of the cross-domain computing power awareness network and the inter-domain forwarding neighbor list of the first boundary CA-UPF, which includes the identification information of the second boundary CA-UPF. Optionally, the seventeenth request message also includes the identification information of the first boundary CA-UPF.

[0456] In step S1602, the first boundary CA-UPF generates second inter-domain tunnel information based on the identification information of the second boundary CA-UPF. This second inter-domain tunnel information is used to establish a second inter-domain forwarding tunnel. For example, the second inter-domain tunnel information includes the identification information of the second inter-domain forwarding tunnel and the device IP address of the first boundary CA-UPF.

[0457] In step S1603, the first boundary CA-UPF sends a seventeenth response message to the first SMF. This seventeenth response message is used to indicate that the first session has been established on the first boundary CA-UPF side, that is, to indicate that the inter-domain virtual network level session on the first boundary CA-UPF side has been established.

[0458] Accordingly, the first SMF receives the seventeenth response message from the first boundary CA-UPF.

[0459] The seventeenth response message includes the identification information of the cross-domain computing power perception network and the inter-domain tunnel information.

[0460] In step S1604, the first SMF sends a fourteenth request message to the second SMF. This fourteenth request message is used to request the establishment of a first session, that is, to request the establishment of a cross-domain virtual network level session.

[0461] Correspondingly, the second SMF receives the fourteenth request message from the first SMF.

[0462] The fourteenth request message includes the identification information of the cross-domain computing power sensing network, the identification information of the first boundary CA-UPF, the identification information of the second boundary CA-UPF, and the inter-domain tunnel information.

[0463] In step S1605, the second SMF sends a fifteenth request message to the second boundary CA-UPF. This fifteenth request message is used to request the establishment of a first session, that is, to request the establishment of an inter-domain virtual network level session on the second boundary CA-UPF side.

[0464] Correspondingly, the second boundary CA-UPF receives the fifteenth request message from the second SMF.

[0465] The fifteenth request message includes the identification information of the cross-domain computing power awareness network, the inter-domain announcement neighbor list of the second boundary CA-UPF, and the second-domain tunnel information. The inter-domain announcement neighbor list includes the identification information of the first boundary CA-UPF. Optionally, the fifteenth request message also includes the identification information of the second boundary CA-UPF.

[0466] Step S1606: The second boundary CA-UPF establishes an inter-domain announcement neighbor relationship and an inter-domain forwarding tunnel between the second boundary CA-UPF and the first boundary CA-UPF based on the inter-domain announcement neighbor list and the second inter-domain tunnel information.

[0467] In step S1607, the second boundary CA-UPF generates first inter-domain tunnel information based on the identification information of the first boundary CA-UPF. This first inter-domain tunnel information is used to establish a first inter-domain forwarding tunnel. For example, the first inter-domain tunnel information includes the identification information of the first inter-domain forwarding tunnel and the device IP address of the second boundary CA-UPF.

[0468] In step S1608, the second boundary CA-UPF sends a fifteenth response message to the second SMF. This fifteenth response message is used to indicate that the first session has been established on the second boundary CA-UPF side, that is, to indicate that the inter-domain virtual network level session of the second boundary CA-UPF has been established.

[0469] Correspondingly, the second SMF receives the fifteenth response message from the second boundary CA-UPF.

[0470] The fifteenth response message includes the identification information of the cross-domain computing power perception network and the first-domain tunnel information.

[0471] In step S1609, the second SMF sends a fourteenth response message to the first SMF, which indicates that the first session has been established on the first domain side.

[0472] Correspondingly, the first SMF receives the fourteenth response message from the second SMF.

[0473] The fourteenth response message includes the identification information of the cross-domain computing power perception network and the first-domain tunnel information.

[0474] In step S1610, the first SMF sends a sixteenth request message to the first boundary CA-UPF. The sixteenth request message is used to request an update to the first session, that is, to request an update to the inter-domain virtual network level session on the first boundary CA-UPF side.

[0475] Accordingly, the first boundary CA-UPF receives the sixteenth request message from the first SMF.

[0476] The sixteenth request message includes the identification information of the cross-domain computing power awareness network, the inter-domain forwarding neighbor list of the first boundary CA-UPF, and the first inter-domain tunnel information. The inter-domain forwarding neighbor list includes the identification information of the second boundary computing power awareness user plane function. Optionally, the sixteenth request message includes the identification information of the first boundary CA-UPF.

[0477] Step S1611: The first boundary CA-UPF establishes an inter-domain forwarding neighbor relationship and a first inter-domain forwarding tunnel between the first boundary CA-UPF and the second boundary CA-UPF based on the inter-domain forwarding neighbor list and the first inter-domain tunnel information.

[0478] In step S1612, the first boundary CA-UPF sends a sixteenth response message to the first SMF. This sixteenth response message is used to indicate that the first session has been updated on the first boundary CA-UPF side, that is, to indicate that the session update at the inter-domain virtual network level of the first boundary CA-UPF has been completed.

[0479] Accordingly, the first SMF receives the sixteenth response message from the first boundary CA-UPF.

[0480] The sixteenth response message includes the identification information of the cross-domain computing power awareness network.

[0481] In the above-described implementation method four, the second inter-domain tunnel information is generated by the first boundary CA-UPF and is used by the second SMF to establish a virtual network-level session of the second boundary CA-UPF; the first inter-domain tunnel information is generated by the second boundary CA-UPF and is used by the first SMF to establish a virtual network-level session of the first boundary CA-UPF.

[0482] To obtain the second inter-domain tunnel information, the first SMF can send a seventeenth request message to the second boundary CA-UPF. Upon receiving this seventeenth request message, the first boundary CA-UPF generates the second inter-domain tunnel information and returns it to the first SMF via a seventeenth response message. During this process, because the seventeenth request message does not include the first inter-domain tunnel information, the first boundary CA-UPF cannot establish the first inter-domain forwarding tunnel. Therefore, the first session on the first boundary CA-UPF side (i.e., the virtual network-level session on the second boundary CA-UPF side) is not truly established successfully. Subsequently, when the first SMF receives the fourteenth response message from the second SMF, it can carry the first inter-domain tunnel information and update the first session by interacting with the first boundary CA-UPF again.

[0483] Understandably, steps S1605 to S1608 are executed after step S1604, and steps S1610 to S1612 are executed after step S1609. However, it should be noted that this application does not specifically limit the execution order between steps S1606 and S1607.

[0484] Step S1410: The first SMF sends a thirteenth response message to the first CMF, which is used to indicate that the first session has been established.

[0485] Correspondingly, the first CMF receives the thirteenth response message from the first SMF.

[0486] The thirteenth response message includes the identification information of the cross-domain computing power perception network.

[0487] The thirteenth response message can be understood as indicating the completion of the inter-domain session or inter-domain forwarding path establishment in the cross-domain computing power awareness network. Therefore, the thirteenth response message can be called the cross-domain computing power awareness network inter-domain session establishment response message, or it may have other names, which are not limited in this application.

[0488] Understandably, the thirteenth response message signifies the completion of the inter-domain session between the first boundary CA-UPF in the first domain and the second boundary CA-UPF in the second domain. Thus, after receiving the sixth response message from the first SMF, the first CMF can continue creating or updating the intra-domain portion of the cross-domain computing power awareness network in the first domain, or request the second CMF to create or update the intra-domain portion of the cross-domain computing power awareness network in the second domain.

[0489] Step S1411: The first CMF sends an eighteenth request message to the second CMF. The eighteenth request message is used to request the creation of a cross-domain computing power awareness network.

[0490] Correspondingly, the second CMF receives the eighteenth request message from the first CMF.

[0491] The eighteenth request message includes the identification information of the cross-domain computing power sensing network and the identification information of the second boundary CA-UPF.

[0492] The eighteenth request message may be called a cross-domain computing power sensing network creation request message, or may have other names, which are not limited in this application.

[0493] The eighteenth request message can also be understood as a request to create or update the third session of the cross-domain computing power awareness network in the second domain, that is, to request the creation or update of the intra-domain session or intra-domain forwarding path of the cross-domain computing power awareness network in the second domain.

[0494] Step S1412: The second CMF creates or updates the intra-domain portion of the cross-domain computing power awareness network in the second domain.

[0495] For a detailed implementation of step S1410, please refer to step S512 in Embodiment 1. Figures 8 to 10 The relevant descriptions will not be repeated here.

[0496] Step S1413: The second CMF sends the eighteenth response message to the first CMF. The eighteenth response message is used to indicate that the cross-domain computing power awareness network has been created on the second domain side.

[0497] Correspondingly, the first CMF receives the eighteenth response message from the second CMF.

[0498] The eighteenth response message includes the identification information of the cross-domain computing power perception network.

[0499] The eighteenth response message may be called the cross-domain computing power sensing network creation response message, or may have other names, which are not limited in this application.

[0500] The eighteenth response message can also be understood as indicating that the creation or update of the third session of the cross-domain computing power awareness network in the second domain is complete, that is, indicating that the creation or update of the intra-domain session or intra-domain forwarding path of the cross-domain computing power awareness network in the second domain is complete.

[0501] Step S1414: The first CMF creates or updates the intra-domain portion of the cross-domain computing power awareness network in the first domain.

[0502] For a detailed implementation of step S1414, please refer to step S514 in Embodiment 1. Figures 11 to 13 The relevant descriptions will not be repeated here.

[0503] It should be noted that in Embodiment 2 of this application, the execution order between steps S1411 to S1413 and step S1414 is not specifically limited. That is, the first CMF may first request the second CMF to create or update the intra-domain part of the cross-domain computing power sensing network in the second domain, or it may first create or update the intra-domain part of the cross-domain computing power sensing network in the first domain itself.

[0504] Optionally, after the first CMF completes the creation or update of the intra-domain portion of the cross-domain computing power awareness network in the first domain, it can also send a response message indicating that the cross-domain computing power awareness network has been successfully created to the first OAM or the first UDM of the first domain.

[0505] It should be noted that if the first domain, as a local domain, has direct connections to multiple consortium domains (i.e., multiple boundary CA-UPFs exist within the first domain), then the first SMF needs to interact with the SMF of each consortium domain to complete the inter-domain session creation process. Correspondingly, after the inter-domain session creation process is completed, the first CMF also needs to send a cross-domain computing power awareness network creation / update request to the CMF of each consortium domain, thereby completing the creation or update of the intra-domain portion of the cross-domain computing power awareness network in each consortium domain.

[0506] Example 3

[0507] Embodiment 3 of this application provides a session management method for a cross-domain computing power awareness network. Specifically, this method is a method for conducting cross-domain information announcements and constructing computing power routing information across operator networks in a cross-domain computing power awareness network.

[0508] It should be noted that in Embodiment 3 of this application, the CA-UPF in the first domain is the ingress CA-UPF in the first domain, and the CA-UPF in the second domain is the egress CA-UPF in the second domain, as an example for illustration.

[0509] Please refer to Figure 17 The above is a flowchart illustrating a session management method for a cross-domain computing power-aware network provided in Embodiment 3 of this application. The method includes:

[0510] Step S1701: The CA-UPF in the second domain sends a third announcement message to the CA-UPF at the second boundary. The third announcement message includes service capability information of the edge computing node associated with the CA-UPF in the second domain. The service capability information indicates the ability of the edge computing node to provide the first computing service to the outside world.

[0511] Correspondingly, the second boundary CA-UPF receives the third announcement message from the second CA-UPF.

[0512] Optionally, the third announcement message may also include the identification information of the CA-UPF in the second domain.

[0513] In Embodiment 3 of this application, before the CA-UPF in the second domain sends the third announcement message to the CA-UPF at the second boundary, the CA-UPF in the second domain can interact with its associated edge computing nodes and perform actions such as... Figure 18 The process shown is as follows:

[0514] In step S1801, the edge computing node in the second domain loads the first computing service and obtains the service identifier of the first computing service.

[0515] In step S1802, the edge computing node sends a service binding information reporting message to the CA-UPF in the associated second domain. The service binding information reporting message includes the service ID of the first computing service and the IP address of the server where the first computing service is located.

[0516] In step S1803, the CA-UPF in the second domain creates a binding relationship between the service identifier of the first computing service and the server IP address, so as to facilitate the subsequent conversion between the service identifier and the server IP address.

[0517] In step S1804, the edge computing node reports service capability information to the CA-UPF in the associated second domain. This service capability information is used to indicate the edge computing node's ability to provide the first computing service to the outside world.

[0518] The service capability information includes computing service information of the first computing service corresponding to the edge computing node and / or the load information of the edge computing node. The computing service information includes the service identifier, service attributes, running status, and computing resource information of the first computing service deployed on the edge computing node, indicating which computing services the edge computing node supports. The load information indicates the overall load status of the edge computing node; the load information of the edge computing node can also be called site load information. Service attributes indicate whether a computing service is stateless or stateful. The running status refers to the current status of the computing service corresponding to the service identifier on the server, including loaded, unloaded, running, suspended, available, and unavailable states. Computing resource information refers to the types of computing resources used by the computing service corresponding to the service identifier on EAS and related information about the use of computing resources. The types of computing resources can be central processing units (CPU), graphics processing units (GPU), neural network processing units (NPU), etc. The related information can be specific indicators such as CPU / GPU load, memory usage, number of service sessions used, number of requests per second, computing latency, etc., or it can be a comprehensive indicator calculated from these specific indicators.

[0519] For example, the MEC platform in an edge computing node can load a microservice or function instance on the EAS and obtain the service ID of that microservice or function instance. Then, the MEC platform sends a service binding information reporting message to the associated second CA-UPF. This message includes the service ID of the microservice or function instance and the IP address of the EAS running the microservice or function instance, i.e., the server IP address. After receiving the service binding information reporting message, the second CA-UPF can create a binding relationship between the service ID and the server IP address through its internal computing power awareness processing unit. Then, the MEC platform reports service capability information to the associated second CA-UPF. This service capability information includes the service ID, the service attributes, running status, computing resource information, and other computing service information of the microservice or function instance corresponding to the service ID, as well as site load information.

[0520] Thus, after the CA-UPF in the second domain receives service capability information from the edge computing node, it can send a third announcement message to the CA-UPF at the second boundary based on its corresponding intra-domain announcement neighbor list. This third announcement message includes the service capability information and, optionally, also includes the identification information of the CA-UPF in the second domain. The identification information of the CA-UPF in the second domain indicates that the service capability information originates from the edge computing node associated with the CA-UPF in the second domain.

[0521] Understandably, in a cross-domain computing power awareness network, the second boundary CA-UPF can serve as the entry CA-UPF in the second domain, and the CA-UPFs within the second domain can serve as the exit CA-UPFs within the second domain, with an intra-domain announcement forwarding relationship between them. Therefore, the intra-domain announcement neighbor list of the CA-UPFs within the second domain includes the identification information of the second boundary CA-UPF, and correspondingly, the intra-domain forwarding neighbor list of the second boundary CA-UPF includes the identification information of the CA-UPFs within the second domain.

[0522] Step S1702: The second boundary CA-UPF generates domain-level service capability information based on the service capability information. This domain-level service capability information is used to indicate the ability of the second domain to provide the first computing service to the outside world.

[0523] Step S1703: The second boundary CA-UPF sends a first announcement message to the first boundary CA-UPF, which includes the domain-level service capability information.

[0524] Correspondingly, the first boundary CA-UPF receives inter-domain announcement messages from the second boundary CA-UPF.

[0525] Optionally, the first announcement message may also include identification information for the second boundary CA-UPF.

[0526] In Embodiment 3 of this application, after the second boundary CA-UPF receives a third announcement message from the CA-UPF within the second domain, on the one hand, the second boundary CA-UPF can generate corresponding domain-level service capability information for the first computing service based on the service capability information related to the first computing service provided by the CA-UPF within the second domain. Then, through the first announcement message, it sends this domain-level service capability information and the identification information of the second boundary CA-UPF to the first boundary CA-UPF of the peer first domain. The domain-level service capability information includes computing service information of the first computing service corresponding to the second domain and / or load information of the second domain, used to indicate the second domain's ability to provide the first computing service externally. The identification information of the second boundary CA-UPF is used to indicate that the domain-level service capability information originates from the second boundary CA-UPF within the second domain (or from a regional computing power group within the second domain whose entry CA-UPF is the second boundary CA-UPF).

[0527] On the other hand, the second boundary CA-UPF can also generate or update the computing power routing information of the first computing service based on the service capability information related to the first computing service provided by the CA-UPF within the second domain, and record it in the database of the second boundary CA-UPF for subsequent routing of requests to access the first computing service. It should be noted that, from the perspective of the second boundary CA-UPF, the computing power routing information of the first computing service recorded by the second boundary CA-UPF indicates that the CA-UPF within the second domain exists as an exit CA-UPF that can provide the first computing service within the second domain.

[0528] More generally, after receiving a third announcement message from a CA-UPF within the second domain, the second boundary CA-UPF can generate or update an intra-domain computing power routing information database between itself and its corresponding egress CA-UPF within the second domain, based on the service capability information and the identification information of the CA-UPF within the second domain. The intra-domain computing power routing information database includes computing power routing information for one or more computing services. The computing power routing information for each computing service includes the service identifier of the computing service, the identification information of one or more egress CA-UPFs within the second domain capable of providing the computing service, the service attributes, operating status, computing resource information, and other computing service information corresponding to each egress CA-UPF, and the load information and network cost information of the edge computing nodes corresponding to each egress CA-UPF. The network cost information may include specific indicators such as latency, bandwidth, or jitter between the second boundary CA-UPF and the egress CA-UPF, or it may include comprehensive indicators determined based on specific indicators such as latency, bandwidth, and jitter.

[0529] Based on the intra-domain computing power routing information database, the second boundary CA-UPF can generate, modify, or delete intra-domain packet forwarding rules for certain service flows. At the same time, the second boundary CA-UPF can also construct domain-level service capability information for each computing service according to the generated intra-domain computing power routing information database, and then send the domain-level service capability information corresponding to each computing service and the identification information of the second boundary CA-UPF to the first boundary CA-UPF of the first domain at the other end through inter-domain announcement messages (such as the first announcement message).

[0530] It should be noted that domain-level service capability information refers to abstracting one or more edge computing nodes associated with the exit CA-UPF that forms a forwarding neighbor relationship with the second boundary CA-UPF within the second domain into a single computing station, indicating the ability of this computing station to provide a certain computing service. This domain-level service capability information can also be understood as the ability of the second domain as a whole to provide a certain computing service when the second boundary CA-UPF is used as the entry CA-UPF between domains.

[0531] Specifically, domain-level service capability information includes domain-level computing service information and / or domain-level load information. Taking the domain-level computing service information constructed for the first computing service as an example, this information includes the service identifier, service attributes, running status, and computing resource information of the first computing service deployed in the second domain, indicating what computing services the second domain as a whole supports. Domain-level load information refers to the load information of the second domain as a whole, indicating its overall load status. It should be noted that the running status and computing resource information in the domain-level computing service information can be evaluated based on the overall usage of the same computing service deployed on multiple related edge computing nodes within the second domain, and the evaluation method is not unique; this application does not specifically limit this method.

[0532] Step S1704: The first boundary CA-UPF sends a second announcement message to the CA-UPF within the first domain. The second announcement message includes the domain-level service capability information.

[0533] Accordingly, the first CA-UPF receives a second announcement message from the first boundary CA-UPF.

[0534] Optionally, the second announcement message may also include identification information for the first boundary CA-UPF.

[0535] In the third embodiment of this application, after the first boundary CA-UPF receives the first announcement message from the second boundary CA-UPF, on the one hand, the first boundary CA-UPF can announce the domain-level service capability information therein to each entry CA-UPF (e.g., CA-UPF within the first domain) corresponding to it in the first domain, and at the same time carry the identification information of the first boundary CA-UPF.

[0536] On the other hand, the first boundary CA-UPF can generate or update the computing power routing information of the first computing service based on the domain-level service capability information related to the first computing service provided by the second boundary CA-UPF, and record it in the database of the first boundary CA-UPF, so as to route subsequent requests for accessing the first computing service initiated in the first domain. It should be noted that, from the perspective of the first boundary CA-UPF, the second boundary CA-UPF exists as an exit CA-UPF that can provide the first computing service in the computing power routing information of the first computing service recorded by the first boundary CA-UPF.

[0537] More generally, after receiving a first announcement message from a second boundary CA-UPF, the first boundary CA-UPF can generate or update an inter-domain computing power routing information database between itself and the boundary CA-UPFs in its corresponding alliance domain, based on the domain-level service capability information and the identification information of the second boundary CA-UPF contained therein. The first boundary CA-UPF can generate, modify, or delete inter-domain packet forwarding rules for certain service flows based on this inter-domain computing power routing information database. The inter-domain computing power routing information database includes computing power routing information for one or more computing services. The computing power routing information for a computing service includes the service identifier of the computing service, the identification information of one or more peer alliance domain boundary CA-UPFs capable of providing the computing service, the domain-level service capability information and network cost information corresponding to each boundary CA-UPF for the computing service, etc., whereby the domain-level service capability information includes domain-level computing service information and / or domain-level load information.

[0538] Furthermore, the first boundary CA-UPF can send a second announcement message to the ingress CA-UPF (e.g., the CA-UPF within the first domain) within the first domain, based on its corresponding intra-domain announcement neighbor list. This second announcement message includes the domain-level service capability information and the identification information of the first boundary CA-UPF. Upon receiving this second announcement message, the CA-UPF within the first domain can generate or update its own intra-domain computing power routing information database based on the domain-level service capability information of the first boundary CA-UPF. Based on this database, it can then generate, modify, or delete intra-domain packet forwarding rules for certain service flows.

[0539] As can be seen from the above, unlike the existing computing power routing in single-domain computing power awareness networks, in cross-domain computing power awareness networks, the boundary CA-UPF of the alliance domain can aggregate the service capability information announced by the neighboring exit CA-UPF into domain-level service capability information, and announce the aggregated domain-level service capability information to the boundary CA-UPF of the local domain, thereby effectively avoiding the leakage of specific resource information within the operator's network.

[0540] Example 4

[0541] Embodiment 4 of this application provides a session management method for a cross-domain computing power awareness network. Specifically, this method is a method for cross-domain forwarding of user packets through the boundary CA-UPF in a cross-domain computing power awareness network.

[0542] Please refer to Figure 19 The above is a flowchart illustrating a session management method for a cross-domain computing power-aware network provided in Embodiment 4 of this application. The method includes:

[0543] Step S1901: The UE in the first domain establishes a PDU session connected to the DNN according to the 3GPP standard procedure. This session selects the CA-UPF within the first domain based on information such as the DNN, UE location, and UE route selection policy (URSP) rules issued by the policy control function (PCF), and associates the PDU session with the CA-VN virtual interface inside the CA-UPF within the first domain. The CA-UPF within the first domain is the entry CA-UPF in the first domain.

[0544] Step S1902: The UE application layer sends a service request message through the aforementioned PDU session. The source IP address of this service request message is the UE's IP address, and the destination IP address is the service identifier (Service ID). The service identifier is also an IP anycast address within a specific address range, and it corresponds one-to-one with a specific type of edge application, service, or function.

[0545] Step S1903: The CA-UPF in the first domain receives a service request message from the UE from the PDU session. If it is determined from the domain's computing power routing information database that the second domain can provide better service than the first domain, then a suitable boundary CA-UPF in the first domain is selected, such as the first boundary CA-UPF. The uplink and downlink message matching and forwarding rules of the service data flow corresponding to the service request message are determined, and the service request message is tunnel-encapsulated and sent to an external interface (such as the N19 interface) for forwarding to the first boundary CA-UPF.

[0546] Step S1904: The first boundary CA-UPF receives a service request message from the first intra-domain CA-UPF within the domain. Based on the inter-domain computing power routing information database, it selects the boundary CA-UPF in the second domain, such as the second boundary CA-UPF, and determines the uplink and downlink message matching and forwarding rules of the service data flow corresponding to the service request message. The service request message is then tunnel-encapsulated and sent to an external interface (such as the N19 interface) for forwarding to the selected second boundary CA-UPF.

[0547] Step S1905: The second boundary CA-UPF receives the service request message from the first boundary CA-UPF of the first domain. Based on the computing power routing information database within the domain, it selects the exit CA-UPF corresponding to the edge computing node that can provide the service, such as the CA-UPF within the second domain. It determines the uplink and downlink message matching and forwarding rules of the business data flow corresponding to the service request message, and encapsulates the service request message in a tunnel and sends it to an external interface (such as the N19 interface) for forwarding to the CA-UPF within the second domain.

[0548] Step S1906: The CA-UPF within the second domain receives a service request message from the CA-UPF at the second boundary, determines the uplink and downlink message matching and forwarding rules for the service data flow corresponding to the service request message, and sends the message to the interface where the computing service is located (such as the N6 interface). Optionally, the address translation unit inside the CA-UPF within the second domain first replaces the destination address of the message with the IP address of the server where the computing service is located, and then sends it to the edge application server through the N6 interface.

[0549] Step S1907: The edge application server completes the computing service and sends the service response message back to the CA-UPF in the second domain. The source IP address of the service response message is the server IP address, and the destination IP address is the UE IP address.

[0550] In step S1908, the CA-UPF within the second domain receives a service response message from the edge computing node. If the source IP address of the message is a server IP address, the internal address translation unit converts the source IP address of the service response message into a service identifier based on the cached mapping relationship between the service ID and the server IP address. Then, according to the previously determined message matching and forwarding rules, the service response message is routed back through the second boundary CA-UPF, the first boundary CA-UPF, and the CA-UPF within the first domain, finally returning to the UE.

[0551] This application also provides a communication device, please refer to... Figure 20 This is a schematic diagram of a communication device provided in an embodiment of this application. The communication device 2000 includes a transceiver module 2010 and a processing module 2020. This communication device can be used to implement the functions of the first session management function network element, the second session management function network element, the first computing management function network element, the second computing management function network element, the first computing power sensing user plane function network element, or the second computing power sensing user plane function network element involved in any of the above method embodiments. For example, the communication device can be a network device or a chip included in a network device.

[0552] For example, when the communication device performs Figure 5In the method embodiment shown, when operating or taking steps corresponding to the first session management function network element, the transceiver module 2010 is configured to: receive a first request message from the second session management function network element of the second domain, the first request message being used to request the establishment of a first session between the first domain and the second domain of the cross-domain computing power awareness network; send a second request message to the first boundary computing power awareness user plane function network element of the first domain, the second request message being used to request the establishment of the first session, one end of the first session being connected to the first boundary computing power awareness user plane function network element of the first domain, and the other end being connected to the second boundary computing power awareness user plane function network element of the second domain; receive a second response message from the first boundary computing power awareness user plane function network element, the second response message being used to indicate that the first session has been established on the first boundary computing power awareness user plane function network element side; and send a first response message to the second session management function network element, the first response message being used to indicate that the first session has been established on the first domain side.

[0553] In one possible design, the first request message includes first inter-domain tunnel information, and the second request message includes first inter-domain tunnel information; the first inter-domain tunnel information is used to establish a tunnel for the first boundary computing power sensing user plane function network element to send messages to the second boundary computing power sensing user plane function network element.

[0554] In one possible design, the first request message includes the identification information of the second boundary computing power sensing user plane functional network element, and the second request message includes the identification information of the second boundary computing power sensing user plane functional network element.

[0555] In one possible design, the first response message includes second inter-domain tunnel information, which is used to establish a tunnel for the second boundary computing power-aware user plane function element to send messages to the first boundary computing power-aware user plane function element.

[0556] In one possible design, the processing module 2020 is used to generate second inter-domain tunnel information; or, the second response message includes the second inter-domain tunnel information.

[0557] In one possible design, the transceiver module 2010 is further configured to: receive a third request message from a first computing management function network element in the first domain, the third request message being used to request the establishment of a second session within the first domain of the cross-domain computing power awareness network; send a fourth request message to a first boundary computing power awareness user plane function network element, the fourth request message being used to request the second session; receive a fourth response message from the first boundary computing power awareness user plane function network element, the fourth response message being used to indicate that the second session has been established on the side of the first boundary computing power awareness user plane function network element; and send a third response message to the first computing management function network element, the third response message being used to indicate that the second session has been established.

[0558] When the communication device performs Figure 5 In the method embodiment shown, when performing operations or steps corresponding to the second session management function network element, the transceiver module 2010 is configured to: send a first request message to the first session management function network element of the first domain, the first request message being used to request the establishment of a first session between the first domain and the second domain in the cross-domain computing power awareness network; receive a first response message from the first session management function network element, the first response message being used to indicate that the first session has been established on the first domain side; send a fifth request message to the second boundary computing power awareness user plane function network element of the second domain, the fifth request message being used to request the establishment of the first session, one end of the first session being connected to the second boundary computing power awareness user plane function network element of the second domain, and the other end being connected to the first boundary computing power awareness user plane function network element of the first domain; and receive a fifth response message from the second boundary computing power awareness user plane function network element, the fifth response message being used to indicate that the first session has been established on the second boundary computing power awareness user plane function network element side.

[0559] In one possible design, the first request message includes first inter-domain tunnel information, which is used to establish a tunnel for the first boundary computing power-aware user plane function element to send messages to the second boundary computing power-aware user plane function element.

[0560] In one possible design, the processing module 2020 is used to generate first inter-domain tunnel information; or, the transceiver module 2010 is also used to receive first inter-domain tunnel information from the second boundary computing power sensing user plane functional network element.

[0561] In one possible design, the first request message includes the identification information of the second boundary computing power sensing user plane functional network element.

[0562] In one possible design, the first response message includes second inter-domain tunnel information, and the fifth request message includes second inter-domain tunnel information; the second inter-domain tunnel information is used to establish a tunnel for the second boundary computing power sensing user plane function network element to send messages to the first boundary computing power sensing user plane function network element.

[0563] In one possible design, the fifth request message includes the identification information of the first boundary computing power sensing user plane functional network element.

[0564] In one possible design, the transceiver module 2010 is further configured to: receive a sixth request message from a second computing management function network element in the second domain, the sixth request message being used to request the establishment of a first session; and send a sixth response message to the second computing management function network element, the sixth response message being used to indicate that the establishment of the first session is complete.

[0565] In one possible design, the sixth request message includes one or more of the following information: identification information of the first session management function network element, identification information of the first boundary computing power awareness user plane function network element, identification information of the second boundary computing power awareness user plane function network element, and identification information of the cross-domain computing power awareness network.

[0566] In one possible design, the transceiver module 2010 is further configured to: receive a seventh request message from a second computing management function network element in the second domain, the seventh request message being used to request the establishment of a third session within the second domain of the cross-domain computing power awareness network; send an eighth request message to a second boundary computing power awareness user plane function network element, the eighth request message being used to request the establishment of the third session; receive an eighth response message from a second boundary computing power awareness user plane function network element, the eighth response message being used to indicate that the third session has been established on the second boundary computing power awareness user plane function network element side; and send a seventh response message to the second computing management function network element, the seventh response message being used to indicate that the third session has been established.

[0567] When the communication device performs Figure 5 In the method embodiment shown, when corresponding to the operation or step of the first computing management function network element, the transceiver module 2010 is used to: send a ninth request message to the second computing management function network element of the second domain, the ninth request message being used to request the creation of a cross-domain computing power awareness network, the cross-domain computing power awareness network including the first domain and the second domain; and receive a ninth response message from the second computing management function network element, the ninth response message being used to indicate that the cross-domain computing power awareness network has been created on the second domain side.

[0568] In one possible design, the ninth request message includes one or more of the following information: identification information of the first session management function network element of the first domain, identification information of the first boundary computing power awareness user plane function network element of the first domain, and identification information of the cross-domain computing power awareness network.

[0569] In one possible design, the transceiver module 2010 is further configured to: send a third request message to a first session management function network element in the first domain, the third request message being used to request the establishment of a second session of the cross-domain computing power awareness network within the first domain; and receive a third response message from the first session management function network element, the third response message being used to indicate that the establishment of the second session is complete.

[0570] When the communication device performs Figure 5In the method embodiment shown, when performing operations or steps corresponding to the second computing management function network element, the transceiver module 2010 is configured to: receive a ninth request message from the first computing management function network element of the first domain, the ninth request message being used to request the creation of a cross-domain computing power awareness network, the cross-domain computing power awareness network including the first domain and the second domain; send a sixth request message to the second session management function network element of the second domain, the sixth request message being used to request the establishment of a first session between the first domain and the second domain in the cross-domain computing power awareness network, one end of the first session being connected to the second boundary computing power awareness user plane function network element of the second domain, and the other end being connected to the first boundary computing power awareness user plane function network element of the first domain; receive a sixth response message from the second session management function network element, the sixth response message being used to indicate that the first session has been established; and send a ninth response message to the first computing management function network element, the ninth response message being used to indicate that the cross-domain computing power awareness network has been created on the second domain side.

[0571] In one possible design, the ninth request message includes one or more of the following information: identification information of the first session management function network element of the first domain, identification information of the first boundary computing power awareness user plane function network element of the first domain, and identification information of the cross-domain computing power awareness network.

[0572] In one possible design, the sixth request message includes one or more of the following information: identification information of the first session management function network element of the first domain, identification information of the first boundary computing power awareness user plane function network element of the first domain, identification information of the second boundary computing power awareness user plane function network element, and identification information of the cross-domain computing power awareness network.

[0573] In one possible design, the transceiver module 2010 is further configured to: send a seventh request message to the second session management function network element, the seventh request message being used to request the establishment of a third session of the cross-domain computing power awareness network within the second domain; and receive a seventh response message from the second session management function network element, the seventh response message being used to indicate that the establishment of the third session is complete.

[0574] When the communication device performs Figure 5In the method embodiment shown, when performing operations or steps corresponding to the first computing power sensing user plane function network element, the transceiver module 2010 is used to receive a second request message from the first session management function network element of the first domain. The second request message is used to request the establishment of a first session between the first domain and the second domain in the cross-domain computing power sensing network. One end of the first session is connected to the first boundary computing power sensing user plane function network element of the first domain, and the other end is connected to the second boundary computing power sensing user plane function network element of the second domain. The second request message includes inter-domain tunnel information. The processing module 2020 is used to establish a tunnel for sending messages from the first boundary computing power sensing user plane function network element to the second boundary computing power sensing user plane function network element according to the inter-domain tunnel information. The transceiver module 2010 is also used to send a second response message to the first session management function network element. The second response message is used to indicate that the first session has been established on the side of the first boundary computing power sensing user plane function network element.

[0575] In one possible design, the processing module 2020 is further configured to establish an inter-domain forwarding neighbor relationship with the second boundary computing power sensing user plane functional network element; the transceiver module 2010 is further configured to send a service request message to the second boundary computing power sensing user plane functional network element according to the inter-domain forwarding neighbor relationship.

[0576] In one possible design, the second request message includes the identification information of the second boundary computing power-aware user plane functional network element.

[0577] In one possible design, the processing module 2020 is further configured to generate second inter-domain tunnel information, which is used to establish a tunnel for the second boundary computing power sensing user plane function network element to send messages to the first boundary computing power sensing user plane function network element, and the second response message includes the second inter-domain tunnel information.

[0578] In one possible design, the transceiver module 2010 is further configured to: receive a fourth request message from the first session management function network element, the fourth request message being used to request the establishment of a second session in the first domain of the cross-domain computing power awareness network; and send a fourth response message to the first session management function network element, the fourth response message being used to indicate that the second session has been established on the side of the first boundary computing power awareness user plane function network element.

[0579] When the communication device performs Figure 5In the method embodiment shown, when performing operations or steps corresponding to the second computing power sensing user plane function network element, the transceiver module 2010 is used to receive a fifth request message from the second session management function network element of the second domain. The fifth request message is used to request the establishment of a first session between the first domain and the second domain in the cross-domain computing power sensing network. One end of the first session is connected to the second boundary computing power sensing user plane function network element of the second domain, and the other end is connected to the first boundary computing power sensing user plane function network element of the first domain. The fifth request message includes inter-domain tunnel information. The processing module 2020 is used to establish a tunnel for the second boundary computing power sensing user plane function network element to send messages to the first boundary computing power sensing user plane function network element according to the inter-domain tunnel information. The transceiver module 2010 is also used to send a fifth response message to the second session management function network element. The fifth response message is used to indicate that the first session has been established on the second boundary computing power sensing user plane function network element side.

[0580] In one possible design, the processing module 2020 is further configured to establish an inter-domain announcement neighbor relationship with the first boundary computing power sensing user plane function network element; the transceiver module 2010 is further configured to send the domain-level service capability information of the second domain to the first boundary computing power sensing user plane function network element according to the inter-domain announcement neighbor relationship.

[0581] In one possible design, the fifth request message includes the identification information of the first boundary computing power sensing user plane functional network element.

[0582] In one possible design, the processing module 2020 is further configured to generate first inter-domain tunnel information, which is used to establish a tunnel for the first boundary computing power sensing user plane function network element to send messages to the second boundary computing power sensing user plane function network element; the transceiver module 2010 is further configured to send the first inter-domain tunnel information to the second session management function network element.

[0583] In one possible design, the transceiver module 2010 is further configured to: receive an eighth request message from the second session management function network element, the eighth request message being used to request the establishment of a third session of the cross-domain computing power awareness network within the second domain; and send an eighth response message to the second session management function network element, the eighth response message being used to indicate that the third session has been established on the second boundary computing power awareness user plane function network element side.

[0584] When the communication device performs Figure 17In the method embodiment shown, when performing operations or steps corresponding to the first computing power sensing user plane function network element, the transceiver module 2010 is used to: receive a first announcement message from the second boundary computing power sensing user plane function network element of the second domain, the first announcement message including domain-level service capability information, the domain-level service capability information indicating the ability of the second domain to provide the first computing service to the outside world; and send a second announcement message to the computing power sensing user plane function network element within the first domain of the first domain, the second announcement message including domain-level service capability information.

[0585] In one possible design, the first announcement message includes the identification information of the second boundary computing power awareness user plane functional network element; the processing module 2020 is used to generate or update the computing power routing information of the first computing service in the first boundary computing power awareness user plane functional network element based on the domain-level service capability information and the identification information of the second boundary computing power awareness user plane functional network element.

[0586] In one possible design, the second announcement message includes the identification information of the first boundary computing power awareness user plane functional network element.

[0587] In one possible design, the domain-level service capability information includes: computing service information of the first computing service corresponding to the second domain and / or load information of the second domain.

[0588] In one possible design, the transceiver module 2010 is used to: receive a service request message from a computing power-aware user plane function network element within a first domain, the service request message being used to request a first computing service, the service request message including a service identifier of the first computing service; and send a service request message to a second boundary computing power-aware user plane function network element according to the computing power routing information of the first computing service.

[0589] When the communication device performs Figure 17 In the method embodiment shown, when performing operations or steps corresponding to the second computing power sensing user plane function network element, the transceiver module 2010 is used to receive a third announcement message from the computing power sensing user plane function network element within the second domain of the second domain. The third announcement message includes service capability information of the edge computing node associated with the computing power sensing user plane function network element within the second domain. The service capability information indicates the ability of the edge computing node to provide the first computing service externally. The processing module 2020 is used to generate domain-level service capability information based on the service capability information of the edge computing node. The domain-level service capability information indicates the ability of the second domain to provide the first computing service externally. The transceiver module 2010 is also used to send a first announcement message to the first boundary computing power sensing user plane function network element of the first domain. The first announcement message includes domain-level service capability information.

[0590] In one possible design, the third announcement message includes the identification information of the computing power-aware user plane functional network element in the second domain; the processing module 2020 is further configured to generate or update the computing power routing information of the first computing service in the second boundary computing power-aware user plane functional network element based on the service capability information of the edge computing node and the identification information of the computing power-aware user plane functional network element in the second domain.

[0591] In one possible design, the first announcement message includes the identification information of the second boundary computing power sensing user plane functional network element.

[0592] In one possible design, the service capability information of the edge computing node includes: computing service information of the first computing service corresponding to the edge computing node and / or load information of the edge computing node; the domain-level service capability information includes: computing service information of the first computing service corresponding to the second domain and / or load information of the second domain.

[0593] In one possible design, the transceiver module 2010 is configured to: receive a service request message from a first boundary computing power-aware user plane function network element, the service request message being used to request a first computing service, the service request message including a service identifier of the first computing service; and send a service request message to a computing power-aware user plane function network element in the second domain according to the computing power routing information of the first computing service.

[0594] The processing module 2020 in this communication device can be implemented by at least one processor or processor-related circuit components, and the transceiver module 2010 can be implemented by at least one transceiver or transceiver-related circuit components or a communication interface. The operation and / or function of each module in this communication device are respectively for the purpose of implementing… Figures 5 to 19 The corresponding flow of the method shown is omitted here for brevity. Optionally, the communication device may also include a storage module, which can be used to store data and / or instructions. The transceiver module 2010 and / or processing module 2020 can read the data and / or instructions from the storage module, thereby enabling the communication device to implement the corresponding method. This storage module can be implemented, for example, through at least one memory.

[0595] The aforementioned storage module, processing module, and transceiver module can exist separately, or all or some of the modules can be integrated, such as integrating the storage module and the processing module, or integrating the processing module and the transceiver module, etc.

[0596] Please refer to Figure 21This is another structural schematic diagram of a communication device provided in an embodiment of this application. This communication device can be used to implement the functions corresponding to the first session management function network element, the second session management function network element, the first computing management function network element, the second computing management function network element, the first computing power sensing user plane function network element, or the second computing power sensing user plane function network element in the above method embodiments. This communication device can be a network device or a device capable of supporting network devices in implementing the corresponding functions in the above method embodiments.

[0597] The communication device 2100 may include a processor 2101, a communication interface 2102, and a memory 2103. The communication interface 2102 is used to communicate with other devices via a transmission medium; this interface 2102 may be a transceiver or an interface circuit such as a transceiver circuit or transceiver chip. The memory 2103 is used to store program instructions and / or data, and the processor 2101 is used to execute the program instructions stored in the memory 2103, thereby implementing the method in the above-described method embodiments. Optionally, the memory 2103 and the processor 2101 are coupled. This coupling is an indirect coupling or communication connection between devices, units, or modules, and may be electrical, mechanical, or other forms, used for information exchange between devices, units, or modules.

[0598] In one embodiment, the communication interface 2102 may be specifically used to execute the actions of the transceiver module 2010, and the processor 2101 may be specifically used to execute the actions of the processing module 2020, which will not be described in detail here.

[0599] This application embodiment does not limit the specific connection medium between the communication interface 2102, processor 2101, and memory 2103. This application embodiment... Figure 21 The memory 2103, processor 2101, and communication interface 2102 are connected via a bus 2104. Figure 21 The connections between other components are shown in bold and are for illustrative purposes only, not as limiting information. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 21 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0600] This application also provides a chip system, including: a processor coupled to a memory, the memory being used to store programs or instructions, and when the program or instructions are executed by the processor, the chip system enables the chip system to implement the method of the corresponding terminal device or the method of the corresponding network device in any of the above method embodiments.

[0601] Optionally, the chip system may contain one or more processors. These processors can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory.

[0602] Optionally, the chip system may contain one or more memories. These memories may be integrated with the processor or separated from it; this application does not limit this. For example, the memory may be a non-transient processor, such as read-only memory (ROM), which may be integrated with the processor on the same chip or disposed on different chips. This application does not specifically limit the type of memory or the arrangement of the memory and processor.

[0603] For example, the chip system may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0604] It should be understood that each step in the above method embodiments can be completed by integrated logic circuits in the processor hardware or by instructions in software form. The method steps disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules in the processor.

[0605] This application also provides a computer-readable storage medium storing computer-readable instructions, which, when read and executed by a computer, cause the computer to perform the method in any of the above method embodiments.

[0606] This application also provides a computer program product that, when read and executed by a computer, causes the computer to perform the method in any of the above method embodiments.

[0607] This application also provides a communication system, which includes one or more of the following communication devices: a first session management function network element of a first domain, a first computing management function network element of a first domain, a first boundary computing power sensing user plane function network element of a first domain, a second session management function network element of a second domain, a second computing management function network element of a second domain, or a second boundary computing power sensing user plane function network element of a second domain.

[0608] The first session management function network element, the first computing management function network element, the first boundary computing power awareness user plane function network element, the second session management function network element, the second computing management function network element, and the second boundary computing power awareness user plane function network element can cooperate with each other to execute the method in any of the above method embodiments, create a cross-domain computing power awareness network, and realize session management in the cross-domain computing power awareness network.

[0609] Optionally, the communication system also includes a computing power-aware user plane function network element within the first domain of the first domain and a computing power-aware user plane function network element within the second domain of the second domain.

[0610] Optionally, the communication system further includes a terminal device and one or more edge computing nodes associated with the computing power sensing user plane function among the aforementioned first boundary computing power sensing user plane function network element, second boundary computing power sensing user plane function network element, first domain computing power sensing user plane function network element, and second domain computing power sensing user plane function network element.

[0611] This application embodiment also provides another communication system, which includes a first boundary computing power sensing user plane functional network element of a first domain and a second boundary computing power sensing user plane functional network element of a second domain. The first boundary computing power sensing user plane functional network element can cooperate with the second boundary computing power sensing user plane functional network element to execute the method in any of the above method embodiments to realize cross-domain information announcement and message forwarding in the cross-domain computing power sensing network.

[0612] Optionally, the communication system also includes a computing power-aware user plane function network element within the first domain of the first domain and a computing power-aware user plane function network element within the second domain of the second domain.

[0613] Optionally, the communication system further includes a terminal device and one or more edge computing nodes associated with the computing power sensing user plane function among the aforementioned first boundary computing power sensing user plane function network element, second boundary computing power sensing user plane function network element, first domain computing power sensing user plane function network element, and second domain computing power sensing user plane function network element.

[0614] It should be understood that the processor mentioned in the embodiments of this application can be a CPU, or other general-purpose processors, DSPs, ASICs, FPGAs, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0615] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DRRAM).

[0616] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) is integrated into the processor.

[0617] It should be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0618] It should be understood that the various numerical designations involved in the various embodiments of this application are merely for the convenience of description. The order of the numbers of the above processes or steps does not imply the order of execution. The execution order of each process or step should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this invention.

[0619] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0620] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0621] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0622] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0623] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0624] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0625] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

Claims

1. A method for session management of a cross-domain computing power-aware network, characterized in that, The method comprises: The first session management function network element in the first domain receives a first request message from a second session management function network element in a second domain, the first request message being used to request establishment of a first session between the first domain and the second domain in a cross-domain computing power-aware network; The first session management function network element sends a second request message to a first boundary computing power-aware user plane function network element in the first domain, the second request message being used to request establishment of the first session, one end of the first session being connected to the first boundary computing power-aware user plane function network element in the first domain and the other end being connected to a second boundary computing power-aware user plane function network element in the second domain; The first session management function network element receives a second response message from the first boundary computing power-aware user plane function network element, the second response message being used to indicate that the first session is established on the first boundary computing power-aware user plane function network element side; The first session management function network element sends a first response message to the second session management function network element, the first response message being used to indicate that the first session is established on the first domain side.

2. The method of claim 1, wherein, The first request message comprises first inter-domain tunnel information, and the second request message comprises the first inter-domain tunnel information; The first inter-domain tunnel information is used to establish a tunnel for the first boundary computing power-aware user plane function network element to send a packet to the second boundary computing power-aware user plane function network element.

3. The method according to claim 1 or 2, characterized in that, The first request message comprises identification information of the second boundary computing power-aware user plane function network element, and the second request message comprises the identification information of the second boundary computing power-aware user plane function network element.

4. The method according to claim 1 or 2, characterized in that, The first response message comprises second inter-domain tunnel information, and the second inter-domain tunnel information is used to establish a tunnel for the second boundary computing power-aware user plane function network element to send a packet to the first boundary computing power-aware user plane function network element.

5. The method of claim 4, wherein, The method further comprises: The first session management function network element generates the second inter-domain tunnel information; or The second response message comprises the second inter-domain tunnel information.

6. The method of claim 1 or 2, wherein, The method further comprises: The first session management function network element receives a third request message from a first computing management function network element in the first domain, the third request message being used to request establishment of a second session of the cross-domain computing power-aware network in the first domain; The first session management function network element sends a fourth request message to the first boundary computing power-aware user plane function network element, the fourth request message being used to request establishment of the second session; The first session management function network element receives a fourth response message from the first boundary computing power-aware user plane function network element, the fourth response message being used to indicate that the second session is established on the first boundary computing power-aware user plane function network element side; The first session management function network element sends a third response message to the first computing management function network element, the third response message being used to indicate that the second session is established. 7.A method for session management of a cross-domain computing power aware network, characterized in that, The method comprises: The second session management function network element of the second domain sends a first request message to the first session management function network element of the first domain, the first request message being used to request establishment of a first session between the first domain and the second domain in the cross-domain computing power aware network; The second session management function network element receives a first response message from the first session management function network element, the first response message being used to indicate that the first session is established on the first domain side; The second session management function network element sends a fifth request message to the second border computing power aware user plane function network element of the second domain, the fifth request message being used to request establishment of the first session, one end of the first session being connected to the second border computing power aware user plane function network element of the second domain, and the other end being connected to the first border computing power aware user plane function network element of the first domain; The second session management function network element receives a fifth response message from the second border computing power aware user plane function network element, the fifth response message being used to indicate that the first session is established on the second border computing power aware user plane function network element side.

8. The method of claim 7, wherein, The first request message comprises first inter-domain tunnel information, the first inter-domain tunnel information being used to establish a tunnel for the first border computing power aware user plane function network element to send a packet to the second border computing power aware user plane function network element.

9. The method of claim 8, wherein, The method further comprises: The second session management function network element generates the first inter-domain tunnel information; or The second session management function network element receives the first inter-domain tunnel information from the second border computing power aware user plane function network element.

10. The method according to any one of claims 7 to 9, characterized in that, The first request message comprises identification information of the second border computing power aware user plane function network element.

11. The method according to any one of claims 7 to 9, characterized in that, The first response message comprises second inter-domain tunnel information, and the fifth request message comprises the second inter-domain tunnel information; The second inter-domain tunnel information is used to establish a tunnel for the second border computing power aware user plane function network element to send a packet to the first border computing power aware user plane function network element.

12. The method according to any one of claims 7 to 9, characterized in that, The fifth request message comprises identification information of the first border computing power aware user plane function network element.

13. The method according to any one of claims 7 to 9, characterized in that, The method further comprises: The second session management function network element receives a sixth request message from a second computing management function network element of the second domain, the sixth request message being used to request establishment of the first session; The second session management function network element sends a sixth response message to the second computing management function network element, the sixth response message being used to indicate that the first session is established.

14. The method of claim 13, wherein, The sixth request message comprises one or more of the following information: identification information of the first session management function network element, identification information of the first border computing power aware user plane function network element, identification information of the second border computing power aware user plane function network element, and identification information of the cross-domain computing power aware network.

15. The method of any one of claims 7-9, wherein, The method further comprises: The second session management function network element receives a seventh request message from a second computing management function network element of the second domain, the seventh request message being used to request establishment of a third session of the cross-domain computing power aware network in the second domain; The second session management function network element sends an eighth request message to the second border AI UP network element, where the eighth request message is used to request to establish the third session; The second session management function network element receives an eighth response message from the second border AI UP network element, where the eighth response message is used to indicate that the third session is established on the second border AI UP network element side; The second session management function network element sends a seventh response message to the second CMF network element, where the seventh response message is used to indicate that the third session is established. 16.A method for session management of a cross-domain computing power aware network, characterized in that, The method comprises: A first CMF network element of a first domain sends a ninth request message to a second CMF network element of a second domain, where the ninth request message is used to request to create a cross-domain AI UP network, and the cross-domain AI UP network comprises the first domain and the second domain; and the ninth request message is used to establish a first session of the cross-domain AI UP network between the first domain and the second domain, one end of the first session is connected to a second border AI UP network element of the second domain, and the other end is connected to a first border AI UP network element of the first domain. The first CMF network element receives a ninth response message from the second CMF network element, where the ninth response message is used to indicate that the cross-domain AI UP network is created on the second domain side.

17. The method of claim 16, wherein, The ninth request message comprises one or more of the following information: Identity information of a first session management function network element of the first domain, identity information of a first border AI UP network element of the first domain, and identity information of the cross-domain AI UP network.

18. The method according to claim 16 or 17, characterized in that The method further comprises: The first CMF network element sends a third request message to a first session management function network element of the first domain, where the third request message is used to request to establish a second session of the cross-domain AI UP network in the first domain; The first CMF network element receives a third response message from the first session management function network element, where the third response message is used to indicate that the second session is established. 19.A method for session management of a cross-domain computing power aware network, the method comprising: The method comprises: A second CMF network element of a second domain receives a ninth request message from a first CMF network element of a first domain, where the ninth request message is used to request to create a cross-domain AI UP network, and the cross-domain AI UP network comprises the first domain and the second domain; The second CMF network element sends a sixth request message to a second session management function network element of the second domain, where the sixth request message is used to request to establish a first session of the cross-domain AI UP network between the first domain and the second domain, one end of the first session is connected to a second border AI UP network element of the second domain, and the other end is connected to a first border AI UP network element of the first domain; The second CMF network element receives a sixth response message from the second session management function network element, where the sixth response message is used to indicate that the first session is established. The second computing management function network element sends a ninth response message to the first computing management function network element, and the ninth response message is used to indicate that the cross-domain computing power perception network is created on the second domain side.

20. The method of claim 19, wherein, The sixth request message includes one or more of the following information: identifier information of a first session management function network element of the first domain, identifier information of a first boundary computing power perception user plane function network element of the first domain, identifier information of the second boundary computing power perception user plane function network element, and identifier information of the cross-domain computing power perception network.

21. The method according to claim 19 or 20, characterized in that, The method further includes: The second computing management function network element sends a seventh request message to the second session management function network element, and the seventh request message is used to request to establish a third session of the cross-domain computing power perception network in the second domain; The second computing management function network element receives a seventh response message from the second session management function network element, and the seventh response message is used to indicate that the third session is established. 22.A method for session management of a cross-domain computing power aware network, characterized in that, The method includes: A first boundary computing power perception user plane function network element of a first domain receives a second request message from a first session management function network element of the first domain, and the second request message is used to request to establish a first session between the first domain and a second domain in a cross-domain computing power perception network, one end of the first session is connected to the first boundary computing power perception user plane function network element of the first domain, and the other end is connected to a second boundary computing power perception user plane function network element of the second domain, and the second request message includes first inter-domain tunnel information; The first boundary computing power perception user plane function network element establishes a tunnel for sending a message from the first boundary computing power perception user plane function network element to the second boundary computing power perception user plane function network element according to the first inter-domain tunnel information; The first boundary computing power perception user plane function network element sends a second response message to the first session management function network element, and the second response message is used to indicate that the first session is established on the first boundary computing power perception user plane function network element side.

23. The method of claim 22, wherein, The method further includes: The first boundary computing power perception user plane function network element establishes an inter-domain forwarding neighbor relationship with the second boundary computing power perception user plane function network element, and the inter-domain forwarding neighbor relationship is used for the first boundary computing power perception user plane network element to send a service request message to the second boundary computing power perception user plane function network element.

24. The method of claim 22 or 23, wherein, The second request message includes identifier information of the second boundary computing power perception user plane function network element.

25. The method of claim 22 or 23, wherein, The method further includes: The first boundary computing power perception user plane function network element generates second inter-domain tunnel information, and the second inter-domain tunnel information is used to establish a tunnel for sending a message from the second boundary computing power perception user plane function network element to the first boundary computing power perception user plane function network element, and the second response message includes the second inter-domain tunnel information.

26. The method of claim 22 or 23, wherein, The method further includes: The first boundary computing power perception user plane function network element receives a fourth request message from the first session management function network element, and the fourth request message is used to request to establish a second session of the cross-domain computing power perception network in the first domain; The first boundary computing power-aware user plane function network element sends a fourth response message to the first session management function network element, and the fourth response message is used to indicate that the second session is established at the first boundary computing power-aware user plane function network element. 27.A method for session management of a cross-domain computing power aware network, characterized in that, The method comprises: The second boundary computing power-aware user plane function network element in the second domain receives a fifth request message from the second session management function network element in the second domain, the fifth request message is used to request to establish a first session between the first domain and the second domain in the cross-domain computing power-aware network, one end of the first session is connected to the second boundary computing power-aware user plane function network element in the second domain, and the other end is connected to the first boundary computing power-aware user plane function network element in the first domain; and the fifth request message comprises second inter-domain tunnel information. The second boundary computing power-aware user plane function network element establishes a tunnel for sending a message from the second boundary computing power-aware user plane function network element to the first boundary computing power-aware user plane function network element according to the second inter-domain tunnel information. The second boundary computing power-aware user plane function network element sends a fifth response message to the second session management function network element, and the fifth response message is used to indicate that the first session is established at the second boundary computing power-aware user plane function network element.

28. The method of claim 27, wherein, The method further comprises: The second boundary computing power-aware user plane function network element establishes an inter-domain announcement neighbor relationship between the second boundary computing power-aware user plane function network element and the first boundary computing power-aware user plane function network element, and the inter-domain announcement neighbor relationship is used for the second boundary computing power-aware user plane function network element to announce domain-level service capability information of the second domain to the first boundary computing power-aware user plane function network element.

29. The method of claim 27 or 28, wherein, The fifth request message comprises identification information of the first boundary computing power-aware user plane function network element.

30. The method of claim 27 or 28, wherein, The method further comprises: The second boundary computing power-aware user plane function network element generates first inter-domain tunnel information, and the first inter-domain tunnel information is used to establish a tunnel for sending a message from the first boundary computing power-aware user plane function network element to the second boundary computing power-aware user plane function network element; The second boundary computing power-aware user plane function network element sends the first inter-domain tunnel information to the second session management function network element.

31. The method of claim 27 or 28, wherein, The method further comprises: The second boundary computing power-aware user plane function network element receives an eighth request message from the second session management function network element, and the eighth request message is used to request to establish a third session of the cross-domain computing power-aware network in the second domain; The second boundary computing power-aware user plane function network element sends an eighth response message to the second session management function network element, and the eighth response message is used to indicate that the third session is established at the second boundary computing power-aware user plane function network element. 32.A method for session management of a cross-domain computing power aware network, characterized in that, The method comprises: The first boundary computing power-aware user plane function network element in the first domain receives a first announcement message from the second boundary computing power-aware user plane function network element in the second domain, the first announcement message comprises domain-level service capability information, and the domain-level service capability information indicates a capability of the second domain to provide a first computing service to the outside; The first border capability-aware user plane function network element sends a second announcement message to a first intra-domain capability-aware user plane function network element in the first domain, and the second announcement message comprises the domain-level service capability information.

33. The method of claim 32, wherein, The first announcement message comprises identification information of the second border capability-aware user plane function network element. The method further comprises: The first border capability-aware user plane function network element generates or updates the capability routing information of the first computing service in the first border capability-aware user plane function network element according to the domain-level service capability information and the identification information of the second border capability-aware user plane function network element.

34. The method of claim 32 or 33, wherein, The second announcement message comprises identification information of the first border capability-aware user plane function network element.

35. The method of claim 32 or 33, wherein, The domain-level service capability information comprises computing service information of the first computing service corresponding to the second domain and / or load information of the second domain.

36. The method of claim 32 or 33, wherein, The method further comprises: The first border capability-aware user plane function network element receives a service request packet from the first intra-domain capability-aware user plane function network element, and the service request packet is used to request the first computing service and comprises a service identifier of the first computing service; The first border capability-aware user plane function network element sends the service request packet to the second border capability-aware user plane function network element according to the capability routing information of the first computing service. 37.A method for session management of a cross-domain compute-aware network, the method comprising: The method comprises: A second border capability-aware user plane function network element in a second domain receives a third announcement message from a second intra-domain capability-aware user plane function network element in the second domain, and the third announcement message comprises service capability information of an edge computing node associated with the second intra-domain capability-aware user plane function network element, and the service capability information indicates the capability of the edge computing node to provide a first computing service externally; The second border capability-aware user plane function network element generates domain-level service capability information according to the service capability information of the edge computing node, and the domain-level service capability information indicates the capability of the second domain to provide the first computing service externally; The second border capability-aware user plane function network element sends a first announcement message to a first border capability-aware user plane function network element in a first domain, and the first announcement message comprises the domain-level service capability information.

38. The method of claim 37, wherein, The third announcement message comprises identification information of the second intra-domain capability-aware user plane function network element. The method further comprises: The second border capability-aware user plane function network element generates or updates the capability routing information of the first computing service in the second border capability-aware user plane function network element according to the service capability information of the edge computing node and the identification information of the second intra-domain capability-aware user plane function network element.

39. The method of claim 37 or 38, wherein, The first announcement message comprises identification information of the second border capability-aware user plane function network element.

40. The method of claim 37 or 38, wherein, The service capability information of the edge computing node comprises computing service information of the first computing service corresponding to the edge computing node and / or load information of the edge computing node. The domain-level service capability information includes: computing service information of the first computing service corresponding to the second domain and / or load information of the second domain.

41. The method of claim 37 or 38, wherein, The method further includes: The second border AIUP network element receives a service request message from the first border AIUP network element, the service request message being used to request the first computing service, and the service request message including a service identifier of the first computing service; The second border AIUP network element sends the service request message to the AIUP network element in the second domain according to the AI routing information of the first computing service.

42. A communications device, characterized by The apparatus includes at least one processor coupled with at least one memory: The at least one processor is configured to execute computer programs or instructions stored in the at least one memory to cause the apparatus to perform the method of any one of claims 1-41.

43. A communications device, characterized by The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41.

44. A computer-readable storage medium, characterized in that, The apparatus includes a processor and an interface circuit; 45. A computer program product, characterised in that, The interface circuit is configured to interact with the processor in code instructions or data; 46. A communication system, characterized by The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; 47. A communication system, characterized by The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured to perform the method of any one of claims 1-41. The apparatus includes a processor and an interface circuit; The interface circuit is configured to interact with the processor in code instructions or data; The processor is configured

Images