Communication method and apparatus

Abstract

Embodiments of the present application provide a communication method and apparatus. A first execution node obtains an identifier of the first execution node and an identifier of a second execution node, wherein the identifier of the first execution node is used for identifying the identity of the first execution node when executing a first service, the second execution node is an execution node that exchanges data of the first service with the first execution node, and the identifier of the second execution node is used for identifying the identity of the second execution node when executing the first service; and the first execution node transmits the data of the first service to the second execution node on the basis of the identifier of the first execution node and the identifier of the second execution node. By means of the method, the identity security of execution nodes can be ensured when a connectionless service is executed.

Description

Communication method and device Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular to a communication method and apparatus. Background Art

[0002] Research on future mobile networks is in full swing. According to white papers published by various organizations, including operators, equipment manufacturers, and universities, future mobile networks will not only provide connectivity services, but also non-connectivity services such as artificial intelligence (AI), computing, data, and perception services. In the past, with connectivity services, users simply consumed the connectivity services provided by the network as consumers. However, with non-connectivity services, end users can also become service providers, providing the network with some of their terminal capabilities, such as perception, computing, and data processing capabilities.

[0003] In existing 5G networks, different network functions can register their capability information and identity information (identifier or address) with a network repository function (NRF). When a network function needs to invoke the services of other network functions, it can send a network function discovery request message to the NRF. This discovery request message is used to request other network functions with corresponding capability information. The NRF then feeds back the identity information of the other network functions based on the request message.

[0004] However, in non-connection services, the service requester may not be concerned about the specific identity of the service execution node, but only needs to obtain the execution results of the service (for example, perception data, AI model, etc.). Interacting non-connection services based on the above-mentioned existing deterministic identities (such as user equipment (UE) ID, network function (NF) NF ID) may be detrimental to the identity security of the service execution node.

[0005] Summary of the Invention

[0006] The present application provides a communication method and apparatus to ensure identity security between execution nodes when executing non-connection services.

[0007] In a first aspect, the present application provides a communication method. The method can be applied to a first execution node. The first execution node can be a terminal, an access network device, a core network device, etc., and can also be a chip or processor in a terminal, an access network device, a core network device, etc. The present application is not specifically limited here. When executed, the method includes the following process:

[0008] The first execution node obtains the identifier of the first execution node and the identifier of the second execution node, where the identifier of the first execution node is used to identify the temporary identity of the first execution node when executing the first business; the second execution node is the execution node that interacts with the first execution node to exchange data of the first business; the identifier of the second execution node is used to identify the temporary identity of the second execution node when executing the first business; the first execution node transmits the data of the first business to the second execution node based on the identifier of the first execution node and the identifier of the second execution node.

[0009] In this application, the first execution node does not need to obtain the real identity information of the target execution node (i.e., the second execution node), and exchanges data of the first business with the target execution node based on a temporary identity associated with the first business. This method can ensure the security of the identity information of each execution node when exchanging data between the execution nodes.

[0010] In an optional manner, the first execution node obtains configuration information of the first service, and the configuration information of the first service includes: connection parameters required for transmitting data of the first service; the first execution node transmits the data of the first service to the second execution node based on the identifier of the first execution node and the identifier of the second execution node, including: the first execution node transmits the data of the first service to the second execution node based on the identifier of the first execution node, the identifier of the second execution node and the connection parameters.

[0011] In this application, the first execution node uses connection parameters to transmit data to the target execution node, which simplifies the processing flow of determining which communication interface to select to transmit data to the target execution node after obtaining the communication interface information supported by the target execution node, thereby improving data processing efficiency.

[0012] In an optional manner, the connection parameters include first indication information, and the first indication information is used to indicate the type of communication interface used by the first execution node to transmit data of the first service; the first execution node transmits the data of the first service to the second execution node based on the identifier of the first execution node, the identifier of the second execution node and the connection parameters, including: the first execution node transmits the data of the first service to the second execution node using the communication interface type indicated by the first indication information based on the identifier of the first execution node and the identifier of the second execution node.

[0013] In this application, the first execution node uses the communication interface indicated by the first indication information to transmit data to the target execution node, which simplifies the processing flow of determining which communication interface to select to transmit data to the target execution node after obtaining the communication interface information supported by the target execution node, thereby improving data processing efficiency.

[0014] In an optional manner, the connection parameters include second indication information, and the second indication information is used to indicate the communication interface type information supported by the second execution node; the first execution node transmits the data of the first service to the second execution node based on the identifier of the first execution node, the identifier of the second execution node and the connection parameters, including: the first execution node determines the communication interface for exchanging data between the first execution node and the second execution node based on the communication interface type information supported by the first execution node and the second indication information; the first execution node uses the communication interface to transmit the data of the first service to the second execution node based on the identifier of the first execution node and the identifier of the second execution node.

[0015] In the present application, the first execution node determines the communication interface type information supported by the second execution node based on the second indication information. When the first execution node transmits data to the target execution node, it selects the communication interface adapted to the target execution node based on the second indication information to transmit the data of the first business to the target execution node. This method simplifies the processing flow of determining which communication interface to select to transmit data to the target execution node after obtaining the communication interface information supported by the target execution node, thereby improving data processing efficiency.

[0016] In an optional manner, the first execution node sends a capability registration request message to the first network function, where the capability registration request message includes: identity information of the first execution node and capability information of the first execution node; the first execution node receives a response message indicating successful capability registration from the first network function; the capability information of the first execution node includes one or more of the following information: service type information supported by the first execution node, the type of the first execution node, communication interface type information supported by the first execution node, selection priority information of the communication interface when the first execution node supports multiple communication interface types, service level information supported by the first execution node, physical address information of the first execution node, an application identifier, and an identity identifier of the first execution node in the application; the application is an application that provides services for the first execution node.

[0017] In this way, the first network function can obtain the real identity information and capability information of the execution node, so as to better assign an identifier to the execution node and maintain a mapping relationship between the real identity and the assigned identifier.

[0018] In an optional manner, the identifier of the first execution node includes one or more of the following information: the network identifier to which the first execution node belongs, the network function identifier for assigning the identifier to the first execution node, the communication interface type information supported by the first execution node, the type of the first execution node, the identifier of the service executed by the first execution node, the type of service executed by the first execution node, the identifier of the application; the application is an application that provides services to the first execution node.

[0019] By using this information, the second execution node can be informed of the network information to which the first execution node belongs, making it easier for the second execution node to apply for corresponding communication resources, such as communication frequency bands. In addition, if the first and second execution nodes are not from the same operator, roaming issues may arise, and the network functions of the corresponding operator can be determined based on this information. In addition, by enriching the information in the execution node identifier (such as adding network identifiers, interface type information, identifiers of the executed services, etc.), interactions between execution nodes or between execution nodes and the network can be reduced (i.e., no additional interactions are required to obtain this information), thereby reducing information exchange.

[0020] In an optional manner, the identifier of the second execution node includes one or more of the following information: the network identifier to which the second execution node belongs, the network function identifier for assigning the identifier to the second execution node, the communication interface type information supported by the second execution node, the type of the second execution node, the identifier of the service executed by the second execution node, the type of service executed by the second execution node, the identifier of the application; and the application is an application that provides services for the second execution node.

[0021] By carrying the above information in the identifier of the target execution node, the first execution node can know the network information to which the second execution node belongs, which facilitates the first execution node to apply for corresponding communication resources, such as communication frequency bands, etc. In addition, if the first execution node and the second execution node are not from the same operator, there may be roaming problems. The network function of the corresponding operator can be determined based on the above information.

[0022] In an optional manner, the configuration information of the first service also includes one or more of the following information: the network identifier to which the second execution node belongs, the network function identifier for assigning the identifier to the second execution node, the communication interface type information supported by the second execution node, the type of the second execution node, the identifier of the service executed by the second execution node, the type of service executed by the second execution node, the identifier of the application; and the application is an application that provides services to the second execution node.

[0023] By using the above information, the first execution node can know the network information to which the second execution node belongs, which facilitates the application of corresponding communication resources, such as communication frequency bands, etc. In addition, if the first execution node and the second execution node are not from the same operator, there may be roaming problems. The network function of the corresponding operator can be determined based on the above information.

[0024] In a second aspect, the present application provides a communication method, which is applied to a first network function. The first network function may be a network entity, or a logical function (co-deployed with other network functions), or a piece of code or script, or a chip or processor in the network entity. The present application is not specifically limited here, and includes the following process when executed:

[0025] The first network function determines at least one execution node for executing the first service; the first network function assigns an identifier to each of the at least one execution nodes, where the identifier of the first execution node is used to identify a temporary identity of the first execution node when executing the first service, and the first execution node is any one of the at least one execution node; the first network function sends an identifier corresponding to each of the at least one execution node to the first execution node, where the at least one execution node includes a first execution node and a second execution node, where the second execution node is an execution node other than the first execution node in the at least one execution node, and where the identifier of the second execution node is used to identify a temporary identity of the second execution node when executing the first service.

[0026] In the present application, the network function allocates a temporary identifier to the execution node that executes the first service to ensure the security of the identity information of each execution node when the execution nodes exchange data.

[0027] In an optional manner, before the first network function determines at least one execution node for executing the first service, it also includes: the first network function receives a request message sent by the second network function, the request message is sent by the second network function after obtaining information about the first service, and the request message is used to request at least one execution node to execute the first service.

[0028] In an optional manner, the first network function determines at least one execution node for executing the first service, including: after the first network function obtains information about the first service, determining at least one execution node for executing the first service.

[0029] The identity information of the execution node provided by the first network function is used to assign an identifier to the node. An identifier can also be generated for the execution node based on the capability information and identity information of the execution node. Regardless of which of the above methods is used to determine the identifier of the execution node, it can be ensured that the real identity information is not obtained during data exchange between the execution nodes, thereby ensuring the security of the identity information of the execution nodes.

[0030] In an optional manner, the first network function assigns an identifier to at least one execution node respectively, including: the first network function assigns an identifier to at least one execution node respectively based on the identity information of the at least one execution node; or, the first network function assigns an identifier to at least one execution node respectively based on the capability information of the at least one execution node and the identity information of the at least one execution node.

[0031] From this, it can be seen that the first network function can directly assign an identifier to the execution node based on the identity information of the execution node, and can also generate an identifier for the execution node based on the capability information of the execution node and the identity information of the execution node. Regardless of which of the above methods is used to determine the identifier of the execution node, it can be ensured that the real identity information is not obtained during data interaction between the execution nodes, thereby ensuring the security of the identity information of the execution nodes.

[0032] In an optional manner, a first network function receives a capability registration request message from at least one execution node, wherein the capability registration request message includes: identity information of at least one execution node and capability information of at least one execution node; the first network function sends a response message of successful capability registration to at least one execution node; the capability information of at least one execution node includes one or more of the following information: service type information supported by at least one execution node, type of at least one execution node, communication interface type information supported by at least one execution node, selection priority information of the communication interface when at least one execution node supports multiple communication interface types, service level information supported by at least one execution node, physical address information of at least one execution node, an application identifier, and an identity identifier of at least one execution node in the application; the application is an application that provides services for at least one execution node.

[0033] In an optional manner, the identifier of at least one execution node includes one or more of the following information: the network identifier to which the at least one execution node belongs, the network function identifier for assigning the identifier to the at least one execution node, the communication interface type information supported by the at least one execution node, the type of the at least one execution node, the identifier of the service executed by the at least one execution node, the type of the service executed by the at least one execution node, the identifier of the application; and the application is an application that provides services for the at least one execution node.

