Communication methods and related devices

Abstract

This application provides a communication method and related apparatus, applicable to the field of communication technology. In the embodiments of this application, the first node registers its functional identification information and first information used to identify the first node with a first network element. This enables the first network element to promptly obtain information about nodes capable of supporting the execution of the business process during subsequent execution of specific business processes, and transmit this information to other network elements. Other network elements then select nodes capable of supporting the execution of the business process to execute the business process. This avoids the problem of frequent interaction between different network elements during session establishment, which would cause significant signaling overhead. Consequently, it improves the efficiency of session establishment, reduces the resource overhead of the session establishment process, and effectively utilizes network transmission resources.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to communication methods and related devices. Background Technology

[0002] In response to diverse and fully connected mobile service scenarios, the 5G network architecture has introduced technologies such as functional modularization, service-oriented interfaces, and separation of control and forwarding, driving the evolution of mobile network architecture towards flexibility and intelligence.

[0003] Due to limitations in air interface spectrum and network bandwidth, the total transmission resources of a network are finite. To efficiently and rationally guarantee the network's transmission capacity for different user service flows with these limited resources, wireless networks effectively utilize network transmission resources by providing control over each connection from the user to the network (including lifecycle control over connection establishment, resource allocation and adjustment, and release). Typically, the connection relationship from the user to the network is a complex system involving multiple aspects, such as PDU sessions, bearer services, access technologies, quality of service, security, and billing policies. These factors collectively determine the user's experience and capabilities within the network. Among these, PDU session services include multiple service processes. Taking the PDU session establishment process as an example, the current wireless network session establishment process is complex. During session establishment, different network elements need to interact frequently, resulting in significant signaling overhead; furthermore, the context information transmitted and maintained between different network elements is duplicated, causing information redundancy.

[0004] Therefore, improving the efficiency of session establishment and reducing the resource overhead of the session establishment process are urgent problems to be solved. Summary of the Invention

[0005] This application provides a communication method and related apparatus that can improve the efficiency of session establishment, reduce the resource overhead of the session establishment process, and effectively utilize network transmission resources.

[0006] In a first aspect, embodiments of this application provide a communication method. The method can be applied to a first network element, which may be, for example, a workflow repository function (WRF) network element or a module within a WRF network element (wherein the modules within the WRF network element include communication modules and computing modules), or a circuit or chip within a WRF network element responsible for communication functions (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip). Alternatively, the first network element may also be a logic module or software capable of implementing all or part of the functions of a communication device. The method includes: receiving registration information from a first node, wherein the registration information includes functional identification information of the first node and first information, the first information being used to identify the first node, and the functional identification information of the first node being used to indicate the first node's ability to support the execution of a first service process, wherein the first node provides the first service process to a terminal device.

[0007] In this application, the first node registers its functional identification information and first information used to identify the first node with the first network element. This enables the first network element to promptly obtain information about nodes that support the execution of business processes when executing specific business processes, and transmit this information to other network elements. Other network elements then select nodes that support the execution of business processes to execute the business processes. This avoids the problem of frequent interactions between different network elements during session establishment, which would cause significant signaling overhead. As a result, session establishment efficiency is improved, resource overhead during session establishment is reduced, and network transmission resources are effectively utilized.

[0008] In one possible implementation, after completing the first business process, the first node does not store the context information of the first business process.

[0009] In the above embodiments, the network entities involved currently require certain information (such as information used and / or generated by the previous business process) to execute the business process. This information can be stored locally or obtained from other network entities. After the business process is completed, new related information (such as information used and / or generated by the new business process) will be generated. This new related information can also be stored locally or stored on other network entities. In contrast, in this solution, the network entity executing the business process typically stores information locally while executing the business process, obtains the necessary information from other network entities before executing the business process, and stores the newly generated related information on other network entities after executing the business process, without storing this information itself. This application, through this design, can reduce information redundancy caused by repeated maintenance of context information, simplify business execution logic, and effectively save network transmission resources.

[0010] In another possible implementation, the method further includes: receiving a first request from a second network element, wherein the first request carries first service identifier information of the first service process, and the first request is used to query the node executing the first service process; and sending first response information to the second network element, wherein the first response information carries the first information.

[0011] In the above implementation, after the first node registers its functional identification information and the first information used to identify the first node to the first network element, the first network element stores the registration information of the first node. When other network elements (such as the second network element) request to query the information of nodes that support the execution of business processes (such as the first business process), the first network element can specifically query the nodes that support the execution of the first business process from the registration information and send the node information (such as the first information) to the second network element, thereby improving the efficiency of nodes in executing business processes.

[0012] In another possible implementation, the first business process is a Protocol Data Unit (PDU) session establishment process, and the functional identification information of the first node is used to indicate the first node's ability to perform the PDU session establishment process.

[0013] In the above implementation, the business process corresponds to the functional identification information of the first node. When the business process is a PDU session establishment process, the functional identification information of the first node is used to indicate the ability of the first node to support the execution of the PDU session establishment process. This design enables the node that can execute the PDU session establishment process to be quickly located when discovering and selecting nodes in the future, thereby improving the processing efficiency of the business process.

[0014] In another possible implementation, the first business process is a PDU session modification process, and the functional identification information of the first node is used to indicate the ability of the first node to perform the PDU session modification process.

[0015] In the above implementation, the business process corresponds to the functional identification information of the first node. When the business process is a PDU session modification process, the functional identification information of the first node is used to indicate the ability of the first node to execute the PDU session modification process. This design enables the node that can execute the PDU session modification process to be quickly located when discovering and selecting nodes in the future, thereby improving the processing efficiency of the business process.

[0016] Secondly, embodiments of this application provide a communication method. This method can be applied to a first network element, which may be, for example, a WRF network element or a module within a WRF network element (wherein the module within the WRF network element includes a communication module and a computing module), or a circuit or chip within the WRF network element responsible for communication functions (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core). Alternatively, the first network element may also be a logic module or software capable of implementing all or part of the functions of a communication device. The method includes: receiving a first request from a second network element, wherein the first request carries first service identification information of a first service process, and the first request is used to query the node executing the first service process; and sending first response information to the second network element, wherein the first response information carries first information, the first information being used to determine the first node, and the first node providing the first service process to the terminal device.

[0017] In this application, when other network elements (such as the second network element) request to query information about nodes that support the execution of a business process (such as the first business process), the first network element can specifically feed back information about nodes that support the execution of the first business process (such as first information) to the second network element. The second network element can determine the first node through the first information so that the first node can execute the first business process and improve processing efficiency.

[0018] Thirdly, embodiments of this application provide a communication method, which can be applied to a second network element. The second network element can be, for example, a core network portal function (CPF) network element or a module within a CPF network element (wherein the modules within the CPF network element include communication modules and computing modules), or a circuit or chip within a CPF network element responsible for communication functions (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core). Alternatively, the second network element can also be a logic module or software capable of implementing all or part of the functions of a communication device. The method includes: receiving a second request from a terminal device, the second request being used to request the execution of a first service process; obtaining first information, wherein the first information is used to determine a first node, the first node providing the first service process to the terminal device; and sending a first service process execution request to the first node according to the second request and the first information.

[0019] In this application, when a terminal device requests the execution of a first service process, after the second network element obtains information about the node that supports the execution of the first service process, the first network element can specifically feed back the information about the node that supports the execution of the first service process (e.g., first information) to the second network element. In this way, the second network element can determine the first node through the first information, thereby enabling the second network element to request the first node to execute the first service process according to the second request and the first information, thus improving processing efficiency.

[0020] In one possible implementation, the first business process includes a PDU session establishment process or a PDU session modification process.

[0021] In another possible implementation, obtaining the first information includes: sending a first request to a first network element, wherein the first request carries first service identifier information of the first service process, and the first request is used to query the node executing the first service process; and receiving first response information from the first network element, wherein the first response information carries the first information.

[0022] In the above embodiments, a possible way to obtain the first information is provided, so that the second network element can determine the first node through the first information, thereby requesting the first node to execute the first business process and improving the processing efficiency of the business process.

[0023] In yet another possible implementation, the first business process execution request carries information about the business process that characterized the previous step of the current business process.

[0024] Alternatively, the first business process execution request carries information representing the most recently executed business process prior to the current business process.

[0025] In the above implementation, the relevant parameters of the business process executed in the previous step (such as the information used and / or generated by the business process executed in the previous step) can be determined by carrying the information of the business process executed in the first business process execution request to characterize the current business process, thereby ensuring the feasibility of executing the current business process.

[0026] Fourthly, embodiments of this application provide a communication method, which can be applied to a third network element. The third network element can be, for example, a data management function (DMF) network element or a module within a DMF network element (wherein the modules within the DMF network element include communication modules and computing modules), or a circuit or chip within a DMF network element responsible for communication functions (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core). Alternatively, the third network element can also be a logic module or software capable of implementing all or part of the functions of a communication device. The method includes: receiving a third request from a first node, wherein the third request carries context information of a first service process, and the third request is used to request storage of the context information of the first service process.

