CN115278608A

CN115278608A - Service identifier distribution method and communication device in cross-domain computing power awareness network

Info

Publication number: CN115278608A
Application number: CN202110472905.9A
Authority: CN
Inventors: 王岩; 胡伟华
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-04-29
Filing date: 2021-04-29
Publication date: 2022-11-01
Also published as: WO2022228460A1

Abstract

The application provides a service identifier distribution method and a communication device in a cross-domain computing power awareness network, wherein the method comprises the following steps: the first service identification management function in the first network domain receives an allocation request from an edge computing node for allocating a service identification for a first computing service, and if the first computing service corresponds to a cross-domain computing power awareness network, the first service identification management function can acquire the first service identification allocated for the first computing service and return the first service identification to the edge computing node, and the first service identification can identify the first computing service in the cross-domain computing power awareness network. The method realizes the function of distributing the service identifier for the first computing service deployed in a plurality of network domains of the cross-domain computing power awareness network, and can support the cross-domain computing power awareness network to construct a dynamic computing power route for the first computing service and perform cross-domain message forwarding based on the first service identifier.

Description

Service identifier distribution method and communication device in cross-domain computing power awareness network

Technical Field

The present application relates to the field of wireless communication technologies, and in particular, to a service identifier allocation method and a communication device in a cross-domain computing power awareness network.

Background

In a 3 GPP-based power-aware network, a basic problem is to implement service identifier-based routing and packet forwarding, regardless of a single-domain power-aware network oriented to a single operator or a cross-domain power-aware network oriented to a multi-operator alliance. This requires that computing services of the same type, regardless of how deployed and how many instances are run, need to be assigned a service identification that can identify the computing service, thereby achieving consistent routing across domains. Therefore, designing a service identity assignment and discovery mechanism is a key issue for implementing a cross-domain computing power aware network.

Disclosure of Invention

The application provides a service identifier distribution method and a communication device in a cross-domain computing power sensing network, which are used for distributing corresponding service identifiers for computing services deployed in the cross-domain computing power sensing network and providing the service identifiers for edge computing nodes.

In a first aspect, an embodiment of the present application provides a method for allocating a service identifier in a cross-domain computing power aware network, where the method may be executed by a first service identifier management function element, and may also be executed by an element (e.g., a chip or a circuit) configured in the first service identifier management function element.

The method comprises the following steps: a first service identifier management function network element receives a first allocation request from an edge computing node, wherein the first allocation request is used for requesting to allocate a service identifier for a first computing service, the first allocation request comprises a service name of the first computing service, the first service identifier management function belongs to a first network domain, and the first network domain is one of a plurality of network domains included in a cross-domain computing power awareness network; if the first computing service corresponds to a cross-domain computing power awareness network, a first service identifier management function network element acquires a first service identifier distributed for the first computing service, wherein the first service identifier is used for identifying the first computing service in the cross-domain computing power awareness network; the first service identification management function network element sends a first allocation response to the edge computing node, wherein the first allocation response comprises the first service identification. Optionally, the first service identifier is used to uniquely identify the first computing service within the cross-domain computing power aware network.

In the foregoing technical solution, the first service identifier management function in the first network domain may obtain a corresponding first service identifier for a first computing service corresponding to the cross-domain computing power aware network, and return the first service identifier to the edge computing node. Since the first service identifier can identify the first computing service in the cross-domain computing power awareness network, the above manner can support deployment of the first computing service in multiple network domains of the cross-domain computing power awareness network, and implementation of dynamic computing power routing and packet forwarding for the first computing service based on the first service identifier.

In one possible design of the first aspect, the first allocation request further includes service scope information for the first computing service; the method further comprises the following steps: and if the service range information indicates that the service range of the first computing service comprises a plurality of network domains in the cross-domain computing power awareness network, the first service identification management function network element determines that the first computing service corresponds to the cross-domain computing power awareness network.

In the above technical solution, the first service identifier management function in the first network domain may identify, according to the service range information of the first computing service, that the cross-domain computing power aware network corresponds to the first computing service, and belongs to a global computing service that may be deployed in the cross-domain computing power aware network, and further obtain, in a corresponding manner, the first service identifier allocated to the first computing service.

In a possible design of the first aspect, the obtaining, by the first service identifier management function element, the first service identifier assigned to the first computing service includes: a first service identification management function network element sends a second allocation request to a second service identification management function network element, wherein the second allocation request is used for requesting to allocate service identifications to a first computing service, and the second allocation request comprises a service name of the first computing service; the first service identification management function network element receives a second allocation response from a second service identification management function network element, the second allocation response including the first service identification, wherein the second service identification management function network element is configured to allocate service identifications for computing services whose service scope includes a plurality of network domains in the cross-domain computing power aware network.

In the foregoing technical solution, after the first service identifier management functional network element of the first network domain determines that the first computing service corresponds to the cross-domain computing power aware network, the first service identifier management functional network element may request the second service identifier management functional network element to allocate a corresponding service identifier for the first computing service, and receive an allocation result from the second service identifier management functional network element.

The process of allocating the service identifier to the first computing service is applicable to a scenario in which a global service identifier management function network element is statically specified, and in the scenario, a specific service identifier management function network element exists in the cross-domain computing power aware network as the global service identifier management function network element, that is, the second service identifier management function network element mentioned in the present application is responsible for allocating the corresponding service identifier to the global computing service corresponding to the cross-domain computing power aware network, and the service scope includes the service identifiers allocated to the global computing services of a plurality of network domains in the cross-domain computing power aware network.

In a possible design of the first aspect, the obtaining, by the first service identifier management function element, the first service identifier assigned to the first computing service includes: a first service identification management function network element obtains the authority of distributing service identification for a first computing service; and the first service identifier management functional network element distributes the first service identifier according to the service name of the first computing service.

In one possible design of the first aspect, the method further includes: the first service identification management function network element sends a first announcement message to a third service identification management function network element, wherein the first announcement message comprises a service name and a first service identification of a first computing service, the third service identification management function belongs to a second network domain, and the second network domain is another network domain except the first network domain, which is included in the cross-domain computing power perception network.

In a possible design of the first aspect, the obtaining, by the first service identifier management function network element, a right to assign a service identifier to a first computing service includes: a first service identification management function network element sends a first permission request to a third service identification management function network element, wherein the first permission request is used for requesting permission of service identification distribution for a first computing service, the first permission request comprises a service name of the first computing service, the third service identification management function network element belongs to a second network domain, and the second network domain is another network domain except the first network domain, which is included in a cross-domain computing power perception network; the first service identification management function network element receives a first permission response from the third service identification management function network element, wherein the first permission response is used for indicating that the first service identification management function network element is accepted to distribute the service identification for the first computing service.

In a possible design of the first aspect, the obtaining, by the first service identifier management function network element, a right to assign a service identifier to the first computing service further includes: the first service identification management function network element receives a second permission request from a third service identification management function network element, wherein the second permission request is used for requesting permission of distributing service identification for the first computing service, and the second permission request comprises a service name of the first computing service; and the first service identifier management function network element sends a second permission response to the third service identifier management function network element, wherein the second permission response is used for indicating that the permission of the third service identifier management function network element for distributing the service identifier for the first computing service is not accepted.

In a possible design of the first aspect, the first permission request includes a first comparison parameter, and the second permission request includes a second comparison parameter; the method further comprises the following steps: and the first service identifier management function network element determines that the permission of distributing the service identifier for the first computing service by the third service identifier management function network element is not accepted according to the first comparison parameter and the second comparison parameter.

In a possible design of the first aspect, the obtaining, by the first service identifier management function network element, the first service identifier assigned to the first computing service includes: the first service identification management function network element receives a second announcement message from a third service identification management function network element and acquires a first service identification according to the second announcement message; the second announcement message includes a service name and a first service identifier of the first computing service, the third service identifier management function network element belongs to a second network domain, and the second network domain is another network domain except the first network domain included in the cross-domain computing power awareness network.

In one possible design of the first aspect, the method further includes: a first service identification management function network element sends a first permission request to a third service identification management function network element, wherein the first permission request is used for requesting permission of service identification distribution for a first computing service, the first permission request comprises a service name of the first computing service, the third service identification management function network element belongs to a second network domain, and the second network domain is another network domain except the first network domain, which is included in a cross-domain computing power perception network; the first service identification management function network element receives a first permission response from the third service identification management function network element, wherein the first permission response is used for indicating that the permission of the first service identification management function network element for distributing the service identification to the first computing service is not accepted.

In one possible design of the first aspect, the method further includes: the first service identification management function network element receives a second permission request from a third service identification management function network element, wherein the second permission request is used for requesting permission for distributing service identification for the first computing service, and the second permission request comprises a service name of the first computing service; and the first service identification management function network element sends a second permission response to the third service identification management function network element, wherein the second permission response is used for indicating that the third service identification management function network element is accepted to distribute the service identification to the first computing service.

In a possible design of the first aspect, the first permission request includes a first comparison parameter, and the second permission request includes a second comparison parameter; the method further comprises the following steps: and the first service identifier management function network element determines to receive the authority of the third service identifier management function network element for distributing the service identifier for the first computing service according to the first comparison parameter and the second comparison parameter.

In the foregoing technical solution, after a first service identifier management function network element of a first network domain determines that a first computing service corresponds to a cross-domain computing power aware network, the first service identifier management function network element may first strive for an authority to allocate a service identifier for the first computing service, after acquiring the authority, allocate a corresponding service identifier according to a service name of the first computing service, which is called the first computing service, and if no authority is acquired, wait for other service identifier management function network elements that acquire the allocation authority to announce their allocation results.

The process of allocating the service identifier for the first computing service is applicable to a scenario of dynamically selecting a global service identifier management function network element, and in the scenario, the local service identifier management function network element of each network domain in the cross-domain computing power aware network may have a function of the global service identifier management function network element. When the first service identifier management function network element needs to allocate service identifiers for global computing services corresponding to multiple network domains in the cross-domain computing power aware network, where the service range includes the service identifiers allocated to global computing services of the multiple network domains in the cross-domain computing power aware network, the first service identifier management function network element may determine, through negotiation with local service identifier management function network elements of other network domains, which local service identifier management function network element specifically obtains the allocation authority (i.e., determine which local service identifier management function network element specifically serves as a function role of the global service identifier management function network element), and the local service identifier management function network element obtaining the allocation authority also needs to announce the allocation result to local service identifier management function network elements of other network domains, so that the allocation result may be synchronized in the multiple network domains, and the first computing service has the same service identifier in the multiple network domains, thereby facilitating implementation of cross-domain computing power awareness and message forwarding for the first computing service.

In one possible design of the first aspect, a global prefix is included in the first service identifier, where the global prefix indicates that the first service identifier is allowed to be routed within a plurality of network domains included in the cross-domain effort-aware network.

In the foregoing technical solution, in order to facilitate identifying a type of a service identifier, if a first computing service corresponds to a cross-domain computing power aware network and belongs to a global computing service whose service range includes multiple network domains in the cross-domain computing power aware network, a first service identifier allocated to the first computing service may carry a global prefix to indicate that the first computing service is the global computing service, and the first service identifier may be routed in the multiple network domains of the cross-domain computing power aware network, so that a computing power aware user plane function in the cross-domain computing power aware network may construct a corresponding computing power route based on the first service identifier, and may perform corresponding control, such as managing a notification and a forwarding range, when a message of the first computing service is forwarded, and determining that the notification and forwarding may be performed in the multiple network domains across domains.

In a second aspect, an embodiment of the present application provides a method for allocating service identifiers in a cross-domain computing power aware network, where the method may be executed by a second service identifier management function network element, and may also be executed by a component (e.g., a chip or a circuit) configured in the second service identifier management function network element.

The method comprises the following steps: a second service identification management function network element receives a second allocation request from a first service identification management function network element, wherein the second allocation request is used for requesting allocation of a service identification for a first computing service, the second allocation request comprises a service name of the first computing service, the first service identification management function network element belongs to a first network domain, and the first network domain is one of a plurality of network domains included in a cross-domain computing power awareness network; the second service identification management function network element distributes a first service identification for identifying the first computing service in the cross-domain computing power awareness network according to the service name of the first computing service; the second service identification management function network element sends a second allocation response to the first service identification management function network element, wherein the second allocation response comprises the first service identification. Optionally, the first service identifier is used to uniquely identify the first computing service within the cross-domain computing power aware network.

Optionally, the second service identifier management function network element is configured to allocate a service identifier for a computing service whose service scope includes multiple network domains in the cross-domain computing power aware network.

Optionally, the first service identifier management function network element is configured to allocate a service identifier for the computing service of the first network domain in the service scope.

In one possible design of the second aspect, a global prefix is included in the first service identification, the global prefix indicating that the first service identification is allowed to be routed within a plurality of network domains included in the cross-domain effort-aware network.

In one possible design of the second aspect, the method further includes: the second service identification management function network element sends a third advertisement message to a third service identification management function network element, wherein the third advertisement message comprises the service name and the first service identification of the first computing service, the third service identification management function belongs to a second network domain, and the second network domain is another network domain except the first network domain included in the cross-domain computing power perception network.

Optionally, the third service identifier management function network element is configured to allocate a service identifier for the computing service of the second network domain in the service range.

In a third aspect, embodiments of the present application provide a method for assigning a service identifier in a cross-domain computing power aware network, where the method may be performed by an edge computing node, and may also be performed by a component (e.g., a chip or a circuit) configured at the edge computing node.

The method comprises the following steps: the method comprises the steps that an edge computing node sends a first distribution request to a first service identification management function network element, the first distribution request is used for requesting service identification distribution for a first computing service, the first distribution request comprises a service name of the first computing service, the first service identification management function network element belongs to a first network domain, the first network domain is one of a plurality of network domains included in a cross-domain computing power sensing network, and the first computing service corresponds to the cross-domain computing power sensing network; the edge compute node receives a first allocation response from a first service identification management function network element, the first allocation response including a first service identification for identifying a first compute service within a cross-domain computing power aware network.

In one possible design of the third aspect, the first computing service corresponds to a cross-domain computing power aware network, including: the first allocation request also includes service scope information for the first computing service indicating that the service scope for the first computing service includes a plurality of network domains in the cross-domain effort-aware network.

In one possible design of the third aspect, a global prefix is included in the first service identifier, where the global prefix indicates that the first service identifier is allowed to be routed within all network domains included in the cross-domain effort-aware network.

The beneficial effects in any possible design of the second aspect and the third aspect may refer to the corresponding descriptions in the first aspect, and are not described again.

