WO2022242661A1 - 通信处理方法及相关设备 - Google Patents

通信处理方法及相关设备 Download PDF

Info

Publication number
WO2022242661A1
WO2022242661A1 PCT/CN2022/093444 CN2022093444W WO2022242661A1 WO 2022242661 A1 WO2022242661 A1 WO 2022242661A1 CN 2022093444 W CN2022093444 W CN 2022093444W WO 2022242661 A1 WO2022242661 A1 WO 2022242661A1
Authority
WO
WIPO (PCT)
Prior art keywords
path
target number
user equipment
service node
data
Prior art date
Application number
PCT/CN2022/093444
Other languages
English (en)
French (fr)
Inventor
赵明宇
严学强
吴建军
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP22803981.4A priority Critical patent/EP4329374A1/en
Publication of WO2022242661A1 publication Critical patent/WO2022242661A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H04W40/36—Modification of an existing route due to handover

Definitions

  • the present invention relates to the technical field of communication, in particular to a communication processing method and related equipment.
  • UCN user-centric network
  • UE user equipment
  • NSN network service node
  • edge cloud will be widely deployed, so that the traffic will be centered on the distributed data center (data center, DC) / multi-access edge computing (mulit-access edge computing, MEC).
  • DC distributed data center
  • MEC multi-access edge computing
  • the trend of the series is growing, and the future traffic will show the characteristics of distributed and local, which is different from the traditional traffic mode of access, aggregation and concentration, and then backbone transmission to the core gateway.
  • the embodiment of the present application discloses a communication processing method and related equipment, which can be applied to a distributed DC/MEC-centric network architecture with distributed, dynamic, short-distance and short-hop data forwarding, and can effectively avoid the
  • the problem caused by the swelling of the routing table caused by the surge of traffic can reduce the complex configuration, reduce the processing burden of the control node, and improve the efficiency of data transmission.
  • the present application provides a communication processing method, the method including:
  • the first target number is used to calculate an egress port number for forwarding data forwarded by a forwarding device on the first path;
  • the ingress forwarding device is the next-hop device of the device at the starting point in the first path, and the first target number is used to add to the in the data of the endpoint device.
  • the user service node and the user equipment belong to nodes covered by the same edge cloud.
  • the communication path between the two is planned, and the communication between the two is realized based on the method of the remainder system. Because the UE and its USN are bound, the uplink transmission path must be from the UE to its USN, and the downlink transmission path must be from the USN to its corresponding UE. Therefore, for uplink and downlink data, when the UE and its USN are initially bound, The route calculation between the UE and the USN is performed by the NSN, and the corresponding target number is delivered to the ingress forwarding device of the communication path.
  • the target number can be reused, and subsequent calculations do not need to be frequent unless the routing conditions change; unlike existing solutions In the OpenFlow or KeyFlow protocol, whenever a new data packet arrives at the ingress router, it is necessary to trigger a pakcket-in message, throw the data packet to the controller, and the controller re-plans the route. That is, in this application, the processing burden of the NSN can be greatly reduced, and the performance of the NSN can be improved. In addition, since there is no need to calculate the communication path in real time, it can also reduce the signaling communication burden and data transmission delay, and improve data transmission efficiency.
  • the communication processing method of this application meets the requirements of more distributed, dynamic, and short-distance/short-hop data forwarding in the traffic model centered on distributed DC/MEC in the future, and is perfectly combined with the distributed MEC architecture, which is better than the current
  • the mainstream SR solution and the combination of KeyFlow and SDN have simpler configuration and simpler protocols, which can greatly reduce deployment and maintenance costs and improve deployment and maintenance efficiency.
  • the communication processing method of the present application does not require a routing table, which avoids the problem of routing table expansion caused by the surge in traffic; and the complex path calculation is realized by NSN, which reduces the number of forwarding devices compared to existing MPLS and SR. Burden, and greatly reduce the cumbersome configuration.
  • the method also includes:
  • the first path cannot realize the communication between the user service node and the user equipment, plan the communication path between the user equipment and the user service node to obtain a second path;
  • the first path is a path from the user equipment to the user service node;
  • the ingress forwarding device is an access device for connecting the user equipment to a communication network;
  • the first path cannot implement the
  • the situation of the communication between the user service node and the user equipment includes: the access device that the user equipment accesses to the communication network changes.
  • the present application provides a communication processing method, the method including:
  • the first target number is used to forward the communication data between the user service node and the user equipment according to a first path, and the first path is the case where authentication is completed between the user service node and the user equipment
  • the user service node is used to provide services for the user equipment
  • a port number is calculated based on the first target number, and the second data is sent out through the outbound port number.
  • the execution subject of the communication processing method may be the ingress forwarding device in the above-mentioned first path, and the ingress forwarding device may receive the above-mentioned first target number sent by the network service node after the UE and the USN are bound, and when needed When forwarding data between the UE and the USN through the first path, add the first target number to the data to be forwarded, and calculate the outbound port for data forwarding based on the first target number to forward the data without routing table lookup table, avoiding the problem of routing table expansion caused by traffic surge. It does not need to be like the OpenFlow or KeyFlow protocol solutions in the existing solutions.
  • this application calculates the outbound port number of the data through the target number at the ingress forwarding device, without looking up the table to find the outbound port, thereby solving the problem of excessive storage resource occupation caused by the expansion of the routing table or flow table.
  • the method further includes: receiving a second target number, and replacing the locally stored first target number with the second target number; the second target number is used to forward the user service according to the second path
  • the second path is planned when the first path cannot realize the communication between the user service node and the user equipment.
  • the ingress forwarding device will receive the second target number, and then replace the first target number corresponding to the original path, so as to ensure that the data communication between UE and USN can be normal proceed without interruption.
  • the present application provides a communication processing device, which includes:
  • a planning unit configured to plan a communication path between the user service node and the user equipment to obtain a first path when the authentication between the perceived user service node and the user equipment is completed, and the user service node is used for the user equipment Provide services;
  • a calculation unit configured to calculate a first target number based on the first path, and the first target number is used to calculate the output port number of the data forwarded by the forwarding device on the first path;
  • a sending unit configured to send the first target number to an ingress forwarding device, the ingress forwarding device is the next-hop device of the device at the starting point in the first path, and the first target number is used to add to the ingress forwarding device In the data to the end device of the first path.
  • the user service node and the user equipment belong to nodes covered by the same edge cloud.
  • the planning unit is further configured to plan a communication between the user equipment and the user service node when the first path cannot realize the communication between the user service node and the user equipment.
  • the communication path obtains the second path;
  • the calculation unit is also used to calculate a second target number based on the second path, and the second target number is used to calculate the output port number of the data forwarded by the forwarding device on the second path;
  • the sending unit is further configured to send the second target number to the ingress forwarding device, and the second target number is used to add to the data sent by the ingress forwarding device to the terminal device of the second path.
  • the first path is a path from the user equipment to the user service node;
  • the ingress forwarding device is an access device for connecting the user equipment to a communication network;
  • the situation that the first path cannot realize the communication between the user service node and the user equipment includes:
  • the access device for accessing the user equipment to the communication network is changed.
  • the present application provides a communication processing device, which includes:
  • a receiving unit configured to receive a first target number, the first target number is used to forward the communication data between the user service node and the user equipment according to a first path, the first path is between the user service node and the user equipment
  • the user service node is used to provide services for the user equipment
  • the receiving unit is also used to receive first data, and find the first target number based on the first data;
  • a writing unit configured to write the first target number into the first data to obtain second data
  • a calculation unit configured to calculate the port number based on the first target number
  • a sending unit configured to send the second data from the outbound port number.
  • the receiving unit is also used for:
  • the second target number is used to forward the communication data between the user service node and the user equipment according to the second path, and the second The path is obtained through planning when the first path cannot realize the communication between the user service node and the user equipment.
  • the present application provides a communication processing device, which may include a processor and a memory, configured to implement the communication processing method described in the foregoing first aspect and its possible implementation manners.
  • the memory is coupled to the processor, and when the processor executes the computer program stored in the memory, the method described in the first aspect or any possible implementation manner of the first aspect may be implemented.
  • the device may further include a communication interface, which is used for the device to communicate with other devices.
  • the communication interface may be a transceiver, circuit, bus, module or other type of communication interface.
  • the communication interface includes a receiving interface and a sending interface, the receiving interface is used for receiving messages, and the sending interface is used for sending messages.
  • the device may include:
  • the processor plans a communication path between the user service node and the user equipment to obtain a first path when the authentication between the user service node and the user equipment is perceived, and the user service node is used to provide services for the user equipment ; Calculate the first target number based on the first path, the first target number is used to calculate the output port number of the forwarding device forwarding data on the first path; send the first target number to the ingress forwarding device through the communication interface, the The ingress forwarding device is a next-hop device of the device at the starting point in the first path, and the first destination number is used to add to the data sent by the ingress forwarding device to the terminal device of the first path.
  • the computer program in the memory in this application can be stored in advance or can be stored after being downloaded from the Internet when using the device.
  • This application does not specifically limit the source of the computer program in the memory.
  • the coupling in the embodiments of the present application is an indirect coupling or connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the present application provides a communication processing device, which may include a processor and a memory, configured to implement the communication processing method described in the above second aspect and its possible implementation manners.
  • the memory is coupled to the processor, and when the processor executes the computer program stored in the memory, the method described in the second aspect or any possible implementation manner of the second aspect may be implemented.
  • the device may further include a communication interface, which is used for the device to communicate with other devices.
  • the communication interface may be a transceiver, circuit, bus, module or other type of communication interface.
  • the communication interface includes a receiving interface and a sending interface, the receiving interface is used for receiving messages, and the sending interface is used for sending messages.
  • the device may include:
  • the processor receives a first target number through a communication interface, and the first target number is used to forward the communication data between the user service node and the user equipment according to a first path, and the first path is between the user service node and the user equipment
  • the user service node is used to provide services for the user equipment; receive the first data through the communication interface, and find the first target number based on the first data; the first target Write the number into the first data to obtain the second data; calculate the port number based on the first target number, and send the second data from the output port number through the communication interface.
  • the computer program in the memory in this application can be stored in advance or can be stored after being downloaded from the Internet when using the device.
  • This application does not specifically limit the source of the computer program in the memory.
  • the coupling in the embodiments of the present application is an indirect coupling or connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the present application provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and the computer program is executed by a processor to implement the method described in any one of the above-mentioned first aspects; or, the The computer program is executed by the processor to implement the method described in the second aspect above.
  • the present application provides a computer program product.
  • the computer program product When the computer program product is run on a computer, the computer is made to execute the method described in any one of the above-mentioned first aspects; or, the computer is made to execute the above-mentioned second aspect. the method described.
  • the devices described in the third aspect, the fourth aspect, the fifth aspect and the sixth aspect provided above, the computer storage medium described in the seventh aspect, and the computer program product described in the eighth aspect are all used to execute The method provided by any one of the first aspect and the second aspect. Therefore, the beneficial effects that it can achieve can refer to the beneficial effects in the corresponding method, and will not be repeated here.
  • FIGS 1 to 3 are schematic diagrams of scenarios provided by the embodiments of the present application.
  • Fig. 4 is a schematic diagram showing a comparison between the network architecture provided by the present application and the traditional network architecture
  • FIG. 5 is a schematic flow diagram of the communication processing method provided by the present application.
  • Figure 6 is a schematic diagram of the transmission path provided by the present application.
  • FIG. 7 is a schematic diagram of an edge cloud structure provided by the present application.
  • Figure 8 and Figure 9 are schematic diagrams showing the logical structure of the device provided by the present application.
  • FIG. 10 and FIG. 11 are schematic diagrams of the physical structure of the device provided by the present application.
  • ⁇ m1,m2,m3,...,mN ⁇ is a group of coprime arrays, and N is an integer greater than 1;
  • ⁇ x1,x2,x3,...,xN ⁇ is a set of integer arrays
  • Any arbitrary integer X smaller than M can be expressed as a set of N smaller integers in the defined remainder system
  • xi ⁇ X>mi
  • xi can be obtained from X by taking the remainder of the corresponding mi. In the following description of the present application, this X may be referred to as a target number.
  • Edge cloud is a small-scale cloud data center that is distributed on the edge of the network and provides real-time data processing and analysis decision-making. Based on the advantages of the edge cloud, network edge cloudification has become an inevitable trend.
  • the edge cloud and the core cloud (the core cloud is a large-scale cloud service data center) form a synergistic complementarity.
  • the edge cloud is closer to the user and can better support latency and data privacy. It is suitable for distributed deployment of network functions, such as applications with high requirements.
  • the scenario of deploying edge cloud can be seen in Figure 1 for example.
  • the entire system architecture can be divided into three layers: terminal layer, edge cloud layer, and core cloud layer.
  • the terminal at the terminal layer accesses the edge cloud through access devices such as base stations or wireless access points, and the terminal is user equipment (UE).
  • UE user equipment
  • Multiple edge clouds in the edge cloud layer can establish communication connections with each other, and the multiple edge clouds establish communication connections with the core cloud. No matter the plurality of edge clouds or core clouds can provide application services (application service, APPs).
  • APPs application service
  • a user-centric (user-centric network, UCN) network architecture can be designed, as shown in Figure 2 for an example.
  • Figure 2 exemplarily shows a schematic diagram of a network architecture of a UCN.
  • a network service node network service node, NSN
  • a user service node network service node, USN
  • the user service node USN can provide required services for the user equipment UE bound to it.
  • the network service node NSN can provide required services to the USN and its corresponding terminals in the edge cloud where it is located.
  • FIG. 3 is a schematic diagram of another UCN network architecture.
  • the core cloud and each edge cloud are deployed with a network service node NSN, and these NSNs can communicate with each other.
  • One or more user service nodes USN are also deployed in each edge cloud, and each USN is associated and bound with a user equipment UE.
  • Data communicated between the USN and the UE is forwarded through the forwarding device.
  • the forwarding device may be, for example, an access device, a router, a gateway, or a switch, and other devices capable of forwarding data
  • the access device may be, for example, a base station or a wireless access point.
  • the aforementioned network service node NSN and user service node USN may be application service software deployed in the server.
  • multiple NSNs and multiple USNs can be deployed on one server or one server cluster, or one NSN and one or more USNs can be deployed on one server or one server cluster, or one server or one server cluster can be deployed An NSN, each USN is also separately deployed on a server and so on. This application does not limit the specific deployment of NSN or USN.
  • each edge cloud is a multi-access edge computing (mulit-access edge computing, MEC) domain, and the nodes and devices under the edge cloud belong to the nodes and devices in the MEC domain.
  • MEC multi-access edge computing
  • IP Internet protocol
  • the existing KeyFlow is combined with a software defined network (software defined network, SDN) solution, and the KeyFlow application is deployed on the OpenFlow controller, which is used to calculate the target number through the above-mentioned remainder system RNS and issue the target number.
  • the ingress edge router throws the data packet to the controller, and the controller calculates the forwarding path and the target number, generates a packet header including the target number (the packet header can be called an RNS header), and sends it to the ingress and egress edges Router; the ingress router adds a packet header including the target number to the data, and calculates the port along the route based on the target number, and forwards it; at the egress edge router, strips the packet header including the target number.
  • SDN software defined network
  • the aforementioned packet header including the target number may be called an RNS header, and the RNS header may include information such as source and destination addresses and destination addresses of the data packet in addition to the target number.
  • RNS header may include information such as source and destination addresses and destination addresses of the data packet in addition to the target number.
  • Step 1 The data packet from autonomous domain 1 enters the ingress edge router, triggers a packet-in message, and sends the data packet to the OpenFlow controller; the KeyFlow application obtains the destination address from the data packet, plans the route based on the real-time network topology, and plans the result From router 4->3->5 to the egress edge router; then based on RNS calculation, the target number is 25;
  • Step 2 The OpenFlow controller generates an RNS header including 25, and sends it to the ingress and egress edge routers through the flow-mod information, and the ingress and egress edge routers add a new flow table after receiving the packet header, indicating that the data packet enters the KeyFlow domain , perform routing based on the RNS header;
  • Step 3 The OpenFlow controller sends a modified-field action message to the ingress edge router, instructing the ingress edge router to write the RNS header into the data packet header; the ingress edge router forwards the data packet to router 4, and the remainder of 25/4 is 1, then from 1 The port is forwarded, reaches router 3, and the remainder is 1, forwarded from port 1 to router 5, the remainder is 0, forwarded from port 0, and reaches the egress edge router;
  • Step 4 The OpenFlow controller sends a modified-field action message to the egress edge router, instructing the egress edge router to remove the RNS header. Further forward according to the destination address.
  • the KeyFlow combined with SDN solution has the following disadvantages: 1. For the SDN controller, because the traffic surges, the short-term traffic is large, and the dynamic changes, when all these new data packets are thrown to the controller, the performance of the controller will drop sharply. At the same time, it is also necessary to frequently update the route forwarding table along the road, which increases signaling burden and delay. 2. KeyFlow must use the packet-in function of the Open-flow protocol to obtain the source and destination address information of the data packet, which requires one more step of operation and consumes more processing resources, and the Open-flow protocol is more complicated and expensive to implement.
  • MPLS multi-protocol label switching
  • RSVP-TE resource reservation protocol-traffic engineering
  • IGP interior gateway protocols
  • SR is an improvement scheme of MPLS and has great potential.
  • SR-BE best effort is the shortest path forwarding model, which uses prefix labels or node labels to guide message forwarding, and does not require a controller.
  • the segment routing (segment routing-traffic engineering, SR-TE) of traffic engineering requires a controller. After centralized path calculation, the controller sends a series of labels to the tunnel ingress node to control the forwarding path.
  • RSVP-TE label distribution protocol
  • LDP label distribution protocol
  • RSVP-TE label distribution protocol
  • the signaling mechanism of RSVP-TE is removed.
  • the root cause of the complexity of the protocol mechanism is that each device needs to maintain a set of complex signaling separately.
  • RSVP-TE After RSVP-TE obtains the path information through the extended IGP, it will calculate a suitable path, and then establish a tunnel by sending RSVP-TE signaling. Because it is possible that the current link has changed, and the convergence takes time, it may happen just at the moment of calculating the path. Therefore, there must be a mechanism to enable each tunnel to confirm the path again and reserve bandwidth before sending packets. This is the role of RSVP-TE signaling.
  • RSVP-TE is a distributed architecture, and each device can only see its own status, and if it needs to know the situation in other places, it must rely on the signaling mechanism to achieve it. However, if in the distributed architecture, a centralized control node is added to perform path calculation and label distribution in a unified manner, it will be easily solved. So SR and SDN are a match made in heaven. 2. Introduce LDP high efficiency and load sharing into RSVP-TE. RSVP-TE determines the path at the source end, and sometimes multiple paths meet the requirements, but RSVP-TE cannot perform load balancing. By 1) directly using IGP to allocate labels, the IGP protocol is extended, and label information is directly carried through IGP signaling, avoiding traffic black holes.
  • SR-TE For SR-TE, a free load sharing mode is implemented on the road sections that require load sharing. For example, there are two routes from Shanghai to Nanjing. Taiyuan and then to Xi'an, avoiding the congested route from Nanjing to Xi'an.
  • MPLS and SR solutions have the following problems: 1. RSVP-TE configuration is very cumbersome, the protocol is complex, and cannot be applied on a large scale; 2. Although SR-TE has been simplified compared to RSVP-TE, it still requires complex label configuration. The protocol is also relatively complex. 3. MPLS and SR are more used in the backbone network. 4. The label stack of SR-TE cannot be infinitely large, and needs to be solved by sticky labels.
  • FIG. 4 exemplarily shows a schematic diagram of a comparison between a three-layer network architecture and a UCN network architecture. It can be seen that the UCN network architecture simplifies the aggregation layer of the classic network architecture, and changes the ring network of the aggregation layer into a tree network. In addition, the edge cloud in the UCN network will be ubiquitous, and most traffic will be forwarded and distributed at the edge of the network. Termination, so that the traffic is centered on the distributed DC/MEC.
  • the surge in the number of access terminals makes the traffic increase in a geometric progression.
  • the surge in traffic leads to the expansion of the routing table, and the future traffic will be distributed and local.
  • the data between the terminal and the core gateway Forwarding is more distributed, dynamic, short-distance and short-hop.
  • the present application provides a communication processing method applicable to the UCN network architecture to solve the routing problem of data transmission in the UCN network architecture.
  • the communication processing method provided by this application includes but is not limited to the following steps:
  • the network service node and the user service node are respectively a certain edge cloud (or a certain MEC domain) in the UCN network architecture introduced above.
  • the certain MEC domain is referred to as the first MEC domain.
  • the following takes the first MEC domain as an example to describe the network service node NSN and the user service node USN.
  • the network service node NSN and the user service node USN are respectively referred to as the first NSN and the first USN.
  • the user equipment in S501 is bound to the first USN, and for the convenience of the following description, the user equipment is called the first UE.
  • the user service nodes are all generated by the first NSN, the network service node in the first MEC domain.
  • the first USN as an example, when the first UE first requests the first NSN in the first MEC domain where it is located to activate the service, after the first NSN receives the service activation request from the first UE, it The first UE generates a USN, and the USN is the above-mentioned first USN.
  • the first NSN After the first NSN generates the first USN, it participates in and assists the first USN to complete the binding operation with the first UE.
  • the first NSN allocates IP addresses to the first UE and the first USN, and the IP addresses are unique and unchanged within the first MEC domain. Then, mutual authentication is completed between the first NSN and the first UE.
  • mutual authentication For specific authentication methods, for example, refer to the authentication methods in the 3GPP TS23.501 standard, 3GPP TS33.501 standard, 3GPP TS33.535 standard, and 3GPP TS 23.303 standard. , this application will not repeat them.
  • both the first USN and the first UE obtain a twin-globally unique temporary user identity (twin-globally unique temporary identity, TWIN-GUTI), and the TWIN-GUTI identity includes the ID of the first USN and the first UE. IP address. Therefore, through the TWIN-GUTI identifier, the first USN obtains the IP address of the first UE, and the first UE obtains the IP address of the first USN. After the first USN and the first UE complete the authentication, the binding between the first USN and the first UE is completed, so that the first USN can provide the first UE with the service subscribed by the first UE.
  • TWIN-GUTI twin-globally unique temporary identity
  • the first USN needs to communicate data during the process of providing services for the first UE.
  • the first NSN is the first USN and the first UE Communication between planning communication path.
  • the first NSN has a global network topology view in the first MEC domain, that is, the first NSN can perceive the connection relationship between each device and node in the first MEC domain, therefore, the first NSN can be in the first USN and An optimal transmission path is planned between the first UEs.
  • the first NSN can specify a specific path according to requirements such as bandwidth, delay, and constraint conditions; when there are multiple reachable routes in the network, it can be based on the minimum delay, the fewest number of hops, the maximum bandwidth, or load balancing. Conditions, choose the most suitable transmission path.
  • the communication path planned by the first NSN between the first USN and the first UE may be referred to as a first path.
  • NSN complex path computation
  • the topology of the network changes dynamically, and the calculation of the communication path requires powerful computing support.
  • NSN is deployed in the edge data center. Compared with routers, it has powerful computing power. At the same time, it has real-time topology in the MEC domain, which can calculate the optimal path more quickly and accurately.
  • the network service node calculates a first target number based on the first path, where the first target number is used to calculate an egress port number for forwarding a data packet by a forwarding device on the first path.
  • the remainder system RNS may be used to implement data forwarding in the first path.
  • the first NSN may acquire a group of relatively prime arrays, and the number of numbers included in the array is equal to the number of forwarding devices included in the first MEC domain.
  • the forwarding devices in this domain are devices for forwarding data other than UE, NSN and USN, such as routers, base stations and gateways.
  • the first NSN allocates the numbers in the coprime array to the forwarding devices in the first MEC domain, each forwarding device allocates a number, and sends the numbers allocated by each forwarding device to the corresponding forwarding device for storage. After the numbers in the co-prime array are assigned to the forwarding device, they may be called the numbers of the forwarding device.
  • the first NSN plan After the first NSN plan obtains the first path between the first USN and the first UE, the number of each forwarding device in the first path and the egress port number of the data forwarded by each forwarding device can be obtained.
  • the first path may be a downlink transmission path starting from the first USN and ending with the first UE.
  • the first NSN can obtain two arrays, one array is an array composed of the numbers of each forwarding device in the first path, referred to as the downlink number array, and the other array is the forwarding device forwarding the first USN to the first UE
  • the array formed by the outbound port numbers of the data to be sent (may be referred to as downlink data) is referred to as an array of downlink ports for short.
  • the first NSN can calculate a target number based on the downlink number array and the downlink port array.
  • the target number can be called a downlink target number, and the downlink target number is the first target number in S502 above.
  • the remainder obtained by taking the remainder of the number of any one of the forwarding devices from the downlink target number is the corresponding outbound port number of the certain device in the downlink port array. Based on this characteristic, the downlink target number can be used to calculate the The outbound port number through which the forwarding device on the first path forwards downlink data.
  • the first path may be an uplink transmission path starting from the first UE and ending with the first USN.
  • the first NSN can obtain two arrays, one array is an array composed of the numbers of each forwarding device in the first path, referred to as the uplink number array, and the other array is the forwarding device forwarding the first UE to the first
  • An array of egress port numbers for data sent by the USN (which may be called uplink data) is referred to as an array of uplink ports for short.
  • the first NSN can calculate a target number based on the uplink number array and the uplink port array.
  • the target number can be called an uplink target number
  • the uplink target number is the first target number in S502 above.
  • the remainder of the uplink target number obtained by subtracting the serial number of any one of the forwarding devices is the corresponding outbound port number of the certain device in the uplink port array. Based on this characteristic, the uplink target number can be used to calculate the The forwarding device on the first path forwards the outgoing port number of the uplink data packet, and the total number of port numbers of the forwarding device is smaller than the serial number of the forwarding device.
  • the forwarding devices included in the uplink and downlink transmission paths are the same.
  • the forwarding device included in the uplink transmission path is different from the forwarding device included in the downlink transmission path, that is, the uplink data is transmitted through a certain path, and the downlink data is transmitted through another path.
  • the method of calculating the number of corresponding targets is the same.
  • the specific calculation method is as follows:
  • the number array is ⁇ m1,m2,m3,...,mN ⁇
  • the port array is ⁇ x1,x2,x3,...,xN ⁇
  • M m1*m2*m3*...*mN; that is, M is the product of all numbers in the numbered array;
  • Li (1/Mi)%mi; Li is that the reciprocal of Mi obtains the remainder of mi;
  • X (L1*M1*x1+L2*M2*x2+...+LN*MN*xN)%M; X is obtained by taking the remainder of M from the sum of all Li*Mi*mi, and this X is the above-mentioned requirement Calculated first target number.
  • the network service node sends the first target number to the ingress forwarding device, the ingress forwarding device is the next-hop device of the device at the starting point in the first path, and the first target number is used to add to the ingress forwarding device In the data sent to the end device of the first path.
  • the first NSN calculates the first target number, it sends the first target number to the next-hop device of the device at the starting point in the first path, and the next-hop device is the first Ingress forwarding device for the path.
  • the ingress forwarding device and the egress forwarding device are relative terms.
  • the next-hop forwarding device of the first USN in the first path is the ingress forwarding device, and the last-hop forwarding device of the first UE
  • the hop forwarding device is an egress forwarding device; if the first path is the above-mentioned uplink transmission path, the next hop forwarding device of the first UE is an ingress forwarding device, and the last hop forwarding device of the first USN is an egress forwarding device.
  • the next-hop forwarding device of the first USN in the downlink transmission path is the last hop of the first USN in the uplink transmission path.
  • the forwarding device at the last hop of the first UE in the downlink transmission path is the forwarding device at the next hop of the first UE in the uplink transmission path.
  • forwarding devices included in the planned first path include forwarding device 1 , forwarding device 2 and forwarding device 3 .
  • forwarding device 1 is an ingress forwarding device
  • forwarding device 3 is an egress forwarding device
  • forwarding device 3 is an ingress forwarding device
  • forwarding device 1 is an egress forwarding device.
  • the first NSN In addition to sending the first target to the ingress forwarding device of the first path, the first NSN also sends the IP addresses of the first UE and the first USN to the ingress forwarding device. After receiving the first target number, the IP addresses of the first UE and the first USN, the ingress forwarding device saves these information for subsequent data forwarding.
  • the first NSN encapsulates the first target number, the IP address of the first UE, and the first USN into a format of a data packet header and sends it to the ingress forwarding device. Indicate the source address and destination address in the packet header.
  • the data packet header may be referred to as an RNS header.
  • the target number sent by the first NSN to the ingress forwarding device of the first path is the above-mentioned uplink target number, and indicates that the source address and destination address associated with the uplink target number are respectively The address of the first UE and the address of the first USN.
  • the target number sent by the first NSN to the ingress forwarding device of the first path is the above-mentioned downlink target number, indicating that the source address and destination address associated with the downlink target number are respectively the first USN address and the address of the first UE.
  • Table 1 For ease of understanding, refer to Table 1.
  • the ingress forwarding device of the above-mentioned first path receives the data to be forwarded (including data packets or control instruction messages, etc.), it finds the corresponding target number in the local memory according to the source address and destination address in the data, that is, the above-mentioned first The target number, then, add the first target number to the data, for example, add it to the header of the data packet or the header of the command message, and calculate the output port number of the data based on the first target number, then, Send the data with the added destination number to the next-hop forwarding device from the port corresponding to the outbound port number.
  • the data to be forwarded including data packets or control instruction messages, etc.
  • the subsequent forwarding device after receiving the data, obtains the first target number in the data, calculates the output port number of the data based on the first target number, and then sends the data from the port corresponding to the output port number Forward the device to the next hop.
  • the egress forwarding device calculates the outbound port number based on the first target number in the data, and removes the first target number from the data, and then uses the outbound port number corresponding to the outbound port number Port forwarding removes data for the first target number.
  • the first NSN may simultaneously plan an uplink transmission path and a downlink transmission path between the first UE and the first USN; or, optionally, after the first UE is bound to the first USN, the first NSN may only plan an uplink transmission path from the first UE to the first USN; or, optionally, between the first UE and the first USN After the USNs are bound, the first NSN may only plan a downlink transmission path between the first USN and the first UE.
  • FIG. 7 shows a schematic diagram of a network architecture in an MEC domain. It can be seen that the numbers of the forwarding devices are mutually prime values, and each forwarding device includes multiple communication ports. Communication ports have corresponding port numbers.
  • NSN1 network service node 1
  • USN1 and UE1 can see two paths from USN1 to UE1 according to the global view in the MEC domain (in the actual network, there may be more), the first One path is from forwarding device 9 ⁇ forwarding device 4 ⁇ forwarding device 5; the second path is from forwarding device 9 ⁇ forwarding device 7 ⁇ forwarding device 11 ⁇ forwarding device 17 ⁇ forwarding device 4 ⁇ forwarding device 5; from delay If the angle with the smallest or smallest tune is used for planning, the first path is selected, so as to plan the routing path. Then, according to the number of the forwarding device in the first path and each output port number, the number of destinations is calculated as 81. The specific calculation process is as follows:
  • NSN1 After calculating the target number 81, NSN1 sends the 81, the source address (the address of USN1) and the destination address (the address of UE1) associated with the 81 to the ingress forwarding device (the forwarding device 9).
  • the data packet After receiving the data packet from USN1 at the forwarding device 9, the data packet can be parsed, and the source address of the data packet is known as the address of USN1, and the destination address is the address of UE1, and the corresponding target number 81 is found locally, and then, Add the target number 81 to the packet header. Moreover, the forwarding device calculates the outgoing port number of the data packet based on the target number 81. Specifically, the target number 81 is used to perform a remainder operation on the number 9 of the forwarding device 9 to obtain a remainder of 0, and the 0 is the data packet The outgoing port number of the packet. Then, the forwarding device 9 forwards the data packet carrying the target number 81 from port 0.
  • the data packet forwarded by the port 0 of the forwarding device 9 is transmitted to the forwarding device 4, and the forwarding device 4 receives the data packet, obtains the target number 81 in the header of the data packet, and uses the target number 81 to number 4 of the forwarding device 4
  • the remainder 1 is obtained by performing the remainder operation, and the 1 is the outgoing port number of the data packet. Then, the forwarding device 4 repackages the data packet and forwards it out through the port 1 .
  • the data packet forwarded by the port 1 of the forwarding device 4 is transmitted to the forwarding device 5, and the forwarding device 5 receives the data packet, obtains the target number 81 in the header of the data packet, and uses the target number 81 to number 5 of the forwarding device 5
  • the remainder 1 is obtained by performing the remainder operation, and the 1 is the outgoing port number of the data packet.
  • the forwarding device 5 removes the target number 81 from the header of the received data packet and then forwards it to UE1 through port 1.
  • the network service node 1 plans the transmission path from UE1 to USN1 from forwarding device 5 ⁇ forwarding device 4 ⁇ forwarding device 9 according to the global view in the MEC domain. Then, according to the number of the forwarding device in the path and the number of each output port, the number of destinations is calculated as 100.
  • the specific calculation process is as follows:
  • NSN1 After calculating the target number 100, NSN1 sends the 100, the source address (the address of UE1) and the destination address (the address of USN1) associated with the 100 to the ingress forwarding device (the forwarding device 5).
  • the data packet can be parsed, and the source address of the data packet is learned to be the address of UE1, and the destination address is the address of USN1. Therefore, the corresponding target number 100 is found locally, and then , add the target number 100 to the packet header. And, the forwarding device calculates the outbound port number of the data packet based on the target number 100. Specifically, the number 5 of the forwarding device 5 is subtracted by using the target number 100 to obtain a remainder of 0, and the 0 is the data packet The outgoing port number of the packet. Then, the forwarding device 5 forwards the data packet carrying the target number 100 from port 0.
  • the data packet forwarded by port 0 of the forwarding device 5 is transmitted to the forwarding device 4, and the forwarding device 4 receives the data packet, obtains the target number 100 in the header of the data packet, and uses the target number 100 to number 4 of the forwarding device 4
  • the remainder 0 is obtained by performing the remainder operation, and the 0 is the outgoing port number of the data packet. Then, the forwarding device 4 repackages the data packet and forwards it through port 0.
  • the data packet forwarded by port 0 of the forwarding device 4 is transmitted to the forwarding device 9, and the forwarding device 9 receives the data packet, obtains the target number 100 in the header of the data packet, and uses the target number 100 to number 9 of the forwarding device 9
  • the remainder 1 is obtained by performing the remainder operation, and the 1 is the outgoing port number of the data packet.
  • the forwarding device 9 removes the target number 100 from the header of the received data packet and forwards it to USN1 from port 1.
  • the communication processing method provided by the present application described in FIG. 7 above is described as an example of data packet transmission, but the communication processing method is not limited to the use of data packet communication, and it can also be used in the case of information communication such as control commands. Use, the communication processing method provided in this application does not limit the type of information communicated.
  • the forwarding devices included in the uplink transmission path and the downlink transmission path between USNs may be different, that is, the uplink transmission path and the downlink transmission path may be different paths.
  • the first NSN may re-plan the communication between the first UE and the first USN.
  • the communication path obtains the second path; then, calculate the second target number based on the second path, and send the second target number to the ingress forwarding device of the second path, and the second target number is used to calculate the second target number on the second path
  • the egress port number of the data forwarded by the forwarding device; the second destination number is used to add to the data sent by the ingress forwarding device to the terminal device of the second path.
  • the first NSN can re-plan the connection between the first UE and the first USN. communication path.
  • the switching of the access device connected by the first UE in the first MEC domain may be, for example, switching the base station connected by the first UE in the first MEC domain from the first base station to the second base station, and so on.
  • the first NSN plans the above-mentioned second path, it also calculates the second target number corresponding to the second path, and then sends the second target number to the ingress forwarding device of the second path, etc.
  • the communication processing method shown in FIG. 5 please refer to the above The description of the communication processing method shown in FIG. 5 will not be repeated here.
  • the ingress forwarding device of the second path is the same device as the ingress forwarding device of the first path, for example, when the access device of the first UE is handed over, the first USN The next-hop device of a UE does not change.
  • the forwarding device in the middle of the first path fails, but the next-hop device of the first UE or the first USN does not change, and so on. Then, in these cases, after receiving the second target number, the ingress forwarding device of the second path may replace the locally stored first target number with the second target number.
  • the embodiment of the present application can reduce the probability of communication interruption between the first UE and the first USN, and improve the communication performance of the entire communication network.
  • the network service node NSN has a global network topology view, and can specify a specific path according to bandwidth, delay, constraint conditions, etc., to achieve functions such as traffic engineering, Therefore, the communication path between the UE and the USN can be quickly planned.
  • the communication processing method of the present application does not require a routing table, which avoids the problem of routing table expansion caused by traffic surges; and the complex path calculation is implemented by NSN, which reduces the burden on forwarding devices compared to existing MPLS and SR , and greatly reduce the cumbersome configuration.
  • the uplink transmission path must be from the UE to its USN, and the downlink transmission path must be from the USN to its corresponding UE. Therefore, for uplink and downlink data, when the UE and its USN are initially bound Timing, the NSN performs route calculation between UE and USN, and sends the corresponding target number to the ingress forwarding device of the communication path. Using the routing scheme of the OpenFlow or KeyFlow protocol, whenever a new data packet arrives at the ingress router, it needs to trigger a pakcket-in message, throw the data packet to the controller, and the controller will re-plan the route.
  • the processing burden of the NSN can be greatly reduced, and the performance of the NSN can be improved.
  • it since there is no need to calculate the communication path in real time, it can also reduce the signaling communication burden and data transmission delay, and improve data transmission efficiency.
  • the ingress router when the ingress router performs data forwarding, it still needs to look up the table to obtain the output port number instead of calculating the port number through the number of destinations. Therefore, compared with this, this application At the ingress forwarding device, the outbound port number of the data is calculated based on the number of targets, and there is no need to look up the table to find out the outbound port number, thereby solving the problem of excessive storage resource occupation caused by the expansion of the routing table or flow table.
  • a modified-field action message needs to be sent to the ingress router to instruct the ingress router to add the target number to the packet header, and a modified-field action message needs to be sent to the egress router to indicate the egress router
  • the router removes the target number of the data packet header, which is a cumbersome process and occupies communication resources.
  • this application does not need to perform these two steps, which simplifies the operation process and saves communication resources.
  • the communication processing method of this application meets the requirements of more distributed, dynamic, and short-distance/short-hop data forwarding in the traffic model centered on distributed DC/MEC in the future, and is perfectly combined with the distributed MEC architecture, which is better than the current
  • the mainstream SR solution and the combination of KeyFlow and SDN have simpler configuration and simpler protocols, which can greatly reduce deployment and maintenance costs and improve deployment and maintenance efficiency.
  • each device includes a corresponding hardware structure and/or software module for performing each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.
  • the embodiments of the present application may divide the device into functional modules according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in this embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 8 shows a schematic diagram of a possible logical structure of the device, which may be the device where the above-mentioned network service node is located (such as the server where the network service node is located, the chip or processing systems, etc.).
  • the apparatus 800 includes a planning unit 801 , a computing unit 802 and a sending unit 803 . in:
  • the planning unit 801 is configured to plan a communication path between the user service node and the user equipment to obtain a first path when the authentication between the user service node and the user equipment is perceived, and the user service node is used for the user equipment to provide services;
  • a calculation unit 802 configured to calculate a first target number based on the first path, where the first target number is used to calculate the output port number of the data forwarded by the forwarding device on the first path;
  • the sending unit 803 is configured to send the first target number to an ingress forwarding device, the ingress forwarding device is the next-hop device of the device at the starting point in the first path, and the first target number is used to add to the ingress forwarding device In the data sent to the end device of the first path.
  • the user service node and the user equipment belong to nodes covered by the same edge cloud.
  • the planning unit 801 is further configured to plan a communication between the user equipment and the user service node when the first path cannot realize the communication between the user service node and the user equipment.
  • the communication path of obtains the second path;
  • the calculation unit 802 is further configured to calculate a second target number based on the second path, and the second target number is used to calculate the output port number of the data forwarded by the forwarding device on the second path;
  • the sending unit 803 is further configured to send the second target number to the ingress forwarding device, where the second target number is used to add to the data sent by the ingress forwarding device to the terminal device of the second path.
  • the first path is a path from the user equipment to the user service node;
  • the ingress forwarding device is an access device for connecting the user equipment to a communication network;
  • the situation that the first path cannot realize the communication between the user service node and the user equipment includes:
  • the access device for accessing the user equipment to the communication network is changed.
  • FIG. 9 shows a schematic diagram of a possible logical structure of the device, which may be the above-mentioned ingress forwarding device, a chip or a processing system of the ingress forwarding device, etc.
  • the device 900 includes a receiving unit 901 , a writing unit 902 , a computing unit 903 and a sending unit 904 . in:
  • the receiving unit 901 is configured to receive a first target number, the first target number is used to forward the communication data between the user service node and the user equipment according to a first path, the first path is between the user service node and the user equipment
  • the user service node is used to provide services for the user equipment
  • the receiving unit 901 is further configured to receive first data, and find the first target number based on the first data;
  • a writing unit 902 configured to write the first target number into the first data to obtain second data
  • a calculating unit 903 configured to calculate the port number based on the first target number
  • a sending unit 904 configured to send the second data through the egress port number.
  • the receiving unit 901 is also configured to:
  • the second target number is used to forward the communication data between the user service node and the user equipment according to the second path, and the second The path is obtained through planning when the first path cannot realize the communication between the user service node and the user equipment.
  • FIG. 10 is a schematic diagram of a possible hardware structure of the device provided by the present application.
  • the device may be the device where the network service node in the method described in the above embodiment is located (for example, the server, chip or processing device where the network service node is located. system, etc.).
  • the device 1000 includes: a processor 1001 , a memory 1002 and a communication interface 1003 .
  • the processor 1001 , the communication interface 1003 and the memory 1002 may be connected to each other or through a bus 1004 .
  • the memory 1002 is used for storing computer programs and data of the device 1000, and the memory 1002 may include but not limited to random access memory (random access memory, RAM), read-only memory (read-only memory, ROM), and Erase programmable read-only memory (erasable programmable read only memory, EPROM) or portable read-only memory (compact disc read-only memory, CD-ROM), etc.
  • random access memory random access memory
  • ROM read-only memory
  • EPROM erasable programmable read only memory
  • portable read-only memory compact disc read-only memory, CD-ROM
  • the communication interface 1003 includes a sending interface and a receiving interface, and there may be multiple communication interfaces 1003, which are used to support the device 1000 to communicate, such as receiving or sending data or messages.
  • the processor 1001 may be a central processing unit, a general processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, a hardware component or any combination thereof.
  • the processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and the like.
  • the processor 1001 may be configured to read the program stored in the above-mentioned memory 1002, so that the apparatus 1000 executes the operations performed by the NSN in any one of the communication processing methods described above in FIG. 5 and its possible embodiments.
  • the processor 1001 may be configured to read the program stored in the memory 1002, and perform the following operations:
  • FIG. 11 is a schematic diagram of a possible hardware structure of the device provided by the present application.
  • the device may be the ingress forwarding device, the chip or the processing system of the ingress forwarding device in the method described in the above embodiment.
  • the device 1100 includes: a processor 1101 , a memory 1102 and a communication interface 1103 .
  • the processor 1101 , the communication interface 1103 and the memory 1102 may be connected to each other or through a bus 1104 .
  • the memory 1102 is used to store computer programs and data of the device 1100, and the memory 1102 may include but not limited to random access memory (random access memory, RAM), read-only memory (read-only memory, ROM), and Erase programmable read-only memory (erasable programmable read only memory, EPROM) or portable read-only memory (compact disc read-only memory, CD-ROM), etc.
  • random access memory random access memory
  • ROM read-only memory
  • EPROM erasable programmable read only memory
  • portable read-only memory compact disc read-only memory, CD-ROM
  • the communication interface 1103 includes a sending interface and a receiving interface, and there may be multiple communication interfaces 1103, which are used to support the device 1100 to communicate, for example, to receive or send data or messages.
  • the processor 1101 may be a central processing unit, a general processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, a hardware component or any combination thereof.
  • the processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and the like.
  • the processor 1101 may be configured to read the program stored in the memory 1102, so that the apparatus 1100 executes the operations performed by the ingress forwarding device in any one of the communication processing methods described above in FIG. 5 and its possible embodiments.
  • the processor 1101 may be configured to read the program stored in the memory 1102, and perform the following operations:
  • the first target number is used to forward the communication data between the user service node and the user equipment according to a first path, the first path is completed between the user service node and the user equipment
  • the user service node is used to provide services for the user equipment
  • receiving the first data through the communication interface and finding the first target number based on the first data
  • writing the first target number into second data is obtained from the first data
  • a port number is calculated based on the first target number
  • the second data is sent out from the output port number through the communication interface.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and the computer program is executed by a processor to implement the above-mentioned any embodiment in FIG. 5 and its possible method embodiments.
  • the operations performed by the NSN in the above method; or, the computer program is executed by the processor to implement the operations performed by the ingress forwarding device in the method described in any one of the above-mentioned FIG. 5 and its possible method embodiments.
  • the embodiment of the present application also provides a computer program product.
  • the computer program product is read and executed by a computer, the operations performed by the NSN in the method described in any of the above-mentioned FIG. 5 and its possible method embodiments will be or, the operations performed by the ingress forwarding device in the method described in any one of the foregoing FIG. 5 and its possible method embodiments will be executed.
  • the communication path between the two is planned, and the communication between the two is realized based on the method of the remainder system. Because the UE and its USN are bound, the uplink transmission path must be from the UE to its USN, and the downlink transmission path must be from the USN to its corresponding UE. Therefore, for uplink and downlink data, when the UE and its USN are initially bound, The route calculation between the UE and the USN is performed by the NSN, and the corresponding target number is delivered to the ingress forwarding device of the communication path.
  • the target number can be reused, and subsequent calculations do not need to be frequent unless the routing conditions change; unlike existing solutions In the OpenFlow or KeyFlow protocol, whenever a new data packet arrives at the ingress router, it is necessary to trigger a pakcket-in message, throw the data packet to the controller, and the controller re-plans the route. That is, in this application, the processing burden of the NSN can be greatly reduced, and the performance of the NSN can be improved. In addition, since there is no need to calculate the communication path in real time, it can also reduce the signaling communication burden and data transmission delay, and improve data transmission efficiency.
  • the communication processing method of this application meets the requirements of more distributed, dynamic, and short-distance/short-hop data forwarding in the traffic model centered on distributed DC/MEC in the future, and is perfectly combined with the distributed MEC architecture, which is better than the current
  • the mainstream SR solution and the combination of KeyFlow and SDN have simpler configuration and simpler protocols, which can greatly reduce deployment and maintenance costs and improve deployment and maintenance efficiency.
  • the communication processing method of the present application does not require a routing table, which avoids the problem of routing table expansion caused by the surge in traffic; and the complex path calculation is realized by NSN, which reduces the number of forwarding devices compared to existing MPLS and SR. Burden, and greatly reduce the cumbersome configuration.