[0034] In an optional manner, the first network function determines configuration information of the first service based on information of the first service and an identifier of at least one execution node, where the configuration information of the first service includes connection parameters required to transmit data of the first service; the first network function sends the configuration information of the first service to the first execution node.

[0035] In an optional manner, the connection parameters include first indication information, where the first indication information is used to indicate the type of communication interface used by the first execution node to transmit data of the first service; or, the connection parameters include second indication information, where the second indication information is used to indicate the type of communication interface supported by the second execution node.

[0036] In an optional manner, the first business includes one or more of the following: computing services, perception services, AI services, and data services.

[0037] In a third aspect, an embodiment of the present application provides a communication device, which may be a first execution node (such as the first execution node in the first aspect, the first execution node in the second aspect) or a chip disposed inside the first execution node, or a first network function (such as the first network function in the first aspect, the first network function in the second aspect) or a chip disposed inside the first network function. The communication device has the function of implementing any one of the above-mentioned first to second aspects. For example, the communication device includes a module or unit or means corresponding to the steps involved in any one of the above-mentioned first to second aspects. The function or unit or means may be implemented by software, or by hardware, or may be implemented by hardware executing the corresponding software.

[0038] In one possible design, the communication device includes a processing unit and a transceiver unit, wherein the transceiver unit can be used to send and receive signals to achieve communication between the communication device and other devices; the processing unit can be used to perform some internal operations of the communication device. The transceiver unit can be called an input / output unit, a communication unit, etc., and the transceiver unit can be a transceiver; the processing unit can be a processor. When the communication device is a module (such as a chip) in a communication device, the transceiver unit can be an input / output interface, an input / output circuit, or an input / output pin, etc., and can also be called an interface, a communication interface, or an interface circuit, etc.; the processing unit can be a processor, a processing circuit, or a logic circuit, etc.

[0039] In another possible design, the communication device includes a processor and may also include a transceiver, the transceiver is used to send and receive signals, and the processor executes program instructions to complete the method in any possible design or implementation of the first to second aspects above. The communication device may also include one or more memories, the memory is used to couple with the processor, and the memory can store the necessary computer programs or instructions for implementing the functions involved in any of the first to second aspects above. The processor can execute the computer program or instructions stored in the memory, and when the computer program or instructions are executed, the communication device implements the method in any possible design or implementation of the first to second aspects above.

[0040] In another possible design, the communication device includes a processor, which can be coupled to a memory. The memory can store the necessary computer programs or instructions for implementing the functions of any of the first and second aspects. The processor can execute the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the communication device implements the method of any possible design or implementation of the first and second aspects.

[0041] In another possible design, the communication device includes a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit and execute the method in any possible design or implementation of the first to second aspects above.

[0042] It can be understood that in the third aspect above, the processor can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. In addition, the above processors can be one or more, and the memories can be one or more. The memory can be integrated with the processor, or the memory and the processor can be set separately. In the specific implementation process, the memory can be integrated with the processor on the same chip, or can be set on different chips respectively. The embodiment of the present application does not limit the type of memory and the setting method of the memory and the processor.

[0043] In a fourth aspect, an embodiment of the present application provides a communication system, which includes a first execution node and a first network function, wherein the first execution node can be used to implement the method steps in the above-mentioned first aspect and each possible design, and the first network function can be used to implement the method steps in the above-mentioned second aspect and each possible design. In addition, the communication system may also include a second execution node.

[0044] In a fifth aspect, the present application provides a chip system, which includes a processor and may also include a memory, the memory being used to store program instructions, and the processor being used to call the program instructions to implement the method described in any possible design of the first to second aspects above. The chip system can be composed of a chip, or it can include a chip and other discrete devices. The memory and processor can be integrated into the chip system, or the memory can be deployed separately on other chip systems.

[0045] In a sixth aspect, the present application also provides a computer-readable storage medium, in which computer-readable instructions are stored. When the computer-readable instructions are run on a computer, the computer executes a method in any possible design of the first aspect to the second aspect.

[0046] In a seventh aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the methods of the various embodiments of the first to second aspects above.

[0047] For the technical effects that can be achieved in the above-mentioned second to seventh aspects, please refer to the description of the technical effects that can be achieved by the corresponding possible design schemes in the above-mentioned first aspect, and this application will not repeat them here. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] FIG1 shows a schematic diagram of a communication system;

[0049] FIG2 shows a flow chart of a communication method provided in an embodiment of the present application;

[0050] FIG2A shows a schematic diagram of an identification structure of an execution node provided in an embodiment of the present application;

[0051] FIG2B shows a schematic diagram of an identification structure of an execution node provided in an embodiment of the present application;

[0052] FIG3A shows a schematic flow chart of another communication method provided in an embodiment of the present application;

[0053] FIG3B shows a schematic diagram of an identification structure of an execution node provided in an embodiment of the present application;

[0054] FIG3C shows a schematic flow chart of another communication method provided in an embodiment of the present application;

[0055] FIG4 shows a flow chart of another communication method provided in an embodiment of the present application;

[0056] FIG5A shows a schematic flow chart of another communication method provided in an embodiment of the present application;

[0057] FIG5B shows a schematic diagram of an identification structure of an execution node provided in an embodiment of the present application;

[0058] FIG5C shows a schematic flow chart of another communication method provided in an embodiment of the present application;

[0059] FIG6 shows a flow chart of another communication method provided in an embodiment of the present application;

[0060] FIG6A shows a schematic diagram of an identification structure of an execution node provided in an embodiment of the present application;

[0061] FIG6B shows a schematic diagram of an identification structure of an execution node provided in an embodiment of the present application;

[0062] FIG7 shows a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0063] FIG8 shows a schematic structural diagram of another communication device provided in an embodiment of the present application;

[0064] FIG9 shows a schematic structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0065] In order to make the purpose, technical solutions and advantages of this application clearer, the present application will be further described in detail below with reference to the accompanying drawings. The specific operating methods in the method embodiments can also be applied to the device embodiments or system embodiments. In the description of this application, unless otherwise specified, "multiple" means two or more. Therefore, the implementation of the device and method can refer to each other, and the repeated parts will not be repeated.

[0066] The technical solutions provided in the embodiments of the present application can be applied to 5G systems, or to future communication systems or other similar communication systems. In addition, the technical solutions provided in the embodiments of the present application can be applied to cellular links, public land mobile networks (PLMN), machine to machine (M2M) networks, Internet of Things (IoT) networks or other networks. It can also be applied to links between devices, such as device to device (D2D) links. D2D links can also be called sidelinks, where sidelinks can also be called side links or side links, etc. In the embodiments of the present application, the above terms all refer to links established between devices of the same type, and their meanings are the same. The so-called devices of the same type can be links between terminal devices, links between base stations, links between relay nodes, etc., and the embodiments of the present application do not limit this. For links between devices, there are D2D links defined in Release (Rel) 12 / 13 of the Third Generation Partnership Project (3GPP), as well as V2X links defined for vehicle-to-vehicle, vehicle-to-mobile, or vehicle-to-any-entity connections in Releases 14 / 15. Also included are V2X links based on the New Radio (NR) system defined in Release 18 and later.

[0067] With reference to FIG1 , an application scenario applied in an embodiment of the present application, or a network architecture applied in an embodiment of the present application, is shown. FIG1 includes a network device and six terminal devices. It should be understood that the number of terminal devices in FIG1 is for example only, and may be more or less. The network architecture may also include other network devices, such as wireless relay devices and wireless backhaul devices, which are not shown in FIG1 . The network device is an access device for the terminal device to access the network through wireless access, and may be a base station. Among them, the network device corresponds to different devices in different systems, for example, in the fourth generation mobile communication technology (4th-generation, 4G) system, it may correspond to an evolutionary base station (eNB), and in the 5G system, it may correspond to a new generation base station (gNB); these six terminal devices may be cellular phones, smart phones, portable computers, handheld communication devices, handheld computing devices, satellite radio devices, global positioning systems, personal digital assistants (PDAs) and / or any other suitable devices for communicating on a wireless communication system, and may all be connected to the network device.

[0068] The embodiments of the present application can be applied to uplink signal transmission, downlink signal transmission, and D2D signal transmission. For downlink signal transmission, the transmitting device is a network device, and the corresponding receiving device is a terminal device; for uplink signal transmission, the transmitting device is a terminal device, and the corresponding receiving device is a network device; for D2D signal transmission, the transmitting device is a terminal device, and the corresponding receiving device is a terminal device. For example, the three terminal devices shown in the dashed area of ​​Figure 1 can be applied to D2D signal transmission. The embodiments of the present application do not limit the direction of signal transmission.

[0069] A terminal device may be a wireless terminal device capable of receiving network device scheduling and instruction information. A wireless terminal device may be a device that provides voice and / or data connectivity to a user, or a handheld device with wireless connection capabilities, or other processing devices connected to a wireless modem. A wireless terminal device may communicate with one or more core networks or the Internet via a radio access network (e.g., a radio access network, RAN). A wireless terminal device may be a mobile terminal device, such as a mobile phone (also known as a "cellular" phone, mobile phone), a computer, and a data card. For example, a mobile device may be portable, pocket-sized, handheld, built-in, or in-vehicle, and may exchange voice and / or data with a radio access network. Examples include personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, PDAs, tablet computers, and computers with wireless transceiver capabilities. A wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station (MS), a remote station, an access point (AP), a remote terminal, an access terminal, a user terminal, a user agent, a subscriber station (SS), a customer premises equipment (CPE), a terminal, a UE, a mobile terminal (MT), etc. A wireless terminal device may also be a wearable device and a next-generation communication system, for example, a terminal device in a 5G network or a terminal device in a future evolved public land mobile network (PLMN) network, a terminal device in an NR communication system, etc.