In a fourth aspect, an embodiment of the present application provides a method for allocating a service identifier in a cross-domain computing power aware network, where the method may be executed by a first service identifier management function element, and may also be executed by a component (e.g., a chip or a circuit) configured in the first service identifier management function element.

The method comprises the following steps: a first service identifier management function network element receives a first allocation request from an edge computing node, wherein the first allocation request is used for requesting to allocate a service identifier for a first computing service, the first allocation request comprises a service name of the first computing service, the first service identifier management function network element belongs to a first network domain, and the first network domain is one of a plurality of network domains included in a cross-domain computing power awareness network; if the first computing service corresponds to a first network domain, the first service identifier management function network element allocates a first service identifier according to the service name of the first computing service, wherein the first service identifier is used for identifying the first computing service in the first network domain; the first service identification management function network element sends a first allocation response to the edge computing node, wherein the first allocation response comprises the first service identification. Optionally, the first service identifier is used to uniquely identify the first computing service within the first network domain.

In the foregoing technical solution, the first service identifier management function in the first network domain may allocate a corresponding first service identifier to the first computing service corresponding to the first network domain, and return the first service identifier to the edge computing node. Since the first service identifier may identify the first computing service in the first network domain, the above manner may support deployment of the first computing service in the first network domain of the cross-domain computing power aware network, and implementation of dynamic computing power routing and packet forwarding for the first computing service based on the first service identifier.

In one possible design of the fourth aspect, the first allocation request further includes service scope information for the first computing service; the method further comprises the following steps: if the service range information indicates that the service range of the first computing service is the first network domain, the first service identifier management function network element determines that the first computing service corresponds to the first network domain.

In the above technical solution, the first service identifier management function in the first network domain may identify, according to the service range information of the first computing service, that the first computing service corresponds to the first network domain, and belongs to the local computing service deployed only in the first network domain of the cross-domain computing power awareness network, and may further directly allocate the first service identifier to the first computing service.

In one possible design of the fourth aspect, the first service identification includes a local prefix therein, the local prefix indicating that the first service identification is allowed to be routed within the first network domain.

In the foregoing technical solution, in order to facilitate identifying the type of the service identifier, if the first computing service corresponds to the first network domain and belongs to a local computing service whose service range is the first network domain, the first service identifier allocated to the first computing service may carry a local prefix to indicate that the first computing service is the local computing service, and the first service identifier may be routed within the first network domain, so that the computing power awareness user plane function in the cross-domain computing power awareness network may construct a corresponding computing power route based on the first service identifier, and may perform corresponding control when advertising the service capability information related to the first computing service and forwarding the packet of the first computing service, for example, manage an advertisement and a forwarding range, and determine to perform advertisement and forwarding only in the first network domain.

In a fifth aspect, the present application provides a method for assigning a service identifier in a cross-domain computing power aware network, where the method may be performed by an edge computing node, and may also be performed by a component (e.g., a chip or a circuit) configured at the edge computing node.

The method comprises the following steps: the method comprises the steps that an edge computing node sends a first distribution request to a first service identification management function network element, the first distribution request is used for requesting service identification distribution for a first computing service, the first distribution request comprises a service name of the first computing service, the first service identification management function network element belongs to a first network domain, the first network domain is one of a plurality of network domains included in a cross-domain computing power perception network, and the first computing service corresponds to the first network domain; the edge compute node receives a first allocation response from the first service identification management function network element, the first allocation response including a first service identification identifying a first computing service within the first network domain. Optionally, the first service identifier is used to uniquely identify the first computing service within the first network domain.

In one possible design of the fifth aspect, the first computing service corresponds to the first network domain and includes: the first allocation request further includes service scope information for the first computing service indicating that a service scope of the first computing service is the first network domain.

In one possible design of the fifth aspect, the first service identification includes a local prefix therein, the local prefix indicating that the first service identification is allowed to be routed within the first network domain.

The beneficial effects in any possible design of the fifth aspect can be referred to the corresponding descriptions in the fourth aspect, and are not repeated.

In a sixth aspect, an embodiment of the present application provides a communication apparatus, where the apparatus may have a function of a network element that implements a first service identity management function in any possible design of the above aspects or aspects, may also have a function of a network element that implements a second service identity management function in any possible design of the above aspects or aspects, and may also have a function of an edge computing node in any possible design of the above aspects or aspects. The apparatus may be a network device, and may also be a chip included in the network device.

The functions of the communication device may be implemented by hardware, or by hardware executing corresponding software, which includes one or more modules or units or means (means) corresponding to the functions.

In one possible design, the apparatus structurally includes a processing module and a transceiver module, where the processing module is configured to support the apparatus to perform a function corresponding to the first service identity management function network element in any one of the above aspects or aspects, or to perform a function corresponding to the second service identity management function network element in any one of the above aspects or aspects, or to perform a function corresponding to the edge computing node in any one of the above aspects or aspects. The transceiver module is configured to support communication between the apparatus and other communication devices, for example, when the apparatus is an edge computing node, the transceiver module may send a first allocation request to a first service identifier management function network element to request the first service identifier management function to allocate a corresponding service identifier to a computing service deployed in the edge computing node. The communication device may also include a memory module, coupled to the processing module, that stores the device's necessary program instructions and data. As an example, the processing module may be a processor, the communication module may be a transceiver, the storage module may be a memory, and the memory may be integrated with the processor or provided separately from the processor.

In another possible design, the apparatus may be configured to include a processor and may also include a memory. A processor is coupled to the memory and is operable to execute computer program instructions stored in the memory to cause the apparatus to perform the method in any of the possible designs of the above-described aspects or aspects. Optionally, the apparatus further comprises a communication interface, the processor being coupled to the communication interface. When the apparatus is a network device, the communication interface may be a transceiver or an input/output interface; when the apparatus is a chip included in a network device, the communication interface may be an input/output interface of the chip. Alternatively, the transceiver may be a transceiver circuit and the input/output interface may be an input/output circuit.

In a seventh aspect, an embodiment of the present application provides a chip system, including: a processor coupled to a memory for storing a program or instructions that, when executed by the processor, cause the system-on-chip to implement the method in any one of the possible designs of the above-described aspects or aspects.

Optionally, the system-on-chip further comprises an interface circuit for interacting code instructions to the processor.

Optionally, the number of processors in the chip system may be one or more, and the processors may be implemented by hardware or software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory.

Optionally, the memory in the system-on-chip may also be one or more. The memory may be integral to the processor or may be separate from the processor. Illustratively, the memory may be a non-transitory processor, such as a read only memory ROM, which may be integrated on the same chip as the processor or may be separately provided on different chips.

In an eighth aspect, embodiments of the present application provide a computer-readable storage medium having stored thereon a computer program or instructions which, when executed, cause a computer to perform the method of any one of the possible designs of the above-described aspects or aspects.

In a ninth aspect, embodiments of the present application provide a computer program product which, when read and executed by a computer, causes the computer to perform the method in any one of the possible designs of the above-described aspect or aspects.

In a tenth aspect, an embodiment of the present application provides a communication system, where the communication system includes a first service identifier management function network element and an edge computing node. Optionally, the communication system may further include a second service identifier management function network element and a third service identifier management function network element.

Drawings

Fig. 1 is a schematic network architecture diagram of a communication system supporting a computing power aware network according to an embodiment of the present application;

FIG. 2 is a specific example of a cross-domain computing power aware network provided by an embodiment of the present application;

fig. 3 is a schematic network architecture diagram of a communication system supporting a cross-domain computing power aware network according to an embodiment of the present application;

fig. 4 is a schematic diagram of a format and a generation manner of a local service identifier or a global service identifier provided in an embodiment of the present application;

fig. 5a is a schematic diagram of a message forwarding relationship between intra-domain and inter-domain in a cross-domain computing power aware network provided in this embodiment of the present application;

fig. 5b is a schematic diagram illustrating an intra-domain and inter-domain advertisement forwarding relationship in a cross-domain computing power aware network according to an embodiment of the present application;

fig. 6 is a schematic flowchart of a service identifier allocation method in a cross-domain computing power aware network according to an embodiment of the present application;

fig. 7 is an expanded flow diagram of a service identifier allocation method in a cross-domain computing power awareness network according to an embodiment of the present application;

fig. 8 is a schematic diagram of a first service identifier when a first computing service corresponds to a cross-domain computing power aware network according to an embodiment of the present application;

fig. 9 is a schematic view of a scenario of a network element with a statically assigned global service identifier management function according to an embodiment of the present application;

fig. 10 is a schematic flowchart of embodiment 1 for acquiring a first service identifier according to an embodiment of the present application;

fig. 11 is a schematic view of a scenario of dynamically selecting a network element with a global service identifier management function according to an embodiment of the present application;

fig. 12 is a flowchart illustrating a situation that a first sifdmf obtains a right to allocate a service identifier to a first computing service in embodiment 2 of obtaining a first service identifier according to an embodiment of the present application;

fig. 13 is a flowchart illustrating a situation that the first SIDMF does not obtain the authority to allocate the service identifier to the first computing service in embodiment 2 of obtaining the first service identifier according to the embodiment of the present application;

fig. 14 is a schematic flowchart of another method for allocating service identifiers in a cross-domain computing power awareness network according to an embodiment of the present application;

fig. 15 is a schematic diagram of a first service identifier when a first computing service corresponds to a first network domain according to an embodiment of the present application;

fig. 16 and 17 are schematic diagrams of a communication device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.

The technical solution of the embodiment of the present application may be applied to various communication systems, such as a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, a fifth generation (5 th generation,5 g) mobile communication system or a New Radio (NR) system, or a future communication system or other similar communication systems.

Hereinafter, some terms in the present application are explained so as to be easily understood by those skilled in the art.

1) The terminal equipment is equipment with a wireless transceiving function. The terminal devices may communicate with a core network or the internet via a Radio Access Network (RAN), exchanging voice and/or data with the RAN.

The terminal device may include a User Equipment (UE), a wireless terminal device, a mobile terminal device, a D2D terminal device, a vehicle to electronic (V2X) terminal device, a machine-to-machine-type communication (M2M/MTC) terminal device, an internet of things (IoT) terminal device, a subscriber unit (subscriber unit), a subscriber station (subscriber state), a mobile station (mobile state), a remote station (remote state), an Access Point (AP), a remote terminal (remote terminal), an access terminal (access terminal), a user terminal (user terminal), a user agent (user agent), or a user equipment (user device), etc. For example, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiving function, a portable, pocket, handheld, computer-embedded mobile device, and the like. For another example, the terminal device may be a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote surgery (remote medical supply), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), a terminal device in future evolution Public Land Mobile Network (PLMN), or a CPE vehicle device in V2X, a customer premise equipment (customer equipment), or the like. For another example, the terminal device may be a Personal Communication Service (PCS) phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), and the like. The embodiment of the present application does not limit the specific technology and the specific device form adopted by the terminal device.

By way of example, and not limitation, the terminal device may also be a wearable device. Wearable equipment can also be called wearable smart device or intelligent wearable equipment etc. is the general term of using wearable technique to carry out intelligent design, develop the equipment that can dress to daily wearing, like glasses, gloves, wrist-watch, dress and shoes etc.. A wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device has full functions and large size, and can realize complete or partial functions without depending on a smart phone, for example: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets, smart helmets, smart jewelry and the like for monitoring physical signs. The various terminal devices described above, if located on a vehicle (e.g. placed in or mounted in a vehicle), may be considered to be vehicle-mounted terminal devices, also referred to as on-board units (OBUs), for example.

2) A radio access network device is a device for accessing a terminal device to a wireless network in a communication system. The radio access network equipment may typically be connected to the core network by a wired link, such as a fibre optic cable. The radio access network device may be a node in the RAN, which may also be referred to as a base station (base station), and may also be referred to as a RAN node (or device).

The radio access network device may include a base station, an evolved NodeB (eNodeB) in an LTE system or an evolved LTE system (LTE-Advanced, LTE-a), a next generation base station (next generation NodeB, gNB) in a 5G communication system, a Transmission Reception Point (TRP), a baseband unit (BBU), an Access Point (AP) in a Wireless Local Area Network (WLAN), an access and backhaul (IAB) node, a base station in a future mobile communication system or an access node in a WiFi system, and the like. The radio access network device may also be a module or unit that performs part of the functionality of the base station, such as a Centralized Unit (CU) or a Distributed Unit (DU). The embodiment of the present application does not limit the specific technology and the specific device form adopted by the radio access network device.

For example, in one network structure, the radio access network device may be a CU node, or a DU node, or a radio access network device including a CU node and a DU node. The CU node is configured to support Radio Resource Control (RRC), packet Data Convergence Protocol (PDCP), service Data Adaptation Protocol (SDAP), and other protocols; the DU node is configured to support a Radio Link Control (RLC) layer protocol, a Medium Access Control (MAC) layer protocol, and a physical layer protocol.

The wireless access network equipment and the terminal equipment can be deployed on land, including indoors or outdoors, and are handheld or vehicle-mounted; can also be deployed on the water surface; it may also be deployed on airborne airplanes, balloons, and satellites. The application scenarios of the wireless access network device and the terminal device are not limited in the embodiments of the present application. In this embodiment, the radio access network device may be referred to as an access network device for short, and unless otherwise specified, the access network device is referred to as a radio access network device hereinafter.

3) The core network device is a device in a Core Network (CN) that provides service support for the terminal device. The core network device may include network elements or functional entities such as an access and mobility management function (AMF), a Session Management Function (SMF), a User Plane Function (UPF), a network capability opening function (NEF), a Unified Data Management (UDM), and an Application Function (AF).

The AMF is mainly used for access management and mobility management of terminal equipment, such as user location update, registered network, cell switching and the like; the SMF is mainly used for session management, such as session establishment, modification, release, etc. of a user; the UPF is a functional entity of the user plane, and is mainly used for connecting an external network and processing user messages, such as forwarding, charging, lawful monitoring and the like; NEF is used to expose part of the functionality of the network to applications in a controlled manner; the UDM is used for managing subscription information of the terminal equipment; the AF is configured to provide service data of various applications to a control plane network element of a communication network of an operator, or obtain data information and control information of the network from the control plane network element of the communication network.

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

It should be noted that the network element or the functional entity may be a network element in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (e.g., a cloud platform). Optionally, the network element or the functional entity may be implemented by one device, may also be implemented by multiple devices together, and may also be different functional modules in one device, which is not specifically limited in this embodiment of the present application.

