WO2024131712A1

WO2024131712A1 - Information processing method and communication device

Info

Publication number: WO2024131712A1
Application number: PCT/CN2023/139447
Authority: WO
Inventors: 袁雁南
Original assignee: 维沃移动通信有限公司
Priority date: 2022-12-22
Filing date: 2023-12-18
Publication date: 2024-06-27
Also published as: CN118250283A

Abstract

The present application belongs to the technical field of communications. Disclosed are an information processing method and a communication device. The information processing method in the embodiments of the present application comprises: a first node acquires first information, the first node being a mobile communication network function node, the first information comprising service information of a service provided by a non-mobile communication network function node and calculation load information, and the first information being used for determining a service node.

Description

Information processing method and communication device

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to Chinese Patent Application No. 202211658851.6 filed on December 22, 2022, the entire contents of which are incorporated herein by reference.

Technical Field

The present application belongs to the field of communication technology, and specifically relates to an information processing method and communication equipment.

Background technique

In the related technologies, mobile communication networks mainly provide mobile communication transmission services for terminal users and application functions (or application servers) to meet the requirements of communication service quality (QoS), but do not involve relevant solutions for how mobile communication network function nodes determine appropriate service nodes. Furthermore, when the services required by mobile terminal devices involve both mobile network transmission and wired network transmission, the network topology and transmission status information in the mobile network are important parts of the end-to-end service, and the related solutions have not yet considered the impact of mobile network transmission performance. When the mobile network transmission performance has a greater impact on the service quality, a solution is needed for how the mobile network function node determines the appropriate service node by combining multi-dimensional information such as service and mobile network transmission.

Summary of the invention

The embodiments of the present application provide an information processing method and a communication device, which can solve the problem of how a mobile communication network function node determines a suitable service node.

In a first aspect, an information processing method is provided, comprising:

The first node obtains first information, where the first node is a mobile communication network function node, the first information includes service information and computing load information of services provided by non-mobile communication network function nodes, and the first information is used to determine a service node.

In a second aspect, an information processing method is provided, comprising:

The second node acquires target information sent by the first node, wherein the first node and the second node are both mobile communication network function nodes;

The target information includes one of the following:

An identifier of a service node determined by the first node according to the first information;

target service identifier and first information;

A target service identifier and target computing load information, wherein the target computing load information is computing load information of a target service, and the target service is a service corresponding to the target service identifier;

A service list and service node information corresponding to each service in the service list;

The first information includes service information and computing load information of the service provided by the non-mobile communication network function node, and the target service identifier is the service identifier in the service request received by the first node.

In a third aspect, an information processing device is provided, applied to a first node, including:

The first acquisition module is used to acquire first information, where the first node is a mobile communication network function node, the first information includes service information and computing load information of services provided by non-mobile communication network function nodes, and the first information is used to determine the service node.

In a fourth aspect, an information processing device is provided, which is applied to a second node and includes:

A second acquisition module, configured to acquire target information sent by a first node, wherein the first node and the second node are both mobile communication network function nodes;

The target information includes one of the following:

target service identifier and first information;

In a fifth aspect, a terminal is provided, comprising 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.

In a sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is used to obtain first information, the first node is a mobile communication network function node, the first information includes service information and computing load information of services provided by non-mobile communication network function nodes, and the first information is used to determine the service node. Alternatively, the communication interface is used to obtain target information sent by the first node, the first node and the second node are both mobile communication network function nodes; wherein the target information includes one of the following: an identifier of a service node determined by the first node according to the first information;

target service identifier and first information;

In a seventh aspect, a network side device is provided, the network side device comprising a processor and a memory, the memory storing a program or instruction that can be run on the processor, the program or instruction being executed by the processor to implement the The steps of the method described in the first aspect or the second aspect.

In an eighth aspect, a network side device is provided, comprising a processor and a communication interface, wherein the communication interface is used to obtain first information, the first node is a mobile communication network function node, the first information includes service information and computing load information of services provided by non-mobile communication network function nodes, and the first information is used to determine the service node. Alternatively, the communication interface is used to obtain target information sent by the first node, the first node and the second node are both mobile communication network function nodes; wherein the target information includes one of the following: an identifier of a service node determined by the first node according to the first information;

target service identifier and first information;

In a ninth aspect, an information processing system is provided, comprising: a first node and a second node, wherein the first node can be used to execute the steps of the method described in the first aspect, and the second node can be used to execute the steps of the method described in the second aspect.

In the tenth aspect, a readable storage medium is provided, on which a program or instruction is stored. When 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.

In the eleventh aspect, a chip is provided, 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.

In the twelfth 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.

In an embodiment of the present application, the mobile communication network function node obtains the service information and computing load information of the services provided by the non-mobile communication network function node, so that the mobile communication network function node can determine the service node that provides services to the nodes within the mobile network in combination with the service information and computing load information of the services provided by the non-mobile communication network function node.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a structural diagram of a communication system applicable to an embodiment of the present application;

FIG2 shows a control plane process for obtaining service information and computing power information attached to a CFN node;

FIG3 shows the data plane process of obtaining service information and computing power information attached to a CFN node;

FIG4 is a schematic diagram showing one of the flow charts of the information processing method according to an embodiment of the present application;

FIG5 is a schematic diagram showing acquisition of service information and computing load information in an embodiment of the present application;

FIG6 shows one of the interactive flow charts of the information processing method according to an embodiment of the present application;

FIG7 shows a second interactive flow chart of the information processing method according to an embodiment of the present application;

FIG8 shows a third interactive flow chart of the information processing method according to an embodiment of the present application;

FIG9 is a second flow chart of the information processing method according to an embodiment of the present application;

FIG10 is a schematic diagram showing one of the modules of the information processing device according to an embodiment of the present application;

FIG11 is a second schematic diagram of a module of an information processing device according to an embodiment of the present application;

FIG12 is a block diagram showing a structure of a communication device according to an embodiment of the present application;

FIG13 is a block diagram showing a structure of a terminal according to an embodiment of the present application;

FIG14 shows one of the structural block diagrams of the network side device according to an embodiment of the present application;

FIG. 15 shows a second structural block diagram of the network side device according to an embodiment of the present application.

Detailed ways

The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

The terms "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. For example, the first object can be one or more. In addition, "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.

It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE)/LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the above-mentioned systems and radio technologies as well as for other systems and radio technologies. The following description describes a new radio (NR) system for example purposes, and NR terms are used in most of the following descriptions, but these technologies can also be applied to applications other than NR system applications, such as the ^6th Generation (6G) communication system.