[0070] A network device is an entity on the network side that transmits or receives signals, such as a transmission reception point (TRP) or gNB. A network device can be a device used to communicate with mobile devices. A network device can be an access point (AP) in a wireless local area network (WLAN), a base transceiver station (BTS) in a global system for mobile communication (GSM) or code division multiple access (CDMA), a base station (NodeB) in wideband code division multiple access (WCDMA), an evolutionary Node B (eNB) or eNodeB in long-term evolution (LTE), a relay station or access point, or a network device in an in-vehicle device, wearable device, future 5G network, or future evolved PLMN, or a gNodeB / gNB in ​​a NR system. In some deployments, a gNB can include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some gNB functions, while the DU implements some gNB functions. For example, the CU is responsible for processing non-real-time protocols and services, such as radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP). The DU is responsible for processing physical layer protocols and real-time services, such as radio link control (RLC), medium access control (MAC), and physical (PHY) layer functions. The AAU implements some physical layer processing functions, RF processing, and active antenna-related functions. Because RRC layer information ultimately becomes PHY layer information, or is converted from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can be considered to be sent by the DU, or by both the DU and the AAU.It can be understood that the network device can be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU can be divided into a network device in an access network (radio access network, RAN), or the CU can be divided into a network device in a core network (core network, CN), and this application does not limit this. In addition, in an embodiment of the present application, the network device provides services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to a network device (for example, a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell. The small cell here may include: a metro cell, a micro cell, a pico cell, a femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services. In addition, in other possible cases, the network device may be other devices that provide wireless communication functions for terminal devices. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device. For the convenience of description, in the embodiment of the present application, the device that provides wireless communication function for the terminal device is called a network device.

[0071] When the aforementioned communication system performs connected services, it typically needs to know the identities of both communicating parties to ensure communication security. However, when the aforementioned communication system performs non-connected services, the service requester may not care about the specific identity of the service execution node, but only needs to obtain the execution results of the service. Non-connected services may include task services, perception services, computing services, data services, trusted services, and AI services. Non-connected services can be referred to as new services. Task services can refer to network services that implement resource coordination and service QoS assurance for multiple types of resources and multiple communication nodes in the form of "tasks." Communication networks have evolved from a single dimension of connection services to a new service dimension that encapsulates and provides connectivity, computing, data, intelligence, and trust in the form of tasks. This ensures service level agreements (SLAs) for various AI, perception, computing, and data services, further expanding the application scenarios of communication networks. Perception services can refer to services that can provide perception capabilities provided by nodes in the network infrastructure. For example, a base station can perceive and image objects near the base station using high-frequency signals and then identify the objects using algorithms based on the imaged content. Alternatively, the network can perceive user data traffic flows and analyze the user's behavior patterns using data packets. Computing services refer to nodes in the network infrastructure that, in addition to providing basic connectivity services, can also provide additional computing capabilities, enabling a deep integration of communication and computing. For example, these services can sense and calculate the status of communication resources in real time, and coordinate the control of communication and computing resources to meet end-to-end QoS requirements such as ultra-low latency, data security protection, and sustainable energy conservation in dynamic and complex wireless network environments. Data services aim to provide data as a service, and may include, for example, raw data collection or acquisition, data preprocessing, data storage, data privacy and security protection, data sharing or trading, data traceability, data analysis, and data dictionaries. Trusted services provide trusted functions as services, and may include blockchain services, remote attestation services, and privacy protection services. AI services can perform AI training or inference within the network, providing intelligent capabilities adapted to different application scenarios.

[0072] Here, we take the example of rendering an oil painting, a non-connected service corresponding to an AI service, as an example. The service requester (AF) only wants to obtain the final rendered oil painting and does not care which specific device performs the operation. However, based on the communication process of executing a connected service, the true identity of the device performing the operation needs to be reported, which is obviously not conducive to ensuring the identity security of the device performing the operation. Based on this, this application provides a communication method to ensure the identity security between execution nodes when executing non-connected services.

[0073] As shown in Figure 2, a communication method is provided by the present application. Figure 2 takes the first network function, the first execution node and the second execution node as examples for illustration. Of course, in actual application, the number of the above-mentioned execution nodes is not limited. Among them, the first network function can be a network entity, or a logical function (deployed together with other network functions), or a piece of code or script, or a chip or processor in the network entity. This application does not specifically limit this. In actual application, the first network function can be a management network element of the execution node (usually maintains the identity information of the execution node and the capability information of the execution node, and can assign an identifier to the execution node); it can also be a scheduling / management network element for non-connected services (usually obtains information about non-connected services, and can assign an identifier to the execution node). The execution node can be a terminal, an access network device, a core network device, etc. It can also be a chip or processor in a terminal, an access network device, a core network device, etc. This application does not specifically limit this and can be determined in combination with actual needs. Execution is as follows:

[0074] Step 201: A first network function determines at least one execution node for executing a first service.

[0075] For example, the first service may be a connection service, and the execution node may use the temporary identity mentioned below in this application to exchange data of the first service when executing the connection service. The first service may also be a non-connection service, which is not specifically limited in this application.

[0076] In an optional implementation, the first network function may be a management network element of an execution node. Before executing step 201, the first network function may receive a request message sent by a second network function (a scheduling / management network element or other network element for a non-connected service). The request message is sent by the second network function after obtaining information about the first service. The request message is used to request at least one execution node for executing the first service. The first network function may then determine the at least one execution node for executing the first service based on the request message.

[0077] Of course, in another optional embodiment, the first network function may also be a scheduling / management network element for a non-connected service. After obtaining information about the first service, the first network function may determine at least one execution node for executing the first service. Specifically, it may send a request message to the management network element of the execution node, requesting at least one execution node for executing the first service through the request message, and the management network element of the execution node feedbacks the at least one execution node for executing the first service, thereby determining the at least one execution node for executing the first service. Of course, the first network function may also integrate the functions of the management network element of the execution node and the functions of the scheduling / management network element for non-connected services. In this case, the first network function itself maintains information about at least one execution node for executing the first service, and the first network function can directly obtain at least one execution node for executing the first service. This application does not specifically limit the specific manner in which the first network function determines at least one execution node for executing the first service.

[0078] Step 202: The first network function assigns an identifier to at least one execution node.

[0079] The identifier of the first execution node is used to identify a temporary identity of the first execution node when executing the first service. The first execution node is any one of the at least one execution node.

[0080] In addition, before the first network function assigns an identifier to at least one execution node, the first network function may receive a capability registration request message from at least one execution node, wherein the capability registration request message includes: identity information of at least one execution node (wherein the identity information of the execution node may be indicated by the terminal identifier UE ID, the base station identifier cell ID, the instance identifier of the network function, etc.) and capability information of at least one execution node; the first network function sends a response message indicating successful capability registration to at least one execution node (of course, in actual application, registration may fail, but based on the solution of the present application, only after the execution node capability registration is successful can the first network function obtain the identity information and capability information of the execution node and assign an identifier to the execution node). Then, the first network function may assign an identifier to at least one execution node based on the identity information of at least one execution node and / or the capability information of at least one execution node; the capability information of at least one execution node includes one or more of the following information:

[0081] Service type information supported by at least one execution node, type of at least one execution node, communication interface type information supported by at least one execution node (such as Uu interface, PC5 interface, non-3GPP interface, WIFI interface, etc.), selection priority information of the communication interface when at least one execution node supports multiple communication interface types, service level information supported by at least one execution node, physical address information of at least one execution node (such as IP address, MAC address, etc.), application identifier, and identity identifier of at least one execution node in the application; the application is an application that provides services to at least one execution node.

[0082] Among them, the service type information supported by the execution node, such as perception services, computing services, data services, etc., can be indicated by a service identifier, such as a Service ID. If the first network function has been categorized by service (for example, specifically responsible for executing perception services), then the execution node can simply register with the first network function corresponding to the service to determine which service it supports. The capabilities supported by the execution node are determined during registration, so the service types supported by the execution node may not be carried. The execution node type, such as terminal type (mobile phone, computing server, etc.), base station, core network network function, etc., may be omitted if the execution node's identity information can reveal the execution node's type. For example, if the execution node's identity information is a SUPI (subscription permanent identifier), IMSI (international mobile subscriber identity), or SUCI (subscription concealed identifier), the execution node can be determined to be a terminal. If the identity information is an NF instance ID, the execution node can be determined to be a core network NF. If it is a Cell ID or RAN ID, the execution node can be determined to be a base station. The service levels supported by the execution node, such as perception accuracy (such as the range of the perception area, the range of perceptible angles, etc.), the upper limit of computing resources (such as the processing power of the central processing unit (CPU), the number of CPUs, etc.), the upper limit of storage resources (such as the amount of storage data that can be provided), etc. When the execution node supports multiple communication interface types, the communication interface selection priority information is as follows: for example, the execution node supports PC5 interface, Uu interface, and non-3GPP interface, among which PC5 interface has the highest priority, Uu interface has the second highest priority, and non-3GPP interface has the lowest priority. Then, when communicating between execution nodes, the PC5 interface can be selected for communication based on the communication interface priority information. The identification of the application (such as the identification of the instant messaging application, the identification of the video application) and the identity of the execution node in the application (such as the account of the execution node in the instant messaging application, the account of the execution node in the video application).

[0083] When executing step 202, the first network function may assign an identifier to at least one execution node based on the identity information of at least one execution node. For example, if the first network function assigns an identifier TB1 to the terminal, the identifier assigned by the first network function can be used when executing the first service regardless of how the terminal moves. Alternatively, the first network function may also assign an identifier to at least one execution node based on the capability information of at least one execution node and the identity information of at least one execution node. For example, the first network function may also write partial capability information of the execution node into the identification field of the execution node based on the capability information of the execution node. The temporary identifier of at least one execution node may include one or more of the following information:

[0084] The network identifier of at least one execution node (such as a PLMN ID), the network function identifier that assigns the identifier to at least one execution node (such as the identifier of the management network element of the execution node, the identifier of the scheduling / management network element of the non-connected service), the communication interface type information supported by at least one execution node (such as a Uu interface, a PC5 interface, a non-3GPP interface, a WIFI interface, etc.), the type of at least one execution node (such as a terminal, an access network device, a network function of the core network, etc.), the identifier of the service executed by at least one execution node (such as a connection service, the service identifier or service information of the connection service, such as slice information, DNN (data network name) information, etc.; if it is a computing service, it can be the service identifier of the computing service), the type of service executed by at least one execution node (such as a computing service, a data service, a perception service, etc.), and the application identifier (such as an instant messaging application identifier, a video application identifier).

[0085] The identifier of the execution node may be a string, or a string consisting of multiple parameters or characters with specific meanings. For example, if PLMN ID = 123, temp ID (a temporary unique identifier of the execution node within the network function that assigns the identifier to the execution node, used to uniquely determine the identity of the execution node within the NF) = 456, then the identifier of the execution node is 123456.

[0086] Of course, the execution node does not carry capability information when registering capabilities, and the execution node identifier usually does not carry capability information. For example, if the execution node does not carry the execution node type when registering capabilities, the execution node identifier usually does not include the execution node type.

[0087] From this, it can be seen that the first network function can assign a temporary identifier to the node based on the identity information of the execution node, and can also assign a temporary identifier to the execution node based on the capability information of the execution node and the identity information of the execution node. Regardless of which of the above methods is used to determine the temporary identifier of the execution node, it can be ensured that when data is exchanged between execution nodes, the real identity information is not obtained, but the assigned temporary identity identifier is used for communication, thereby ensuring the security of the identity information of the execution node.

[0088] In addition, by carrying the network identifier described by the execution node, the network function identifier assigned to the execution node, etc. in the identifier of the execution node, it is convenient for the execution node to apply for corresponding communication resources, such as communication frequency bands, etc. In addition, if the first execution node and the second execution node are not from the same operator, there may be roaming problems. The network function of the corresponding operator can be determined based on the network identifier described by the execution node, the network function identifier assigned to the execution node, etc.

[0089] For example, referring to FIG2A , which is a schematic diagram of a data structure for a temporary identifier assigned to an execution node, the temporary identifier assigned to the execution node is at the user or device granularity, that is, each execution node identifier corresponds to a device identifier, that is, a one-to-one correspondence with the actual identity of the execution node. The identifier of the execution node may include: the network identifier PLMN ID to which the execution node belongs, the network function identifier NF ID to which the execution node identifier is assigned, the temporary unique identifier temp ID of the execution node within the network function to which the identifier is assigned (hereinafter, the temp ID can be understood with reference to this and will not be repeated below), the identifier of the service executed by the execution node, the type of service executed by the execution node, the type of communication interface supported by the execution node, and the type of the execution node. The information indicated by the dotted box in FIG2A is optional, and the information indicated by the solid box is mandatory.

[0090] For example, referring to FIG2B , which is a schematic diagram of another data structure for a temporary identifier assigned to an execution node, the temporary identifier of the execution node is service-granular, meaning that multiple execution nodes can correspond to the same identifier, i.e., corresponding to a specific service. Multiple execution nodes executing a specific service use the same identifier. The identifier of the execution node may include: the PLMN ID of the network to which the execution node belongs, the NF ID of the network function that assigns the identifier to the execution node, the identifier of the service executed by the execution node, the type of service executed by the execution node, information about the communication interface types supported by the execution node, and the type of the execution node. The difference from FIG2A is that the identifier of the execution node in FIG2B does not need to carry the temp ID, but carries the identifier of the service executed by the execution node. In FIG2A , the identifier of the execution node carries the temp ID, but the identifier of the service executed by the execution node is optional. The information indicated by the dashed box in FIG2B is optional, while the information indicated by the solid box is mandatory.

[0091] In practical applications, when executing a non-connected service, the service data exchanged between participating execution nodes includes header information and data information. The header information indicates the identity information of the execution node, and the data information refers to the specific content of the exchange between the different execution nodes. The header information may include a temporary identifier assigned to the execution node for executing the non-connected service.

[0092] The first network function may then send an identifier corresponding to at least one execution node to the first execution node. The at least one execution node includes a first execution node and a second execution node, and the second execution node is an execution node other than the first execution node in the at least one execution node. The identifier of the second execution node is used to identify the temporary identity of the second execution node when executing the first service. The first execution node transmits data for the first service to the second execution node based on the identifiers of the first execution node and the second execution node. In Figure 2, the first execution node and the second execution node are used as an example for explanation. For details, refer to steps 203A and 203B.

[0093] Step 203A: The first network function sends the identifier of the first execution node and the identifier of the second execution node to the first execution node.

[0094] Step 203B: The first network function sends the identifier of the first execution node and the identifier of the second execution node to the second execution node.

[0095] Accordingly, the first execution node and the second execution node obtain identifiers of corresponding execution nodes.

[0096] Step 204: The first execution node transmits the data of the first service to the second execution node based on the identifier of the first execution node and the identifier of the second execution node.

[0097] Specifically, the first execution node can obtain the data of the first business after executing the first business. The first execution node can send the data of the first business to other execution nodes so that the other execution nodes know that the first execution node has completed the execution of the first business. The other execution nodes can directly use the data of the first business to execute the first business, or they can execute other businesses based on the data of the first business. This application is not specifically limited here. For example, if the first business is a business corresponding to an AI service, the data of the first business can be the AI ​​model data involved in the task service, such as AI training results, model gradients, etc.; if the first business is a business corresponding to a computing service, the data of the first business can be data that has been processed by computing, such as encrypted computing. data, compressed or decompressed data, rendered video data, etc.; if the first business is a business corresponding to a data service, the data of the first business may be data processed data or raw data, data processing may refer to preprocessing of the collected data (such as data screening, deduplication, compression, etc.), and the raw data may be data collected by a sensor or raw data stored by a user; if the first business is a business corresponding to a perception service, the data of the first business may be raw data collected by a sensor, or perception data that has been optimized, etc.; if the first business is a business corresponding to a task service, the data of the first business may be algorithm model data, calculation data, etc. in the task execution process.

[0098] In addition, the first network function determines configuration information for the first service based on the information about the first service and the identifier of at least one execution node. The configuration information for the first service includes connection parameters required for transmitting data for the first service. The first network function then sends the configuration information for the first service to the first execution node. Accordingly, the first execution node obtains the configuration information for the first service. Specifically, when executing step 204, the first execution node transmits the data for the first service to the second execution node based on the identifier of the first execution node, the identifier of the second execution node, and the connection parameters. By using the connection parameters to transmit data to the second execution node, the first execution node simplifies the process of obtaining information about the communication interfaces supported by the second execution node and determining which communication interface to select for transmitting data to the second execution node, thereby improving data processing efficiency.

[0099] Of course, in actual application, the configuration information of the first service may also come from other network functions, or may be stored by the first execution node itself after executing the first service at a certain point in time. This application does not specifically limit this.

[0100] It should be understood that the connection parameters required for transmitting the data of the first service may include indication information of the communication interface for transmitting the data of the first service, indication information of the time for transmitting the data of the first service (for example, a specific time or timing), indication information of the manner of transmitting the data of the first service (for example, carrying the service information of the first service when transmitting the data of the first service), session parameter information used for transmitting the data of the first service (for example, DNN and / or slice information corresponding to the session, session and service continuity mode (SSC mode, Session and Service Continuity mode), QoS information, etc.), etc., which are not specifically limited in this application.

[0101] Optionally, the connection parameters may include first indication information, where the first indication information indicates the type of communication interface used by the first execution node to transmit data for the first service. Therefore, when executing step 204, the first execution node, based on the identifier of the first execution node and the identifier of the second execution node, uses the communication interface type indicated by the first indication information to transmit the data for the first service to the second execution node. There are various types of communication interfaces, such as a Uu interface, a PC5 interface, a non-3GPP interface, and a Wi-Fi interface. The communication interface type indicated by the first indication information is a communication interface type supported by both the first execution node and the second execution node.

[0102] Since the scheduling / management network element of the non-connected service obtains the configuration information of the non-connected service (i.e., the configuration information of the first service), the above-mentioned first indication information may be sent by the scheduling / management network element of the non-connected service. The scheduling / management network element of the non-connected service may request the management network element of the execution node with which the execution node capability information is registered for information on the communication interface types supported by each execution node, and then determine which communication interface the first execution node uses to transmit data of the first service based on the specific circumstances of the first service. For example, the scheduling / management network element of the non-connected service learns from the management network element of the execution node that the communication interface types supported by the first execution node are PC5 interface, non-3GPP interface, and WIFI interface, and the communication interface types supported by the second execution node are PC5 interface and WIFI interface. Since the data of the first service involves private data and WIFI transmission has lower security, to prevent data leakage, the scheduling / management network element of the non-connected service may use the PC5 interface to transmit the data of the first service as the first indication information. Then, the first execution node may use the PC5 interface to transmit the data of the first service to the second execution node.

[0103] In this application, the first execution node uses the communication interface indicated by the first indication information to transmit data to the second execution node, which simplifies the processing flow of obtaining the communication interface information supported by the second execution node and determining which communication interface to select to transmit data to the second execution node, thereby improving data processing efficiency.

[0104] Optionally, the above-mentioned connection parameters may also include second indication information, and the second indication information is used to indicate the communication interface type information supported by the second execution node; then when executing step 204, the first execution node determines the communication interface for exchanging data between the first execution node and the second execution node based on the communication interface type information supported by the first execution node and the second indication information; the first execution node uses the communication interface to transmit the data of the first service to the second execution node based on the identifier of the first execution node and the identifier of the second execution node.

[0105] Since the scheduling / management network element of the non-connected service obtains the configuration information of the non-connected service (i.e., the configuration information of the first service), the above-mentioned second indication information can be sent by the scheduling / management network element of the non-connected service. The scheduling / management network element of the non-connected service can request the management network element of the execution node with which the execution node capability information is registered for the communication interface type information supported by each execution node, and then send the communication interface type information supported by each execution node as indication information to the corresponding execution node. For example, the scheduling / management network element of the non-connected service learns from the management network element of the execution node that the communication interface types supported by the second execution node are PC5 interface, non-3GPP interface, and WIFI interface. The scheduling / management network element of the non-connected service can use the communication interface type supported by the second execution node as the second indication information. Then, based on the communication interface types supported by itself, the first execution node can select a communication interface adapted to the second execution node to transmit data of the first service to the second execution node.

[0106] In the present application, the first execution node determines the communication interface type information supported by the second execution node based on the second indication information. When the first execution node transmits data to the second execution node, the communication interface adapted to the second execution node is selected based on the second indication information to transmit the data of the first service to the second execution node. This method simplifies the processing flow of obtaining the communication interface information supported by the second execution node and determining which communication interface to select to transmit data to the second execution node, thereby improving data processing efficiency.

[0107] In the present application, the first execution node does not need to obtain the real identity information of the second execution node. It exchanges the data of the first business with the second execution node having a temporary identifier associated with the first business based on the temporary identifier associated with the first business. This method can ensure the security of the identity information of each execution node when the data of the first business is exchanged between the execution nodes, and reduces the process of obtaining the identity information of each execution node when exchanging data, thereby further improving data processing efficiency.

[0108] In addition, it should be noted that if the identifier of the above-mentioned second execution node includes information related to the capabilities of the second execution node (the network identifier to which the second execution node belongs, the network function identifier for assigning the identifier to the second execution node, the communication interface type information supported by the second execution node, the type of the second execution node, the identifier of the service executed by the second execution node, the type of service executed by the second execution node, and the identifier of the application), the first execution node and the second execution node can directly exchange data of the first service based on the identifier of the first execution node and the identifier of the second execution node. However, if the identifier of the above-mentioned second execution node does not include information related to the capabilities of the second execution node, then the information related to the capabilities of the second execution node can be configured in the configuration information of the first service. In this way, the network information to which the second execution node belongs can be known, which facilitates the application of corresponding communication resources, such as communication frequency bands, etc. In addition, if the first execution node and the second execution node are not from the same operator, there may be roaming problems, and the network functions of the corresponding operator can be determined based on the above-mentioned information.

[0109] In addition, in step 202 above, the identifier of the execution node mentioned may be allocated by different network functions. The following will be explained in combination with different situations. The following will be explained using any execution node as an example. Any execution node can be the first execution node or the second execution node mentioned above, and is not specifically limited.

[0110] Case 1: The identifier of the execution node is assigned by the management network element of the execution node

[0111] Typically, after receiving the capability registration request message of the execution node, the management network element of the execution node may allocate an identifier to the execution node based on the identity information of the execution node in the capability registration request message. Alternatively, the management network element of the execution node may allocate an identifier to the execution node after receiving a request message to execute the first service from the scheduling / management network element of the non-connected service. This is not specifically limited in this application. Referring to FIG3A , the management network element of the execution node, the scheduling / management network element of the non-connected service, the execution node, and the direct discovery function management parameters are used as an example for explanation. The execution is as follows:

[0112] Step A301: The execution node sends a capability registration request message to the management network element of the execution node.

[0113] The information in the capability registration request message may be understood by referring to the description of step 202 in FIG. 2 , which will not be described in detail here.

[0114] [Corrected 07.03.2024 according to Rule 91] Specifically, the management network element of the execution node may refer to step A302a or step A302b to allocate an identifier (i.e., a temporary identifier) ​​to the execution node:

[0115] In step A302a, the management network element of the execution node allocates an identifier to the execution node according to the identity information of the execution node.

[0116] Step A302b: The management network element of the execution node allocates an identifier to the execution node according to the identity information and capability information of the execution node.

[0117] In the above step A302a, the management network element of the execution node can directly assign an identifier to the execution node based on the identity information of the execution node. For example, if the management network element of the execution node assigns the identifier TB1 to the terminal, the identifier of the execution node can remain unchanged when executing a specific service regardless of how the terminal moves.

[0118] In the above step A302b, the management network element of the execution node may further write part of the capability information of the execution node into the identification field of the execution node based on the capability information of the execution node.

[0119] Since the management network element of the execution node in steps A302a and A302b has not yet obtained the service information, the identification of the execution node can be constructed with reference to Figure 3B. The identification of the execution node constructed in Figure 3B can execute different services. For example, the execution node uses the same identification to execute perception services, AI services, etc. The identification of the execution node is user or device granularity, that is, each execution node identification corresponds to a device identification, that is, one-to-one correspondence with the real identity of the execution node. The identification of the execution node may include: the network identification PLMN ID to which the execution node belongs, the network function identification NF ID that assigns the identification to the execution node, the temp ID, the communication interface type information supported by the execution node, and the type of the execution node. The information indicated by the dotted box in Figure 3B is optional, and the information indicated by the solid box is required.

[0120] For details, please refer to step 202 above to understand the specific information in the execution node identifier.

[0121] Step A303: The management network element of the execution node sends a response message indicating successful capability registration to the execution node.

[0122] The response message may carry an identifier allocated to the execution node by the management network element of the execution node.

[0123] In this application, the management network element of the execution node assigns an identifier to the execution node so that the execution nodes can transmit data of the first service based on the assigned identifier. This method can ensure the security of the identity information of each execution node when exchanging data between the execution nodes.

[0124] Step A304: The scheduling / management network element of the non-connected service triggers execution of the first service.

[0125] The above-mentioned step A304 may be triggered after receiving the instruction information for executing the first service, or may be determined autonomously. For example, the scheduling / management network element of the non-connected service receives a request trigger for executing the first service from a third-party application server or other network function or UE. Specifically, for example, if the third-party application service needs to perceive and track drones in a certain geographical area, the third-party server can initiate a request for perception service to the scheduling / management network element of the non-connected service, thereby triggering the scheduling / management network element of the non-connected service to request the management network element of the execution node for information on the execution node that can execute the perception service. Autonomous determination can be that the scheduling / management network element of the non-connected service itself needs to execute a certain service, for example, the scheduling / management network element of the non-connected service needs to analyze and predict certain data, then the scheduling / management network element of the non-connected service can request the management network element of the execution node for information on the execution node that can perform data analysis.

[0126] Step A305: The scheduling / management network element of the non-connected service sends a request message to the management network element of the execution node, where the request message is used to request at least one execution node to execute the first service.

[0127] Step A306: The management network element of the execution node determines at least one execution node for executing the first service.

[0128] Of course, if the execution node executing the first business is a terminal and the execution node is in an idle state, then steps A307-A308 can also be executed after step A306. Figure 3A takes the execution node as a terminal as an example for illustration, but in actual application, if the execution node is not a terminal, steps A307-A308 may not be executed.

[0129] Step A307: The management network element of the execution node pages the execution node for executing the first service.

[0130] The management network element of the execution node may page the terminal by calling a network function that provides a terminal paging function.

[0131] Step A308: The execution node for executing the first service receives the paging, changes from the idle state to the connected state, and feeds back a service request to the management network element of the execution node.

[0132] Step A309: The management network element of the execution node sends the identifier of at least one execution node for executing the first service to the scheduling / management network element of the non-connected service.

[0133] In addition, if the execution node fails to receive the paging successfully, in step A309, the management network element of the execution node does not need to feed back the identifier of the terminal that failed the paging to the scheduling / management network element of the non-connected service, because the terminal that failed the paging cannot execute the first service.

[0134] If the execution node for executing the first service supports PC5 communication, steps A310-A311 may be executed. FIG3A illustrates the example of the execution node for the first service supporting PC5 communication. However, in actual applications, if the execution node does not support PC5 communication, steps A310-A311 may not be executed.

[0135] Step A310: The scheduling / management network element of the connectionless service requests the direct discovery parameter management function for the discovery parameters used to execute the node to communicate using PC5.

[0136] Specifically, when an execution node needs to use the PC5 interface for communication, the execution node needs to obtain discovery parameters from the direct discovery management function, then find other execution nodes by broadcasting the discovery parameters, establish a PC5 connection, and then transmit data through the PC5 interface.

[0137] Step A311 : The direct discovery parameter management function sends discovery parameters for executing the node to communicate using PC5 to the scheduling / management network element of the non-connected service.

[0138] Step A312: The scheduling / management network element of the non-connected service sends configuration information of the first service to at least one execution node used to execute the first service.

[0139] The configuration information for the first service may include connection parameters required for transmitting data for the first service, which can be understood with reference to the above. Furthermore, if the identifier of the execution node is determined in step A302a, the configuration information for the first service may also include one or more of the following information: an identifier of the network to which the execution node belongs, an identifier of the network function that assigns the identifier to the execution node, information on the types of communication interfaces supported by the execution node, the type of the execution node, an identifier of the service executed by the execution node, and the type of service executed by the execution node.

[0140] If the identification of the execution node is determined in step A302b, the configuration information of the first service may not carry the above information. In addition, in step A312, the configuration information of the first service may also carry the discovery parameters of the execution node using PC5 communication.

[0141] Step A313: The execution node exchanges data of the first service with other execution nodes (the other execution nodes are other execution nodes for executing the first service) based on the identification of the execution node and the configuration information of the first service.

[0142] Step A313 is the data interaction process between the first execution node and the second execution node in FIG. 2 . Step A313 can be understood by referring to the relevant steps in FIG. 2 , and will not be described in detail here.

[0143] Step A314: The execution node feeds back the execution result to the scheduling / management network element of the connectionless service.

[0144] It should be understood that only after all execution nodes used to execute the first business have completed the execution of the first business will any execution node feedback the execution result. For example, the first business is rendering an oil painting. The oil painting includes 5 parts. There are 3 execution nodes that can be used to execute the rendering oil painting business, namely execution node 1, execution node 2 and execution node 3. After execution node 1 renders the first part of the oil painting, it sends the rendered oil painting and the used network model and model parameters to execution node 2. After execution node 2 renders the second and third parts of the oil painting, it sends the rendered oil painting and the used network model and model parameters to execution node 3. Execution node 3 renders the fourth and fifth parts of the oil painting to obtain the finished oil painting, and sends the rendered oil painting (that is, the execution result) to the scheduling / management network element of the non-connected service. This is only an illustrative description and does not limit the specific process of the execution node executing the first business.

[0145] The identifier of the execution node in Figure 3A above is assigned to the execution node by the management network element of the execution node after the execution node sends a registration request message to the management network element of the execution node. However, in actual application, the management network element of the execution node can also assign an identifier to the execution node after the scheduling / management network element of the non-connected service triggers the execution of the first service and receives a request message from the scheduling / management network element of the non-connected service. Specifically, it can be executed with reference to Figure 3C, where the execution node used to execute the first service is not a terminal and the execution node does not support PC5 communication. Referring to Figure 3C, taking the management network element of the execution node, the scheduling / management network element of the non-connected service, the execution node, and the direct discovery function management parameters as an example, the execution is as follows:

[0146] Step C301: The execution node sends a capability registration request message to the management network element of the execution node.

[0147] The information in the capability registration request message may be understood by referring to the description of step 202 above, which will not be described in detail here.

[0148] Step C302: The management network element of the execution node sends a response message indicating successful capability registration to the execution node.

[0149] Step C303: The scheduling / management network element of the non-connected service triggers the execution of the first service. This can be understood by referring to step A304 in FIG3A , and will not be described in detail here.

[0150] Step C304: The scheduling / management network element of the non-connected service sends a request message to the management network element of the execution node, where the request message is used to request at least one execution node to execute the first service.

[0151] Step C305: The management network element of the execution node determines at least one execution node for executing the first service.

[0152] After executing step C305, the management network element of the execution node may refer to step C306a or step C306b to allocate an identifier (ie, a temporary identifier) ​​to the execution node:

[0153] In step C306a, the management network element of the execution node allocates an identifier to at least one execution node according to the identity information of the at least one execution node.

[0154] Step C306b: The management network element of the execution node allocates an identifier to the at least one execution node according to the identity information of the at least one execution node and the capability information of the at least one execution node.

[0155] How to assign identifiers can be understood with reference to step 202 of FIG. 2 , which will not be described in detail here. When assigning identifiers to execution nodes using step C306b , the structure of the execution node identifiers can be understood with reference to FIG. 2A , FIG. 2B or FIG. 3B .

[0156] Step C307: The management network element of the execution node sends the identifier of at least one execution node for executing the first service to the scheduling / management network element of the non-connected service.

[0157] When the execution node needs to use the PC5 interface to communicate with other execution nodes, the following steps C309-C310 can be executed.

[0158] In step C308 , the execution node requests the direct discovery parameter management function for discovery parameters used by the execution node to communicate using PC5.

[0159] Step C309 : The direct discovery parameter management function sends the discovery parameters used by the execution node to communicate using PC5 to the execution node.

[0160] Step C310: The scheduling / management network element of the non-connected service sends configuration information of the first service to at least one execution node for executing the first service.

[0161] In addition, in step C310, the configuration information of the first service may also carry discovery parameters for the execution node to adopt PC5 communication.

[0162] In step C311 , the execution node exchanges data of the first service with other execution nodes (the other execution nodes are other execution nodes for executing the first service) based on the identifier of the execution node and the configuration information of the first service.

[0163] Step C311 is the data interaction process between the first execution node and the second execution node in FIG2 . Step C311 can be understood by referring to the relevant steps in FIG2 , and will not be described in detail here.

[0164] In step C312, the execution node feeds back the execution result to the scheduling / management network element of the non-connected service. This can be understood by referring to step A314 in FIG3A above, and will not be described in detail here.

[0165] In step A302a and step A302b of FIG3A above, the management network element of the execution node will allocate an identifier for the execution node that registers the capability. The allocated identifier is not specific to the service, and the same identifier can be used even if the execution node executes different services. The identifier allocated in this way can also be used to identify the temporary identity when executing the second service (service other than the first service). The same identifier can be allocated to the execution node for different services, that is, the identifier of the execution node can be decoupled from the service, and this method can adapt to the needs of more business scenarios. In step C306a and step C306b of FIG3C above, the management network element of the execution node allocates an identifier for the execution node that executes the first service. Not every execution node that registers the capability will be allocated an identifier. Since the management network element of the execution node receives a request from the scheduling / management network element of the non-connected service, the management network element of the execution node can allocate an identifier to the execution node based on the first service when allocating the identifier, which can be more adapted to the needs of the first service.

[0166] Case 2: Scheduling / management network element allocation for non-connected services when the execution node is identified

[0167] Typically, the scheduling / management network element of a non-connected service obtains service information of a service, obtains the execution node that executes the service, and then assigns an identifier to the execution node. This application does not specifically limit this. Referring to Figure 4, the management network element of the execution node, the scheduling / management network element of the non-connected service, the execution node, and the direct discovery function management parameters are used as an example to illustrate the following:

[0168] Step 401: The execution node sends a capability registration request message to the management network element of the execution node. The information in the capability registration request message can be understood by referring to the description of step 202 in FIG. 2 , which will not be described here in detail.

[0169] Step 402: The management network element of the execution node sends a response message indicating successful capability registration to the execution node.

[0170] Step 403: The scheduling / management network element of the non-connected service triggers execution of the first service.

[0171] Step 404: After obtaining information about the first service, the scheduling / management network element of the non-connected service sends a request message to the management network element of the execution node, where the request message is used to request at least one execution node to execute the first service.

[0172] Step 405: The management network element of the execution node determines at least one execution node for executing the first service.

[0173] After receiving the capability registration request message of the execution node, the management network element of the execution node maintains the capability information of the execution node. Therefore, the management network element of the execution node can learn which execution nodes can execute the first service.

[0174] If the management network element of the execution node determines that the execution node executing the first service is a terminal and the execution node is in an idle state, steps 406 and 407 may be further executed. After the execution node successfully receives the paging message, the execution node that successfully received the paging message may be included in step 408. If the paging message fails, the execution node that failed to receive the paging message is not included. FIG4 illustrates this by taking the execution node as a terminal as an example.

[0175] Step 406: The management network element of the execution node pages at least one execution node for executing the first service.

[0176] Step 407: The execution node for executing the first service receives the paging, changes from the idle state to the connected state, and feeds back a service request reception to the management network element of the execution node.

[0177] Step 408: The management network element of the execution node sends a response message to the scheduling / management network element of the non-connected service, wherein the response message includes information about at least one execution node executing the first service.

[0178] After executing step 408, the scheduling / management network element of the non-connected service may obtain information of the execution node according to the response message. Specifically, the following steps may be referred to:

[0179] If the response information includes the identity information of the execution node and the capability information of the execution node, step 409A or step 409B may be executed:

[0180] Step 409A: The scheduling / management network element of the non-connected service allocates an identifier to at least one execution node according to the identity information of at least one execution node.

[0181] Step 409B: The scheduling / management network element of the non-connected service allocates an identifier to the at least one execution node according to the capability information and identity information of the at least one execution node.

[0182] Either step 409A or step 409B can be performed. Furthermore, since the scheduling / management network element for the non-connected service obtains service information for the first service, the scheduling / management network element for the non-connected service can assign an identifier to the execution node based on service granularity. The identifier of the execution node includes the identifier of the service executed by the execution node and the type of service executed by the execution node. This allows the scheduling / management network element for the non-connected service to assign an identifier to the execution node based on the service. This allows the same identifier to be used when executing the same service on different execution nodes. This means that the identifier of the first execution node can also be used to identify the identity of the second execution node when executing the first service. The second execution node is another execution node that executes the first service.

[0183] If the execution node for executing the first service supports PC5 communication, steps 410 and 411 may be executed.

[0184] Step 410: The scheduling / management network element of the connectionless service requests the direct discovery parameter management function for the discovery parameters used to execute the node to communicate using PC5.

[0185] Step 411 : The direct discovery parameter management function sends discovery parameters for executing the node to communicate using PC5 to the scheduling / management network element of the non-connected service.

[0186] Step 412: The scheduling / management network element of the non-connected service sends configuration information of the first service to at least one execution node for executing the first service.

[0187] Step 413: The execution node exchanges data of the first service with other execution nodes based on the identifier of the execution node and the configuration information of the first service.

[0188] Step 414: The execution node feeds back the execution result to the scheduling / management network element of the connectionless service.

[0189] The above steps 410 to 414 can be understood with reference to steps A310 to A314 in FIG. 3A , and are not described in detail here.

[0190] In addition, the initiator of the execution service in this embodiment may be an application installed on the execution node. In this scenario, it can be understood that the service is provided specifically for a certain application. Therefore, when the execution node is registered, the corresponding application information that can provide the execution service must also be carried. Then refer to Figures 5A, 5C and 6 for execution. Figure 5A indicates the case where the identification of the execution node is the management network element allocation of the execution node, and Figure 6 indicates the case where the identification of the execution node is the scheduling / management network element allocation of a non-connected service, as follows:

[0191] Case 1: The identifier of the execution node is assigned by the management network element of the execution node

[0192] 5A , the execution node management network element, the scheduling / management network element of the non-connected service, the execution node, the direct discovery function management parameters, and the application client / server are used as an example to illustrate that the execution is as follows:

[0193] Step A501: The application client / server sends a capability registration request message to the execution node.

[0194] The request message carries the application identifier (such as the instant messaging application identifier, the video application identifier) ​​and the identity identifier of the execution node in the application (such as the account of the execution node in the instant messaging application, the account of the execution node in the video application).

[0195] The application is an application that provides services for the execution node.

[0196] Step A502: The execution node sends a capability registration request message to the management network element of the execution node.

[0197] The capability registration request message includes not only the message mentioned in step A301 of FIG. 3A , but also the identifier of the application in step A501 and the identity identifier of the execution node in the application.

[0198] The management network element of the execution node may allocate an identifier to the execution node according to the capability registration request message; specifically, the management network element of the execution node may allocate an identifier to the execution node with reference to step A503a or step A503b:

[0199] In step A503a, the management network element of the execution node allocates an identifier to the execution node according to the identity information of the execution node.

[0200] Step A503b: The management network element of the execution node allocates an identifier to the execution node according to the identity information and capability information of the execution node.

[0201] Since the management network element of the execution node in steps A503a and A503b has not yet obtained the service information, the identification of the execution node can be constructed with reference to Figure 5B. The identification of the execution node constructed in Figure 5B can execute different services. For example, the execution node uses the same identification to execute perception services, AI services, etc. The identification of the execution node is user or device granularity, that is, the identification of each execution node corresponds to a device identification, that is, it corresponds one-to-one with the real identity of the execution node. The identification of the execution node may include: the network identification PLMN ID to which the execution node belongs, the network function identification NF ID for assigning the identification to the execution node, temp ID, the communication interface type information supported by the execution node, the type of the execution node, and the application identification APP ID. The information indicated by the dotted box in Figure 5B is optional, and the information indicated by the solid box is mandatory.

[0202] Step A504: The management network element of the execution node sends a response message indicating successful capability registration to the execution node.

[0203] Step A505: The execution node sends a response message indicating successful capability registration to the application client / server.

[0204] Step A506: The application client / server initiates a service request to the scheduling / management network element of the connectionless service.

[0205] In the above step A506, the service request carries the application identifier and, optionally, the application identifier or list of the execution node.

[0206] Step A507: The scheduling / management network element of the non-connected service sends a request message to the management network element of the execution node, where the request message is used to request at least one execution node to execute the first service.

[0207] Step A508: The management network element of the execution node determines an execution node for executing the first service.

[0208] The management network element of the execution nodes maintains the capability information of the execution nodes, so the management network element of the execution nodes can learn which execution nodes can execute the first service.

[0209] Of course, if the execution node executing the first service is a terminal and the execution node is in an idle state, then steps A509 to A510 can also be executed.

[0210] Step A509: The management network element of the execution node pages the execution node for executing the first service.

[0211] The management network element of the execution node may page the terminal by calling a network function that provides a terminal paging function.

[0212] In step A510, the execution node for executing the first service receives paging, changes from an idle state to a connected state, and feeds back a service request to the management network element of the execution node.

[0213] In step A511 , the management network element of the execution node sends the identifier of the execution node for executing the first service to the scheduling / management network element of the non-connected service.

[0214] If the execution node for executing the first service supports PC5 communication, steps A512 to A513 may be executed.

[0215] Step A512: The scheduling / management network element of the connectionless service requests the direct discovery parameter management function for the discovery parameters used to execute the node to communicate using PC5.

[0216] Step A513: The direct discovery parameter management function sends discovery parameters for executing the node to communicate using PC5 to the scheduling / management network element of the non-connected service.

[0217] Step A514: The scheduling / management network element of the non-connected service sends configuration information of the first service to the execution node used to execute the first service.

[0218] Step A515 : The execution node exchanges data of the first service with other execution nodes based on the identifier of the execution node and the configuration information of the first service.

[0219] Step A516: The execution node feeds back the execution result to the scheduling / management network element of the connectionless service.

[0220] The above steps A512 to A516 can be understood with reference to steps A310 to A314 in FIG. 3A , and are not described in detail here.

[0221] The identifier of the execution node in Figure 5A above is assigned to the execution node by the management network element of the execution node after the execution node sends a registration request message to the management network element of the execution node. However, in actual application, the management network element of the execution node can also assign an identifier to the execution node after the scheduling / management network element of the non-connected service triggers the execution of the first service and receives a request message from the scheduling / management network element of the non-connected service. Specifically, it can be executed with reference to Figure 5C, where the execution node used to execute the first service is not a terminal and the execution node does not support PC5 communication. Referring to Figure 5C, taking the management network element of the execution node, the scheduling / management network element of the non-connected service, the execution node, the direct discovery function management parameters, and the application client / server as an example, the execution is as follows:

[0222] Step C501: The application client / server sends a capability registration request message to the execution node.

[0223] Step C502: The execution node sends a capability registration request message to the management network element of the execution node.

[0224] The above steps C501 and C502 can be understood by referring to the above steps A501 and A502 in FIG. 5A , and are not described in detail here.

[0225] Step C503: The management network element of the execution node sends a response message indicating successful capability registration to the execution node.

[0226] Step C504: The execution node sends a response message indicating successful capability registration to the application client / server.

[0227] Step C505: The application client / server initiates a service request to the scheduling / management network element of the connectionless service.

[0228] In the above step C505, the service request carries the application identifier and, optionally, the application identifier or list of the execution node.

[0229] Step C506: The scheduling / management network element of the non-connected service sends a request message to the management network element of the execution node, where the request message is used to request at least one execution node to execute the first service.

[0230] Step C507: The management network element of the execution node determines an execution node for executing the first service.

[0231] Specifically, the management network element of the execution node may allocate an identifier (ie, a temporary identifier) ​​to the execution node with reference to step C508a or step C508b:

[0232] Step C508a: The management network element of the execution node allocates an identifier to at least one execution node according to the identity information of the at least one execution node.

[0233] Step C508b: The management network element of the execution node allocates an identifier to the at least one execution node according to the identity information of the at least one execution node and the capability information of the at least one execution node.

[0234] Step C508a or step C508b can be understood with reference to step 202 of Figure 2 and will not be described in detail here. In addition, when assigning an identifier in step C508b, the timing of the execution node may include the identifier of the application.

[0235] Step C509: The management network element of the execution node sends the identifier of the execution node for executing the first service to the scheduling / management network element of the non-connected service.

[0236] If the execution node needs to use the PC5 interface to communicate with other execution nodes, then the following steps C510-C511 can be executed.

[0237] In step C510 , the execution node requests the direct discovery parameter management function for discovery parameters used by the execution node to communicate using PC5 .

[0238] Step C511 , the direct discovery parameter management function sends discovery parameters for the execution node to communicate using PC5 to the execution node.

[0239] Step C512: The scheduling / management network element of the non-connected service sends configuration information of the first service to at least one execution node used to execute the first service.

[0240] In addition, in step C512, the configuration information of the first service may also carry discovery parameters for the execution node to use PC5 communication.

[0241] Step C513 : The execution node exchanges data of the first service with other execution nodes (the other execution nodes are other execution nodes for executing the first service) based on the identifier of the execution node and the configuration information of the first service.

[0242] Step C513 is the data interaction process between the first execution node and the second execution node in FIG. 2 . Step C513 can be understood by referring to the relevant steps in FIG. 2 , and will not be described in detail here.

[0243] In step C514, the execution node feeds back the execution result to the scheduling / management network element of the connectionless service.

[0244] The above steps C510 to C514 can be understood with reference to steps C308 to C312 in FIG. 3C , and are not described in detail here.

[0245] Case 2: Scheduling / management network element allocation for non-connected services when the execution node is identified

[0246] 6, the execution node management network element, the non-connection service scheduling / management network element, the execution node, the direct discovery function management parameters, and the application client / server are used as an example to illustrate that the execution is as follows:

[0247] Step 601: The application client / server sends a capability registration request message to an execution node.

[0248] The request message carries the application identifier (such as the instant messaging application identifier, the video application identifier) ​​and the identity identifier of the execution node in the application (such as the account of the execution node in the instant messaging application, the account of the execution node in the video application).

[0249] The application is an application that provides services for the execution node.

[0250] Step 602: The execution node sends a capability registration request message to the management network element of the execution node. This can be understood by referring to step A502 in FIG. 5A above and will not be described in detail here.

[0251] Step 603: The management network element of the execution node sends a response message indicating successful capability registration to the execution node.

[0252] Step 604: The execution node feeds back a response message indicating successful capability registration to the application client / server.

[0253] Step 605: The application client / server initiates a service request to the scheduling / management network element of the connectionless service.

[0254] In the above step 605, the service request carries the application identifier and, optionally, the application identifier or list of the execution node.

[0255] Step 606: After obtaining information about the first service, the scheduling / management network element of the non-connected service sends a request message to the management network element of the execution node, where the request message is used to request at least one execution node to execute the first service.

[0256] Step 607: The management network element of the execution node determines at least one execution node for executing the first service.

[0257] It should be understood that the management network element of the execution nodes maintains the capability information of the execution nodes, so the management network element of the execution nodes can learn which execution nodes can execute the first service.

[0258] If the management network element of the execution node determines that the execution node executing the first service is a terminal and the execution node is in an idle state, then steps 608-609 can also be executed. After the execution node successfully receives the paging, the execution node that successfully received the paging can be carried in step 610. If the paging fails, the execution node that failed to receive the paging will not be carried.

[0259] Step 608: The management network element of the execution node pages at least one execution node for executing the first service.

[0260] Step 609: The execution node for executing the first service receives the paging, changes from the idle state to the connected state, and feeds back a service request reception to the management network element of the execution node.

[0261] Step 610: The management network element of the execution node sends a response message to the scheduling / management network element of the non-connected service, wherein the response message includes information of at least one execution node executing the first service.

[0262] After executing step 610, the scheduling / management network element of the non-connected service may obtain information of the execution node according to the response message. Specifically, the following steps may be referred to for execution:

[0263] If the response information includes the identity information of the execution node and the capability information of the execution node, step 611A or step 611B may be executed:

[0264] Step 611A: The scheduling / management network element of the non-connected service allocates an identifier to at least one execution node according to the identity information of at least one execution node.

[0265] Step 611B: The scheduling / management network element of the non-connected service allocates an identifier to the at least one execution node according to the capability information of the at least one execution node and the identity information of the at least one execution node.

[0266] For example, FIG6A shows a schematic diagram of the data structure of an execution node identifier. The identifiers of the execution nodes are user- or device-granular, meaning each execution node identifier corresponds to a device identifier, i.e., a one-to-one correspondence with the actual identity of the execution node. The identifier of the execution node may include: the PLMN ID of the network to which the execution node belongs, the NF ID of the network function that assigns the identifier to the execution node, the temp ID, the identifier of the service executed by the execution node, the type of service executed by the execution node, information about the types of communication interfaces supported by the execution node, the type of the execution node, and the application ID. Information indicated by dashed lines in FIG6A is optional, while information indicated by solid lines is mandatory.

[0267] For example, referring to FIG6B , which is a schematic diagram of the data structure of an execution node identifier, the identifier of the execution node is service-granular, meaning that multiple execution nodes can correspond to the same identifier, i.e., corresponding to a specific service. The execution node identifier for a specific service uses the same identifier. The identifier of the execution node may include: the PLMN ID of the network to which the execution node belongs, the NF ID of the network function that assigns the identifier to the execution node, the identifier of the service executed by the execution node, the type of service executed by the execution node, information about the communication interface types supported by the execution node, the type of execution node, and the application identifier APP ID. The difference from FIG6A above is that the identifier of the execution node in FIG6B does not need to carry a temp ID, but must carry the identifier of the service executed by the execution node. In FIG6A , the large identifier of the execution node must carry the temp ID, and the identifier of the service executed by the execution node is optional. The information indicated by the dashed box in FIG6B is optional, while the information indicated by the solid box is mandatory.

[0268] The above-mentioned step 611A and step 611B can be performed alternatively.

[0269] If the execution node for executing the first service supports PC5 communication, steps 612 and 613 may be executed.

[0270] Step 612: The scheduling / management network element of the connectionless service requests the direct discovery parameter management function for the discovery parameters used to execute the node to communicate using PC5.

[0271] Step 613: The direct discovery parameter management function sends the discovery parameters for executing the node to communicate using PC5 to the scheduling / management network element of the non-connected service.

[0272] Step 614: The scheduling / management network element of the non-connected service sends the configuration information of the first service to the execution node for executing the first service.

[0273] Step 615: The execution node exchanges data of the first service with other execution nodes based on the identifier of the execution node and the configuration information of the first service.

[0274] Step 616: The execution node feeds back the execution result to the scheduling / management network element of the connectionless service.

[0275] The above steps 612 to 616 can be understood with reference to steps A310 to A314 in FIG. 3A , and are not described in detail here.

[0276] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of device interaction. It is understandable that, in order to implement the above functions, each device may include a hardware structure and / or software module that performs each function. Those skilled in the art should easily appreciate that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0277] In the embodiments of the present application, the functional units of the device can be divided according to the above method examples. For example, each functional unit can be divided according to each function, or two or more functions can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or software functional units.