4) The terms "system" and "network" in the embodiments of the present application may be used interchangeably. The "plurality" means two or more, and in view of this, the "plurality" may also be understood as "at least two" in the embodiments of the present application. "at least one" is to be understood as meaning one or more, for example one, two or more. For example, the inclusion of at least one means that one, two or more are included, and does not limit which is included. For example, including at least one of A, B, and C, then what is included may be A, B, C, A and B, A and C, B and C, or A and B and C. Similarly, the understanding of the description of "at least one" and the like is similar. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of single item(s) or plural items. For example, "at least one of A, B, and C" includes A, B, C, AB, AC, BC, or ABC. "and/or" describes the association relationship of the associated object, indicating that there may be three relationships, for example, a and/or B, which may indicate: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" generally indicates that the preceding and following related objects are in an "or" relationship, unless otherwise specified.

Unless specifically stated otherwise, the embodiments of the present application refer to the ordinal numbers "first", "second", etc., for distinguishing between a plurality of objects, and do not limit the sequence, timing, priority, or importance of the plurality of objects, and the descriptions of "first", "second", etc., do not limit the objects to be necessarily different.

The network architecture and related technical features applicable to the embodiments of the present application are described in detail below.

1. Computing power sensing network

In order to enable a third generation partnership project (3 rd generation partnership project,3 GPP) network to adapt MEC intensive deployment and high dynamic scheduling of edge micro services/functions, improve addressing efficiency of edge service discovery and access, realize connection and calculation end-to-end unified session and mobility management, and make a network aware of the success.

The computing-power-aware network is also called a computing-power-aware virtual network (CA-VN) or a mobile computing-power network, and introduces a Computing Management Function (CMF) and a computing-power-aware user plane function (CA-UPF) based on the existing 3GPP network architecture, implements computing power awareness through information advertisement between CA-UPFs, and dynamically implements computing power routing and packet forwarding based on service identification.

Referring to fig. 1, a network architecture of a communication system supporting a computing power aware network according to an embodiment of the present disclosure includes a terminal device, an access network device, an AMF, an SMF, a CMF, a service identification management function (SIDMF), an NEF, a MEC platform manager (manager), a computing power aware network, and an edge data network (edge data network). Wherein the computing-aware network may include at least one CA-UPF and the edge data network may include at least one edge computing node, which may also be referred to as MEC node (or site). Optionally, a client (client) is installed in the terminal device, and the client may be an Application Client (AC).

The main features of the above computing power sensing network can be summarized as follows:

1) And the functional roles of the CA-UPF are divided into an inlet (Ingress) CA-UPF and an outlet (Egress) CA-UPF. The entry CA-UPF refers to the CA-UPF which can be used as an access anchor point for the terminal equipment to access the computing power sensing network, and the exit CA-UPF refers to the CA-UPF associated with the edge computing node in the edge data network.

Because each CA-UPF in the computing power aware network may be selected by the terminal device as an access anchor point, and according to the dynamic change of the network deployment situation, each CA-UPF in the computing power aware network may also establish or disassociate a relationship with an edge computing node in the edge data network, therefore, the functional roles of the CA-UPFs may be relatively and dynamically changed, and one CA-UPF may exist only as an ingress CA-UPF, only as an egress CA-UPF, or both as an ingress CA-UPF and an egress CA-UPF, without limitation.

2) The outlet CA-UPF can establish an association relation with an edge computing node in an edge data network, receive service binding information reported by the edge computing node, record a mapping relation between a service identifier (service ID) of a computing service and a server IP address (server IP) according to the service binding information, receive the computing service information and load information reported by the edge computing node, and announce the computing service information and the load information to a corresponding inlet CA-UPF according to an announcing neighbor list.

In a force-aware network, one egress CA-UPF may correspond to one or more ingress CA-UPFs. The neighbor relation between the outlet CA-UPF and one or more corresponding inlet CA-UPFs is called as advertisement neighbor relation, which indicates that the outlet CA-UPF needs to advertise information, such as computing service information and load information, for representing the computing service capability provided by the associated edge computing node to the outside, to the corresponding inlet CA-UPF, so that the inlet CA-UPF constructs the computing force routing information according to the information. Accordingly, the egress CA-UPF is configured with an advertising neighbor list including identification information of one or more ingress CA-UPFs corresponding to the egress CA-UPF.

It is to be understood that, in the embodiment of the present application, the computing service information and the load information of the edge computing node associated with the egress CA-UPF may be collectively referred to as service capability information, and one or more ingress CA-UPFs corresponding to the egress CA-UPF may be considered as an advertisement object for the egress CA-UPF to advertise the service capability information.

3) The entry CA-UPF can gather the calculation service information and the load information received from the corresponding exit CA-UPF, construct corresponding calculation force routing information aiming at each calculation service according to the forwarding neighbor list and the calculation service information and the load information, and forward the service request message of the terminal equipment to one of the corresponding exit CA-UPF based on the calculation force routing information.

In a force-aware network, one ingress CA-UPF may correspond to one or more egress CA-UPFs. The neighbor relation between the inlet CA-UPF and one or more corresponding outlet CA-UPF is called forwarding neighbor relation, which indicates that the inlet CA-UPF needs the service request message of the terminal device to be forwarded to one of the corresponding outlet CA-UPF, so that the service request message of the terminal device can be dynamically forwarded to a proper edge computing node for processing. Accordingly, the ingress CA-UPF is configured with a forwarding neighbour list including identification information of one or more egress CA-UPFs to which the ingress CA-UPF corresponds.

It should be understood that, in this embodiment of the present application, one or more egress CA-UPFs corresponding to an ingress CA-UPF may be considered as multiple optional forwarding objects for the ingress CA-UPF to forward the service request packet, where the service request packet may also be referred to as a service request packet, or has other names, and is not limited.

4) And on the basis of Protocol Data Unit (PDU) session processing of the existing UPF, the CA-UPF is additionally provided with a computing power sensing processing unit, an area dynamic session processing unit and a network address conversion unit.

Specifically, the computing power awareness processing unit in the egress CA-UPF is responsible for acquiring Service capability information from the edge computing node, storing a mapping relationship between a Service identifier (Service ID) of the computing Service and a Server IP address (Server IP address), and advertising the Service capability information of the edge computing node to the ingress CA-UPF in the advertisement neighbor list. The service capability information of the edge computing node may include computing service information and/or load information of the edge computing node, where the computing service information is used to indicate which computing services the edge computing node supports, and specifically may include one or more items of information such as a service identifier, a service attribute, an operating state, or computing resource information of each computing service, and the load information is used to characterize a current load state of the edge computing node.

The computing power perception processing unit in the entrance CA-UPF is responsible for receiving the service capability information from the exit CA-UPF and generating or updating the computing power routing information base in the entrance CA-UPF. The computing routing information base includes computing routing information for one or more computing services. The computation force routing information of a computation service comprises one or more items of information such as service identification of the computation service, identification information of one or more egress CA-UPFs capable of providing the computation service, service capability information (including computation service information and/or load information of an associated edge computation node) corresponding to each egress CA-UPF, network cost information (such as time delay, bandwidth and jitter between the ingress CA-UPF and the egress CA-UPF), and the like. The calculation force sensing processing unit can select a proper forwarding tunnel for the service request message received by the regional dynamic session processing unit based on the calculation force routing information of the calculation service in the calculation force routing information base, and generate a corresponding message matching forwarding rule.

The regional dynamic session processing unit mainly has the functions of establishing a forwarding tunnel between an inlet CA-UPF and an outlet CA-UPF according to forwarding tunnel information issued by the SMF, and matching forwarding rules based on messages generated by the calculation sensing processing unit to realize real-time forwarding of the messages. After the regional dynamic session processing in the inlet CA-UPF receives the service request message from the terminal equipment, if no corresponding message matching forwarding rule matches the message to the corresponding forwarding tunnel, the computing power sensing processing unit selects an outlet CA-UPF for the regional dynamic session processing based on the computing power routing information base and generates a corresponding message matching forwarding rule.

The network address conversion unit is mainly used for finishing the mutual replacement between the service identifier of the computing service and the server IP address in the message according to the mapping relation between the service identifier of the computing service provided by the computing power sensing and processing unit and the server IP address. The network address conversion unit can replace a destination IP address in an uplink message sent to the edge computing node with a server IP address from a service identifier of computing service, and replace a source IP address in a downlink message returned to the terminal equipment with the server IP address from the service identifier of computing service.

5) The CMF is used for creating and managing the calculation power perception network instance, and specifically comprises the following steps: the management algorithm-aware network includes which CA-UPF members, determines the functional role of each CA-UPF member (i.e., whether a CA-UPF is an ingress CA-UPF, an egress CA-UPF, or both), establishes and updates forwarding neighbor relationships and/or advertising neighbor relationships between CA-UPF members, and the like. In addition, the CMF may also be configured to record information such as service identifiers and service statuses of computing services deployed in the edge data network, so that the terminal device performs querying before initiating the service request.

The computing awareness network exists in the form of an internal virtual interface in CA-UPF and may have multiple instances. Each computing awareness network may correspond to a different Network Slice Instance (NSI) and/or Data Network Name (DNN). The members of the CA-UPF included in different force sensing networks may be completely different, may also partially overlap, and may also be completely the same, and the application is not limited thereto.

The CMF can create the computing power awareness network among the CA-UPFs by sending a request for creating the computing power awareness network to the SMF, establish a neighbor relation for adjacent CA-UPFs in the computing power awareness network, and perform dynamic session management for the CA-UPFs forming the neighbor relation based on computing awareness. Therefore, regional computing power groups can be formed among the edge computing nodes associated with the adjacent CA-UPFs, computing services can be dynamically deployed in the regional computing power groups, the service capability information of the edge computing nodes can be rapidly announced among the CA-UPFs, so that service requests of terminal equipment can be rapidly responded, the service requests can be forwarded to the appropriate edge computing nodes based on the dynamic computing power routing information, the resource load balance of the system is achieved, and the user experience is improved.

It is understood that in the embodiment of the present application, the forwarding neighbor list and/or the advertising neighbor list of each CA-UPF may be added, modified, and deleted as needed, and since the forwarding neighbor relation and the advertising neighbor relation are relative, the CMF may identify each egress CA-UPF in the forwarding neighbor list of the ingress CA-UPF, and the advertising neighbor list of the ingress CA-UPF includes the ingress CA-UPF.

6) The SMF can receive a request for establishing the computing power sensing network from the CMF, establish a virtual network level forwarding tunnel between the CA-UPFs according to the forwarding neighbor relation and the announcement neighbor relation among the CA-UPFs, and issue a corresponding forwarding neighbor list and/or an announcement neighbor list to each CA-UPF.

7) Each edge computing node in the edge data network can be associated with a CA-UPF in the computing power sensing network and used as the last hop before a service request message of the terminal equipment is forwarded to the edge computing node, so that the end-to-end data forwarding paths are ensured to be controlled by the mobile network. The interface between the edge computing node and the CA-UPF may be an N6 interface defined by 3GPP, and the interface between the CA-UPF and the CA-UPF may be an N19 interface defined by 3 GPP.

A group formed by a plurality of adjacent edge computing nodes in the edge data network is called an area computing power group. And the CA-UPFs associated with the edge computing nodes in the regional computing power group are in a mutual neighbor relation. By forming the adjacent edge computing nodes into the regional computing power cluster, the edge data network can break through the resource bottleneck of a single site by using a load balancing technology, so that the scale of the edge computing serviceable application is improved. It should be noted that the regions and the neighbors are divided based on the network delay between the edge computing nodes, and the region computation power group can be formed by the edge computing nodes with interaction delay within a specified range, so that the response efficiency of the edge service is improved.

The edge compute nodes may include MEC platforms and/or Edge Application Servers (EAS). The MEC platform is used for taking charge of local computation, storage, scheduling of network resources and the like. EAS is used to deploy or run a computing service, and a particular computing service that is run in EAS may be referred to as a service instance of the computing service. An edge compute node may include one or more EAS each assigned a different server IP address. The physical form of the EAS may be a physical bare machine, a virtual machine, a container, or the like, and the present application is not limited thereto.

The MEC platform manager is used for managing MEC platforms and EAS resources in the edge computing nodes, and dynamically deploying, arranging and managing life cycles of computing services with different granularities, such as virtual machines, micro-services and function instances, on the EAS in the edge computing nodes through interaction with the MEC platforms in the edge computing nodes.

9) Each type of computing service can correspond to a unique service identifier (service ID) in an operator network domain, and the computing force sensing network dynamically routes and forwards a message of a terminal device requesting the computing service based on the service identifier.

Each type of computing service may also have a service name (service name) for characterizing what the computing service is, and the service names of the computing services may correspond to the service identifications one to one. The service name may be in the form of a description of a Uniform Resource Identifier (URI) or a Uniform Resource Locator (URL).

The same computing service may be deployed on different edge computing nodes in the edge data network, equivalent to distributing multiple copies of the computing service in the edge data network, the multiple copies corresponding to different server IP addresses but still having the same service identification. For example, the multiple copies may be multiple service instances of the same computing service running on EAS of different edge computing nodes.

The computing power sensing network can realize computing power routing information of computing services based on the service identifications, map server IP addresses of multiple copies of the same computing service deployed on different edge computing nodes to the same service identification, and indicate that the multiple edge computing nodes can provide the same computing service, so that routing consistency is realized.

In order to reuse the existing IP protocol stack as much as possible, the service identity of the computing service may be an IP anycast address, and the terminal device may initiate a service request using the service identity of the computing service without concern for the specific EAS on which the service instance of the computing service is running, and for the specific details of what the server IP address of the EAS is. Specifically, the terminal device may translate a service name in the service request into a service identifier, and construct a corresponding IP packet (i.e., a service request packet) by using the service identifier as a destination IP address. The CA-UPF can perform routing forwarding on the service request message based on the service identifier of the computing service and perform mutual replacement between the service identifier and the IP address of the server when the message is transmitted and received to the EAS in the edge computing node.

The computing services referred to in the embodiments of the present application, also referred to as edge computing services or edge applications, are not monolithic applications in the traditional client-server model, but rather are relatively lightweight services, such as microservices or function instances, etc. These lightweight computing services are deployed and run on EAS in the edge computing nodes. Alternatively, the computing service may be a stateless, short-life microservice or function instance.

10 SIDMF), which is used to provide a unified service identity assignment function for computing services deployed in the edge data network. The SIDMF may be deployed together with the CMF as an enhanced function of the CMF, or may be deployed independently of the CMF, which is not limited in this application.

Specifically, service identifier assignment in a computing-aware network involves the following two processes:

