WO2022228460A1 - Procédé d'attribution d'identifiant de service dans un réseau à partage de ressources informatiques inter-domaine, et dispositif de communication - Google Patents

Procédé d'attribution d'identifiant de service dans un réseau à partage de ressources informatiques inter-domaine, et dispositif de communication Download PDF

Info

Publication number
WO2022228460A1
WO2022228460A1 PCT/CN2022/089532 CN2022089532W WO2022228460A1 WO 2022228460 A1 WO2022228460 A1 WO 2022228460A1 CN 2022089532 W CN2022089532 W CN 2022089532W WO 2022228460 A1 WO2022228460 A1 WO 2022228460A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
computing
domain
management function
network
Prior art date
Application number
PCT/CN2022/089532
Other languages
English (en)
Chinese (zh)
Inventor
王岩
胡伟华
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2022228460A1 publication Critical patent/WO2022228460A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring

Definitions

  • 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 aware network.
  • a basic problem is to implement service identifier-based routing. and message forwarding. This requires that, no matter how the same type of computing service is deployed and how many instances it runs, it needs to be assigned a service ID that can identify the computing service, so as to achieve consistent cross-domain routing. Therefore, designing a service identity allocation and discovery mechanism is a key issue in realizing a cross-domain computing power-aware network.
  • the present application provides a service identifier allocation method and a communication device in a cross-domain computing power-aware network, which are used to allocate a corresponding service identifier for a computing service deployed in a cross-domain computing power-aware network, and provide it to an edge computing node.
  • the embodiments of the present application provide a method for allocating service identifiers in a cross-domain computing power-aware network.
  • a component eg, a chip or circuit
  • the method includes: a first service identity management function network element receives a first allocation request from an edge computing node, where the first allocation request is used to request allocation of a service identity for a first computing service, and the first allocation request includes the first computing service , the first service identifier management function belongs to the first network domain, and the first network domain is one of multiple network domains included in the cross-domain computing power-aware network; if the first computing service corresponds to the cross-domain computing power-aware network, The first service identifier management function network element obtains a first service identifier allocated for 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; the first service identifier management function network element Send a first allocation response to the edge computing node, where the first allocation response includes the first service identifier.
  • the first service identifier is used to uniquely identify the first computing service in the cross-domain computing power aware network.
  • the first service identifier management function in the first network domain can obtain the corresponding first service identifier for the first computing service corresponding to the cross-domain computing power aware network, and return the first service identifier to the edge. calculate node. Since the first service identifier can identify the first computing service in the cross-domain computing power-aware network, the above method can support deploying the first computing service in multiple network domains of the cross-domain computing power-aware network, and based on the first computing service The service identifier implements dynamic computing power routing and packet forwarding for the first computing service.
  • the first allocation request further includes service scope information of the first computing service; the method further includes: if the service scope information indicates that the service scope of the first computing service includes cross-domain computing power perception For multiple network domains in the network, the first service identifier management function network element determines that the first computing service corresponds to the cross-domain computing power aware network.
  • the first service identifier management function in the first network domain can identify, according to the service scope information of the first computing service, that the first computing service corresponds to the cross-domain computing power-aware network, which belongs to the cross-domain computing power.
  • the global computing service deployed in the network is sensed, and a first service identifier allocated for the first computing service is obtained in a corresponding manner.
  • obtaining the first service identifier allocated for the first computing service by the first service identifier management function network element includes: the first service identifier management function network element reporting to the second service identifier
  • the management function network element sends a second allocation request, the second allocation request is used to request to allocate a service identifier for the first computing service, the second allocation request includes the service name of the first computing service;
  • the first service identifier management function network element receives The second allocation response from the second service identification management function network element, the second allocation response includes the first service identification, wherein the second service identification management function network element Compute services for multiple network domains assign service identities.
  • the first service identification management function network element may request the second service identification management function network.
  • the element assigns a corresponding service identifier to the first computing service, and receives an assignment result from the second service identifier management function network element.
  • the above process of allocating a service identifier for the first computing service is applicable to the scenario of statically specifying the global service identifier management function network element.
  • the management function network element that is, the second service identity management function network element mentioned in this application, is responsible for the second service identity management function network element corresponding to the cross-domain computing power-aware network, and the service scope includes cross-domain computing power
  • the global computing services of multiple network domains in the aware network are assigned corresponding service identifiers.
  • obtaining the first service identifier allocated for the first computing service by the first service identifier management function network element includes: obtaining the first service identifier management function network element as the first computing service.
  • the service assigns the authority of the service identifier; the first service identifier management function network element assigns the first service identifier to the first computing service according to the service name of the first computing service.
  • the method further includes: the first service identity management function network element sends a first announcement message to the third service identity management function network element, where the first announcement message includes the first calculation The service name and first service identifier of the service, and the third service identifier management function belongs to the 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 aware network.
  • the first service identifier management function network element obtains the authority to assign the service identifier to the first computing service, including: the first service identifier management function network element manages the third service identifier
  • the functional network element sends a first permission request, where the first permission request is used to request permission to assign a service identifier to the first computing service, the first permission request includes the service name of the first computing service, and the third service identifier manages the functional network
  • the element belongs to the 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-aware network; the network element of the first service identification management function receives information from the third service identification management function A first permission response of the network element, where the first permission response is used to indicate that the network element accepts the permission of the first service identifier management function to assign a service identifier to the first computing service.
  • the first service identifier management function network element obtains the authority to assign a service identifier to the first computing service, and further includes: the first service identifier management function network element receives data from the third service A second permission request from the network element of the identity management function, the second permission request is used to request the permission to assign a service identity to the first computing service, and the second permission request includes the service name of the first computing service; the first service identity management function The network element sends a second authority response to the third service identification management function network element, where the second authority response is used to indicate that the third service identification management function network element does not accept the authority to assign the service identification to the first computing service.
  • the first permission request includes a first comparison parameter
  • the second permission request includes a second comparison parameter
  • the method further includes: the first service identifier management function network element according to the first comparison The parameter is compared with the second parameter, and it is determined that the authority of the third service identification management function network element to assign the service identification to the first computing service is not accepted.
  • obtaining, by the first service identifier management function network element, the first service identifier allocated for the first computing service includes: the first service identifier management function network element receiving information from the first service identifier management function network element.
  • the 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 aware network.
  • the method further includes: the first service identity management function network element sends a first permission request to the third service identity management function network element, where the first permission request is used to request a
  • the first computing service assigns the permission of the service identifier, the first permission request includes the service name of the first computing service, the third service identifier management function network element belongs to the second network domain, and the second network domain is cross-domain computing power perception another network domain other than the first network domain included in the network;
  • the first service identity management function network element receives a first permission response from the third service identity management function network element, where the first permission response is used to indicate that it does not accept
  • the first service identifier management function network element assigns the authority of the service identifier to the first computing service.
  • the method further includes: the first service identity management function network element receives a second permission request from the third service identity management function network element, where the second permission request is used to request Allocate the authority of the service identifier to the first computing service, and the second authorization request includes the service name of the first computing service; the first service identifier management function network element sends a second authorization response to the third service identifier management function network element, and the first service identifier management function network element sends a second authorization response.
  • the second authority response is used to indicate accepting the authority of the network element with the third service identification management function to assign the service identification to the first computing service.
  • the first permission request includes a first comparison parameter
  • the second permission request includes a second comparison parameter
  • the method further includes: the first service identifier management function network element according to the first comparison The parameter is compared with the second parameter to determine the authority to accept the third service identifier management function network element to assign the service identifier to the first computing service.
  • the first service identifier management function network element of the first network domain may first strive to serve the first computing service.
  • the authority to assign the service identifier after obtaining the authority, allocate the corresponding service identifier to the first computing service according to the service name of the first computing service, if the authority is not obtained, wait for the announcement of other service identifier management function network elements that have obtained the assignment authority its distribution result.
  • the above process of allocating a service identifier for the first computing service is suitable for the scenario of dynamically selecting the global service identifier management function network element.
  • the local service identifier management function network element of each network domain in the cross-domain computing power aware network can be It has the function of network element with global service identity management function.
  • the first service identification management function When the network element of the first service identification management function needs to allocate service identifications for the global computing services corresponding to the cross-domain computing power-aware network and whose service scope includes multiple network domains in the cross-domain computing power-aware network, the first service identification management function The network element can determine which local service identifier management function network element obtains the allocation authority through negotiation with the local service identifier management function network elements of other network domains (that is, determine which local service identifier management function network element is responsible for the global service identifier management function). The functional role of the functional network element), the local service identity management function network element that has obtained the allocation authority also needs to announce the allocation result to the local service identity management function network element of other network domains, so that the allocation results can be synchronized in multiple network domains.
  • the first computing service has the same service identifier in multiple network domains, which facilitates the realization of cross-domain computing power perception and packet forwarding for the first computing service.
  • the first service identifier includes a global prefix
  • the global prefix indicates that the first service identifier is allowed to be routed in multiple network domains included in the cross-domain computing power aware network.
  • the first computing service corresponds to a cross-domain computing power-aware network and belongs to a global computing service whose service scope includes multiple network domains in the cross-domain computing power-aware network, it is the first computing service.
  • the first service identifier allocated by the first computing service may carry a global prefix to indicate that the first computing service is a global computing service.
  • the computing power-aware user plane function in the domain computing power-aware network can construct a corresponding computing power route based on the first service identifier, announce the service capability information related to the first computing service, and forward the information of the first computing service.
  • Corresponding management and control can be performed on packets, such as managing announcements and forwarding ranges, and determining that they can be advertised and forwarded across multiple network domains.
  • the embodiments of the present application provide a method for allocating service identifiers in a cross-domain computing power-aware network.
  • the method can be executed by a second service identifier management function network element, and can also be configured by a second service identifier management function network element.
  • a component eg, a chip or circuit executes.
  • the method includes: the second service identity management function network element receives a second allocation request from the first service identity management function network element, the second allocation request is used to request allocation of a service identity for the first computing service, the second allocation request It includes the service name of the first computing service, the first service identification management function network element belongs to the first network domain, and the first network domain is one of the multiple network domains included in the cross-domain computing power aware network; the second service identification management The functional network element allocates a first service identifier to the first computing service according to the 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-aware network; the second service identifier manages the functional network The element sends a second allocation response to the first service identity management function network element, where the second allocation response includes the first service identity.
  • the first service identifier is used to uniquely identify the first computing service in the cross-domain computing power aware network.
  • the second service identifier management function network element is configured to assign service identifiers to computing services whose service scope includes multiple network domains in the cross-domain computing power aware network.
  • the first service identifier management function network element is configured to assign a service identifier to a computing service whose service scope is the first network domain.
  • the first service identifier includes a global prefix
  • the global prefix indicates that the first service identifier is allowed to be routed in multiple network domains included in the cross-domain computing power aware network.
  • the method further includes: the second service identity management function network element sends a third advertisement message to the third service identity management function network element, where the third advertisement message includes the first calculation The service name and first service identifier of the service, and the third service identifier management function belongs to the 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 aware network.
  • the third service identifier management function network element is configured to assign a service identifier to a computing service whose service scope is the second network domain.
  • the embodiments of the present application provide a method for allocating service identifiers in a cross-domain computing power-aware network.
  • the method can be executed by an edge computing node or by a component (eg, a chip or circuit) configured on the edge computing node.
  • the method includes: an edge computing node sends a first allocation request to a first service identity management function network element, where the first allocation request is used to request allocation of a service identity for the first computing service, and the first allocation request includes the first allocation request of the first computing service.
  • service name, the first service identifier management function network element belongs to the first network domain, the first network domain is one of multiple network domains included in the 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 identity management function network element, the first allocation response includes a first service identity, and the first service identity is used to identify the first computing service in the cross-domain computing power aware network .
  • the first computing service corresponds to a cross-domain computing power-aware network, including: the first allocation request further includes service scope information of the first computing service, where the service scope information indicates the first computing service
  • the scope of services includes multiple network domains in the cross-domain computing power-aware network.
  • the first service identifier includes a global prefix
  • the global prefix indicates that the first service identifier is allowed to be routed in all network domains included in the cross-domain computing power aware network.
  • the embodiments of the present application provide a method for allocating service identifiers in a cross-domain computing power-aware network.
  • a component eg, a chip or circuit
  • the method includes: a first service identity management function network element receives a first allocation request from an edge computing node, where the first allocation request is used to request allocation of a service identity for a first computing service, and the first allocation request includes the first computing service
  • the first service identifier management function network element belongs to the first network domain, and the first network domain is one of multiple network domains included in the cross-domain computing power aware 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 of the first computing service, where the first service identifier is used to identify the first computing service in the first network domain; the first service identifier management function network The element sends a first allocation response to the edge computing node, where the first allocation response includes the first service identifier.
  • the first service identifier is used to uniquely identify the first computing service within the first network domain.
  • the first service identifier management function in the first network domain may allocate a corresponding first service identifier for 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 can identify the first computing service in the first network domain, the above method can support the deployment of the first computing service in the first network domain of the cross-domain computing power aware network, and the implementation of the first computing service based on the first service identifier Dynamic computing power routing and packet forwarding for the first computing service.
  • the first allocation request further includes service scope information of the first computing service; the method further includes: if the service scope information indicates that the service scope 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.
  • the first service identifier management function in the first network domain can identify, according to the service scope information of the first computing service, that the first computing service corresponds to the first network domain, and belongs to the cross-domain computing power-aware network only.
  • the local computing service deployed in the first network domain of the server can directly assign the first service identifier to the first computing service.
  • the first service identifier includes a local prefix, and the local prefix indicates that the first service identifier is allowed to be routed in the first network domain.
  • the first service identifier management function network element is configured to assign a service identifier to a computing service whose service scope is the first network domain.
  • the first service identifier allocated to the first computing service. It can carry a local prefix to indicate that the first computing service is a local computing service, and the first service identifier can be routed within the first network domain, so that the computing power-aware user plane function in the cross-domain computing power-aware network can be based on the first service.
  • a service identifier constructs a corresponding computing power route, and can perform corresponding management and control when advertising the service capability information related to the first computing service and forwarding the message of the first computing service, such as managing the announcement and forwarding range, determining Announcement and forwarding, etc. are only performed in the first network domain.
  • the embodiments of the present application provide a method for assigning service identifiers in a cross-domain computing power-aware network.
  • the method can be performed by an edge computing node or by a component (such as a chip or circuit) configured on the edge computing node.
  • the method includes: an edge computing node sends a first allocation request to a first service identity management function network element, where the first allocation request is used to request allocation of a service identity for the first computing service, and the first allocation request includes the first allocation request of the first computing service.
  • Service name, the first service identifier management function network element belongs to the first network domain, the first network domain is one of multiple network domains included in the cross-domain computing power perception network, and the first computing service corresponds to the first network domain; edge computing The node receives a first allocation response from the first service identity management function network element, where the first allocation response includes a first service identity for identifying the first computing service within the first network domain.
  • the first service identifier is used to uniquely identify the first computing service within the first network domain.
  • the first computing service corresponds to the first network domain, including: the first allocation request further includes service scope information of the first computing service, where the service scope information indicates the first The service scope of the computing service is the first network domain.
  • the first service identifier includes a local prefix, and the local prefix indicates that the first service identifier is allowed to be routed within the first network domain.
  • an embodiment of the present application provides a communication device, the device may have the function of implementing the first service identity management function network element in any of the above aspects or any possible design of the various aspects, and may also have the function of implementing the above-mentioned various aspects.
  • the function of the second service identity management function network element in any possible design of the aspect or aspects may also have the function of an edge computing node in any possible design of the above-mentioned aspects or aspects.
  • the apparatus may be a network device or a chip included in the network device.
  • the functions of the above communication apparatus may be implemented by hardware, or by executing corresponding software in hardware, and the hardware or software includes one or more modules or units or means corresponding to the above functions.
  • the structure of the apparatus includes a processing module and a transceiver module, wherein the processing module is configured to support the apparatus to perform the first service identity management function network in the above aspects or any design of the various aspects Element corresponding functions, or perform the corresponding functions of the second service identity management function network element in the above aspects or any design of the various aspects, or perform the above aspects or the corresponding functions of the edge computing node in any design of the various aspects.
  • the transceiver module is used to support the communication between the device and other communication devices.
  • the communication device may also include a storage module, which is coupled to the processing module and stores necessary program instructions and data of the device.
  • the processing module may be a processor
  • the communication module may be a transceiver
  • the storage module may be a memory
  • the memory may be integrated with the processor, or may be provided separately from the processor.
  • the structure of the apparatus includes a processor and may also include a memory.
  • the processor is coupled to the memory and operable to execute computer program instructions stored in the memory to cause an apparatus to perform the methods in the aspects described above or in any possible design of the aspects.
  • the apparatus further includes a communication interface to which the processor is coupled.
  • the communication interface may be a transceiver or an input/output interface; when the device is a chip included in the network device, the communication interface may be an input/output interface of the chip.
  • the transceiver may be a transceiver circuit, and the input/output interface may be an input/output circuit.
  • an embodiment of the present application provides a chip system, including: a processor, the processor is coupled to a memory, and the memory is used to store a program or an instruction, when the program or the instruction is executed by the processor , so that the system-on-a-chip implements the above aspects or any method in any possible design of the various aspects.
  • the chip system further includes an interface circuit, and the interface circuit is used to exchange code instructions to the processor.
  • processors in the chip system, and the processors may be implemented by hardware or software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor implemented by reading software codes stored in memory.
  • the memory can be integrated with the processor, or can be provided separately from the processor.
  • the memory may be a non-transitory processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip, or may be provided on different chips.
  • an embodiment of the present application provides a computer-readable storage medium on which a computer program or instruction is stored, and when the computer program or instruction is executed, enables the computer to execute the above aspects or any of the various aspects. method in the design.
  • the embodiments of the present application provide a computer program product, which, when a computer reads and executes the computer program product, causes the computer to execute the above aspects or the methods in any possible designs of the various aspects.
  • an embodiment of the present application provides a communication system, where the communication system includes a first service identity management function network element and an edge computing node.
  • the communication system may further include a second service identification management function network element and a third service identification management function network element.
  • FIG. 1 is a schematic diagram of a network architecture 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 perception network provided by an embodiment of the present application
  • FIG. 3 is a schematic diagram of a network architecture 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 the format and generation method of a local service identifier or a global service identifier provided by an embodiment of the present application;
  • FIG. 5a is a schematic diagram of a packet forwarding relationship between intra-domain and cross-domain in a cross-domain computing power-aware network provided by an embodiment of the present application;
  • 5b is a schematic diagram of the forwarding relationship between intra-domain and cross-domain announcements in a cross-domain computing power-aware network provided by an embodiment of the present application;
  • FIG. 6 is a schematic flowchart of a method for allocating service identifiers in a cross-domain computing power-aware network according to an embodiment of the present application
  • FIG. 7 is a schematic expanded flowchart of a method for allocating service identifiers in a cross-domain computing power-aware network according to an embodiment of the present application
  • FIG. 8 is a schematic diagram of a first service identifier when the 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 diagram of a scenario of statically specifying a global service identity management function network element provided by an embodiment of the present application.
  • Embodiment 10 is a schematic flowchart of Embodiment 1 of obtaining a first service identifier provided by an embodiment of the present application;
  • FIG. 11 is a schematic diagram of a scenario for dynamically selecting a network element with a global service identity management function according to an embodiment of the present application
  • FIG. 12 is a schematic flowchart of the situation in which the first SIDMF obtains the authority to allocate the service identifier for the first computing service in Embodiment 2 of obtaining the first service identifier provided by the embodiment of the present application;
  • FIG. 13 is a schematic flowchart of a situation in which the first SIDMF does not obtain the authority to allocate a service identifier for the first computing service in Embodiment 2 of obtaining the first service identifier provided by the embodiment of the present application;
  • FIG. 14 is a schematic flowchart of another method for assigning service identifiers in a cross-domain computing power-aware network according to an embodiment of the present application
  • FIG. 15 is a schematic diagram of a first service identifier when the first computing service corresponds to a first network domain according to an embodiment of the present application
  • FIG. 16 and FIG. 17 are schematic diagrams of a communication apparatus according to an embodiment of the present application.
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD time division duplex
  • 5G fifth generation mobile communication systems or new radio (NR) systems
  • NR new radio
  • Terminal equipment which is a device with wireless transceiver function. Terminal devices may communicate with the core network or the Internet via a radio access network (eg, radio access network, RAN), exchanging voice and/or data with the RAN.
  • a radio access network eg, radio access network, RAN
  • Terminal equipment may include user equipment (UE), wireless terminal equipment, mobile terminal equipment, D2D terminal equipment, vehicle to everything (V2X) terminal equipment, machine-to-machine communication (machine-to-machine) /machine-type communications, M2M/MTC) terminal equipment, Internet of things (IoT) terminal equipment, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile station), remote station (remote) station), access point (AP), remote terminal (remote terminal), access terminal (access terminal), user terminal (user terminal), user agent (user agent) or user equipment (user device), etc.
  • UE user equipment
  • V2X vehicle to everything
  • M2M/MTC machine-to-machine communication
  • M2M/MTC machine-to-machine communication terminal equipment
  • M2M/MTC machine-to-machine communication terminal equipment
  • M2M/MTC machine-to-machine communication terminal equipment
  • M2M/MTC machine-to-machine communication terminal equipment
  • the terminal device may be a mobile phone, a tablet computer, a computer with a wireless transceiver function, a portable, pocket-sized, hand-held, mobile device built into a computer, and the like.
  • the terminal device may also be a virtual reality (virtual reality, VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control (industrial control), a self-driving (self driving) terminal device Wireless terminal, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, smart home Wireless terminal in (smart home), terminal equipment in the future evolution of public land mobile network (PLMN), or vehicle equipment in V2X, customer premises equipment (customer premises equipment, CPE), etc.
  • VR virtual reality
  • AR augmented reality
  • the terminal device may also 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 (personal digital assistant, PDA) and other equipment.
  • PCS personal communication service
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices or smart wearable devices, etc. It is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. Wait.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones.
  • Use such as all kinds of smart bracelets, smart helmets, smart jewelry, etc. for physical sign monitoring.
  • the various terminal devices described above if they are located on the vehicle (for example, placed in the vehicle or installed in the vehicle), can be considered as on-board terminal equipment.
  • the on-board terminal equipment is also called on-board unit (OBU). ).
  • a wireless access network device is a device in a communication system for connecting a terminal device to a wireless network.
  • Radio access network equipment can generally be connected to the core network through wired links (eg, fiber optic cables).
  • a radio access network device may be a node in the RAN, also known as a base station (base station), or a RAN node (or device).
  • the radio access network equipment may include a base station, an evolved base station (evolved NodeB, eNodeB) in an LTE system or an evolved LTE system (LTE-Advanced, LTE-A), a next generation NodeB (next generation NodeB) in a 5G communication system, gNB), transmission reception point (TRP), base band unit (BBU), access point (AP) in wireless local area networks (WLAN), access backhaul Integrated access and backhaul (IAB) nodes, base stations in future mobile communication systems or access nodes in WiFi systems, etc.
  • eNodeB evolved NodeB
  • LTE-Advanced LTE-A
  • LTE-A next generation NodeB
  • next generation NodeB next generation NodeB
  • 5G communication system gNB
  • TRP transmission reception point
  • BBU base band unit
  • AP access point
  • WLAN wireless local area networks
  • IAB access backhaul Integrated access and backhaul
  • the radio access network device may also be a module or unit that completes some functions of the base station, such as a centralized unit (central unit, CU) or a distributed unit (distributed unit, DU).
  • a centralized unit central unit, CU
  • a distributed unit distributed unit, DU.
  • the embodiments of the present application do not limit the specific technology and specific device form adopted by the wireless access network device.
  • the radio access network device may be a CU node, a DU node, or a radio access network device including a CU node and a DU node.
  • the CU node is used to support radio resource control (radio resource control, RRC), packet data convergence protocol (packet data convergence protocol, PDCP), service data adaptation protocol (service data adaptation protocol, SDAP) and other protocols;
  • DU nodes use To support radio link control (radio link control, RLC) layer protocol, medium access control (medium access control, MAC) layer protocol and physical layer protocol.
  • Radio access network equipment and terminal equipment can be deployed on land, including indoor or outdoor, handheld or vehicle; can also be deployed on water; can also be deployed in the air on aircraft, balloons and satellites.
  • the embodiments of the present application do not limit the application scenarios of the wireless access network device and the terminal device.
  • the wireless access network device may be referred to as an access network device for short. Unless otherwise specified, the access network device in the following refers to a wireless access network device.
  • Core network equipment refers to the equipment in the core network (core network, CN) that provides service support for terminal equipment.
  • the core network equipment may include an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), and a network capability opening function (network capability).
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • NEF network capability opening function
  • exposure function, NEF unified data management
  • UDM unified data management
  • application function application function
  • AF application function
  • AMF is mainly used for access management and mobility management of terminal equipment, such as user location update, registered network, cell handover, etc.
  • SMF is mainly used for session management, such as user session establishment, modification, release, etc.
  • UPF is user The functional entity of the plane is mainly used to connect to the external network and process user packets, such as forwarding, charging, lawful interception, etc.
  • NEF is used to controlly expose some functions of the network to applications
  • the core network equipment may also include other network elements or functional entities related to multi-access edge computing (MEC), which will be described in detail in the following application.
  • MEC multi-access edge computing
  • network elements or functional entities may be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (eg, a cloud platform).
  • a platform eg, a cloud platform
  • the foregoing network element or functional entity may be implemented by one device, or jointly implemented by multiple devices, or may be different functional modules in one device, which are not specifically limited in this embodiment of the present application.
  • system and “network” in the embodiments of this application may be used interchangeably.
  • “Plurality” refers to two or more than two, and in view of this, “plurality” may also be understood as “at least two” in the embodiments of the present application.
  • “At least one” can be understood as one or more, such as one, two or more. For example, including at least one means including one, two or more, and does not limit which ones are included. For example, if at least one of A, B, and C is included, then A, B, C, A and B, A and C, B and C, or A and B and C may be included. Similarly, the understanding of descriptions such as “at least one” is similar.
  • At least one item(s) below or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s).
  • at least one of A, B and C includes A, B, C, AB, AC, BC or ABC.
  • And/or which describes the association relationship of the associated objects, means that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone, A and B exist at the same time, and B exists alone.
  • the character "/" unless otherwise specified, generally indicates that the related objects are an "or" relationship.
  • ordinal numbers such as “first” and “second” mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the order, sequence, priority, or importance of multiple objects, and The description of "first” and “second” also does not limit the objects to be different.
  • 3GPP 3rd generation partnership project
  • the computing power-aware network is also called computing-aware-virtual network (CA-VN) or mobile computing power network.
  • CA-VN computing-aware-virtual network
  • CMF computing management function
  • CA-UPF computing aware-user plane function
  • realize computing power awareness through information announcement between CA-UPF and realize dynamic computing power routing and packet forwarding based on service identifier .
  • FIG. 1 is a network architecture of a communication system supporting a computing power-aware network provided by an embodiment of the present application.
  • the network architecture includes terminal equipment, access network equipment, AMF, SMF, CMF, and service identity management functions ( service ID management function, SIDMF), NEF, MEC platform manager (manager), computing power-aware network and edge data network (edge data network).
  • the computing power-aware network may include at least one CA-UPF
  • the edge data network may include at least one edge computing node, which may also be referred to as an MEC node (or site).
  • a client is installed in the terminal device, and the client may be an application client (application client, AC).
  • CA-UPF The functional roles of CA-UPF are divided into ingress (Ingress) CA-UPF and egress (Egress) CA-UPF.
  • the ingress CA-UPF refers to the CA-UPF that can serve as the access anchor for terminal devices to access the computing power-aware network
  • the egress CA-UPF refers to the CA-UPF associated with the edge computing nodes in the edge data network.
  • each CA-UPF in the computing power-aware network may be selected by the terminal device as an access anchor, and according to the dynamic changes of the network deployment, each CA-UPF in the computing power-aware network may also be associated with Edge computing nodes in the edge data network establish or disassociate relationships. Therefore, the functional role of CA-UPF can be relative and dynamic.
  • a CA-UPF can exist only as an ingress CA-UPF or only as an egress CA-UPF.
  • the UPF exists, and may also exist as an ingress CA-UPF and an egress CA-UPF, which is not limited.
  • the export CA-UPF can establish an association relationship with the edge computing nodes in the edge data network, receive the service binding information reported by the edge computing nodes, and record the service ID and server IP of the computing service according to the service binding information.
  • the mapping relationship between addresses (server IP), and the computing service information and load information reported by edge computing nodes are received, and the computing service information and load information are advertised to the corresponding entry CA-UPF according to the advertisement neighbor list.
  • one egress CA-UPF can correspond to one or more ingress CA-UPFs.
  • the neighbor relationship between the egress CA-UPF and its corresponding one or more ingress CA-UPFs is called the advertisement neighbor relationship, which means that the egress CA-UPF needs to use computing service information and load information to characterize its associated edge computing nodes externally.
  • the information providing computing service capability is advertised to its corresponding ingress CA-UPF, so that the ingress CA-UPF can construct computing power routing information accordingly.
  • the egress CA-UPF is configured with an advertisement neighbor list, and the advertisement neighbor list includes identification information of one or more ingress CA-UPFs corresponding to the egress CA-UPF.
  • the computing service information and load information of the edge computing nodes 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 It is the announcement object for the export CA-UPF to announce the above-mentioned service capability information.
  • the ingress CA-UPF can aggregate the computing service information and load information received from its corresponding egress CA-UPF, and build corresponding computing power for each computing service according to the forwarding neighbor list and the above computing service information and load information.
  • the routing information based on the computing power routing information, forwards the service request message of the terminal device to one of the corresponding egress CA-UPFs.
  • one ingress CA-UPF can correspond to one or more egress CA-UPFs.
  • the neighbor relationship between the ingress CA-UPF and its corresponding one or more egress CA-UPFs is called forwarding neighbor relationship, which means that the ingress CA-UPF needs to forward the service request message of the terminal device to the corresponding egress CA-UPF.
  • the ingress CA-UPF is configured with a forwarding neighbor list, and the forwarding neighbor list includes identification information of one or more egress CA-UPFs corresponding to the ingress CA-UPF.
  • one or more egress CA-UPFs corresponding to the ingress CA-UPF may be considered as multiple optional forwarding objects for the ingress CA-UPF to forward the above-mentioned service request message.
  • the message may also be called a service request message, or have other names, which are not limited.
  • CA-UPF adds a computing power awareness processing unit, a regional dynamic session processing unit and a network address translation unit on the basis of the existing UPF's protocol data unit (protocol data unit, PDU) session processing.
  • PDU protocol data unit
  • the computing power perception processing unit located in the egress CA-UPF is responsible for obtaining service capability information from edge computing nodes, and storing the mapping relationship between the service identifier (Service ID) of the computing service and the server IP address (Server IP address), And advertise the service capability information of the edge computing node to the entry 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, and the computing service information is used to indicate which computing services are supported by the edge computing node, and may specifically include the service identifier of each computing service.
  • One or more pieces of information such as , service attributes, running status, or computing resource information, and the load information is used to represent the current load status of the edge computing node.
  • the computing power perception processing unit located in the ingress CA-UPF is responsible for receiving the service capability information from the egress CA-UPF, and generating or updating the computing power routing information base in the ingress CA-UPF.
  • the computing power routing information base includes computing power routing information of one or more computing services.
  • the computing power routing information of a computing service includes the service identifier of the computing service, the identification information of one or more egress CA-UPFs that can provide the computing service, and the service capability information corresponding to each egress CA-UPF (including associated One or more pieces of information, such as computing service information and/or load information of the edge computing node), network cost information (such as the delay, bandwidth, and jitter between the ingress CA-UPF and the egress CA-UPF).
  • the computing power-aware processing unit can select the appropriate forwarding tunnel for the service request message received by the regional dynamic session processing unit based on the computing power routing information of the computing service in the computing power routing information database, and generate the corresponding message matching the forwarding rule .
  • the main function of the regional dynamic session processing unit is to establish a forwarding tunnel between the ingress CA-UPF and the egress CA-UPF according to the forwarding tunnel information issued by the SMF, and match the forwarding rules based on the packets generated by the computing power-aware processing unit. Real-time forwarding of packets.
  • the computing power-aware processing unit can Select an egress CA-UPF for it based on the computing power routing information base and generate corresponding packet matching forwarding rules.
  • the main function of the network address translation unit is to complete the mutual replacement between the service identifier of the computing service and the server IP address in the message according to the mapping relationship between the service identifier of the computing service provided by the computing power perception processing unit and the server IP address.
  • the network address translation unit can replace the destination IP address in the uplink message sent to the edge computing node by the service identifier of the computing service with the server IP address, and replace the source IP address in the downlink message returned to the terminal device by the server The IP address is replaced with the service identifier of the computing service.
  • CMF is used to create and manage computing power-aware network instances, specifically including: managing which CA-UPF members the computing power-aware network includes, and determining the functional role of each CA-UPF member (that is, a CA-UPF is the entry CA -UPF, or export CA-UPF, or both), establish and update forwarding neighbor relationships and/or advertise neighbor relationships among CA-UPF members, etc.
  • CMF can also be used to record information such as service identification and service status of computing services deployed in edge data networks, so that terminal devices can query before initiating a service request.
  • the computing power-aware network exists in the form of an internal virtual interface in CA-UPF, and there can be multiple instances. Each computing power-aware network can correspond to a different network slice instance (NSI) and/or data network name (DNN).
  • NSI network slice instance
  • DNN data network name
  • the CA-UPF members included in different computing power perception networks may be completely different, may partially overlap, or may be completely the same, which is not limited in this application.
  • CMF can create the above-mentioned computing power-aware network between CA-UPFs by sending a request for creating a computing-power-aware network to SMF, and establish neighbor relationships for adjacent CA-UPFs in the computing-power-aware network.
  • These CA-UPFs that form neighbor relationships perform dynamic session management.
  • a regional computing power group can be formed between the edge computing nodes associated with these adjacent CA-UPFs, so that computing services can be dynamically deployed in the regional computing power group, and the service capability information of edge computing nodes can be quickly calculated between CA-UPFs.
  • Announcement so that the service request of the terminal device can be quickly responded, and it can be forwarded to the appropriate edge computing node based on the dynamic computing power routing information, so as to realize the resource load balance of the system and improve the user experience.
  • the forwarding neighbor list and/or the advertisement neighbor list of each CA-UPF can be added, modified and deleted as needed. Since the forwarding neighbor relationship and the advertisement neighbor relationship are relative, therefore, The CMF can confirm that each egress CA-UPF in the forwarding neighbor list of the ingress CA-UPF includes the ingress CA-UPF in its advertisement neighbor list.
  • the SMF can receive the request from the CMF for creating a computing power-aware network, and establish a virtual network-level forwarding tunnel between the CA-UPFs according to the forwarding neighbor relationship and the advertisement neighbor relationship between each CA-UPF, and Deliver the corresponding forwarding neighbor list and/or advertisement neighbor list to each CA-UPF.
  • Each edge computing node in the edge data network can be associated with a CA-UPF in the computing power-aware network, and forward the service request message of the terminal device to the last hop before the edge computing node to ensure end-to-end
  • the data forwarding paths are all controlled by the mobile network.
  • the interface between the edge computing node and the CA-UPF can be the N6 interface defined by 3GPP, and the interface between the CA-UPF and the CA-UPF can be the N19 interface defined by 3GPP.
  • a group composed of multiple adjacent edge computing nodes in an edge data network is called a regional computing power group.
  • the CA-UPFs associated with each edge computing node in the regional computing power group are neighbors.
  • the edge data network can use load balancing technology to break through the resource bottleneck of a single site, thereby increasing the scale of edge computing serviceable applications.
  • the area and the neighbor are divided based on the network delay between edge computing nodes.
  • the edge computing nodes whose interaction delay is within the specified range can form a regional computing power group, thereby improving the edge computing power. The response efficiency of the service.
  • An edge computing node may include an MEC platform and/or an edge application server (EAS).
  • the MEC platform is used for local computing, storage, and network resource scheduling.
  • the EAS is used to deploy or run a computing service, and a certain computing service running in the EAS may be referred to as a service instance of the computing service.
  • An edge computing node may include one or more EASs, and each EAS is assigned a different server IP address (server IP address).
  • server IP address server IP address
  • the physical form of the EAS may be a physical bare metal, or may be a virtual machine, a container, or the like, which is not limited in this application.
  • the MEC platform manager is used to manage the MEC platform and EAS resources in the edge computing nodes. By interacting with the MEC platform in the edge computing nodes, it realizes the computing services of different granularities such as virtual machines, microservices and function instances in multiple edge computing nodes. Dynamic deployment, orchestration and lifecycle management on EAS.
  • Each type of computing service can correspond to a unique service ID (service ID) in the operator's network domain, and the computing power-aware network dynamically routes and forwards the packets requested by the terminal device for computing services based on the service ID.
  • service ID a unique service ID in the operator's network domain
  • Each type of computing service may also have a service name (service name), which is used to characterize what computing service the computing service is, and the service name of the computing service may correspond one-to-one with the service identifier.
  • service name can take the form of a description of a uniform resource identifier (URI) or a uniform resource locator (URL).
  • URI uniform resource identifier
  • URL uniform resource locator
  • the same computing service can be deployed on different edge computing nodes in the edge data network, which is equivalent to distributing multiple copies of the computing service in the edge data network. These multiple copies correspond to different server IP addresses, but still have the same service. logo.
  • the multiple replicas may be multiple service instances of the same computing service running on EASs of different edge computing nodes.
  • the computing power-aware network can realize the computing power routing information of computing services based on the service ID, and map the server IP addresses of multiple copies of the same computing service deployed on different edge computing nodes to the same service ID, indicating that these multiple edge computing nodes The same computing service can be provided to achieve routing consistency.
  • the service identifier of the computing service can be an IP anycast address
  • the terminal device can use the service identifier of the computing service to initiate a service request, without paying attention to the specific running of the service instance of the computing service in Which EAS is on, and what is the server IP address of the EAS and other specific details.
  • the terminal device can translate the service name in the service request into a service identifier, and use the service identifier as a destination IP address to construct a corresponding IP packet (ie, a service request packet).
  • CA-UPF can route and forward the service request message based on the service ID of the computing service, and perform mutual replacement between the service ID and the server IP address when sending and receiving messages to the EAS in the edge computing node.
  • edge computing services are not single applications in the traditional client-server model, but relatively lightweight services, such as microservices or function instances Wait. These lightweight computing services are deployed and run on EAS in edge computing nodes.
  • the computing service may be a stateless microservice or a function instance with a short life cycle.
  • the SIDMF is used to provide a unified service identifier allocation function for computing services deployed in the edge data network.
  • the SIDMF can be deployed together with the CMF as an enhanced function of the CMF, or can be deployed independently of the CMF, which is not limited in this application.
  • the allocation of service identifiers in a computing power-aware network involves the following two processes:
  • Process 1 Deployment of computing services and assignment of service IDs.
  • the MEC platform manager first deploys and runs a service instance of the computing service on the specified edge computing node, and the MEC platform generates the service name remotely invoked by the client of the terminal device for the deployment of the computing service. Then, the MEC platform sends a service identifier allocation request to the SIDMF through the NEF, and the SIDMF allocates a corresponding service identifier for the service name and returns it to the MEC platform.
  • the service ID allocation algorithm can be a direct hash of the service name, or a table lookup, or any other algorithm to ensure the uniqueness of the service ID in the computing power-aware network.
  • the SIDMF saves the mapping relationship between the service name and the service identifier, which is used by the subsequent terminal device to obtain the service identifier corresponding to the computing service.
  • the MEC platform After the MEC platform obtains the assigned service ID, it advertises the service ID and the corresponding service capability information to the associated CA-UPF to create a computing power route.
  • Process 2 The terminal device obtains the service identifier. Before initiating a service request for the application layer of a computing service, the client in the terminal device needs to know the service identifier corresponding to the service name of the computing service, so as to use the service identifier of the computing service as the destination IP address to construct a service request report. The text is sent to the computing power perception network through the terminal device.
  • the client can request the terminal device to obtain the service identifier corresponding to the service name of the computing service, and the terminal device forwards the service identifier request message to the SMF through the CA-UPF, and then forwards it to the CMF, and the CMF obtains from the SIDMF to assign the service name to the At the same time, the service identifier and the corresponding service status information are returned to the terminal device according to the original route, and the terminal device is returned to the client.
  • the above-mentioned network architecture is for a large-scale and dense deployment scenario of MEC implemented by a single operator. That is to say, the above computing power-aware network is independently deployed and managed by a single operator, which can be understood as a single-domain computing power-aware network implemented within the management scope of a single operator.
  • the CA-UPF in the computing power-aware network, the access network equipment and various types of core network equipment (such as AMF, SMF, CMF, etc.) in the communication system supporting the computing power-aware network are all controlled and controlled by the same operator. manage.
  • this application further introduces edge computing power-aware users on the basis of the computing power-aware network shown in the network architecture in FIG. 1 .
  • Surface function border computing aware-user plane function, border CA-UPF.
  • the computing power-aware networks of different operators with alliance relationships can establish mutual computing power routing and forwarding tunnels through the boundary CA-UPF, thereby creating a cross-domain computing power-aware network.
  • edge computing services can be flexibly deployed on edge computing nodes connected by computing power-aware networks of multiple operators with alliance relationships, and users of one operator can access the operator network in the local domain.
  • the edge computing services in the network can also be accessed through the border CA-UPF to the edge computing services in the operator network in the alliance domain, which can solve the problems of edge application coverage and limited user groups faced by a single operator's computing power-aware network. , which is beneficial to aggregating the infrastructure capabilities of multiple operators, providing a unified capability open interface for application providers and enterprise users, and achieving a consistent and seamless edge service experience across operators.
  • a cross-domain computing power-aware network can include multiple network domains, and different network domains can be managed by different operators.
  • the intra-domain part of a cross-domain computing power-aware network can be called an intra-domain computing power-aware network, or operator network for short.
  • the plurality of network domains may have a distinction between local domains and federated domains.
  • FIG. 2 is a specific example of the cross-domain computing power awareness network provided by the embodiment of the present application. This application uses this example to illustrate the concepts of the local domain and the federation domain in the cross-domain computing power-aware network.
  • each operator's computing power-aware network can be called a local domain relative to itself, and the computing power-aware network directly connected by terminal devices belongs to the local domain, whether it is the home network or the visited network.
  • the computing power-aware networks of other operators interconnected by the local domain through the border CA-UPF can be called a federation domain, and the federation domain can be further divided into a direct federation domain and an indirect federation domain.
  • the direct confederation domain refers to a confederation domain to which the local domain is directly connected through the boundary CA-UPF
  • the indirect confederation domain refers to the confederation domain reachable from the local domain through the multi-hop boundary CA-UPF. Exemplarily, as shown in FIG.
  • the cross-domain computing power awareness network is composed of computing power awareness network connections of 4 operators with alliance relationships.
  • the computing power awareness network of operator 1 is the domain
  • the computing power awareness networks of operator 2, operator 3, and operator 4 are the direct alliance domains of the computing power awareness network of operator 1.
  • the computing power-aware network of operator 4 is the local area
  • the computing power-aware network of operator 1 is the direct alliance domain of the computing power-aware network of operator 4
  • operators 2 and 3 The computing power-aware network is an indirect federation domain of operator 4's computing power-aware network.
  • end users can only access computing services deployed in the local domain and the direct federation domain.
  • a delay of at most two hops is introduced.
  • users of operator 4 can only access computing services provided by operators 4 and 1. If they access computing services provided by operators 2 and 3, excessive delay will be introduced, resulting in poor service experience.
  • FIG. 3 shows a network architecture of a communication system supporting a cross-domain computing power-aware network provided by an embodiment of the present application.
  • the network architecture shows the relationship between the computing power-aware network in the local domain and the computing power-aware network in the alliance domain. connection between.
  • the boundary CA-UPF of the local domain and the boundary CA-UPF of the federation domain are directly connected to realize packet forwarding of service request and response messages between the two domains and announcement of service capability information.
  • the border CA-UPF of the local domain and the border CA-UPF of the federation domain can be directly connected through the N19 interface defined by 3GPP.
  • a connection relationship is configured between the CMF in the local domain and the CMF in the consortium domain, so that the CMF in the local domain and the CMF in the consortium domain can interact to complete the creation of a cross-domain computing power-aware network.
  • the SMF in the local domain and the SMF in the confederation domain are also configured with a connection relationship.
  • the SMF in the local domain and the SMF in the confederation domain can interact with each other to complete the establishment of the inter-domain forwarding neighbor relationship and the inter-domain advertisement neighbor relationship between the border CA-UPF and the forwarding tunnel. establishment.
  • the boundary CA-UPF is a special CA-UPF.
  • the border CA-UPF is equivalent to the egress CA-UPF for the ingress CA-UPF in the domain, except that the packets received by the border CA-UPF are not directly sent to the associated edge computing node, but to the peer.
  • Boundary CA-UPF of the computing power-aware network in the federation domain Between border CA-UPFs, the border CA-UPF of the local domain is equivalent to the ingress CA-UPF, and the border CA-UPF of the federated domain is equivalent to the egress CA-UPF. In the federation domain, the border CA-UPF is equivalent to the ingress CA-UPF for the 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) can be used as the entry CA-UPF, and the CA-UPF associated with the edge computing node and the boundary CA-UPF of the local domain can be used as Export CA-UPF.
  • FIG. 3 is only an illustration. In actual deployment scenarios, there can be one or more border CA-UPFs in the local domain, one or more border CA-UPFs in the federation domain, and the local domain can be created with one or more federated domains
  • the cross-domain computing power perception network is not limited.
  • the allocation mechanism of service identifiers needs to be able to handle the following two situations: 1) Service identifier allocation and computing power-aware routing of computing services deployed in a single network domain of the operator; 2) In multiple Service ID allocation and power-aware routing for jointly deployed computing services in an operator's network domain.
  • the present application introduces two types of SIDMF, the local SIDMF and the global SIDMF.
  • the local SIDMF is used for allocating service identifiers for the local computing services
  • the local computing services refer to the computing services deployed in the network domain of a single operator
  • the service identifiers of the local computing services may be called the local service identifiers.
  • the global SIDMF is used to assign a service identifier to a global computing service.
  • the global computing service refers to a computing service jointly deployed in the network domains of multiple operators.
  • the service identifier of the global computing service may be called a global service identifier.
  • the global SIDMF may have two possible implementation forms of static designation and dynamic selection, which will be described in detail in the following embodiments of this application.
  • the local service identifier and the global service identifier in this application may have different prefixes .
  • the prefix in the local service ID is called the local prefix
  • the prefix in the global service ID is called the global prefix
  • the local prefix is different from the global prefix. For example, as shown in FIG.
  • the SIDMF in this application may include a service name (service name) or function name (function name) (for example: 123.cmccapi.com/image-process/face-detect/[pic]) Mapped to a service identity with a local or global prefix represented by an IPv6 anycast address.
  • service name service name
  • function name function name
  • FIG. 5a and FIG. 5b another specific example of the cross-domain computing power-aware network provided by the embodiment of the present application.
  • This example shows the connection and forwarding relationship between the local domain and the federation domain on the user plane, and The effect of the service ID allocation mechanism on cross-domain computing power routing.
  • there is an alliance relationship between Operator 1, Operator 2, and Operator 3, and the cross-domain computing power awareness network is created with Operator 1 as the domain, and Operator 2 and Operator 3 as the alliance domain.
  • Computing services are deployed in the edge computing nodes of the three operators' networks.
  • those with the letter L in the circle are local computing services, which can only be deployed in the network domain of local operator 1, and can be assigned a local service identifier;
  • those with the letter G in the circle are global computing services , which can be deployed in the network domains of three operators, and can be assigned a global service identifier.
  • Figure 5a shows the packet forwarding relationship between intra-domain and inter-domain.
  • the ingress CA-UPF of the local domain establishes an intra-domain forwarding neighbor relationship and an intra-domain forwarding tunnel with the adjacent egress CA-UPF and border CA-UPF in the domain.
  • the border CA-UPF of the local domain establishes an inter-domain forwarding neighbor relationship and an inter-domain forwarding tunnel with the border CA-UPF of the direct federation domain.
  • the border CA-UPF of the confederation domain establishes an intra-domain forwarding neighbor relationship and an intra-domain forwarding tunnel with the adjacent egress CA-UPF in the domain.
  • the ingress CA-UPF when the service request sent by the user of operator 1 includes the local service identifier, as shown by the dashed arrow in the figure, the ingress CA-UPF only forwards the service request to the edge associated with the egress CA-UPF in this domain. calculate node. If the service request sent by the user of operator 1 contains the global service identifier, as shown by the solid arrow in the figure, the ingress CA-UPF can forward the service request to the edge computing node associated with the egress CA-UPF in the domain , and can also be forwarded to the edge computing nodes associated with the egress CA-UPF of other federated domains through the border CA-UPF.
  • Figure 5b shows the intra-domain and cross-domain advertisement forwarding relationships.
  • the service capability information related to the local computing service can only be advertised to the corresponding entry CA-UPF in this domain, and the service capability information of the global computing service can be advertised to the corresponding entry CA-UPF in the domain and the boundary CA-UPF through the federation domain at the same time After the aggregation, it is advertised to the boundary CA-UPF of the local domain, and then advertised to the ingress CA-UPF.
  • the same global computing service may be deployed on edge computing nodes distributed in the network domains of operator 1, operator 2, and operator 3.
  • the egress CA-UPF in the network domain of operator 1 can 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 nodes to the ingress CA-UPF in the domain, while the operator
  • the egress CA-UPF in the network domain of 2 and operator 3 can 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, and the boundary CA-UPF passes through the inter-domain.
  • the interface is advertised to the border CA-UPF in operator 1's network domain, and finally advertised to the ingress CA-UPF in operator 1's network domain.
  • the network architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute limitations on the technical solutions provided by the embodiments of the present application.
  • the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • SIDMF SIDMF
  • SIDMF service identity management function network element
  • FIG. 6 is a schematic flowchart of a method for allocating service identifiers in a cross-domain computing power-aware network according to an embodiment of the present application.
  • 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 allocation of a service identifier for the first computing service, and the allocation request 01 includes the service name of the first computing service.
  • the first SIDMF receives the allocation request 01 from the edge computing node.
  • the cross-domain computing power-aware network may include multiple network domains, and different network domains may be network domains of different operators, such as intra-domain computing power-aware networks of different operators.
  • the first network domain is one of multiple network domains included in the cross-domain computing power perception network.
  • the first SIDMF belongs to the first network domain, and may also be referred to as a local SIDMF of the first network domain, and is used to allocate a corresponding service identifier for the local computing service of the first network domain.
  • the local computing service refers to a computing service deployed in a certain network domain in the cross-domain computing power-aware network, and only serving the network domain, not serving other network domains in the cross-domain computing power-aware network. Understandably, the service scope of the local computing service only includes the network domain where the local computing service is deployed, and does not include other network domains in the cross-domain computing power-aware network.
  • the service identifier of the local computing service can be called the local service identifier.
  • the local service identifier can only be routed within the local scope of the network domain where the computing service is deployed, and cannot be routed in other network domains in the cross-domain computing power-aware network.
  • the local service identifier in the embodiment of the present application may include a corresponding local prefix (local prefix), which is used to indicate that the service identifier is a local service identifier, and can be used in the deployment of the identified local computing service. Routing within the local network domain.
  • the "local" can also be understood as local or other meanings, and the service scope can also be referred to as a routing scope or a routing domain, which is not limited in this application.
  • the edge computing node may send an allocation request 01 to the NEF, and the NEF will then forward the allocation request 01 to the first SIDMF.
  • the edge computing node may also send the above allocation request 01 after loading or starting the service instance of the first computing service.
  • the MEC platform in the edge computing node can request to load or start the 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 loaded or started successfully, to the NEF An allocation request 01 is sent, which is forwarded by the NEF to the first SIDMF.
  • Step S602 If the first computing service corresponds to a cross-domain computing power-aware network, the first SIDMF obtains a first service identifier allocated for the first computing service, and the first service identifier is used to identify the first service in the cross-domain computing power-aware network. computing services.
  • the first computing service corresponding to the cross-domain computing power perception network may refer to that the first computing service is a global computing service in the cross-domain computing power perception network.
  • the global computing service refers to a computing service that is deployed in a certain network domain in the cross-domain computing power-aware network, but can serve multiple network domains in the cross-domain computing power-aware network.
  • the network domain of the global computing service and at least one other network domain. Understandably, the service scope of the global computing service may include multiple network domains in the cross-domain computing power-aware network.
  • 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.
  • the first computing service is a global computing service
  • the first computing service may serve the first network domain and the second network domain in the cross-domain computing power-aware network, or may also serve the cross-domain computing power-aware network All domains in .
  • the service identifier of the global computing service may be referred to as a global service identifier, and the global service identifier may be routed in the global scope of the cross-domain computing power-aware network, where the global scope includes all network domains in the cross-domain computing power-aware network.
  • the global service identifier in this embodiment of the present application may include a corresponding global prefix (global prefix) to indicate that the service identifier is a global service identifier , which can be routed in all network domains included in the cross-domain computing power-aware network.
  • the allocation request 01 may include service scope information of the first computing service, where the service scope information is used to indicate the service scope of the first computing service.
  • the first SIDMF can determine whether the first computing service is a global computing service or a local computing service according to the service scope information, and then decides 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 multiple network domains in the cross-domain computing power-aware network, the first SIDMF can determine that the first computing service is a global computing service, corresponding to a cross-domain computing service. A computing power-aware network needs to be assigned a global service identifier.
  • the first SIDMF can determine that the first computing service is a local computing service, and corresponding to the first network domain, a local service identifier needs to be allocated .
  • the service scope information may be a piece of indication information in the allocation request 01, which is used to indicate that the first computing service (or the service scope of the first computing service) is local (local) or global (global).
  • the indication information may be a flag bit occupying 1 bit, and when the flag bit is 0, it means local, that is, the first computing service is a local computing service or the service scope of the first computing service only includes the local first computing service.
  • the first SIDMF can 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 then decide whether to allocate a global service identifier or a local computing service for the first computing service.
  • Local service ID For example, if the service name of the first computing service contains 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, corresponding to a cross-domain computing power-aware network , you need to assign a global service ID. Otherwise, the first SIDMF may determine that the first computing service is a local computing service, and corresponding to the first network domain, a local service identifier needs to be allocated.
  • the first SIDMF can obtain a first service identifier allocated for the first computing service, and the first service identifier is used in the cross-domain computing power-aware network Inside identifies the first computing service.
  • the first service identifier is used to uniquely identify the first computing service in the cross-domain computing power aware network. Understandably, at this time, the first service identifier is the global service identifier. As shown in FIG. 8 , the first service identifier may include a global prefix to indicate that the first service identifier is allowed to be routed in multiple network domains included in the cross-domain computing power aware network, or to indicate that the first service The ID is the global service ID.
  • the first service identifier obtained by the first SIDMF and allocated for the first computing service may be: the first SIDMF allocates the first computing service through the second SIDMF
  • the first service identifier, where the second SIDMF is a global SIDMF, is used for allocating service identifiers for computing services whose service scope includes multiple network domains in the cross-domain computing power aware network.
  • Embodiment 1 is directed to the scenario of statically specifying the global SIDMF.
  • the statically designated global SIDMF refers to: as shown in Figure 9, the functional roles of the local SIDMF and the global SIDMF are clearly specified within a period of time, and the local SIDMF of each network domain can be allocated for the global computing service through the same global SIDMF. Service ID.
  • the global SIDMF can be a separately deployed SIDMF (for example, can be provided by a third party) in addition to the local SIDMF of each network domain in the cross-domain computing power-aware network, or it can be in the cross-domain computing power-aware network.
  • Embodiment 1 may include the following steps:
  • 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 for the first computing service, and the allocation request 02 includes the service name of the first computing service.
  • the second SIDMF receives the allocation request 02 from the first SIDMF.
  • the first SIDMF is a local SIDMF of the first network domain, and is only used for allocating service identifiers for local computing services of the first network domain, and not for allocating service identifiers for global computing services.
  • the second SIDMF is a global SIDMF for assigning service identities to global computing services.
  • 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 a global computing service before allocating a 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.
  • the second SIDMF can convert the service name of the first computing service into an initial service identifier unique in the 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. logo.
  • the initial service identifier may be an IPv4/IPv6 anycast address.
  • the conversion method may be obtained by hash, or calculated based on a specific algorithm, or searched through database matching, which is not limited in this application.
  • the second SIDMF may also store the 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.
  • the first SIDMF receives the allocation response 02 from the second SIDMF, and acquires the first service identifier from the allocation response 02 .
  • the first SIDMF may also store the mapping relationship between the service name of the first computing service and the first service identifier, so that when a terminal device accessing the first network domain subsequently queries the first computing service through the service name of the first computing service.
  • the first SIDMF may provide the terminal device with the first service identifier.
  • the first SIDMF can send the allocation request 02 to the second SIDMF as the global SIDMF and carry the service name of the first computing service to request the second SIDMF to allocate the corresponding global service identifier for the first computing service, and assign the result Return to the first SIDMF.
  • Embodiment 1 may further include the following optional step S1004:
  • Step S1004 the second SIDMF sends an announcement message 03 to the third SIDMF, where the announcement message 03 includes the service name and the first service identifier of the first computing service.
  • the third SIDMF may receive the announcement message 03 from the second SIDMF, and obtain the service name and the first service identifier of the first computing service from the announcement message 03 .
  • the third SIDMF belongs to the second network domain, is a local SIDMF of the second network domain, and is used for allocating a service identifier for the local computing service of the third network domain.
  • the third SIDMF can obtain the service name and the first service identifier of the first computing service from the announcement message 03, and save the service of the first computing service
  • the mapping relationship between the name and the first service identifier so that when the edge computing node in the second network domain requests to assign a service identifier to the first computing service, the third SIDMF can query the first computing service according to the service name of the first computing service.
  • the first service identifier corresponding to the service name is returned to the edge computing node.
  • the second SIDMF can send the above-mentioned announcement message 03 to the local SIDMF of each other network domain except the first network domain in the cross-domain computing power-aware network, so as to allocate the first computing service.
  • the first service identifier of the network domain is notified to the local SIDMF of each network domain, so that the first computing service has the same service identifier in each network domain included in the cross-domain computing power aware network.
  • the local SIDMF of each network domain can store the mapping relationship between the service name of the first computing service and the first service identifier, so that the corresponding query can be performed subsequently.
  • the local SIDMF of a certain network domain receives a request sent by an edge computing node in the network domain to allocate a service identifier for the first computing service
  • the local SIDMF does not need to request the second SIDMF (ie, the global SIDMF).
  • the global service identifier is allocated, but the saved mapping relationship can be queried according to the service name of the first computing service, and the first service identifier corresponding to the service name is returned to the edge computing node.
  • the first SIDMF acquiring the first service identifier allocated for the first computing service may be: the first SIDMF attempts to acquire the global allocation for the first computing service Permissions for the service ID. If the first SIDMF obtains the right to assign the service identifier to the first computing service, the first SIDMF may assign the first service identifier 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 SIDMFs of other network domains (eg, the third SIDMF) successfully obtain the right to assign the service identifier to the first computing service, the first SIDMF may receive the first SIDMF.
  • the first SIDMF may receive the first SIDMF.
  • the announcement message sent by the third SIDMF, and the first service identifier allocated by the third SIDMF for the first computing service is obtained from the announcement message.
  • the "attempt to acquire” can also be understood as other meanings such as application, request, competition, preemption, and striving.
  • Embodiment 2 is directed to the scenario of dynamically selecting the global SIDMF.
  • the dynamic selection of the global SIDMF refers to: as shown in Figure 11, the local SIDMF of each network domain in the cross-domain computing power perception network can serve as the functional role of the global SIDMF, and the local SIDMF of each network domain completes the global SIDMF through mutual negotiation. Assignment of service IDs. Understandably, since the local SIDMF of each network domain can assume the functional role of the global SIDMF, the purpose of the negotiation between the local SIDMFs of each network domain is to confirm which network domain’s local SIDMF is used as the global SIDMF for global services. Assignment of identity.
  • any local SIDMF that temporarily obtains the functional role of the global SIDMF needs to save the difference between the service name and the service ID after completing the global service ID assignment and returning it to the edge computing node.
  • the allocation result should also be announced to the local SIDMFs of other network domains in the cross-domain computing power-aware network, so as to synchronize the service ID allocation information, so that the local SIDMFs of other network domains receive the same global service ID allocation.
  • This assigned service ID can be provided directly upon request to ensure consistent global service ID assignments across all network domains.
  • the situation in which the first SIDMF obtains the right to assign the service identifier to the first computing service may include the following steps:
  • Step S1201 The first SIDMF sends a permission request 01 to the third SIDMF, where the permission request 01 is used to request permission to assign a service identifier to the first computing service, and the permission request 01 includes the service name of the first computing service.
  • the third SIDMF receives the permission request 01 from the first SIDMF.
  • the first SIDMF is a local SIDMF of the first network domain, and also has the function of a global SIDMF, which can be used for allocating service identifiers for the global computing services deployed in the first network domain.
  • the third SIDMF is the local SIDMF of the second network domain, and can also have the function of a global SIDMF, which can be used to assign service identifiers to the global computing services deployed in the second network domain.
  • the permission request 01 may further include a first comparison parameter, and the first comparison parameter may be determined by the first SIDMF according to the timestamp and/or the random number generated when the permission request 01 is sent.
  • the first comparison parameter can be used to assist in determining which network domain local SIDMF is used as the global SIDMF for the first computing service. Assign a global service ID.
  • the first comparison parameter may also be called the first comparison item or have other names, which is not limited in this application.
  • Step S1202 the third SIDMF sends a permission response 01 to the first SIDMF, where the permission response 01 is used to indicate accepting the permission of the first SIDMF to assign a service identifier for the first computing service.
  • the first SIDMF receives the authorization response 01 from the third SIDMF.
  • the third SIDMF can directly send a permission response 01 to the first SIDMF, and notify the first SIDMF through the permission response 01: the third SIDMF
  • the SIDMF accepts the authority requested by the first SIDMF to assign a service identifier to the first computing service.
  • the third SIDMF may, as shown in optional step S1203 below, send a permission request 02 to the first SIDMF, requesting to assign a service identifier to the first computing service permission.
  • Step S1203 The third SIDMF sends a permission request 02 to the first SIDMF, where the permission request 02 is used to request permission to assign a service identifier to the first computing service, and the permission request 02 includes the service name of the first computing service.
  • the first SIDMF receives the permission request 02 from the third SIDMF.
  • the permission request 02 may further include a second comparison parameter, the second comparison parameter is determined by the third SIDMF according to the timestamp and/or random number generated when the permission request 02 is sent, and the function of the second comparison parameter is the same as that of the first comparison parameter.
  • the comparison parameter works similarly. In this way, after the third SIDMF receives the permission request 01 from the first SIDMF and sends the permission request 02, it can judge whether to accept the first comparison parameter in the permission request 01 and the second comparison parameter in the permission request 02 A SIDMF-requested right to assign a service identity to the first computing service.
  • the first comparison parameter and the second comparison parameter may be parameter values obtained by performing certain operations according to the timestamp and/or the random number, and the larger the parameter value, the easier it is to obtain the assignment authority.
  • the third SIDMF can judge according to the size of the first comparison parameter and the second comparison parameter, and if the first comparison parameter is greater than the second comparison parameter, the third SIDMF can determine to accept the first SIDMF to allocate a service identifier for the first computing service and notify the first SIDMF through the above-mentioned permission response 01.
  • the first comparison parameter and the second comparison parameter may be timestamps. The earlier the timestamp, the earlier the permission request is sent, and the easier it is to obtain the assigned permission.
  • the third SIDMF may judge according to the time indicated by the first comparison parameter and 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 to accept the first comparison parameter.
  • a SIDMF assigns the authority of the service identifier to the first computing service, and notifies the first SIDMF through the above authority response 01.
  • the first SIDMF sends the above-mentioned permission request 01 and receives the permission request 02 from the third SIDMF, it can also be judged according to the first comparison parameter in the permission request 01 and the second comparison parameter in the permission request 02. Accept the authority of the third SIDMF to assign a service identity to the first computing service.
  • the first comparison parameter and the second comparison parameter may be parameter values obtained by performing certain operations according to the timestamp and/or the random number, and the larger the parameter value, the easier it is to obtain the assignment authority.
  • the first SIDMF can judge according to the size 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 can determine not to accept the third SIDMF as the first computing service allocation service
  • the identified authority is notified to the third SIDMF through the authority response 02 in the following optional step S1204.
  • the first comparison parameter and the second comparison parameter may be timestamps. The earlier the timestamp, the earlier the permission request is sent, and the easier it is to obtain the assigned permission.
  • the first SIDMF can judge according to the time indicated by the first comparison parameter and 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 can determine not to accept
  • the third SIDMF assigns the authority of the service identifier to the first computing service, and notifies the third SIDMF through the authority response 02 in the following optional step S1204.
  • Step S1204 The first SIDMF sends a permission response 02 to the third SIDMF, where the permission response 02 is used to indicate that the permission of the third SIDMF to assign a service identifier to the first computing service is not accepted.
  • the third SIDMF receives the authorization response 02 from the first SIDMF.
  • the present application does not specifically limit the order in which steps S1201 and S1203 are executed. That is, since the first SIDMF and the third SIDMF independently determine that the first computing service needs to be assigned a global service identifier, it is possible that the first SIDMF sends the permission request 01 first, or the third SIDMF sends the permission request 02 first. , this application is not limited. Similarly, the present application does not limit the order of execution of step S1202 and step S1204.
  • Step S1205 the first SIDMF determines to obtain the right to assign a service identifier to the first computing service.
  • the present application exemplifies through the above steps S1201 to S1204 that in Embodiment 2, when the first SIDMF tries to obtain the right to allocate a service identifier for the first computing service, the first SIDMF negotiates the rights with local SIDMFs in other network domains the process of. Understandably, in an actual application scenario, the first SIDMF can send the above-mentioned permission request 01 to the local SIDMF of each network domain in the cross-domain computing power-aware network, so as to request the permission to assign a service identifier to the first computing service. .
  • the first SIDMF may determine that it has obtained the permission to assign the service identifier to the first computing service . For example, it is possible that the local SIDMFs of other network domains do not have the need to allocate service identifiers for the first computing service at this time, or there are local SIDMFs of one or more other network domains that are also allocating service identifiers to the first computing service at this time, but The first SIDMF has won the right to assign the service identifier to the first computing service through the first comparison parameter in the permission request 01 .
  • Step S1206 The first SIDMF assigns a first service identifier to the first computing service according to the service name of the first computing service.
  • the first SIDMF can convert the service name of the first computing service into an initial service identifier unique in the 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. logo.
  • the initial service identifier may be an IPv4/IPv6 anycast address.
  • the conversion method may be obtained by hash, or calculated based on a specific algorithm, or searched through database matching, which is not limited in this application.
  • the first SIDMF may also store the mapping relationship between the service name of the first computing service and the first service identifier, so that when a terminal device accessing the first network domain subsequently queries the first computing service through the service name of the first computing service.
  • the first SIDMF may provide the terminal device with the first service identifier.
  • step S1207 may also be included:
  • Step S1207 the first SIDMF sends an announcement message 01 to the third SIDMF, where the announcement message 01 includes the service name and the first service identifier of the first computing service.
  • the third SIDMF may receive the announcement message 01 from the first SIDMF, and obtain the service name and the first service name of the first computing service from the announcement message 01.
  • the third SIDMF can also save the 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 a service identifier for the first computing service later , the third SIDMF can query the first service identifier corresponding to the service name according to the service name of the first computing service, and then return it to the edge computing node.
  • the first SIDMF can report to the local SIDMF of each network domain (including the above-mentioned The third SIDMF) sends the above-mentioned announcement message 01 to notify the local SIDMF of each network domain of the first service identifier allocated for the first computing service, so that the first computing service is in each network domain included in the cross-domain computing power-aware network. both have the same service ID.
  • the local SIDMF of each network domain can store the mapping relationship between the service name of the first computing service and the first service identifier, so that the corresponding query can be performed subsequently, and details are not repeated here.
  • the situation in which the first SIDMF does not obtain the right to assign a service identifier to the first computing service in Embodiment 2 may include the following steps:
  • Step S1301 The first SIDMF sends a permission request 01 to the third SIDMF, where the permission request 01 is used to request permission to assign a service identifier to the first computing service, and the permission request 01 includes the service name of the first computing service.
  • the third SIDMF receives the permission request 01 from the first SIDMF.
  • the permission request 01 may further include a first comparison parameter, and the first comparison parameter may be determined by the first SIDMF according to the timestamp and/or the random number generated when the permission request 01 is sent.
  • the first comparison parameter can be used to assist in determining which network domain local SIDMF is used as the global SIDMF for the first computing service. Assign a global service ID.
  • Step S1302 The third SIDMF sends a permission response 01 to the first SIDMF, where the permission response 01 is used to indicate that the permission of the first SIDMF to assign a service identifier to the first computing service is not accepted.
  • the first SIDMF receives the authorization response 01 from the third SIDMF.
  • this Embodiment 2 may further include the following steps S1303 and S1303.
  • Step S1303 The third SIDMF sends a permission request 02 to the first SIDMF, where the permission request 02 is used to request permission to assign a service identifier to the first computing service, and the permission request 02 includes the service name of the first computing service.
  • the first SIDMF receives the permission request 02 from the third SIDMF.
  • the permission request 02 may further include a second comparison parameter, the second comparison parameter is determined by the third SIDMF according to the timestamp and/or random number generated when the permission request 02 is sent, and the function of the second comparison parameter is the same as that of the first comparison parameter.
  • the comparison parameter works similarly.
  • Step S1304 The first SIDMF sends a permission response 02 to the third SIDMF, where the permission response 02 is used to indicate accepting the permission of the third SIDMF to assign the service identifier to the first computing service.
  • the third SIDMF receives the authorization response 02 from the first SIDMF.
  • the first SIDMF can determine whether to accept the third SIDMF to allocate services for 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 Identity permissions.
  • the first comparison parameter and the second comparison parameter may be parameter values obtained by performing certain operations according to the timestamp and/or the random number, and the larger the parameter value, the easier it is to obtain the assignment authority.
  • the first SIDMF may determine to accept the permission of the third SIDMF to assign the service identifier to the first computing service, and notify the third SIDMF through the permission response 02 in step S1404.
  • the first comparison parameter and the second comparison parameter may be timestamps, and the earlier the timestamp, the earlier the permission request is sent, and the easier it is to obtain the assigned permission.
  • the first SIDMF may determine to accept the permission of the third SIDMF to assign the service identifier to the first computing service, and respond to 02 through the permission in step S1404 Notify the third SIDMF.
  • the third SIDMF may also determine whether to accept the permission of the first SIDMF to assign 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 .
  • the first comparison parameter and the second comparison parameter may be parameter values obtained by performing a certain operation according to the timestamp and the random number, and the larger the parameter value, the easier it is to obtain the assignment authority. In this way, if the first comparison parameter is less than the second comparison parameter, the third SIDMF may determine that it does not accept the first SIDMF's right to assign the service identifier to the first computing service, and notify the first SIDMF through the right response 01 in step S1404.
  • the first comparison parameter and the second comparison parameter may be timestamps. The earlier the timestamp, the earlier the permission request is sent, and the easier it is to obtain the assigned permission. In this way, 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 right of the first SIDMF to assign the service identifier to the first computing service, and respond with the right in step S1404 01 is notified to the first SIDMF.
  • Step S1305 the first SIDMF determines that it has not obtained the right to assign a service identifier to the first computing service.
  • the first SIDMF may send the above permission request 01 to the local SIDMF of each network domain in the cross-domain computing power-aware network, so as to request the permission to assign the service identifier to the first computing service.
  • the first SIDMF receives the permission response 01 returned by the local SIDMF (for example, the third SIDMF) in any network domain, indicating that the permission request 01 of the first SIDMF is not accepted, the first SIDMF can determine that it has not obtained the first SIDMF as the first SIDMF.
  • a computing service has the right to assign service IDs, but waits for the local SIDMF of other network domains to announce the service ID assignment results.
  • the third SIDMF may assign the first service identifier to the first computing service according to the service name of the first computing service.
  • the third SIDMF can convert the service name of the first computing service into an initial service identifier that is unique in the 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. logo.
  • the initial service identifier may be an IPv4/IPv6 anycast address.
  • the conversion method may be obtained by hash, or calculated based on a specific algorithm, or searched through database matching, which is not limited in this application.
  • the third SIDMF may also store the mapping relationship between the service name of the first computing service and the first service identifier, so that when a terminal device accessing the second network domain queries the first computing service by the service name of the first computing service later.
  • the third SIDMF may provide the terminal device with the first service identifier.
  • the third SIDMF may also notify the first SIDMF of the first service identifier allocated to the first computing service through the announcement message 02 in the following step S1406. It can be understood that the third SIDMF can send the announcement message 02 to the local SIDMF of each other network domain except the second network domain in the cross-domain computing power-aware network, so as to allocate the first service identifier for the first computing service. Notify the local SIDMF of each other network domain.
  • Step S1306 the third SIDMF sends an announcement message 02 to the first SIDMF, where the announcement message 02 includes the service name and the first service identifier of the first computing service.
  • the first SIDMF receives the announcement message 02 from the third SIDMF, and acquires the first service identifier allocated by the third SIDMF for the first computing service from the announcement message 02 .
  • the first SIDMF may also store the mapping relationship between the service name of the first computing service and the first service identifier for subsequent query use.
  • the first SIDMF when the first computing service is a global computing service, although the first SIDMF serves as the local SIDMF of the first network domain, it can still have the function of the global SIDMF. However, since local SIDMFs of other network domains also have the function of global SIDMF, it is possible that local SIDMFs of other network domains also need to allocate service identifiers for the first computing service. Therefore, in order to avoid conflicts, the first SIDMF can The SIDMF negotiates the allocation authority, and then the local SIDMF of a certain network domain that has obtained the allocation authority is responsible for allocating the corresponding global service identifier for the first computing service, and announces the allocation result to the local SIDMF of other network domains, thereby completing the global service. The assignment of the identifier enables the first computing service to have the same global service identifier in the entire scope of the cross-domain computing power 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.
  • the edge computing node receives the allocation response 01 from the first SIDMF.
  • the first SIDMF sends an allocation response 01 to the NEF, and the NEF then forwards the allocation response 01 to the edge computing node.
  • the edge computing node can also advertise the first service identifier and service capability information related to the first computing service to the associated CA-UPF, and initiate the creation of computing power. Routing process, so that the computing service corresponding to the local service ID can only be accessed by users in the local network domain, while the computing service corresponding to the global service ID can be accessed by users in multiple network domains in the cross-domain computing power-aware network.
  • the allocation request 01 in this embodiment of the present application may be sent through a message, and the message may be called the allocation request message 01 or the service identifier allocation request 01 or have other names, which are not limited.
  • Allocation Response 01 may also be sent by a message, which may be called Allocation Response Message 01 or Service ID Allocation Response 01 or have other names, without limitation.
  • the allocation request 02 and the allocation response 02 are similar to this, and will not be repeated here.
  • the permission request 01 in this embodiment of the present application may also be sent through a message, and the message may be called a permission request message 01 or an allocation right request message 01 or have other names, which are not limited.
  • the rights response 02 may also be sent by a message, which may be called the rights response message 01 or the assignment rights response message 01 or have other names, which are not limited. Permission request 02 and permission response 02 are similar to this, and will not be repeated here.
  • FIG. 14 is a schematic flowchart of another method for assigning service identifiers in a cross-domain computing power-aware network according to an embodiment of the present application, and 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 for the first computing service, and the allocation request 01 includes the service name of the first computing service.
  • the first SIDMF receives the first allocation request from the edge computing node.
  • step S140 For the specific implementation of the step S1401, reference may be made to the step S601 above, and details are not repeated here.
  • Step S1402 if the first computing service corresponds to the first network domain, the first SIDMF allocates a first service identifier to the first computing service according to the service name of the first computing service, and the first service identifier is used to identify the first network domain First Computing Service.
  • the first computing service corresponding to the first network domain may refer to that the first computing service is a local computing service in the first network domain.
  • the allocation request 01 may include service scope information of the first computing service, where the service scope information is used to indicate the service scope of the first computing service.
  • the first SIDMF can determine whether the first computing service is a global computing service or a local computing service according to the service scope information, and then decides 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 can determine that the first computing service is a local computing service, and corresponding to the first network domain, a local service identifier needs to be allocated .
  • the first SIDMF can 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 then decide whether to allocate a global service identifier or a local computing service for the first computing service.
  • the local service identifier is not repeated here.
  • the first service identifier mentioned here refers to the local service identifier, which is used to identify the first computing service in the first network domain, or is used to identify the first computing service in the first network domain.
  • the first computing service is uniquely identified within a network domain.
  • the first service identifier may include a local prefix to indicate that the first service identifier is allowed to be routed within the first network domain, or to indicate that the first computing service is a local computing service.
  • the first SIDMF may convert the service name of the first computing service into an initial service identifier unique within the 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 identifier may be an IPv4/IPv6 anycast address.
  • the conversion method may be obtained by hash, or calculated based on a specific algorithm, or searched through database matching, which is not limited in this 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 identifier.
  • the edge computing node receives the allocation response 01 from the first SIDMF.
  • step S1403 For the specific implementation of the step S1403, reference may be made to the step S603 above, which will not be repeated.
  • the embodiment of the present application provides a unified service identifier allocation mechanism in a cross-operator computing power-aware network environment, and allocates the same service identifier for the same type of edge computing services deployed in different operators' network domains, thereby Achieve consistent access to cross-domain edge computing services.
  • the service identification allocation mechanism in the environment of a single-domain computing power-aware network, no additional interfaces and configuration operations are added, and the unified management and control of local service identifications within a domain and global service identifications across domains can be realized. It is convenient for application providers to deploy single-domain edge applications and cross-domain edge applications in a unified manner.
  • the present application also provides a communication device.
  • FIG. 16 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 1600 includes a transceiver module 1610 and a processing module 1620 .
  • the communication device can be used to implement the functions related to the first service identity management function network element or the second service identity management function network element or the edge computing node in any of the above method embodiments.
  • the communication apparatus may be a network device, or a chip included in the network device.
  • the transceiver module 1610 is configured to receive the first allocation request from the edge computing node.
  • the first allocation request is used to request to allocate a service identifier for the first computing service
  • the first allocation request includes the service name of the first computing service
  • the first service identifier management function belongs to the first network domain
  • the first network domain is One of multiple network domains included in the cross-domain computing power perception network
  • the processing module 1620 is configured to, if the first computing service corresponds to the cross-domain computing power perception network, obtain the first service identifier allocated for the first computing service, the first The service identifier is used to identify the first computing service in the cross-domain computing power-aware network
  • the transceiver 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.
  • the first service identifier is used to uniquely
  • the first allocation request further includes service scope information of the first computing service; the processing module 1620 is further configured to, if the service scope information indicates that the service scope of the first computing service includes the cross-domain computing power-aware network It is determined that the first computing service corresponds to a cross-domain computing power-aware network.
  • the processing module 1620 is specifically configured to: send a second allocation request to the second service identity management function network element through the transceiver module 1610, where the second allocation request is used to request to allocate a service identity for the first computing service , the second allocation request includes the service name of the first computing service; and a second allocation response is received from the second service identification management function network element through the transceiver module 1610, where the second allocation response includes the first service identification.
  • the processing module 1620 is specifically configured to: obtain the right to assign a service identifier to the first computing service; and assign the first service identifier to the first computing service according to the service name of the first computing service.
  • the transceiver module 1610 is further configured to send a first announcement message to the third service identifier management function network element, where the first announcement message includes the service name and the first service identifier of the first computing service,
  • the third service identity management function 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 aware network.
  • the transceiver module 1610 is further configured to: send a first permission request to the third service identifier management function network element, where the first permission request is used to request the permission to assign a service identifier to the first computing service, the The first permission request includes the service name of the first computing service, the third service identification management function network element belongs to the second network domain, and the second network domain is included in the cross-domain computing power aware network except the first network domain. Another network domain; receiving a first permission response from a third service identity management function network element, where the first permission response is used to indicate accepting the permission of the first service identity management function network element to assign a service identity to the first computing service.
  • the transceiver module 1610 is further configured to: receive a second permission request from a network element with a third service identity management function, where the second permission request is used to request the permission to assign a service identity to the first computing service,
  • the second permission request includes the service name of the first computing service;
  • a second permission response is sent to the third service ID management function network element, where the second permission response is used to indicate that the third service ID management function network element is not accepted as the first Compute Service's authority to assign service IDs.
  • the first permission request includes a first comparison parameter
  • the second permission request includes a second comparison parameter
  • the processing module 1620 is further configured to, according to the first comparison parameter and the second comparison parameter, determine not to accept the first comparison parameter
  • the three service identifier management function network element assigns the authority of the service identifier to the first computing service.
  • the processing module 1620 is specifically configured to: receive the second announcement message from the third service identifier management function network element through the transceiver module 1610, and obtain the first service identifier according to the second announcement message;
  • the second announcement message includes the service name and first service identifier of the first computing service.
  • the third service identifier management function network element belongs to the second network domain, and the second network domain is the first network except the first network included in the cross-domain computing power aware network. Another network domain outside the domain.
  • the transceiver module 1610 is further configured to: send a first permission request to the third service identifier management function network element, where the first permission request is used to request the permission to assign a service identifier to the first computing service, the The first permission request includes the service name of the first computing service, the third service identification management function network element belongs to the second network domain, and the second network domain is included in the cross-domain computing power aware network except the first network domain. Another network domain; receiving a first permission response from a third service identifier management function network element, where the first permission response is used to indicate that the first service identifier management function network element does not accept the right to assign a service identifier to the first computing service.
  • the transceiver module 1610 is further configured to: receive a second permission request from a network element with a third service identity management function, where the second permission request is used to request the permission to assign a service identity to the first computing service,
  • the second permission request includes the service name of the first computing service;
  • a second permission response is sent to the third service ID management function network element, where the second permission response is used to indicate that the third service ID management function network element is accepted as the first computing service Service Permission to assign service IDs.
  • the first permission request includes a first comparison parameter
  • the second permission request includes a second comparison parameter
  • the processing module 1620 is further configured to, according to the first comparison parameter and the second comparison parameter, determine to accept the third comparison parameter
  • the service identifier management function network element assigns the authority of the service identifier to the first computing service.
  • the first service identifier includes a global prefix
  • the global prefix indicates that the first service identifier is allowed to be routed in multiple network domains included in the cross-domain computing power aware network.
  • the transceiver module 1610 is configured to receive the second allocation from the first service identifier management function network element request, the second allocation request is used to request to allocate a service identifier for the first computing service, the second allocation request includes the service name of the first computing service, the first service identifier management function network element belongs to the first network domain, the first A network domain is one of multiple network domains included in the cross-domain computing power-aware network; the processing module 1620 is configured to assign a first service identifier to the first computing service according to the service name of the first computing service, and the first service identifier uses for identifying the first computing service in the cross-domain computing power-aware network; the transceiver module 1610 is configured to send a second allocation response to the network element of the first service identity management function, where the second allocation response includes the first service identity.
  • the first service identifier is used to uniquely identify the first
  • the first service identifier includes a global prefix
  • the global prefix indicates that the first service identifier is allowed to be routed in multiple network domains included in the cross-domain computing power aware network.
  • the transceiver module 1610 is configured to send a third announcement message to the third service identifier management function network element, where the third announcement message includes the service name and the first service identifier of the first computing service, and the third announcement message includes the service name and the first service identifier of the first computing service.
  • the three-service identification management function 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 aware network.
  • the third service identifier management function network element is configured to assign a service identifier to a computing service whose service scope is the second network domain.
  • the transceiver module 1610 is configured to: send a first allocation request to the first service identifier management function network element, and the first allocation The request is used to request to allocate a service identifier for the first computing service, the first allocation request includes the service name of the first computing service, the first service identifier management function network element belongs to the first network domain, and the first network domain is a cross-domain computing service.
  • One of the multiple network domains included in the force-aware network, and the first computing service corresponds to the cross-domain computing force-aware network; receiving a first allocation response from the network element of the first service identification management function, where the first allocation response includes the first service identification , where the first service identifier is used to identify the first computing service in the cross-domain computing power aware network.
  • the first computing service corresponds to a cross-domain computing power-aware network, including: the first allocation request further includes service scope information of the first computing service, where the service scope information indicates that the service scope of the first computing service includes Multiple network domains in a cross-domain computing power-aware network.
  • the first service identifier includes a global prefix
  • the global prefix indicates that the first service identifier is allowed to be routed in all network domains included in the cross-domain computing power aware network.
  • the transceiver module 1610 is configured to receive a first allocation request from an edge computing node, the first The allocation request is used to request to allocate a service identifier for the first computing service, the first allocation request includes the service name of the first computing service, the first service identifier management function network element belongs to the first network domain, and the first network domain is cross-domain One of multiple network domains included in the computing power-aware network; the processing module 1620 is configured to, if the first computing service corresponds to the first network domain, assign a first service identifier to the computing service according to the service name of the first computing service, and the first computing service The service identifier is used to identify the first computing service in the first network domain; the transceiver 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.
  • the first service identifier is
  • the first allocation request further includes service scope information of the first computing service; the processing module 1620 is further configured to, if the service scope information indicates that the service scope of the first computing service is the first network domain, determine the first network domain. A computing service corresponds to the first network domain.
  • the first service identifier includes a local prefix, and the local prefix indicates that the first service identifier is allowed to be routed within the first network domain.
  • the first service identifier management function network element is configured to assign a service identifier to a computing service whose service scope is the first network domain.
  • the transceiver module 1610 is configured to send a first allocation request to the first service identifier management function network element, and the first allocation The request is used to request to allocate a service identifier for the first computing service, the first allocation request includes the service name of the first computing service, the first service identifier management function network element belongs to the first network domain, and the first network domain is a cross-domain computing service.
  • the first computing service corresponds to the first network domain; receiving a first allocation response from the network element of the first service identity management function, where the first allocation response includes a first service identity, the The first service identifier is used to identify the first computing service within the first network domain.
  • the first service identifier is used to uniquely identify the first computing service within the first network domain.
  • the first computing service corresponds to the first network domain, including: the first allocation request further includes service scope information of the first computing service, where the service scope information indicates the service of the first computing service The scope is the first network domain.
  • the first service identifier includes a local prefix, and the local prefix indicates that the first service identifier is allowed to be routed within the first network domain.
  • the processing module 1620 involved in the communication apparatus may be implemented by at least one processor or a processor-related circuit component, and the transceiver module 1610 may be implemented by at least one transceiver or a transceiver-related circuit component or a communication interface.
  • the operations and/or functions of the various modules in the communication device are respectively to implement the corresponding processes of the methods shown in FIG. 6 to FIG. 15 , and are not repeated here for brevity.
  • the communication device may further include a storage module, the storage module may be used 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, Thereby, the communication device can implement the corresponding method.
  • the memory module can be implemented, for example, by at least one memory.
  • the above-mentioned storage module, processing module, and transceiver module may exist separately, 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.
  • FIG. 17 is another schematic structural diagram of a communication apparatus provided in an embodiment of the present application.
  • the communication device can be used to implement the functions corresponding to the first service identity management function network element or the second service identity management function network element or the edge computing node in the above method embodiments, and the communication device can be a network device or can support the network device to implement the above Apparatuses with corresponding functions in the method embodiments, etc.
  • the communication apparatus 1700 may include a processor 1701 , a communication interface 1702 and a memory 1703 .
  • the communication interface 1702 is used to communicate with other devices through a transmission medium, and the communication interface 1702 may be a transceiver or 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 method embodiments.
  • 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 forms, used between devices, units or modules. information interaction.
  • the communication interface 1702 may be specifically configured to perform the operations of the above-mentioned transceiver module 1610, and the processor 1701 may be specifically configured to perform the operations of the above-mentioned processing module 1620, which will not be described herein again.
  • the specific connection medium between the communication interface 1702 , the processor 1701 , and the memory 1703 is not limited in this embodiment of the present application.
  • the memory 1703, the processor 1701, and the communication interface 1702 are connected by a bus 1704 in FIG. 17.
  • the bus is represented by a thick line in FIG. 17, and the connection between other components is only for schematic illustration. , is not limited.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 17, but it does not mean that there is only one bus or one type of bus.
  • An embodiment of the present application further provides a chip system, including: a processor, where the processor is coupled with a memory, the memory is used to store a program or an instruction, and when the program or instruction is executed by the processor, the The chip system implements a method corresponding to a terminal device or a method corresponding to a network device in any of the foregoing method embodiments.
  • the number of processors in the chip system may be one or more.
  • the processor can be implemented by hardware or by software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor implemented by reading software codes stored in memory.
  • the memory may be integrated with the processor, or may be provided separately from the processor, which is not limited in this application.
  • the memory may be a non-transitory processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip, or may be separately provided on different chips.
  • ROM read-only memory
  • the type of memory and the manner in which the memory and the processor are arranged are not particularly limited.
  • the system-on-chip may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a system on chip (SoC), It can also be a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), or a microcontroller (microcontroller).
  • controller unit, MCU it can also be a programmable logic device (PLD) or other integrated chips.
  • each step in the above method embodiments may be implemented by a hardware integrated logic circuit in a processor or an instruction in the form of software.
  • the method steps disclosed in conjunction with the embodiments of the present application may be directly embodied as being executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • Embodiments of the present application further provide a computer-readable storage medium, where computer-readable instructions are stored in the computer storage medium, and when the computer reads and executes the computer-readable instructions, the computer is made to execute any of the foregoing method embodiments method in .
  • Embodiments of the present application further provide a computer program product, which, when the computer reads and executes the computer program product, causes the computer to execute the method in any of the above method embodiments.
  • An 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 the first network domain included in the cross-domain computing power perception network, and is used for allocating a corresponding service identifier to the local computing service deployed in the first network domain (i.e. the local service ID).
  • 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 uses It is used to assign corresponding service identifiers (ie, global service identifiers) to global computing services that can be deployed in multiple network domains of the cross-domain computing power-aware network.
  • 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 uses It is used to assign corresponding service identifiers (ie, global service identifiers) to global computing services that can be deployed in multiple network domains of the cross-domain computing power-aware network.
  • the communication system further includes a third service identification management function network element, where the third service identification management function network element is a local service identification management function network element of the second network domain included in the cross-domain computing power perception network. , which is used to assign a corresponding service identifier (ie, a local service identifier) to the local computing service deployed in the second network domain.
  • a third service identification management function network element is a local service identification management function network element of the second network domain included in the cross-domain computing power perception network. , which is used to assign a corresponding service identifier (ie, a local service identifier) to the local computing service deployed in the second network domain.
  • the communication system further includes a third service identity management function network element, where the third service identity management function network element is a local service of the second network domain included in the cross-domain computing power aware network
  • the identity management function network element is configured to allocate a corresponding service identity (ie, a local service identity) to the local computing service deployed in the second network domain.
  • the above-mentioned first service identification management function network element and third service identification management function network element can also have a global service identification management function network element while having the service identification for the local computing service deployed in the local network domain. Function.
  • the first service identifier management function network element and the third service identifier management function network element can decide through mutual negotiation who is responsible for the function of the global service identifier management function network element. Specifically, the assignment of the global service identifier is performed.
  • processors mentioned in the embodiments of the present application may be a CPU, other general-purpose processors, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like.
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the memory mentioned in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be ROM, programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM) , EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM enhanced synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SCRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components
  • the memory storage module
  • memory described herein is intended to include, but not be limited to, these and any other suitable types of memory.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne un procédé d'attribution d'identifiant de service dans un réseau à partage de ressources informatiques inter-domaine, et un dispositif de communication. Le procédé comprend les étapes suivantes : une première fonction de gestion d'identifiant de service d'un premier domaine de réseau reçoit une demande d'attribution qui provient d'un nœud informatique en périphérie de réseau et concerne l'attribution d'un identifiant de service à un premier service informatique ; et si le premier service informatique correspond au réseau à partage de ressources informatiques inter-domaine, la première fonction de gestion d'identifiant de service peut obtenir un premier identifiant de service attribué au premier service informatique, et renvoyer le premier identifiant de service au nœud informatique en périphérie de réseau, le premier identifiant de service servant à identifier le premier service informatique dans le réseau à partage de ressources informatiques inter-domaine. Le procédé permet de réaliser une fonction servant à attribuer l'identifiant de service au premier service informatique qui peut être déployé dans une pluralité de domaines de réseau du réseau à partage de ressources informatiques inter-domaine, et le réseau à partage de ressources informatiques inter-domaine peut être pris en charge dans la construction d'un itinéraire de calcul informatique dynamique et la réalisation d'un transfert de paquets inter-domaine pour un premier service informatique sur la base du premier identifiant de service.