[0027] In this application, after the first node completes the execution of the current business process, it can request the third network element to store the information used and / or generated by the current business process, so that subsequent nodes can pass context information through the third network element when executing the business process, ensuring the feasibility of the node executing the business process.

[0028] In one possible implementation, the method further includes: receiving a sixth request from a second node, wherein the sixth request is for querying context information of the first node; and sending the context information of the first business process to the second node.

[0029] In the above implementation, during the execution of the current business process, the second node can request information on the use and / or generation of the previous business process from the third network element. This solution supplements the function of transmitting context information between nodes through the third network element, ensuring the feasibility of the node executing the business process.

[0030] In another possible implementation, the third request also carries second business identification information of the first business process, which is used to query the context information of the first business process.

[0031] In the above implementation, subsequent nodes can query relevant indicators of the first business process (such as session and service continuity (SSC), single network slice selection assistance information (S-NSSAI), etc.) through the second business identification information of the first business process carried by the third request (such as the second business identification information of the first business process being a PDU session ID). This allows them to quickly query the context information of the first business process and improve processing efficiency.

[0032] In another possible implementation, the third request also carries second business identification information of the first business process and functional identification information of the first node. The functional identification information of the first node is used to indicate the ability of the first node to support the execution of the first business process. The second business identification information of the first business process and the functional identification information of the first node are used to query the context information of the first business process.

[0033] In the above implementation, subsequent nodes can query the relevant indicators (such as SSC, S-NSSAI, etc.) of the first business process through the second business identification information of the first business process carried by the third request (for example, when the first business process is a PDU session establishment process, the second business identification information of the first business process is PDU session ID) and the function identification information of the first node (for example, function ID = PDU session establishment). This allows them to quickly query the context information of the first business process and improve processing efficiency.

[0034] In another possible implementation, the method further includes: receiving a seventh request from the second node, wherein the seventh request carries context information of a second business process, the seventh request being used to request storage of the context information of the second business process, the second business process including a Protocol Data Unit (PDU) session establishment process or a PDU session modification process.

[0035] In the above implementation, after the second node completes the current business process, it can request the third network element to store the information used and / or generated by the current business process, so that subsequent nodes can pass context information through the third network element when executing the business process, ensuring the feasibility of the node executing the business process.

[0036] Fifthly, embodiments of this application provide a communication method. This method can be applied to a first node, which may be, for example, a workflow or a module within the workflow (wherein the modules in the workflow include communication modules and computing modules), or a circuit or chip in the workflow responsible for communication functions (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core). Alternatively, the first node may also be a logic module or software capable of implementing all or part of the functions of a communication device. The method includes: receiving a first service process execution request; and sending a third request to a third network element, wherein the third request carries context information of the first service process, and the third request is used to request the storage of the context information of the first service process.

[0037] In this application, after the first node completes the current business process, it can request the third network element to store the information used and / or generated by the current business process, so that subsequent nodes can directly obtain the information used and / or generated by the previous business process through the third network element when executing the business process, thereby improving the processing efficiency of the business process.

[0038] In one possible implementation, after completing the first business process, the first node does not store the context information of the first business process.

[0039] In the above embodiments, the network entities involved currently require certain information (such as information used and / or generated by the previous business process) to execute the business process. This information can be stored locally or obtained from other network entities. After the business process is completed, new related information (such as information used and / or generated by new business processes) is generated. This new related information can also be stored locally or on other network entities. In contrast, in this solution, the network entity executing the business process typically stores information locally while executing the business process, obtains the necessary information from other network entities before executing the business process, and stores the newly generated related information on other network entities after executing the business process, without storing this information itself. This design reduces information redundancy caused by repeated maintenance of context information, simplifies business execution logic, and effectively saves network transmission resources.

[0040] In another possible implementation, the first business process includes a Protocol Data Unit (PDU) session establishment process or a PDU session modification process.

[0041] In another possible implementation, the method further includes: sending registration information to a first network element, wherein the registration information includes functional identification information of the first node and first information, the first information being used to identify the first node, the functional identification information of the first node being used to indicate the ability of the first node to support the execution of a first business process, and the first node providing the first business process to a terminal device.

[0042] In the above implementation, the first node registers its functional identification information and first information for identifying the first node with the first network element in advance. This enables the first network element to obtain information about nodes that support the execution of business processes in a timely manner when executing specific business processes, and transmits this information to other network elements. Other network elements then select nodes that support the execution of business processes to execute the business processes. This avoids the problem of frequent interaction between different network elements during session establishment, which would cause significant signaling overhead. As a result, session establishment efficiency is improved and resource overhead during session establishment is reduced.

[0043] In another possible implementation, the third request also carries second business identification information of the first business process, which is used to query the context information of the first business process.

[0044] In the above implementation, subsequent nodes can query relevant indicators of the first business process (such as SSC, S-NSSAI, etc.) through the second business identification information of the first business process carried by the third request (such as the second business identification information of the first business process being the PDU session ID), thereby quickly querying the context information of the first business process and improving processing efficiency.

[0045] In another possible implementation, the third request also carries second business identification information of the first business process and functional identification information of the first node. The functional identification information of the first node is used to indicate the ability of the first node to support the execution of the first business process. The second business identification information of the first business process and the functional identification information of the first node are used to query the context information of the first business process.

[0046] In the above implementation, subsequent nodes can query the relevant indicators (such as SSC, S-NSSAI, etc.) of the first business process through the second business identification information of the first business process carried by the third request (for example, when the first business process is PDU session establishment, the second business identification information of the first business process is PDU session ID) and the function identification information of the first node (for example, function ID = PDU sessionestablishment). This allows them to quickly query the context information of the first business process and improve processing efficiency.

[0047] In another possible implementation, the method further includes: sending a fourth request to a fourth network element, wherein the fourth request carries the identification information of the terminal device, and the fourth request is used to request access and mobility management subscription data corresponding to the terminal device. Receiving the access and mobility management subscription data corresponding to the terminal device from the fourth network element. Obtaining supplemented session management context information based on the non-access stratum (NAS) information and the access and mobility management subscription data corresponding to the terminal device.

[0048] In the above embodiments, a scheme is provided to standardize the interface parameter configuration of each service within the first node and the process of outputting the information required to implement the first business process. For example, for the first node in this scheme to execute the smallest granularity service (also known as an atomic capability, such as the supplementary atomic capability of session management context information) that an entity in the core network can provide to implement the first business process, the scheme for standardizing the process of outputting the information required to implement the first business process can be as follows: the input information is NAS message and the access and mobility management subscription data (UE subscription data) corresponding to the terminal device, and the output information is the supplemented session management context information (SM context). This enables the first node and the fourth network element to achieve cross-vendor combination, increasing the flexibility of orchestration and internal implementation.

[0049] In another possible implementation, the method further includes: sending a fifth request to a fourth network element, wherein the fifth request carries the identification information of the terminal device, and the fifth request is used to request session management subscription data corresponding to the terminal device. The method also includes receiving the session management subscription data corresponding to the terminal device from the fourth network element. Finally, based on the supplemented session management context information and the session management subscription data corresponding to the terminal device, a PDU session is determined to be established.

[0050] In the above embodiments, a scheme is provided to standardize the interface parameter configuration of each service within the first node and the process of outputting the information required to implement the first business process. For example, for the first node in this scheme to implement the smallest granularity service (also known as an atomic capability, such as the atomic capability to determine whether to establish a PDU session) that an entity in the core network can provide to implement the first business process, the scheme for standardizing the process of outputting the information required to implement the first business process can be as follows: the input information is session management context information (SM context) and session management subscription data (SM Subscription Data), and the output information is result indication information and session management context information (SM context). This enables the first node and the fourth network element to achieve cross-vendor combination, increasing the flexibility of orchestration and internal implementation.

[0051] Sixthly, embodiments of this application provide a communication method. This method can be applied to a first node, which may be, for example, a workflow or a module within a workflow (wherein the modules in the workflow include communication modules and computing modules), or a circuit or chip in the workflow responsible for communication functions (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core). Alternatively, the first node may also be a logic module or software capable of implementing all or part of the functions of a communication device. The method includes: sending registration information to a first network element, wherein the registration information includes functional identification information of the first node and first information, the first information being used to identify the first node, the functional identification information of the first node being used to indicate the first node's ability to support the execution of a first service process, and the first node providing the first service process to a terminal device.

[0052] In this application, the first node registers its functional identification information and first information for identifying the first node with the first network element in advance. This enables the first network element to obtain information about nodes that support the execution of business processes in a timely manner when executing specific business processes, and transmit this information to other network elements. Other network elements then select nodes that support the execution of business processes to execute the business processes. This avoids the problem of frequent interaction between different network elements during session establishment, which would cause significant signaling overhead. As a result, session establishment efficiency is improved and resource overhead during session establishment is reduced.

