WO2024131812A1 - Procédé et appareil de mise en œuvre de service informatique, dispositif de communication, et support de stockage - Google Patents

Procédé et appareil de mise en œuvre de service informatique, dispositif de communication, et support de stockage Download PDF

Info

Publication number
WO2024131812A1
WO2024131812A1 PCT/CN2023/140074 CN2023140074W WO2024131812A1 WO 2024131812 A1 WO2024131812 A1 WO 2024131812A1 CN 2023140074 W CN2023140074 W CN 2023140074W WO 2024131812 A1 WO2024131812 A1 WO 2024131812A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
service
identifier
data packet
address
Prior art date
Application number
PCT/CN2023/140074
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 WO2024131812A1 publication Critical patent/WO2024131812A1/fr

Links

Definitions

  • the present application belongs to the field of wireless communication technology, and specifically relates to a method, device, communication equipment and storage medium for implementing a computing service.
  • the 5th Generation (5G) protocol mainly provides mobile communication transmission services for user equipment (UE, also known as terminal) and application functions (or application servers) to meet the communication service quality (QoS) requirements, and does not involve service information and computing load information.
  • UE user equipment
  • application functions or application servers
  • the 6th Generation (6G) communication system is an information system that integrates communication, computing, and storage.
  • the services required by user devices may involve both mobile network transmission and wired network transmission, so a mobile computing and network integration solution is needed.
  • the embodiments of the present application provide a method, apparatus, communication device and storage medium for implementing a computing service, which can solve the problem of how to forward data packets between a service request sending node, a service response receiving node and a service node.
  • a method for implementing a computing service comprising:
  • the first node receives a first data packet sent by a service request sending node, wherein a header of the first data packet includes at least one of the following: an identifier of the service request sending node, an identifier of a service response receiving node, and a service identifier of the requested service;
  • the first node performs address translation on the first data packet, wherein the first node performs address translation on the first data packet includes: translating a source address of the first data packet into an identifier of the service response receiving node or an identifier of the first node, and translating a destination address of the first data packet into an identifier of a service node providing the requested service or an identifier of a routing node connected to the service node;
  • the first node sends a first data packet after the address conversion is performed.
  • a method for implementing a computing service including:
  • the second node receives a first request sent by a service request sending node, wherein the first request includes first information, and the first information includes at least one of the following: an identifier of the service request sending node, an identifier of a service response receiving node, and a service identifier of the requested service;
  • the second node selects the first node and determines the address conversion indication information according to the first information
  • the second node sends a first response to the service request sending node, where the first response is used to indicate that it can assist the service request sending node to complete the address conversion, and the first response includes an identifier of the first node;
  • the second node sends the address conversion indication information to the first node according to the identifier of the first node, and the address conversion indication information is used to perform address conversion on the first data packet received from the service request sending node.
  • a computing service implementation device including:
  • a first receiving module is used to receive a first data packet sent by a service request sending node, wherein a header of the first data packet includes at least one of the following: an identifier of the service request sending node, an identifier of a service response receiving node, and a service identifier of the requested service;
  • a first address translation module is configured to perform address translation on the first data packet, wherein the address translation on the first data packet includes: translating the source address of the first data packet into an identifier of the service response receiving node or an identifier of the first node, and translating the destination address of the first data packet into an identifier of a service node providing the requested service or an identifier of a routing node connected to the service node;
  • the first sending module is used to send a first data packet after address conversion.
  • a computing service implementation device including:
  • a first receiving module is used to receive a first request sent by a service request sending node, wherein the first request includes first information, and the first information includes at least one of the following: an identifier of the service request sending node, an identifier of a service response receiving node, and a service identifier of the requested service;
  • a processing module configured to select a first node and determine address conversion indication information according to the first information
  • a first sending module configured to send a first response to the service request sending node, wherein the first response is used to indicate that the service request sending node can be assisted to complete the address conversion, and the first response includes an identifier of the first node;
  • the second sending module is used to send the address conversion indication information to the first node according to the identifier of the first node, and the address conversion indication information is used to perform address conversion on the first data packet received from the service request sending node.
  • a communication device which terminal includes a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect or the second aspect are implemented.
  • a first node comprising a processor and a communication interface, wherein the communication interface is used to receive a first data packet sent by a service request sending node, wherein a header of the first data packet includes at least one of the following: an identifier of the service request sending node, an identifier of a service response receiving node, and a service identifier of the requested service; and the processor is used to perform address conversion on the first data packet, wherein the address conversion on the first data packet
  • the method comprises: converting the source address of the first data packet into the identifier of the service response receiving node or the identifier of the first node, and converting the destination address of the first data packet into the identifier of the service node providing the requested service or the identifier of the routing node connected to the service node; the communication interface is also used to send the first data packet after the address conversion.
  • a second node comprising a processor and a communication interface, wherein the communication interface is used to receive a first request sent by a service request sending node, the first request comprising first information, the first information comprising at least one of the following: an identifier of the service request sending node, an identifier of a service response receiving node and a service identifier of the requested service; the processor is used to select a first node and determine address conversion indication information according to the first information; the communication interface is also used to send a first response to the service request sending node, the first response is used to indicate that the service request sending node can be assisted to complete the address conversion, and the first response includes the identifier of the first node; the communication interface is also used to send the address conversion indication information to the first node according to the identifier of the first node, and the address conversion indication information is used to perform address conversion on the first data packet received from the service request sending node.
  • a readable storage medium on which a program or instruction is stored.
  • the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.
  • a chip comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect, or to implement the method described in the second aspect.
  • a computer program/program product is provided, wherein the computer program/program product is stored in a storage medium and is executed by at least one processor to implement the steps of the method described in the first aspect or the second aspect.
  • FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application.
  • FIG2 is a flow chart of the CFN control plane
  • FIG3 is a schematic diagram of the flow of the CFN data plane
  • Figure 4 is a schematic diagram of an SRv6 IP data packet
  • FIG5 is a flowchart of a method for implementing a computing service according to an embodiment of the present application
  • FIG6 is a second flow chart of a method for implementing a computing service according to an embodiment of the present application.
  • FIG7 is one of the example diagrams of a first data packet based on IPv6 according to an embodiment of the present application.
  • FIG8 is one of the example diagrams of the service response according to the embodiment of the present application.
  • FIG9 is one of the exemplary diagrams of a data packet after address conversion according to an embodiment of the present application.
  • FIG10 is a second example diagram of a data packet after address translation according to an embodiment of the present application.
  • FIG11 is a second example diagram of a first data packet based on IPv6 according to an embodiment of the present application.
  • FIG12 is a second example diagram of a service response according to an embodiment of the present application.
  • FIG13 is a third example diagram of a data packet after address translation according to an embodiment of the present application.
  • FIG14 is a fourth example diagram of a data packet after address translation according to an embodiment of the present application.
  • FIG15 is a third example diagram of a first data packet based on IPv6 according to an embodiment of the present application.
  • FIG16 is a fifth example diagram of a data packet after address translation according to an embodiment of the present application.
  • FIG17 is a schematic diagram of a mapping relationship between a service flow and a determined service node according to an embodiment of the present application
  • FIG18 is a fourth example diagram of a first data packet based on IPv6 according to an embodiment of the present application.
  • FIG19 is a sixth example diagram of a data packet after address conversion according to an embodiment of the present application.
  • FIG20 is a second schematic diagram of a mapping relationship between a service flow and a determined service node according to an embodiment of the present application
  • FIG21 is a fifth example diagram of a first data packet based on IPv6 according to an embodiment of the present application.
  • FIG22 is a third example diagram of a service response according to an embodiment of the present application.
  • FIG23 is a seventh example diagram of a data packet after address translation according to an embodiment of the present application.
  • FIG24 is an eighth example diagram of a data packet after address translation according to an embodiment of the present application.
  • FIG25 is a schematic diagram of a structure of a device for implementing a computing service according to an embodiment of the present application.
  • FIG26 is a second structural diagram of the device for implementing the computing service according to an embodiment of the present application.
  • FIG27 is a schematic diagram of the structure of a communication device according to an embodiment of the present application.
  • Figure 28 is a schematic diagram of the hardware structure of the network side device of an embodiment of the present application.
  • first, second, etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by “first” and “second” are generally of the same type, and the number of objects is not limited.
  • the first object can be one or more.
  • “and/or” in the specification and claims represents at least one of the connected objects, and the character “/" generally represents that the objects associated with each other are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency Division Multiple Access
  • SC-FDMA Division Multiple Access
  • NR New Radio
  • NR terminology is used in most of the following descriptions, but these techniques can also be applied to applications other than NR system applications, such as 6th Generation (6G) communication systems.
  • 6G 6th Generation
  • FIG1 shows a block diagram of a wireless communication system applicable to an embodiment of the present application.
  • the wireless communication system includes a terminal 11 and a network side device 12 .
  • the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (AR)/virtual reality (VR) device, a robot, a wearable device (Wearable Device), a vehicle user equipment (VUE), a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (a home appliance with wireless communication function, such as a refrigerator, a television, a washing machine or furniture, etc.), a game console, a personal computer (personal computer, PC), a teller machine or a self-service machine and other terminal side devices, and the wearable device includes: a smart watch
  • the network side device 12 may include an access network device or a core network device, wherein the access network device may also be referred to as a wireless access network device, a wireless access network (Radio Access Network, RAN), a wireless access network function or a wireless access network unit.
  • the access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point or a wireless local area network (Wireless Local Area Network, WiFi) node, etc.
  • the base station may be referred to as a node B, an evolved node B (Evolved Node B, eNB), an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a home B node, a home evolved B node, a transmission reception point (Transmission Reception Point, TRP) or other appropriate terms in the field, as long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary, it should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.
  • the core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), edge application service discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data storage (Unified Data Repository, UDR), home user server (Home Subscriber Server, HSS), centralized network configuration (CNC), network storage function (Network Repository Function, NRF), network exposure function (Network Exposure Function, NEF), local NEF (Local NEF, or L-NEF), Binding Support Function (BSF), Application Function (AF), etc. It should be noted that in the embodiment of the present application, only the core network
  • IETF CFN has studied and proposed a solution for the integration of wired transmission and computing power in the case of dynamic changes in computing power provided by multiple mobile edge computing (MEC) connected to different transmission devices (such as routers).
  • MEC mobile edge computing
  • This solution solves how to obtain the service and computing power information attached to a CFN node (CFN node) in the transmission bearer network, and selects and routes service nodes based on service information, computing power information and transmission overhead.
  • CFN node CFN node
  • the CFN control plane process is used to obtain the service and computing power information attached to a certain CFN node.
  • the CFN node in FIG2 may be a router.
  • the mobile edge computing (MEC) platform management node connected to the CFN node 3 sends service information registration/update/revocation to the CFN node 3.
  • the information includes at least a service identifier (service ID, SID) and a binding identifier/IP (Binding ID/IP, BID/BIP).
  • SID is a unique ID that identifies a service, which can be an anycast address (for example, there is a class of IP addresses in IPv6 that are anycast addresses), and BID/BIP is used to access a specific service instance (also called a service node), which can be a unicast address (unicast address). That is, if different MECs provide the same service, the SID of the same service is the same, but the service instances of different MECs have different BID/BIPs.
  • the MEC platform management node sends the computing load update of the service to the CFN node 3, including the SID and computing load information.
  • the computing load information includes the CPU used, the number of sessions being served, the number of queries per second, the computation delay, etc.
  • CFN node 3 can update the above service information and computation load information to other CFN nodes (such as CFN node 1 and node 2) within the configured range through a routing protocol (such as Border Gateway Protocol (BGP)).
  • the service includes SID, the CFN node identifier (CFN node 3) that can be routed to the SID, and the computation load information.
  • CFN node 1 and node 2 the same process is used to send the service information and computation load information attached to CFN node 1 and node 2 to other nodes within the configured range.
  • each CFN node After multiple CFN nodes share information with each other, each CFN node obtains all service information and computation load conditions within the configured range.
  • a computing load measurement threshold or update timer can be set, and it will only be updated when the threshold is exceeded or the timer expires.
  • Another method is the most appropriate exit node selection method, which is to select an exit with relatively low computing load to avoid fluctuations.
  • the data plane process when the client (such as an APP on the UE) initiates the first request for a service flow, the destination address of the request is SID (which can be the anycast IP address of the service obtained through the Domain Name System (DNS)), and the source address is the client IP (client_IP).
  • SID which can be the anycast IP address of the service obtained through the Domain Name System (DNS)
  • client_IP client IP
  • the destination address of the request is identified as SID
  • the egress CFN node (CFN egress) is selected based on the service information and calculation load information obtained.
  • the ingress CFN node is the first CFN node to receive the data request
  • the egress CFN node is the CFN node that routes to the selected target service node.
  • the ingress CFN node After selecting the egress CFN node, the ingress CFN node will add the external (outer) source address and destination address, where the source address is the IP address of the ingress CFN node 1, and the destination address is the IP address of the egress CFN node 3.
  • CFN node 3 After receiving the IP packet, CFN node 3 removes the outer source and destination IP according to the mapping relationship between SID2 and BIP32 it obtains, and forwards (routes) it to the service instance of BIP32.
  • the service response is the reverse process of the above, which will not be repeated here.
  • D-Router is a node that supports dynamic anycast (Dyncast). That is, it can understand the metrics related to the network and the metrics related to the service instance, make forwarding decisions based on instance affinity and maintain instance affinity, and forward messages belonging to the same business requirement to the same instance.
  • Dyncast Metric Agent is a dyncast-specific agent that can collect and send metrics updates from the network and instances, but does not perform forwarding decisions. D-MA can run on D-Router or be implemented as a separate module (such as a software library) parallel to the service instance.
  • the resources and status of different service instances are propagated from the D-Router connected to the edge site where the service is deployed to the D-Router connected to the client.
  • D-Router also collects network topology and status information.
  • the entry D-Router that receives the client's business request independently decides which service instance to access based on the status of the service instance and the network status, and maintains the affinity of the instance.
  • the resources and status of different service instances are reported to the network controller from the D-Routers connected to the edge sites where the services are deployed.
  • the controller collects network topology and status information. The controller makes routing decisions for each entry D-Router based on the service instance status and network status, and downloads the decisions to all entry D-Routers.
  • the service flow can be divided into the following cases:
  • Case 1 Terminal A requests, and the service result is returned to the terminal computing power unloading of terminal A;
  • Terminal A requests and the service result is provided to terminal B, which is the fusion of inter-terminal communication and computing;
  • Case 3 Terminal A requests, and the service result is provided to the application function/application server, which is the communication and computing integration between the terminal and the application function/server;
  • Case 4 Application function/application server requests, service results are provided to terminal A, and communication and computing between the terminal and application function/server are integrated;
  • Case 5 Application function/application server M requests, and the service result is returned to application function/application server M, and the application function/application server computing power is offloaded;
  • Application function/application server M requests and service results are returned to application function/application server N, which is the fusion of communication and computing between application functions/application servers.
  • IPv6 Internet Protocol Version 6
  • IPv4 routing and timestamp functions are implemented in this way, and other features (such as fragmentation and jumbo packets) are not supported.
  • IPv6 header is rarely used in IPv6 (but still needed), so no corresponding bits are allocated for them in the IPv6 header.
  • the IPv6 header is fixed to 40 bytes, and the extension header is added only when needed.
  • the extension header is required to be processed only by the end host (with one exception).
  • Segment List Encode n segments by sorting the path in reverse order. The first position is the last segment, and the last position is the first segment.
  • Next Header 43 corresponds to the above SRv6 extension header.
  • Next Header field value 0. This option is mainly used to specify the transmission parameters for each hop on the transmission path. Each intermediate node on the transmission path must read and process this field.
  • the main applications of the hop-by-hop option header are as follows:
  • RSVP Resource Reservation Protocol
  • the destination option header carries some information that only the destination node will process. Currently, the destination option header is mainly used in mobile IPv6.
  • Next Header field value 43, the routing header is similar to the Loose Source and Record Route option of IPv4. This header can be used by IPv6 source nodes to force packets to pass through specific routers;
  • IPv6 message sending is also subject to the Maximum Transmission Unit (MTU) limit. When the message length exceeds the MTU value, the message needs to be sent in segments. In IPv6, segmented sending uses the segment header.
  • MTU Maximum Transmission Unit
  • Next Header field value 51. This header is used by IPSec to provide authentication, data integrity, and replay protection. It also protects some fields in the IPv6 basic header.
  • Next Header field value 50. This header is used by IPSec to provide authentication, data integrity, replay protection, and confidentiality of IPv6 data, similar to the authentication header.
  • an embodiment of the present application provides a method for implementing a computing service, including:
  • Step 51 The first node receives a first data packet sent by a service request sending node, wherein the header of the first data packet includes at least one of the following: an identifier of the service request sending node, an identifier of a service response receiving node, and a service identifier of the requested service;
  • the first data packet may be the first data packet of the service flow sent by the service request sending node (also referred to as a service request data packet), or may be a subsequent data packet of the service flow, such as the second data packet, the third data packet, etc.
  • the service request sending node and the service response receiving node may be the same node or different nodes.
  • Step 52 The first node performs address translation on the first data packet, wherein the first node performs address translation on the first data packet includes: translating the source address of the first data packet into the identifier of the service response receiving node or the identifier of the first node, and translating the destination address of the first data packet into the identifier of the service node providing the requested service or the identifier of a routing node connected to the service node;
  • a service node may also be referred to as a service instance.
  • Potential service instances include online conferences, simultaneous interpretation, virtual digital humans, augmented reality (AR)/virtual reality (VR), artificial intelligence (AI) model training, AI reasoning, image recognition, video rendering, etc.
  • AR augmented reality
  • VR virtual reality
  • AI artificial intelligence
  • Step 53 The first node sends the first data packet after address conversion.
  • the following is an introduction to each information in the header of the first data packet.
  • Service ID which is a unique ID for a service. It can be an anycast IP address or a predefined service ID. An identification (such as a specific IPv4 address negotiated by the service node, router and first node; or a value of a predefined bit length, such as a MAC address, etc.) Accordingly, it means that the service node needs to be able to provide the identified service.
  • the identifier of the node sending the service request used to identify the node sending the service request. It can be a unicast IP address, a Media Access Control (MAC) address, etc., or an identifier defined by the 3rd Generation Partnership Project (3GPP), such as a Subscription Permanent Identifier (SUPI).
  • 3GPP 3rd Generation Partnership Project
  • the service response receiving node identifier is used to identify the node receiving the service response. It can be a unicast IP address, a MAC address, or an identifier defined by 3GPP, such as SUPI. If the service response receiving node is the same as the service request sending node, the service response receiving node identifier may not be required.
  • the first information further includes at least one of the following:
  • the computational complexity measurement required for the requested service is used to measure the computational load required for the requested service.
  • it can be a value calculated by weighting multiple parameters (such as CPU/Graphics Processing Unit (GPU) consumption and/or the number of related sessions).
  • the service provider can define a digital value of the service load by integrating bandwidth resources, number of requests, and computing resources.
  • the computational load measurement can also be a set of parameters, including at least one of the following: the number of central processing unit (CPU) cores, the number of service sessions, computing latency, and the characterization of computing resource requirements in units of Turing, hash rate, TOPS/GOPS/MOPS, FLOPS, etc.
  • a service may usually be deployed on one or more servers.
  • a server has multiple CPUs, and a CPU has multiple CPU cores.
  • Turing (Turing Unit, TU) is the world's first creation of the Turing Fog Foundation, which defines an objective unit of computing power measurement for production nodes.
  • Hash rate also known as computing power, is a unit of measurement for the processing power of the Bitcoin network. It is the speed at which a computer (CPU) calculates the output of a hash function.
  • the Bitcoin network must perform intensive mathematical and cryptographic operations for security purposes. For example, when the network reaches a hash rate of 10Th/s, it means that it can perform 10 trillion calculations per second.
  • TOPS/GOPS/MOPS is a unit of processor computing power
  • 1TOPS means that the processor can perform one trillion operations per second. It is generally used as a measure of CPU computing power.
  • 1GOPS means that the processor can perform one billion operations per second
  • 1MOPS means that the processor can perform one million operations per second.
  • Floating-point operations per second FLOPS is the number of floating-point operations performed per second.
  • the computing delay required for the requested service such as the maximum computing delay required for the requested service
  • the response time required for the requested service refers to the time taken from initiating a service request to receiving a response from the server.
  • Memory information required for the requested service memory information such as sustainable memory bandwidth and memory random access rate;
  • Storage information required for the requested service may include, for example, the number of read and write operations per second (IOPS), storage bandwidth, response time, and metadata operations;
  • IOPS read and write operations per second
  • the network bandwidth required for the requested service may include at least one of the following: bandwidth within the mobile network, bandwidth outside the mobile network, and minimum bandwidth of the internal and external networks;
  • the service duration required by the requested service is used to indicate the maximum duration of the service from the first service message. How long will it take to end?
  • the identifier of the service request sending node is indicated by the source address field in the header of the first data packet;
  • the identifier of the service response receiving node is indicated by the destination address field in the header of the first data packet;
  • the service identifier is indicated by the extended header field in the header of the first data packet;
  • the identifier of the service request sending node is indicated by the source address field in the header of the first data packet; the service identifier is indicated by the destination address field in the header of the first data packet; and the identifier of the service response receiving node is indicated by the extended header field in the header of the first data packet.
  • the first node performing address conversion on the first data packet also includes: the first node adding a destination option header to the first data packet, the destination option header including a source address field, and the source address field of the destination option header indicates an identifier of the node sending the service request.
  • converting the source address of the first data packet into the identifier of the service response receiving node or the identifier of the first node includes: modifying the identifier of the service request sending node in the source address field of the first data packet into the identifier of the service response receiving node or the identifier of the first node;
  • an external source address field is added to the first data packet, where the external source address field indicates the identifier of the service response receiving node or the identifier of the first node.
  • converting the destination address of the first data packet into an identifier of a service node providing the requested service or an identifier of a routing node connected to the service node includes: the first node modifies the identifier of the service response receiving node in the destination address field of the first data packet to the identifier of the service node or the identifier of the routing node connected to the service node; or, the first node adds an external destination address field to the first data packet, and the external destination address field indicates the identifier of the service node or the identifier of the routing node connected to the service node.
  • the source address of the first data packet is converted into the identifier of the first node
  • the destination address of the first data packet is converted into the identifier of the routing node connected to the service node, including: the first node adds an external source address field and an external destination address field to the first data packet, the external source address field indicates the identifier of the first node, and the external destination address indicates the identifier of the routing device connected to the service node.
  • the first node performs address conversion on the first data packet and further includes: if the identifier of the service response receiving node is indicated by an extended header field in the header of the first data packet, the first node maintains the internal source address of the first data packet as the identifier of the service request sending node, converts the internal destination address into the identifier of the service response receiving node, and deletes the extended header field.
  • the first node performing address conversion on the first data packet includes:
  • the first node acquires first information, the first information including at least one of the following: an identifier of the node sending the service request, an identifier of the node receiving the service response, and a service identifier of the requested service;
  • the first node performs address translation on the first data packet according to the first information.
  • the first node performing address conversion on the first data packet includes:
  • the first node receives address conversion indication information sent by the second node, the address conversion indication information is determined by the second node according to the received first information, the first information including at least one of the following: an identifier of the node sending the service request, an identifier of the node receiving the service response and a service identifier of the requested service;
  • the first node performs address conversion on the first data packet according to the address conversion indication information.
  • address mapping and address translation are decoupled and are not completed on the same node. Address mapping is completed by the second node, and address translation is completed by the first node.
  • the address conversion indication information includes at least one of the following:
  • Source address conversion indication used to indicate whether to perform source address conversion
  • Destination address conversion indication used to indicate whether to perform destination address conversion
  • An extended header adding indication is used to indicate whether to add an extended header
  • the address conversion indication information can be expressed in the following form: Address conversion indication information 1: source address ⁇ , destination address ⁇ , source port number ⁇ , destination port number ⁇ , protocol, source address modified to ⁇ , destination address modified to ⁇ , effective time.
  • the first node before the first node performs address conversion on the first data packet, the first node also includes: the first node determines the identifier of the service node; or, the first node receives the identifier of the service node sent by a third node, and the third node is a node that determines the service node.
  • the method further includes:
  • the service node is determined according to the mapping relationship, where the mapping relationship is a mapping relationship between the identifier of the service flow of the requested service and the identifier of the service node.
  • mapping relationship In the embodiment of the present application, optionally, in the mapping relationship:
  • the service flow is identified by the following information: an identifier of a service request sending node, an identifier of a service response receiving node, a PDU session identifier, and a QoS flow identifier;
  • the service flow is identified by the following information: the IP address and/or port of the node sending the service request, and the IP address and/or port of the node receiving the service response;
  • the service flow is identified by the following information: the IP address and/or port of the node sending the service request, and the IP address and/or port of the service node;
  • the service flow is identified by the following information: QoS flow identification.
  • the method further includes:
  • the first node receives a second data packet sent by the service node, wherein a header of the second data packet includes at least one of the following: an identifier of the service node, an identifier of the first node, and a service identifier of the requested service;
  • the first node performs address translation on the second data packet, wherein the first node performs address translation on the second data packet comprises: translating a source address of the second data packet into an identifier of the service request sending node, and translating a destination address of the second data packet into an identifier of the service response receiving node;
  • the first node sends a second data packet after performing address conversion to the service response receiving node.
  • converting the source address of the second data packet into the identifier of the service request sending node includes:
  • the external source address field of the second data packet is deleted, the external source address field indicates the identifier of the service node, and the internal source address field of the second data packet is retained, the internal source address field indicates the identifier of the service request sending node.
  • converting the destination address of the second data packet into the identifier of the service response receiving node includes:
  • the external destination address field of the second data packet is deleted, the external destination address field indicates the identifier of the first node, and the internal destination address field of the second data packet is retained, the internal destination address field indicates the identifier of the service response receiving node.
  • the first node acts as an address conversion node, forwarding data packets between the service request sending node, the service node and the service response receiving node.
  • the first node itself can also act as a service node, in which case the above address conversion operation is not required.
  • the present embodiment also provides a method for implementing a computing service, including:
  • Step 61 The second node receives a first request sent by a service request sending node, where the first request includes first information, and the first information includes at least one of the following: an identifier of the service request sending node, an identifier of a service response receiving node, and a service identifier of the requested service;
  • Step 62 The second node selects a first node and determines address conversion indication information according to the first information
  • Step 63 The second node sends a first response to the service request sending node, where the first response is used to indicate that it can assist the service request sending node to complete the address conversion, and the first response includes an identifier of the first node;
  • Step 64 the second node sends the address conversion indication information to the first node according to the identifier of the first node, where the address conversion indication information is used to perform address conversion on the first data packet received from the service request sending node.
  • the address conversion indication information includes at least one of the following:
  • Source address conversion indication used to indicate whether to perform source address conversion
  • Destination address conversion indication used to indicate whether to perform destination address conversion
  • An extended header adding indication is used to indicate whether to add an extended header
  • the first information further includes at least one of the following:
  • the length of service duration required for the requested service is the length of service duration required for the requested service.
  • the service flow belongs to case 3: terminal A requests, the service result is provided to the application function/application server, and the communication and computing fusion service process between the terminal and the application function/server.
  • Step 1 The first node (such as UPF) receives the first data packet (such as a service request data packet, where the first message or the first data packet in the service process is referred to as a service request data packet) sent by the service request sending node (UE).
  • UE service request sending node
  • An example of the first data packet based on IPv6 is shown in Figure 7, where the source IP address (Source address) is the UE IP address, that is, the identifier of the service request sending node; the destination IP address is the IP address of the application server, that is, the identifier of the service response receiving node.
  • the service identifier can be indicated by the following extended header, for example, by setting the next header to a certain value (such as 1) to indicate that the header indicates a service identifier, such as an anycast IP address.
  • a certain value such as 1
  • the length and order of each field can be adjusted according to the situation, and only one example is given here.
  • Step 2 The first node identifies that the service request requires network assistance to select a suitable service node based on the service identification field, and maintains the mapping relationship between the service flow and the determined service node. For example, the corresponding relationship between the service request sending node information (IP address and port number), the service response receiving node information (IP address and port number) and the service node information (IP address and port number) is used as the mapping relationship to ensure that subsequent data packets of the service are processed by the same service node.
  • IP address and port number IP address and port number
  • IP address and port number IP address and port number
  • the first node in the embodiment of the present application can be a UPF with the function of determining the service node, or it can be a UPF that obtains the determined service node information from a control plane node (such as SMF or a newly added computing management function, etc.), or it can be a CNF node or a D-Router.
  • a control plane node such as SMF or a newly added computing management function, etc.
  • the first node may perform the processing of step 2a, 2b or 2c, as described in detail below.
  • Step 2a If the first node can provide the service indicated by the service identifier (such as video rendering, etc.) and meet the service quality requirements, then the first node performs service processing, generates a service response, and sends the service response to the application function/application server.
  • a schematic diagram of the service response is shown in Figure 8.
  • the service node is determined according to the service identifier, and the service processing is completed at the first node. For nodes other than the first node, the service node determination and service processing processes are invisible.
  • Step 2b Or if the first node can determine the service node based on the service information and/or computing load information of the service node, as well as the network topology and/or status information, etc. obtained.
  • the first node can perform address conversion based on the determined service node.
  • the first node can also perform address conversion based on the address conversion indication information obtained from other nodes. Convert the source address to the address of the service response receiving node, that is, the application server IP address. Convert the destination address to the determined service node identifier, such as the unicast IP address of the service instance.
  • a converted data packet is shown in Figure 9, where the following two cases are taken as examples:
  • Case 2 A service node provides all services in the service ID list in the service request.
  • Step 2c The solution of step 2b is more suitable for requests with better transmission link quality from the service request sending node to the service node or UDP services, because if packet loss occurs, the service node may also send packet loss retransmission related messages to the service response receiving node.
  • Step 2c is a potential improvement solution for step 2b.
  • the first node can determine the service node based on the service information and/or computing load information of the service node, as well as the network topology and/or status information obtained.
  • the first node can perform address conversion based on the determined service node.
  • the first node can also perform address conversion based on the address conversion indication information obtained from other nodes.
  • the source address is converted to the address of the service response receiving node, that is, the application server IP address.
  • the destination address is converted to the determined service node identifier, such as the unicast IP address of the service instance.
  • the destination option header with the next header field value of 60 is reused.
  • the destination option header carries some information that only the destination node will process.
  • the UE IP is indicated in the field with the Next header value of 60. This field is only processed at the destination address (i.e., the service node). If packet loss and retransmission occur, the service node can send ACK/NACK to the UE based on this field instead of sending it to the application server. If packet loss and retransmission do not occur, the destination node (i.e., the service node) does not need to use this extended IP header with the next header field of 60.
  • a converted data packet is shown in Figure 10.
  • Step 3 If the first node is not a service node, the first node forwards the service request after the address translation to the service node.
  • Step 4 The service node processes the request, generates a service response, and sends it to the application server.
  • the first node receives subsequent messages of the service sent by the UE and adopts the same processing and forwarding methods according to the saved mapping relationship, thereby ensuring the consistency of service performance, which can also be called flow affinity.
  • the service flow belongs to case 3: terminal A requests, the service result is provided to the application function/application server, and the communication and computing fusion service process between the terminal and the application function/server.
  • Step 1 The first node (such as UPF) receives the first data packet (such as a service request data packet, where the first message or the first data packet in the service process is referred to as a service request data packet) sent by the first service request sending node (UE).
  • UE first service request sending node
  • An example of the first data packet based on IPv6 is shown in Figure 11, where the source IP address (Source address) is the UE IP address, that is, the identifier of the service request sending node; the destination IP address is the service identifier (such as an anycast IP address).
  • the identifier of the service response receiving node can be indicated by the following extended header, and the next header is set to a certain value (such as 2) to indicate that the header indicates the identifier of the service response receiving node, such as a unicast IP address.
  • a certain value such as 2
  • the length and order of each field can be adjusted according to the situation, and only one example is given here.
  • Step 2 The first node identifies that the service request requires network assistance to select a suitable service node based on the destination IP address (service identifier) field, and maintains the mapping relationship between the service flow and the determined service node. For example, the corresponding relationship between the service request sending node information (IP address and port number), the service response receiving node information (IP address and port number) and the service node information (IP address and port number) is used as the mapping relationship to ensure that subsequent data packets of the service are processed by the same service node.
  • IP address and port number IP address and port number
  • IP address and port number IP address and port number
  • the first node may perform the processing of step 2a, 2b or 2c, as described in detail below.
  • Step 2a If the first node can provide the service indicated by the service identifier in the destination address field (e.g., video rendering, etc.), and meets the service quality requirements, then the first node performs service processing and generates a service response.
  • the service response is sent to the application function/application server, and a schematic diagram of the service response is shown in FIG12.
  • the service node is determined according to the service identifier, and the service processing is completed at the first node. For nodes other than the first node, the service node determination and service processing processes are invisible.
  • Step 2b Or if the first node can determine the service node based on the service information and/or computing load information of the service node, as well as the network topology and/or status information, etc. obtained.
  • the first node can perform address conversion based on the determined service node.
  • the first node can also perform address conversion based on the address conversion indication information obtained from other nodes. Convert the source address to the address of the service response receiving node, that is, the application server IP address. Convert the destination address to the determined service node identifier, such as the unicast IP address of the service instance.
  • a data packet after address conversion is shown in Figure 13.
  • Step 2c The solution of step 2b is more suitable for requests with better transmission link quality from the service request sending node to the service node or UDP services, because if packet loss occurs, the service node may also send packet loss retransmission related messages to the service response receiving node.
  • Step 2c is a potential improvement solution for step 2b.
  • the first node can determine the service node based on the service information and/or computing load information of the service node, as well as the network topology and/or status information obtained.
  • the first node can perform address conversion based on the determined service node.
  • the first node can also perform address conversion based on the address conversion indication information obtained from other nodes.
  • the source address is converted to the address of the service response receiving node, that is, the application server IP address.
  • the destination address is converted to the determined service node identifier, such as the unicast IP address of the service instance.
  • the destination option header with the next header field value of 60 is reused.
  • the destination option header carries some information that only the destination node will process.
  • the UE IP is indicated in the field with the Next header value of 60. This field is only processed at the destination address (i.e., the service node). If packet loss and retransmission occur, the service node can send ACK/NACK to the UE based on this field instead of sending it to the application server. If packet loss and retransmission do not occur, the destination node (i.e., the service node) does not need to use this extended IP header with the next header field value of 60.
  • a converted The data packet is shown in Figure 14.
  • Step 3 If the first node is not a service node, the first node forwards the service request after the address translation to the service node.
  • Step 4 The service node processes the request, generates a service response, and sends it to the application server.
  • the first node receives subsequent messages of the service sent by the UE and adopts the same processing and forwarding methods according to the saved mapping relationship, thereby ensuring the consistency of service performance, which can also be called flow affinity.
  • the service flow belongs to situation 2: terminal A requests, the service result is provided to terminal B, and the communication and computing between terminals are integrated into the service process.
  • Step 1 The first node (such as UPF) receives the first data packet (such as a service request data packet, where the first message or the first data packet in the service process is referred to as a service request data packet) sent by the service request sending node (UE).
  • UE service request sending node
  • An example of the first data packet based on IPv6 is shown in Figure 15, where the source IP address (Source address) is the UE A IP address, that is, the identifier of the service request sending node; the destination IP address is the UE B IP address that receives the service response, that is, the identifier of the service response receiving node.
  • the service identifier can be indicated by the following extended header, and the next header is set to a certain value (such as 1) to indicate that the header indicates the service identifier, such as an anycast IP address.
  • a certain value such as 1
  • the length and order of each field can be adjusted according to the situation, and only one example is given here.
  • Step 2 The first node identifies that the service request requires network assistance to select a suitable service node based on the service identification field, and maintains the mapping relationship between the service flow and the determined service node. For example, the corresponding relationship between the service request sending node information (IP address and port number), the service response receiving node information (IP address and port number) and the service node information (IP address and port number) is used as the mapping relationship to ensure that subsequent data packets of the service are processed by the same service node.
  • IP address and port number IP address and port number
  • IP address and port number IP address and port number
  • the first node in the embodiment of the present application may be a UPF having a function of determining a service node, or may be a UPF from a control plane.
  • the UPF from which the node (such as SMF or newly added computing management function, etc.) obtains the determined service node information may also be a CNF node or a D-Router.
  • the first node may perform the processing of step 2a or 2b, as described in detail below.
  • Step 2a If the first node can determine the service node based on the service information and/or computing load information of the service node, as well as the network topology and/or status information, etc. obtained.
  • the first node can perform address conversion based on the determined service node. Or the first node can also perform address conversion based on the address conversion indication information obtained from other nodes.
  • the source address is converted to the first node identifier (such as the first node IP address), and the destination address is converted to the identifier of the determined service node, such as the unicast IP address of the service instance.
  • a converted data packet is shown in Figure 16, and the following two cases are taken as examples:
  • Case 2 A service node provides all services in the service ID list in the service request.
  • a mapping relationship between a service flow and a determined service node is shown in FIG17 .
  • the service node processes it, generates a service response (the source address is the service node identifier, and the destination address is the first node) and sends it to the first node.
  • the first node performs corresponding address conversion on the received response (the source address is the address of UE A, and the destination address is the address of UE B) according to the maintained mapping relationship, and forwards it to UE B.
  • Step 2b The solution of step 2a is more suitable for the case where both the service request sending node and the service response receiving node are processed by the first node (such as routing). If the service response is processed by the first node after being processed by the service node, the delay may be increased. Then step 2b is a potential improvement solution for step 2a.
  • the external destination address is the identifier of the routing device (such as a CFN node, or other first node entities with the same function as the first node, i.e., other UPFs, etc.) connected to the service node, such as an IP address.
  • the external source address is the first node identifier.
  • the service node is determined, and the address conversion and/or forwarding between the service request sending node and the service node is completed by the first node.
  • the address conversion and/or forwarding between the service node and the service response receiving node is completed by the routing device.
  • the service node can reuse the destination option header when the next header field value is 60.
  • the destination option header carries some information that only the destination node will process.
  • the UE A IP is indicated in the field with a Next header value of 60. This field is only processed at the destination address (i.e., UE B), so that UE B can obtain the message that the data packet is processed by the service node indicated by the source address for UE A.
  • the first node receives subsequent messages of the service sent by the UE and adopts the same processing and forwarding methods according to the saved mapping relationship, thereby ensuring the consistency of service performance, which can also be called flow affinity.
  • the service flow belongs to case 2: terminal A requests, the service result is provided to terminal B, and the terminals Communication and computing fusion service process.
  • Step 1 The first node (such as UPF) receives the first data packet (such as a service request data packet, where the first message or the first data packet in the service process is referred to as a service request data packet) sent by the service request sending node (UE).
  • UE service request sending node
  • An example of the first data packet based on IPv6 is shown in Figure 18, where the source IP address (Source address) is the UE IP address, that is, the identifier of the service request sending node; the destination IP address is the service identifier (such as an anycast IP address).
  • the identifier of the service response receiving node can be indicated by the following extended header, and the next header is set to a certain value (such as 2) to indicate that the header indicates the identifier of the service response receiving node, such as a unicast IP address.
  • a certain value such as 2
  • the length and order of each field can be adjusted according to the situation, and only one example is given here.
  • Step 2 The first node identifies that the service request requires network assistance to select a suitable service node based on the service identification field of the destination address field, and maintains the mapping relationship between the service flow and the determined service node. For example, the corresponding relationship between the service request sending node information (IP address and port number), the service response receiving node information (IP address and port number) and the service node information (IP address and port number) is used as the mapping relationship to ensure that subsequent data packets of the service are processed by the same service node.
  • IP address and port number IP address and port number
  • IP address and port number IP address and port number
  • the first node in the embodiment of the present application can be a UPF with the function of determining the service node, or it can be a UPF that obtains the determined service node information from a control plane node (such as SMF or a newly added computing management function, etc.), or it can be a CNF node or a D-Router.
  • a control plane node such as SMF or a newly added computing management function, etc.
  • the first node may perform the processing of step 2a or 2b, as described in detail below.
  • Step 2a If the first node can determine the service node based on the service information and/or computing load information of the service node, as well as the network topology and/or status information, etc. obtained.
  • the first node can perform address conversion based on the determined service node. Or the first node can also perform address conversion based on the address conversion indication information obtained from other nodes.
  • the source address is converted to the first node identifier (such as the first node IP address), and the destination address is converted to the determined service node identifier, such as the unicast IP address of the service instance.
  • a converted data packet is shown in Figure 19, where the following two cases are taken as examples:
  • Case 2 A service node provides all services in the service ID list in the service request.
  • a mapping relationship between a service flow and a determined service node is shown in FIG20 .
  • the service node processes it, generates a service response (the source address is the service node identifier, and the destination address is the first node) and sends it to the first node.
  • the first node performs corresponding address conversion on the received response (the source address is the address of UE A, and the destination address is the address of UE B) according to the maintained mapping relationship, and forwards it to UE B.
  • Step 2b The solution of step 2a is more suitable for the case where both the service request sending node and the service response receiving node are processed by the first node (such as routing). If the service response is processed by the first node after the service node, the delay may be increased. Then step 2b is a potential improvement solution for step 2a.
  • the external destination address is the identifier of the routing device (such as a CFN node, or other first node entities with the same function as the first node, i.e., other UPFs, etc.) connected to the service node, such as an IP address.
  • the external source address is the first node identifier.
  • the internal source address is still UE A IP, and the internal destination address is converted to UE B IP of R_Destination Address. Remove the header indicating the service response receiving node in step 1. In this way, the service node is determined, and the address conversion and/or forwarding between the service request sending node and the service node is completed by the first node. The address conversion and/or forwarding between the service node and the service response receiving node is completed by the routing device.
  • the routing device connected to the service node After receiving the service request data packet forwarded by the first node, the routing device connected to the service node converts the destination address into a service node identifier. Then the service node processes the service request data packet after receiving it and generates a service response.
  • the service node can reuse the destination option header when the next header field value is 60.
  • the destination option header carries some information that only the destination node will process.
  • the UE A IP is indicated in the field with a Next header value of 60. This field is only processed at the destination address (i.e., UE B), so that UE B can obtain the message that the data packet is processed by the service node indicated by the source address for UE A.
  • the first node receives subsequent messages of the service sent by the UE and adopts the same processing and forwarding methods according to the saved mapping relationship, thereby ensuring the consistency of service performance, which can also be called flow affinity.
  • the first node performs an address conversion processing service flow according to the address conversion indication information sent by the second node.
  • Step 1 The second node (such as SMF) receives the first message (such as service relationship registration request) sent by the service request sending node (UE).
  • the first message can be a newly defined NAS message, or it can be an extension of the NAS message of the related technology (such as PDU session establishment or modification, etc.).
  • the NAS message extension in the related technology is that when the UE needs to perform communication and computing fusion services, the UE sends a PDU session establishment or modification to the SMF.
  • the first message packet is the first information.
  • the content of the first information refers to the above embodiment and will not be repeated.
  • Step 2 The second node (such as SMF) selects the first node (such as UPF) according to the received first information, and establishes or modifies the PDU session.
  • the first node can perform address conversion according to the instruction of the second node.
  • Step 3 The second node sends a service relationship registration response to the UE, wherein the service relationship registration response indicates whether the network can assist the UE in completing the address conversion of the registered service, including the mapping of the service identifier to the service instance identifier and/or the address conversion of the service response receiving node.
  • the second node sends the address conversion indication information to the first node.
  • An address conversion indication information is as follows, including one or more of the following.
  • the target value of the extension header which is valid only when indicating to add an extension header. It can include the Next header value, the extension header length or the extension header content, etc., and set the extension header to the indicated value of this field.
  • UE ID, PDU session ID, and QoS flow ID X in the address conversion indication information are used to indicate the service flow, and can also be identified by source IP address, destination IP address, source port number, and destination port number.
  • the second node has determined the serving node that the UE needs to serve, and/or the second node has determined the address conversion method according to the function of the first node.
  • the service request sending node (such as UE) sends a service request data packet (herein, the first message or data packet in the service process is referred to as a service request data packet) to the first node.
  • a service request data packet herein, the first message or data packet in the service process is referred to as a service request data packet
  • Step 1 If the service relationship registration response indicates that the network can assist the UE to complete the address conversion, the service request sending node (such as the UE) sends a service request packet (the first message or data packet in the service process is referred to as a service request packet) to the first node.
  • a service request packet the first message or data packet in the service process is referred to as a service request packet
  • An example of an IPv6-based service request packet is shown in Figure 21, where the source IP address is the UE IP address, that is, the identifier of the service request sending node; the destination ... The IP address of the server is used, that is, the identifier of the service response receiving node.
  • the service identifier can be indicated by the following extended header, and the next header is set to a certain value (such as 1) to indicate that the header indicates the service identifier, such as the anycast IP address.
  • a certain value such as 1
  • the length and order of each field can be adjusted according to the situation, and only one example is given here.
  • Step 2 The first node identifies the service request of the UE according to the address conversion indication information received from the second node, performs address conversion, and maintains the mapping relationship between the service flow and the determined service node. For example, the correspondence between the service request sending node information (IP address and port number), the service response receiving node information (IP address and port number) and the service node information (IP address and port number) is used as a mapping relationship to ensure that subsequent data packets of the service are processed by the same service node. If the address conversion indication information includes the target value of the source address/destination address conversion/extension header, the first node performs conversion according to the address conversion indication information. If the target value of the source address/destination address conversion/extension header is not included, the first node determines the service node according to the service identifier and the obtained service information and calculation load information, and performs address conversion.
  • IP address and port number IP address and port number
  • IP address and port number IP address and port number
  • the first node in the embodiment of the present application can be a UPF with the function of determining the service node, or it can be a UPF that obtains the determined service node information from a control plane node (such as SMF or a newly added computing management function, etc.), or it can be a CNF node or a D-Router.
  • a control plane node such as SMF or a newly added computing management function, etc.
  • the first node may perform the processing of step 2a, 2b or 2c, as described in detail below.
  • Step 2a If the first node can provide the service indicated by the service identifier (such as video rendering, etc.) and meet the service quality requirements, then the first node performs service processing, generates a service response, and sends the service response to the application function/application server.
  • a schematic diagram of the service response is shown in Figure 22.
  • the service node is determined according to the service identifier, and the service processing is completed at the first node. For nodes other than the first node, the service node determination and service processing processes are invisible.
  • Step 2b Alternatively, if the first node can determine the service node based on the service information and/or computing load information of the service node, as well as the network topology and/or status information, etc. obtained, the first node can perform address conversion based on the determined service node. Alternatively, the first node can also perform address conversion based on the service node indication obtained from other nodes.
  • the destination address is converted to the service response receiving node address, that is, the application server IP address.
  • the destination address is converted to the determined service node identifier, such as the unicast IP address of the service instance.
  • a converted data packet is shown in FIG23, where the following two cases are taken as examples:
  • Case 2 A service node provides all services in the service ID list in the service request.
  • Step 2c The solution of step 2b is more suitable for requests with good transmission link quality from the service request sending node to the service node or UDP services, because if packet loss occurs, the service node may also send the packet loss retransmission related message to the service response receiving node.
  • Step 2c is a potential improvement to step 2b.
  • the first node can determine the service node based on the service information and/or computing load information of the service node, as well as the network topology and/or status information obtained.
  • the first node can perform address conversion based on the determined service node.
  • the first node can also perform address conversion based on the address conversion indication information obtained from other nodes. Convert the source address to the address of the service response receiving node, that is, the application server IP address.
  • the destination option header when the next header field value is 60 is reused, and the destination option header carries some information that only the destination node will process.
  • the UE IP is indicated in the Next header field with a value of 60. This field is only processed at the destination address (i.e., the service node). If packet loss and retransmission occur, the service node can send ACK/NACK to the UE based on this field instead of sending it to the application server. If packet loss and retransmission do not occur, the destination node (i.e., the service node) does not need to use this extended IP header with a next header field value of 60.
  • a converted data packet is shown in Figure 24.
  • Step 3 If the first node is not a service node, the first node forwards the service request after the address translation to the service node.
  • Step 4 The service node processes the request, generates a service response, and sends it to the application server.
  • the first node receives subsequent messages of the service sent by the UE and adopts the same processing and forwarding methods according to the saved mapping relationship, thereby ensuring the consistency of service performance, which can also be called flow affinity.
  • the implementation method of the computing service provided in the embodiment of the present application can be executed by a computing service implementation device.
  • the implementation method of the computing service implemented by the computing service implementation device is taken as an example to illustrate the computing service implementation device provided in the embodiment of the present application.
  • the present embodiment further provides a computing service implementation device 250, including:
  • the first receiving module 251 is used to receive a first data packet sent by a service request sending node, wherein the header of the first data packet includes at least one of the following: an identifier of the service request sending node, an identifier of a service response receiving node, and a service identifier of the requested service;
  • a first address conversion module 252 is used to perform address conversion on the first data packet, wherein the address conversion on the first data packet includes: converting the source address of the first data packet into the identifier of the service response receiving node or the identifier of the first node, and converting the destination address of the first data packet into the identifier of the service node providing the requested service or the identifier of a routing node connected to the service node;
  • the first sending module 253 is used to send the first data packet after the address conversion is performed.
  • the identifier of the service request sending node is indicated by a source address field in a header of the first data packet
  • the identification of the service response receiving node is indicated by a destination address field in a header of the first data packet
  • the service identifier is indicated by an extended header field in a header of the first data packet
  • the identifier of the service request sending node is indicated by a source address field in a header of the first data packet
  • the service identifier is indicated by a destination address field in a header of the first data packet
  • the identifier of the service response receiving node is indicated by an extended header field in the header of the first data packet.
  • the first address conversion module 252 is further used to add a destination option header to the first data packet, the destination option header including a source address field, and the source address field of the destination option header indicates an identifier of the service request sending node.
  • converting the source address of the first data packet into an identifier of the service response receiving node or an identifier of the first node includes:
  • An external source address field is added to the first data packet, where the external source address field indicates an identifier of the service response receiving node or an identifier of the first node.
  • converting the destination address of the first data packet into an identifier of a service node providing the requested service or an identifier of a routing node connected to the service node includes:
  • An external destination address field is added to the first data packet, where the external destination address field indicates an identifier of the service node or an identifier of a routing node connected to the service node.
  • converting the source address of the first data packet into an identifier of the first node, and converting the destination address of the first data packet into an identifier of a routing node connected to the service node includes:
  • An external source address field and an external destination address field are added to the first data packet, wherein the external source address field indicates an identifier of the first node, and the external destination address field indicates an identifier of a routing device connected to the service node.
  • the first address conversion module 252 is further configured to, if the identifier of the service response receiving node is indicated by an extended header field in the header of the first data packet, keep the internal source address of the first data packet as the identifier of the service request sending node, convert the internal destination address to the identifier of the service response receiving node, and delete the Extension header fields.
  • the first address conversion module 252 is also used to obtain first information, the first information including at least one of the following: the identifier of the node sending the service request, the identifier of the node receiving the service response and the service identifier of the requested service; and perform address conversion on the first data packet based on the first information.
  • the first address conversion module 252 is also used to receive address conversion indication information sent by the second node, and the address conversion indication information is determined by the second node based on the received first information, and the first information includes at least one of the following: the identifier of the node sending the service request, the identifier of the node receiving the service response and the service identifier of the requested service; according to the address conversion indication information, the first data packet is addressed.
  • the address conversion indication information includes at least one of the following:
  • Source address conversion indication used to indicate whether to perform source address conversion
  • Destination address conversion indication used to indicate whether to perform destination address conversion
  • An extended header adding indication is used to indicate whether to add an extended header
  • the first information further includes at least one of the following:
  • the length of service duration required for the requested service is the length of service duration required for the requested service.
  • the computing service implementation device 250 further includes:
  • a first determining module configured to determine an identifier of the service node
  • the second receiving module is used to receive the identifier of the service node sent by a third node, where the third node is a node that determines the service node.
  • the computing service implementation device 250 further includes:
  • the second determination module is used to determine the service node according to the mapping relationship if other first data packets except the first first data packet of the service flow are received, and the mapping relationship is the mapping relationship between the identifier of the service flow of the requested service and the identifier of the service node.
  • the service flow is identified by the following information: an identifier of a service request sending node, an identifier of a service response receiving node, a PDU session identifier, and a QoS flow identifier;
  • the service flow is identified by the following information: the IP address and/or port of the node sending the service request, and the IP address and/or port of the node receiving the service response;
  • the service flow is identified by the following information: the IP address and/or port of the node sending the service request, and the IP address and/or port of the service node;
  • the service flow is identified by the following information: QoS flow identification.
  • the computing service implementation device 250 further includes:
  • a third receiving module is configured to receive a second data packet sent by the service node, wherein a header of the second data packet includes at least one of the following: an identifier of the service node, an identifier of the first node, and a service identifier of the requested service;
  • a second address conversion module is used to perform address conversion on the second data packet, wherein the first node performs address conversion on the second data packet including: converting the source address of the second data packet into the identifier of the node sending the service request, and converting the destination address of the second data packet into the identifier of the node receiving the service response;
  • the second sending module is used to send a second data packet after the address conversion to the service response receiving node.
  • converting the source address of the second data packet into an identifier of the service request sending node includes:
  • the external source address field of the second data packet is deleted, the external source address field indicates the identifier of the service node, and the internal source address field of the second data packet is retained, the internal source address field indicates the identifier of the service request sending node.
  • converting the destination address of the second data packet into the identifier of the service response receiving node includes:
  • the external destination address field of the second data packet is deleted, the external destination address field indicates the identifier of the first node, and the internal destination address field of the second data packet is retained, the internal destination address field indicates the identifier of the service response receiving node.
  • the implementation device of the computing service in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in the electronic device, such as an integrated circuit or a chip.
  • the computing service implementation device provided in the embodiment of the present application can implement each process implemented by the method embodiment of Figure 5 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the present embodiment further provides a computing service implementation device 260, including:
  • a first receiving module 261 is configured to receive a first request sent by a service request sending node, wherein the first request includes first information, and the first information includes at least one of the following: an identifier of the service request sending node, an identifier of a service response receiving node, and a service identifier of the requested service;
  • a processing module 262 configured to select a first node and determine address conversion indication information according to the first information
  • a first sending module 263, configured to send a first response to the service request sending node, where the first response is used to indicate that the service request sending node can be assisted to complete the address conversion, and the first response includes an identifier of the first node;
  • the second sending module 264 is used to send the address conversion indication information to the first node according to the identifier of the first node, and the address conversion indication information is used to perform address conversion on the first data packet received from the service request sending node.
  • the address conversion indication information includes at least one of the following:
  • Source address conversion indication used to indicate whether to perform source address conversion
  • Destination address conversion indication used to indicate whether to perform destination address conversion
  • An extended header adding indication is used to indicate whether to add an extended header
  • the first information further includes at least one of the following:
  • the length of service duration required for the requested service is the length of service duration required for the requested service.
  • the implementation device of the computing service in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in the electronic device, such as an integrated circuit or a chip.
  • the computing service implementation device provided in the embodiment of the present application can implement each process implemented by the method embodiment of Figure 6 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • an embodiment of the present application also provides a communication device 270, including a processor 271 and a memory 272, and the memory 272 stores programs or instructions that can be executed on the processor 271.
  • the program or instruction is executed by the processor 271, the various steps of the implementation method embodiment of the above-mentioned computing service are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
  • the embodiment of the present application also provides a first node, including a processor and a communication interface, wherein the communication interface is used to receive a first data packet sent by a service request sending node, wherein the header of the first data packet includes at least one of the following: an identifier of the service request sending node, an identifier of a service response receiving node, and a service identifier of the requested service; the processor is used to perform address conversion on the first data packet, wherein the address conversion on the first data packet includes: converting the source address of the first data packet to the identifier of the service response receiving node or the identifier of the first node, converting the destination address of the first data packet to the identifier of the service node providing the requested service or the identifier of a routing node connected to the service node; the communication interface is also used to send the first data packet after address conversion.
  • This first node embodiment corresponds to the above-mentioned first node side method embodiment, and each implementation process and implementation method of the above-
  • the embodiment of the present application also provides a second node, including a processor and a communication interface, wherein the communication interface is used to receive a first request sent by a service request sending node, the first request includes first information, and the first information includes at least one of the following: the identifier of the service request sending node, the identifier of the service response receiving node and the service identifier of the requested service; the processor is used to select a first node and determine address conversion indication information according to the first information; the communication interface is also used to send a first response to the service request sending node, the first response is used to indicate that the service request sending node can be assisted to complete the address conversion, and the first response includes the identifier of the first node; the communication interface is also used to send the address conversion indication information to the first node according to the identifier of the first node, and the address conversion indication information is used to perform address conversion on the first data packet received from the service request sending node.
  • This second node embodiment corresponds to the above-mentioned
  • the embodiment of the present application further provides a network side device.
  • the network side device 280 includes: a processor 281, a network interface 282 and a memory 283.
  • the network interface 282 is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the network side device 280 of the embodiment of the present application also includes: instructions or programs stored in the memory 283 and executable on the processor 281.
  • the processor 281 calls the instructions or programs in the memory 283 to execute the methods executed by the modules shown in Figure 25 or Figure 26 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored.
  • a program or instruction is stored.
  • each process of the embodiment of the implementation method of the above-mentioned computing service is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
  • the processor is the processor in the terminal described in the above embodiment.
  • the readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.
  • An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the implementation method embodiment of the above-mentioned computing service, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
  • the embodiments of the present application further provide a computer program/program product, which is stored in a storage medium, and is executed by at least one processor to implement the various processes of the above-mentioned computing service implementation method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the technical solution of the present application can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM/RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.
  • a storage medium such as ROM/RAM, a magnetic disk, or an optical disk
  • a terminal which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente demande appartient au domaine technique des communications sans fil. L'invention concerne un procédé et un appareil de mise en œuvre de service informatique, un dispositif de communication et un support de stockage. Le procédé de mise en œuvre de service informatique selon la présente demande comprend les étapes suivantes : un premier nœud reçoit un premier paquet de données envoyé par un nœud d'envoi de demande de service, un en-tête du premier paquet de données comprenant au moins l'un des éléments suivants : un identifiant du nœud d'envoi de demande de service, un identifiant d'un nœud de réception de réponse de service, et un identifiant de service d'un service demandé ; le premier nœud effectue une conversion d'adresse sur le premier paquet de données, l'étape de conversion d'adresse effectuée par le premier nœud sur le premier paquet de données comprenant : la conversion d'une adresse source du premier paquet de données en l'identifiant du nœud de réception de réponse de service ou un identifiant du premier nœud, et la conversion d'une adresse de destination du premier paquet de données en un identifiant d'un nœud de service qui fournit le service demandé ou un identifiant d'un nœud de routage qui est connecté au nœud de service ; et le premier nœud envoie le premier paquet de données qui a été soumis à une conversion d'adresse.