[0278] In the case of using an integrated unit, Figure 7 shows a possible exemplary block diagram of a communication device involved in an embodiment of the present application. As shown in Figure 7, the communication device 700 may include: a processing unit 701 and a transceiver unit 702. The processing unit 701 is used to control and manage the operations of the communication device 700. The transceiver unit 702 is used to support communication between the communication device 700 and other devices. Optionally, the transceiver unit 702 may include a receiving unit and / or a sending unit, respectively, for performing receiving and sending operations. Optionally, the communication device 700 may also include a storage unit for storing program code and / or data of the communication device 700. The transceiver unit may be referred to as an input / output unit, a communication unit, etc., and the transceiver unit may be a transceiver; the processing unit may be a processor. When the communication device is a module (such as a chip) in a communication device, the transceiver unit may be an input / output interface, an input / output circuit, or an input / output pin, etc., and may also be referred to as an interface, a communication interface, or an interface circuit, etc.; the processing unit may be a processor, a processing circuit, or a logic circuit, etc. Specifically, the device may be the above-mentioned first network function, the first execution node, etc.

[0279] In one instance, the communication device 700 is a first execution node, and the transceiver unit 702 is used to obtain the identifier of the first execution node and the identifier of the second execution node, the identifier of the first execution node is used to identify the temporary identity of the first execution node when executing the first business; the second execution node is an execution node that interacts with the first execution node for data of the first business; the identifier of the second execution node is used to identify the temporary identity of the second execution node when executing the first business; the processing unit 701 is used to transmit the data of the first business to the second execution node based on the identifier of the first execution node and the identifier of the second execution node.