the first process is as follows: the deployment of computing services and the assignment of service identities. The MEC platform manager deploys and runs service instances of the computing service on the designated edge computing nodes, and the MEC platform generates a service name remotely called by a client of the terminal device for the deployment of the computing service. And then, the MEC platform sends a service identifier distribution request to the SIDF through the NEF, and the SIDF distributes a corresponding service identifier for the service name and returns the service identifier to the MEC platform. The service identification assignment algorithm may be a direct hash of the service name, or a table lookup, or any other algorithm to ensure the uniqueness of the service identification in the effort-aware network. And the SIDF stores the mapping relation between the service name and the service identifier and is used for the subsequent terminal equipment to obtain the service identifier corresponding to the computing service. And after obtaining the distributed service identification, the MEC platform announces the service identification and the corresponding service capability information to the associated CA-UPF for creating a calculation power route.

And a second process: and the terminal equipment acquires the service identifier. Before a client in a terminal device initiates a service request for an application layer of a certain computing service, a service identifier corresponding to a service name of the computing service needs to be known, so that a service request message is constructed by using the service identifier of the computing service as a destination IP address and is sent to a computing power sensing network through the terminal device. Therefore, the client can request the terminal device to acquire the service identifier corresponding to the service name of the computing service, the terminal device forwards the service identifier request message to the SMF through the CA-UPF and then to the CMF, the CMF acquires the service identifier allocated to the service name from the SIDMF, and simultaneously returns the service identifier and the corresponding service state information to the terminal device according to the original path, and the terminal device returns the service identifier and the corresponding service state information to the client.

It should be noted that the above network architecture is a MEC scale intensive deployment scenario for a single operator implementation. That is, the effort-aware network is independently deployed and managed by a single operator, and may be understood as a single-domain effort-aware network implemented within the management scope of the single operator. The CA-UPF in the effort awareness network, and the access network devices and various types of core network devices (such as AMF, SMF, CMF, etc.) in the communication system supporting the effort awareness network are controlled and managed by the same operator.

2. Cross-domain computing power awareness network

In order to solve the problem that the edge application coverage and the user group of the power-aware network of a single operator are limited, a boundary power-aware user plane function (boundary CA-UPF) is further introduced in the present application on the basis of the power-aware network shown in the network architecture in fig. 1. The computing power awareness networks of different operators with alliance relations can establish computing power routing and forwarding tunnels among the different operators through a boundary CA-UPF, and therefore the cross-domain computing power awareness network is established.

By introducing the boundary CA-UPF, the edge computing service can be flexibly deployed at the edge computing node connected with the computing power sensing networks of a plurality of operators in a union relationship, and a user of one operator can access the edge computing service in the operator network of a local domain and can also access the edge computing service in the operator network of a union domain through the boundary CA-UPF, so that the problems of limited edge application coverage and user group of the computing power sensing network of a single operator can be solved, the infrastructure capabilities of the plurality of operators are favorably aggregated, a uniform capability open interface is provided for an application provider and an enterprise user, and the consistent seamless edge service experience across operators is realized.

The cross-domain computing power aware network may include multiple network domains, and different network domains may be managed by different operators. The intra-domain part of a cross-domain computing power aware network within one network domain may be referred to as an intra-domain computing power aware network, or simply as an operator network. Depending on the perspective, the multiple network domains may have a distinction between local domains and federated domains.

Referring to fig. 2, a specific example of a cross-domain computing power aware network provided in the embodiment of the present application is shown. The present application illustrates by way of this example the concept of cross-domain computational power awareness of local and federated domains in a network.

In a federation, the effort-aware network of each operator may be referred to as a local domain with respect to itself, and the effort-aware network to which the terminal device is directly connected belongs to the local domain regardless of whether it is a home network or a visited network. The effort-aware networks of other operators whose local domains are interconnected by the boundary CA-UPF may be referred to as federation domains, which may be further divided into direct federation domains and indirect federation domains. The direct alliance domain is an alliance domain which is directly connected with the local domain through a boundary CA-UPF, and the indirect alliance domain is an alliance domain which can be reached by the local domain through a multi-hop boundary CA-UPF. Illustratively, as shown in fig. 2, the cross-domain effort-aware network consists of effort-aware network connections of 4 operators with federation relationships. From the perspective of operator 1, the effort-aware network of operator 1 is the local domain, and the effort-aware networks of operators 2, 3, and 4 are the direct federation domains of the effort-aware network of operator 1. From the perspective of operator 4, operator 4's effort-aware network is a local domain, operator 1's effort-aware network is a direct federation domain of operator 4's effort-aware networks, and operator 2's and operator 3's effort-aware networks are indirect federation domains of operator 4's effort-aware networks.

Optionally, in order to guarantee the time delay, it may be limited that the end user can only access the computing services deployed in the local domain and the direct federation domain, so that two-hop time delay is introduced at most compared with the computing awareness network in the local domain. For example, a user of operator 4 can only access the computing services provided by operators 4 and 1, and if access to the computing services provided by operators 2 and 3, too much delay is introduced, resulting in poor business experience.

Referring to fig. 3, a network architecture of a communication system supporting a cross-domain power aware network is provided for the embodiment of the present application, where the network architecture shows a connection relationship between a power aware network of a local domain and a power aware network of a federated domain.

In the user plane, the boundary CA-UPF of the local domain is directly connected with the boundary CA-UPF of the alliance domain so as to realize the message forwarding of the service request and response messages between the two domains and the announcement of the service capability information. Illustratively, as shown in fig. 3, the boundary CA-UPF of the local domain and the boundary CA-UPF of the federation domain may be directly connected via an N19 interface defined by 3 GPP.

And at the control plane, a connection relation is configured between the CMF of the local domain and the CMF of the alliance domain, so that the CMF of the local domain and the CMF of the alliance domain can interactively complete the creation of the cross-domain computing power sensing network. The SMF of the local domain and the SMF of the alliance domain are also configured with a connection relation, and the SMF of the local domain and the SMF of the alliance domain can mutually interact to complete the establishment of an inter-domain forwarding neighbor relation and an inter-domain advertisement neighbor relation between boundary CA-UPF and the establishment of a forwarding tunnel.

It should be noted that the boundary CA-UPF is a special CA-UPF. In the local domain, the boundary CA-UPF is equivalent to the outlet CA-UPF for the inlet CA-UPF in the domain, except that the message received by the boundary CA-UPF is not directly sent to the associated edge computing node, but is sent to the boundary CA-UPF of the computing power perception network of the opposite-end alliance domain. Among the boundary CA-UPFs, the boundary CA-UPF of the local domain is equivalent to the ingress CA-UPF, and the boundary CA-UPF of the federation domain is equivalent to the egress CA-UPF. In the federation domain, the boundary CA-UPF corresponds to an ingress CA-UPF for an egress CA-UPF within the domain.

Each CA-UPF in the cross-domain computing power aware network (including the boundary CA-UPF of the local domain) may be an ingress CA-UPF, and the CA-UPF associated with the edge computing node and the boundary CA-UPF of the local domain may be egress CA-UPF.

Further, it should be understood that the network architecture shown in fig. 3 is merely illustrative. In an actual deployment scenario, the number of the boundary CA-UPFs in the local domain may be one or more, the number of the boundary CA-UPFs in the federation domain may also be one or more, and the local domain may create a cross-domain computing-aware network with one or more federation domains, without limitation.

In a cross-domain computing-aware network, the mechanism for allocating service identities needs to be able to handle the following two cases: 1) Service identity assignment and effort-aware routing of computing services deployed within a carrier's local single network domain; 2) Service identification assignment and effort-aware routing for computing services co-deployed in network domains of multiple operators.

In view of this, in order to implement service identifier allocation in the cross-domain effort-aware network, two types of local SIDMF and global SIDMF are introduced in the present application. The local SIDMF is used to allocate a service identifier to a local computing service, where the local computing service refers to a computing service deployed in a network domain of a single operator, and the service identifier of the local computing service may be referred to as a local service identifier. The global SIDMF is used to allocate a service identifier to a global computing service, where the global computing service refers to a computing service jointly deployed in network domains of multiple operators, and the service identifier of the global computing service may be referred to as a global service identifier. Further, the global SIDMF may have two possible implementation forms of static assignment and dynamic selection, which will be described in detail in the following examples.

In order to effectively distinguish the local service identifier from the global service identifier so that the CA-UPF can identify the type of the computing service according to the service identifier and perform corresponding routing control, the local service identifier and the global service identifier in the present application may have different prefixes. The prefix (prefix) in the local service identification is called local prefix (local prefix), the prefix in the global service identification is called global prefix (global prefix), and the local prefix is different from the global prefix. For example, as shown in fig. 4, the SIDMF of the present application may map a service name (service name) or a function name (function name) (e.g., 123.Cmccapi. Com/image-process/face-detect/[ pic ]) to a service identifier with a local or global prefix represented by an IPv6 anycast address.

Referring to fig. 5a and 5b, another specific example of a cross-domain computing power aware network provided in an embodiment of the present application is shown, which illustrates a connection and forwarding relationship between a local domain and a federation domain in a user plane, and an effect of a service identifier assignment mechanism in the present application on cross-domain computing power routing. In this example, there is a federation relationship between operator 1, operator 2, and operator 3, and the cross-domain effort-aware network is created with operator 1 as the local domain and operators 2 and 3 as federation domains. The computing service is distributed and deployed at the edge computing nodes of 3 operator networks. From the perspective of the operator 1, what is provided with the letter L in the circle is a local computing service, which can only be deployed in the network domain of the local operator 1 and can be assigned with a local service identifier; the circle with the letter G is a global computing service which can be distributed and deployed in network domains of 3 operators and can be distributed with global service identifications.

Fig. 5a shows the intra-domain and cross-domain packet forwarding relationships. And establishing an intra-domain forwarding neighbor relation and an intra-domain forwarding tunnel by the entrance CA-UPF of the local domain and the adjacent exit CA-UPF and boundary CA-UPF in the domain. And establishing an inter-domain forwarding neighbor relation and an inter-domain forwarding tunnel by the boundary CA-UPF of the local domain and the boundary CA-UPF of the direct alliance domain. And establishing an intra-domain forwarding neighbor relation and an intra-domain forwarding tunnel by the boundary CA-UPF of the alliance domain and the adjacent exit CA-UPF in the domain.

Illustratively, when the service request sent by the user of the operator 1 includes the local service identifier, the ingress CA-UPF forwards the service request only to the edge computing node associated with the egress CA-UPF in the local domain, as shown by the dotted arrow in the figure. If the service request sent by the user of the operator 1 includes the global service identifier, as shown by the solid arrow in the figure, the ingress CA-UPF may forward the service request to the edge computing node associated with the egress CA-UPF in the local domain, or may forward the service request to the edge computing node associated with the egress CA-UPF in another federation domain through the boundary CA-UPF.

Figure 5b illustrates the intra-domain and cross-domain advertisement forwarding relationships. The service capability information related to the local computing service can be announced to the corresponding entrance CA-UPF only in the local domain, and the service capability information of the global computing service can be announced to the corresponding entrance CA-UPF in the local domain, converged by the boundary CA-UPF of the alliance domain, then announced to the boundary CA-UPF of the local domain, and then announced to the entrance CA-UPF.

Illustratively, the same global computing service may be deployed decentralized to edge computing nodes in operator 1, operator 2, and operator 3's network domains. The egress CA-UPF in the operator 1's network domain may advertise the service capability information of the local computing service and the service capability information of the global computing service deployed on its associated edge computing node to the ingress CA-UPF in the domain, while the egress CA-UPF in the operator 2 and operator 3's network domains may advertise the service capability information of the global computing service deployed on its associated edge computing node to the boundary CA-UPF in the domain, which is advertised by the boundary CA-UPF to the boundary CA-UPF in the operator 1's network domain through the inter-domain interface and finally to the ingress CA-UPF in the operator 1's network domain.

The network architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application, and as a person of ordinary skill in the art knows that along with the evolution of the communication network architecture and the appearance of a new service scenario, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

For simplicity of description, the following examples illustrate the use of SIDMF as an example. It should be understood that the SIDMF in the following embodiments may be replaced with a service identity management function network element.

Referring to fig. 6, a schematic flow chart of a method for allocating a service identifier in a cross-domain computing power aware network according to an embodiment of the present application is shown, where the method includes:

step S601, the edge computing node sends an allocation request 01 to the first SIDMF, where the allocation request 01 is used to request to allocate a service identifier to the first computing service, and the allocation request 01 includes a service name of the first computing service.

Accordingly, the first SIDF receives an allocation request 01 from an edge compute node.

In this embodiment, the cross-domain effort-aware network may include multiple network domains, and different network domains may be network domains of different operators, for example, intra-domain effort-aware networks of different operators. The first network domain is one of a plurality of network domains included in the cross-domain computing power aware network. The first SIDMF belongs to the first network domain, which may also be referred to as a local SIDMF of the first network domain, and is configured to assign a corresponding service identifier to a local computing service of the first network domain. The local computing service is a computing service which is deployed in a certain network domain in the cross-domain computing power awareness network, only serves the network domain, and does not serve other network domains in the cross-domain computing power awareness network. It will be appreciated that the service scope of the local computing service includes only the network domain in which the local computing service is deployed, and does not include other network domains in the cross-domain computing-aware network.

The service identification of a local computing service may be referred to as a local service identification, which may be routed only within a local scope of the network domain in which the computing service is deployed and may not be routed within other network domains in the cross-domain computing aware network. To facilitate identifying the local service identifier, the local service identifier in the embodiment of the present application may include a corresponding local prefix (local prefix) for indicating that the service identifier is a local service identifier that can be routed within a local network domain that deploys the local computing service identified by the local service identifier. The term "local" may also be understood in a local or other sense, and the service scope may also be referred to as a routing scope or a routing domain, which is not limited in this application.

Alternatively, as shown in fig. 7, the edge computing node may send an allocation request 01 to the NEF, and the NEF forwards the allocation request 01 to the first SIDMF. Optionally, the edge computing node may further send the allocation request 01 after loading or starting the service instance of the first computing service. Illustratively, the MEC platform in the edge computing node may request to load or launch a service instance of the first computing service on the selected EAS, and then, after learning that the service instance of the first computing service is successfully loaded or launched, send an allocation request 01 to the NEF, which forwards the allocation request 01 to the first SIDMF.

Step S602, if the first computing service corresponds to the cross-domain computing power aware network, the first SIDMF obtains a first service identifier allocated to the first computing service, where the first service identifier is used to identify the first computing service in the cross-domain computing power aware network.