PCT/CN2022/089532 2021-04-29 2022-04-27 Procédé d'attribution d'identifiant de service dans un réseau à partage de ressources informatiques inter-domaine, et dispositif de communication WO2022228460A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110472905.9A CN115278608A (zh) 2021-04-29 2021-04-29 一种跨域算力感知网络中的服务标识分配方法及通信装置
CN202110472905.9 2021-04-29

Publications (1)

Publication Number Publication Date
WO2022228460A1 true WO2022228460A1 (fr) 2022-11-03

Family

ID=83744886

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/089532 WO2022228460A1 (fr) 2021-04-29 2022-04-27 Procédé d'attribution d'identifiant de service dans un réseau à partage de ressources informatiques inter-domaine, et dispositif de communication

Country Status (2)

Country Link
CN (1) CN115278608A (fr)
WO (1) WO2022228460A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024119292A1 (fr) * 2022-12-05 2024-06-13 华为技术有限公司 Procédé de service de réseau, appareil de communication et système de communication
CN118283124A (zh) * 2024-06-03 2024-07-02 中国电子科技集团公司第十研究所 一种跨域测控网络分级资源调度方法
WO2024153081A1 (fr) * 2023-01-18 2024-07-25 维沃移动通信有限公司 Procédé et appareil de détermination de ressource de puissance de calcul, et dispositif côté réseau

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118677830A (zh) * 2023-03-16 2024-09-20 中国移动通信有限公司研究院 算力信息通告方法、装置、网络边缘节点及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110476444A (zh) * 2017-11-16 2019-11-19 华为技术有限公司 用于网络服务的标识符分配和/或标识符映射的网络实体和方法
US20190380028A1 (en) * 2016-11-22 2019-12-12 Nokia Technologies Oy User equipment identity implementation in mobile edge scenarios
CN112202844A (zh) * 2020-09-10 2021-01-08 中国联合网络通信集团有限公司 一种跨域多接入边缘计算能力开放的方法及设备
CN112311899A (zh) * 2020-11-18 2021-02-02 中国联合网络通信集团有限公司 一种会话处理方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190380028A1 (en) * 2016-11-22 2019-12-12 Nokia Technologies Oy User equipment identity implementation in mobile edge scenarios
CN110476444A (zh) * 2017-11-16 2019-11-19 华为技术有限公司 用于网络服务的标识符分配和/或标识符映射的网络实体和方法
CN112202844A (zh) * 2020-09-10 2021-01-08 中国联合网络通信集团有限公司 一种跨域多接入边缘计算能力开放的方法及设备
CN112311899A (zh) * 2020-11-18 2021-02-02 中国联合网络通信集团有限公司 一种会话处理方法、装置及系统

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024119292A1 (fr) * 2022-12-05 2024-06-13 华为技术有限公司 Procédé de service de réseau, appareil de communication et système de communication
WO2024153081A1 (fr) * 2023-01-18 2024-07-25 维沃移动通信有限公司 Procédé et appareil de détermination de ressource de puissance de calcul, et dispositif côté réseau
CN118283124A (zh) * 2024-06-03 2024-07-02 中国电子科技集团公司第十研究所 一种跨域测控网络分级资源调度方法