[0280] In order to simplify the data interaction process between the first execution node and the second execution node, the transceiver unit 702 also obtains the configuration information of the first service, and the configuration information of the first service includes: the connection parameters required to transmit the data of the first service; the transceiver unit 702 also transmits the data of the first service to the second execution node based on the identifier of the first execution node, the identifier of the second execution node and the connection parameters.

[0281] Specifically, in order to simplify the data interaction process between the first execution node and the second execution node, the above-mentioned connection parameters may include first indication information, and the first indication information is used to indicate the type of communication interface used by the first execution node to transmit the data of the first business; the transceiver unit 702 also uses the communication interface type indicated by the first indication information to transmit the data of the first business to the second execution node based on the identifier of the first execution node and the identifier of the second execution node.

[0282] Specifically, in order to simplify the data interaction process between the first execution node and the second execution node, the above-mentioned connection parameters may also include second indication information, and the second indication information is used to indicate the communication interface type information supported by the second execution node; the processing unit 701 also determines the communication interface for the first execution node and the second execution node to exchange data based on the communication interface type information supported by the first execution node and the second indication information; the transceiver unit 702 also uses the communication interface to transmit the data of the first service to the second execution node based on the identifier of the first execution node and the identifier of the second execution node.

[0283] In an optional manner, the first execution node may register its capabilities with the first network function so that the first network function can better allocate an identifier for the first execution node. Specifically, the transceiver unit 702 also sends a capability registration request message to the first network function, where the capability registration request message includes: identity information of the first execution node and capability information of the first execution node; receives a response message indicating successful capability registration from the first network function; the capability information of the first execution node includes one or more of the following information: service type information supported by the first execution node, the type of the first execution node, communication interface type information supported by the first execution node, selection priority information of the communication interface when the first execution node supports multiple communication interface types, service level information supported by the first execution node, physical address information of the first execution node, application identifier, and identity identifier of the first execution node in the application; the application is an application that provides services for the first execution node.