In this embodiment, that the first computing service corresponds to the cross-domain computing power aware network may mean that the first computing service is a global computing service in the cross-domain computing power aware network. The global computing service refers to a computing service which is deployed in a certain network domain in the cross-domain computing power awareness network, but can serve a plurality of network domains in the cross-domain computing power awareness network, and the network domains comprise a network domain where the global computing service is deployed and at least one other network domain. It will be appreciated that the service scope of the global computing service may include multiple network domains in a cross-domain computing power aware network. Optionally, the global computing service may also serve all network domains in the cross-domain computing power aware network, that is, the service scope of the global computing service may include all network domains in the cross-domain computing power aware network. For example, if the first computing service is a global computing service, the first computing service may serve a first network domain and a second network domain in a cross-domain computing power aware network, or may also serve all network domains in the cross-domain computing power aware network.

The service identification of the global computing service may be referred to as a global service identification, which may be routed within a global scope of the cross-domain computing power aware network, including all network domains in the cross-domain computing power aware network. In order to facilitate identifying the global service identifier and making it effectively distinguished from the local service identifier, the global service identifier in the embodiment of the present application may include a corresponding global prefix (global prefix) for indicating that the service identifier is a global service identifier, and may be routed within all network domains included in the cross-domain computing awareness network.

Optionally, the allocation request 01 may include service scope (scope) information of the first computing service, where the service scope information is used to indicate a service scope of the first computing service. The first SIDDMF may determine whether the first computing service is a global computing service or a local computing service according to the service scope information, and further determine whether a global service identifier or a local service identifier needs to be allocated to the first computing service. If the service scope information in the allocation request 01 indicates that the service scope of the first computing service includes a plurality of network domains in the cross-domain computing power aware network, the first SIDMF may determine that the first computing service is a global computing service, and a global service identifier needs to be allocated to the cross-domain computing power aware network. If the service scope information in the allocation request 01 indicates that the service scope of the first computing service includes the first network domain, the first SIDMF may determine that the first computing service is a local computing service, and needs to allocate a local service identifier corresponding to the first network domain.

Illustratively, the service scope information may be a piece of indication information in the allocation request 01, for indicating that the first computing service (or the service scope of the first computing service) is local (local) or global (global). For example, the indication information may be a flag bit occupying 1 bit, and when the value of the flag bit is 0, it indicates that the first computing service is local, that is, the first computing service is a local computing service or the service range of the first computing service only includes a local first network domain; when the flag value is 1, the global state is represented, that is, the first computing service is the global computing service or the service range of the first computing service includes the global cross-domain computing power awareness network.

Optionally, the first SIDMF may determine whether the first computing service is a global computing service or a local computing service according to the service name of the first computing service in the allocation request 01, and further determine that a global service identifier or a local service identifier needs to be allocated to the first computing service. For example, if the service name of the first computing service includes certain specific information or conforms to a certain preset format, the first SIDMF may determine that the first computing service is a global computing service, and a global service identifier needs to be allocated corresponding to the cross-domain computing power aware network. Otherwise, the first SIDMF may determine that the first computing service is a local computing service, and the local service identifier needs to be allocated corresponding to the first network domain.

If the first computing service is a global computing service (corresponding to a cross-domain computing power aware network), the first SIDMF may obtain a first service identifier allocated to the first computing service, where the first service identifier is used to identify the first computing service within the cross-domain computing power aware network. Optionally, the first service identifier is used to uniquely identify the first computing service within the cross-domain computing power aware network. As can be appreciated, at this time, the first service identification is a global service identification. As shown in fig. 8, a global prefix may be included in the first service identifier, which is used to indicate that the first service identifier is allowed to be routed within a plurality of network domains included in the cross-domain computing power aware network, or to indicate that the first service identifier is a global service identifier.

In one possible implementation (which will be referred to as implementation 1 below), the first SIDMF may obtain the first service identifier allocated for the first computing service as: the first SIDF assigns a first service identifier to the first computing service through a second SIDF, which is a global SIDF for assigning service identifiers to computing services whose service scope includes multiple network domains in a cross-domain computing power aware network.

Embodiment 1 is directed to a scenario in which the global SIDMF is statically specified. The statically specified global SIDMF means: as shown in fig. 9, the functional roles of the local SIDMF and the global SIDMF are explicitly specified in a period of time, and the local SIDMF of each network domain can allocate the service identification to the global computing service through the same global SIDMF. It should be noted that the global SIDMF may be a separately deployed SIDMF other than the local SIDMF of each network domain in the cross-domain effort-aware network (e.g., may be provided by a third party), or may be a local SIDMF of one of the network domains in the cross-domain effort-aware network, and the local SIDMF of the network domain simultaneously plays a functional role of the global SIDMF. The selection of a local SIDMF for a certain network domain as a global SIDMF may be achieved by management plane configuration and may be changed as needed, but the functional roles of the local SIDMF and the global SIDMF are explicitly specified for a period of time. It should also be noted that there may be one or more global SIDMF, and when there are multiple global SIDMF, the service identifier allocation information may be synchronized among the global SIDMF, so as to meet the requirement of disaster recovery backup or load balancing. Similarly, there may be one or more local SIDMF within a network domain, and service identifier assignment information may also be synchronized between local SIDMF of the same network domain, which is not described in detail below.

As shown in fig. 10, embodiment 1 may include the steps of:

step S1001, the first SIDMF sends an allocation request 02 to the second SIDMF, where the allocation request 02 is used to allocate a service identifier to the first computing service, and the allocation request 02 includes a service name of the first computing service.

Accordingly, the second SIDMF receives the allocation request 02 from the first SIDMF.

In this embodiment 1, the first SIDMF is a local SIDMF of the first network domain, and is only used for allocating the service identifier to the local computing service of the first network domain, but is not used for allocating the service identifier to the global computing service. The second SIDMF is a global SIDMF for assigning a service identification for the global computing service.

Optionally, the allocation request 02 may include service scope information of the first computing service, so that the first SIDMF confirms that the first computing service is the global computing service before allocating the service identifier to the first computing service.

Step S1002, the second SIDMF allocates a first service identifier to the first computing service according to the service name of the first computing service.

For example, the second SIDMF may convert the service name of the first computing service into an initial service identifier that is unique within a global scope of the cross-domain computing power aware network, and then add a global prefix to the initial service identifier to obtain the first service identifier. The initial service identification may be an IPv4/IPv6 anycast (anycast) address. The conversion method may be hash, or calculation based on a specific algorithm, or database matching search, which is not limited in the present application.

Optionally, the second SIDMF may further store a mapping relationship between the service name of the first computing service and the first service identifier.

Step S1003, the second SIDMF sends an allocation response 02 to the first SIDMF, where the allocation response 02 includes the first service identifier.

Accordingly, the first SIDMF receives the allocation response 02 from the second SIDMF, and obtains the first service identification from the allocation response 02.

Optionally, the first SIDMF may further store a mapping relationship between the service name of the first computing service and the first service identifier, so that when the terminal device accessing the first network domain queries the service identifier of the first computing service through the service name of the first computing service, the first SIDMF may provide the first service identifier to the terminal device.

It can be seen that, when the first computing service is a global computing service, since the first SIDMF is a local SIDMF of the first network domain, it does not have a function of assigning a global service identity. Therefore, the first SIDMF may send an allocation request 02 to a second SIDMF serving as a global SIDMF and carrying the service name of the first computing service, so as to request the second SIDMF to allocate a corresponding global service identifier to the first computing service, and return an allocation result to the first SIDMF.

Further, embodiment 1 may further include optional step S1004 of:

in step S1004, the second SIDMF sends an advertisement message 03 to the third SIDMF, where the advertisement message 03 includes the service name and the first service identifier of the first computing service.

Accordingly, the third SIDMF may receive the advertisement message 03 from the second SIDMF, and obtain the service name and the first service identification of the first computing service from the advertisement message 03.

In this embodiment, the third SIDMF belongs to the second network domain, and is a local SIDMF of the second network domain, and is configured to allocate a service identifier to a local computing service of the third network domain. After the third SIDMF receives the advertisement message 03 from the second SIDMF, the third SIDMF may obtain the service name and the first service identifier of the first computing service from the advertisement message 03, and store the mapping relationship between the service name of the first computing service and the first service identifier, so that when an edge computing node in the second network domain subsequently requests to allocate the service identifier to the first computing service, the third SIDMF may query the first service identifier corresponding to the service name according to the service name of the first computing service, and then return the first service identifier to the edge computing node.

It is to be understood that, as the global SIDMF, the second SIDMF may send the advertisement message 03 to local SIDMF of each other network domain except the first network domain in the cross-domain computing power aware network, so as to notify the local SIDMF of each network domain of the first service identifier allocated to the first computing service, so that the first computing service has the same service identifier in each network domain included in the cross-domain computing power aware network. Accordingly, the local SIDMF of each network domain may store the mapping relationship between the service name of the first computing service and the first service identifier, so as to perform the corresponding query in the following. For example, when a local SIDMF of a certain network domain receives a request that is sent by an edge computing node in the network domain and requests for allocating a service identifier for a first computing service, the local SIDMF does not need to request a second SIDMF (i.e., a global SIDMF) to perform global service identifier allocation, but may query a stored mapping relationship according to a service name of the first computing service and return the first service identifier corresponding to the service name to the edge computing node.

In another possible implementation (which will be referred to as implementation 2 below), the first SIDMF obtained the first service identifier allocated for the first computing service may be: the first SIDDMF attempts to obtain permission to assign a global service identification to the first computing service. If the first SIDF obtains the right to assign the service identification to the first computing service, the first SIDF may assign the first service identification to the first computing service according to the service name of the first computing service. If the first SIDMF does not obtain the right to assign the service identifier to the first computing service, but the SIDMF of the other network domain (e.g., the third SIDMF) successfully obtains the right to assign the service identifier to the first computing service, the first SIDMF may receive an advertisement message sent by the third SIDMF, and obtain the first service identifier assigned by the third SIDMF to the first computing service from the advertisement message. The "attempt to acquire" may also be understood as other meanings such as applying, requesting, competing, preempting, contending, etc., and the "right" may also be referred to as an allocation right, which is not limited in the present application.

Embodiment 2 is directed to a scenario where global SIDMF is dynamically selected. The dynamic selection of global SIDDMF refers to: as shown in fig. 11, the local SIDMF of each network domain in the cross-domain effort-aware network can serve as a function role of the global SIDMF, and the local SIDMF of each network domain completes the distribution of the global service identifier through mutual negotiation. As can be understood, since the local SIDMF of each network domain may assume the functional role of the global SIDMF, the purpose of negotiating the local SIDMF of each network domain is to confirm that the local SIDMF of which network domain is specifically used as the global SIDMF for the global service identifier assignment. It should also be noted that, for a scenario of dynamically selecting a global SIDMF, after any local SIDMF temporarily obtaining a functional role of the global SIDMF completes global service identifier assignment and returns the global service identifier assignment to the edge computing node, in addition to the mapping information between the service name and the service identifier needs to be locally stored, an assignment result is also advertised to local SIDMF of other network domains in the cross-domain computing power aware network, so as to synchronize service identifier assignment information, so that the local SIDMF of other network domains can directly provide the assigned service identifier when receiving the same global service identifier assignment request, so as to ensure consistency of global service identifier assignment in all network domains.

As shown in fig. 12, the case where the first SIDMF obtains the right to assign the service identifier to the first computing service in embodiment 2 may include the following steps:

step S1201, the first SIDMF sends an authority request 01 to the third SIDMF, where the authority request 01 is used to request an authority for allocating a service identifier to the first computing service, and the authority request 01 includes a service name of the first computing service.

Accordingly, the third SIDMF receives the permission request 01 from the first SIDMF.

In this embodiment 2, the first SIDMF is a local SIDMF of the first network domain, and may also have a function of a global SIDMF, and may be configured to allocate a service identifier to a global computing service deployed in the first network domain. The third SIDMF is a local SIDMF of the second network domain and may also have the function of a global SIDMF, and may be used to assign a service identity to a global computing service deployed in the second network domain.

The permission request 01 may further include a first comparison parameter, where the first comparison parameter may be determined by the first dmf according to a timestamp and/or a random number generated when the permission request 01 is transmitted. When there are multiple local SIDMF of network domains simultaneously allocating global service identity for the same first computing service, the first comparison parameter may be used to assist in determining which local SIDMF of a network domain is specifically used as the global SIDMF to allocate the global service identity for the first computing service. The first comparison parameter may also be referred to as a first comparison term or by other names, and the present application is not limited thereto.

Step S1202, the third SIDMF sends an authority response 01 to the first SIDMF, where the authority response 01 is used to indicate that the authority for allocating the service identifier to the first computing service by the first SIDMF is accepted.

Accordingly, the first SIDMF receives permission response 01 from the third SIDMF.

In this embodiment 2, if the third SIDMF does not currently need to assign a service identifier to the first computing service, the third SIDMF may send an authority response 01 directly to the first SIDMF, and notify the first SIDMF through the authority response 01: the third SIDMF accepts the right requested by the first SIDMF to assign the service identification for the first computing service.

If the third SIDMF is also simultaneously allocating a service identity to the first computing service, the third SIDMF may send an authority request 02 to the first SIDMF requesting an authority to allocate the service identity to the first computing service, as shown in the following optional step S1203.

Step S1203, the third SIDMF sends an authority request 02 to the first SIDMF, where the authority request 02 is used to request an authority for allocating a service identifier to the first computing service, and the authority request 02 includes a service name of the first computing service.

Accordingly, the first SIDMF receives the permission request 02 from the third SIDMF.

The permission request 02 may further include a second comparison parameter, which is determined by the third SIDMF according to a timestamp and/or a random number generated when the permission request 02 is transmitted, and the function of the second comparison parameter is similar to that of the first comparison parameter. Thus, after the third SIDMF receives the permission request 01 from the first SIDMF and sends the permission request 02, whether to accept the permission requested by the first SIDMF for allocating the service identifier to the first computing service may be determined according to the first comparison parameter in the permission request 01 and the second comparison parameter in the permission request 02. For example, the first comparison parameter and the second comparison parameter may be parameter values obtained by performing some operation according to a timestamp and/or a random number, and the larger the parameter value, the easier the allocation authority is obtained. Thus, the third SIDMF may determine, according to the size of the first comparison parameter and the second comparison parameter, that the third SIDMF determines the right to accept the first SIDMF to assign the service identifier to the first computing service, and notifies the first SIDMF through the right response 01. As another example, the first comparison parameter and the second comparison parameter may be timestamps, the earlier the timestamp represents the earlier the permission request is sent, the easier it is to obtain the assigned permission. In this way, the third SIDMF may determine whether the time indicated by the first comparison parameter is earlier than the time indicated by the second comparison parameter, and if the time indicated by the first comparison parameter is earlier than the time indicated by the second comparison parameter, the third SIDMF may determine the right to accept the first SIDMF to assign the service identifier to the first computing service, and notify the first SIDMF through the right response 01.