PCT/CN2023/140074 2022-12-22 2023-12-20 Procédé et appareil de mise en œuvre de service informatique, dispositif de communication, et support de stockage WO2024131812A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211658880.2A CN118250334A (zh) 2022-12-22 2022-12-22 计算服务的实现方法、装置、通信设备及存储介质
CN202211658880.2 2022-12-22

Publications (1)

Publication Number Publication Date
WO2024131812A1 true WO2024131812A1 (fr) 2024-06-27

Family

ID=91554177

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/140074 WO2024131812A1 (fr) 2022-12-22 2023-12-20 Procédé et appareil de mise en œuvre de service informatique, dispositif de communication, et support de stockage

Country Status (2)

Country Link
CN (1) CN118250334A (fr)
WO (1) WO2024131812A1 (fr)

Also Published As

Publication number Publication date
CN118250334A (zh) 2024-06-25

Similar Documents

Publication Publication Date Title
US11929977B2 (en) System, apparatus and method to support data server selection
EP3755117B1 (fr) Procédé de communication et appareil de communication
US20220225075A1 (en) Roaming Signaling Message Sending Method, Related Device, and Communications System
WO2020068605A1 (fr) Systèmes et procédés de sélection de nœuds colocalisés dans un réseau 5g
WO2016150140A1 (fr) Procédé et système de traitement pour un paquet de commande dans une passerelle basée sur un réseau défini par logiciel (sdn)
US20240196273A1 (en) Predictive user plane function (upf) load balancing based on network data analytics
WO2020233249A1 (fr) Procédé de transmission de paquets et appareil associé
CN112738855B (zh) 一种应用在quic的基于多链路的传输方法和装置
JP2010028422A (ja) ゲートウェイ装置
WO2021134446A1 (fr) Procédé de traitement d'informations, dispositif et système de communication
WO2016180113A1 (fr) Procédé d'initiation de service vocal wi-fi, dispositif de communication lte, terminal, et système de communication
JP2014155072A (ja) 通信装置及びその制御方法、プログラム
JP2017503407A (ja) パケット処理方法および装置
JP6128116B2 (ja) 通信端末、通信方法、通信システムおよびプログラム
Purohith et al. Network architecture supporting seamless flow mobility between LTE and WiFi networks
US20240214301A1 (en) Packet processing method and related apparatus
US11870683B2 (en) 3GPP network function set adaptation for pre-5G network elements
WO2024131812A1 (fr) Procédé et appareil de mise en œuvre de service informatique, dispositif de communication, et support de stockage
CN114745456A (zh) 报文处理方法、装置及网络地址转换设备
JP2024503412A (ja) コアネットワークにおいてサービングネットワークノードを動的に発見するための方法、ネットワークノード、及びコンピュータ読取可能媒体
WO2024131714A1 (fr) Procédé de traitement d'informations et dispositif de communication
WO2024131712A1 (fr) Procédé de traitement d'informations et dispositif de communication
WO2024131754A1 (fr) Procédé et appareil de mise en œuvre de service informatique, et dispositif de communication et support de stockage lisible
CN115915196A (zh) 一种链路状态检测方法、通信装置及通信***
WO2012088828A1 (fr) Procédé, système et routeur de passerelle d'accès pour maintenance de table