[0284] In order to reduce the signaling interaction process when the first execution node and the second execution node interact with data, the identifier of the first execution node may include one or more of the following information: the network identifier to which the first execution node belongs, the network function identifier for assigning the identifier to the first execution node, the communication interface type information supported by the first execution node, the type of the first execution node, the identifier of the service executed by the first execution node, the type of the service executed by the first execution node, and the identifier of the application; the application is the application that provides services for the first execution node.

[0285] In order to reduce the signaling interaction process when the first execution node and the second execution node interact with data, the identifier of the second execution node may include one or more of the following information: the network identifier to which the second execution node belongs, the network function identifier for assigning the identifier to the second execution node, the communication interface type information supported by the second execution node, the type of the second execution node, the identifier of the service executed by the second execution node, the type of service executed by the second execution node, and the identifier of the application; the application is the application that provides services for the second execution node.

[0286] If the identifier of the second execution node does not include the above information (such as the network identifier described by the second execution node), in order to reduce the data interaction signaling between the first execution node and the second execution node, the configuration information of the first service may also include one or more of the following information: the network identifier to which the second execution node belongs, the network function identifier for assigning the identifier to the second execution node, the communication interface type information supported by the second execution node, the type of the second execution node, the identifier of the service executed by the second execution node, the type of service executed by the second execution node, and the identifier of the application; the application is the application that provides services for the second execution node.