Similarly, after the first SIDMF transmits the permission request 01 and receives the permission request 02 from the third SIDMF, whether to accept the permission of the third SIDMF to assign the service identifier to the first computing service may also be determined according to the first comparison parameter in the permission request 01 and the second comparison parameter in the permission request 02. For example, the first comparison parameter and the second comparison parameter may be parameter values obtained by performing some operation according to a timestamp and/or a random number, and the larger the parameter value, the easier the allocation authority is obtained. In this way, the first SIDMF may perform a determination according to the sizes of the first comparison parameter and the second comparison parameter, and if the first comparison parameter is greater than the second comparison parameter, the first SIDMF may determine that the right of the third SIDMF to allocate the service identifier to the first computing service is not accepted, and notify the third SIDMF through the right response 02 in the following optional step S1204. As another example, the first comparison parameter and the second comparison parameter may be timestamps, the earlier the timestamp represents the earlier the permission request is sent, the easier it is to obtain the assignment permission. In this way, the first SIDMF may determine according to the time indicated by the first comparison parameter and the time indicated by the second comparison parameter, and if the time indicated by the first comparison parameter is earlier than the time indicated by the second comparison parameter, the first SIDMF may determine that the authority of the third SIDMF to assign the service identifier to the first computing service is not accepted, and notify the third SIDMF through the authority response 02 in the following optional step S1204.

Step S1204, the first SIDMF sends an authority response 02 to the third SIDMF, where the authority response 02 is used to indicate that the authority of the third SIDMF to allocate the service identifier to the first computing service is not accepted.

Accordingly, the third SIDMF receives the permission response 02 from the first SIDMF.

It should be noted that the sequence of execution of step S1201 and step S1203 is not specifically limited in the present application. That is, since the first SIDMF and the third SIDMF perform independent determination on the global service identifier that needs to be allocated to the first computing service, the first SIDMF may issue the permission request 01 first, and the third SIDMF may issue the permission request 02 first, which is not limited in this application. Similarly, the sequence of executing steps S1202 and S1204 is not limited in this application.

Step S1205, the first SIDMF determines to obtain the right to allocate the service identifier for the first computing service.

The present application exemplarily illustrates, through the above steps S1201 to S1204, a process of performing, in embodiment 2, an authority negotiation between a first SIDMF and local SIDMF of other network domains when the first SIDMF attempts to acquire an authority to allocate a service identifier to a first computing service. It is to be understood that, in an actual application scenario, the first SIDMF may send the above-mentioned permission request 01 to the local SIDMF of each network domain in the cross-domain computing power awareness network, so as to request to acquire the permission for allocating the service identifier to the first computing service. And when the first SIDMF receives an authority response 01 returned by the local SIDMF of all other network domains to indicate acceptance of the authority request 01 of the first SIDMF, the first SIDMF may determine that the authority to assign the service identification to the first computing service is obtained. For example, there may be no need for the local SIDMF of other network domains to allocate the service identifier to the first computing service at this time, or there may be one or more local SIDMF of other network domains that are also allocating the service identifier to the first computing service at this time, but the first SIDMF won the right to allocate the service identifier to the first computing service through the first comparison parameter in the right request 01.

In step S1206, the first SIDMF allocates a first service identifier to the first computing service according to the service name of the first computing service.

For example, the first SIDMF may convert the service name of the first computing service into an initial service identifier that is unique within a global scope of the cross-domain computing power aware network, and then add a global prefix to the initial service identifier to obtain the first service identifier. The initial service identification may be an IPv4/IPv6 anycast (anycast) address. The conversion method may be hash, or calculation based on a specific algorithm, or database matching search, which is not limited in the present application.

Further, in the case that the first SIDMF obtains the right to assign the service identifier to the first computing service in embodiment 2, the following optional step S1207 may be further included:

step S1207, the first SIDMF sends an advertisement message 01 to the third SIDMF, where the advertisement message 01 includes the service name and the first service identifier of the first computing service.

Accordingly, the third SIDMF may receive the advertisement message 01 from the first SIDMF, and obtain the service name of the first computing service and the first service name from the advertisement message 01.

Optionally, the third SIDMF may further store a mapping relationship between the service name of the first computing service and the first service name, so that when the edge computing node in the second network domain requests to allocate the service identifier to the first computing service in the subsequent period, the third SIDMF may query the first service identifier corresponding to the service name according to the service name of the first computing service, and then return the first service identifier to the edge computing node.

It is to be understood that, after the first SIDMF allocates the first service identifier to the first computing service, the first SIDMF may send the advertisement message 01 to local SIDMF of each network domain (including the third SIDMF) except the first network domain in the cross-domain computing power aware network, so as to notify the local SIDMF of each network domain of the first service identifier allocated to the first computing service, so that the first computing service has the same service identifier in each network domain included in the cross-domain computing power aware network. Correspondingly, the local SIDMF of each network domain may store the mapping relationship between the service name of the first computing service and the first service identifier, so as to perform corresponding query in the following, which is not described any further.

As shown in fig. 13, the case where the first SIDMF does not obtain the right to allocate the service identifier to the first computing service in embodiment 2 may include the following steps:

step S1301, the first SIDMF sends an authority request 01 to the third SIDMF, where the authority request 01 is used to request an authority to allocate a service identifier to the first computing service, and the authority request 01 includes a service name of the first computing service.

Accordingly, the third SIDMF receives the rights request 01 from the first SIDMF.

The permission request 01 may further include a first comparison parameter, where the first comparison parameter may be determined by the first SIDMF according to a timestamp and/or a random number generated when the permission request 01 is transmitted. When there are multiple local SIDMF of network domains simultaneously allocating global service identity for the same first computing service, the first comparison parameter may be used to assist in determining which local SIDMF of a network domain is specifically used as the global SIDMF to allocate the global service identity for the first computing service.

Step S1302, the third SIDMF sends an authority response 01 to the first SIDMF, where the authority response 01 is used to indicate that the authority of the first SIDMF to allocate the service identifier to the first computing service is not accepted.

As described above, if the third SIDMF is also distributing the service identifier to the first computing service, this embodiment 2 may further include the following step S1303 and step S1303.

Step S1303, the third SIDMF sends an authority request 02 to the first SIDMF, where the authority request 02 is used to request an authority to allocate a service identifier to the first computing service, and the authority request 02 includes a service name of the first computing service.

The permission request 02 may further include a second comparison parameter, which is determined by a third dmf according to a timestamp and/or a random number generated when the permission request 02 is sent, and the function of the second comparison parameter is similar to that of the first comparison parameter.

In step S1304, the first SIDMF sends an authority response 02 to the third SIDMF, where the authority response 02 is used to indicate that the third SIDMF is accepted to assign the service identifier to the first computing service.

As described above, in this embodiment 2, the first SIDMF may determine whether to accept the authority of the third SIDMF to assign the service identifier to the first computing service according to the first comparison parameter in the authority request 01 and the second comparison parameter in the authority request 02. For example, the first comparison parameter and the second comparison parameter may be parameter values obtained by performing some operation according to a timestamp and/or a random number, and the larger the parameter value, the easier the allocation authority is obtained. As such, if the first comparison parameter is less than the second comparison parameter, the first SIDMF may determine that the right to accept the third SIDMF for assigning the service identifier to the first computing service, and notify the third SIDMF with the right response 02 in step S1404. As another example, the first comparison parameter and the second comparison parameter may be timestamps, the earlier the timestamp represents the earlier the permission request is sent, the easier it is to obtain the assignment permission. As such, if the time indicated by the first comparison parameter is later than the time indicated by the second comparison parameter, the first SIDMF may determine to accept the authority of the third SIDMF to assign the service identifier to the first computing service, and notify the third SIDMF through the authority response 02 in step S1404.

The third SIDMF may also determine whether to accept the permission of the first SIDMF for allocating the service identifier to the first computing service according to the first comparison parameter in the permission request 01 and the second comparison parameter in the permission request 02. For example, the first comparison parameter and the second comparison parameter may be parameter values obtained by performing some operation according to a timestamp and a random number, and a larger parameter value represents that it is easier to obtain the distribution authority. As such, if the first comparison parameter is less than the second comparison parameter, the third SIDMF may determine that the authority of the first SIDMF to assign the service identifier to the first computing service is not accepted, and notify the first SIDMF through the authority response 01 in step S1404. As another example, the first comparison parameter and the second comparison parameter may be timestamps, the earlier the timestamp represents the earlier the permission request is sent, the easier it is to obtain the assigned permission. As such, if the time indicated by the first comparison parameter is later than the time indicated by the second comparison parameter, the third SIDMF may determine not to accept the authority of the first SIDMF to assign the service identifier to the first computing service, and notify the first SIDMF through the authority response 01 in step S1404.

It should be noted that, in the present application, the execution sequence of the above steps S1301 and S1303 is not specifically limited, and the execution sequence of the step S1302 and S1304 is not specifically limited.

Step S1305, the first SIDMF determines that the right to assign the service identifier to the first computing service is not obtained.

The first SIDMF may send the permission request 01 to the local SIDMF of each network domain in the cross-domain computing power aware network, so as to request to obtain the permission for allocating the service identifier to the first computing service. However, as long as the first SIDMF receives the permission response 01 returned by the local SIDMF (e.g., the third SIDMF) of any network domain to indicate that the permission request 01 of the first SIDMF is not accepted, the first SIDMF may determine that the permission to allocate the service identifier to the first computing service is not obtained, and wait for the local SIDMF of other network domains to announce the service identifier allocation result.

Assuming that the third SIDMF obtains the right to assign the service identifier to the first computing service, the third SIDMF may assign the first service identifier to the first computing service according to the service name of the first computing service. For example, the third SIDMF may convert the service name of the first computing service into an initial service identifier unique within a global scope of the cross-domain computing power aware network, and then add a global prefix to the initial service identifier to obtain the first service identifier. The initial service identification may be an IPv4/IPv6 anycast (anycast) address. The conversion method may be hash, or calculation based on a specific algorithm, or search by database matching, which is not limited in this application.

Optionally, the third SIDMF may further store a mapping relationship between the service name of the first computing service and the first service identifier, so that when the terminal device accessing the second network domain queries the service identifier of the first computing service through the service name of the first computing service, the third SIDMF may provide the first service identifier to the terminal device.

Further, the third SIDMF may also inform the first SIDMF of the first service identification allocated for the first computing service through the advertisement message 02 in step S1406 as follows. It is to be appreciated that the third SIDMF may send the advertisement message 02 to the local SIDMF of each of the other network domains in the cross-domain computing power aware network except the second network domain to inform the local SIDMF of each of the other network domains of the first service identification assigned for the first computing service.

In step S1306, the third SIDMF sends an advertisement message 02 to the first SIDMF, where the advertisement message 02 includes the service name and the first service identifier of the first computing service.

Accordingly, the first SIDMF receives the advertisement message 02 from the third SIDMF, and obtains the first service identifier allocated by the third SIDMF for the first computing service from the advertisement message 02.

Optionally, the first SIDMF may further store a mapping relationship between the service name of the first computing service and the first service identifier, so as to be used in a subsequent query.

It follows that when the first computing service is a global computing service, the first SIDMF may also have the function of a global SIDMF, although it is a local SIDMF of the first network domain. However, since the local SIDMF of other network domains also has the function of the global SIDMF, and it is possible that the local SIDMF of other network domains also needs to allocate a service identifier to the first computing service, so to avoid a conflict, the first SIDMF may perform an assignment right negotiation with the local SIDMF of other network domains, and then the local SIDMF of a certain network domain that obtains the assignment right is responsible for allocating the corresponding global service identifier to the first computing service, and the allocation result is posted to the local SIDMF of other network domains, thereby completing the allocation of the global service identifier, so that the first computing service has the same global service identifier in the whole range of the cross-domain computing awareness network.

Step S603, the first SIDMF sends an allocation response 01 to the edge computing node, where the allocation response 01 includes the first service identifier.

Accordingly, the edge compute node receives an allocation response 01 from the first SIDMF.

Alternatively, as shown in fig. 7, the first SIDMF sends an allocation response 01 to the NEF, and the NEF forwards the allocation response 01 to the edge computing node. Further, after obtaining the first service identifier allocated to the first computing service, the edge computing node may also advertise the first service identifier and service capability information related to the first computing service to the associated CA-UPF, and initiate a process of creating an computation power route, so that the computing service corresponding to the local service identifier can only be accessed by users of the local network domain, and the computing service corresponding to the global service identifier can be accessed by users of multiple network domains in the cross-domain computation power aware network.

In this embodiment, the assignment request 01 may be sent through a message, which may be referred to as an assignment request message 01 or a service identifier assignment request 01 or have another name, which is not limited. The assignment response 01 may also be sent via a message, which may be referred to as an assignment response message 01 or a service identification assignment response 01 or by other names, without limitation. The allocation request 02 and the allocation response 02 are similar to each other and will not be described again.

Similarly, the permission request 01 in the embodiment of the present application may also be sent through a message, which may be referred to as a permission request message 01 or an assignment request message 01 or by other names, which is not limited. Permission response 02 may also be sent via a message, which may be referred to as, without limitation, permission response message 01 or assignment response message 01 or by another name. The permission request 02 and the permission response 02 are similar to each other, and are not described in detail.

Referring to fig. 14, a schematic flow chart of another method for allocating a service identifier in a cross-domain computing power aware network according to an embodiment of the present application is shown, where the method includes:

step S1401, the edge computing node sends an allocation request 01 to the first SIDMF, where the allocation request 01 is used to request to allocate a service identifier to the first computing service, and the allocation request 01 includes a service name of the first computing service.

Accordingly, the first SIDMF receives a first allocation request from an edge compute node.

The specific implementation of step S1401 may refer to step S601 above, and is not described again.

Step S1402, if the first computing service corresponds to a first network domain, the first SIDMF allocates a first service identifier to the first computing service according to a service name of the first computing service, where the first service identifier is used to identify the first computing service in the first network domain.

In this embodiment, that the first computing service corresponds to the first network domain may mean that the first computing service is a local computing service in the first network domain.

Optionally, the allocation request 01 may include service scope (scope) information of the first computing service, where the service scope information is used to indicate a service scope of the first computing service. The first SIDMF may determine whether the first computing service is a global computing service or a local computing service according to the service scope information, and further determine whether a global service identifier or a local service identifier needs to be allocated to the first computing service. If the service scope information in the allocation request 01 indicates that the service scope of the first computing service includes the first network domain, the first SIDMF may determine that the first computing service is a local computing service, and needs to allocate a local service identifier corresponding to the first network domain.