Landscapes

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

Abstract

本申请实施例提供一种通信处理方法及相关设备，该方法包括：在感知用户服务节点和用户设备之间完成认证的情况下，规划该用户服务节点和该用户设备之间的通信路径得到第一路径，该用户服务节点用于为该用户设备提供服务；基于该第一路径计算第一目标数，该第一目标数用于计算该第一路径上的转发设备转发数据的出端口号；向入口转发设备发送该第一目标数，该入口转发设备为该第一路径中处于起点的设备的下一跳设备，该第一目标数用于添加到该入口转发设备发往该第一路径的终点设备的数据中。本申请能够减轻控制节点的处理负担，提高数据传输效率。

Description

通信处理方法及相关设备
本申请要求于2021年05月21日提交中国专利局、申请号为202110557277.4、申请名称为“通信处理方法及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，尤其涉及一种通信处理方法及相关设备。
背景技术
现有移动通信***都是以网络为中心，用户适应网络，即用户只能选择网络提供的功能，尤其是集中式的核心网提供的功能都是大颗粒度的，无法满足用户个性化需求。而用户越来越追求个性化服务，同时万物互联带来终端的类型剧增，需要按需定制的功能，比如不移动的终端，就不需要寻呼，而有些物联终端不需要话音功能等。
现有集中式的核心网网元(移动性管理，会话管理，用户数据管理，策略管理)实体一般能处理大量的用户，且集中部署，存在单点失效和分布式拒绝服务攻击(distributed deny of service，DDoS)的风险，造成巨大财产和声誉损失。用户个人数据缺乏可信和安全机制，且难以满足越来越严格的数据隐私保护趋势和需求。为解决以上问题，提出了以用户为中心的网络(user-centric network，UCN)架构。在UCN架构中，每一个用户设备(user equipment，UE)都有一个自己的用户服务节点(network service node，USN)，USN由网络服务节点(network service node，NSN)生成，根据需要，USN可以随用户动态生成和迁移，实现以用户为中心的网络架构设计。
未来边缘云将广泛部署，从而使得流量以分布式数据中心(data center，DC)/多接入边缘计算(mulit-access edge computing，MEC)为中心，同时接入终端的数量激增导致流量以几何级数的趋势增长，未来流量将呈现分布式和本地为主的特征，与传统的经过接入、汇聚和集中，再骨干传输到核心网关的流量模式不同。这导致终端与核心网关之间的数据转发更加分布式、动态化、短距离和短跳数，而流量激增导致路由表膨胀，因此需要研究适应这些新需求的路由方法。
发明内容
本申请实施例公开了一种通信处理方法及相关设备，能够适用于数据转发分布式、动态化、短距离和短跳数的以分布式DC/MEC为中心的网络架构，且可以有效避免因流量激增而导致路由表膨胀带来的问题，且可以减少复杂的配置，减轻控制节点的处理负担，提高数据传输效率。
第一方面，本申请提供一种通信处理方法，该方法包括：
在感知用户服务节点和用户设备之间完成认证的情况下，规划该用户服务节点和该用户设备之间的通信路径得到第一路径，该用户服务节点用于为该用户设备提供服务；
基于该第一路径计算第一目标数，该第一目标数用于计算该第一路径上的转发设备转发数据的出端口号；
向入口转发设备发送该第一目标数，该入口转发设备为该第一路径中处于起点的设备的下一跳设备，该第一目标数用于添加到该入口转发设备发往该第一路径的终点设备的数据中。
可选的，该用户服务节点和该用户设备属于同一个边缘云下覆盖的节点。
本申请中，在用户设备(user equipment，UE)和用户服务节点USN绑定后，规划该两者之间的通信路径，并基于余数***的方法来实现该两者的通信。因为UE和其USN是绑定的，上行传输路径一定是从UE到其USN，下行传输路径一定是从USN到其对应的UE，因此对于上下行数据，在UE和其USN初始绑定时，由NSN进行UE和USN之间的路由计算，并给通信路径的入口转发设备下发对应的目标数，该目标数可以重复使用，后续不需要频繁计算，除非路由条件改变；不像现有方案中的OpenFlow或KeyFlow协议，每当一个新数据包到达入路由器时，都需要触发pakcket-in消息，将该数据包扔给控制器，由控制器重新规划路由。即在本申请中，可以极大减少NSN的处理负担，提升NSN的性能，另外，由于无需实时计算通信路径，因此还可以减少信令通信负担和降低数据传输时延，提高数据传输效率。
其次，本申请的通信处理方法满足未来以分布式DC/MEC为中心的流量模型中数据转发更加分布式、动态化、短距/短跳数的需求，与分布式MEC架构完美结合，比目前主流的SR方案和KeyFlow结合SDN的方案配置更简单，协议也更简单，可以极大降低部署和维护成本，提高部署和维护效率。
再者，本申请的通信处理方法中无需路由表，避免了因流量激增导致的路由表膨胀问题；且复杂的路径计算由NSN集中实现，相比于现有的MPLS和SR，降低了转发设备负担，以及极大减少了繁琐的配置。
一种可能的实施方式中，该方法还包括：
在该第一路径无法实现该用户服务节点和该用户设备之间的通信的情况下，规划该用户设备和该用户服务节点之间的通信路径得到第二路径；
基于该第二路径计算第二目标数，该第二目标数用于计算该第二路径上的转发设备转发数据的出端口号；
向该入口转发设备发送该第二目标数，该第二目标数用于添加到该入口转发设备发往该第二路径的终点设备的数据中。
本申请中，如果原先规划好的UE和USN之间的通信路径无法通信，可以重新规划新的路径，可以避免数据通信中断，提高通信网络的可靠性和性能。
一种可能的实施方式中，该第一路径为从该用户设备到该用户服务节点的路径；该入口转发设备为将该用户设备接入通信网络的接入设备；该第一路径无法实现该用户服务节点和该用户设备之间的通信的情况，包括：将该用户设备接入该通信网络的接入设备发生变更。
本申请中，在本申请中当用户设备UE的接入设备切换的情况下，可以及时感知并规划新的通信路径，保证UE与USN之间正常的通信。
第二方面，本申请提供一种通信处理方法，该方法包括：
接收第一目标数，该第一目标数用于按照第一路径转发用户服务节点和用户设备之间的通信数据，该第一路径为在该用户服务节点和该用户设备之间完成认证的情况下规划得到，该用户服务节点用于为该用户设备提供服务；
接收第一数据，并基于该第一数据查找到该第一目标数；
将该第一目标数写入该第一数据得到第二数据；
基于该第一目标数计算出端口号，将该第二数据从该出端口号发送出去。
本申请中，该通信处理方法的执行主体可以是上述第一路径中的入口转发设备，入口转发设备可以在UE和USN绑定后，接收到网络服务节点发送的上述第一目标数，在需要通过第一路径转发UE和USN之间的数据时，将该第一目标数添加到需要转发的数据中，并基于 第一目标数计算数据转发的出端口来将数据转发出去，无需路由表查表，避免了因流量激增导致的路由表膨胀问题。也不需要像现有方案中的OpenFlow或KeyFlow协议的方案，每当一个新数据包到达入路由器时，都需要触发pakcket-in消息，将该数据包扔给控制器，由控制器重新规划路由，从而也减轻了入口准发设备的处理负担。
另外，在现有的采用OpenFlow或KeyFlow协议的路由方案中，入口路由器进行数据转发的时候，仍然需要查表获取出端口号，而不是通过目标数来计算出端口号，因此，相比于现有的方案，本申请在入口转发设备就通过目标数计算数据的出端口号，无需查表来查找出端口，从而解决了路由表或流表等膨胀导致的存储资源占用过多等问题。
一种可能的实施方式中，该方法还包括：接收第二目标数，将本地存储的该第一目标数替换为该第二目标数；该第二目标数用于按照第二路径转发用户服务节点和用户设备之间的通信数据，该第二路径为在该第一路径无法实现该用户服务节点和该用户设备之间的通信的情况下规划得到。
本申请中，UE和USN之间的通信路径重新规划后，入口转发设备会接收到第二目标数，然后替换原来路径对应的第一目标数，从而保证UE和USN之间的数据通信可以正常进行无中断。
第三方面，本申请提供一种通信处理装置，该装置包括：
规划单元，用于在感知用户服务节点和用户设备之间完成认证的情况下，规划该用户服务节点和该用户设备之间的通信路径得到第一路径，该用户服务节点用于为该用户设备提供服务；
计算单元，用于基于该第一路径计算第一目标数，该第一目标数用于计算该第一路径上的转发设备转发数据的出端口号；
发送单元，用于向入口转发设备发送该第一目标数，该入口转发设备为该第一路径中处于起点的设备的下一跳设备，该第一目标数用于添加到该入口转发设备发往该第一路径的终点设备的数据中。
一种可能的实施方式中，该用户服务节点和该用户设备属于同一个边缘云下覆盖的节点。
一种可能的实施方式中，该规划单元，还用于在该第一路径无法实现该用户服务节点和该用户设备之间的通信的情况下，规划该用户设备和该用户服务节点之间的通信路径得到第二路径；
该计算单元，还用于基于该第二路径计算第二目标数，该第二目标数用于计算该第二路径上的转发设备转发数据的出端口号；
该发送单元，还用于向该入口转发设备发送该第二目标数，该第二目标数用于添加到该入口转发设备发往该第二路径的终点设备的数据中。
一种可能的实施方式中，该第一路径为从该用户设备到该用户服务节点的路径；该入口转发设备为将该用户设备接入通信网络的接入设备；
该第一路径无法实现该用户服务节点和该用户设备之间的通信的情况，包括：
将该用户设备接入该通信网络的接入设备发生变更。
第四方面，本申请提供一种通信处理装置，该装置包括：
接收单元，用于接收第一目标数，该第一目标数用于按照第一路径转发用户服务节点和用户设备之间的通信数据，该第一路径为在该用户服务节点和该用户设备之间完成认证的情况下规划得到，该用户服务节点用于为该用户设备提供服务；
该接收单元，还用于接收第一数据，并基于该第一数据查找到该第一目标数；
写入单元，用于将该第一目标数写入该第一数据得到第二数据；
计算单元，用于基于该第一目标数计算出端口号；
发送单元，用于将该第二数据从该出端口号发送出去。
一种可能的实施方式中，该接收单元，还用于：
接收第二目标数，将本地存储的该第一目标数替换为该第二目标数；该第二目标数用于按照第二路径转发用户服务节点和用户设备之间的通信数据，该第二路径为在该第一路径无法实现该用户服务节点和该用户设备之间的通信的情况下规划得到。
第五方面，本申请提供一种通信处理装置，该装置可以包括处理器和存储器，用于实现上述第一方面及其可能的实施方式描述的通信处理方法。该存储器与处理器耦合，处理器执行存储器中存储的计算机程序时，可以实现上述第一方面或第一方面任一种可能的实现方式所述的方法。该装置还可以包括通信接口，通信接口用于该装置与其它装置进行通信，示例性的，通信接口可以是收发器、电路、总线、模块或其它类型的通信接口。该通信接口包括接收接口和发送接口，该接收接口用于接收消息，该发送接口用于发送消息。
在一种可能的实现中，该装置可以包括：
存储器，用于存储计算机程序；
处理器，在感知用户服务节点和用户设备之间完成认证的情况下，规划该用户服务节点和该用户设备之间的通信路径得到第一路径，该用户服务节点用于为该用户设备提供服务；基于该第一路径计算第一目标数，该第一目标数用于计算该第一路径上的转发设备转发数据的出端口号；通过通信接口向入口转发设备发送该第一目标数，该入口转发设备为该第一路径中处于起点的设备的下一跳设备，该第一目标数用于添加到该入口转发设备发往该第一路径的终点设备的数据中。
需要说明的是，本申请中存储器中的计算机程序可以预先存储也可以使用该装置时从互联网下载后存储，本申请对于存储器中计算机程序的来源不进行具体限定。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或连接，其可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。
第六方面，本申请提供一种通信处理装置，该装置可以包括处理器和存储器，用于实现上述第二方面及其可能的实施方式描述的通信处理方法。该存储器与处理器耦合，处理器执行存储器中存储的计算机程序时，可以实现上述第二方面或第二方面任一种可能的实现方式所述的方法。该装置还可以包括通信接口，通信接口用于该装置与其它装置进行通信，示例性的，通信接口可以是收发器、电路、总线、模块或其它类型的通信接口。该通信接口包括接收接口和发送接口，该接收接口用于接收消息，该发送接口用于发送消息。
在一种可能的实现中，该装置可以包括：
存储器，用于存储计算机程序；
处理器，通过通信接口接收第一目标数，该第一目标数用于按照第一路径转发用户服务节点和用户设备之间的通信数据，该第一路径为在该用户服务节点和该用户设备之间完成认证的情况下规划得到，该用户服务节点用于为该用户设备提供服务；通过通信接口接收第一数据，并基于该第一数据查找到该第一目标数；将该第一目标数写入该第一数据得到第二数据；基于该第一目标数计算出端口号，通过通信接口将该第二数据从该出端口号发送出去。
需要说明的是，本申请中存储器中的计算机程序可以预先存储也可以使用该装置时从互联网下载后存储，本申请对于存储器中计算机程序的来源不进行具体限定。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或连接，其可以是电性，机械或其它的形式，用 于装置、单元或模块之间的信息交互。
第七方面，本申请提供一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，该计算机程序被处理器执行以实现上述第一方面任意一项所述的方法；或者，该计算机程序被处理器执行以实现上述第二方面所述的方法。
第八方面，本申请提供一种计算机程序产品，当计算机程序产品在计算机上运行时，使得该计算机执行如上述第一方面任意一项所述的方法；或者，使得该计算机执行上述第二方面所述的方法。
可以理解地，上述提供的第三方面、第四方面、第五方面和第六方面所述的装置、第七方面所述的计算机存储介质以及第八方面所述的计算机程序产品均用于执行第一方面和第二方面中任一项所提供的方法。因此，其所能达到的有益效果可参考对应方法中的有益效果，此处不再赘述。
附图说明
下面将对本申请实施例中所需要使用的附图作介绍。
图1至图3所示为本申请实施例提供的场景示意图；
图4所示为本申请提供的网络架构与传统网络架构比较的示意图；
图5所示为本申请提供的通信处理方法的流程示意图；
图6所示为本申请提供的传输路径示意图；
图7所示为本申请提供的一种边缘云结构示意图；
图8和图9所示为本申请提供的装置的逻辑结构示意图；
图10和图11所示为本申请提供的装置的实体结构示意图。
具体实施方式
下面结合附图对本申请的实施例进行描述。
首先介绍一下本申请涉及到的余数***。
余数***(residue number system，RNS)基于中国余数定理(chineseremainder theorem，CRT)实现。该原理简单描述如下：
1、{m1,m2,m3,...,mN},是一组互质数组，N为大于1的整数；
2、{x1,x2,x3,...,xN}是一组整数数组；
3、任何小于M的任意整数X都可以在定义的余数***中表示为N个较小的整数的集合；
4、xi＝<X>mi，对xi可以由X通过对相应的mi进行取余而得到。在本申请下面的描述中，可以称该X为目标数。
边缘云是分布在网络边缘侧，提供实时数据处理和分析决策的小规模云数据中心。基于边缘云的优势，网络边缘云化成为必然趋势，边缘云和核心云(核心云为大型云服务数据中心)形成协同互补，边缘云更靠近用户，能够更好地支持对时延和数据隐私等有高要求的应用，适合网络功能的分布式部署。部署边缘云的场景可以示例性参见图1。
在图1中可以看到，整个***架构可以分为三层：终端层、边缘云层和核心云层。终端层的终端通过基站或无线接入点等接入设备接入到边缘云，该终端为用户设备(user equipment，UE)。边缘云层中的多个边缘云可以互相建立通信连接，该多个边缘云与核心云建立通信连接。不管是该多个边缘云还是核心云都可以提供应用服务(application service，APPs)。
基于上述图1所示的场景，可以设计得到用户为中心(user-centric network，UCN)的网 络架构，示例性地可以参见图2。图2示例性示出了一种UCN的网络架构示意图，可以看到边缘云上部署有网络服务节点(network service node，NSN)和用户服务节点(network service node，USN)，每一个用户设备UE都对应有一个自己的用户服务节点USN。用户服务节点USN可以为与其绑定的用户设备UE提供需要的服务。网络服务节点NSN可以为其所在的边缘云中的USN及其对应的终端等提供需要的服务。
示例性地，还可以参见图3，图3所示为另一个UCN网络架构的示意图。可以看到，UCN网络架构中核心云和和每个边缘云都部署有一个网络服务节点NSN，这些NSN之间可以互相通信。每个边缘云中还部署了一个或多个用户服务节点USN，每个USN与一个用户设备UE关联绑定。USN和UE之间通信的数据通过转发设备进行转发。该转发设备例如可以是接入设备、路由器、网关或者交换机等可以转发数据的设备，该接入设备例如为基站或无线接入点等等。
需要说明的是，上述网络服务节点NSN和用户服务节点USN可以是服务器中部署的应用服务软件。可选的，一个服务器或者一个服务器集群中可以部署多个该NSN和多个USN，或者，一个服务器或者一个服务器集群中部署一个NSN和一个或多个USN，或者，一个服务器或一个服务器集群部署一个NSN，每个USN也各自单独部署在一个服务器上等等。本申请对NSN或USN的具体部署不做限制。
一种可能的实施例中，每一个边缘云为一个多接入边缘计算(mulit-access edge computing，MEC)域，该边缘云下的节点和设备属于该MEC域内的节点和设备。
由于上述的UCN网络架构以分布式DC/MEC为中心，同时接入终端的数量激增导致流量的几何级数的增长，未来流量将呈现分布式和本地为主的特征，导致终端与核心网关之间的数据转发更加分布式、动态化、短距离以及短跳数，而流量激增导致路由表膨胀，因此，需要设计一种满足该UCN网络架构特性的数据通信路由规则。在此之前，先分析一下现有的几种路由规则。
例如，现有的经典的网际互联协议(internet protocol，IP)路由表方案，是沿路路由器通过查找路由表，确定转发出口及下一跳路由。但在面向未来网络的新流量模型时，存在以下的问题：随着终端数量的几何级数激增，会带来路由表膨胀问题。
又例如，现有的KeyFlow结合软件定义网络(software defined network，SDN)的方案，在OpenFlow控制器上部署KeyFlow应用程序，用于通过上述余数***RNS计算得到目标数及将该目标数下发。具体的，由入口边缘路由器，将数据包扔给控制器，控制器计算转发路径和该目标数，生成包括目标数的包头(该包头可以称为RNS头)，并下发给入口和出口边缘路由器；入口路由器为数据加上包括目标数的包头，并基于目标数沿路计算出端口，并转发；在出口边缘路由器，将包括目标数的包头剥离。
上述包括目标数的包头可以称为RNS头，该RNS头除了包括该目标数还可以包括数据包的源目的地址和目的地址等信息。KeyFlow结合SDN的方案的具体流程描述如下：
步骤1：来自自治域1的数据包进入入口边缘路由器，触发packet-in消息，将数据包发送OpenFlow控制器；KeyFlow应用程序从数据包中得到目的地址，基于实时网络拓扑，规划路由，规划结果为从路由器4->3->5到出口边缘路由器；进而基于RNS计算得到目标数为25；
步骤2：OpenFlow控制器生成包括25的RNS头，通过flow-mod信息发送给入口和出口边缘路由器，该入口和出口边缘路由器收到包头后增加一个新的流表，表示该数据包进入 KeyFlow域，执行基于该RNS头的路由；
步骤3：OpenFlow控制器发送modified-field action消息给入口边缘路由器，指示入口边缘路由器将RNS头写入数据包头；入口边缘路由器转发数据包到路由器4，25/4取余得1，则从1端口转发出去，到达路由器3，取余得1，从1端口转发出去，到路由器5，取余得0，从0端口转发出去，到达出口边缘路由器；
步骤4：OpenFlow控制器发送modified-field action消息给出口边缘路由器，指示出口边缘路由器将RNS头去掉。根据目的地址进一步转发。
该KeyFlow结合SDN的方案存在如下缺点：1.对SDN控制器，因为流量激增，短时流量多，动态变化，当把这些新的数据包都扔给控制器时，导致控制器性能急剧下降。同时还需要频繁更新沿路路由转发表，增加信令负担和延时。2.KeyFlow必须用Open-flow协议的packet-in功能来获得数据包的源和目的地址信息，需要多一步操作，耗费更多处理资源，且Open-flow协议较复杂，实现起来成本高。
又例如，多标签协议交换(multi-Protocol label switching，MPLS)及段路由(segment rout ing，SR)方案。该两种方案中，基于流量工程扩展的资源预留协议(resource reservation prot ocol-traffic engineering，RSVP-TE)通过内部网关协议(interior gateway protocols，IGP)泛洪，收敛后，每台设备获取每条路径的状态，再根据约束条件进行路径计算，然后逐跳发送报文，请求预留带宽和分配标签。SR是MPLS的改进方案，具有极大的潜力。SR-BE(best effort)是最短路径转发模型，由前缀标签或节点标签指导报文转发，不需要控制器。流量工程的段路由((segment routing-traffic engineering，SR-TE)需要控制器，控制器集中算路后，向隧道入节点发送一连串标签，用以控制转发路径。
结合标签分发协议(label distribution protocol，LDP)和RSVP-TE的优点形成SR-TE。具体的，1、去掉RSVP-TE的信令机制。协议机制复杂的根源就在于每一台设备都需要单独维护一套复杂的信令。但RSVP-TE通过扩展的IGP获取到路径信息后，会计算出一条合适的路径，然后通过发送RSVP-TE信令来建立隧道。因为有可能当前链路发生了变化，而收敛需要时间，可能正好发生在计算路径的时刻。所以必须有一个机制，使每条隧道在发送报文之前，再次进行路径的确认，并对带宽进行预留，这就是RSVP-TE信令的作用。究其原因，是因为RSVP-TE是分布式的架构，每台设备只能看到自己的状态，而如果需要知道其他地方的情况，就必须依靠信令机制去实现。但如果分布式架构中，增加一个集中控制的节点，统一进行路径计算和分发标签，就迎刃而解了。所以SR与SDN是天作之合。2、将LDP高效和负载分担引入到RSVP-TE。RSVP-TE在源端就确定好路径，而有时候有多条路都满足要求，但RSVP-TE不能进行负载分担。通过1)直接利用IGP去分配标签，扩展了IGP协议，通过IGP的信令直接携带标签信息，规避了流量黑洞。2)设置Node ID(全局标签)，可以单独标识一台设备，而且全局有效且唯一。这样就可以通过一个全局标识进行查表转发。3)设置Adjacent ID(邻接标签)。本地有效，有方向性，本地唯一标识了一条链路。这样实现选择特定路线的需求。
对于SR-TE，在需要负载分担的路段实现自由的负载分担模式，例如，上海到南京，有两条路径可自由选择；而在需要严谨选路的路段严格的进行路径指定，例如，南京到太原再到西安，避开南京到西安直达的拥塞路径。
但是上述MPLS和SR方案存在如下一些问题：1.RSVP-TE配置非常繁琐，协议复杂，无法大规模应用；2.SR-TE虽然相对RSVP-TE已经配置简化，但仍需要复杂的标签配置，协议也相对复杂。3.MPLS及SR更多应用在骨干网络。4.SR-TE的标签栈不能无限大，需要用 粘连标签来解决。
上述现有的路由规则的应用场景均为传统的三层网络架构，与UCN网络架构不同，为了便于理解，可以参见图4。图4示例性示出了三层网络架构和UCN网络架构的对比示意图。可以看到，UCN网络架构简化了经典网络架构的汇聚层，将汇聚层的环状网络改为树状网络，另外，UCN网络中边缘云将泛在化，大部分流量将在网络边缘转发及终结，从而使得流量以分布式DC/MEC为中心。
UCN网络架构中，接入终端的数量激增使得流量以几何级数的趋势增长，流量激增导致路由表膨胀，且未来流量将呈现分布式和本地为主的特征，终端与核心网关之间的数据转发更加分布式、动态化、短距离和短跳数，基于这些特性，若将上述现有的路由规则应用到UCN网络架构中则上述所描述的现有路由方案的缺陷会更加突出。因此，本申请提供了适用于UCN网络架构的通信处理方法，解决UCN网络架构中数据发送的路由问题。
参见图5，本申请提供的通信处理方法包括但不限于如下步骤：
S501、在感知用户服务节点和用户设备之间完成认证的情况下，规划该用户服务节点和该用户设备之间的通信路径得到第一路径，该用户服务节点用于为该用户设备提供服务。
在具体实施例中，该网络服务节点和用户服务节点分别为上述介绍的UCN网络架构中某个边缘云(或者说某个MEC域，为了便于描述称该某个MEC域为第一MEC域，下面以该第一MEC域为例来描述)的网络服务节点NSN和用户服务节点USN，为了便于后面的描述该网络服务节点NSN和用户服务节点USN分别称为第一NSN和第一USN。S501中的用户设备与第一USN绑定，为了便于后面的描述，该用户设备称为第一UE。
在第一MEC域内，用户服务节点都是由该第一MEC域内的网络服务节点第一NSN生成的。示例性地，以第一USN为例，在第一UE首次向其所在的第一MEC域内的第一NSN请求开通服务时，该第一NSN接收到第一UE的服务开通请求后，为该第一UE生成一个USN，该USN即为上述第一USN。
上述第一NSN生成第一USN后，参与并协助该第一USN与该第一UE完成绑定操作。示例性地，该第一NSN为该第一UE和该第一USN分配IP地址，该IP地址在该第一MEC域内唯一且不变。然后，第一NSN和第一UE之间互相完成认证，具体的认证方式例如可以参考3GPP TS23.501标准、3GPP TS33.501标准、3GPP TS33.535标准和3GPP TS 23.303标准等标准中的认证方式，本申请不做赘述。完成认证后，第一USN和第一UE均获得一个孪生全球唯一的用户临时标识(twin-globally unique temporary identity，TWIN-GUTI)，该TWIN-GUTI标识中包括该第一USN和第一UE的IP地址。因此，通过该TWIN-GUTI标识，第一USN获得了第一UE的IP地址，该第一UE获得了第一USN的IP地址。该第一USN与该第一UE完成认证后即完成了该第一USN与该第一UE之间的绑定，从而该第一USN可以为第一UE提供该第一UE订制的服务。
第一USN为第一UE提供服务的过程中需要进行数据的通信，在本申请中，第一USN和第一UE之间完成绑定后，第一NSN即为该第一USN和第一UE之间的通信规划通信路径。具体的，该第一NSN拥有第一MEC域内的全局网络拓扑视图，即第一NSN能够感知该第一MEC域内各个设备和节点之间的连接关系，因此，第一NSN可以在第一USN和第一UE之间规划出最优传输路径。
示例性地，第一NSN可以根据带宽、时延和约束条件等要求指定具体的路径；当网络中存在多条可达路由时，可以根据时延最小、跳数最少、带宽最大或者负载均衡等条件，选择 最适合的传输路径。第一NSN在第一USN和第一UE之间规划的通信路径可以称为第一路径。
在本申请中，复杂的路径计算由NSN集中实现。网络的拓扑是动态变化的，而通信路径的计算需要强大的算力支持。NSN部署在边缘数据中心，相比路由器，具有强大的算力，同时拥有MEC域内的实时拓扑，可以更快速，更准确的计算出最优路径。
S502、该网络服务节点基于该第一路径计算第一目标数，该第一目标数用于计算该第一路径上的转发设备转发数据包的出端口号。
在具体实施例中，第一NSN规划好上述第一USN和第一UE之间的传输路径(即第一路径)后，可以采用余数***RNS来实现数据在该第一路径中的转发。
具体的，第一NSN可以获取一组互质的数组，该数组中包括的数的个数与第一MEC域内包括的转发设备的个数相等。该域内的转发设备为除了用户设备UE、NSN和USN外的用于转发数据的设备，例如路由器、基站和网关等等。然后，第一NSN为该第一MEC域内的转发设备分配该互质数组中的数，每一个转发设备分配一个数，并将各个转发设备分配得到的数发送给对应的转发设备保存。该互质数组中的数分配给转发设备后可以称为转发设备的编号。
上述第一NSN规划得到第一USN和第一UE之间的第一路径后，可以获得该第一路径中各个转发设备的编号，以及获得该各个转发设备转发数据的出端口号。
一种可能的实施方式中，该第一路径可以为以第一USN为起点，以第一UE为终点的下行传输路径。那么，第一NSN可以获得两个数组，一个数组为该第一路径中各个转发设备的编号组成的数组，简称为下行编号数组，另一个数组为该各个转发设备转发第一USN向第一UE发送的数据(可以称为下行数据)的出端口号组成的数组，简称为下行端口数组。然后，第一NSN可以基于该下行编号数组和下行端口数组计算得到一个目标数，本申请中可以将该目标数称为下行目标数，该下行目标数即为上述S502中的第一目标数。该下行目标数对该各个转发设备中任意某一个设备的编号取余得到的余数为该某一个设备在下行端口数组中对应的出端口号，基于该特性，该下行目标数可以用于计算该第一路径上的转发设备转发下行数据的出端口号。
另一种可能的实施方式中，该第一路径可以为以第一UE为起点，以第一USN为终点的上行传输路径。同理，第一NSN可以获得两个数组，一个数组为该第一路径中各个转发设备的编号组成的数组，简称为上行编号数组，另一个数组为该各个转发设备转发第一UE向第一USN发送的数据(可以称为上行数据)的出端口号组成的数组，简称为上行端口数组。然后，第一NSN可以基于该上行编号数组和上行端口数组计算得到一个目标数，本申请中可以将该目标数称为上行目标数，该上行目标数即为上述S502中的第一目标数。该上行目标数对该各个转发设备中任意某一个设备的编号取余得到的余数为该某一个设备在上行端口数组中对应的出端口号，基于该特性，该上行目标数可以用于计算该第一路径上的转发设备转发上行数据包的出端口号，且转发设备的端口号总数要小于该转发设备的编号值。
可选的，虽然上行传输路径相比于下行传输路径的起点和终点对换了，但是上下行传输路径中包括的转发设备是相同的。或者，可选的，上行传输路径中包括的转发设备和下行传输路径中包括的转发设备不同，即该上行数据通过某一个路径传输，而该下行数据通过另一个路径传输。
不管是下行传输路径还是上行传输路径，计算对应目标数的方式是相同的，示例性的，具体的计算方式如下：
假设编号数组为{m1,m2,m3,...,mN}，端口数组为{x1,x2,x3,...,xN}，那么，
M＝m1*m2*m3*...*mN；即M为编号数组内所有数的乘积；
Mi＝M/mi，i＝1,2,3,...,N；即Mi为编号数组中，除去mi后其余数的乘积；
Li＝(1/Mi)％mi；Li为Mi的倒数对mi的取余得到；
X＝(L1*M1*x1+L2*M2*x2+...+LN*MN*xN)％M；X为所有Li*Mi*mi的和对M的取余得到，该X即为上述需要计算的第一目标数。
S503、该网络服务节点向入口转发设备发送该第一目标数，该入口转发设备为该第一路径中处于起点的设备的下一跳设备，该第一目标数用于添加到该入口转发设备发往该第一路径的终点设备的数据中。
在具体实施例中，上述第一NSN计算得到第一目标数后，将该第一目标数发送给上述第一路径中处于起点的设备的下一跳设备，该下一跳设备为该第一路径的入口转发设备。该入口转发设备和出口转发设备是相对而言的，若该第一路径为上述下行传输路径，第一路径中第一USN的下一跳转发设备为入口转发设备，第一UE的上一跳转发设备为出口转发设备；若该第一路径为上述上行传输路径，第一UE的下一跳转发设备为入口转发设备，第一USN的上一跳转发设备为出口转发设备。
可选的，若该上行传输路径和该下行传输路径中包括的转发设备相同，那么，下行传输路径中第一USN的下一跳转发设备为上行传输路径中第一USN的上一跳转发设备，下行传输路径中第一UE的上一跳转发设备为上行传输路径中第一UE的下一跳转发设备。
为了便于理解，示例性地，可以参见图6。在图6中，规划的第一路径包括的转发设备有转发设备1、转发设备2和转发设备3。对于下行传输路径，转发设备1为入口转发设备，转发设备3为出口转发设备。对于上行传输路径，转发设备3为入口转发设备，转发设备1为出口转发设备。
第一NSN除了将上述第一目标发送给第一路径的入口转发设备，还将上述第一UE和第一USN的IP地址也一起发送给该入口转发设备。该入口转发设备接收到该第一目标数、第一UE和第一USN的IP地址后，将这些信息保存以用于后续数据的转发。
一种可能的实施方式中，上述第一NSN是将该第一目标数、第一UE和第一USN的IP地址封装成一个数据包头的格式发送给该入口转发设备。在该数据包头中指明源地址和目的地址。该数据包头可以称为RNS头。
具体的，若上述第一路径为上行传输路径，则第一NSN向第一路径的入口转发设备发送的目标数为上述上行目标数，并指明该上行目标数关联的源地址和目的地址分别为第一UE的地址和第一USN的地址。若上述第一路径为下行传输路径，则第一NSN向第一路径的入口转发设备发送的目标数为上述下行目标数，指明该下行目标数关联的源地址和目的地址分别为第一USN的地址和第一UE的地址。为了便于理解，可以参见表1。
表1
目标数 关联的源地址 关联的目的地址
上行目标数 第一USN的地址 第一USN的地址
下行目标数 第一USN的地址 第一USN的地址
经过上述的操作，第一UE和第一USN之间可以实现数据的传输。上述第一路径的入口转发设备接收到需要转发的数据(包括数据包或控制指令报文等)后，根据数据中的源地址和目的地址在本地存储器中查找到对应的目标数即上述第一目标数，然后，将该第一目标数添 加在该数据中，例如添加在数据包的包头或命令报文的报文头等，并基于该第一目标数计算出数据的出端口号，然后，将添加了目标数的数据从该出端口号对应的端口发送给下一跳转发设备。后面的转发设备同样的，在接收到该数据后，获取数据中的第一目标数，基于该第一目标数计算出数据的出端口号，然后，将数据从该出端口号对应的端口发送给下一跳转发设备。当数据发送到出口转发设备时，出口转发设备基于该数据中的第一目标数计算得到出端口号，并将该第一目标数从该数据中去掉，然后，从该出端口号对应的出端口转发去掉第一目标数的数据。
一种可能的实施方式中，在上述第一UE和第一USN绑定后，上述第一NSN可以同时规划该第一UE和第一USN之间的上行传输路径和下行传输路径；或者，可选的，在上述第一UE和第一USN绑定后，上述第一NSN可以只规划该第一UE到第一USN的上行传输路径；或者，可选的，在上述第一UE和第一USN绑定后，上述第一NSN可以只规划该第一USN到第一UE之间的下行传输路径。
为了便于理解上述介绍的通信处理方法，下面分别举例介绍下行数据和上行数据的传输过程。可以示例性地参见图7，图7示例性示出了一个MEC域内的网络架构示意图，可以看到，转发设备的编号都是互质的数值，每个转发设备包括多个通信端口，每个通信端口都有对应的端口号。
首先，以图7中用户服务节点1(简称为USN1)和用户设备1(简称为UE1)之间的下行数据传输为例。在USN1和UE1完成绑定后，网络服务节点1(简称为NSN1)根据该MEC域内的全局视图，在USN1到UE1，可以看到有两条路径(实际网络中，可能会更多)，第一条路径为从转发设备9→转发设备4→转发设备5；第二条路径为从转发设备9→转发设备7→转发设备11→转发设备17→转发设备4→转发设备5；从时延最小或调数最小的角度来规划，则选定第一条路径，从而规划出路由路径。然后，根据该第一条路径中转发设备的编号以及各个出端口号计算得到目标数为81，具体的计算过程如下：
上述第一条路径对应的下行编号数组为{m1，m2，m3}＝{9，4，5}，下行端口数组为{x1，x2，x3}＝{0，1，1}，那么，
M＝m1*m2*m3＝9*4*5＝180；
M1＝M/m1＝180/9＝20，M2＝M/m2＝180/4＝45，M3＝M/m3＝180/5＝36；
L1＝(1/M1)％m1＝(1/20)％9＝5，L2＝(1/M2)％m2＝(1/45)％4＝1，L3＝(1/M3)％m3＝(1/36)％5＝1；
X＝(L1*M1*x1+L2*M2*x2+L3*M3*x3)＝(5*20*0+1*45*1+1*36*1)％180＝81。
NSN1计算得到目标数81后，将该81，以及该81关联的源地址(USN1的地址)和目的地址即(UE1的地址)发送给入口转发设备(转发设备9)。
在转发设备9接收到来自USN1的数据包，可以解析该数据包，获知该数据包的源地址为USN1的地址，目的地址为UE1的地址，并在本地查找到对应的目标数81，然后，将目标数81添加到该数据包包头。且，该转发设备基于该目标数81计算得到该数据包的出端口号，具体的，用该目标数81对转发设备9的编号9进行取余操作得到余数0，则该0即为该数据包的出端口号。然后，转发设备9将携带有目标数81的数据包从端口0转发出去。
该转发设备9的端口0转发出去的数据包被传输到转发设备4，转发设备4接收该数据包，获取该数据包包头中的目标数81，用该目标数81对转发设备4的编号4进行取余操作得到余数1，则该1即为该数据包的出端口号。然后，转发设备4将数据包重新封装好并从端口1转发出去。
该转发设备4的端口1转发出去的数据包被传输到转发设备5，转发设备5接收该数据包，获取该数据包包头中的目标数81，用该目标数81对转发设备5的编号5进行取余操作得到余数1，则该1即为该数据包的出端口号。另外，由于转发设备5的端口1连接的即为目的地UE1，因此，转发设备5将接收到的数据包包头中的目标数81去掉后再从端口1转发给UE1。
下面以图7中USN1和UE1之间的上行数据传输为例。在USN1和UE1完成绑定后，网络服务节点1(简称为NSN1)根据该MEC域内的全局视图，规划出从UE1到USN1的传输路径为从转发设备5→转发设备4→转发设备9。然后，根据该路径中转发设备的编号以及各个出端口号计算得到目标数为100，具体的计算过程如下：
上述第一条路径对应的下行编号数组为{m1，m2，m3}＝{5，4，9}，下行端口数组为{x1，x2，x3}＝{0，0，1}，那么，
M＝m1*m2*m3＝5*4*9＝180；
M1＝M/m1＝180/5＝36，M2＝M/m2＝180/4＝45，M3＝M/m3＝180/9＝20；
L1＝(1/M1)％m1＝(1/36)％5＝1，L2＝(1/M2)％m2＝(1/45)％4＝1，L3＝(1/M3)％m3＝(1/20)％9＝5；
X＝(L1*M1*x1+L2*M2*x2+L3*M3*x3)＝(1*36*0+1*45*0+5*20*1)％180＝100。
NSN1计算得到目标数100后，将该100，以及该100关联的源地址(UE1的地址)和目的地址即(USN1的地址)发送给入口转发设备(转发设备5)。
在转发设备5接收到来自UE1的数据包，可以解析该数据包，获知该数据包的源地址为UE1的地址，目的地址为USN1的地址，因此，在本地查找到对应的目标数100，然后，将目标数100添加到该数据包包头。且，该转发设备基于该目标数100计算得到该数据包的出端口号，具体的，用该目标数100对转发设备5的编号5进行取余操作得到余数0，则该0即为该数据包的出端口号。然后，转发设备5将携带有目标数100的数据包从端口0转发出去。
该转发设备5的端口0转发出去的数据包被传输到转发设备4，转发设备4接收该数据包，获取该数据包包头中的目标数100，用该目标数100对转发设备4的编号4进行取余操作得到余数0，则该0即为该数据包的出端口号。然后，转发设备4将数据包重新封装好并从端口0转发出去。
该转发设备4的端口0转发出去的数据包被传输到转发设备9，转发设备9接收该数据包，获取该数据包包头中的目标数100，用该目标数100对转发设备9的编号9进行取余操作得到余数1，则该1即为该数据包的出端口号。另外，由于转发设备9的端口1连接的即为目的地USN1，因此，转发设备9将接收到的数据包包头中的目标数100去掉后再从端口1转发给USN1。
需要说明的是，上述图7介绍的本申请提供的通信处理方法以数据包发送为例介绍，但该通信处理方法不限于数据包通信的情况下使用，控制命令等信息通信的情况下也可以使用，本申请提供的通信处理方法不限制通信的信息的类型。另外，上述图7中UE1和USN1之间的上行传输路径和下行传输路径包括的转发设备相同，均为转发设备4、转发设备5和转发设备9，但在实际实现过程中UE和其对应的USN之间的上行传输路径和下行传输路径包括的转发设备可以不相同，即该上行传输路径和下行传输路径可以为不同的路径。
一种可能的实施方式中，在上述第一路径无法实现上述第一USN和上述第一UE之间的通信的情况下，上述第一NSN可以重新规划该第一UE和该第一USN之间的通信路径得到 第二路径；然后，基于该第二路径计算第二目标数，并向该第二路径的入口转发设备发送该二目标数，该第二目标数用于计算该第二路径上的转发设备转发数据的出端口号；该第二目标数用于添加到该入口转发设备发往该第二路径的终点设备的数据中。
具体实施例中，在上述第一路径出现故障、出现拥堵或者第一UE在第一MEC域内连接的接入设备切换等情况下，第一NSN可以重新规划第一UE和第一USN之间的通信路径。该第一UE在第一MEC域内连接的接入设备切换例如可以是：第一UE在该第一MEC域内连接的基站由第一基站切换为第二基站等等。
第一NSN规划好上述第二路径后，同样计算该第二路径对应的第二目标数，然后将该第二目标数下发给第二路径的入口转发设备等等，具体的实现可以参考上述图5所示的通信处理方法的描述，此处不再赘述。
一种可能的实施方式中，上述第二路径的入口转发设备与上述第一路径的入口转发设备为同一个设备，例如，在第一UE的接入设备切换的情况下，第一USN往第一UE的下一跳设备没有改变，再例如，在第一路径中间的转发设备出现故障，而第一UE或第一USN的下一跳设备均没有改变等等。那么，在这些情况下，该第二路径的入口转发设备接收到第二目标数后，可以将本地存储的第一目标数替换成该第二目标数。
本申请实施例可以减少第一UE和第一USN之间的通信中断的概率，提高整个通信网络的通信性能。
综上所述，在本申请提供的通信处理方法中，首先，网络服务节点NSN拥有全局网络拓扑视图，可以根据带宽、时延、约束条件等要求指定具体的路径，达到诸如流量工程等功能，从而可以快速规划出UE和USN之间的通信路径。
其次，本申请的通信处理方法中无需路由表，避免了因流量激增导致的路由表膨胀问题；且复杂的路径计算由NSN集中实现，相比于现有的MPLS和SR，降低了转发设备负担，以及极大减少了繁琐的配置。
再者，因为UE和其USN是绑定的，上行传输路径一定是从UE到其USN，下行传输路径一定是从USN到其对应的UE，因此对于上下行数据，在UE和其USN初始绑定时，由NSN进行UE和USN之间的路由计算，并给通信路径的入口转发设备下发对应的目标数，该目标数可以重复使用，后续不需要频繁计算，除非路由条件改变；不像采用OpenFlow或KeyFlow协议的路由方案，每当一个新数据包到达入口路由器时，都需要触发pakcket-in消息，将该数据包扔给控制器，由控制器重新规划路由。即在本申请中，可以极大减少NSN的处理负担，提升NSN的性能，另外，由于无需实时计算通信路径，因此还可以减少信令通信负担和降低数据传输时延，提高数据传输效率。
另外，上述采用OpenFlow或KeyFlow协议的路由方案中，入口路由器进行数据转发的时候，仍然需要查表获取出端口号，而不是通过目标数来计算出端口号，因此，相比于此，本申请在入口转发设备就通过目标数计算数据的出端口号，无需查表来查找出端口号，从而解决了路由表或流表等膨胀导致的存储资源占用过多等问题。并且，上述采用OpenFlow或KeyFlow协议的路由方案中，还需要给入口路由器发送modified-field action消息以指示入口路由器将目标数添加到数据包头，并且需要给出口路由器发送modified-field action消息以指示出口路由器将数据包头的目标数去掉，流程繁琐且占用通信资源，而本申请无需执行这两个步骤，简化了操作流程节省了通信资源。
其次，本申请的通信处理方法满足未来以分布式DC/MEC为中心的流量模型中数据转发更加分布式、动态化、短距/短跳数的需求，与分布式MEC架构完美结合，比目前主流的SR 方案和KeyFlow结合SDN的方案配置更简单，协议也更简单，可以极大降低部署和维护成本，提高部署和维护效率。
上述主要对本申请实施例提供的通信处理方法进行了介绍。可以理解的是，各个设备为了实现上述对应的功能，其包含了执行各个功能相应的硬件结构和/或软件模块。结合本文中所公开的实施例描述的各示例的单元及步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用使用不同方法来实现所描述的功能，但这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图8示出了装置的一种可能的逻辑结构示意图，该装置可以是上述网络服务节点所在的装置(例如该网络服务节点所在的服务器、芯片或处理***等)。该装置800包括规划单元801、计算单元802和发送单元803。其中：
规划单元801，用于在感知用户服务节点和用户设备之间完成认证的情况下，规划该用户服务节点和该用户设备之间的通信路径得到第一路径，该用户服务节点用于为该用户设备提供服务；
计算单元802，用于基于该第一路径计算第一目标数，该第一目标数用于计算该第一路径上的转发设备转发数据的出端口号；
发送单元803，用于向入口转发设备发送该第一目标数，该入口转发设备为该第一路径中处于起点的设备的下一跳设备，该第一目标数用于添加到该入口转发设备发往该第一路径的终点设备的数据中。
一种可能的实施方式中，该用户服务节点和该用户设备属于同一个边缘云下覆盖的节点。
一种可能的实施方式中，该规划单元801，还用于在该第一路径无法实现该用户服务节点和该用户设备之间的通信的情况下，规划该用户设备和该用户服务节点之间的通信路径得到第二路径；
该计算单元802，还用于基于该第二路径计算第二目标数，该第二目标数用于计算该第二路径上的转发设备转发数据的出端口号；
该发送单元803，还用于向该入口转发设备发送该第二目标数，该第二目标数用于添加到该入口转发设备发往该第二路径的终点设备的数据中。
一种可能的实施方式中，该第一路径为从该用户设备到该用户服务节点的路径；该入口转发设备为将该用户设备接入通信网络的接入设备；
该第一路径无法实现该用户服务节点和该用户设备之间的通信的情况，包括：
将该用户设备接入该通信网络的接入设备发生变更。
图8所示装置800中各个单元的具体操作以及有益效果可以参见上述图5及其可能的方法实施例中对应的描述，此处不再赘述。
在采用对应各个功能划分各个功能模块的情况下，图9示出了装置的一种可能的逻辑结 构示意图，该装置可以是上述入口转发设备、该入口转发设备的芯片或处理***等。该装置900包括接收单元901、写入单元902、计算单元903和发送单元904。其中：
接收单元901，用于接收第一目标数，该第一目标数用于按照第一路径转发用户服务节点和用户设备之间的通信数据，该第一路径为在该用户服务节点和该用户设备之间完成认证的情况下规划得到，该用户服务节点用于为该用户设备提供服务；
该接收单元901，还用于接收第一数据，并基于该第一数据查找到该第一目标数；
写入单元902，用于将该第一目标数写入该第一数据得到第二数据；
计算单元903，用于基于该第一目标数计算出端口号；
发送单元904，用于将该第二数据从该出端口号发送出去。
一种可能的实施方式中，该接收单元901，还用于：
接收第二目标数，将本地存储的该第一目标数替换为该第二目标数；该第二目标数用于按照第二路径转发用户服务节点和用户设备之间的通信数据，该第二路径为在该第一路径无法实现该用户服务节点和该用户设备之间的通信的情况下规划得到。
图9所示装置900中各个单元的具体操作以及有益效果可以参见上述图5及其可能的方法实施例中对应的描述，此处不再赘述。
图10所示为本申请提供的装置的一种可能的硬件结构示意图，该装置可以是上述实施例所述方法中的网络服务节点所在的装置(例如该网络服务节点所在的服务器、芯片或处理***等)。该装置1000包括：处理器1001、存储器1002和通信接口1003。处理器1001、通信接口1003以及存储器1002可以相互连接或者通过总线1004相互连接。
示例性的，存储器1002用于存储装置1000的计算机程序和数据，存储器1002可以包括但不限于是随机存储记忆体(random access memory，RAM)、只读存储器(read-only memory，ROM)、可擦除可编程只读存储器(erasable programmable read only memory，EPROM)或便携式只读存储器(compact disc read-only memory，CD-ROM)等。
通信接口1003包括发送接口和接收接口，通信接口1003的个数可以为多个，用于支持装置1000进行通信，例如接收或发送数据或消息等。
示例性的，处理器1001可以是中央处理器单元、通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，数字信号处理器和微处理器的组合等等。处理器1001可以用于读取上述存储器1002中存储的程序，使得装置1000执行如上述图5及其可能的实施例中所述的任一种通信处理方法中NSN所做的操作。
一种可能的实施方式中，处理器1001可以用于读取上述存储器1002中存储的程序，执行如下操作：
在感知用户服务节点和用户设备之间完成认证的情况下，规划该用户服务节点和该用户设备之间的通信路径得到第一路径，该用户服务节点用于为该用户设备提供服务；基于该第一路径计算第一目标数，该第一目标数用于计算该第一路径上的转发设备转发数据的出端口号；通过通信接口向入口转发设备发送该第一目标数，该入口转发设备为该第一路径中处于起点的设备的下一跳设备，该第一目标数用于添加到该入口转发设备发往该第一路径的终点设备的数据中。
图10所示装置1000中各个单元的具体操作以及有益效果可以参见上述图5及其可能的 方法实施例中对应的描述，此处不再赘述。
图11所示为本申请提供的装置的一种可能的硬件结构示意图，该装置可以是上述实施例所述方法中的入口转发设备、入口转发设备的芯片或处理***等。该装置1100包括：处理器1101、存储器1102和通信接口1103。处理器1101、通信接口1103以及存储器1102可以相互连接或者通过总线1104相互连接。
示例性的，存储器1102用于存储装置1100的计算机程序和数据，存储器1102可以包括但不限于是随机存储记忆体(random access memory，RAM)、只读存储器(read-only memory，ROM)、可擦除可编程只读存储器(erasable programmable read only memory，EPROM)或便携式只读存储器(compact disc read-only memory，CD-ROM)等。
通信接口1103包括发送接口和接收接口，通信接口1103的个数可以为多个，用于支持装置1100进行通信，例如接收或发送数据或消息等。
示例性的，处理器1101可以是中央处理器单元、通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，数字信号处理器和微处理器的组合等等。处理器1101可以用于读取上述存储器1102中存储的程序，使得装置1100执行如上述图5及其可能的实施例中所述的任一种通信处理方法中入口转发设备所做的操作。
一种可能的实施方式中，处理器1101可以用于读取上述存储器1102中存储的程序，执行如下操作：
通过通信接口接收第一目标数，该第一目标数用于按照第一路径转发用户服务节点和用户设备之间的通信数据，该第一路径为在该用户服务节点和该用户设备之间完成认证的情况下规划得到，该用户服务节点用于为该用户设备提供服务；通过通信接口接收第一数据，并基于该第一数据查找到该第一目标数；将该第一目标数写入该第一数据得到第二数据；基于该第一目标数计算出端口号，通过通信接口将该第二数据从该出端口号发送出去。
图11所示装置1100中各个单元的具体操作以及有益效果可以参见上述图5及其可能的方法实施例中对应的描述，此处不再赘述。
本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，该计算机程序被处理器执行以实现上述图5及其可能的方法实施例中任一实施例所述方法中NSN所做的操作；或者，该计算机程序被处理器执行以实现上述图5及其可能的方法实施例中任一实施例所述方法中入口转发设备所做的操作。
本申请实施例还提供一种计算机程序产品，当该计算机程序产品被计算机读取并执行时，上述图5及其可能的方法实施例中任一实施例所述方法中NSN所做的操作将被执行；或者，上述图5及其可能的方法实施例中任一实施例所述方法中入口转发设备所做的操作将被执行。
综上所述，在用户设备(user equipment，UE)和用户服务节点USN绑定后，规划该两者之间的通信路径，并基于余数***的方法来实现该两者的通信。因为UE和其USN是绑定的，上行传输路径一定是从UE到其USN，下行传输路径一定是从USN到其对应的UE，因此对于上下行数据，在UE和其USN初始绑定时，由NSN进行UE和USN之间的路由计算，并给通信路径的入口转发设备下发对应的目标数，该目标数可以重复使用，后续不需要频繁计算，除非路由条件改变；不像现有方案中的OpenFlow或KeyFlow协议，每当一个新数据包到达入路由器时，都需要触发pakcket-in消息，将该数据包扔给控制器，由控制器重新规划 路由。即在本申请中，可以极大减少NSN的处理负担，提升NSN的性能，另外，由于无需实时计算通信路径，因此还可以减少信令通信负担和降低数据传输时延，提高数据传输效率。
其次，本申请的通信处理方法满足未来以分布式DC/MEC为中心的流量模型中数据转发更加分布式、动态化、短距/短跳数的需求，与分布式MEC架构完美结合，比目前主流的SR方案和KeyFlow结合SDN的方案配置更简单，协议也更简单，可以极大降低部署和维护成本，提高部署和维护效率。
再者，本申请的通信处理方法中无需路由表，避免了因流量激增导致的路由表膨胀问题；且复杂的路径计算由NSN集中实现，相比于现有的MPLS和SR，降低了转发设备负担，以及极大减少了繁琐的配置。
最后应说明的是：以上各实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述各实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (16)

  1. 一种通信处理方法，其特征在于，所述方法包括：
    在感知用户服务节点和用户设备之间完成认证的情况下，规划所述用户服务节点和所述用户设备之间的通信路径得到第一路径，所述用户服务节点用于为所述用户设备提供服务；
    基于所述第一路径计算第一目标数，所述第一目标数用于计算所述第一路径上的转发设备转发数据的出端口号；
    向入口转发设备发送所述第一目标数，所述入口转发设备为所述第一路径中处于起点的设备的下一跳设备，所述第一目标数用于添加到所述入口转发设备发往所述第一路径的终点设备的数据中。
  2. 根据权利要求1所述的方法，其特征在于，所述用户服务节点和所述用户设备属于同一个边缘云下覆盖的节点。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    在所述第一路径无法实现所述用户服务节点和所述用户设备之间的通信的情况下，规划所述用户设备和所述用户服务节点之间的通信路径得到第二路径；
    基于所述第二路径计算第二目标数，所述第二目标数用于计算所述第二路径上的转发设备转发数据的出端口号；
    向所述入口转发设备发送所述第二目标数，所述第二目标数用于添加到所述入口转发设备发往所述第二路径的终点设备的数据中。
  4. 根据权利要求3所述的方法，其特征在于，所述第一路径为从所述用户设备到所述用户服务节点的路径；所述入口转发设备为将所述用户设备接入通信网络的接入设备；
    所述第一路径无法实现所述用户服务节点和所述用户设备之间的通信的情况，包括：
    将所述用户设备接入所述通信网络的接入设备发生变更。
  5. 一种通信处理方法，其特征在于，所述方法包括：
    接收第一目标数，所述第一目标数用于按照第一路径转发用户服务节点和用户设备之间的通信数据，所述第一路径为在所述用户服务节点和所述用户设备之间完成认证的情况下规划得到，所述用户服务节点用于为所述用户设备提供服务；
    接收第一数据，并基于所述第一数据查找到所述第一目标数；
    将所述第一目标数写入所述第一数据得到第二数据；
    基于所述第一目标数计算出端口号，将所述第二数据从所述出端口号发送出去。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    接收第二目标数，将本地存储的所述第一目标数替换为所述第二目标数；所述第二目标数用于按照第二路径转发用户服务节点和用户设备之间的通信数据，所述第二路径为在所述第一路径无法实现所述用户服务节点和所述用户设备之间的通信的情况下规划得到。
  7. 一种通信处理装置，其特征在于，所述装置包括：
    规划单元，用于在感知用户服务节点和用户设备之间完成认证的情况下，规划所述用户 服务节点和所述用户设备之间的通信路径得到第一路径，所述用户服务节点用于为所述用户设备提供服务；
    计算单元，用于基于所述第一路径计算第一目标数，所述第一目标数用于计算所述第一路径上的转发设备转发数据的出端口号；
    发送单元，用于向入口转发设备发送所述第一目标数，所述入口转发设备为所述第一路径中处于起点的设备的下一跳设备，所述第一目标数用于添加到所述入口转发设备发往所述第一路径的终点设备的数据中。
  8. 根据权利要求7所述的装置，其特征在于，所述用户服务节点和所述用户设备属于同一个边缘云下覆盖的节点。
  9. 根据权利要求7或8所述的装置，其特征在于，
    所述规划单元，还用于在所述第一路径无法实现所述用户服务节点和所述用户设备之间的通信的情况下，规划所述用户设备和所述用户服务节点之间的通信路径得到第二路径；
    所述计算单元，还用于基于所述第二路径计算第二目标数，所述第二目标数用于计算所述第二路径上的转发设备转发数据的出端口号；
    所述发送单元，还用于向所述入口转发设备发送所述第二目标数，所述第二目标数用于添加到所述入口转发设备发往所述第二路径的终点设备的数据中。
  10. 根据权利要求9所述的装置，其特征在于，所述第一路径为从所述用户设备到所述用户服务节点的路径；所述入口转发设备为将所述用户设备接入通信网络的接入设备；
    所述第一路径无法实现所述用户服务节点和所述用户设备之间的通信的情况，包括：
    将所述用户设备接入所述通信网络的接入设备发生变更。
  11. 一种通信处理装置，其特征在于，所述装置包括：
    接收单元，用于接收第一目标数，所述第一目标数用于按照第一路径转发用户服务节点和用户设备之间的通信数据，所述第一路径为在所述用户服务节点和所述用户设备之间完成认证的情况下规划得到，所述用户服务节点用于为所述用户设备提供服务；
    所述接收单元，还用于接收第一数据，并基于所述第一数据查找到所述第一目标数；
    写入单元，用于将所述第一目标数写入所述第一数据得到第二数据；
    计算单元，用于基于所述第一目标数计算出端口号；
    发送单元，用于将所述第二数据从所述出端口号发送出去。
  12. 根据权利要求11所述的装置，其特征在于，所述接收单元，还用于：
    接收第二目标数，将本地存储的所述第一目标数替换为所述第二目标数；所述第二目标数用于按照第二路径转发用户服务节点和用户设备之间的通信数据，所述第二路径为在所述第一路径无法实现所述用户服务节点和所述用户设备之间的通信的情况下规划得到。
  13. 一种通信处理装置，其特征在于，包括处理器和存储器；其中，所述存储器用于存储计算机程序，所述处理器用于调用所述计算机程序，以使得所述装置执行如权利要求1至4任一项所述的方法。
  14. 一种通信处理装置，其特征在于，包括处理器和存储器；其中，所述存储器用于存储计算机程序，所述处理器用于调用所述计算机程序，以使得所述装置执行如权利要求5或6所述的方法。
  15. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行以实现权利要求1至4任意一项所述的方法；或者，所述计算机程序被处理器执行以实现权利要求5或6所述的方法。
  16. 一种计算机程序产品，其特征在于，当计算机程序产品在计算机上运行时，使得所述计算机执行如权利要求1至4任意一项所述的方法；或者，使得所述计算机执行如权利要求5或6所述的方法。