[0287] In another instance, the communication device 700 is a first network function, and the processing unit 701 is used to determine at least one execution node for executing the first service; an identifier is assigned to the at least one execution node, and the identifier of the first execution node is used to identify the temporary identity of the first execution node when executing the first service, and the first execution node is any one of the at least one execution node; the transceiver unit 702 sends the identifier corresponding to the at least one execution node to the first execution node, and the at least one execution node includes the first execution node and the second execution node, and the second execution node is an execution node other than the first execution node in the at least one execution node, and the identifier of the second execution node is used to identify the temporary identity of the second execution node when executing the first service.

[0288] In an optional manner, after receiving the request message, the communication device 700 may determine at least one execution node for executing the first service. During execution, the request message sent by the second network function may be received through the transceiver unit 702. The request message is sent by the second network function after obtaining information about the first service. The request message is used to request at least one execution node to execute the first service.

[0289] In another optional manner, the communication device 700 may independently determine at least one execution node for executing the first service. During execution, the processing unit 701 may obtain information of the first service and then determine at least one execution node for executing the first service.

[0290] After the communication device 700 determines at least one execution node for executing the first business, it is necessary to assign an identifier to the at least one execution node to ensure the security of the identity information when the execution nodes exchange data. Specifically, the processing unit 701 can assign an identifier to the at least one execution node based on the identity information of the at least one execution node; or, the processing unit 701 can assign an identifier to the at least one execution node based on the capability information of the at least one execution node and the identity information of the at least one execution node.

[0291] In order to ensure that the first network function better allocates an identifier for the execution node, specifically, the transceiver unit 702 can receive a capability registration request message from at least one execution node, wherein the capability registration request message includes: identity information of at least one execution node and capability information of at least one execution node; send a response message of successful capability registration to at least one execution node; the capability information of at least one execution node includes one or more of the following information: service type information supported by at least one execution node, type of at least one execution node, communication interface type information supported by at least one execution node, selection priority information of the communication interface when at least one execution node supports multiple communication interface types, service level information supported by at least one execution node, physical address information of at least one execution node, identification of the application and identity identification of at least one execution node in the application; the application is an application that provides services for at least one execution node.

[0292] In order to reduce the signaling interaction process when executing node data interaction, the identifier of at least one execution node may include one or more of the following information: the network identifier to which the at least one execution node belongs, the network function identifier for assigning the identifier to the at least one execution node, the communication interface type information supported by the at least one execution node, the type of the at least one execution node, the identifier of the service executed by the at least one execution node, the type of the service executed by the at least one execution node, the identifier of the application; the application is an application that provides services for the at least one execution node.