[0053] In a seventh aspect, embodiments of this application provide a communication device that can be used for a first network element in the first or second aspect. The first network element can be a WRF network element, a device in the WRF network element (e.g., a chip, a chip system, or a circuit), or a device that can be matched with the WRF network element. It can also be a logic module or software that can implement all or part of the functions of the WRF network element.

[0054] In one possible implementation, the communication device may include modules or units that perform the methods / operations / steps / actions described in the first or second aspect. These modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0055] Eighthly, embodiments of this application provide a communication device that can be used for a second network element in the third aspect. The second network element can be a CPF network element, a device (e.g., a chip, a chip system, or a circuit) within a CPF network element, or a device that can be matched with a CPF network element, or a logic module or software that can implement all or part of the functions of a CPF network element.

[0056] In one possible implementation, the communication device may include modules or units that perform the methods / operations / steps / actions described in the third aspect one by one. These modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0057] Ninthly, embodiments of this application provide a communication device that can be used for a third network element in the fourth aspect. The third network element can be a DMF network element, a device (e.g., a chip, a chip system, or a circuit) within a DMF network element, or a device that can be matched with a DMF network element, or a logic module or software that can implement all or part of the functions of a DMF network element.

[0058] In one possible implementation, the communication device may include modules or units that perform the methods / operations / steps / actions described in the third aspect one by one. These modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0059] In a tenth aspect, embodiments of this application provide a communication device that can be used as a first node in the fifth or sixth aspect. The first node can be a workflow, a device in the workflow (e.g., a chip, a chip system, or a circuit), a device that can be matched with the workflow, or a logic module or software that can implement all or part of the workflow functions.

[0060] In one possible implementation, the communication device may include modules or units that perform the methods / operations / steps / actions described in the fifth or sixth aspect, and these modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0061] Eleventhly, embodiments of this application provide a communication device, which includes at least one processor and a communication interface; the communication interface is used for inputting and / or outputting information, and the at least one processor is used to call a computer program stored in at least one memory to implement the method described in any one of the first to sixth aspects.

[0062] In one possible implementation of the eleventh aspect, the communication device further includes at least one of the aforementioned memories. Optionally, the memory and processor are integrated together.

[0063] In a twelfth aspect, embodiments of this application provide a communication device including a logic circuit and an interface, the logic circuit and the interface being coupled; the interface is used for inputting and / or outputting information, and the logic circuit is used for implementing the method described in any of the embodiments of the first to sixth aspects.

[0064] In one possible implementation of the twelfth aspect, the communication device is a chip or chip system.

[0065] In a thirteenth aspect, embodiments of this application provide a communication system comprising a first network element, a second network element, a third network element, and a first node, wherein the first network element, the second network element, the third network element, and the first node are communicatively connected. The first network element is used to implement the method of any embodiment of the first or second aspect; the second network element is used to implement the method of any embodiment of the third aspect; the third network element is used to implement the method of any embodiment of the fourth aspect; and the first node is used to implement the method of any embodiment of the fifth or sixth aspect.

[0066] In a fourteenth aspect, embodiments of this application provide a computer-readable storage medium for storing instructions or computer programs; when the instructions or computer programs are executed, they implement the method of any one of the embodiments of the first to sixth aspects.

[0067] In a fifteenth aspect, this application provides a computer program product including computer instructions that, when executed on at least one processor, can implement the methods described in any of the first to sixth aspects or any possible implementation thereof. Exemplarily, the computer program product can be a software installation package, which can be downloaded and executed on a computing device when the aforementioned methods are required.

[0068] The beneficial effects of the technical solutions provided in aspects seven to fifteen of this application can be referred to the beneficial effects of the technical solutions in aspects one to six, and will not be repeated here. Attached Figure Description

[0069] The accompanying drawings used in the description of the embodiments will be briefly introduced below.

[0070] Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0071] Figure 2 This is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0072] Figure 3 This is a schematic diagram of a fifth-generation mobile communication technology network architecture provided in an embodiment of this application;

[0073] Figure 4 This is a flowchart illustrating a communication method provided in an embodiment of this application;

[0074] Figure 5A This is a flowchart illustrating the process of registering node information and obtaining context information for the PDU session establishment process, as provided in an embodiment of this application.

[0075] Figure 5B This is a flowchart illustrating the process of registering node information and obtaining context information for the PDU session modification process, as provided in an embodiment of this application.

[0076] Figure 6 This is a schematic diagram of the structure of a communication device 60 provided in an embodiment of this application;

[0077] Figure 7 This is a schematic diagram of the structure of another communication device 70 provided in the embodiments of this application. Detailed Implementation

[0078] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0079] The system architecture used in the embodiments of this application is described below. It should be noted that the system architecture and business scenarios described in this application are for the purpose of more clearly illustrating the technical solutions of this application, and do not constitute a limitation on the technical solutions provided in this application. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in this application are also applicable to similar technical problems.

[0080] Please see Figure 1 , Figure 1This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. The communication system includes a core network device 101. Optionally, the communication system may also include a terminal device 102 and an access network device 103.

[0081] Core network equipment 101 refers to equipment in the core network (CN) that provides service support for terminal equipment 102. In this embodiment, the core network equipment 101 includes a first network element 1001, a second network element 1002, and a first node 1003. Optionally, core network equipment 101 further includes a third network element 1004 and a fourth network element 1005. Figure 1 (Shown by dashed boxes in the diagram). Optionally, the third network element 1004 may be deployed together with the fourth network element 1005 on other equipment, or they may be deployed separately as independent devices; this application does not limit this. For ease of description, the following explanation will use the example of the third network element 1004 and the fourth network element 1005 not being deployed together.

[0082] For example, the first network element 1001 can be a workflow repository function (WRF) network element, the second network element 1002 can be a core network portal function (CPF) network element, and the first node 1003 can also be called a workflow, which is an entity that provides fixed functions for a certain business process. The first node 1003 contains multiple network entity services (e.g., represented as services) that provide one or more atomic capabilities. Multiple services with different functions jointly provide a certain business process (e.g., PDU session establishment process, PDU session modification process, etc.). Here, atomic capability refers to the smallest granularity of service that an entity in the core network can provide. For example, the services provided by each network element in the protocol data unit session (PDU session) establishment process include: supplementary session management (SM) context information, PDU session establishment confirmation, and other atomic capabilities. The third network element 1004 can be a data management function (DMF) network element, and the fourth network element 1005 can be a unified data management (UDM) network element, etc., which will not be listed here. Specifically, the WRF network element can be used to receive the registration information of the first node 1003 and to assist the CPF network element in discovering and selecting suitable nodes that can provide services; the CPF network element can be used to manage access and mobility in the mobile network, such as user registration management, connection management, reachability management, terminal device location update, terminal device registration network, terminal device handover, and node discovery and selection, etc. Specific functions can include non-access stratum signaling termination, registration area management, access authentication, etc. The DMF network element can be used to store and manage the context information of the service process. It should be noted that in this application, network elements can also be referred to as entities or functional entities. For example, a WRF network element can be referred to as a WRF entity or a WRF functional entity, etc.

[0083] In this embodiment, the terminal device 102 may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities. The terminal device 102 may also be referred to as user equipment (UE), mobile station (MS), mobile terminal (MT), etc., or a device used to provide voice or data connectivity to users, or an Internet of Things (IoT) device. For example, terminal devices include handheld devices and vehicle-mounted devices with wireless connectivity. Currently, terminal device 102 can be: mobile phone, tablet computer, laptop computer, handheld computer, mobile internet device (MID), wearable device (such as smartwatch, smart bracelet, pedometer, smart glasses, etc.), vehicle-mounted device (such as car, bicycle, electric vehicle, airplane, ship, train, high-speed rail, etc.), satellite terminal, virtual reality (VR) device, augmented reality (AR) device, smart point of sale (POS) machine, customer-premises equipment (CPE), light user equipment (light UE), reduced capability user equipment (REDCAP UE), wireless terminal in industrial control, smart home device (such as refrigerator, television, air conditioner, electricity meter, etc.), smart robot, robotic arm, workshop equipment, wireless terminal in autonomous driving, wireless terminal in telemedicine, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, or wireless terminal in smart home, flying equipment (such as smart robot, hot air balloon, drone, airplane), etc. Terminal device 102 can also be a vehicle device, such as a vehicle device, vehicle module, vehicle chip, on-board unit (OBU) or telematics box (T-BOX), etc. Terminal device 102 can also be other devices with terminal functions. For example, terminal device can also be a device that plays the role of terminal in D2D communication.