FIG1 is a block diagram of a wireless communication system applicable to the 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 (Personal Digital Assistant, The terminal side devices include PDA, PDA, PDA, netbook, ultra-mobile personal computer (UMPC), mobile Internet device (MID), augmented reality (AR)/virtual reality (VR) equipment, robot, wearable device (Wearable Device), vehicle user equipment (VUE), pedestrian terminal (Pedestrian User Equipment, PUE), smart home (home equipment with wireless communication function, such as refrigerator, TV, washing machine or furniture, etc.), game console, personal computer (Personal Computer, PC), teller machine or self-service machine, etc., wearable devices include: smart watch, smart bracelet, smart headset, smart glasses, smart jewelry (smart bracelet, smart bracelet, smart ring, smart necklace, smart anklet, smart anklet, etc.), smart wristband, smart clothing, etc. It should be noted that the specific type of terminal 11 is not limited in the embodiment of the present application. 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 radio access network device, a radio access network (RAN), a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point or a WiFi node, etc. The base station may be referred to as a node B, an evolved node B (eNB), an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home B node, a home evolved B node, a 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 (Binding Support Function, BSF), application function (Application Function, AF), etc. It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

In order to enable those skilled in the art to better understand the embodiments of the present application, the following description is first made.

1. In the 6G era, the network is no longer a simple communication network, but an information system that integrates communication, computing, and storage. It realizes endogenous computing internally and provides computing services externally, reshaping the communication network structure. In order to meet the needs of new network services and lightweight and dynamic computing in the future, the integration of network and computing has become a new development trend. Under the general trend of deep integration of network and computing, the core demand of network evolution requires mutual perception and high collaboration between network and computing. The computing network will realize ubiquitous computing interconnection, realize efficient collaboration between cloud, network, and edge, and improve network resources and computing. Resource efficiency, thereby achieving:

(1) Real-time and accurate computing power discovery: Based on the real-time perception of network status and computing power location at the network layer, whether it is traditional centralized cloud computing power or other computing power distributed in the network, the computing power network can combine real-time information to achieve fast computing power discovery and routing;

(2) Flexible and dynamic service scheduling: Based on the user's service level agreement (SLA) requirements, the network takes into account the real-time network resource status and computing resource status, and quickly matches the service traffic to the optimal node through flexible and dynamic network scheduling, allowing the network to support the provision of dynamic services to ensure the user experience of the service;

(3) Consistent user experience: Since the computing network can perceive ubiquitous computing and services, users do not need to worry about the location and deployment status of computing resources in the network. The coordinated scheduling of network and computing ensures that users have a consistent experience.

2. Internet Engineering Task Force (IETF) Compute First Networking (CFN);

Aiming at the integration of bearer network and computing power services, 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 multi-access edge computing (MEC) connected to different transmission devices (such as routers). This solution solves how to obtain service information and computing power information attached to a CFN node in the transmission bearer network, and selects and routes service nodes based on service information, computing power information and transmission overhead.

As shown in Figure 2, the control plane process is used to obtain the service information and computing power information attached to a certain CFN node. The CFN node in the figure can be a router. Taking the CFN node 3 in Figure 2 as an example, the MEC platform management node connected to the CFN node 3 sends service information registration/update/revocation to the CF node 3. The information includes at least a service identifier (service ID, SID) and a binding identifier/IP (Binding ID/IP, BID/BIP). Among them, SID is a unique ID that identifies a service, which can be an anycast address (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, which can be a unicast address. That is to say, 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. In addition, the MEC platform management node sends the computing load update of the service to the CFN node 3, including SID and computing load information. Computation load information includes CPU used, number of sessions being served, query per second, computation delay, etc. According to the configured range, CFN node 3 can update the above service information and computing 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), wherein the service includes SID, CFN node identifier (CFN node 3) that can be routed to the SID, and computing load information. For CFN node 1 and node 2, the same process is used to send the service information and computing load information attached to CFN node 1 and node 2 to other nodes within the configured range. After multiple CFN nodes share information with each other, each CFN node obtains all service information and computing load conditions within the configured range. In order to avoid frequent updates of service and computing load information, especially computing load information, between CFN nodes, a computing load measurement threshold or update timer can be set, and the information is updated only when the threshold is exceeded or the timer expires. The other method is the most suitable exit node selection method, that is, to select an exit node with a relatively low computing load. mouth to avoid fluctuations.

As shown in Figure 3, the data plane process, when a client (such as an application (APP) on a user equipment (UE)) initiates the first request for a flow, the request destination address is the SID (which can be the anycast Internet Protocol (IP) address of the service obtained through DNS), and the source address is the client IP. The request destination address is identified as the SID, and the egress CFN node (CFN egress) is selected based on the service information and computing load information obtained. The ingress CFN node (ingress) is the first CFN node to receive the data request, and the egress CFN node is the CFN node that routes to the selected target service 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 ingress CFN node (the IP address of CFN node 1), and the destination address is the egress CFN node (the IP address of 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, and forwards (routes) it to the service instance of BIP32. The service response is the reverse process of the above, which will not be described here.

3. IETF Computing-Aware Networking (CAN);

CAN, which is currently in the Bus-Off (BOF) state, is consistent with the basic CFN approach. A dynamic router (D-Router) is a node that supports dynamic anycast (Dyncast) functionality. That is, it can understand network-related metrics and service instance-related metrics, make forwarding decisions based on instance affinity and maintain instance affinity, that is, forward packets belonging to the same business requirement to the same instance. This affinity can be called flow affinity or instance affinity, which means that packets from the same service "flow" should always be sent to the same exit and processed by the same service instance. Typically, a flow is identified by a 5-tuple value (source IP, destination IP, source port number, destination port number, and protocol). A dynamic metric agent (D-MA) is a dyncast-specific agent that can collect and send metric updates from the network and instances, but does not perform forwarding decisions. D-MA can run on a D-Router or be implemented as a separate module (e.g., a software library) parallel to a service instance. Compared with the service information and computing load information shared by the aforementioned CFN nodes, the service information and computing load information shared by D-MA include dynamic service ID (D-SID), dynamic binding ID (D-BID) and metrics, where D-SID, D-BID and metrics are similar to the SID, BID/BIP and metrics of the aforementioned CFN. It can be seen that what D-MA shares directly is the service instance ID (i.e. D-BID) rather than the router ID (CFN node ID or D-router ID).

For the distributed mode, 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. In addition, the 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. For the centralized mode, the resources and status of different service instances are reported to the network controller from the D-Router connected to the edge site where the service is deployed. At the same time, 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 information processing method provided by the embodiment of the present application is described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.

As shown in FIG4 , the embodiment of the present application provides an information processing method, including:

Step 401: A first node obtains first information, where the first node is a mobile communication network function node. The first information includes service information and computing load information of services provided by non-mobile communication network function nodes. The first information is used to determine a service node.

Optionally, the first node in the embodiment of the present application includes: an IP Multimedia Subsystem (IMS), a trusted data network (DN) node, a core network function node and a wireless access network node.

The non-mobile communication network function node is a node other than the first node mentioned above, and may be a CAN node, a CFN node, a D-MA, a D-Router or a network controller, etc.

Optionally, the service node is a non-mobile communication network function node. The services provided by the non-mobile communication network function node include services provided by service providers deployed in the central cloud, services provided by service providers deployed in the edge cloud, and services deployed in self-owned servers or private clouds, etc. And in the embodiments of the present application, it is assumed that the CFN node or D-MA or D-Router or network controller has obtained service information and computational load information outside the mobile communication network. The first node can obtain the above-mentioned service information and computational load information from the non-mobile communication network function node (i.e., CFN node, D-MA, D-Router or network controller). The computational load information is information used to calculate the transmission load.

Optionally, in an embodiment of the present application, the service information includes at least one of the following: at least one of a service identifier and a service instance identifier, wherein the service identifier is used to identify a service, and the client uses the service identifier to access the service; the service instance identifier is used to identify a service instance that provides the service, and the service instance corresponds to a service node;

Optionally, the computing load information includes at least one of the following:

Load value;

The metric parameter corresponding to the load value;

The transmission overhead of the service provided by the non-mobile communication network function node in the non-mobile communication network. That is, the transmission overhead of the bearer network outside the mobile network, for example, the network transmission overhead from the UPF to the service instance. Because there may be multiple routes to a certain service instance, the next hop address and the corresponding network overhead (such as transmission delay, or network overhead level) are included. For example, the next hop is CFN node 1 (CFN node1) (or D-router1), and the corresponding bearer network transmission delay is 30ms; or the next hop is CFN node1 (or D-router1), and the corresponding bearer network transmission overhead level is 2 (which may mean that the delay is between 30 and 50ms. The definition of the overhead level may be different depending on the situation. This is just an example).

In the embodiment of the present application, the above-mentioned service identifier can be an anycast IP address or a predefined service identifier (for example, a specific IPv4 address negotiated by the service node, router and first node; for example, a MAC address, etc.).

The service instance identifier may be a unicast IP address (such as UE intranet IP address, UE extranet IP address, IMS server IP address), a MAC address, an IP address and a port number, etc.

The above-mentioned metric parameters may include at least one parameter or multiple parameters, such as CPU occupancy, CPU idle rate, service session occupancy, service session idle rate, number of used CPUs, number of available CPUs, number of used CPU cores, number of available CPU cores, number of used sessions, number of available sessions, computing latency, Turing, hash rate, The computing resources used or available in units of Tera Operations Per Second (TOPS), Giga Operations Per Second (GOPS), Million Operations Per Second (MOPS), Floating-point Operations Per Second (FLOPS), etc.

The above-mentioned metric parameter may also be a parameter, and the load value corresponding to the parameter may be a value calculated by weighting the load values corresponding to multiple parameters. For example, it may be a single digital value calculated from weighted attributes (such as CPU/GPU consumption and/or the number of related sessions). For example, for an image recognition service, the service provider may define a digital value of the service load by comprehensively considering bandwidth resources, number of requests, and computing resources.

It should be noted that, depending on different designs, a service may be deployed on one or more servers. Usually, a server has multiple CPUs, and a CPU has multiple CPU cores.

Turing: The Turing Fog Foundation is the first in the world to define an objective unit of computing power for production nodes: Turing Unit (TU), and defines 24 hours of computing of GPU 1080Ti as 1TU, which is used as a measurement benchmark. The market price of 1TU is RMB 25, so the computing power value of 1TU is RMB 25.

Hash rate: Computing power (also known as hash rate) is a measure of the processing power of the Bitcoin network. It is the speed at which the CPU calculates the output of the 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: Units of processor computing power. 1TOPS means that the processor can perform one trillion (10^12) operations per second. Generally used as a measure of CPU computing power. 1GOPS means that the processor can perform one billion (10^9) operations per second, and 1MOPS means that the processor can perform one million (10^6) operations per second.

Optionally, the first information is a plurality of service information and computing load information, for example: service 1 (video conferencing), service instance 1, computing load 10%; service 1 (video conferencing), service instance 2, computing load 50%; service 2 (Convolutional Neural Networks (CNN) training), service instance M, computing load 5%; service 2 (CNN training), service instance N, computing load 60%.

After acquiring the first information, the first node continues to track and update the first information.

Optionally, the method of the embodiment of the present application further includes:

The first node receives a service request sent by a service request sending node, where the service request at least includes a target service identifier, and the target service identifier is used to identify a target service requested by the service request;

The first node determines a service node according to the target service identifier and the first information, where the service node is a node that provides the target service.

In the embodiment of the present application, the service request sending node may be specifically a mobile communication network function node or a non-mobile network function node. The service request sending node directly sends a service request to the first node. The first node, based on the service request, Determine the service node.

The first node receives service node request information sent by the second node, the service node request information at least includes a target service identifier, the target service identifier is used to identify a target service requested by the service request, the second node is a mobile communication network function node, and the service node request information is sent by the second node after receiving the service request sent by the service request node;

The first node determines a service node according to the target service identifier and the first information, where the service node is a node that provides the target service;

The first node sends the identifier of the service node to the second node.

The service node request information in the embodiment of the present application is used to request to determine the service node that provides the target service.

In an embodiment of the present application, the service request sending node may specifically be a mobile communication network function node. The service request sending node sends a service request to the second node. The second node sends service node request information to the first node based on the service request. The first node determines the service node based on the service node request information and the first information, and then sends the identifier of the service node to the second node.

Optionally, the first node determines a service node according to the target service identifier and the first information, including:

The first node determines the service node according to the target service identifier, the first information and the second information;

The second information includes at least one of the following:

A network topology structure between a third node and the target node, wherein the target node is a node that receives service data sent by the service request sending node; for example, the target node is the first node or the second node;

The network transmission state corresponding to the network topology structure;

The third node includes a terminal device in a mobile communication network that sends the service request and/or receives a service response corresponding to the service request; or, the third node includes a terminal device in a mobile communication network that potentially performs a first type of service, and the first type of service includes communication and computing fusion services.

In the embodiment of the present application, a terminal device that potentially provides a first type of service refers to a terminal device that may provide a first type of service.

Optionally, the terminal device that potentially performs the first type of service is determined according to at least one of the following:

capability information of the terminal device, the capability information being used to indicate whether the terminal device supports the first type of service;

The network slice type corresponding to the terminal device, for example, the network slice type is a communication and computing fusion service slice;

The protocol data unit PDU session type supported by the terminal device, for example, the PDU session type is a computing session, which is used to carry data packets of communication and computing fusion services.

As an optional implementation, the first node receives a service request sent by the service request sending node, and determines whether the service request sending node or the service response receiving node is a mobile network user equipment (i.e., the above-mentioned terminal device) according to the service request. If the service request sending node and/or the service response receiving node are mobile network user equipment, the first node obtains the network topology structure and network transmission information between the service request sending node and/or the service response receiving node and the first node. The first node determines the service node (i.e., the service instance identifier) according to the service information (such as the service identifier) in the service request, the first information, the network topology, and the network transmission status. Optionally, the first node may also determine the router node of the next hop. If the destination or source address conversion is required, the first node may also perform address conversion and forward the data service request. Accordingly, the first node receives the service response and sends it to the user equipment.

As an optional implementation method, the first node obtains the network topology and network transmission status between the user equipment that potentially performs communication and computing fusion services and the first node according to whether the supported user equipment or the mobile network bearer (such as PDU session) of the user equipment can perform communication and computing fusion services. For example, the first node can determine which user equipment is potentially performing communication and computing services according to the user equipment capability information indicating whether communication and computing fusion services are supported, or according to the network slice type where the user equipment is located, or according to the PDU session type of the user equipment (for example, some session types are used for communication and computing fusion, and some session types are used for communication). Based on the determined user equipment, the network topology and network transmission status between the user equipment and the first node are obtained. The first node comprehensively determines the service node (i.e., the service instance identifier) according to the service information (such as service identification) in the service request, the first information, the network topology and the network transmission status. Optionally, the first node can also determine the router node of the next hop. If destination or source address conversion is required, the first node can also perform address conversion and forward data service requests. Accordingly, the first node receives the service response and sends it to the user equipment.

In the above two implementations, the first node receives the service request and comprehensively determines the service node according to the service request, the first information, the network topology and the network transmission status.

The first node receives a service request sent by a service request sending node, where the service request includes a target service identifier, and the target service identifier is used to identify a target service requested by the service request;

The first node sends third information to the second node according to the service request, where the third information is used by the second node to determine a service node, and the second node is a mobile communication network function node;

The first node obtains the service node identifier sent by the second node;

The third information includes one of the following:

the target service identifier and the first information;

The target service identifier and target computing load information, wherein the target computing load information is computing load information of the target service, and the target service is the service corresponding to the service request.

Optionally, the third information may specifically be service node request information. Here, after the first node receives the service request sent by the service request sending node, it sends the third information to the second node, so that the second node determines the service node according to the third information.

Optionally, in the embodiment of the present application, in addition to the target service identifier, the service request also includes at least one of the following:

The identifier of the node sending the service request;

The identification of the node receiving the service response;

Load values and measurement parameters corresponding to the load values;

Calculate delay information;

response time information;

Memory information;

Store information;

Network bandwidth information;

Length of service duration.

A service list and service node information corresponding to each service in the service list are sent to a second node, where the second node is a mobile communication network function node.

When a communication bearer establishment request or a communication bearer modification request is received from a terminal device, the service node corresponding to each service in the service list is determined based on the service list, the service node identifier, the computing load information corresponding to each service node identifier, the network topology between the terminal device and the first node, and at least one of the network transmission states corresponding to the network topology, wherein the services in the service list are services potentially requested by the terminal device.

The services in the embodiments of the present application may be video conferencing, artificial intelligence (AI) training, image recognition, video rendering, etc.

When at least one of the services in the service list, the computing load information corresponding to the service node identifier, the network topology structure, and the network transmission status corresponding to the network topology structure is updated, the service node corresponding to each service in the service list is re-determined.

In one implementation of the present application, a first node receives a service request sent by a service request sending node, and then the first node determines information related to the service request. Specifically, one method is to obtain network overhead and computing load information corresponding to a service node providing a service corresponding to a service identifier, such as a network overhead corresponding to a CFN egress node, a BID/BIP or a D-BID, according to the service request and the first information. The node identifier of the first node sending the service request, the node identifier receiving the service response, and information related to this service request (such as the identifier of the service node that potentially provides the requested service, network overhead, computing load information, etc.) are sent to the second node. Another method is that the first node sends all service information and computing load information obtained outside the network to the second node, and sends this service request to the second node. The second node comprehensively determines the service node (i.e., the service instance identifier) based on the received information, as well as the topology and status information within the mobile network of the user equipment. Optionally, the second node can also determine the router node of the next hop. And send the determined service node and/or next hop routing information to the first node. If destination or source address conversion is required, the first node can also perform address conversion and forward data service requests. Correspondingly, the first node receives the service response and sends it to the user equipment.

In one implementation of the present application, the first node collects all relevant information (service information and computing load information outside the mobile communication network, as well as the network topology and network transmission status inside the mobile communication network). Responsible for timely access to all relevant information, and/or continuous updating.

One scenario of this implementation is: after receiving the service request, the second node determines whether the service needs to determine the service node and route according to the latest status of communication and calculation based on the service information. If necessary, the second node sends the service request to the first node. The first node determines the service node according to the service request, and optionally, the first node determines the next hop route. The first node sends the determined information to the second node, and the second node forwards it according to the message of the first node. If destination or source address conversion is required, the second node can also perform address conversion and forward data service requests. Accordingly, the second node receives the service response and sends it to the user equipment.

Another situation is: when the first node receives a request to establish or modify a communication bearer of a UE (e.g., a PDU session establishment/modification request), the first node comprehensively determines the preferred service node (i.e., service instance identifier) of each potential requested service based on the service information (e.g., SID, IP address) list of potential service requests of the UE, the service node identifier of the potential service provider and its corresponding computing load information, the topology and network status information within the mobile network of the user equipment, etc., and sends the potential service list and its preferred service node information to the second node, that is, sends the service list and the service node information corresponding to each service in the service list to the second node. When the first node obtains at least one update of the service information, computing load information, topology and status information within the mobile network of the user equipment, the preferred service node for each potential service is reselected and determined. If the new result is different from the aforementioned one sent to the second node, the first node reconfigures the potential service list and its preferred service node information to the second node. The specific method may be to send the entire potential service list and its preferred service node information, or to send information on changes in the preferred service node corresponding to the potential service.

Taking UE1 as an example, a definition method of UE1's potential service list and its preferred service node information is as follows:

UE1, service 1 (e.g., SID is 10.2.5.7), better service node (e.g., BID is 104.2.5.6);

UE1, service 2 (such as SID is 10.2.5.3), better service node (such as BID is 104.2.5.2).

Optionally, in an embodiment of the present application, the network topology structure includes at least one of the following: a serving RAN node of the terminal device; a target node for transmitting a first PDU session; wherein the first PDU session is a PDU session corresponding to the service request;

And/or, the network transmission status includes at least one of the following:

Uplink transmission delay between terminal equipment and base station;

Downlink transmission delay between terminal equipment and base station;

The round-trip transmission delay between the terminal device and the base station;

Uplink transmission delay between the base station and the target node;

Downlink transmission delay between the base station and the target node;

The round-trip transmission delay between the base station and the target node;

Uplink bandwidth between terminal devices and base stations;

Downlink bandwidth between terminal devices and base stations;

Uplink bandwidth between the terminal device and the target node

Downlink bandwidth between the terminal device and the target node;

The target node is a node that receives service data sent by the service request sending node.

It should be noted that based on the 5th Generation Mobile Communication Technology (5G) network, computing services are carried on the user plane, so the transmission path of user equipment related computing services in the network is the base station and UPF. If considering the expansion towards 6G, the base station still generalizes to represent the wireless access network node, and the UPF can be expanded to the core network to carry computing services (such as the computing plane function discussed in 6G, or the data plane function, etc.).

It should be noted that the delay mentioned in the above description may be real-time delay measurement information, historical delay information, or delay information for a certain period of time in the future predicted based on historical data. The above items may be maximum delay, minimum delay, or average delay, etc.

Obtaining the router node information of the next hop to which the first node forwards the service request;

The service request is forwarded according to the router node information of the next hop.

Specifically, the router node information may be determined by the first node itself, or may be sent by the second node to the first node.

Convert at least one of the destination address and the source address corresponding to the service request.

Optionally, performing conversion processing on at least one of a destination address and a source address corresponding to the service request includes:

Setting the external source address of the service request to the IP address corresponding to the first node, and setting the external destination address of the service request to the IP address of an egress computing priority network CFN node that can be routed to the target service node;

Alternatively, the destination address in the service request is set to the identifier of the service instance that provides the target service information;

Alternatively, when the internal source address of the service request is the intranet IP address of the terminal device, the source address of the service request is converted into the extranet IP address and port number of the terminal device.

It should be noted that the method of the embodiment of the present application can be used in different service flow interaction situations, and the service flow related to the terminal includes the following situations:

1. Terminal A requests, and the service result is returned to the terminal computing power unloading of terminal A;

2. Terminal A requests and the service result is provided to terminal B, which is a fusion of inter-terminal communication and computing;

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;

4. Application function/application server requests and service results are provided to terminal A, which integrates communication and computing between the terminal and the application function/server.

The solution of the present application is described in detail below with reference to embodiments.

In the first embodiment of the present application, according to the definition of IETF CFN or CAN, the CFN node, D-MA, D-Router and controller jointly provided with D-MA can understand the service information and computing load information outside the mobile network in the range. This embodiment can be based on the 5G network function, assuming that the first node is UPF (it can also be other network functions, such as 6G user plane function, or newly added computing service function, etc.). As shown in FIG5, a method for obtaining service information outside the mobile communication network The method of obtaining service information and calculating load information is based on a routing protocol (such as BGP, etc.) to obtain the service information and calculated load information known to the device from a CFN node, D-MA, or a D-Router co-established with a D-MA. UPF can also be obtained through other methods, and here only the method of obtaining through a CFN node or D-MA is used as an example. The first node can obtain and continuously track service information and calculated load information outside the network through the process shown in Figure 5. Specifically including:

Step 1: The service node sends service information and calculation load information to the transmission device.

Step 2a: Transmission device 1 sends calculation load update information to transmission device 2.

Step 2b: The transmission device 1 sends calculation load update information to the first node.

The computing load update information includes the updated computing load, or the change information between the updated computing load and the computing load before the update.

The process of a communication and computing fusion service is shown in Figure 6, including:

Step 1: The first node receives a service request sent by a UE, and determines, based on the service request information, that the node sending the service request or the node receiving the service response is a mobile network user equipment, such as a UE sending a service request. Determine, based on the service request, whether the service request requires the assistance of a mobile network function node in determining a service node, for example, based on the service identification information in the service request (such as identifying the requested service by the destination IP address of the data packet), whether the first node needs to assist in determining the service node. If necessary, proceed to step 2.

Step 2: The first node obtains the network topology and network transmission status between the UE and the first node. The network topology and network transmission status include at least one of the following:

A serving RAN node of the user equipment;

a UPF node for transmitting the service request PDU session of the user equipment;

Uplink delay from user equipment to base station;

Downlink delay from user equipment to base station;

The round-trip delay from user equipment to base station;

Uplink delay between base station sending and receiving UPF;

Downlink delay between UPF sending and receiving base stations;

The round-trip delay between the base station and the UPF.

Step 3: The first node comprehensively determines the service node (i.e., service instance identifier) based on the service information (such as service ID, IP address) of the service request, the latest service information and computing load information of the service obtained by the first node, the topology and status information of the mobile network of the user equipment, etc., and saves the mapping relationship between the service flow and the service node. For example, the service request sending node information (such as IP address and port number), the service response receiving node information (such as IP address and port number) and the service node information (such as IP address and port number) can be used as a mapping relationship to ensure that subsequent data transmission of the service uses the same route and service node.

Step 4: If destination or source address conversion is required, for example, in a CFN network, the first node sets the external source address (outer: src IP) to the first node IP address and sets the external destination address (outer: dst IP) to the CFN egress node IP address that can be routed to the determined service instance. For example, in a CAN network, the first node sets the destination address (outer: dst IP) to the D-BID of the determined service instance (i.e., the unicast IP address that corresponds to the service implementation one-to-one). address); if the inner source IP address (inner: src IP) is the UE intranet IP address, the first node also needs to convert the source IP address to the UE extranet IP address and port number. The first node sends the service request to the routing device to which it is connected, and the first node can optionally select the next hop routing address.

Step 5: The transmission device (such as a router, CFN node, etc.) routes the request to the service node.

Step 6: After the service node completes the processing, it sends a service response.

Step 7: The transmission device 1 forwards the service response to the first node.

Step 8: The first node sends a service response to the terminal device.

If the first node performs address conversion, it needs to perform corresponding inverse mapping after receiving the service response and send it to the user equipment.

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. It can also be called flow affinity.

In the second embodiment of the present application, according to the definition of IETF CFN or CAN, the CFN node, D-MA, D-Router and controller jointly provided with D-MA can understand the service information and computing load information outside the mobile network in the range. This embodiment can be based on the 5G network function, assuming that the first node is UPF (it can also be other network functions, such as 6G user plane functions, or newly added computing service functions, etc.), and the method for the first node to obtain service information and computing load information outside the mobile communication network is the same as the above-mentioned first embodiment, which will not be repeated here. The second node is SMF. At the same time, the first node also obtains and maintains the mobile network topology and network transmission status between the potential terminal device and the first node.

The process of a certain communication and computing fusion service (i.e., the UE needs the network to assist in selecting a more appropriate service node) is shown in FIG7 and includes:

Step 1: The first node receives a service request sent by the UE, and determines whether the service request requires the assistance of a mobile network function node in determining a service node based on the service request, for example, based on the service identification information in the service request (such as identifying the requested service by the destination IP address of the data packet), whether the first node needs to assist in determining the service node. If necessary, then the node that sends the service request or the node that receives the service response is determined to be a mobile network user equipment (terminal device), such as UE A and UE B, based on the service information requested by the service request (such as SID). Further, the first node determines the potential service node that provides the service, computing load, and other information maintained by the first node based on the service information (such as SID) requested by the service request.

Step 2: The first node sends a service node request message to the second node, wherein the service node request includes the node identifier that sends the service request, the node identifier that receives the service response, and information related to this service request (such as the identifier of the aforementioned potential service node, network overhead, computing load information, etc.).

Step 3: The second node obtains the network topology and network transmission status between UE A and the first node, and the network topology and network transmission status between UE B and the first node according to the service node request information. The network topology and network transmission status are the same as those in the first embodiment and will not be repeated here. The second node determines the service node (i.e., service instance identifier) based on the service information (such as SID identified by IP address), the identifier of the service node that potentially provides the service, the corresponding computing load information, the network topology and network transmission status information within the mobile network of the user equipment, etc. Sending service node indication information to the first node, wherein the service indication at least includes a service node identifier (such as BID, D-BID, etc.).

Step 4: The first node forwards the service request according to the indication information and saves the mapping relationship between the service flow and the service node. For example, the mapping relationship between the service request sending node information (such as IP address and port number), the service response receiving node information (such as IP address and port number) and the service node information (such as IP address and port number) can be used to ensure that the subsequent data transmission of the service uses the same route and service node. If the destination or source address conversion is required, for example, in the CFN network, the first node sets the external source address (outer: src IP) to the first node IP address and sets the external destination address (outer: dst IP) to the CFN egress node IP address that can be routed to the determined service instance. For example, in the CAN network, the first node sets the destination address (outer: dst IP) to the D-BID of the determined service instance (i.e., the unicast IP address that corresponds to the service implementation one by one); if the internal source IP address (inner: src IP) is the UE intranet IP address, the first node also needs to convert the source IP address to the UE extranet IP address and port number. The first node sends the service request to a routing device connected thereto, and the first node may optionally select a next-hop routing address.

Step 8: The first node sends a service response to the terminal device.

If the first node performs address conversion, then after receiving the service response, it needs to perform corresponding reverse mapping and send it to the user equipment UE B. For example, remove the outer address information and convert the inner:dst IP to the intranet IP address of the service response receiving node UE B.

In the third embodiment of the present application, according to the definition of IETF CFN or CAN, the CFN node, D-MA, D-Router and controller jointly provided with D-MA can understand the service information and computing load information outside the mobile network in the range. This embodiment can be based on the 5G network function, assuming that the first node is UPF (it can also be other network functions, such as 6G user plane functions, or newly added computing service functions, etc.). The method for the first node to obtain service information and computing load information outside the mobile communication network is the same as the first embodiment described above, and will not be repeated here. The first node also collects and maintains the internal topology (network topology structure) and status (network transmission status) of the mobile network from the UE to the first node based on the received UE indication information. The process of the first node obtaining and maintaining the internal topology and status of the mobile network, as shown in Figure 8, includes:

Step 1: The UE indicates in the message sent to AMF (such as registration request message, service request message, etc.) or the PDU session establishment/modification request sent by the UE to SMF that the UE may potentially need network assistance to select a more appropriate service node (i.e., to perform communication and computing fusion services).

Step 2: If the UE sends via a session management message, then the SMF can obtain the UE information from the session management message. If the UE sends via a registration request or other message to the AMF, then the SMF can obtain the UE information from the AMF. The SMF selects a UPF based on the UE information received or the UE information obtained from the AMF, and sends the UE information to the selected UPF. For example, one way is to indicate the potential need for network access through an N4PDU establishment request or an N4PDU modification request. Assist in selecting a more suitable service node for UE. Optionally, there may be multiple UPFs in the network, and a UPF that can understand service information and calculate load information is responsible for collecting and maintaining relevant UE information. When the network does not need to assist in selecting a more suitable service node, the SMF selects a UPF that does not support this function.

Step 3: UPF subscribes to SMF for the UE's serving RAN node information and UE context such as the delay information between the UE and its serving RAN node measured by the RAN node based on the received UE information.

Step 4: UPF measures the latency and other information between it and the service node corresponding to the potential UE. Thus, UPF obtains the latency, bandwidth and other information from the UE to the UPF based on the information obtained from SMF and the information measured by itself. UPF can update the information periodically, or update the topology and status information in the mobile network based on events such as the UE service RAN node change information triggered by SMF subscription.

The process of a communication and computing fusion service includes:

Step 1: The first node receives a service request sent by a UE, and determines, based on the service request information, that the node sending the service request is a mobile network user equipment, that is, the UE sending the service request. Determine, based on the service request, whether the service request requires the assistance of a mobile network function node in determining a service node, for example, based on the service identification information in the service request (such as identifying the requested service by the destination IP address of the data packet), whether the first node needs to assist in determining the service node. If necessary, proceed to step 2.

Step 2: The first node comprehensively determines the service node (i.e., service instance identifier) based on the service information of the service request (such as the service ID represented by the IP address), the latest service information and computing load information of the service obtained by the first node, the topology and status information of the mobile network of the user equipment, etc., and saves the mapping relationship between the service flow and the service node, for example, the mapping relationship between the service request sending node information, the service response receiving node information and the service node information can be used to ensure that the subsequent data transmission of the service uses the same route and service node.

Step 3: If destination or source address conversion is required, for example, in a CFN network, the first node sets the external source address (outer: src IP) to the first node IP address, and sets the external destination address (outer: dst IP) to the CFN egress node IP address that can be routed to the determined service instance. For example, in a CAN network, the first node sets the destination address (outer: dst IP) to the D-BID of the determined service instance (i.e., a unicast IP address that corresponds one-to-one with the service implementation); if the internal source IP address (inner: src IP) is the UE intranet IP address, the first node also needs to convert the source IP address to the UE extranet IP address and port number. The first node sends the service request to the routing device to which it is connected, and the first node can optionally select the next hop routing address.

Step 4: The transmission device (such as a router, CFN node, etc.) routes the request to the service node

Step 5: After the service node completes the processing, it sends a service response. Accordingly, the first node receives the service response. If the first node performs address conversion, it needs to perform a corresponding reverse mapping after receiving the service response and send the application function. For example, remove the outer address information and convert the inner:dst IP to the service response receiving node application function IP address.

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. It can also be called affinity (flow affinity).

In the fourth embodiment of the present application, according to the definition of IETF CFN or CAN, the CFN node, D-MA, D-Router and controller co-located with D-MA can understand the service information and computing load outside the mobile network in the range. Information. This embodiment can be based on 5G network functions, assuming that the first node is SMF (it can also be other network functions, such as AMF, or newly added computing service functions, etc.). The method for the first node to obtain service information and computing load information outside the mobile communication network is similar to the first embodiment. Compared with the first embodiment in which UPF obtains information from the CFN node or router, SMF is more suitable for obtaining the service information and computing load information from the controller when it is the first node. A method for the first node to obtain the internal topology and status information of the UE network is: the first node determines the UE identifier set that potentially requires network assistance to select a more suitable service node based on information such as UE capabilities and/or PDU types. The first node collects the internal topology and status information of the UE network in a periodic and/or event-triggered manner, thereby maintaining the latest internal topology and status information of the network. Another method for the first node to obtain the internal topology and status information of the UE network is when the first node receives a PDU session request sent by the UE, it obtains the internal topology and status of the UE network, rather than maintaining the information all the time. Taking the latter method as an example, the steps are briefly described as follows.

Step 1: The UE sends a PDU session establishment/modification request to the SMF, which indicates that the UE may potentially need network assistance to select a more appropriate service node (i.e., to perform communication and computing fusion services). Optionally, it may also include information about the service requested by the UE, such as a SID or a SID list.

Step 2: SMF sends status information (such as latency) measurements to the wireless access network node (such as gNB) and UPF through the N2 and N4 interfaces based on the received UE information, thereby obtaining the topology and status information of the UE in the mobile network.

Step 3: Based on the information obtained, SMF selects the UPF that supports network-assisted selection of a better service node to complete the establishment or modification of the PDU session.

The process of a communication and computing fusion service includes:

Step 1: The second node (such as UPF) receives the service request sent by the UE and determines whether the service request requires network assistance to select a more appropriate service node based on the service request information. If necessary, proceed to step 2;

Step 2: The second node sends the UE identifier for sending the service request, service information (such as SID), and the node identifier for receiving the service response to the first node, requesting to determine a suitable service node.

Step 3: The first node (SMF) selects UPF and determines the service node (such as BID, etc.) according to the service information requested by the UE, the service information outside the network and the calculated load information, and the topology and status information of the UE in the mobile network obtained in step 2. The determined service node information is sent to the second node.

Step 4: The second node forwards according to the received service node information and saves the mapping relationship between the service flow and the service node. For example, the mapping relationship between the service request sending node information, the service response receiving node information and the service node information can be saved to ensure that subsequent data transmission of the service uses the same route and service node.

Step 5: If destination or source address conversion is required, for example, in a CFN network, the second node sets the external source address (outer: src IP) to the second node IP address, and sets the external destination address (outer: dst IP) to the CFN egress node IP address that can be routed to the determined service instance. For example, in a CAN network, the second node sets the destination address (outer: dst IP) to the D-BID of the determined service instance (i.e., a unicast IP address that corresponds one-to-one to the service implementation); if the internal source IP address (inner: src IP) is the UE intranet IP address, the second node also needs to convert the source IP address to the UE extranet IP address and port number. The second node sends the service request to the routing device to which it is connected, and the second node can optionally select the next hop routing address.

Step 6: The transmission device (such as a router, CFN node, etc.) routes the request to the service node;

Step 7: After the service node completes the processing, it sends a service response. Accordingly, the second node receives the service response. If the second node performs address conversion, it needs to perform a corresponding reverse mapping after receiving the service response and send the application function. For example, remove the outer address information and convert the inner:dst IP to the service response receiving node application function IP address.

The second 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. It can also be called flow affinity.

It should be noted that, in the embodiment of the present application, flow affinity is maintained by mapping the source address, source port number, destination address, destination port number and protocol type (such as TCP/UDP, etc.). The service request sending node information can be mapped to the source address and source port number in the background technology. The service node information can be mapped to the destination address, destination port number and protocol type in the background technology. Since the present application takes into account the different situations of the service request sending node and the service response receiving node, the service response receiving node information is added.

The above-mentioned transmission equipment can be a controller, a CFN node, a D-MA, etc.

In an embodiment of the present application, the first node or the second node selects a more suitable service node based on the service information and computing load information of the service provided by the non-mobile communication network function node, as well as the topology and network transmission status information within the mobile network. This solution selects a suitable service node based on the latest information obtained for each service request, which can effectively avoid the problem of inappropriate service nodes caused by outdated status information. At the same time, the selection of this solution is based on the computing load information of the service and the transmission information within the mobile network. For services related to user equipment (UE), it truly comprehensively considers communication and computing information to select service nodes. Compared with only considering mobile network transmission or only considering service computing load information, more relevant factors are considered, and the selected service node is better. In particular, when the mobile network transmission performance has a greater impact on the quality of service, the selected service node is better.

As shown in FIG9 , the embodiment of the present application further provides an information processing method, including:

Step 901: a second node obtains target information sent by a first node, wherein the first node and the second node are both mobile communication network function nodes;

The target information includes one of the following:

target service identifier and first information;

It should be noted that various contents in the above target information have been described in detail in the method embodiment on the first node side and will not be repeated here.

In the embodiment of the present application, the second node obtains the target information sent by the first node, and the target information includes one of the following: the identifier of the service node determined by the first node according to the first information; the target service identifier and the first information; The target service identifier and target computing load information, wherein the target computing load information is the computing load information of the target service, and the target service is the service corresponding to the service identifier; a service list and service node information corresponding to each service in the service list; wherein the first information includes service information and computing load information of services provided by non-mobile communication network function nodes, and the target service identifier is the service identifier in the service request received by the first node. Through the target information, the second node can determine the service node that provides services for the nodes in the mobile network in combination with the service information and computing load information of services provided by the non-mobile communication network function nodes.

Optionally, when the target information is an identifier of a service node, the method further includes:

The second node receives a service request sent by a service request sending node, where the service request at least includes a target service identifier;

The second node sends service node request information to the first node according to the service request, where the service node request information at least includes the target service identifier.

A service node is determined according to the target information, where the target information includes a target service identifier and first information, or includes a target service identifier and target computing load information.

The identifier of the service node is sent to the first node.

The second node determines a service node according to the target service identifier and the target information.

Optionally, in the method of the embodiment of the present application, the service node is further related to second information, and the second information includes at least one of the following:

The second information includes at least one of the following:

A network topology structure between a third node and the target node, the target node being a node that receives service data sent by the service request sending node;

The network transmission state corresponding to the network topology structure;

Optionally, in the method of the embodiment of the present application, the terminal device that potentially performs the first type of service is determined according to at least one of the following:

The network slice type corresponding to the terminal device;

Protocol data unit (PDU) session types supported by the terminal device.

Optionally, in the method of the embodiment of the present application, the network topology structure includes at least one of the following: a service base station of the terminal device; a target node for transmitting the first PDU session; wherein the first PDU session is a PDU session corresponding to the service request;

And/or, the network transmission status includes at least one of the following:

Uplink transmission delay between terminal equipment and base station;

Downlink transmission delay between terminal equipment and base station;

Uplink transmission delay between the base station and the target node;

Downlink transmission delay between the base station and the target node;

The round-trip transmission delay between the base station and the target node;

Uplink bandwidth between terminal devices and base stations;

Downlink bandwidth between terminal devices and base stations;

Uplink bandwidth between the terminal device and the target node

Downlink bandwidth between the terminal device and the target node;

Optionally, in the method of the embodiment of the present application, the service information includes at least one of the following: at least one of a service identifier and a service instance identifier, wherein the service identifier is used to identify a service, the service instance identifier is used to identify a service instance that provides the service, and the service instance corresponds to a service node;

And/or, the computing load information includes at least one of the following:

Load value;

The metric parameter corresponding to the load value;

The transmission overhead of the service provided by the non-mobile communication network function node in the non-mobile communication network.

The router node information of the next hop to which the second node forwards the service request is obtained.

The router node information here may be determined by the second node itself, or may be sent by the first node to the second node.

Optionally, the method of the embodiment of the present application converts at least one of the destination address and the source address corresponding to the service request, including:

Alternatively, if the internal source address of the service request is the intranet IP address of the terminal device, the source address of the service request The address is converted into the external IP address and port number of the terminal device.

In an embodiment of the present application, the second node obtains target information sent by the first node, and the target information includes one of the following: an identifier of a service node determined by the first node based on the first information; a target service identifier and the first information; a target service identifier and a target computing load information, wherein the target computing load information is computing load information of a target service, and the target service is a service corresponding to the service identifier; a service list and service node information corresponding to each service in the service list; wherein the first information includes service information and computing load information of services provided by non-mobile communication network function nodes, and the target service identifier is a service identifier in a service request received by the first node. Through the target information, the second node can determine the service node that provides services for nodes within the mobile network in combination with the service information and computing load information of services provided by non-mobile communication network function nodes.

The information processing method provided in the embodiment of the present application can be executed by an information processing device. In the embodiment of the present application, the information processing device provided in the embodiment of the present application is described by taking the information processing device executing the information processing method as an example.

As shown in FIG. 10 , the embodiment of the present application further provides an information processing device 1000, which is applied to a first node and includes:

The first acquisition module 1001 is used to acquire first information, where the first node is a mobile communication network function node, the first information includes service information and computing load information of services provided by non-mobile communication network function nodes, and the first information is used to determine the service node.

Optionally, the device of the embodiment of the present application further includes:

A first receiving module, configured to receive a service request sent by a service request sending node, wherein the service request at least includes a target service identifier, and the target service identifier is used to identify a target service requested by the service request;

The first determining module is used to determine a service node according to the target service identifier and the first information, where the service node is a node that provides the target service.

A second receiving module is used to receive service node request information sent by a second node, the service node request information at least includes a target service identifier, the target service identifier is used to identify a target service requested by the service request, the second node is a mobile communication network function node, and the service node request information is sent by the second node after receiving the service request sent by the service request node;

A second determining module, configured to determine a service node according to the target service identifier and the first information, wherein the service node is a node that provides the target service;

A first sending module is configured to send the identifier of the service node to the second node.

Optionally, the second determination module is used to determine the service node according to the target service identifier, the first information and the second information;

The second information includes at least one of the following:

The network transmission state corresponding to the network topology structure;

The network slice type corresponding to the terminal device;

Protocol data unit (PDU) session types supported by the terminal device.

A third receiving module, configured to receive a service request sent by a service request sending node, wherein the service request includes a target service identifier, and the target service identifier is used to identify a target service requested by the service request;

A second sending module, configured to send third information to a second node according to the service request, wherein the third information is used by the second node to determine a service node, and the second node is a mobile communication network function node;

A third acquisition module, used to acquire a service node identifier sent by the second node;

The third information includes one of the following:

the target service identifier and the first information;

Optionally, the service request further includes at least one of the following:

The identifier of the node sending the service request;

The identification of the node receiving the service response;

Load values and measurement parameters corresponding to the load values;

Calculate delay information;

response time information;

Memory information;

Store information;

Network bandwidth information;

Length of service duration.

The third sending module is used to send a service list and service node information corresponding to each service in the service list to a second node, where the second node is a mobile communication network function node.

The third determination module is used to, when receiving a communication bearer establishment request or a communication bearer modification request from a terminal device, determine the communication bearer establishment request or a communication bearer modification request according to the service list, the service node identifier, the computing load information corresponding to each service node identifier, the network topology between the terminal device and the first node, and the network transmission state corresponding to the network topology. at least one item of the service list, determining a service node corresponding to each service in the service list, wherein the services in the service list are services potentially requested by the terminal device.

The fourth determination module is used to re-determine the service node corresponding to each service in the service list when at least one of the services in the service list, the computing load information corresponding to the service node identifier, the network topology structure, and the network transmission status corresponding to the network topology structure is updated.

Optionally, the network topology structure includes at least one of the following: a serving base station of the terminal device; a target node for transmitting a first PDU session; wherein the first PDU session is a PDU session corresponding to the service request;

And/or, the network transmission status includes at least one of the following:

Uplink transmission delay between terminal equipment and base station;

Downlink transmission delay between terminal equipment and base station;

Uplink transmission delay between the base station and the target node;

Downlink transmission delay between the base station and the target node;

The round-trip transmission delay between the base station and the target node;

Uplink bandwidth between terminal devices and base stations;

Downlink bandwidth between terminal devices and base stations;

Uplink bandwidth between the terminal device and the target node

Downlink bandwidth between the terminal device and the target node;

Optionally, the service information includes at least one of the following: at least one of a service identifier and a service instance identifier, wherein the service identifier is used to identify a service, the service instance identifier is used to identify a service instance that provides the service, and the service instance corresponds to a service node;

And/or, the computing load information includes at least one of the following:

Load value;

The metric parameter corresponding to the load value;

A fourth acquisition module, used to acquire the router node information of the next hop to which the first node forwards the service request;

The first forwarding module is used to forward the service request according to the router node information of the next hop.

The first conversion processing module is used to convert at least one of the destination address and the source address corresponding to the service request.

Optionally, the first conversion processing module is used to:

The external source address of the service request is set to the IP address corresponding to the first node, and the service request The external destination address is set to the IP address of the egress computing priority network CFN node that can be routed to the target service node;

Optionally, the first node includes: an IMS function node, a trusted data network node, a core network function node or a radio access network function node.

As shown in FIG. 11 , the embodiment of the present application further provides an information processing device 1100, which is applied to a second node and includes:

A second acquisition module 1101 is used to acquire target information sent by a first node, where the first node and the second node are both mobile communication network function nodes;

The target information includes one of the following:

target service identifier and first information;

The fifth determination module is used to determine the service node according to the target information, where the target information includes the target service identifier and the first information, or includes the target service identifier and the target computing load information.

The fourth sending module is used to send the identifier of the service node to the first node.

The fourth receiving module is used to receive a service request sent by the service request sending node, wherein the service request at least includes Target service identifier;

The sixth determination module is used to determine the service node according to the target service identifier and the target information.

Optionally, the service node is further related to second information, and the second information includes at least one of the following:

The second information includes at least one of the following:

The network transmission state corresponding to the network topology structure;

The network slice type corresponding to the terminal device;

Protocol data unit (PDU) session types supported by the terminal device.

And/or, the network transmission status includes at least one of the following:

Uplink transmission delay between terminal equipment and base station;

Downlink transmission delay between terminal equipment and base station;

Uplink transmission delay between the base station and the target node;

Downlink transmission delay between the base station and the target node;

The round-trip transmission delay between the base station and the target node;

Uplink bandwidth between terminal devices and base stations;

Downlink bandwidth between terminal devices and base stations;

Uplink bandwidth between the terminal device and the target node

Downlink bandwidth between the terminal device and the target node;

And/or, the computing load information includes at least one of the following:

Load value;

The metric parameter corresponding to the load value;

A fifth acquisition module, used to acquire the router node information of the next hop to which the second node forwards the service request;

The second forwarding module is used to forward the service request according to the router node information of the next hop.

The second conversion processing module is used to convert at least one of the destination address and the source address corresponding to the service request.

Optionally, the second conversion processing module is used to:

In an embodiment of the present application, the second node obtains target information sent by the first node, and the target information includes one of the following: an identifier of a service node determined by the first node based on the first information; a target service identifier and the first information; a target service identifier and a target computing load information, wherein the target computing load information is computing load information of a target service, and the target service is a service corresponding to the target service identifier; a service list and service node information corresponding to each service in the service list; wherein the first information includes service information and computing load information of services provided by non-mobile communication network function nodes, and the target service identifier is a service identifier in a service request received by the first node. Through the target information, the second node can determine the service node that provides services for nodes within the mobile network in combination with the service information and computing load information of services provided by non-mobile communication network function nodes.

The information processing device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device may be a terminal, or may be other devices other than a terminal. Exemplarily, the terminal may include but is not limited to the types of terminal 11 listed above, and other devices may be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

The information processing device provided in the embodiment of the present application can implement the various processes implemented by the method embodiments of Figures 4 to 8 and achieve the same technical effects. To avoid repetition, they will not be described here.

Optionally, as shown in FIG12, an embodiment of the present application further provides a communication device 1200, including a processor 1201 and a memory 1202, wherein the memory 1202 stores a program or instruction that can be run on the processor 1201. For example, when the communication device 1200 is a first node, the program or instruction is executed by the processor 1201 to implement the various steps of the information processing method embodiment executed by the first node, and the same technical effect can be achieved. When the communication device 1200 is a second node, the program or instruction is executed by the processor 1201 to implement the various steps of the information processing method embodiment executed by the second node, 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 terminal, including a processor and a communication interface, the communication interface is used to obtain first information, the first node is a mobile communication network function node, the first information includes service information and computing load information of services provided by non-mobile communication network function nodes, and the first information is used to determine the service node. Alternatively, the communication interface is used to obtain target information sent by the first node, the first node and the second node are both mobile communication network function nodes; wherein the target information includes one of the following: an identifier of a service node determined by the first node according to the first information;

target service identifier and first information;

The terminal embodiment corresponds to the first node or second node side method embodiment, and each implementation process and implementation mode of the method embodiment can be applied to the terminal embodiment and can achieve the same technical effect. Specifically, Figure 13 is a schematic diagram of the hardware structure of a terminal implementing the embodiment of the present application.

The terminal 1300 includes but is not limited to: a radio frequency unit 1301, a network module 1302, an audio output unit 1303, an input unit 1304, a sensor 1305, a display unit 1306, a user input unit 1307, an interface unit 1308, a memory 1309 and at least some of the components of a processor 1310.

Those skilled in the art will appreciate that the terminal 1300 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor 1310 through a power management system, so as to manage charging, discharging, and power consumption management through the power management system. The terminal structure shown in FIG13 does not constitute a limitation on the terminal, and the terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange components differently, which will not be described in detail here.

It should be understood that in the embodiment of the present application, the input unit 1304 may include a graphics processing unit (GPU) 13041 and a microphone 13042, and the graphics processor 13041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 1306 may include a display panel 13061, and the display panel 13061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1307 includes a touch panel 13071 and at least one of other input devices 13072. The touch panel 13071 is also called a touch screen. The touch panel 13071 may include two parts: a touch detection device and a touch controller. Other input devices 13072 may include, but are not limited to, a physical keyboard, function keys (such as a volume control key, a switch key, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

In the embodiment of the present application, after receiving downlink data from the network side device, the RF unit 1301 can transmit the data to the processor 1310 for processing; in addition, the RF unit 1301 can send uplink data to the network side device. Generally, the RF unit 1301 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

The memory 1309 can be used to store software programs or instructions and various data. The memory 1309 can mainly include storage A first storage area for programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 1309 may include a volatile memory or a non-volatile memory, or the memory 1309 may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM). The memory 1309 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

The processor 1310 may include one or more processing units; optionally, the processor 1310 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1310.

In one embodiment of the present application, the radio frequency unit 1301 is used to obtain first information, where the first node is a mobile communication network function node, and the first information includes service information and computing load information of services provided by non-mobile communication network function nodes, and the first information is used to determine the service node.

Optionally, the radio frequency unit 1301 is further configured to receive a service request sent by a service request sending node, wherein the service request at least includes a target service identifier, and the target service identifier is used to identify a target service requested by the service request;

The processor 1310 is configured to determine a service node according to the target service identifier and the first information, where the service node is a node that provides the target service.

Optionally, the radio frequency unit 1301 is further used to receive service node request information sent by the second node, where the service node request information at least includes a target service identifier, where the target service identifier is used to identify a target service requested by the service request, and the second node is a mobile communication network function node. The service node request information is sent by the second node after receiving the service request sent by the service request node;

The processor 1310 is configured to determine a service node according to the target service identifier and the first information, where the service node is a node that provides the target service;

The radio frequency unit 1301 is further configured to send the identifier of the serving node to the second node.

Optionally, the processor 1310 is further configured to determine the service node according to the target service identifier, the first information, and the second information;

The second information includes at least one of the following:

The network topology between the third node and the target node, the target node is a node for receiving the service request The node that sends the service data;

The network transmission state corresponding to the network topology structure;

The network slice type corresponding to the terminal device;

Protocol data unit (PDU) session types supported by the terminal device.

Optionally, the radio frequency unit 1301 is further used to receive a service request sent by a service request sending node, where the service request includes a target service identifier, and the target service identifier is used to identify a target service requested by the service request; according to the service request, send third information to a second node, where the third information is used by the second node to determine a service node, where the second node is a mobile communication network function node; and obtain a service node identifier sent by the second node;

The third information includes one of the following:

the target service identifier and the first information;

Optionally, the service request also includes at least one of the following: an identifier of a node sending a service request; an identifier of a node receiving a service response; a load value and a measurement parameter corresponding to the load value; calculation delay information; response time information; memory information; storage information; network bandwidth information; and service duration length.

Optionally, the radio frequency unit 1301 is further configured to send a service list and service node information corresponding to each service in the service list to a second node, where the second node is a mobile communication network function node.

Optionally, the processor 1310 is further used to determine, upon receiving a communication bearer establishment request or a communication bearer modification request from a terminal device, a service node corresponding to each service in the service list based on the service list, a service node identifier, computing load information corresponding to each service node identifier, a network topology between the terminal device and the first node, and at least one of a network transmission state corresponding to the network topology, wherein the services in the service list are services potentially requested by the terminal device.

Optionally, the processor 1310 is further used to re-determine the service node corresponding to each service in the service list when at least one of the services in the service list, the computing load information corresponding to the service node identifier, the network topology structure, and the network transmission status corresponding to the network topology structure is updated.

And/or, the network transmission status includes at least one of the following:

Uplink transmission delay between terminal equipment and base station;

Downlink transmission delay between terminal equipment and base station;

Uplink transmission delay between the base station and the target node;

Downlink transmission delay between the base station and the target node;

The round-trip transmission delay between the base station and the target node;

Uplink bandwidth between terminal devices and base stations;

Downlink bandwidth between terminal devices and base stations;

Uplink bandwidth between the terminal device and the target node

Downlink bandwidth between the terminal device and the target node;

And/or, the computing load information includes at least one of the following:

Load value;

The metric parameter corresponding to the load value;

Optionally, the radio frequency unit 1301 is further configured to obtain the router node information of the next hop to which the first node forwards the service request; and forward the service request according to the router node information of the next hop.

Optionally, the processor 1310 is further configured to convert at least one of a destination address and a source address corresponding to the service request.

Optionally, the processor 1310 is further configured to set the external source address of the service request to the IP address corresponding to the first node, and set the external destination address of the service request to the IP address of an egress computing priority network CFN node that can be routed to the target service node;

Optionally, the processor 1310 is further configured to: the first node includes: an IMS function node, a trusted data network node, a core network function node, or a radio access network function node.

In one embodiment of the present application, the radio frequency unit 1301 is used to obtain target information sent by a first node, where the first node and the second node are both mobile communication network function nodes;

The target information includes one of the following:

target service identifier and first information;

The target service identifier and the target computing load information are the computing load information of the target service. information, the target service being the service corresponding to the target service identifier;

Optionally, when the target information is an identifier of a service node, the radio frequency unit 1301 is further used to receive a service request sent by a service request sending node, wherein the service request includes at least a target service identifier; and send service node request information to the first node according to the service request, wherein the service node request information includes at least the target service identifier.

Optionally, the processor 1310 is further configured to determine a service node according to the target information, where the target information includes a target service identifier and the first information, or includes a target service identifier and target computing load information.

Optionally, the radio frequency unit 1301 is further configured to send an identifier of the service node to the first node.

Optionally, the radio frequency unit 1301 is further used to receive a service request sent by a service request sending node, where the service request at least includes a target service identifier; the processor 1310 is further used to determine a service node according to the target service identifier and target information.

The second information includes at least one of the following:

The network transmission state corresponding to the network topology structure;

The network slice type corresponding to the terminal device;

Protocol data unit (PDU) session types supported by the terminal device.

And/or, the network transmission status includes at least one of the following:

Uplink transmission delay between terminal equipment and base station;

Downlink transmission delay between terminal equipment and base station;

Uplink transmission delay between the base station and the target node;

Downlink transmission delay between the base station and the target node;

The round-trip transmission delay between the base station and the target node;

Uplink bandwidth between terminal devices and base stations;

Downlink bandwidth between terminal devices and base stations;

Uplink bandwidth between the terminal device and the target node

Downlink bandwidth between the terminal device and the target node;

And/or, the computing load information includes at least one of the following:

Load value;

The metric parameter corresponding to the load value;

Optionally, the radio frequency unit 1301 is further configured to obtain information about a next-hop router node to which the second node forwards the service request.

The embodiment of the present application also provides a network side device, including a processor and a communication interface, wherein the communication interface is used to obtain first information, the first node is a mobile communication network function node, the first information includes service information and computing load information of services provided by non-mobile communication network function nodes, and the first information is used to determine the service node. Alternatively, the communication interface is used to obtain target information sent by the first node, and the first node and the second node are both mobile communication network function nodes; wherein the target information includes one of the following: an identifier of a service node determined by the first node according to the first information;

target service identifier and first information;

This network side device embodiment corresponds to the method embodiment on the first node or second node side described above. Each implementation process and implementation method of the method embodiment described above can be applied to this network side device embodiment and can achieve the same technical effect.

Specifically, the embodiment of the present application also provides a network side device. As shown in Figure 14, the network side device 1400 includes: an antenna 141, a radio frequency device 142, a baseband device 143, a processor 144 and a memory 145. The antenna 141 is connected to the radio frequency device 142. In the uplink direction, the radio frequency device 142 receives information through the antenna 141 and sends the received information to the baseband device 143 for processing. In the downlink direction, the baseband device 143 processes the information to be sent and sends it to the radio frequency device 142. The radio frequency device 142 processes the received information and sends it out through the antenna 141.

The method executed by the network-side device in the above embodiment may be implemented in the baseband device 143, which includes a baseband processor.

The baseband device 143 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 14, one of the chips is, for example, a baseband processor, which is connected to the memory 145 through a bus interface to call the program in the memory 145 to execute the network device operations shown in the above method embodiment.

The network side device may also include a network interface 146, which is, for example, a common public radio interface (CPRI).

Specifically, the network side device 1400 of the embodiment of the present application also includes: instructions or programs stored in the memory 145 and executable on the processor 144. The processor 144 calls the instructions or programs in the memory 145 to execute the methods executed by the modules shown in Figures 10 or 11 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

Specifically, the embodiment of the present application further provides a network side device. As shown in FIG15 , the network side device 1500 includes: a processor 1501, a network interface 1502, and a memory 1503. The network interface 1502 is, for example, a common public radio interface (CPRI).

Specifically, the network side device 1500 of the embodiment of the present application also includes: instructions or programs stored in the memory 1503 and executable on the processor 1501. The processor 1501 calls the instructions or programs in the memory 1503 to execute the methods executed by the modules shown in Figures 10 or 11 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. When the program or instruction is executed by a processor, the various processes of the above-mentioned information processing method embodiment are 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.

The present application embodiment further provides a chip, the chip comprising a processor and a communication interface, the communication interface and The processor is coupled, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned information processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

It should be understood that 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 information processing method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described here.

An embodiment of the present application also provides an information transmission system, including: a first node and a second node, wherein the first node can be used to execute the steps of the information processing method executed by the first node as described above, and the second node can be used to execute the steps of the information processing method executed by the second node as described above.

It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be noted that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, 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.

The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

An information processing method, comprising:

The first node obtains first information, where the first node is a mobile communication network function node, the first information includes service information and computing load information of services provided by non-mobile communication network function nodes, and the first information is used to determine a service node.
The method according to claim 1, further comprising:

The first node receives a service request sent by a service request sending node, where the service request at least includes a target service identifier, and the target service identifier is used to identify a target service requested by the service request;

The first node determines a service node according to the target service identifier and the first information, where the service node is a node that provides the target service.
The method according to claim 1, further comprising:

The first node receives service node request information sent by the second node, the service node request information at least includes a target service identifier, the target service identifier is used to identify a target service requested by the service request, the second node is a mobile communication network function node, and the service node request information is sent by the second node after receiving the service request sent by the service request node;

The first node determines a service node according to the target service identifier and the first information, where the service node is a node that provides the target service;

The first node sends the identifier of the service node to the second node.
The method according to claim 2 or 3, wherein the first node determines the service node according to the target service identifier and the first information, comprising:

The first node determines the service node according to the target service identifier, the first information and the second information;

The second information includes at least one of the following:

A network topology structure between a third node and a target node, wherein the target node is a node that receives service data sent by the service request sending node;

The network transmission state corresponding to the network topology structure;

The third node includes a terminal device in a mobile communication network that sends the service request and/or receives a service response corresponding to the service request; or, the third node includes a terminal device in a mobile communication network that potentially performs a first type of service, and the first type of service includes communication and computing fusion services.
The method according to claim 4, wherein the terminal device that potentially performs the first type of service is determined according to at least one of the following:

capability information of the terminal device, the capability information being used to indicate whether the terminal device supports the first type of service;

The network slice type corresponding to the terminal device;

Protocol data unit (PDU) session types supported by the terminal device.
The method according to claim 1, further comprising:

The first node receives a service request sent by a service request sending node, where the service request includes a target service identifier, and the target service identifier is used to identify a target service requested by the service request;

The first node sends third information to the second node according to the service request, where the third information is used by the second node to determine a service node, and the second node is a mobile communication network function node;

The first node obtains the service node identifier sent by the second node;

The third information includes one of the following:

the target service identifier and the first information;

The target service identifier and target computing load information, wherein the target computing load information is computing load information of the target service, and the target service is the service corresponding to the service request.
The method according to claim 2 or 6, wherein the service request further comprises at least one of the following:

The identifier of the node sending the service request;

The identification of the node receiving the service response;

Load values and measurement parameters corresponding to the load values;

Calculate delay information;

response time information;

Memory information;

Store information;

Network bandwidth information;

Length of service duration.
The method according to claim 1, further comprising:

A service list and service node information corresponding to each service in the service list are sent to a second node, where the second node is a mobile communication network function node.
The method according to claim 8, further comprising:

When a communication bearer establishment request or a communication bearer modification request is received from a terminal device, the service node corresponding to each service in the service list is determined based on the service list, the service node identifier, the computing load information corresponding to each service node identifier, the network topology between the terminal device and the first node, and at least one of the network transmission states corresponding to the network topology, wherein the services in the service list are services potentially requested by the terminal device.
The method according to claim 9, further comprising:

When at least one of the services in the service list, the computing load information corresponding to the service node identifier, the network topology structure, and the network transmission state corresponding to the network topology structure is updated, the service node corresponding to each service in the service list is re-determined.
The method according to claim 4, 5, 9 or 10, wherein the network topology includes at least one of the following: a serving base station of the terminal device; a target node for transmitting a first PDU session; wherein the first PDU The session is a PDU session corresponding to the service request;

And/or, the network transmission status includes at least one of the following:

Uplink transmission delay between terminal equipment and base station;

Downlink transmission delay between terminal equipment and base station;

The round-trip transmission delay between the terminal device and the base station;

Uplink transmission delay between the base station and the target node;

Downlink transmission delay between the base station and the target node;

The round-trip transmission delay between the base station and the target node;

Uplink bandwidth between terminal devices and base stations;

Downlink bandwidth between terminal devices and base stations;

Uplink bandwidth between the terminal device and the target node

Downlink bandwidth between the terminal device and the target node;

The target node is a node that receives service data sent by the service request sending node.
The method according to any one of claims 1 to 11, wherein the service information comprises at least one of the following: at least one of a service identifier and a service instance identifier, wherein the service identifier is used to identify a service, the service instance identifier is used to identify a service instance that provides a service, and the service instance corresponds to a service node;

And/or, the computing load information includes at least one of the following:

Load value;

The metric parameter corresponding to the load value;

The transmission overhead of the service provided by the non-mobile communication network function node in the non-mobile communication network.
The method according to claim 2 or 7, further comprising:

Obtaining the router node information of the next hop to which the first node forwards the service request;

The service request is forwarded according to the router node information of the next hop.
The method according to claim 2, 7 or 13, further comprising:

Convert at least one of the destination address and the source address corresponding to the service request.
The method according to claim 14, wherein converting at least one of a destination address and a source address corresponding to the service request comprises:

Setting the external source address of the service request to the IP address corresponding to the first node, and setting the external destination address of the service request to the IP address of an egress computing priority network CFN node that can be routed to the target service node;

Alternatively, the destination address in the service request is set to the identifier of the service instance that provides the target service information;

Alternatively, when the internal source address of the service request is the intranet IP address of the terminal device, the source address of the service request is converted into the extranet IP address and port number of the terminal device.
The method according to any one of claims 1 to 15, wherein the first node comprises: an IMS function node, a trusted data network node, a core network function node, or a radio access network function node.
An information processing method, comprising:

The second node acquires target information sent by the first node, wherein the first node and the second node are both mobile communication network function nodes;

The target information includes one of the following:

An identifier of a service node determined by the first node according to the first information;

target service identifier and first information;

A target service identifier and target computing load information, wherein the target computing load information is computing load information of a target service, and the target service is a service corresponding to the target service identifier;

A service list and service node information corresponding to each service in the service list;

The first information includes service information and computing load information of the service provided by the non-mobile communication network function node, and the target service identifier is the service identifier in the service request received by the first node.
The method according to claim 17, wherein, when the target information is an identifier of a service node, the method further comprises:

The second node receives a service request sent by a service request sending node, where the service request at least includes a target service identifier;

The second node sends service node request information to the first node according to the service request, where the service node request information at least includes the target service identifier.
The method according to claim 17, further comprising:

A service node is determined according to the target information, where the target information includes a target service identifier and first information, or includes a target service identifier and target computing load information.
The method according to claim 19, further comprising:

The identifier of the service node is sent to the first node.
The method according to claim 17, further comprising:

The second node receives a service request sent by a service request sending node, where the service request at least includes a target service identifier;

The second node determines a service node according to the target service identifier and the target information.
The method according to claim 19 or 21, wherein the service node is further associated with second information, and the second information includes at least one of the following:

The second information includes at least one of the following:

A network topology structure between a third node and a target node, wherein the target node is a node that receives service data sent by the service request sending node;

The network transmission state corresponding to the network topology structure;

The third node includes a terminal device in a mobile communication network that sends the service request and/or receives a service response corresponding to the service request; or, the third node includes a terminal device in a mobile communication network that potentially performs a first type of service, and the first type of service includes communication and computing fusion services.
The method according to claim 22, wherein the terminal device that potentially performs the first type of service is determined according to at least one of the following:

capability information of the terminal device, the capability information being used to indicate whether the terminal device supports the first type of service;

The network slice type corresponding to the terminal device;

Protocol data unit (PDU) session types supported by the terminal device.
The method according to claim 22 or 23, wherein the network topology structure includes at least one of the following: a serving base station of the terminal device; a target node for transmitting a first PDU session; wherein the first PDU session is a PDU session corresponding to the service request;

And/or, the network transmission status includes at least one of the following:

Uplink transmission delay between terminal equipment and base station;

Downlink transmission delay between terminal equipment and base station;

The round-trip transmission delay between the terminal device and the base station;

Uplink transmission delay between the base station and the target node;

Downlink transmission delay between the base station and the target node;

The round-trip transmission delay between the base station and the target node;

Uplink bandwidth between terminal devices and base stations;

Downlink bandwidth between terminal devices and base stations;

Uplink bandwidth between the terminal device and the target node

Downlink bandwidth between the terminal device and the target node;

The target node is a node that receives service data sent by the service request sending node.
The method according to any one of claims 17 to 24, wherein the service information comprises at least one of the following: at least one of a service identifier and a service instance identifier, wherein the service identifier is used to identify a service, the service instance identifier is used to identify a service instance that provides a service, and the service instance corresponds to a service node;

And/or, the computing load information includes at least one of the following:

Load value;

The metric parameter corresponding to the load value;

The transmission overhead of the service provided by the non-mobile communication network function node in the non-mobile communication network.
The method according to claim 18 or 21, further comprising:

Obtaining the router node information of the next hop to which the second node forwards the service request;

The service request is forwarded according to the router node information of the next hop.
The method according to any one of claims 17 to 26, further comprising:

Convert at least one of the destination address and the source address corresponding to the service request.
The method according to claim 27, wherein converting at least one of a destination address and a source address corresponding to the service request comprises:

Setting the external source address of the service request to the IP address corresponding to the first node, and setting the external destination address of the service request to the IP address of an egress computing priority network CFN node that can be routed to the target service node;

Alternatively, the destination address in the service request is set to the identifier of the service instance that provides the target service information;

Alternatively, when the internal source address of the service request is the intranet IP address of the terminal device, the source address of the service request is converted into the extranet IP address and port number of the terminal device.
An information processing device, applied to a first node, comprising:

The first acquisition module is used to acquire first information, where the first node is a mobile communication network function node, the first information includes service information and computing load information of services provided by non-mobile communication network function nodes, and the first information is used to determine the service node.
The apparatus according to claim 29, further comprising:

A first receiving module, configured to receive a service request sent by a service request sending node, wherein the service request at least includes a target service identifier;

The first determining module is used to determine a service node according to the target service identifier and the first information, wherein the service node is a node that provides a service corresponding to the target service identifier.
The apparatus according to claim 29, further comprising:

A second receiving module is used to receive service node request information sent by a second node, the service node request information at least includes a target service identifier, the target service identifier is used to identify a target service requested by the service request, the second node is a mobile communication network function node, and the service node request information is sent by the second node after receiving the service request sent by the service request node;

A second determining module, configured to determine a service node according to the target service identifier and the first information, wherein the service node is a node that provides the target service;

A first sending module is configured to send the identifier of the service node to the second node.
An information processing device, applied to a second node, comprising:

A second acquisition module, configured to acquire target information sent by a first node, wherein the first node and the second node are both mobile communication network function nodes;

The target information includes one of the following:

An identifier of a service node determined by the first node according to the first information;

target service identifier and first information;

A target service identifier and target computing load information, wherein the target computing load information is computing load information of a target service, and the target service is a service corresponding to the target service identifier;

A service list and service node information corresponding to each service in the service list;

The first information includes service information and computing load information of the service provided by the non-mobile communication network function node, and the target service identifier is the service identifier in the service request received by the first node.
A communication device comprises a processor and a memory, wherein the memory stores a program executable on the processor. A program or instruction, which, when executed by the processor, implements the steps of the information processing method according to any one of claims 1 to 16, or implements the steps of the information processing method according to any one of claims 17 to 28.
A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the information processing method according to any one of claims 1 to 16, or implements the steps of the information processing method according to any one of claims 17 to 28.