PCT/CN2022/093444 2021-05-21 2022-05-18 通信处理方法及相关设备 WO2022242661A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP22803981.4A EP4329374A1 (en) 2021-05-21 2022-05-18 Communication processing method and related device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110557277.4A CN115379525A (zh) 2021-05-21 2021-05-21 通信处理方法及相关设备
CN202110557277.4 2021-05-21

Publications (1)

Publication Number Publication Date
WO2022242661A1 true WO2022242661A1 (zh) 2022-11-24

Family

ID=84058670

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/093444 WO2022242661A1 (zh) 2021-05-21 2022-05-18 通信处理方法及相关设备

Country Status (3)

Country Link
EP (1) EP4329374A1 (zh)
CN (1) CN115379525A (zh)
WO (1) WO2022242661A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150207724A1 (en) * 2012-12-18 2015-07-23 Juniper Networks, Inc. Dynamic control channel establishment for software-defined networks having centralized control
CN108064443A (zh) * 2017-09-30 2018-05-22 深圳前海达闼云端智能科技有限公司 一种代理转发方法和装置、代理服务器和多级代理网络
CN108282402A (zh) * 2018-01-24 2018-07-13 中南大学 数据中心网络中基于编码的包散射方法
CN109150604A (zh) * 2018-08-20 2019-01-04 南瑞集团有限公司 一种基于sdn的电力通信网络***及跨域切片方法
CN111600754A (zh) * 2020-05-11 2020-08-28 重庆邮电大学 一种面向tsn和非tsn互联的工业异构网络调度方法
CN112637368A (zh) * 2021-03-10 2021-04-09 江苏金恒信息科技股份有限公司 分布式工业数据采集***及方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150207724A1 (en) * 2012-12-18 2015-07-23 Juniper Networks, Inc. Dynamic control channel establishment for software-defined networks having centralized control
CN108064443A (zh) * 2017-09-30 2018-05-22 深圳前海达闼云端智能科技有限公司 一种代理转发方法和装置、代理服务器和多级代理网络
CN108282402A (zh) * 2018-01-24 2018-07-13 中南大学 数据中心网络中基于编码的包散射方法
CN109150604A (zh) * 2018-08-20 2019-01-04 南瑞集团有限公司 一种基于sdn的电力通信网络***及跨域切片方法
CN111600754A (zh) * 2020-05-11 2020-08-28 重庆邮电大学 一种面向tsn和非tsn互联的工业异构网络调度方法
CN112637368A (zh) * 2021-03-10 2021-04-09 江苏金恒信息科技股份有限公司 分布式工业数据采集***及方法

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
3GPP TS 23.303
3GPP TS23.501
3GPP TS33.501
3GPP TS33.535