Optionally, the first SIDMF may determine whether the first computing service is the global computing service or the local computing service according to the service name of the first computing service in the allocation request 01, and further determine that the global service identifier or the local service identifier needs to be allocated to the first computing service, which is not described again.

It will be appreciated that the local computing service needs to be assigned a local service identification, and thus reference herein to a first service identification is to a local service identification for identifying the first computing service within the first network domain, or for uniquely identifying the first computing service within the first network domain. As shown in fig. 15, the first service identifier may include a local prefix for indicating that the first service identifier is allowed to be routed within the first network domain, or for indicating that the first computing service is a local computing service.

For example, the first SIDMF may convert the service name of the first computing service into an initial service identifier unique within a local scope of the first network domain, and then add a local prefix to the initial service identifier to obtain the first service identifier. The initial service identification may be an IPv4/IPv6 anycast (anycast) address. The conversion method may be hash, or calculation based on a specific algorithm, or database matching search, which is not limited in the present application.

Step S1403, the first SIDMF sends an allocation response 01 to the edge computing node, where the allocation response 01 includes the first service identification.

Accordingly, the edge compute node receives the assignment response 01 from the first SIDDMF.

The specific implementation of step S1403 may refer to step S603 in the above description, and is not described again.

Therefore, the embodiment of the application provides a uniform service identifier distribution mechanism under the cross-operator computing power awareness network environment, and distributes the same service identifier to the same type of edge computing service deployed in different operator network domains, so as to realize the consistent access of the cross-domain edge computing service. Compared with a service identifier distribution mechanism in the environment of a single-domain computing awareness network, the method and the system do not need to add extra interfaces and configuration operations, can realize unified management and control of local service identifiers in the domain and cross-domain global service identifiers at the same time, and facilitate application providers to deploy single-domain edge applications and cross-domain edge applications in a unified manner.

Referring to fig. 16, a schematic structural diagram of a communication device according to an embodiment of the present invention is provided, where the communication device 1600 includes: a transceiver module 1610 and a processing module 1620. The communication device may be configured to implement the functions related to the first service identifier management function network element or the second service identifier management function network element or the edge computing node in any of the above method embodiments. For example, the communication device may be a network device, or may be a chip included in the network device.

Illustratively, when the communication apparatus performs the operation or step corresponding to the first service identifier management function network element in the embodiment of the method shown in fig. 6, the transceiver module 1610 is configured to receive a first allocation request from the edge computing node, the first allocation request being used to request allocation of a service identifier for the first computing service, the first allocation request including a service name of the first computing service, the first service identifier management function belonging to a first network domain, the first network domain being one of a plurality of network domains included in the cross-domain computing power aware network; the processing module 1620 is configured to, if the first computing service corresponds to the cross-domain computing power awareness network, obtain a first service identifier allocated to the first computing service, where the first service identifier is used to identify the first computing service in the cross-domain computing power awareness network; the transceiving module 1610 is further configured to send a first allocation response to the edge computing node, where the first allocation response includes the first service identifier. Optionally, the first service identifier is used to uniquely identify the first computing service within the cross-domain computing power aware network.

In one possible design, the first allocation request further includes service scope information for the first computing service; the processing module 1620 is further configured to determine that the first computing service corresponds to a cross-domain computing-aware network if the service scope information indicates that the service scope of the first computing service includes a plurality of network domains in the cross-domain computing-aware network.

In one possible design, the processing module 1620 is specifically configured to: sending a second allocation request to a second service identifier management function network element through the transceiving module 1610, where the second allocation request is used to request allocation of a service identifier to the first computing service, and the second allocation request includes a service name of the first computing service; and receives a second allocation response from the second service identity management function network element, the second allocation response including the first service identity, through the transceiving module 1610.

In one possible design, the processing module 1620 is specifically configured to: obtaining a right to assign a service identifier to the first computing service; a first service identification is assigned to the first computing service based on a service name of the first computing service.

In one possible design, the transceiver module 1610 is further configured to send a first advertisement message to a third service identifier management function network element, where the first advertisement message includes a service name of the first computing service and a first service identifier, and the third service identifier management function belongs to a second network domain, which is another network domain included in the cross-domain computing power awareness network except for the first network domain.

In one possible design, the transceiver module 1610 is further configured to: sending a first permission request to a third service identifier management function network element, wherein the first permission request is used for requesting permission of service identifier allocation for the first computing service, the first permission request comprises a service name of the first computing service, the third service identifier management function network element belongs to a second network domain, and the second network domain is another network domain except the first network domain included in the cross-domain computing power awareness network; and receiving a first permission response from the third service identification management function network element, wherein the first permission response is used for indicating that the first service identification management function network element is accepted to distribute the service identification to the first computing service.

In one possible design, the transceiver module 1610 is further configured to: receiving a second permission request from a third service identifier management function network element, wherein the second permission request is used for requesting permission of service identifier allocation for the first computing service, and the second permission request comprises a service name of the first computing service; and sending a second permission response to the third service identifier management function network element, wherein the second permission response is used for indicating that the permission of the third service identifier management function network element for distributing the service identifier for the first computing service is not accepted.

In one possible design, the first permission request includes a first comparison parameter, and the second permission request includes a second comparison parameter; the processing module 1620 is further configured to determine, according to the first comparison parameter and the second comparison parameter, that the permission for the third service identifier management function network element not to be accepted to allocate the service identifier to the first computing service is allocated.

In one possible design, the processing module 1620 is specifically configured to: receiving a second advertisement message from a third service identifier management function network element through the transceiving module 1610, and acquiring a first service identifier according to the second advertisement message; the second announcement message includes a service name and a first service identifier of the first computing service, the third service identifier management function network element belongs to a second network domain, and the second network domain is another network domain except the first network domain included in the cross-domain computing power awareness network.

In one possible design, the transceiver module 1610 is further configured to: sending a first permission request to a third service identifier management function network element, wherein the first permission request is used for requesting permission of service identifier allocation for the first computing service, the first permission request comprises a service name of the first computing service, the third service identifier management function network element belongs to a second network domain, and the second network domain is another network domain except the first network domain included in the cross-domain computing power awareness network; and receiving a first permission response from the third service identifier management function network element, wherein the first permission response is used for indicating that the permission of the first service identifier management function network element for allocating the service identifier to the first computing service is not accepted.

In one possible design, the transceiver module 1610 is further configured to: receiving a second permission request from a third service identifier management function network element, wherein the second permission request is used for requesting permission of allocating service identifiers for the first computing service, and the second permission request comprises a service name of the first computing service; and sending a second permission response to the third service identifier management function network element, wherein the second permission response is used for indicating the permission of receiving the service identifier distributed by the third service identifier management function network element for the first computing service.

In one possible design, the first permission request includes a first comparison parameter, and the second permission request includes a second comparison parameter; the processing module 1620 is further configured to determine, according to the first comparison parameter and the second comparison parameter, that the third service identifier management function network element is allowed to assign the service identifier to the first computing service.

In one possible design, a global prefix is included in the first service identification, the global prefix indicating that the first service identification is allowed to be routed within a plurality of network domains included in the cross-domain effort-aware network.

When the communication apparatus performs the operation or step corresponding to the second service identifier management function network element in the method embodiment shown in fig. 10, the transceiver module 1610 is configured to receive a second allocation request from the first service identifier management function network element, where the second allocation request is used to request to allocate a service identifier to the first computing service, the second allocation request includes a service name of the first computing service, the first service identifier management function network element belongs to a first network domain, and the first network domain is one of a plurality of network domains included in the cross-domain computing power awareness network; the processing module 1620 is configured to assign a first service identifier to the first computing service according to a service name of the first computing service, where the first service identifier is used to identify the first computing service in the cross-domain computing power awareness network; the transceiving module 1610 is configured to send a second allocation response to the first service identifier management function network element, where the second allocation response includes the first service identifier. Optionally, the first service identifier is used to uniquely identify the first computing service within the cross-domain computing power aware network.

In one possible design, a global prefix is included in the first service identification, the global prefix indicating that the first service identification is allowed to be routed within a plurality of network domains included in the cross-domain power aware network.

In one possible design, the transceiver module 1610 is configured to send a third advertisement message to a third service identifier management function network element, where the third advertisement message includes the service name and the first service identifier of the first computing service, and the third service identifier management function belongs to a second network domain, and the second network domain is another network domain included in the cross-domain computing power aware network except for the first network domain. Optionally, the third service identifier management function network element is configured to allocate a service identifier for the computing service of the second network domain in the service range.

When the communication device performs the operations or steps of the corresponding edge computing node in the method embodiment shown in fig. 6, the transceiving module 1610 is configured to: sending a first allocation request to a first service identifier management function network element, wherein the first allocation request is used for requesting to allocate a service identifier for a first computing service, the first allocation request comprises a service name of the first computing service, the first service identifier management function network element belongs to a first network domain, the first network domain is one of a plurality of network domains included in a cross-domain computing power sensing network, and the first computing service corresponds to the cross-domain computing power sensing network; a first allocation response is received from the first service identification management function network element, the first allocation response including a first service identification for identifying a first computing service within the cross-domain computing-aware network.

In one possible design, the first computing service corresponds to a cross-domain computing power aware network, comprising: the first allocation request further includes service scope information for the first computing service indicating that a service scope of the first computing service includes a plurality of network domains in the cross-domain effort-aware network.

In one possible design, a global prefix is included in the first service identification, the global prefix indicating that the first service identification is allowed to be routed within all network domains included in the cross-domain power aware network.

When the communication apparatus performs the operation or step corresponding to the first service identifier management function network element in the method embodiment shown in fig. 14, the transceiver module 1610 is configured to receive a first allocation request from the edge computing node, where the first allocation request is used to request that a service identifier is allocated to a first computing service, the first allocation request includes a service name of the first computing service, the first service identifier management function network element belongs to a first network domain, and the first network domain is one of a plurality of network domains included in the cross-domain computing power awareness network; the processing module 1620 is configured to, if the first computing service corresponds to a first network domain, allocate a first service identifier according to a service name of the first computing service, where the first service identifier is used to identify the first computing service in the first network domain; the transceiving module 1610 is further configured to send a first allocation response to the edge computing node, where the first allocation response includes the first service identifier. Optionally, the first service identifier is used to uniquely identify the first computing service within the first network domain.

In one possible design, the first allocation request further includes service scope information for the first computing service; the processing module 1620 is further configured to determine that the first computing service corresponds to the first network domain if the service range information indicates that the service range of the first computing service is the first network domain.

In one possible design, the first service identification includes a local prefix therein, the local prefix indicating that the first service identification is allowed to be routed within the first network domain.

Optionally, the first service identifier management function network element is configured to allocate a service identifier to the computing service of the first network domain for the service scope.

When the communication apparatus performs the operation or step corresponding to the edge computing node in the method embodiment shown in fig. 14, the transceiver module 1610 is configured to send a first allocation request to a first service identifier management function network element, where the first allocation request is used to request to allocate a service identifier to a first computing service, the first allocation request includes a service name of the first computing service, the first service identifier management function network element belongs to a first network domain, the first network domain is one of multiple network domains included in a cross-domain computing power aware network, and the first computing service corresponds to the first network domain; a first allocation response is received from the first service identification management function network element, the first allocation response including a first service identification identifying a first computing service within the first network domain. Optionally, the first service identifier is used to uniquely identify the first computing service within the first network domain.

In one possible design, the first computing service corresponds to the first network domain and includes: the first allocation request further includes service scope information for the first computing service indicating that a service scope of the first computing service is the first network domain.

The processing module 1620 may be implemented by at least one processor or processor-related circuit component, and the transceiver module 1610 may be implemented by at least one transceiver or transceiver-related circuit component or communication interface. The operations and/or functions of the modules in the communication apparatus are respectively for implementing the corresponding flows of the methods shown in fig. 6 to fig. 15, and are not described herein again for brevity. Optionally, the communication device may further include a storage module, which may be configured to store data and/or instructions, and the transceiver module 1610 and/or the processing module 1620 may read the data and/or instructions in the access module, so as to enable the communication device to implement the corresponding method. The storage module may be implemented, for example, by at least one memory.

The storage module, the processing module and the transceiver module may be separated, or all or part of the modules may be integrated, for example, the storage module and the processing module are integrated, or the processing module and the transceiver module are integrated.

Please refer to fig. 17, which is a schematic structural diagram of a communication device according to an embodiment of the present application. The communication device may be a network device or a device capable of supporting the network device to implement the corresponding function in the method embodiment, and may be used to implement the function corresponding to the first service identifier management function network element, the second service identifier management function network element, or the edge computing node in the method embodiment.

The communication device 1700 may include a processor 1701, a communication interface 1702, and a memory 1703. The communication interface 1702 is used for communicating with other devices through a transmission medium, and the communication interface 1702 may be a transceiver, and may also be an interface circuit, such as a transceiver circuit, a transceiver chip, and the like. The memory 1703 is used to store program instructions and/or data, and the processor 1701 is used to execute the program instructions stored in the memory 1703, thereby implementing the methods in the above-described method embodiments. Optionally, the memory 1703 is coupled to the processor 1701, and the coupling is an indirect coupling or communication connection between devices, units or modules, which may be electrical, mechanical or other, for information exchange between the devices, units or modules.

In one embodiment, the communication interface 1702 may be specifically configured to perform the operations of the transceiver module 1610, and the processor 1701 may be specifically configured to perform the operations of the processing module 1620, which will not be described herein again.

The embodiment of the present application does not limit the specific connection medium among the communication interface 1702, the processor 1701, and the memory 1703. In the embodiment of the present application, the memory 1703, the processor 1701, and the communication interface 1702 are connected by the bus 1704 in fig. 17, the bus is indicated by a thick line in fig. 17, and the connection manner between other components is merely illustrative and not limited. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 17, but this does not mean only one bus or one type of bus.

An embodiment of the present application further provides a chip system, including: a processor coupled to a memory for storing a program or instructions which, when executed by the processor, cause the system-on-chip to implement the method of the corresponding terminal device or the method of the corresponding network device in any of the above method embodiments.

Optionally, the system on a chip may have one or more processors. The processor may be implemented by hardware or by software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory.

Optionally, the memory in the system on chip may also be one or more. The memory may be integrated with the processor or may be separate from the processor, which is not limited in this application. For example, the memory may be a non-transitory processor, such as a read-only memory (ROM), which may be integrated on the same chip as the processor or separately disposed on different chips, and the application does not specifically limit the type of the memory and the arrangement of the memory and the processor.