[0084] In this embodiment, the access network device 103 is a node in a radio access network (RAN), and may also be referred to as an RAN node (or device). The access network device 103 assists the terminal device 102 in achieving wireless access. Figure 2As shown, the multiple access network devices 210 in the communication system 2000 can be nodes of the same type or nodes of different types. In some scenarios, the roles of the access network devices 210 and the terminal devices 220 are relative, for example, Figure 2 Network element 220i can be a helicopter or a drone, and it can be configured as a mobile base station. For terminal devices 220j that access RAN 200 through network element 220i, network element 220i is a base station; however, for base station 210a, network element 220i is a terminal device. Access network device 210 and terminal device 220 are sometimes referred to as communication devices, for example... Figure 2 Network elements 210a and 210b can be understood as communication devices with base station functions, while network elements 220a-220j can be understood as communication devices with terminal functions.

[0085] In one possible scenario, access network equipment can be a base station, an evolved NodeB (eNodeB), a transmitting and receiving point (TRP), a transmitting point (TP), a next-generation NodeB (gNB), a base station in a future mobile communication system, a satellite, or an access point (AP) in a Wi-Fi system, an integrated access and backhaul (IAB) node, or access network equipment in a mobile switching center non-terrestrial network (NTN) communication system. This means it can be deployed on high-altitude platforms or satellites. Access network equipment can also be a macro base station (such as...). Figure 2 210a), micro base stations or indoor stations (such as Figure 2 Access network equipment can be 210b), relay nodes or donor nodes, or wireless controllers in cloud radio access network (CRAN) scenarios. Access network equipment can also function as base stations in device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, drone communication, and machine-to-machine (M2M) communication. Optionally, access network equipment can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, in vehicle-to-everything (V2X) technology, the access network equipment can be a roadside unit (RSU).

[0086] In another possible scenario, multiple access network devices collaborate to assist terminals in achieving wireless access, with each device performing a portion of the base station's functions. For example, access network devices can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs). CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio equipment or radio units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs). It is understood that access network devices can be CU nodes, DU nodes, or devices comprising both CU and DU nodes. Furthermore, CUs can be classified as access network devices within the RAN (RAN) or the CN (CN), without limitation.

[0087] To address the challenges of diverse, fully connected mobile service scenarios and maintain the leading edge of 3GPP networks, the fifth-generation (5G) mobile communication technology network architecture has emerged. (See also...) Figure 3 , Figure 3 This is a schematic diagram of a fifth-generation mobile communication technology network architecture provided in an embodiment of this application, as shown below. Figure 3As shown, this 5G network architecture not only supports 3GPP radio technologies (such as Long Term Evolution (LTE) and 5G Radio Access Network (5G RAN)) to access the core network (CN), but also supports non-3GPP access technologies to access the core network through non-3GPP interworking functions (N3IWF) or next-generation packet data gateways (ngPDG). This 5G network architecture includes UE, (R)AN, data network (DN), and CN. The CN includes PCF network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, and user plane function (UPF) network elements, which are connected through various interfaces.

[0088] Among them, the 5G network architecture introduces a large number of new technical features, such as functional modularization, service-oriented interfaces, and separation of control and forwarding, driving the evolution of mobile network architecture towards flexibility and intelligence.

[0089] Specifically, the technical feature of functional modularization is mainly to achieve network architecture flexibility, allowing for on-demand customization according to different needs. By decoupling complex network functions and breaking them down into multiple independent modules, each module can have simplified or complex implementations. Ideally, they can be assembled like "building blocks" according to actual requirements. The modular approach is easy to understand; the challenge lies in the fact that different functions in mobile communication networks are often coupled together. Furthermore, the granularity of decoupling affects both flexibility and assembly complexity, requiring a balance between different decoupling schemes.

[0090] Due to limitations in air interface spectrum and network bandwidth, the total transmission resources of a network are finite. To efficiently and rationally guarantee the network's transmission capacity for different user service flows with these limited resources, the wireless network needs to provide control over each connection from the user to the network (including control over the connection establishment, resource allocation and adjustment, and release throughout its lifecycle), thereby effectively utilizing network transmission resources. Generally, the connection relationship between the user and the network is a complex system involving multiple aspects, such as PDU sessions, bearer services, access technologies, quality of service, security, and charging policies. These factors collectively determine the user's experience and capabilities within the network. Among these, a PDU session includes multiple service processes. Taking the PDU session establishment process as an example, in a 5G network, this user-to-network connection relationship can be termed a PDU session (protocol data unit session). A PDU session is an abstract concept representing the logical connection between the UE and the DN via the AN, user plane function (UPF) network elements. The 5G network assigns an independent session identifier to each PDU session and manages its establishment and release processes.

[0091] In some solutions, wireless networks effectively utilize network transmission resources by providing relevant service processes for PDU sessions. However, in reality, the PDU session establishment process involves numerous and dispersed states with complex logic, leading to frequent interactions between network elements. Furthermore, the context information transmitted and maintained between different network elements (such as data network name (DNN), single network slice selection assistance information (S-NSSAI), and PDU session ID) is duplicated, resulting in information redundancy. Existing network architectures aggregate multiple atomic capabilities among network elements, and there are strong dependencies between them. Service deployment requires the cooperation and upgrading of multiple network elements, which continuously increases the complexity of process interactions, and the deployment and upgrade cycle of new features is long.

[0092] In view of this, embodiments of this application provide a communication method and related apparatus. On one hand, a first node registers its functional identification information and first information used to determine the first node with a first network element. This enables the first network element to promptly obtain information about nodes capable of supporting the execution of business processes during subsequent execution of specific business processes, and transmit this information to other network elements. Other network elements then select nodes capable of supporting the execution of business processes to execute the business processes. This avoids the problem of frequent interactions between different network elements during session establishment, which would cause significant signaling overhead, thereby improving session establishment efficiency, reducing resource overhead in the session establishment process, and effectively utilizing network transmission resources. On the other hand, when other network elements (e.g., a second network element) request information about nodes supporting the execution of business processes (e.g., a first business process), the first network element can specifically provide feedback to the second network element with information about nodes supporting the execution of the first business process (e.g., first information). The second network element can then determine the first node using the first information, enabling the first node to execute the first business process, thus improving processing efficiency. In summary, this application not only improves session establishment efficiency, reduces resource overhead in the session establishment process, and effectively utilizes network transmission resources, but also improves the processing efficiency of business processes.

[0093] The communication methods shown below (such as) Figure 4 For detailed descriptions of the first network element, second network element, third network element, fourth network element, and first node, please refer to [the relevant documentation / reference]. Figure 1 Details will not be elaborated here. For ease of description, in the embodiments of this application, specific examples may be used, such as the first network element being a WRF network element, the second network element being a CPF network element, the third network element being a DMF network element, the fourth network element being a UDM network element, and the first node being the first workflow or workflow1. However, this should not be construed as a limitation on the embodiments of this application.

[0094] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0095] Please see Figure 4 , Figure 4 This is a flowchart illustrating a communication method provided in an embodiment of this application. Optionally, this method can be applied to a communication system, for example, to... Figure 1 The communication system shown.

[0096] like Figure 4 The method shown may include steps S401-S402. It should be understood that, for ease of description, this application describes the process using the sequence S401-S402, but does not limit the execution to this specific order. This application's embodiments do not limit the order of execution, the execution time, or the number of executions of one or more of the above steps. Steps S401-S402 are as follows:

[0097] Step S401: The first node sends registration information to the first network element.

[0098] Accordingly, the first network element receives the registration information.

[0099] The registration information includes the functional identification information of the first node and the first information, which is used to identify the first node. For example, the first node can be replaced with the first workflow or workflow1.

[0100] The functional identification information and first information of the first node are described in detail below, as exemplified:

[0101] (1) The function identification information of the first node (e.g., represented as function ID) is used to indicate the ability of the first node to support the execution of the first business process. This ability may consist of service nodes that provide one or more atomic capabilities and interactions with third network elements.

[0102] For example, function ID=PDU session establishment indicates that the first node has the atomic capabilities related to PDU session establishment, specifically including atomic capabilities such as creating session management context information, generating session policies, and confirming session-related parameters. Similarly, function ID=PDU session modification indicates that the first node has the capability to modify PDU sessions, and function ID=PDU session release indicates that the first node has the capability to release PDU sessions.

[0103] It should be understood that the above are only some possible cases shown for the convenience of describing the functional identification information of the first node, and are not intended to limit the specific content of the functional identification information of the first node in the embodiments of this application.

[0104] (2) The first information includes the identification information of the first node (e.g., represented as workflow instance ID) and / or the address information of the first node (e.g., represented as the fully qualified domain name (FQDN) of the first node or the IP address of the first node).

[0105] The identifier information of the first node is used to identify instances of the first node, and instances of the first node can be distinguished by this identifier. For example, the identifier information of the first node can be workflow1. Optionally, the identifier information of multiple nodes can correspond to the same functional identifier information.