Also Published As

Publication number Publication date
CN115278608A (zh) 2022-11-01

Similar Documents

Publication Publication Date Title
WO2022228460A1 (fr) Procédé d'attribution d'identifiant de service dans un réseau à partage de ressources informatiques inter-domaine, et dispositif de communication
WO2022161196A1 (fr) Procédé d'attribution d'identifiant de service dans un réseau sensible au calcul et appareil de communication
KR102589956B1 (ko) 데이터 전송 방법, 장치, 및 시스템
JP2023109789A (ja) ローカルエリアネットワーク（ｌａｎ）をサポートする方法および装置
EP2497286B1 (fr) Découverte d'homologue dans un réseau de communications sans fil
WO2022205241A1 (fr) Procédé et appareil de gestion de session pour réseau sensible au calcul inter-domaine
EP2810461B1 (fr) Système et procédé pour une architecture de partage de réseau partenaire
WO2022111646A1 (fr) Procédé de gestion de session sensible au calcul et dispositif de communication
KR102469973B1 (ko) 통신 방법 및 장치
KR101692259B1 (ko) Wi-Fi 다이렉트 멀티그룹 네트워크 상에서 통신을 위한 방법, 장치 및 컴퓨터 판독 가능한 기록 매체
JP2022544488A (ja) ネットワーク機能サービスディスカバリのための方法および装置
EP3930378B1 (fr) Changement de cellule d'un réseau non public
EP4203607A1 (fr) Procédé informatique de périphérie de réseau et appareil de communication
EP4185009A1 (fr) Procédé, appareil et système d'acheminement de paquets
CN116530208A (zh) 一种通信方法、装置及系统
EP4044614A1 (fr) Procédé d'établissement d'une session de multidiffusion et dispositif de réseau
JP7547701B2 (ja) アプリケーションがネットワーク、装置、およびシステムにアクセスするための方法
WO2022036508A1 (fr) Procédé et appareil de découverte d'une amf cible
WO2023141909A1 (fr) Procédé de communication sans fil, ue distant et élément de réseau
WO2024086996A1 (fr) Procédé et dispositif d'attribution d'adresse
WO2023134516A1 (fr) Procédé et appareil de communication de diffusion
WO2024193166A1 (fr) Procédé et appareil de communication
WO2024169468A1 (fr) Procédé de communication et appareil de communication
WO2022268053A1 (fr) Procédé et appareil de relocalisation de contexte
WO2022068336A1 (fr) Procédé de mise à jour d'informations de routage, appareil de communication et support de stockage

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22794930

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22794930

Country of ref document: EP

Kind code of ref document: A1