[0293] In order to reduce the signaling interaction process when executing node data interaction, the processing unit 701 can determine the configuration information of the first service based on the information of the first service and the identifier of at least one execution node. The configuration information of the first service includes the connection parameters required to transmit the data of the first service; the transceiver unit 702 can send the configuration information of the first service to the first execution node.

[0294] Specifically, in order to simplify the data interaction process between the first execution node and the second execution node, the above-mentioned connection parameters may include first indication information, and the first indication information is used to indicate the type of communication interface used by the first execution node to transmit data of the first business; or, the connection parameters may also include second indication information, and the second indication information is used to indicate the communication interface type information supported by the second execution node.

[0295] In actual application, the first business may include one or more of the following: computing services, perception services, AI services, and data services.

[0296] As shown in Figure 8, this application also provides a communication device 800. The communication device 800 can be a chip or a chip system. The communication device can be located in the device involved in any of the above method embodiments, such as the first network function, the second network function, the first execution node, etc., to perform the corresponding actions of the device. Optionally, the chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0297] The communication device 800 includes a processor 810. The processor 810 is configured to execute a computer program stored in a memory 820 to implement the actions of each device in any of the above method embodiments. The communication device 800 may also include a memory 820 for storing the computer program.

[0298] Optionally, the memory 820 and the processor 810 are coupled. Coupling is an indirect coupling or communication connection between devices, units, or modules, and can be electrical, mechanical, or other forms, used for information exchange between the devices, units, or modules. Optionally, the memory 820 is integrated with the processor 810. The processor 810 and the memory 820 can each be one or more, without limitation.

[0299] Optionally, in actual applications, the communication device 800 may or may not include a transceiver 830, as illustrated by a dashed box in the figure. The communication device 800 can exchange information with other devices via the transceiver 830. The transceiver 830 can be a circuit, a bus, a transceiver, or any other device capable of exchanging information.

[0300] In a possible implementation, the communication device 800 may be the first network function, the second network function, or the first execution node in the implementation of the above methods.

[0301] The specific connection medium between the transceiver 830, processor 810, and memory 820 is not limited in the embodiments of the present application. In FIG8 , the memory 820, processor 810, and transceiver 830 are connected via a bus. The bus is represented by a bold line in FIG8 . The connection methods between other components are for illustrative purposes only and are not intended to be limiting. Buses can be classified as address buses, data buses, control buses, etc. For ease of illustration, FIG8 shows only one bold line, but this does not imply that there is only one bus or type of bus. In the embodiments of the present application, the processor can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present application can be directly executed by a hardware processor or by a combination of hardware and software modules within the processor.

[0302] In an embodiment of the present application, the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), such as a random-access memory (RAM). The memory may also be any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory in an embodiment of the present application may also be a circuit or any other device that can implement a storage function, for storing computer programs, program instructions and / or data.

[0303] Based on the above embodiments, referring to FIG9 , the embodiment of the present application also provides another communication device 900, including: an interface circuit 910 and a logic circuit 920; the interface circuit 910 can be understood as an input and output interface, which can be used to execute the receiving and sending steps of each device in any of the above method embodiments; the logic circuit 920 can be used to run code or instructions to execute the method executed by each device in any of the above embodiments, which will not be repeated.

[0304] Based on the above embodiments, embodiments of the present application further provide a computer-readable storage medium storing instructions that, when executed, cause the method executed by each device in any of the above method embodiments to be implemented. For example, the method executed by the first network function and the first execution node in the embodiment shown in FIG2 to be implemented. The computer-readable storage medium may include various media capable of storing program code, such as a USB flash drive, a mobile hard drive, a read-only memory, a random access memory, a magnetic disk, or an optical disk.

[0305] Based on the above embodiments, an embodiment of the present application provides a communication system, which includes the first network function and the first execution node mentioned in any of the above method embodiments, and can be used to execute the method executed by each device in any of the above method embodiments.

[0306] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0307] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0308] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0309] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

Claims

1. A communication method, applied to a first execution node, characterized in that: include: Acquire an identifier of the first execution node and an identifier of the second execution node, where the identifier of the first execution node is used to identify a temporary identity of the first execution node when executing the first service; The second execution node is an execution node that exchanges data of the first service with the first execution node; The identifier of the second execution node is used to identify a temporary identity of the second execution node when executing the first service; Based on the identifier of the first execution node and the identifier of the second execution node, the data of the first service is transmitted to the second execution node.

2. The method according to claim 1, characterized in that Also includes: Acquire configuration information of the first service, where the configuration information of the first service includes: connection parameters required for transmitting data of the first service; Transmitting data of the first service to the second execution node based on the identifier of the first execution node and the identifier of the second execution node includes: The data of the first service is transmitted to the second execution node based on the identifier of the first execution node, the identifier of the second execution node, and the connection parameter.

3. The method according to claim 2, characterized in that The connection parameters include first indication information, where the first indication information is used to indicate a type of communication interface used by the first execution node to transmit data of the first service; Transmitting data of the first service to the second execution node based on the identifier of the first execution node, the identifier of the second execution node, and the connection parameter includes: Based on the identifier of the first execution node and the identifier of the second execution node, the data of the first service is transmitted to the second execution node using the communication interface type indicated by the first indication information.

4. The method according to claim 2, characterized in that: The connection parameters include second indication information, where the second indication information is used to indicate type information of the communication interface supported by the second execution node; Transmitting data of the first service to the second execution node based on the identifier of the first execution node, the identifier of the second execution node, and the connection parameter includes: Determine, according to the communication interface type information supported by the first execution node and the second indication information, a communication interface for exchanging data between the first execution node and the second execution node; Based on the identifier of the first execution node and the identifier of the second execution node, the data of the first service is transmitted to the second execution node using the communication interface.

5. The method according to any one of claims 1 to 4, characterized in that: Also includes: Sending a capability registration request message to the first network function, where the capability registration request message includes: identity information of the first execution node and capability information of the first execution node; receiving a response message of successful capability registration from the first network function; The capability information of the first execution node includes one or more of the following information: The service type information supported by the first execution node, the type of the first execution node, the communication interface type information supported by the first execution node, the selection priority information of the communication interface when the first execution node supports multiple communication interface types, the service level information supported by the first execution node, the physical address information of the first execution node, the application identifier and the identity identifier of the first execution node in the application; the application is an application for which the first execution node provides services.

6. The method according to any one of claims 1 to 5, characterized in that: The identifier of the first execution node includes one or more of the following information: an identifier of a network to which the first execution node belongs, an identifier of a network function for allocating an identifier to the first execution node, information on types of communication interfaces supported by the first execution node, a type of the first execution node, an identifier of a service executed by the first execution node, a type of service executed by the first execution node, and an identifier of an application; The application is an application that provides services for the first execution node.

7. The method according to any one of claims 1 to 6, characterized in that: The identifier of the second execution node includes one or more of the following information: The network identifier to which the second execution node belongs, the network function identifier for assigning the identifier to the second execution node, and the second execution The communication interface type information supported by the node, the type of the second execution node, the identifier of the service executed by the second execution node, the type of service executed by the second execution node, and the identifier of the application; the application is an application that provides services for the second execution node.

8. The method according to any one of claims 2 to 4, characterized in that: The configuration information of the first service also includes one or more of the following information: The network identifier to which the second execution node belongs, the network function identifier for assigning the identifier to the second execution node, the type information of the communication interface supported by the second execution node, the type of the second execution node, the identifier of the service executed by the second execution node, the type of service executed by the second execution node, and the identifier of the application; the application is an application that provides services to the second execution node.

9. A communication method, applied to a first network function, characterized in that: include: Determining at least one execution node for executing a first service; Assigning an identifier to each of the at least one execution nodes, where the identifier of the first execution node is used to identify a temporary identity of the first execution node when executing the first service, and the first execution node is any one of the at least one execution node; Sending an identifier corresponding to the at least one execution node to the first execution node, the at least one execution node includes the first execution node and a second execution node, the second execution node is an execution node of the at least one execution node other than the first execution node, and the identifier of the second execution node is used to identify a temporary identity of the second execution node when executing the first business.

10. The method according to claim 9, characterized in that Before determining at least one execution node for executing the first service, the method further includes: A request message sent by a second network function is received, where the request message is sent by the second network function after acquiring information about a first service, and the request message is used to request at least one execution node to execute the first service.

11. The method according to claim 9, characterized in that The determining of at least one execution node for executing the first service includes: After acquiring information about the first service, at least one execution node for executing the first service is determined.

12. The method according to any one of claims 9 to 11, characterized in that: The assigning of an identifier to the at least one execution node respectively includes: Assign an identifier to each of the at least one execution nodes according to the identity information of the at least one execution node; or, According to the capability information of the at least one execution node and the identity information of the at least one execution node, an identifier is respectively allocated to the at least one execution node.

13. The method according to claim 12, characterized in that Also includes: Receiving a capability registration request message from the at least one execution node, wherein the capability registration request message includes: identity information of the at least one execution node and capability information of the at least one execution node; Sending a response message of successful capability registration to the at least one execution node; The capability information of the at least one execution node includes one or more of the following information: The service type information supported by the at least one execution node, the type of the at least one execution node, the communication interface type information supported by the at least one execution node, the selection priority information of the communication interface when the at least one execution node supports multiple communication interface types, the service level information supported by the at least one execution node, the physical address information of the at least one execution node, the identification of the application and the identity identification of the at least one execution node in the application; the application is an application that provides services to the at least one execution node.

14. The method according to any one of claims 9 to 13, characterized in that: The identification of the at least one execution node includes one or more of the following information: The network identifier to which the at least one execution node belongs, the network function identifier for allocating the identifier to the at least one execution node, the type information of the communication interface supported by the at least one execution node, the type of the at least one execution node, the identifier of the service executed by the at least one execution node, the type of the service executed by the at least one execution node, and the identifier of the application; The application is an application that provides services for the at least one execution node.

15. The method according to any one of claims 9 to 14, characterized in that: Also includes: Determine, according to the information of the first service and the identifier of the at least one execution node, configuration information of the first service, where the configuration information of the first service includes connection parameters required for transmitting data of the first service; Send configuration information of the first service to the first execution node.

16. The method according to claim 15, characterized in that The connection parameters include first indication information, where the first indication information is used to indicate the type of communication interface used by the first execution node to transmit data of the first service; or, the connection parameters include second indication information, where the second indication information is used to indicate the type of communication interface supported by the second execution node.

17. The method according to any one of claims 1 to 16, characterized in that: The first service includes one or more of the following: Computing services, perception services, AI services, and data services.

18. A communication device, characterized in that: include: A functional module for implementing the method according to any one of claims 1 to 17.

19. A communication device, characterized in that: include: at least one processor and memory; The memory is used to store computer programs or instructions; The at least one processor is configured to execute the computer program or instruction so that the method according to any one of claims 1 to 17 is performed.

20. A chip system, characterized in that: The chip system comprises: a processing circuit; the processing circuit is coupled to a storage medium; The processing circuit is used to execute part or all of the computer programs or instructions in the storage medium, and when the part or all of the computer programs or instructions are executed, it is used to implement the method according to any one of claims 1 to 17.

21. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed by a computer, the method according to any one of claims 1 to 17 is executed.

22. A computer program product comprising a computer program or instructions, characterized in that When it is run on a computer, the method described in any one of claims 1 to 17 is executed.

Images