[0106] The address information of the first node indicates the FQDN address or IP address of that node instance, and the corresponding node instance can be found through the FQDN address or IP address. For example, if the IP address of the first node is 192.168.111.1, the corresponding first node can be found through this address.

[0107] Optionally, the terminal device sends a second request to the second network element via a Non-Access stratum (NAS) message.

[0108] Accordingly, the second network element receives a second request from the terminal device.

[0109] The second request is used to request the execution of the first business process. For example, the first business process includes at least one of the following business processes: PDU session establishment process, PDU session modification process, PDU session release process, UE registration process, N2 handover process, etc.

[0110] It should be understood that the above are only some possible scenarios shown for the purpose of describing the first business process, and are not intended to limit the specific content of the first business process in the embodiments of this application.

[0111] Furthermore, after receiving the second request from the terminal device, the second network element can obtain the first information.

[0112] Optionally, the second network element may obtain the first information by having the first network element send the first information to the second network element according to an instruction from the second network element.

[0113] As one possible implementation, the second network element sends a first request to the first network element.

[0114] The first request carries the first business identifier information of the first business process, which is used to query the node executing the first business process. The first response information carries first information. For example, when it is necessary to request a node to execute a PDU session establishment process, the first business identifier information of the first business process is the identifier of the PDU session establishment process. Similarly, when it is necessary to request a node to execute a PDU session modification process, the first business identifier information of the first business process is the identifier of the PDU session modification process.

[0115] For example, when the first business process is a PDU session establishment process, the second network element requests the first network element to discover the node with function ID = PDU session establishment.

[0116] Optionally, the second network element receives first response information from the first network element. For example, the first network element sends first response information to the second network element based on stored registration information. This first response information carries first information about the node satisfying function ID = PDU session establishment. For instance, the node satisfying function ID = PDU sessionestablishment is the first node (e.g., represented as workflow1), and the first information is workflow1 and / or the address information of workflow1, 192.168.111.1.

[0117] Furthermore, after receiving the first response information, the second network element can send a first service process execution request to the selected first node based on the second request and the first information, that is, send a PDU session establishment request to workflow1.

[0118] Accordingly, the first node receives the first business process execution request. Optionally, after receiving the first business process execution request, the first node executes the PDU session establishment process.

[0119] During or after the first node completes the PDU session establishment process, the first node and / or the second network element may send messages to the user plane function network element and / or access network equipment and / or terminal equipment to establish a PDU session.

[0120] The following are three possible implementation methods for the interaction and division of labor between the first node and / or the second network element and the user plane functional network element and / or access network equipment and / or terminal equipment, as exemplified below:

[0121] In the first implementation method, during or after the PDU session establishment process is executed, the first node is responsible for interacting with the user plane function network element and / or access network device and / or terminal device to obtain the information required to establish the PDU session, and the second network element is responsible for receiving the second request from the terminal device and transmitting the NAS message.

[0122] In the second implementation method, the second network element is responsible for interacting with the user plane function network element and / or access network equipment and / or terminal equipment. The first node sends the information used to establish the PDU session to the second network element. For example, after completing the PDU session establishment process, the first node sends information such as Quality of Service (QoS) profiles to the access network equipment.

[0123] In the third implementation method, the first node is responsible for interacting with at least one of the user plane function network elements and / or access network devices and / or terminal devices, while the second network element is responsible for interacting with the user plane function network elements and / or access network devices and / or terminal devices other than those that have already interacted with the first node. For example, the second network element is responsible for interacting with the access network devices and / or terminal devices, while the first node is responsible for interacting with the user plane function network elements.

[0124] Step S402: The first node sends a third request to the third network element.

[0125] The third request carries context information about the first business process. This context information typically refers to parameter information related to the current business process, used and / or generated during its execution. For example, taking the first business process as a PDU session establishment process, the context information might include DNN, S-NSSAI, etc. The third request is used to request the storage of the first business process's context information.

[0126] Optionally, after the first node completes the first business process, it can store the relevant information of the first business process (such as the context information of the first business process) in a third network element, so that other nodes can directly call the relevant information of the first business process when executing other business processes. For example, taking the first business process as a PDU session establishment process and other business processes as PDU session modification processes, after the first node completes the PDU session establishment process, it can store the relevant information of the PDU session establishment process (such as the context information of the PDU session establishment process) in a third network element, so that other nodes can directly call the relevant information of the PDU session establishment process when executing the PDU session modification process. Further optionally, after uploading the relevant information of the first business process, the first node does not store the relevant parameters. For example, after completing the first business process, the first node does not store the context information of the first business process.

[0127] It should be noted that the network entities involved currently require certain information (such as information used and / or generated by the previous business process) to execute the business process. This information can be stored locally or obtained from other network entities. After the business process is completed, new related information (such as information used and / or generated by new business processes) will be generated. This new related information can also be stored locally or on other network entities. In the embodiments of this application, the network entities executing the business process typically store information locally while executing the business process, obtain the necessary information from other network entities before executing the business process, and store the newly generated related information on other network entities after executing the business process, without storing this information themselves. This design reduces information redundancy caused by repeated maintenance of context information, simplifies business execution logic, and effectively saves network transmission resources.

[0128] Optionally, since the third request may carry not only the context information of the first business process, but also identification parameter information that can be used to identify the context information of the first business process, the following are two possible scenarios for setting the identification parameter information:

[0129] In scenario one, the third request also carries the second business identification information of the first business process. This second business identification information is used to query the context information of the first business process. For example, when the first business process is a PDU session establishment process, the second business identification information of the first business process can be the PDU session ID.