Also Published As

Publication number Publication date
CN115379525A (zh) 2022-11-22
EP4329374A1 (en) 2024-02-28

Similar Documents

Publication Publication Date Title
EP2911348B1 (en) Control device discovery in networks having separate control and forwarding devices
CN112448900B (zh) 一种数据传输方法及装置
CN108574616A (zh) 一种处理路由的方法、设备及***
JP7121759B2 (ja) 通信方法、ネットワークサーバ、及びコンピュータ読取可能記憶媒体
US10425327B2 (en) System and method for routing in software defined networks using a flow header
US9668160B2 (en) Topology discovery based on SCTP/X2 snooping
CN111263373B (zh) 数据处理方法、控制器和转发设备
US20170149685A1 (en) Address information publishing method and apparatus
US10965594B2 (en) Pseudo wire load sharing method and device
WO2015113297A1 (zh) 数据传输方法、传输控制方法及设备
US9294986B2 (en) Topology discovery based on explicit signaling
CN113923161A (zh) 一种报文转发方法及装置
CN114710975B (zh) 一种用于多域间传输多传输网络上下文标识的方法、基站、网元及装置
CN110708229B (zh) 一种收发消息的方法、装置和***
US20190334814A1 (en) Path establishment method and device, and network node
WO2022242661A1 (zh) 通信处理方法及相关设备
CN111464441A (zh) 一种通信方法及装置
CN114980243A (zh) 一种数据转发方法、装置及存储介质
EP3471351B1 (en) Method and device for acquiring path information about data packet
CN113595915A (zh) 转发报文的方法及相关设备
CN114268577B (zh) 网络连接的建立方法、装置、设备及存储介质
EP4214914A1 (en) First node, second node, and methods performed thereby for configuring handling of two or more ingress member flows
CN116366593A (zh) 报文转发方法及相关装置
WO2017079901A1 (zh) 一种路由方法及路由装置

Legal Events

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

Ref document number: 22803981

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022803981

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022803981

Country of ref document: EP

Effective date: 20231120

NENP Non-entry into the national phase

Ref country code: DE