The chip system may be a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), a system on chip (SoC), a Central Processor Unit (CPU), a Network Processor (NP), a Digital Signal Processor (DSP), a Microcontroller (MCU), a Programmable Logic Device (PLD) or other integrated chips.

It will be appreciated that the steps of the above described method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in a processor.

The embodiments of the present application further provide a computer-readable storage medium, where the computer-readable instructions are stored, and when the computer reads and executes the computer-readable instructions, the computer is caused to execute the method in any of the method embodiments.

The embodiments of the present application further provide a computer program product, which when read and executed by a computer, enables the computer to execute the method in any one of the method embodiments.

The embodiment of the present application further provides a communication system, where the communication system includes a first service identifier management function network element and an edge computing node. The first service identifier management function network element is a local service identifier management function network element of a first network domain included in the cross-domain computing power awareness network, and is configured to allocate a corresponding service identifier (i.e., a local service identifier) to a local computing service deployed in the first network domain.

In a possible design, the communication system further includes a second service identifier management function network element, where the second service identifier management function network element is a global service identifier management function network element in the cross-domain computing power aware network, and is configured to allocate corresponding service identifiers (i.e., global service identifiers) to global computing services that can be deployed in multiple network domains of the cross-domain computing power aware network.

Optionally, the communication system further includes a third service identifier management function network element, where the third service identifier management function network element is a local service identifier management function network element of the second network domain included in the cross-domain computing power awareness network, and is configured to allocate a corresponding service identifier (that is, a local service identifier) to a local computing service deployed in the second network domain.

In another possible design, the communication system further includes a third service identifier management function network element, where the third service identifier management function network element is a local service identifier management function network element of the second network domain included in the cross-domain computing power awareness network, and is configured to allocate a corresponding service identifier (that is, a local service identifier) to a local computing service deployed in the second network domain.

Moreover, the first service identifier management function network element and the third service identifier management function network element may have a function of a global service identifier management function network element while allocating a service identifier to a local computing service deployed in a local network domain. When a service identifier is allocated to a specific global computing service, the first service identifier management function network element and the third service identifier management function network element may determine who assumes the function of the global service identifier management function network element through mutual negotiation, so as to specifically execute allocation of the global service identifier.

It should be understood that the processor referred to in the embodiments of the present application may be a CPU, but may also be other general purpose processors, DSPs, ASICs, FPGAs, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It will also be appreciated that the memory referred to in the embodiments herein may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile memory may be a ROM, a Programmable Read Only Memory (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, synchronous Link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

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

It should be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the various numerical references mentioned in the various embodiments of the present application are merely for convenience of description and differentiation, and the serial numbers of the above-mentioned processes or steps do not imply any order of execution, and the execution order of the processes or steps should be determined by their functions and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one type of logical functional division, and other divisions may be realized in practice, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions may be stored in a computer-readable storage medium if they are implemented in the form of software functional units and sold or used as separate products. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk or an optical disk, and various media capable of storing program codes.

In various embodiments of the present application, unless otherwise specified or conflicting, terms and/or descriptions between different embodiments have consistency and may be mutually referenced, and technical features in different embodiments may be combined to form a new embodiment according to their inherent logical relationships.

Claims

1. A method for service identifier assignment in a cross-domain computing power aware network, the method comprising:

a first service identifier management function network element receives a first allocation request from an edge computing node, wherein the first allocation request is used for requesting allocation of a service identifier for a first computing service, the first allocation request comprises a service name of the first computing service, the first service identifier management function belongs to a first network domain, and the first network domain is one of a plurality of network domains included in a cross-domain computing power awareness network;

if the first computing service corresponds to the cross-domain computing power awareness network, the first service identifier management function network element obtains a first service identifier allocated to the first computing service, where the first service identifier is used to identify the first computing service in the cross-domain computing power awareness network;

and the first service identifier management function network element sends a first allocation response to the edge computing node, wherein the first allocation response comprises the first service identifier.

2. The method of claim 1, wherein the first allocation request further comprises service scope information for the first computing service;

the method further comprises the following steps:

if the service range information indicates that the service range of the first computing service includes a plurality of network domains in the cross-domain computing power aware network, the first service identifier management function network element determines that the first computing service corresponds to the cross-domain computing power aware network.

3. The method according to claim 1 or 2, wherein the obtaining, by the first service identifier management function network element, the first service identifier allocated for the first computing service comprises:

the first service identification management function network element sends a second allocation request to a second service identification management function network element, wherein the second allocation request is used for requesting allocation of a service identification to the first computing service, and the second allocation request comprises a service name of the first computing service;

and the first service identifier management function network element receives a second allocation response from the second service identifier management function network element, wherein the second allocation response includes the first service identifier, and the second service identifier management function network element is configured to allocate service identifiers for computing services whose service ranges include multiple network domains in the cross-domain computing power aware network.

4. The method according to claim 1 or 2, wherein the obtaining, by the first service identifier management function network element, the first service identifier allocated for the first computing service comprises:

the first service identifier management function network element obtains the authority of distributing the service identifier for the first computing service;

and the first service identifier management function network element distributes the first service identifier for the first computing service according to the service name.

5. The method of claim 4, further comprising:

the first service identifier management function network element sends a first advertisement message to a third service identifier management function network element, where the first advertisement message includes the service name of the first computing service and the first service identifier, the third service identifier management function belongs to a second network domain, and the second network domain is another network domain included in the cross-domain computing power awareness network except for the first network domain.

6. The method according to claim 4 or 5, wherein the obtaining, by the first service identifier management function network element, the right to assign a service identifier to the first computing service comprises:

the first service identification management function network element sends a first permission request to a third service identification management function network element, the first permission request is used for requesting permission of service identification distribution for the first computing service, the first permission request comprises a service name of the first computing service, the third service identification management function network element belongs to a second network domain, and the second network domain is another network domain except the first network domain included in the cross-domain computing power awareness network;

and the first service identifier management function network element receives a first permission response from the third service identifier management function network element, wherein the first permission response is used for indicating that the permission of the first service identifier management function network element for allocating the service identifier for the first computing service is accepted.

7. The method of claim 6, wherein the first service identifier management function network element obtains a right to assign a service identifier to the first computing service, further comprising:

the first service identifier management function network element receives a second permission request from the third service identifier management function network element, where the second permission request is used to request permission for allocating a service identifier to the first computing service, and the second permission request includes a service name of the first computing service;

and the first service identifier management function network element sends a second permission response to the third service identifier management function network element, wherein the second permission response is used for indicating that the permission of the third service identifier management function network element for distributing the service identifier to the first computing service is not accepted.

8. The method of claim 7, wherein the first permission request includes a first comparison parameter, wherein the second permission request includes a second comparison parameter, and wherein the method further comprises:

and the first service identifier management function network element determines that the permission of allocating the service identifier to the first computing service by the third service identifier management function network element is not accepted according to the first comparison parameter and the second comparison parameter.

9. The method according to claim 1 or 2, wherein the obtaining, by the first service identifier management function network element, the first service identifier allocated for the first computing service comprises:

the first service identifier management function network element receives a second advertisement message from a third service identifier management function network element, and acquires the first service identifier according to the second advertisement message, wherein the second advertisement message includes a service name of the first computing service and the first service identifier, the third service identifier management function network element belongs to a second network domain, and the second network domain is another network domain other than the first network domain included in the cross-domain computing power awareness network.

10. The method of claim 9, further comprising:

and the first service identifier management function network element receives a first permission response from the third service identifier management function network element, where the first permission response is used to indicate that permission for allocating a service identifier to the first computing service by the first service identifier management function network element is not accepted.

11. The method of claim 10, further comprising:

the first service identifier management function network element receives a second permission request from the third service identifier management function network element, wherein the second permission request is used for requesting permission for allocating a service identifier to the first computing service, and the second permission request comprises a service name of the first computing service;

and the first service identifier management function network element sends a second permission response to the third service identifier management function network element, wherein the second permission response is used for indicating that the permission of the third service identifier management function network element for distributing the service identifier to the first computing service is accepted.

12. The method of claim 11, wherein the first permission request comprises a first comparison parameter, and wherein the second permission request comprises a second comparison parameter;

the method further comprises the following steps:

and the first service identifier management function network element determines, according to the first comparison parameter and the second comparison parameter, to accept the right of the third service identifier management function network element to allocate the service identifier to the first computing service.

13. The method according to any of claims 1 to 12, wherein a global prefix is included in the first service identity, the global prefix indicating that the first service identity is allowed to be routed within a plurality of network domains comprised by the cross-domain computing power aware network.

14. A method for allocating service identifiers in a cross-domain effort-aware network, the method comprising:

a second service identifier management function network element receives a second allocation request from a first service identifier management function network element, wherein the second allocation request is used for requesting allocation of a service identifier for a first computing service, the second allocation request includes a service name of the first computing service, the first service identifier management function network element belongs to a first network domain, and the first network domain is one of a plurality of network domains included in a cross-domain computing power awareness network;

the second service identifier management function network element allocates a first service identifier for the first computing service according to the service name, wherein the first service identifier is used for identifying the first computing service in the cross-domain computing power awareness network;

and the second service identification management function network element sends a second allocation response to the first service identification management function network element, wherein the second allocation response comprises the first service identification.

15. The method of claim 14, wherein a global prefix is included in the first service identifier, and wherein the global prefix indicates that the first service identifier is allowed to be routed within a plurality of network domains included in the cross-domain effort-aware network.

16. The method according to claim 14 or 15, further comprising:

the second service identifier management function network element sends a third advertisement message to a third service identifier management function network element, where the third advertisement message includes the service name of the first computing service and the first service identifier, the third service identifier management function belongs to a second network domain, and the second network domain is another network domain included in the cross-domain computing power awareness network except the first network domain.

17. A method for allocating service identifiers in a cross-domain effort-aware network, the method comprising:

an edge computing node sends a first allocation request to a first service identifier management function network element, wherein the first allocation request is used for requesting to allocate a service identifier for a first computing service, the first allocation request comprises a service name of the first computing service, the first service identifier management function network element belongs to a first network domain, the first network domain is one of a plurality of network domains included in a cross-domain computing power awareness network, and the first computing service corresponds to the cross-domain computing power awareness network;

the edge computing node receives a first allocation response from the first service identification management function network element, the first allocation response including a first service identification for identifying the first computing service within the cross-domain computing power aware network.

18. The method of claim 17, wherein the first computing service corresponds to the cross-domain computing power aware network, and wherein the method comprises:

the first allocation request further includes service scope information for the first computing service indicating that a service scope of the first computing service includes a plurality of network domains in the cross-domain computing-aware network.

19. The method according to claim 17 or 18, wherein a global prefix is included in the first service identity, wherein the global prefix indicates that the first service identity is allowed to be routed within all network domains included in the cross-domain effort-aware network.

20. A method for service identifier assignment in a cross-domain computing power aware network, the method comprising:

a first service identifier management function network element receives a first allocation request from an edge computing node, wherein the first allocation request is used for requesting allocation of a service identifier for a first computing service, the first allocation request comprises a service name of the first computing service, the first service identifier management function network element belongs to a first network domain, and the first network domain is one of a plurality of network domains included in a cross-domain computing power awareness network;

if the first computing service corresponds to the first network domain, the first service identifier management function network element allocates a first service identifier to the computing service according to the service name, wherein the first service identifier is used for identifying the first computing service in the first network domain;

21. The method of claim 20, wherein the first allocation request further comprises service scope information for the first computing service;

the method further comprises the following steps:

if the service range information indicates that the service range of the first computing service is the first network domain, the first service identifier management function network element determines that the first computing service corresponds to the first network domain.

22. The method according to claim 20 or 21, wherein a local prefix is included in the first service identity, the local prefix indicating that the first service identity is allowed to be routed within the first network domain.

23. A method for service identifier assignment in a cross-domain computing power aware network, the method comprising:

an edge computing node sends a first allocation request to a first service identifier management function network element, wherein the first allocation request is used for requesting to allocate a service identifier for a first computing service, the first allocation request comprises a service name of the first computing service, the first service identifier management function network element belongs to a first network domain, the first network domain is one of a plurality of network domains included in a cross-domain computing power awareness network, and the first computing service corresponds to the first network domain;

the edge computing node receives a first allocation response from the first service identification management function network element, the first allocation response including a first service identification, the first service identification identifying the first computing service within the first network domain.

24. The method of claim 23, wherein the first computing service corresponds to the first network domain and comprises:

the first allocation request further includes service scope information of the first computing service, the service scope information indicating that a service scope of the first computing service is the first network domain.

25. The method according to claim 23 or 24, wherein a local prefix is included in the first service identity, the local prefix indicating that the first service identity is allowed to be routed within the first network domain.

26. A communications apparatus, comprising at least one processor coupled with at least one memory:

the at least one processor configured to execute computer programs or instructions stored in the at least one memory to cause the apparatus to perform the method of any of claims 1-13, or 20-22.

27. An apparatus for communication, the apparatus comprising at least one processor coupled with at least one memory:

the at least one processor to execute computer programs or instructions stored in the at least one memory to cause the apparatus to perform the method of any of claims 14-16.

28. An apparatus for communication, the apparatus comprising at least one processor coupled with at least one memory:

the at least one processor configured to execute computer programs or instructions stored in the at least one memory to cause the apparatus to perform the method of any of claims 17-19, or 23-25.

29. A communication device comprising a processor and interface circuitry;

the interface circuit is used for interacting code instructions or data with the processor;

the processor is configured to perform the method of any one of claims 1 to 13, or 20 to 22.

30. A communication device comprising a processor and interface circuitry;

the processor is configured to perform the method of any one of claims 14 to 16.

31. A communication device comprising a processor and interface circuitry;

the processor is configured to perform the method of any one of claims 17 to 19, or 23 to 25.

32. A computer-readable storage medium storing instructions that, when executed, cause the method of any one of claims 1 to 25 to be implemented.

33. A computer program product, characterized in that it comprises instructions which, when executed, cause the method according to any one of claims 1 to 25 to be implemented.

34. A communication system, characterized in that the communication system comprises one or more of the following communication devices:

a first service identifier management function network element, a second service identifier management function network element or an edge computing node;

wherein the first service identity management function network element is configured to perform the method of any of claims 1 to 13;

the second service identity management function network element is configured to perform the method of any of claims 14 to 16;

the edge computing node is configured to perform the method of any of claims 17 to 19.

35. A communication system, comprising a first service identification management function network element and an edge computing node;

wherein the first service identity management function network element is configured to perform the method of any of claims 20 to 22;

the edge computing node is configured to perform the method of any of claims 23 to 25.