[0130] In summary, the third request (i.e., storage request) sent by the first node to the third network element carries the PDU session ID and the context information of the first business process. If a subsequent node executing other business processes (e.g., the second node, or workflow2) needs to obtain the relevant information carried in the third request (e.g., workflow2 performing the PDU session modification process needs to obtain the relevant information generated by the first node's workflow1 executing the PDU session establishment process), and there is no conflict between the first and second nodes (i.e., the second network element will not execute two conflicting nodes simultaneously, such as two nodes both executing the PDU session modification process being conflicting), the second node queries the third network element for relevant indicators of the first business process (e.g., SSC, S-NSSAI, etc.) based on the second business identification information of the first business process (e.g., the PDU session ID). The third network element can then obtain the context information of the first business process based on the second business identification information and return it to the second node.

[0131] In the second scenario, the third request also carries the second business identification information of the first business process and the functional identification information of the first node. The functional identification information of the first node is used to indicate the first node's ability to execute the first business process. The second business identification information of the first business process and the functional identification information of the first node are used to query the context information of the first business process. For example, when the first business process is a PDU session establishment process, the second business identification information of the first business process can be the PDU session ID.

[0132] In summary, the third request (also known as a storage request) sent by the first node to the third network element carries the PDU session ID, function ID, and context information of the first business process. When subsequent nodes executing other business processes (such as the second node, or workflow2) need to obtain the relevant information carried in the third request (e.g., workflow2 performing a PDU session modification process needs to obtain the relevant information generated by the first node's workflow1 executing the PDU session establishment process), the second network element sends a business process request message to the second node carrying the previous function identifier information (e.g., represented by the previous function ID). The previous function identifier information is used to represent the information of the business process executed in the previous step of the current business process, or it is used to represent the information of the business process executed in the most recent step before the current business process (e.g., if the second network element finds that the second node is executing a PDU session release process, and the second network element locally records that the previous step of this PDU session was a PDU session establishment process, then previous function ID = PDU session establishment; if the second network element locally records that the previous step of this PDU session was a PDU session modification process, then previous function ID = PDU session). The second node queries the third network element for relevant indicators of the first business process (such as SSC, S-NSSAI, etc.) based on the second business identification information and the front-end function identification information of the first business process. The third network element can obtain the context information of the first business process based on the second business identification information and the function identification information of the first node, and return it to the second node.

[0133] In one possible design, the above scheme does not standardize the process of parameter passing and generating context information for the first business process within the first node. This brings a certain degree of flexibility in orchestration and internal implementation, but it also introduces new problems. For example, nodes from different vendors cannot directly load the context information of the corresponding business processes, which will prevent sequentially related services from being implemented across vendor devices (for example, the nodes executing the PDU session establishment process and the PDU session modification process must come from the same vendor to ensure that the context information of the business process can be read smoothly). In addition, different parameter passing within nodes from different vendors may lead to differences in the content exchanged with the fourth network element and the third network element, causing services from different vendors to be unable to work together, thus reducing the flexibility of orchestration.

[0134] Based on this, a standardized solution is provided below for configuring the interface parameters of each service within the first node and for outputting the context information of the first business process. Taking the node executing the PDU session as an example, a possible parameter configuration for the context information of the PDU session process uploaded or requested by the node is shown in Table 1:

[0135] Table 1

[0136]

[0137]

[0138] In one possible design, referring to Table 1, during the PDU session establishment process executed by the first node, the first node can send a fourth request to the fourth network element, receive access and mobility management subscription data corresponding to the terminal device from the fourth network element, and obtain supplementary session management context information based on NAS information and access and mobility management subscription data corresponding to the terminal device.

[0139] The fourth request carries the identification information of the terminal device and is used to request the access and mobility management subscription data corresponding to the terminal device.

[0140] For example, this scheme performs the context information supplementary atomic capability for session management, with input information being NASmessage and UE subscription data, and output information being SM context.

[0141] Furthermore, the first node sends a fifth request to the fourth network element, receives session management subscription data corresponding to the terminal device from the third network element, and determines to establish a PDU session based on the supplemented session management context information and the session management subscription data corresponding to the terminal device.

[0142] The fifth request carries the identification information of the terminal device and is used to request the session management subscription data corresponding to the terminal device.

[0143] For example, this scheme performs an atomic capability to determine whether to establish a PDU session, with the input information being SMcontext and SM subscription data, and the output information being result indication and SM context.

[0144] Optionally, referring to Table 1, the process of generating the context information of the first service process in this scheme needs to be standardized. Standardization of this process enables cross-vendor combinations of the first node and the fourth network element, increasing the flexibility of orchestration and internal implementation. For example, in the PDU session establishment process, the context information of the first service process may include session management context information (e.g., SMcontext) and user subscription data (e.g., user subscription data). The session management context information may include PDU session identification information (e.g., PDU session ID), terminal device identification information (e.g., UE ID), DNN, S-NSSAI, radio access technology type (RAT type), quality of service profiles (QoS profiles), and user plane function network element information (UPF info). User subscription data may include user permanent identifier (SUPI), authentication information, service area restriction information, allowed data networks (DNs), allowed session and service continuity modes (SSC modes), and other information.

[0145] As one possible implementation, taking the first business process as the PDU session establishment process as an example, after the first node completes the PDU session establishment process, if a second business process needs to be executed (for example, the second business process includes the PDU session release process or the PDU session modification process; this solution takes the second business process as the PDU session modification process as an example), the terminal device sends a PDU session modification request to the second network element through a NAS message.

[0146] Accordingly, the second network element receives a PDU session modification request from the terminal device. The process by which a node capable of executing the second service process (e.g., denoted as the second node) registers with the first network element, and the process by which the second network element discovers a node capable of executing the second service process, can be referred to in step S401; this solution will not elaborate further on this.

[0147] The following is an example of how the second node executes the second business process:

[0148] As one possible implementation, the second node sends a sixth request to the third network element to receive context information of the first service process from the third network element.

[0149] Accordingly, the third network element receives the sixth request from the second node and sends the context information of the first service process to the second node.

[0150] The sixth request is used to query the context information of the first node.

[0151] Optionally, the second node sends a seventh request to the third network element.

[0152] The seventh request carries the context information of the second business process, and is used to request the storage of the context information of the second business process.

[0153] Specifically, after the second node completes the execution of the second business process, it can store the relevant information of the second business process (such as the context information of the second business process) in the third network element, so that other nodes can directly call the relevant information of the second business process when executing other business processes (such as the third business process, which can be the PDU session release process).

[0154] Alternatively, after uploading the relevant information for the second business process, the second node does not store the relevant parameters, thus becoming stateless. For example, after completing the PDU session modification process, the second node does not store the context information of the PDU session modification process.

[0155] In this application, the first node registers its functional identification information and first information used to identify the first node with the first network element. This enables the first network element to promptly obtain information about nodes that support the execution of business processes when executing specific business processes, and transmit this information to other network elements. Other network elements then select nodes that support the execution of business processes to execute the business processes. This avoids the problem of frequent interactions between different network elements during session establishment, which would cause significant signaling overhead. As a result, session establishment efficiency is improved, resource overhead during session establishment is reduced, and network transmission resources are effectively utilized.

[0156] Please see Figure 5A , Figure 5A This is a flowchart illustrating the registration of node information and the acquisition of context information for a PDU session establishment process, as provided in an embodiment of this application. It should be understood that, for ease of description, this application describes the process in the order of steps S11-S17, but does not limit the execution to this specific order. This application does not limit the order of execution, the execution time, or the number of executions of one or more of the above steps. Figure 5A As shown, the specific steps in Case 1 are as follows:

[0157] S11: The first node sends registration information to the first network element.

[0158] The registration information includes the functional identification information of the first node and the first information. The first information is used to identify the first node. The first node provides a PDU session establishment process for the terminal device. The functional identification information of the first node is used to indicate the first node's ability to support the execution of the PDU session establishment process.

[0159] S12: The first network element sends an indication message to the first node. The indication message is used to indicate whether the first node's registration was successful or failed.

[0160] S13: The terminal device sends a second request to the second network element.

[0161] Accordingly, the second network element receives the second request. The second request is used to request the execution of the PDU session establishment process.

[0162] S14: The second network element obtains the first information. The first information is used to determine the first node.

[0163] Optionally, a possible implementation of the second network element obtaining the first information includes: the second network element sending a first request to the first network element and receiving first response information from the first network element.

[0164] The first request carries the first business identification information of the first business process (for example, when a requesting node needs to execute the PDU session establishment process, the first business identification information of the first business process is the identifier of the PDU session establishment process). The first request is used to query the node executing the PDU session establishment process, and the first response information carries the first information.

[0165] Optionally, the first information includes the identification information of the first node (e.g., represented as workflow instance ID) and / or the address information of the first node (e.g., represented as the fully qualified domain name (FQDN) of the first node or the IP address of the first node).

[0166] The identifier information of the first node is used to identify instances of the first node, and instances of the first node can be distinguished by this identifier. For example, the identifier information of the first node can be workflow1. Optionally, the identifier information of multiple nodes can correspond to the same functional identifier information.

[0167] The address information of the first node indicates the FQDN address or IP address of that node instance, and the corresponding node instance can be found through the FQDN address or IP address. For example, if the IP address of the first node is 192.168.111.1, the corresponding first node can be found through this address.

[0168] S15: The second network element sends a first service process execution request to the first node. Accordingly, the first node receives the first service process execution request.

[0169] S16: The first node executes the PDU session establishment process.

[0170] Optionally, to enable cross-vendor combinations between the first node and subsequent network elements, increasing orchestration and internal implementation flexibility, the interface parameter configuration and output of information required for the PDU session establishment process of each service within the first node can be standardized. The following provides exemplary steps for standardizing the interface parameter configuration and output of information required for the PDU session establishment process of each service within the first node:

[0171] Step 1: The first node sends the fourth request to the fourth network element.

[0172] Accordingly, the fourth network element receives the fourth request.

[0173] The fourth request carries the identification information of the terminal device and is used to request the access and mobility management subscription data corresponding to the terminal device.

[0174] Step 2: The fourth network element sends the access and mobility management subscription data corresponding to the terminal device to the first node.

[0175] Accordingly, the first node receives the access and mobility management subscription data corresponding to the terminal device.

[0176] Step 3: The first node performs atomic capabilities to supplement the context information of session management.

[0177] Specifically, the first node obtains supplementary session management context information based on NAS information and access and mobility management subscription data corresponding to the terminal device.

[0178] Step 4: The first node sends the fifth request to the fourth network element.

[0179] Accordingly, the fourth network element receives the fifth request.

[0180] The fifth request carries the identification information of the terminal device and is used to request the session management subscription data corresponding to the terminal device.

[0181] Step 5: The fourth network element sends the session management subscription data corresponding to the terminal device to the first node.

[0182] Accordingly, the first node receives the session management subscription data corresponding to the terminal device.

[0183] Step 6: The first node executes the atomic capability to determine whether to establish a PDU session.

[0184] Specifically, the first node determines to establish a PDU session based on the supplemented session management context information and the session management subscription data corresponding to the terminal device.

[0185] Step 7: The first node sends a data request to the fourth network element.

[0186] Accordingly, the fourth network element receives the data request. This data request carries the identification information of the terminal device and is used to request policy data.

[0187] Step 8: The fourth network element sends policy data to the first node. Accordingly, the first node receives the policy data.

[0188] Step 9: The first node executes the atomic capability to generate policy information for the PDU session.

[0189] Step 10: The first node executes the atomic capability to determine the PDU session release parameters.

[0190] Step 11: Optionally, the first node performs an atomic capability to update policy information for the PDU session.

[0191] Step 12: The first node executes the atomic capability to determine the PDU session release parameters.

[0192] S17: The first node sends a third request to the third network element.

[0193] The third request carries context information about the PDU session establishment process, and is used to request the storage of this context information.

[0194] It should be noted that detailed explanations of steps S11-S17 above can be found at [link to relevant documentation]. Figure 4 The embodiments described herein will not be repeated here.

[0195] Please see Figure 5B , Figure 5B This is a flowchart illustrating the registration of node information and the acquisition of context information for PDU session modification, provided in an embodiment of this application. It should be understood that, for ease of description, this application describes the process in the order of steps S21-S27, but does not limit the execution to this specific order. This application does not limit the order of execution, the execution time, or the number of executions of one or more of the above steps. Figure 5B As shown, the specific steps in Case 2 are as follows:

[0196] S21: The second node sends registration information to the first network element.

[0197] The registration information includes the functional identification information of the second node and the first information. The first information is used to identify the second node. The second node provides the PDU session modification process for the terminal device. The functional identification information of the second node is used to indicate the ability of the second node to perform the PDU session modification process.

[0198] S22: The first network element sends an indication message to the second node. This indication message indicates whether the second node's registration was successful or failed.

[0199] S23: The terminal device sends a second request to the second network element.

[0200] Accordingly, the second network element receives the second request. The second request is used to request the execution of the PDU session modification procedure.

[0201] S24: The second network element obtains the first information. The first information is used to determine the second node.

[0202] Optionally, a possible implementation of the second network element obtaining the first information includes: the second network element sending a first request to the first network element and receiving first response information from the first network element.

[0203] The first request carries the first business identification information of the first business process (for example, when a requesting node needs to execute the PDU session modification process, the first business identification information of the first business process is the identifier of the PDU session modification process). The first request is used to query the node executing the PDU session modification process, and the first response information carries the first information.

[0204] Optionally, the first information includes the identification information of the second node (e.g., represented as a workflow instance ID) and / or the address information of the second node (e.g., represented as the fully qualified domain name (FQDN) of the second node or the IP address of the second node).

[0205] The identification information of the second node is used to identify instances of the second node, and instances of the second node can be distinguished by this identification. For example, the identification information of the second node can be workflow2. Optionally, the identification information of multiple nodes can correspond to the same functional identification information.

[0206] The address information of the second node indicates the FQDN address or IP address of the node instance, which can be used to find the corresponding node instance. For example, if the IP address of the second node is 153.121.155.1, the corresponding second node can be found through this address.

[0207] S25: The second network element sends a first service process execution request to the second node. Accordingly, the second node receives the first service process execution request.

[0208] S26: The second node sends the sixth request to the third network element.

[0209] Accordingly, the third network element receives the sixth request.

[0210] The sixth request carries PDU session identification information (e.g., represented as PDU session ID) and information about the business process executed in the previous step of the current business process (or alternatively, information about the business process executed in the previous step of the current business process can also be called previous function identification information, such as previous functionID; for example, if the second network element finds that the second node supports the execution of the PDU session modification process, and the second network element locally records that the previous step of this PDU session was the PDU session establishment process, then previous function ID = PDU session establishment). The sixth request is used to request information about the use and / or generation of the business process executed in the previous step of the current business process.

[0211] S27: The third network element sends information about the use and / or generation of the business process executed in the previous step of the current business process to the second node.

[0212] Accordingly, the second node receives information about the usage and / or generation of the business process executed in the previous step of the current business process. For example, if the current business process is a PDU session modification process, and the business process executed in the previous step of the PDU session modification process was a PDU session establishment process, the second node receives information about the usage and / or generation of the PDU session establishment process. For instance, the information about the usage and / or generation of the PDU session establishment process may include DNN, S-NSSAI, etc.

[0213] S28: The second node executes the PDU session modification process.

[0214] Optionally, to enable cross-vendor combinations between the second node and subsequent network elements, increasing orchestration and internal implementation flexibility, the process of configuring interface parameters and outputting the information required for the PDU session modification process for each service within the second node can be standardized during the execution of the PDU session modification process. The following provides exemplary steps for standardizing the process of configuring interface parameters and outputting the information required for the PDU session modification process for each service within the second node:

[0215] Step 1: The second node performs the atomic capability of updating the context information of session management.

[0216] Specifically, the second node obtains the updated session management context information based on the information used and / or generated by the business process executed in the previous step of the current business process.

[0217] Step 2: The second node sends a data request to the fourth network element.

[0218] Accordingly, the fourth network element receives the data request. This data request carries the terminal device's identification information and relevant metrics of the current business process (such as DNN, S-NSSAI, etc.), and is used to request policy data.

[0219] Step 3: The fourth network element sends policy data to the second node. Accordingly, the second node receives the policy data.

[0220] Step 4: The second node executes the atomic capability to update policy information for the PDU session.

[0221] Step 5: The second node executes the atomic capability of releasing parameters for the PDU session release.

[0222] S29: The second node sends the seventh request to the third network element.

[0223] The seventh request carries the identification information of the PDU session (e.g., represented as the PDU session ID) and the context information of the PDU session modification process. The seventh request is used to request the storage of the context information of the PDU session modification process. Optionally, the seventh request also carries the functional identification information of the second node.

[0224] Accordingly, the third network element receives the seventh request. Optionally, the third network element sends a response to the seventh request to the second node. Accordingly, the second node receives the response. The response carries storage result indication information.

[0225] It should be noted that detailed explanations of steps S21-S29 above can be found at [link to relevant documentation]. Figure 4 The aforementioned embodiments will not be repeated here. Additionally, Figure 5A The PDU creation process is executed with the first node. Figure 5B The example of the second node executing the PDU modification process is only for the purpose of illustrating the solution. The second node and the first node mentioned above can be the same node or different nodes. This application does not limit the ability of the nodes to execute business.

[0226] The methods of the embodiments of this application have been described in detail above. The apparatus of the embodiments of this application is provided below.

[0227] It should be understood that the division of units in the apparatus provided in this application embodiment is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units in the apparatus can be implemented by a processor calling software. For example, the apparatus includes a processor connected to a memory, which stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of each unit of the apparatus. The processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is either internal or external to the apparatus.

[0228] Alternatively, the units in the device can be implemented as hardware circuits. The functionality of some or all of the units can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the above units is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through a configuration file, thereby achieving the functionality of some or all of the above units.

[0229] In the embodiments of this application, each unit in the device may be one or more processors (or processing circuits) configured to implement the above methods, such as: CPU, graphics processing unit (GPU), neural network processing unit (NPU), tensor processing unit (TPU), deep learning processing unit (DPU), microprocessor unit (MPU), digital signal processor (DSP), ASIC, FPGA, or a combination of at least two of these processor forms.

[0230] Furthermore, the units in the above devices can be integrated in whole or in part, or they can be implemented independently. In one implementation, these units are integrated together as a system-on-a-chip (SOC). The SOC may include at least one processor for implementing any of the above methods or for implementing the functions of the units in the device. The at least one processor can be of different types, such as including a CPU and an FPGA, or including a CPU and an AI processor, or including a CPU and a GPU, etc. Several possible devices are listed below.

[0231] Please see Figure 6 , Figure 6This is a schematic diagram of the structure of a communication device 60 provided in an embodiment of this application. Optionally, the communication device 60 can be a first network element, or a device within the first network element, such as a chip or integrated circuit. The communication device 60 is used to implement the aforementioned communication method, for example... Figure 4 The communication method shown.

[0232] In one possible design, the communication device 60 includes a communication unit 601 and a processing unit 602. The communication device 60 is used to implement the aforementioned communication method, for example... Figure 4 The communication method is illustrated. For example, the communication device may be used to execute a method executed by a first network element, or a method executed by a second network element, or a method executed by a third network element, or a method executed by a first node.

[0233] The embodiments of this application and the method embodiments shown above are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the embodiments shown above, which will not be repeated here.

[0234] Please see Figure 7 , Figure 7 This is a schematic diagram of another communication device 70 provided in an embodiment of this application. The communication device 70 can be an independent device, such as a first network element, a second network element, a third network element, or a first node, or it can be a device included in a first network element, a second network element, a third network element, or a first node, such as a chip, a software module, or an integrated circuit. The communication device 70 can include at least one processor 701 and a communication interface 702. Optionally, it can also include at least one memory 703. Further optionally, it can also include a connection line 704, wherein the processor 701, the communication interface 702, and / or the memory 703 are connected through the connection line 704, and / or communicate with each other through the connection line 704 to transmit control signals and / or data signals.

[0235] Wherein: Processor 701 is a module that performs arithmetic and / or logical operations, and may specifically include one or more of the following modules: filter, modem, power amplifier, low noise amplifier (LNA), baseband processor, radio frequency processor, radio frequency circuit, CPU, AP, microcontroller unit (MCU), electronic control unit (ECU), GPU, MPU, ASIC, image signal processor (ISP), DSP, FPGA, complex programmable logic device (CPLD), or coprocessor, etc.

[0236] The communication interface 702 can be used to provide information input or output to at least one processor, or to receive signals sent externally and / or send signals to externally.

[0237] For example, the communication interface 702 may include interface circuitry, such as input / output interfaces, chip pins, etc.

[0238] For example, the communication interface 702 may include a wired link interface such as an Ethernet cable, or a wireless link interface (Wi-Fi, Bluetooth, general wireless transmission, vehicle short-range communication technology and other short-range wireless communication technologies, etc.).

[0239] Optionally, the communication interface 702 may also include a radio frequency transmitter, an antenna, etc. When the communication interface 702 includes an antenna, the number of antennas can be one or more.

[0240] As one possible design, if the communication device 70 is a first network element, a second network element, a third network element, or a first node, the communication interface 702 may include a receiver and a transmitter. The receiver and transmitter may be the same component or different components. When the receiver and transmitter are the same component, this component may be referred to as a transceiver.

[0241] As another possible design, if the communication device 70 is a chip or circuit, the communication interface 702 may include an input interface and an output interface. The input interface and the output interface may be the same interface or they may be different interfaces.

[0242] Alternatively, the functions of the communication interface 702 can be implemented by a transceiver circuit or a dedicated transceiver chip.

[0243] Memory 703 provides storage space, in which data such as the operating system and computer programs can be stored. Memory 703 can be one or a combination of several of the following: cache, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), compact disc read-only memory (CD-ROM), synchronous dynamic random access memory (SDRAM), hard disk drive (HDD), solid-state drive (SSD), etc. Memory is any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in the embodiments of this application can also be a circuit or any other device capable of implementing storage functions, used to store computer programs or instructions, and / or data.

[0244] The functions and operations of each module or unit in the communication device 70 listed above are merely illustrative examples.

[0245] Each functional unit in the communication device 70 can be used to implement the aforementioned communication method, for example... Figure 4 The communication method shown is, for example, a method for executing the first network element, or a method for executing the second network element, or a method for executing the third network element, or a method for executing the first node.

[0246] Optionally, processor 701 may be a processor specifically designed to perform the aforementioned methods (for ease of distinction, referred to as a dedicated processor), or a processor that performs the aforementioned methods by calling a computer program (for ease of distinction, referred to as a dedicated processor). Optionally, at least one processor may include both dedicated processors and general-purpose processors.

[0247] Optionally, if the communication device 70 includes at least one memory 703, and the processor 701 implements the aforementioned communication method by calling a computer program, the computer program can be stored in the memory 703.

[0248] This application also provides a chip, which includes logic circuitry and a communication interface. The communication interface is used to receive or transmit signals; the logic circuitry is used to receive or transmit signals through the communication interface. The chip is used to implement the aforementioned communication method, for example... Figure 4 The communication method shown is, for example, a method for executing the first network element, or a method for executing the second network element, or a method for executing the third network element, or a method for executing the first node.

[0249] This application also provides a communication system, which includes a first network element, a second network element, a third network element, and a first node.

[0250] Optionally, the communication system may also include a fourth network element.

[0251] This application also provides a computer-readable storage medium storing instructions that, when executed on at least one processor (or communication device), implement the aforementioned communication method, for example... Figure 4 The communication method shown is, for example, a method for executing the first network element, or a method for executing the second network element, or a method for executing the third network element, or a method for executing the first node.

[0252] This application also provides a computer program product, which includes computer instructions for implementing the aforementioned communication method, for example... Figure 4 The communication method shown is, for example, a method for executing the first network element, or a method for executing the second network element, or a method for executing the third network element, or a method for executing the first node.

[0253] It should be noted that, in the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplarily" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0254] In the embodiments of this application, "at least one" refers to one or more items, and "more than one" refers to two or more items. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items.

[0255] For example, at least one of a, b, or c can be represented as: a, b, c, (a and b), (a and c), (b and c), or (a and b and c), where a, b, and c can be single or multiple. "AND / OR" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects have an "OR" relationship.

[0256] Furthermore, unless otherwise stated, the use of ordinal numbers such as "first" and "second" in the embodiments of this application is for distinguishing multiple objects and is not for limiting the order, sequence, priority, or importance of multiple objects. Similarly, terms like "first node" and "second node" are merely for convenience in describing new parameters in different implementations and do not indicate differences in their execution operations, importance, structure, etc.

[0257] In the above embodiments, the term "when..." can be interpreted, depending on the context, as meaning "if...", "before...", "determined...", or "detected...". The above descriptions are merely optional embodiments of this application and are not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the concept and principles of this application should be included within the protection scope of this application.

[0258] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

Claims

1. A communication method, characterized in that, Applied to the first network element, the method includes: The system receives registration information from a first node, wherein the registration information includes the first node's functional identification information and first information. The first information is used to identify the first node, and the first node's functional identification information is used to indicate the first node's ability to support the execution of a first business process. The first node provides the first business process to the terminal device.

2. The method according to claim 1, characterized in that, After completing the first business process, the first node does not store the context information of the first business process.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Receive a first request from a second network element, wherein the first request is used to query the node executing the first business process; Send a first response message to the second network element, wherein the first response message carries the first information.

4. The method according to any one of claims 1-3, characterized in that, The first business process is the Protocol Data Unit (PDU) session establishment process, and the functional identification information of the first node is used to indicate the first node's ability to perform the PDU session establishment process.

5. The method according to any one of claims 1-3, characterized in that, The first business process is a PDU session modification process, and the function identification information of the first node is used to indicate the ability of the first node to execute the PDU session modification process.

6. A communication method, characterized in that, Applied to the first node, the method includes: Receive the first service process execution request from the second network element; A third request is sent to a third network element, wherein the third request carries context information of the first service process, and the third request is used to request the storage of the context information of the first service process.

7. The method according to claim 6, characterized in that, After completing the first business process, the first node does not store the context information of the first business process.

8. The method according to claim 6 or 7, characterized in that, The first business process includes a Protocol Data Unit (PDU) session establishment process or a PDU session modification process.

9. The method according to any one of claims 6-8, characterized in that, The method further includes: The first network element sends registration information, wherein the registration information includes the first node's functional identification information and first information, the first information being used to identify the first node, and the first node's functional identification information being used to indicate the first node's ability to support the execution of a first business process, and the first node providing the first business process to the terminal device.

10. The method according to any one of claims 6-9, characterized in that, The third request also carries the second business identification information of the first business process, which is used to query the context information of the first business process.

11. The method according to any one of claims 6-9, characterized in that, The third request also carries the second business identification information of the first business process and the functional identification information of the first node. The functional identification information of the first node is used to indicate the ability of the first node to execute the first business process. The second business identification information of the first business process and the functional identification information of the first node are used to query the context information of the first business process.

12. The method according to any one of claims 6-11, characterized in that, The method further includes: A fourth request is sent to a fourth network element, wherein the fourth request carries the identification information of the terminal device and is used to request access and mobility management subscription data corresponding to the terminal device; Receive access and mobility management subscription data corresponding to the terminal device from the fourth network element; Based on the non-access stratum NAS information and the access and mobility management subscription data corresponding to the terminal device, the supplemented session management context information is obtained.

13. The method according to claim 12, characterized in that, The method further includes: Send a fifth request to the fourth network element, wherein the fifth request carries the identification information of the terminal device and is used to request the session management subscription data corresponding to the terminal device; Receive session management subscription data from the terminal device corresponding to the fourth network element; Based on the supplemented session management context information and the session management subscription data corresponding to the terminal device, a PDU session is determined to be established.

14. A communication device, characterized in that, The communication device includes a communication unit and a processing unit, the communication unit and the processing unit being used to perform the method as described in any one of claims 1-5.

15. A communication device, characterized in that, The communication device includes a communication unit and a processing unit, the communication unit and the processing unit being used to perform the method as described in any one of claims 6-13.

16. A communication device, characterized in that, The communication device includes a processor; When the processor invokes a computer program or instruction in memory, it causes the communication device to implement the method as described in any one of claims 1-5.

17. A communication device, characterized in that, The communication device includes a processor; When the processor invokes a computer program or instruction in memory, it causes the communication device to implement the method as described in any one of claims 6-13.

18. A communication device, characterized in that, It includes logic circuits and interfaces, wherein the logic circuits and the interfaces are coupled; The interface is used for inputting and / or outputting information, and the logic circuit is used to enable the communication device to implement the method as described in any one of claims 1-13.

19. The apparatus according to claim 18, characterized in that, The communication device is a chip or chip system.

20. A communication system, characterized in that, The communication system includes the communication device as described in claim 14 and the communication device as described in claim 15; or The communication system includes the communication device as described in claim 16 and the communication device as described in claim 17.

21. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store instructions or computer programs; The instructions or the computer program are executed to implement the method as described in any one of claims 1-13.

22. A computer program product, characterized in that, include: Instructions or computer programs; The instructions or the computer program are executed to implement the method as described in any one of claims 1-13.

Images